Zxg10-Mscvlr (v3.0) Operation Manual (Volume II)

ZXG10
Z ZT TE E G GS SM M W WL LL L S SY YS ST TE EM M
GSM W LL SYSTEM
Operation Manual
OF
ZXG10-MSC/VLR (V3.0) Vol ume II
SH E NZHE N, CH INA
Operation Manual of ZXG10-MSC/VLR Vol. II
Table of Contents
6 6.1 6.1.1 6.1.2 6.1.3 6.2 6.2.1 6.2.2 6.2.3 6.2.4 6.2.5 7 7.1 7.1.1 7.1.2 7.2 7.2.1 7.2.2 7.2.3 7.2.4 7.2.5 7.2.6 7.2.7 7.2.8 7.3 7.3.1 7.3.2 7.3.3 7.3.4 7.4 8 8.1 8.2 8.2.1 8.2.2 8.3 8.3.1 8.3.2 8.3.3 8.3.4 8.3.5 8.3.6 8.4 8.4.1 8.4.2 User Tracing System .............................................................................1 System Overview......................................................................................1 Main Functions ..........................................................................................1 Interfaces ...................................................................................................2 Number Types...........................................................................................3 Basic Operations ......................................................................................5 Real-time Tracing .....................................................................................6 Tracing Map...............................................................................................10 Query History Information .......................................................................13 Query the Location Information..............................................................15 Maintenance Tools ...................................................................................16 Service Observation System ...............................................................18 System Overview......................................................................................18 System Architecture .................................................................................18 System Functions .....................................................................................18 Basic Operations ......................................................................................20 Introduction to the Interfaces ..................................................................20 Statistics Observation..............................................................................21 State Observation.....................................................................................26 Failure observation...................................................................................29 User Observation......................................................................................35 Base Station Management......................................................................42 Inter-office Observation ...........................................................................51 No.7 Observation......................................................................................56 Database Tool...........................................................................................67 Database List Creation Tool for MSC Service Failure........................67 DB List Creation Tool for VLR Service Failure List .............................69 DB List Creation Tool for TM Service Failure List ...............................69 DB List Creation Tool for MP_MP data flow.........................................69 Windows Management ............................................................................69 Billing System .........................................................................................71 Mobile Billing System ...............................................................................71 Introduction to ZXG10 Billing System ...................................................71 Performance introduction........................................................................72 Bill Data Management..............................................................................73 Operations on the Alarm Management Interface ................................89 User Logon................................................................................................89 Operation Management ...........................................................................92 Offline Bills .................................................................................................93 Bill Browsing and Querying .....................................................................97 Bill Field Settings ......................................................................................101 Setting Parameters...................................................................................103 Introduction to Charge Monitoring System ...........................................105 Module Functions .....................................................................................105 Module Structure ......................................................................................107
Page I of IV
8.5 8.5.1 8.5.2 8.5.3 8.5.4 8.5.5 8.5.6 8.5.7 8.6 8.6.1 8.6.2 8.6.3 8.6.4 8.6.5 8.6.6 8.6.7 9 9.1 9.1.1 9.1.2 9.1.3 9.2 9.2.1 9.2.2 9.2.3 9.3 9.3.1 9.3.2 9.3.3 9.3.4 9.4 10 10.1 10.2 10.3 11 11.1 11.1.1 11.1.2 11.1.3 11.2 11.2.1 11.2.2 11.2.3 11.2.4 11.2.5 11.2.6 11.2.7 11.2.8
Charge Monitoring Management ...........................................................108 Introduction to Main Interface .................................................................108 Foreground Monitoring ............................................................................111 Parameter Settings...................................................................................114 Transmission Filtering ..............................................................................116 Receive Monitoring ...................................................................................117 Synchronization 129.................................................................................118 Alarm Interface..........................................................................................119 Billing System Operations .......................................................................120 Query Bills ..................................................................................................120 Bill Offline ...................................................................................................121 Add, Delete Billing Operator ...................................................................121 The Foreground Monitoring ....................................................................122 Bill Receive Monitoring ............................................................................122 Transmission Filtering ..............................................................................123 Common Charge Alarms Recovery Methods ......................................123 Variable Control System.......................................................................125 System Overview......................................................................................125 Main Functions ..........................................................................................125 Introduction to Interfaces .........................................................................126 System Management ...............................................................................127 Mobility security management................................................................127 Basic Concepts .........................................................................................128 Basic Operations of VLR Module on Server Security Variables .......130 Basic Operations of VLR Module on Foreground Security Variables 137 Variable Control........................................................................................138 A-interface Variable Control on MSC Module ......................................138 CC Variable Control for MSC Module ...................................................141 Number Expansion Variable and TM Control ......................................143 Service Variable Control..........................................................................144 Selecting Service Control Variable ........................................................153 Log Viewer................................................................................................154 View Logs ..................................................................................................154 Save or Delete Logs.................................................................................156 Observe Tools ...........................................................................................156 Fault Management System ..................................................................158 System Overview......................................................................................158 Functions ....................................................................................................158 Performance ..............................................................................................159 System Architecture .................................................................................159 Background Interface Operations ..........................................................160 Introduction................................................................................................160 Configuration Tree....................................................................................161 Real-time Observation .............................................................................162 Current Alarms ..........................................................................................162 Rack Map ...................................................................................................162 Man-machine Commands .......................................................................164 Query Historical Alarms And Notifications ............................................169 Query Current Alarms ..............................................................................172
Page II of IV
11.2.9 11.2.10 11.2.11 11.2.12 11.2.13 11.2.14 11.2.15 11.2.16 11.3 11.4 11.5 11.5.1 11.5.2 12 12.1 12.2 12.2.1 12.2.2 12.2.3 12.2.4 13 13.1 13.2 13.3 13.4 14 14.1 14.2 14.2.1 14.2.2 14.2.3 14.2.4 14.2.5 14.2.6 14.2.7 14.2.8 14.2.9 14.2.10 14.2.11 14.2.12 15 15.1 15.2 15.3 16 16.1 16.2 16.3 16.4
Set Alarm Levels .......................................................................................172 Alarm Mask Settings ................................................................................174 Notification Masking .................................................................................176 Environment Setting .................................................................................177 Set IMSI Authentication ...........................................................................178 Alarm Database ........................................................................................180 Other Settings ...........................................................................................181 Chang over Billing Server .......................................................................182 Connect Alarm panel................................................................................183 Real-time Alarm Text Output ..................................................................184 Examples of Fault Management ............................................................185 Query Current Alarms ..............................................................................185 Query History Alarms and Notifications ................................................185 Diagnosis and Test System.................................................................186 System Overview......................................................................................186 Basic Operations ......................................................................................187 Intra-module Real-Time Test..................................................................188 Intra-module Routine Test.......................................................................190 Inter-module Real-Time Test..................................................................193 Inter-module Routine Test.......................................................................195 File Management System .....................................................................197 System Overview......................................................................................197 Directory Structure....................................................................................197 Basic Operations ......................................................................................198 Reference for Exceptions ........................................................................202 Version Management System .............................................................203 System Overview......................................................................................203 Basic Operations ......................................................................................204 MP Version Management........................................................................204 How to Query MP Versions .....................................................................212 How to Add an MP Version.....................................................................213 How to Copy an MP Version...................................................................213 How to Reset an MP Version .................................................................213 PP version management .........................................................................214 How to Query PP Version History..........................................................220 How to Query a PP Version....................................................................220 How to Add a PP Version........................................................................220 How to Set a PP Version.........................................................................221 How to Force Load of a PP Version ......................................................221 How to Change a PP Version.................................................................221 Clock Management System .................................................................222 Timer Management ..................................................................................222 Time Management....................................................................................224 Exceptions and Meanings .......................................................................225 Tone Management System ..................................................................226 System Overview......................................................................................226 Select a Tone File .....................................................................................227 Tone Play...................................................................................................228 Tone Record..............................................................................................229
Page III of IV
16.5 16.6 16.7 16.8 16.9 16.10 16.11 17 17.1 17.2 17.2.1 17.2.2 17.2.3 17.2.4 17.2.5
Tone Editing ..............................................................................................230 Tone Load..................................................................................................235 How to Make a Tone File ........................................................................238 How to Load 64M Tone File to the Foreground ...................................239 How to Load 4M Tone File to the Foreground .....................................240 Description of Loading Status .................................................................241 Description of Error Messages ...............................................................241 Signaling Trace System........................................................................243 System Overview......................................................................................243 Basic operations .......................................................................................247 Interfaces ...................................................................................................247 Signaling Trace .........................................................................................249 View Message Details, Database Data and Tracing information .....266 Database Tool...........................................................................................268 Cancel Tracing, Clear Record, Windows Management and Help ....269
Page IV of IV
User Tracing System

The user tracing is a tracing tool provided for PLMN administrators, which is used to observe the actions of some specific users of PLMN when some events happen (for example, location updating, call services, supplementary services, etc) and locate the cell of suspicious users or equipment? Users are identified with IMSI or MSISDN, and the equipment is identified with IMEI. This function not only provides a means of tracing for PLMN administrators, but also serves as a tool for convenient commissioning, testing and maintenance.
6.1
6.1.1
System Overview
Main Functions With the tracing function, the PLMN administrators can observe and trace users in the following conditions. 1. In such cases when a subscriber keeps complaining about a service or its performance, this subscriber may be traced. Observe the operations of this subscriber and the operations of its equipment in the network to see if anything goes wrong. 2. Tracing at request of the police The police may require a suspect to be traced in order to find out his location and activities. 3. Tracing illegal equipment based on IMEI at the request of subscribers. The user tracing system may provide the following functions: 1. Tracing subscribers of local mobile telecommunication network. 2. Tracing the subscribers outside the local mobile telecommunications network, who roam to the local network. 3. Display the current tracing information on a real-time basis; 4. Querying the historical tracing information. 5. Query the current location of subscribers without activating the tracing function.
Page 1 of 273
6. Display visually on a map the locations of the subscribers being traced. 7. Display visually on a map the locations of the equipment being traced 8. Locate the cell of subscriber/equipment being traced. The logical relationship between the user tracing system and the entire switching system is shown in Fig. 6-1.
Human-machine command
MP NT Server User tracing process User tracing client
Foreground
Background
Fig. 6-1 Logical Relationship During User Tracing 6.1.2 Interfaces
Click the user tracing icon on the ZXG10 operation and maintenance system floating menu, and you will see a pop-up interface as shown in Fig. 6-2.
Fig. 6-2 ZXG10-MSS User Tracing System

Page 2 of 273
The interface of ZXG10-MSS user tracing system consists of menu bar, tool bar and status bar. On the tool bar are some common command icons of ZXG10-MSS/VLR user tracing system and a rotating globe indicating the running status of the system, as shown in Fig. 6-3. Click the icons on the tool bar to execute corresponding commands.
Fig. 6-3 Tool Bar On the interface as shown in Fig. 6-3, all other icons except the activate trace icon are disabled, indicating that no tracing event is activated currently. If user tracing or equipment tracing is activated, the globe on the right will be rotating, and the corresponding buttons Deactivate user trace, User tracing map, Deactivate equipment tracing, and Equipment tracing map will be enabled. The status bar is located on the bottom of the main interface of ZXG10MSS user tracing system, as shown in Fig. 6-4.
Fig. 6-4 Status Bar In the middle of the status bar is the local terminal number, and on the right hand of the status bar are two indicators. The left indicator shows the status of the communications between the Server and the foreground, and the right one shows the status of the communications between the Server and the local terminal. The indicator showing green indicates proper communication; the indicator showing red indicates the communication is totally interrupted; the indicator showing gray means the communication is partly interrupted and partly normal (only applicable to multiple modules). 6.1.3 Number Types The number is of the following types: 1. MSISDN number MSISDN is the number dialed to call a subscriber. For GSM system in China, the TDMA independent numbering scheme is employed:
Page 3 of 273
CC+NDC+SN SN=PQ (R) + ABCD CC is the country code. For China, it is 86; NDC is the mobile network access code, identifying different mobile systems. At present, the access code for China Telecoms mobile network ranges from 135 to 139, while the access code for China Unicom includes 130 and 131. PQ (R), namely, the H0 H1H2 H3, is designed to identify the HLR offices in the mobile system. These switching offices may be in different areas; ABCD refers to the subscriber number, assigned by different localities. 2. IMSI number The IMSI number is used to uniquely identify the international universal number of a mobile subscriber, which is composed of MCC+MNC+MSIN. MCC stands for the country code. For China, it is 460; MNC refers to the network number. For the telecom network, it is 00; for Chi na Unicom network, it is 01; MSIN is the subscriber ID, which consists of H1H2 H39XXXXXX, in which the H1 H2H3 indicates the place where a subscriber opens his account. H1 H2 is allocated to each province by the post and telecom departments, while each province may have more than one H1H2. For example, Jiangsu has 51 and 52. H3 is assigned by each province/city according to actual conditions. The IMSI of a subscriber is written into the SIM card of the subscriber using special equipment or software, uniquely identifying a subscriber. In addition, the IMSI stores information relating to this subscriber in the network (HLR). 3. IMEI number IMEI is the equipment identifier number, uniquely identifying an MS equipment, which is composed of 15 decimal numbers. The first 6 digits are assigned by the European type authentication center. The IMEI mainly serves to safeguard that the MS equipment used in the system are legal. 4. Location area ID (LAI):
Page 4 of 273
Each MSC/VLR service area is divided into several location areas. The mobile station can freely move in a single location area without updating the location information contained in the MSC/VLR that controls the location area. The location area ID contains MCC+MNC+LAC. MCC is the mobile subscriber country code, which is identical to the first three digits of IMSI. MNC is the mobile network code, which is the same as the MNC in IMSI. LAC is the location area code, which is a 2-byte BCD code. A maximum of 65536 location areas can be defined in a GSM PLMN network. In the ZXG1-MSS/VLR user tracing subsystem, LAI is represented by a 9digit decimal number. 5. Global cell identifier (GCI) One location area is divided into several cells. The cell number comprises a cell ID (CI) following a location area ID (LAI). CI is a 2-byte BCD code, which is decided by each MSC.
6.2
Basic Operations
ZXG10-MSS/VLR user tracing system provides the following functions: 1. Real-time tracing: activating the tracing of a specific subscriber or equipment. 2. Display Tracing map: allowing operators to observe visually.. 3. Query history information: querying the history records of a traced subscriber. 4. Query subscriber location: finding out the current location of the subscriber. 5. Maintenance tool: providing a set of maintenance and management tools, such as background setting, font selection, windows management, etc.
Page 5 of 273
6.2.1
Real-time Tracing The user tracing subsystem may either trace a subscriber based on his MSISDN or IMSI number, or trace equipment based on its IMEI number. The traced result can be displa yed in real time. Detailed operations are described as follows: 1. Select a module on the interface shown in Fig. 6-2, and then select the Trace ? Activate trace command or click the Activate trace icon on the tool bar, to pop up an interface shown in Fig. 6-5.
Fig. 6-5 Tracing Activation 2. Enter the MSISDN or IMSI number of the subscriber to be traced on the interface shown in Fig. 6-5. 3. Choose an option from the MSC active event type box, and the meaning of each item is as follows: 1) All: generating tracing records for all services of the current subscriber. 2) Location update, IMSI Attach/detach: generating tracing records only in the event of these three services. 3) Calling Service, SMS, and SS: generating tracing records only in the event of these three services. 4. Select MSC record type and BSS record type in the selection box on the right of the interface.
Page 6 of 273
5. For the Save trace record to database check box, if checked, user tracing records will be saved to the database and you may choose Query history information for later querying; when unchecked, user tracing records will not be saved to the database and you are not allowed to query this trace later. 6. Click the <OK> button. If you choose to enter IMSI or MSISDN, this subscriber will be traced, and an interface will pop up, as shown in Fig. 6-6.
Fig. 6-6 Tracing Information Display On the upper part of the interface are the check boxes for service type. If one service is not checked, the tracing information about this service, even if applicable, will not be displayed. 1)After clicking the <OK> button on the interface as shown in Fig. 6-5, if only a message pops up as shown in Fig. 6-7, it indicates that the MSISDN of the user you entered does not exist.
Fig. 6-7 Error Hint (1) 2)If after clicking the <OK> button on the interface shown in Fig. 6-5, not only the message as shown in Fig. 6-7 but also another message as
Page 7 of 273
shown in Fig. 6-8 pop up, this indicates this subscriber does exist, but not in the current VLR.
Fig. 6-8 Error Hint (2) There are two possibilities: lThis subscriber is an outside subscriber, who does not roam into the local area lThis subscriber is a local subscriber, who has roamed to other areas. In both cases, the labels are already in the VLR. As soon as this subscriber appears in the area under the current VLR, he will be traced immediately. 3) Click the <OK> button on the interface as shown in Fig. 6-5. If a pop-up message as shown in Fig. 6-9 is followed by another pop-up message as shown in Fig. 6-10, it indicates that the link between the foreground and the server, or the link between the operation console and the server, or the link between HLR and VLR might be interrupted. In this case, check the physical link first. If the physical link is not disconnected, the failure might be caused by the transitory abnormality during message transmission. Have another try, please.
Fig. 6-9 Hint Message
Fig. 6-10 Error Message (3)

Page 8 of 273
4) The user tracing system can trace a maximum number of 10 subscribers or devices at the same time. When the tracing of more than ten subscribers or devices is activated, click the <OK> button on the interface as shown in Fig. 6-5, and an interface as shown in Fig. 6-11 will pop up.
Fig. 6-11 Error Message (4) 7. To stop tracing a subscriber, select Trace ? Deactivate user trace, and a pop-up interface as shown in Fig. 6-12 will appear.
Fig. 6-12 Deactivate User Trace Select the desired user, and click the <OK> button to cancel the tracing of this user. Or you may deactivate the tracing of a subscriber by closing the box that displays information about the tracing of this subscriber. In addition to displaying the tracing information activated by MSC, you may select trace ? BSS activated tracing information to display the BSS activated tracing information.
Page 9 of 273
6.2.2
Tracing Map To learn the geographic location of a subscriber being traced more directly, activate the tracing map. ZXG10-MSS user tracing sub-system provides real and clear tracing map, The map allows you to mark each location area or cell. When a subscriber being traced roams into a location area, the corresponding mark will flash. This helps find out the precise location of this subscriber. The initial tracing map has no mark at all. Therefore, before observing the tracing map, the map must be initialized. Briefly, the initialization process is intended to mark each location (location area number or cell number). Below is the specific procedure of tracing map initialization: Choose the Tools ? Initialize user trace picture command from the menu as shown in Fig. 6-2, a pop-up menu will appear, as shown in Fig. 6-13.
Fig. 6-13 Initialize User Trace Picture Fig. 6-13 shows the map of Beijing. In practice, you may configure a detailed local map according to actual requirements, so as to trace subscribers accurately within a certain range. For example, supposing that the location area code of the China National Park is defined as 46001211, we now need to mark it on the map. Below is the operation procedure: first, enter 460001211 in the Location box. To locate the cell, please enter the
Page 10 of 273
cell code; then, click on the button to change it into ; finally, click on the locaiton that represents China National Partk, as shown in Fig. 6-14.
Fig. 6-14 Initialize a Map If the cursor stays on the mark for about 1s, the location area code will appear by the side of the mark, as shown in Fig. 6-15.
Page 11 of 273
Fig. 6-15 Display Location Area Number Thus, the location area number 460001211 is initialized. Other locations on the map can be initialized in the same way. After the location area initialization, click the <Close> button and save the location area information, then the initialization process of the tracing map is completed. The Display trace map button in Fig. 6-13 and 6-14 cannot be used unless the traced subscriber already exists. First, activate the tracing box for the traced subscriber, and then select the Tool ? Display user trace map on the interface shown in Fig. 6-2 or click the Display user tracing map icon on the tool bar, to see a pop-up tracing map of the traced subscriber as shown in Fig. 6-16. Only the roaming location of one subscriber can be displayed on the user tracing map.
Fig. 6-16 Tracing Map with Initialization Completed

Page 12 of 273
On this map, the icon indicates the location area specified during the initialization. When a subscriber roams to this location area, for example, the China National Park, this icon will flash, as shown in Fig. 6-17.
Fig. 6-17 Display the Location of the Traced User on the Tracing Map 6.2.3 Query History Information All users who have chosen the option Save tracing record data to the database are allowed to query the history information. The database stores the subscriber tracing information within one month. To obtain the history information of a subscriber, query the user information traced most recently. The detailed operations are as follows: Select the Query ? Query MSC/VLR history information command from the menu on the interface as shown in Fig. 6-2, and a pop-up interface will appear, as shown in Fig. 6-18.
Fig. 6-18 Query MSC/VLR user Tracing History Information

Page 13 of 273
First, enter the IMSI of the user to be queried or the IMEI of the equipment to be queried, or just click the pull-down list and select them from the list. The list specifies all IMSIs or equipment IMEIs contained in database. Then, select the time period for a query and the record to be queried. Nine options are available: all, MOC, MTC, supplementary service, location update, IMSI attach, IMSI detach, sending short message, and receiving short message. Click the <OK> button to display the user tracing history information to be queried in the list box, as shown in Fig. 6-19.
Fig. 6-19 Display User Tracing History Information Select a record, and double -click it to pop up an interface as shown in Fig. 6-20, which displays the details about the selected records.
Page 14 of 273
Fig. 6-20 Details of User Information By clicking the <First>, <Next>, or <Last> button, view the corresponding records. Click the <Close> button to return to the interface as shown in Fig. 6-19 6.2.4 Query the Location Information The location information query function of ZXG10-MSS/VCR user tracing system allows you to check whether a specific user is in the current MSC/VLR. If so, the specific location area will be displayed. Click the Query ? Query user location in Fig. 6-2, and an interface as shown in Fig. 6-21 will pop up.
Fig. 6-21 Query User Location Enter the MSISDN number or IMSI number in this interface. If the number of this user was entered not long ago, click the pull-down list and select it in the list. After entering the number, click the <OK> button. If this user is recorded in the current VLR, an interface shown in Fig. 6-22 will pop up.
Page 15 of 273
Fig. 6-22 Location Area Information If this user is not recorded in the MSC/VLR office, an interface shown in Fig. 6-23 will pop up .
Fig. 6-23 Hint Message 6.2.5 Maintenance Tools ZXG10-MSS/VLR user tracing system provides a set of maintenance and management tools. 1. Select background color and font The user tracing system provides the tools similar to those in Window NT in order for you to set the background color, and the font size, style and color. Select Option ? Font or Option ? Color shown in Fig. 6-2, to set the font and background color. 2. Arrange windows Since multiple subscribers can be traced at the same time, the system provides a management tool for the opened windows: 1) Display the opened windows
Page 16 of 273
Select Windows ? Cascade or Windows ? Tile from the menu shown in Fig. 6-2, to display the opened windows in the corresponding mode. 2) Minimize windows Select Windows ? Minimize all on the interface shown in Fig. 6-2, to minimize all of the opened windows. 3) Arrange icons Select Windows ? Arrange icons on the interface shown in Fig. 6-2, to arrange all of the minimized windows.
Page 17 of 273
7
7.1
7.1.1
Service Observation System

System Overview
System Architecture The service observation system is a tool for system debugging, maintenance and observation. It is characterized by simple operations, accurate and reliable information provision, and rich contents. Service observation involves both the foreground and the background. The foreground and the background communicate with each other through the foreground-background communication supporting platform of ZXG10MSS/VLR. The foreground MP and the background are connected through Ethernet, as shown in Fig. 7-1.
MP
MP
MP
Ethernet
Service observation server
Service observation workbench
Fig. 7-1 Architecture of the Service Observation System 7.1.2 System Functions Service observation achieves the following functions: 1. Statistics observation Dynamically trace the utilization of MSC and VLR data area, and collect statistics of the occupation of data areas. 2. State observation
Page 18 of 273
Observe the working status of MSC/VLR data areas in real time, to find out which data areas are occupied. 3. Call loss observation When MSC/VLR services fail, this function allows you to observe the causes of service failure in a real time manner and make a judgment accordingly; meantime, the service failure data can be saved in the database list for later analysis. 4. User observation Observe the data in a specified data area according to subscriber ID or data area i ndex. 5. Base station management 1) Query subscriber level information; 2) Browse base station resource; 3) MSC resetting; 4) Query IMSI based on subscribers MSISDN 5) If a subscriber has trouble in making a call, the operators with the authority are allowed to delete the record of this subscriber in the VLR, so that the subscriber can re-register the location. 6) View the user record removed from the VLR; 7) Release the falsely occupied data area 6.Inter-office service observation This includes call loss data area observation, viewing auxiliary call structures, viewing false occupation and PP memory management. 7. No.7 observation Monitor the foreground signaling link and signaling board.
Page 19 of 273
7.2
7.2.1
Basic Operations
Introduction to the Interfaces Click the Service Observation icon on the floating menu in the ZXG10-MSC/VLR Operation and Maintenance System to pop up an interface as shown in Fig. 7-2.
Fig. 7-2 ZXG10-MSS Service Observation System The interface of ZXG10-MSS service observation system consists of the menu bar, tool bar, windows and status bar. The common command icons of ZXG10-MSS/VLR service observation system are shown on the tool bar, as shown in Fig. 7-3. On the right end of the tool bar, there is a rotating globe, indicating the system is running.
Fig. 7-3 Tool Bar The status bar is at the bottom of the ZXG10-MSS service observation interface, as shown in Fig. 7-4. In the middle of the status bar is the local terminal number, while the right indicator shows the status of the
Page 20 of 273
communications between the Server and the foreground. The indicator showing green indicates proper communication; the indicator showing gray means the communication is partly interrupted and partly normal (only applicable to multiple modules) the indicator showing red indicates the communication is totally interrupted;
Fig. 7-4 Status Bar Select Tool ? exit shown in Fig. 7-2 to see a pop-up menu shown in Fig. 7-5. Click the <OK> button to exit the service observation system.
Fig. 7-5 Prompt for Exiting the System 7.2.2 Statistics Observation The statistics observation function is designed to dynamically trace the utilization of MSC/VLR data area and the occupation of the statistical data area. It mainly includes MSC statistics observation and VLR statistics observation. Select Observation ? Statistics on the interface shown in Fig. 7-2, or click the Statistics button on the tool bar to display a pop-up interface as shown in Fig. 7-6.
Page 21 of 273
Fig. 7-6 Statistics Observation Interface (MSC Statistics Observation) 7.2.2.1 MSC Service Observation The MSC service observation tab is shown in Fig. 7-6. From this interface, the utilization o each MSC data areas can be observed in a real time manner, including the total number of data areas, the number of data areas in use and the utilization rate of data areas. After selecting the necessary parameter in the Period pull-down list in Fig. 7-6, as shown in Fig. 7-7, click the Register button, to observe the selected MM, CC, MAP process data areas, as shown in Fig. 7-8.
Page 22 of 273
Fig. 7-7 Set Observation Intervals
Fig. 7-8 MSC statistics Observation The main body of this interface includes MM observation box, CC observation box and MAP observation box. The X-axis of the observation box means the observation time, and the Y-axis shows the percentage of total numbers of the data areas occupied. In the observation state, the Register button will be disabled while the Terminate button will become active. The observation box in the left pane shown in Fig. 7-8 displays different MSC data areas, total number of data areas for different modules, current number of data areas in use and the utilization rate of data area. The right pane shows the statistics curve indicating the use of MSC data areas within different observation periods. Operators can select the statistics chart of each MSC data area in the check boxes above the statistics curve. 7.2.2.2 VLR Service Observation Select the VLR tab as shown in Fig. 7-9.
Page 23 of 273
Fig. 7-9 VLR Service Observation Similar to MSC service observation, this page allows you to observe the utilization of VLR data areas in a real time manner, including the total number of data areas, the number of used data areas and the utilization rate of data areas. The Period pull-down box is shown in Fig. 7-10.
Page 24 of 273
Fig. 7-10 Set Observation Intervals After setting the required parameters on the interface shown in Fig. 7-9, click the Register button to observe the selected PDB, Remark and DID process data areas, as shown Fig. 7-11.
Fig. 7-11 VLR Service Observation Example Diagram The main body of the interface consists of PDB observation box, Remark observation box and DID observation box. The X-axis of the observation
Page 25 of 273
box means the observation time, and the Y-axis shows the percentage of total numbers of the data areas occupied. In the observation state, the Register button will be disabled while the Terminate button will become active The observation box in the left pane had shown in Fig. 7-11 displays different MSC data areas, total number of data areas for different modules, current number of data areas in use and the utilization rate of data area. The right pane shows the statistics curve indicating the use of MSC data areas within different observation periods.. Operators can select the statistics chart of each MSC data area in the check boxes above the statistics curve 7.2.3 State Observation The Status observation function is used to observe the working status of current MSC/VLR data area, which includes MSC data area status observation and VLR data area status observation. Select Observation ? Status observation on the interface shown in Fig. 7-2, or click the status button to display a pop-up interface shown in Fig. 7-12.
Page 26 of 273
Fig. 7-12 Data area Status Observation (MSC Status Observation) 7.2.3.1 Observe the Status of MSC Data Area The MSC service observation tab is shown in Fig. 7-12. This page allows operators to observe the current status of MSC data area occupation and help them to judge whether MSC data area is falsely occupied, thus obtaining the index of the falsely occupied MSC data area. Select the number of the MSC module to be observed from the Module setup pull-down menu, and then select the data area(s) to be observed from the check boxes. After the setting, click the Start button to observe the selected MM, MAP, CC, SSF, SRF and CCF data area. The results are shown in Fig. 7-13.
Fig. 7-13 MSC Data Area Status Observation If you choose to observe CAMEL service, you will be able to the data areas CC, SSF, SRF and CCF; if you do not select CAMEL service, you may observe the data areas MM, MAP and CC. Select an observation result from the interface shown in Fig. 7-13, and right click it to pop up the the observation result. menu. Click this menu to delete
Page 27 of 273
7.2.3.2
Observe VLR Data Area Status Select the VLR tab in Fig. 7-12, as shown in Fig. 7-14.
Fig. 7-14 VLR Status Observation Similar to the MSC service observation tab, this interface allows operators to see the current occupation of VLR MAP_PDB process data area and helps them to judge whether MAP_PDB data area is falsely occupied, thus obtaining the index of the falsely occupied MAP_PDB data area. Select the module number to be observed from the Module pull-down list. Click the Start button to observe this module, and the result of this observation is shown as in Fig. 7-15.
Page 28 of 273
Fig. 7-15 VLR Data Area Status Observation Example Diagram As shown in Fig. 7-15, the VLR MAP_PDB data area currently used by module 2 is 0; however, in actual applications, the MAP_PDB data area may not necessarily be 0. Thus, you m ay judge if there exists a falsely occupied MAP process data area based on actual conditions. If such an area does exist, you should analyze the cause and release the data area according to Section 14.2.6. Select an observation result from the interface shown in Fig. 7-15, and right click it to pop up the the observation result. 7.2.4 Failure observation When MSC/VLR services fail, Failure observation allows you to observe the causes of service failure in a real time manner and make a judgment accordingly. In addition, the service failure data can be saved in the database list for later analysis. The Failure observation function mainly includes MSC service failure observation and VLR service failure observation. menu. Click this menu to delete
Page 29 of 273
Select Observation ? Failure on the interface shown in Fig. 7-2, or click the Failure button to display a pop-up interface shown in Fig. 7-16.
Fig. 7-16 Service Failure Observation (MSC Service Observation) 7.2.4.1 Observe MSC Service Failure The MSC service observation tab is shown in Fig. 7-16. This page allows you to observe the service failure time, the failed MSC module number, the service failure origin and index number, and the failure cause. Set the parameter of MSC service failure observation on the right side of the interface, namely, the module number and the source of the failure. By selecting the different tabs of MM, CC, MAP, SSF, SRF, GMSC, and CCF from the module setup box, set the module number observed in each data area. By selecting Filter, you are allowed to set the filter conditions for MSC failure observation. By clicking on the highlighted observation records (module number or failure origin), you may specify the filter condition for the records to be observed in the Filter condition pull-down list: if you choose to filter by module number or failure origin, as shown in Fig. 7-17, only the failure records that meet the filtering condition will be displayed (TUP as the origin).
Page 30 of 273
Fig. 7-17 Set Filtering Conditions for MSC Service Failure Observation After setting the parameters for MSC failure observation, click the <Start> button to observe the service failure. When the selected module has a service failure, the MSC service observation page can help get the failure data on a real time basis. Click the Terminate button to stop observing service failures. In the observation state, the <Start> button will be disabled, and the <Terminate> button will become active. If the loaded historical data are displayed, the <History> button will be in disabled. Meanings of some buttons in this interface are defined as follows: 1. 2. 3. 4. : Selecting the 1st record. : Selecting the previous record. : Selecting the next record. : Selecting the last record.
Page 31 of 273
Double click the failure record, and the details on this record will pop up, as shown in Fig. 7-18.
Fig. 7-18 MSC Service Failure Record Right-click the interface shown in Fig. 7-16 and select the Statistic option. The pop-up shortcut menu is shown in Fig. 7-19. By selecting the Delete option, the pop-up menu will be as shown in Fig. 7-20.
Fig. 7-19 Statistics Menu
Fig. 7-20 Deletion Menu
Page 32 of 273
After selecting the commands under the Stat option shown in Fig. 7-19, the system will take statistics of the failure records in the selected manner. For example, if you select the Statistics ? By Current Module number, statistical results will be shown in Fig. 7-21.
Fig. 7-21 Statistics by the Current Module Number On the interface shown in 7-16, click the Backup button to pop up the interface, as shown i n Fig. 7-22.
Fig. 7-22 Save the Service Failure Record Files After entering the file name, click the Save button to save the MSC service failure record as this file name. On the interface shown in Fig. 7-16, click the History button and the popup interface will be shown in Fig. 7-23. After selecting the MSC failure record file, click the Open button, to open the failure record previously back upped.
Page 33 of 273
Fig. 7-23 Open MSC Failure Record File 7.2.4.2 Observe VLR Service Failure Select the VLR service observation tab in Fig. 7-16, as shown in Fig. 724.
Fig. 7-24 VLR Service Observation This interface allows you to observe the time, service type, record number and failure causes of VLR service failures. The operations of VLR service observation tab are similar to those of MSC service observation.
Page 34 of 273
7.2.5
User Observation User observation refers to the observation of the data contained in a specified data area based on user ID or data area indexes. In general, the operation and maintenance personnel use the user observation function mainly to dynamically analyze the contents of this data area when this data area is occupied, or to observe the falsely seized data area, and analyze the causes of such false occupation. Select Observation ? User/observation of specific data area on the interface shown in Fig. 7-2, or click the Data button to see a pop-up interface shown in Fig. 7-25.
Fig. 7-25 User Data Area Observation (MSC Service Observation) 7.2.5.1 MSC Service Observation The MSC service observation tab is shown in Fig. 7-25 in order for you to observe the contents of MSC data areas. The icons of MSC data area observation tools are shown as in Fig. 7-26.
Page 35 of 273
Fig. 7-26 MS Data Area Observation Icons The Save icon is used to save the data of specific MSC data area. Click the Save button to pop up a menu shown in Fig. 7-27.
Fig. 7-27 Save Shortcut Menu In general, the data in MSC service observation are used for observation and debugging. Therefore, you may choose either to save the specific data area of a process (MM or CC), or save the entire data area being observed. The Index button shown in Fig. 7-25 is used for searching the index for MSC data area. There are two ways of searching the MSC data areas: search using the Index of a data area or using the MSC user IDs. Click the Index button to pop up a menu shown in Fig. 7-28. The Subscriber option allows you to switch to a search by user ID.
Fig. 7-28 Index Pull-Down Menu The Read data button in Fig. 7-25 is used to obtain the data contained in MSC data area. There are two ways of obtaining the data: from MP and from the saved files. Click the Read Data button to pop up a menu shown in Fig. 7-29.
Fig. 7-29 Obtaining Data from MSC Data Area
Page 36 of 273
The Detailed data button shown in Fig. 7-25 is used to view the contents of obtained MSC data area (MM, CC, MAP or HO). Click the Detailed Data button to pop up a menu shown in Fig. 7-30.
Fig. 7-30 Detailed Data Pull-Down Menu Right click the display area shown in Fig. 7-25, and the
.menu will pop up. Click this menu to delete the results of current query from the display area. As stated above, there are two ways of searching MSC data area: using the index of the data area, and using the MSC user IDs. Now we will introduce them in details. 1. Search the MSC data area by Index On the interface shown in 7-25, click the Index button and an shortcut menu will pop up, as shown in Fig. 7-28. Select the Index option, and the INDEX parameter setup identifier will appear on the right pane of the interface shown in Fig. 7-25. See Fig. 7-31.
Page 37 of 273
Fig. 7-31 INDEX Parameter Setting Select the desired data area, the MSC module number and the Index on the interface, and click the Read Data button, and then select the From MP option on the pop-up menu shown in Fig. 7-29 (searching by INDEX allows you to read data from MP only instead of the file. Thus, the data contained in the data area corresponding to this INDEX will be displayed in the display pane, as shown in Fig. 7-32.
Fig. 7-32 MSC Data Area Obtained by INDEX Select the desired data area (for instance, MM data ) on the interface shown in Fig. 7-30, and a box for data structure explanation of this data area will appear, as shown in Fig. 7-33.
Page 38 of 273
Fig. 7-33 Data Structure Explanation Box You may view the details of this data area on this interface. Select the data structure from the tree, and the data type and contents corresponding to this data structure will be displayed in the display pane on the right side of the interface. Click the Expand button to unfold this data structure tree; click the Collapse button to fold the tree; click the Exit button to quit this interface. The data area contents obtained by INDEX cannot be saved using the interface shown in Fig. 7-27. 2. Search MSC data area by user ID On the interface shown in 7-25, click the Index button to pop up the interface, as shown in Fig. 7-28. Select the Subscriber option from this pop-up menu, and the Parameter setup box will be shown on the right side of Fig. 7-25. See Fig. 7-34.
Page 39 of 273
Fig. 7-34 User Parameter Setup On this interface, set the MSC data area to be searched, and select IMSI as the subscriber type, and then enter the subscriber ID. On the interface shown in Fig. 7-29, select From MP (this data area must be in use during the operation) or From file, to obtain the data in the MSC data area of this subscriber. If the From MP is selected, you are allowed to select the data area shown on the interface in Fig. 7-30, and an interface shown in Fig. 7-33 will pop up. To save the data read from MP, use the saving interface shown in Fig. 727 to save this data area. If the from file option is selected, you will see a pop-up interface as shown in Fig. 7-35.
Fig. 7-35 Parameter Setting For Reading Data From Files

Page 40 of 273
Select the type of the data area to be viewed, and click the Display button to read the contents of this type of data area (MM or MAP) from the file, and the data structure explanation box of the data area corresponding to the current record number will pop up, as shown in Fig. 7-33. Click the <Delete> button to delete the records in this data area. Click the Exit button to return to the previous interface. 7.2.5.2 VLR Service Observation Select the VLR service observation tab in Fig. 7-25, as shown in Fig. 736.
Fig. 7-36 VLR Service Observation This interface allows you to observe the contents of VLR data areas, and search data in a way similar to the MSC data area; however, there is only one way to search VLR data areas, which is, searchi ng by INDEX. The Read data button shown in Fig. 7-36 allows you to get data contained in the VLR data areas. The VLR data area data is only obtainable from MP.
Page 41 of 273
The Detailed data button shown in Fig. 7-36 allows you to view the obtained contents of VLR data areas. Click this button to obtain VLRMAP data. Right click on the display area shown in Fig. 7-36, the menu will pop up. This option allows you to delete the results of current query from the display area. The method for searching VLR data area is similar to the search by INDEX in MSC data areas. Set the INDEX parameter setup identifier shown in Fig. 7-36. After setting the desired VLR module number and the data area index number, click the Read Data button, and a pop-up menu will appear, as shown in Fig. 7-29. Select the from MP option from the pop-up menu. If this data area is occupied, the data contained in the data area process corresponding to this index will appear in the display box, as shown in Fig. 7-36. Select the desired data area from the menu shown in Fig. 7-30, and the data structure explanation box for this data area will pop up, as shown in Fig. 7-33. Refer to section 14.2.5.1 for operations. 7.2.6 Base Station Management The base station management includes base station management, numbering management and the clearing of falsely occupied data areas. On the interface shown in Fig. 7-2, select Observation ? Numbering management/base station management/clear fault occupation or click the Number icon, and a pop-up interface will appear, as shown in Fig. 7-37.
Page 42 of 273
Fig. 7-37 Base Station Management And Numbering Management (Query Subscriber Classmark Information) 7.2.6.1 Query Subscriber Classmark Information The Classmark Information subtab under the MSC tab is shown in Fig. 7-37. You may set the parameters for subscriber classmark information on the right side of the interface. Enter a subscriber IMSI ID and select the corresponding module settings. Click the View button to display the classmark information, shown in the display box in Fig. 7-37. The classmark information cannot be queried unless this subscriber is in conversation. 7.2.6.2 Base Station Resource Request Select the BS resource requirement tab on the MSC tab, as shown Fig. 7-38.
Page 43 of 273
Fig. 7-38 Base Station Resource Request The purpose of requesting resource from BSC is to return the following messages: 1. The amount of idle radio resources in BSS, which can be used as the traffic channel. 2. Total amount of radio resource. The detailed operations are as follows: Enter the last four digits of the location area code into the LAI box, and enter the last four digits of the cell number into the CI box. The four resource indication modes are: 1. Expected auto indication BSS immediately sends a Resource Indication message without any resource information to MSC as an acknowledgement of resource request. When the corresponding cell meets the conditions set by OMC, BSS will automatically send a Resource indication message at the specified time period specified in the periodical information unit for the resource request message, indicating the cell resource information.
Page 44 of 273
2. Expected single indication BSS should return a single Resource indication message with some resource information without delay. If the Resource request message does not contain the extended resource indicator information unit, BSS will stop transmitting any resource information of this cell until it receives a new Resource request message with an expanded resource indication unit to MSC. Then BSS will follow the requirement in the subsequence field in the message. 3. Expected circle indication BSS should return a Resource indication message with some resource information, and then keep sending the Resource indication message at the pre-defined cyc le. The time cycle is an integer multiply of 100ms. 4. No resource information Indication BSS should return a single Resource indication message without any resource information, which serves as the acknowledgement of Resource request . Subsequently, BSS stops sending any resource information related to this cell to MSC until it receives a new Resource request or Reset message. In the resource request parameter setting box, there are two options Resource expanded flag and Successive Mode. Their meanings are briefly described in the explanation of Expected single indication , These two modes may be selected depending on actual conditions. After setting the parameters, click the <OK> button to send the resource request to MSC. Then, the MSC will send the resource request to the BSC, and the BSC will return the desired information, as shown in Fig. 7-39.
Page 45 of 273
Fig. 7-39 Example of Base Station Resource Request 7.2.6.3 MSC Reset Select the Reset BSC tab on the MSC tab, as shown in Fig. 7-40.
Fig. 7-40 Reset BSC

Page 46 of 273
MSC will not send the Reset message to BSC unless a failure has occurred and all the reference information for processing gets lost. After receiving the message, the BSC will release the affected calls, and delete the affected reference information. On the interface shown in Fig. 7-40, select the desired module and base station, and click the Reset button to see a pop-up message shown in Fig. 7-41.
Fig. 7-41 Hint for MSC Reset To view BSC information, click the BSC information button, as shown in Fig. 7-42.
Fig. 7-42 View BSC Information
Page 47 of 273
7.2.6.4
Clear Falsely Occupied MSC Data Areas Select the Clear fault occupation subtab under the MSC tab in Fig. 7-37, as shown in Fig. 7-43.
Fig. 7-43 Clear Fault Occupation When the switching goes wrong, this might result from the failure to release relevant data upon completion of a call. This is called falsely occupied data area. A large number of falsely occupied data areas would reduce the resources available to the switching system, thus worsening the system performance to the detriment of system operations. The ZXG10-MSS/VLR service observation system enables you to release data areas manually. On the right side of the interface, clear the falsely occupied parameters for MSC data areas. Select the MM, CC and MAP data area to be cleared, as well as the corresponding module numbers and INDEXes, click the <OK> button and you can see a pop-up menu as shown in Fig. 744.
Page 48 of 273
Fig. 7-44 Alert Box for Clearing Fault Occupation Click the <OK> button to delete the corresponding data area. You may set the operation authority for Release fault occupation in the Authority management system. 7.2.6.5 Query IMSI Select Number management ? query IMSI tab on the VLR tab in Fig. 7-37, as shown in Fig. 7-45.
Fig. 7-45 Query IMSI Query subscribers IMSI number in VLR based on the MSISDN number and this is one of the numbering management functions. If the subscriber already exists in the VLR DB, enter his module number and MSISDN, and click the <OK> button to display the IMSI of this subscriber in the display box.
Page 49 of 273
7.2.6.6
Delete VLR Subscribers Select Number management ? Delete sub subtab under the VLR tab in the interface shown in Fig. 7-37, as shown in Fig. 7-46.
Fig. 7-46 Delete VLR Subscribers The subscribers are deleted only in some specific conditions. If a subscriber cannot get through a call for a long time, the data of this subscriber will be deleted from VLR, so that this subscriber will have to reregister with VLR. Enter the module number, and select the desired number type (IMSI or MSISDN) of the subscriber, and then enter the corresponding number. The records of this subscriber in VLR will be deleted by clicking the <OK> button. 7.2.6.7 Clear Falsely Occupied VLR data area Select the Clear fault occupation subtab on the MSC tab in the interface shown in Fig. 7-37, as shown Fig. 7-47.
Page 50 of 273
Fig. 7-47 Clear the Falsely Occupied VLR Data Area On the right side of the interface, you may make the setting to clear the falsely occupied parameters for the VLR data areas. Select the module number and enter the MAP index number, click the <OK> button and you will see a pop-up menu as shown in Fig. 7-48.
Fig. 7-48 Releasing Falsely Occupied VLR Data Area Similar to MSC operations, only the authorized operators are allowed to execute the Release falsely occupied data areas operation with their authority assigned in the Authority management system. 7.2.7 Inter-office Observation The inter-office observation serves to achieve the following functions: 1. Dynamically trace foreground call loss records;
Page 51 of 273
2. View the auxiliary structure data of calls in real time. 3. View/release falsely occupied data area 4. View/modify PP memory data area in a real time manner The inter-office observation is to search the data area that meets the observation conditions. The dynamical tracing objects include associated channel call data areas, common channel TUP call data areas and common channel ISUP data areas. Select Observation ? Inter-office service observation on the interface shown in Fig. 7-2, or click the Inter-office icon on the tool bar and a popup interface will appear, as shown in Fig. 7-49.
Fig. 7-49 Inter-Office Service Observation (Call Loss Data Area Observation) 7.2.7.1 Observe Call Loss Data Area Failure Observation tab is shown in Fig. 7-49. This interface allows you to trace the foreground call loss records dynamically by carrying out the following operations:
Page 52 of 273
1. Set the observation parameters and specify the module number to be observed, failure cause and call type (you are allowed to check multiple options) on the right side of the interface. 2. Click the Register button to register the set parameters with the foreground. If the registration succeeds, the Register button will be inactive, and the foreground call loss records will be traced dynamically. 3. In the registration state, a call loss record will be generated for each inter-office call failure that meets the conditions, and the record will be listed in the pull-down menu for call loss record on the upper part of this page. Also, the call type of the current record and the total number of records will be displayed to the right of the list. You may choose the records to be viewed from this pull down list, as shown in Fig. 7-50.
Fig. 7-50 View the Call Loss Data Area The current call loss data in the above diagram belongs to the common channel ISUP calls. Click the desired data structure from the tree and the specific values of this structure will be displayed on the display box on the right side of the interface. Operators are allowed to analyze the failure causes. As the current data fall under the common channel ISUP data, if
Page 53 of 273
you select the tab for associated channel calls or common channel TUP calls, the data structure tree will turn gray. 4. If these data are no longer needed, click the <Delete> button to delete all these records. 7.2.7.2 View the Auxiliary Structure On the interface shown in Fig. 7-49, select the View Aux. Struct tab in Fig. 7-49, and the interface will be shown in Fig. 7-51.
Fig. 7-51 View Auxiliary Structures The operation procedures are as follows: 1. Set parameters in the Parameter setup field, including module number, structure name and CCS office ID. 2. Click the View button to view the specified auxiliary structure. According to the data structure name, the following buttons will become active. For example, if the data structure name is CCS TUP common structure, the CCS TUP common structure button will become active. 3. Click the button corresponding to this data structure name, and you will see a pop-up data structure explanation box for this data area.
Page 54 of 273
7.2.7.3
Call False Occupation Select Call fault occupation tab in Fig. 7-49, and an interface will be shown in Fig. 7-52.
Fig. 7-52 Clear False Occupation This interface allows you to view or release the falsely occupied data areas. The operation procedures are as follows: 1. Set the parameters in the Fault Occupation Cond. box, including module number, call type and occupied time. If the call data area exists longer than the occupation time, you may determine that this is a false occupation. 2. Click the View button to find out the falsely occupied data areas. If the records that meet the conditions are found, the system will give a prompt message shown in Fig. 7-53.
Page 55 of 273
Fig. 7-53 Example of Searching Call Fault Occupation 3. Select the index of call fault occupation records, to view the explanation box for this data structure. You may analyze the cause of false occupation based on such explanation. 4. After selecting the index of call false occupation records, by clicking the Clear button, you can release the falsely occupied data area corresponding to this record index. 7.2.8 No.7 Observation No.7 service observation is a useful tool for you to supervise the foreground signaling link and the running status of signaling board, including No .7 status, No.7 MTP status and the signaling board status. Select Observation ? No.7 observation and PP memory management on the interface shown in Fig. 7-2, or click the No.7 button, and you will see a pop-up interface shown in Fig. 7-54.
Page 56 of 273
Fig. 7-54 No.7 service Observation (No.7 Dynamic Alarm) 7.2.8.1 No.7 Dynamic Alarm The Alarm tab is shown in Fig. 7-54. Click the Register button. An interface will pop up as shown in Fig. 7-55. This interface allows you to dynamically view the No.7 alarms, including alarm types and causes.
Page 57 of 273
Fig. 7-55 No.7 Dynamic Alarms 7.2.8.2 No.7 Board Status Monitoring On the interface shown in Fig. 7-54, select the Status observation tab, as shown in Fig. 7-56.
Page 58 of 273
Fig. 7-56 No.7 Board Status Monitoring Set the desired module number and board number on this interface. Then click the Monitor button, and you will see the result of monitoring shown in Fig. 7-57.
Fig. 7-57 Example of No.7 Board Status Monitoring This interface shows the current status of the physical link of this signaling board. Click the Stop button to stop monitoring the current No .7 signaling board. 7.2.8.3 No. 7 MTP Status Observation On the interface shown in Fig. 7-54, select the No.7 MTP Status Observation tab, as shown in Fig. 7-58.
Page 59 of 273
Fig. 7-58 No.7 MTP Status Observation On the right side of the interface, select the observation category and type. If you select the MTP status observation as your desired observation type, click the View button to view the signaling links, signaling link groups and signaling link group status . For example, Fig. 7-59 shows the status of signaling link 1, Fig. 7-60 shows the status of signaling link group 1, and Fig. 7-61 shows the status of signaling route group 1.
Page 60 of 273
Fig. 7-59 Results of the Status of Signaling Link 1
Fig. 7-60 Results of the Status OF Signaling Link Group 1
Page 61 of 273
Fig. 7-61 Results of the Status of Signaling Route Group 1 If you select the type Link statistic, by clicking the View button, you can collect statistics of the status of the signaling links with different serial numbers. Fig. 7-62 shows the status of signaling link 1.
Fig. 7-62 Statistics of Signaling Link 1 Status

Page 62 of 273
If the selected type is SP statistic, by clicking the View button, you can collect statistics of the status of the signaling route groups with different serial numbers. Select the number of a signaling route, and click the View button to obtain the statistic data of this signaling route, as shown in Fig. 7-63.
Fig. 7-63 Result of Signaling Point Statistics 7.2.8.4 Signaling Board Status Observation On the interface shown in Fig. 7-54, select the Status Observation tab, as shown in Fig. 7-64.
Page 63 of 273
Fig. 7-64 Signaling Board Status Observation Select the desired module number and board number, and click the <Query> button to obtain the current status of the signaling board, as shown in Fig. 7-65.
Fig. 7-65 Result of Signaling Board Link Status Observation
Page 64 of 273
7.2.8.5
PP Memory Observation The memory management is designed to view and modify the contents of PP memory. As this function is powerful and mis-operations might lead to serious system problems, please be cautious during the operation. On the interface shown in Fig. 7-54, select the PP Memory Observation tab, as shown in Fig. 7-66.
Fig. 7-66 PP Memory Management The functions of the buttons in the above Fig. are described as follows: 1. conditions. 2. 3. : Displaying the PP memory that meets the viewing
: Displaying the previous 128-byte PP memory. : Displaying the next 128-byte PP memory.
The operation procedures are as follows: 1. Set the parameters on the right side of the interface, including module number, PP index number, selecting the main/slave PP, and originating address.
Page 65 of 273
2. Click the Display button to display the PP memory that meets the viewing conditions. Then click the Previous batch button to display last 128-byte PP memory, and click the Next batch button to display the next 128-byte PP memory. Enter the module number, PP unit index number, and originating address and other parameters, and then click the Display button to view the PP memory data, as shown in Fig. 7-67.
Fig. 7-67 PP memory Observation Result 7.2.8.6 Data Flow Observation In Fig. 7-54, select the MP-MP Data Flow tab, as shown in Fig. 7-68. Enter the interval and the module number, and then click the Start button to observe the result; click the Terminate button to stop the observation.
Page 66 of 273
Fig. 7-68 Flow Observation
7.3
Database Tool
The ZXG10-MSC/VLR service observation system allows you to create independent data list for storing the service failure data. Under special conditions (for example, the system is powered off in the process when the records are being inserted into the database), the database lists might be damaged. In order to ensure that this function is used properly, this system enables you to re-create database lists. The re-creation of database lists may result in the loss of all the original data. Therefore, this function is only recommended when the database list is damaged.
7.3.1
Database List Creation Tool for MSC Service Failure On the interface shown in Fig. 7-2, select Tool ? MSC service failure DB list creation tool, and you will see a pop-up message, as shown in Fig. 769.
Page 67 of 273
Fig. 7-69 Service Observation Prompt After closing all windows, select Tool ? MSC service failure DB creation tool to start creating the MSC service failure database list, and an interface will pop up, as shown in Fig. 7-70.
Fig. 7-70 Prompt for Starting to Create Service Observation Failure List To re-create a list, click the <OK> button to exit the service observation program automatically, and enter the ZXG10-MSS/VLR service observation DB list creation tool system, as shown in Fig. 7-71.
Fig. 7-71 ZXG10-MSS Service Observation DB list Creation Tool Click the <Create> button and the interface will pop up, as shown in Fig. 772.
Page 68 of 273
Fig. 7-72 The Confirmation Box of Creating MSC service Failure Observation List Click the <OK> button, and the new list will be created successfully after a while, and another interface will pop up, as shown in Fig. 7-73.
Fig. 7-73 The Confirmation Box Of Creating MSC Service Failure Observation List 7.3.2 DB List Creation Tool for VLR Service Failure List On the interface shown in Fig. 7-2, select Tool ? VLR service failure DB list creation tool, to start creating the VLR service failure database list. The process is similar to the creation of MSC service failure lists. 7.3.3 DB List Creation Tool for TM Service Failure List On the interface shown in Fig. 7-2, select Tool ? TM service failure DB list creation tool, to start creating the TM service failure database list. The process is similar to the creation of MSC service failure lists. 7.3.4 DB List Creation Tool for MP_MP data flow On the interface shown in Fig. 7-2, select Tool ? MP_MP message flow DB list creation tool, to start creating the MP_MP message flow DB list. The process is similar to the creation of MSC service failure lists.
7.4
Windows Management
ZXG10-MSS/VLR service observation system provides the following methods for windows management.
Page 69 of 273
1. Display the opened windows Select Windows ? Cascade or Windows ? Tile on the interface shown in Fig. 7-2, to display the opened windows accordingly. 2. Minimize windows Select Windows ? Minimize all on the interface shown in Fig. 7-2, to minimize all the opened windows. 3. Arrange icons Select Windows ? Arrange icons on the interface shown in Fig. 7-2, to arrange all of the minimized windows. 4. Close a wi ndow Select Windows ? Close all on the interface shown in Fig. 7-2, to close all the open windows. Before exiting the program, you must close all the open windows. 5. Display only one window Select the name of the window to be displayed from the Window menu on the interface shown in Fig. 7-2, to display the selected window, while other windows are covered.
Page 70 of 273
8
8.1
Billing System
Mobile Billing System
Currently, as defined in the specifications, a local transport system must deliver the following data to the provincial billing center: serial No., record type, call/processing type, calling number, called number, location of the mobile station, tariff, call forwarding number, charging date and duration, reliability indication of charging time field, used service No., transmission mode, trunk group and circuit, communication ending cause, mobile station level (priority), handover date and time, and data related to the handover target office. The X.25 protocol is generally used between the mobile end office and local billing center, as well as the billing centers at various levels. The FTAM (File Transfer, Access and Management) protocol is used for file transfer. The architecture of entire billing system is shown in Fig. 8-1.
Other provincial billing centers
National Billing Center
Charging data for international roaming
Provincial
Other mobile end offices
Local bill transmission system
Local billing system
Call fees charged on subscribers
Fig. 8-1 Architecture of Mobile Billing System
8.2
Introduction to ZXG10 Billing System

ZXG10 billing system consists of charge management module and charge monitoring module. The charge management module allows you to perform background operations on CDR files, such as offline bill backup, deleting offline CDR files; the charge monitoring module is designed to strengthen the control of foreground charging module, improve the charging modules capability to process exceptions, monitor and process
Page 71 of 273
the operation status of the foreground charging module. The charge monitoring module is intended to deliver a series of approaches to problem analysis, problem location, and troubleshooting, and optimize the performance of the charging module.
Billing monitoring process (MP) Foreground Background Billing monitoring process (Server)
Bill collection process
Bill receiving process
Billing management process (Server)
Billing monitoring process (Client)
Billing encoding/ decoding module
Billing management process (Client)
Fig. 8-2 Functional Modules of the ZXG10 Billing System 8.2.1 Performance introduction ZXG10 billing system serves primarily to gather various charging information, and save such information to disks as files in appropriate format. The system also provides a standard interface (FTP/FTAM) for the billing center to transmit the CDR files to the billing system on a real time basis so as to carry out offline settlements. Below are the major functions: The billing management module of the ZXG10 billing system has the following performances: 1. The foreground can correctly create all types of bills. The transmission part should make sure that the bills are transmitted to the background without any loss or repetition and the system is not restarted; 2. The background back up the CDR file to a CDR; 3. The background can backup CDR files to offline storage media such as tapes, removable disks, fixed disks, and network image drive. 4. Only operators with higher authority are allowed to delete CDR files; 5. The background allows you to query and print subscriber charging information randomly;
Page 72 of 273
6. The FTAM protocol is used to send the CDR files to the billing center regularly. The monitoring module of the ZXG10 billing system delivers the following performances: 1. By setting bill filtering conditions, you may filter unnecessary bills so as to ease the communication tension between the foreground and the background. 2. The module provides a number of counters, such as bill quantity counter, data packet counter, and counter of operations on CDR file overstore for you to understand the performance of the foreground charging module during the operation of the entire system. The functions of background counter are implemented through performance statistics. 3. The functionality of foreground service observation allows you to observe the occupation of foreground process data area, analyze and locate problems and provide parameters for the optimization of system performance. 4. By setting foreground charging performance parameters, you may modify the charging performance to optimize the system performance. Foreground charging performance parameters include the size of bill buffer, the number of sent buffers (i.e. logical bill transmission link), bill transmission delay etc. 5. The module is capable of exceptions, so that you can manually clear abnormal bill data and lengthily occupied data areas by force to ensure proper service operations. 8.2.2 Bill Data Management The ZXG10 billing system can be divided into three parts in terms of function: 1. Collecting and transmitting original bills of the foreground. 2. Collecting , processing and backing up the original charging bills. 3. Transmitting the bills to the billing center. The charging bill process is shown in Fig. 8-3.
Page 73 of 273
Fig. 8-3 Bill Flow Chart ZXG10 charging bill management system employs dual buffers (CDR buffer and send buffer). At the server, disk Cluster dual systems plus disk arrange are used. The RAID mirror technology is used for the bill data disk, to ensure the most reliable data storage. Stop-and-wait acknowledgement mechanism with serial numbers is applied between the foreground and the background, so as to ensure reliable and complete CDRs. The features are described respectively as follows:. 1. Bill collection and transmission The foreground MPM collects original bills, and sends them to the billing server. In the foreground, upon completion of each call, a bill will be generated accordingly, and the bill will be automatically transmitted to the CDR buffer in the foreground. If a call lasts over 30 minutes, an intermediate data record will be generated to avoid data loss. Once they meet the sending conditions, the CDRs received in the CDR buffer will be sent to the billing server through a logical communication link. In order to ensure the security of CDRs, in the case of large traffic or abnormal communication between the foreground and the background, when the CDR buffer is full, new CDRs will be saved on the hard disk in the foreground. Till the foreground-background communication sta ys idle, the overstore CDRs will be read from the disk files following the principle of First in first out. These CDRs will be transmitted to the CDR send buffer in the foreground and then to the background billing server, so as to make sure no CDR will get lost.
Page 74 of 273
2. The billing server employs the same mechanism as the foreground to receive the bills from the foreground. The bills received will be saved on the disk immediately, and an ack message will be sent at the same time. ZXG10 billing system employs the stop-and-wait ack mechanism and multi-link bill transmission mechanism to greatly improve the transmission efficiency. The number of links during multi-link transmission is adjustable through the background interface. The hard disks on the server use the disk mirror technology to ensure data security. If the files on the hard disk overflow the pre-set threshold, an alarm will occur at the system alarming console. At this time, the operators must offline the files to a tape drive or CD, and then release the CDR files on the hard disk. 3. Charging client With a man-machine interface, the client features perfect, and specific functions and easy operation. 4. Bill transfer The billing system transmits bills to the billing center in a real time manner. The server is connected to the collector in the billing center via a network cable. FTAM protocol is used to send the CDR files to the billing center. The CDR file is in the format of standard ASN.1. 8.2.2.1 Contents of Charging Bills Under the ZXG10 billing system, bills are divided into five categories: 1. Ordinary CDR: including common calling and called bills, forwarding bills and emergency bills, etc. 2. CDRs arising from changes during the call: including intermediate bills resulting from switch, change in location area, change in mobile phone level, AOC changes etc.; 3. Incoming /outgoing trunk bills: including the outgoing and incoming trunk bills. Whether to generate a bill for the use of a trunk is subject to configuration management;
Page 75 of 273
4. Supplementary services: bill generated for user operations in supplementary services, such as registration, activation and deletion. 5. The bills generated for short messages. The CDR files in the ZXG10 billing system are stored and named based on user-defined parameters. 6. Users select Not support FTAM All the CDR files are saved under the directory \ZXGBIL , and the drive is specified during installation.. A CDR file uses the format prefix + the character string for CDR file naming format. The prefix takes three forms: 1) ON indicates the CDR file with data is being opened. 2) UN indicates the CDR file with data is closed. 3) BN indicates the offline CDR files. Add the field BakFileNameType in the DB SETTING table. By modifying this field, you may change the naming format for the current file, subject to users decision. At present, 32 formats are available: -- Serial number Value -- 001 YYYYMMDDHHMMSSxxxx Second + a 4-digit serial number -- 002 YYMMDDHHMMSSxxxx + a 4-digit serial number -- 003 YYYYMMDDxxxx number -- 004 YYMMDDxxxx -- 005 xxxx -- 006 YYYYMMDDxxx -- 007 YYMMDDxxx Meaning Year Month Day Hour Minute
Year Month Day Hour Minute Second
Year Month Day + a 4-digit serial
Year Month Day + a 4-digit serial number a 4-digit serial number Year Month Day + a 3-digit serial number Year Month Day + a 3-digit serial number
Page 76 of 273
-- 008 YYYYMMDDxxxxx number -- 009 YYMMDDxxxxx -- 010 YYYYMMDD.xxx number -- 011 YYMMDD.xxx -- 012 YYYYMMDD.xxxx -- 013 YYMMDD.xxxx -- 014 YYYYMMDD.xxxxx number
Year Month Day + a 5-digit serial number Year Month Day + a 3-digit serial
Year Month Day + a 3-digit serial number Year Month Day + a 4-digit serial number Year Month Day + a 4-digit serial number Year Month Day + a 5-digit serial
-- 015 YYMMDD.xxxxx Year month date +5 digits of a serial number -- 016 xxx -- 017 xxxxx -- 018 YYYYMMDDHHMMSS -- 019 YYMMDDHHMMSS -- 020 YYYYMMDDHHMMxx + a 2-digit serial number -- 021 YYMMDDHHMMxx + a 2-digit serial number -- 022 YYYYMMDDHHMMxxx digit serial number -- 023 YYMMDDHHMMxxx digit serial number -- 024 YYYYMMDDHHMMxxxx digit serial number -- 025 YYMMDDHHMMxxxx digit serial number a 3-digit serial number a 5-digit serial number Year Month Day Hour Minute Second Year Month Day Hour Minute Second Year Month Day Hour Minute Second
Year Month Day Hour Minute + a 3-
Page 77 of 273
-- 026 YYYYMMDDHHMMxxxxx a 5-digit serial number -- 027 YYMMDDHHMMxxxxx 5-digit serial number -- 028 YYYYMMDDHHMMSSxx Second+2-digit Serial number -- 029 YYMMDDHHMMSSxx Second+2-digit Serial number -- 030 YYYYMMDDHHMMSSxxx Second+a 3-digit serial number -- 031 YYMMDDHHMMSSxxx Second+a 3-digit serial number -- 032 YYYYMMDDHHMMSSxxxxx Second+a 5-digit serial number
Year Month Day Hour Minute +
Year Month Day Hour Minute +a
Year Month Day Hour Minute
The suffix is GCDR, indicating the CDR file is the detailed record of a GSM call. 2. The user selects Support FTAM In addition to the generation of offline backup CDR files (stored under the directory \ZXGBIL), the FTAM file will be generated and stored under the directory \FTAM. The files under this directory in the format of standard FTAM and will be transmitted to the billing center at an interval of 5~30 minutes: FTAM files are named in the following way: The structure of the FTAM filename follows Prefix + character string for CDR file name format + suffix Add the field FtamFileNameType in the DB SETTING table. By modifying this field, you may change the naming format for the current file, subject to users decision. At present, 32 formats are available: -- Serial number Value Meaning
Page 78 of 273
-- 001 YYYYMMDDHHMMSSxxxx Second + a 4-digit serial number -- 002 YYMMDDHHMMSSxxxx Second + a 4-digit serial number -- 003 YYYYMMDDxxxx number -- 004 YYMMDDxxxx number -- 005 xxxx -- 006 YYYYMMDDxxx number -- 007 YYMMDDxxx number -- 008 YYYYMMDDxxxxx number -- 009 YYMMDDxxxxx number -- 010 YYYYMMDD.xxx number -- 011 YYMMDD.xxx number -- 012 YYYYMMDD.xxxx number -- 013 YYMMDD.xxxx number -- 014 YYYYMMDD.xxxxx number -- 015 YYMMDD.xxxxx number
a 4-digit serial number Year Month Day + a 3-digit serial
Year Month Day +.a 3-digit serial
Page 79 of 273
-- 016 xxx -- 017 xxxxx
a 3-digit serial number a 5-digit serial number Year Month Day Hour Minute
-- 018 YYYYMMDDHHMMSS Second -- 019 YYMMDDHHMMSS Second -- 020 YYYYMMDDHHMMxx Second + a 2-digit serial number -- 021 YYMMDDHHMMxx + a 2-digit serial number -- 022 YYYYMMDDHHMMxxx digit serial number -- 023 YYMMDDHHMMxxx digit serial number -- 024 YYYYMMDDHHMMxxxx digit serial number -- 025 YYMMDDHHMMxxxx digit serial number -- 026 YYYYMMDDHHMMxxxxx digit serial number -- 027 YYMMDDHHMMxxxxx digit serial number -- 028 YYYYMMDDHHMMSSxx Second+2-digit Serial number -- 029 YYMMDDHHMMSSxx Second+2-digit Serial number -- 030 YYYYMMDDHHMMSSxxx Second+a 3-digit serial number
Year Month Day Hour Minute +a 5-
Year Month Day Hour Minute +a 5-
Page 80 of 273
-- 031 YYMMDDHHMMSSxxx Second+a 3-digit serial number -- 032 YYYYMMDDHHMMSSxxxxx Second + a 5-digit serial number
Their prefix is FN, and their suffix is GCDR. Both can be modified in the database. The prefix and suffix of the specific CDR files are configurable as required. The charging bill contains the following information: Serial number Record type (or called intermediate charge indication): single charging record or intermediate charging record. Call/processing types: mobile station originated call (MOC), transferring call, mobile station terminated call (MTC), emergency call, short message service, as well as registration, activation and deletion of the supplementary services, etc. Calling number: for mobile subscribers, it includes: IMSI, MSISDN. Called number: for mobile subscribers, it includes: IMSI, MSISDN, MSRN. Mobile station location (original location): MSC identity, location area identity (LAI), cell identity (CI). Other calling/called parties (such as Party C). Starting/ending time of charging. Service codes used: telecom service, bearer service, and supplementary service Transmission mode: transparent and non-transparent transmission. Trunk group and circuit (mainly for No .7 signaling) identification (incoming and outgoing calls). Causes of call termination: normal termination and abnormal termination. Level of MS (priority).
Page 81 of 273
Date and time of handover. The data related to the destination office of handover. Description of service types Supplementary services Short message service (SMS) 8.2.2.2 Generation of Bills Below are examples of the generation of bills in the ZXG10-MSC/VLR billing management system. 1. A mobile subscriber calls a fixed subscriber The system architecture of the mobile subscriber calling a fixed subscriber is shown in Fig. 8-4.
B
ISDN/PSTN
Gate Out GMSC

?
HPLMN
Trunk In
HLR
MSC-A
Trunk Out
MOC
Page 82 of 273
Fig. 8-4 the system Architecture of a Mobile Subscriber Calling a Fixed System Notes: 1) MSC-A generates an MOC bill for subscriber A. 2) The call is routed from MSC-A to GMSC, and a TrunkOut bill is generated at the MSC-A side and a TrunkIn bill is generated at the GMSC side. 3) The call is routed from GMSC to PSTN gateway, and a GateOut bill is generated at the GMSC side. 2. A fixed subscriber calls a mobile subscriber The system architecture of a fixed subscriber calling a mobile subscriber is shown in Fig. 8-5.
A
ISDN/PSTN
?
HPLMN
GateIn GMSC InRoam HLR TrunkOut
MSC-B
Trunk In
MTC
Page 83 of 273
Fig. 8-5 System Architecture of a Fixed Subscriber Calling a Mobile Subscriber 1) PSTN subscriber A is routed to GMSC via the PSTN gateway, a GateIn bill is generated at the GMSC side. 2) GMSC interacts with HLR, and an InRoam bill of subscriber B is generated. 3) The call is routed from GMSC to MSC-B, a TrunkOut bill is generated at the GMSC side and a TrunkIn bill is generated at the MSC-B side. 4) MSC-B generates an MTC bill of subscriber B. 3. A mobile subscriber calls a mobile subscriber The system architecture of the mobile subscribers calling each other in the same network is as shown in Fig. 8-6.
HPLMN
MOC GMSC/MSC
?
HLR
MTC
Fig. 8-6 System Architecture of the Mobile Subscribers Calling Each Other 1) MSC generates an MOC of subscriber A. 2) GMSC exchanges message with HLR to obtain the location of subscriber B. Since A and B are in the same office, the InRoam bill of subscriber B wont be generated. 3) MSC generates an MTC bill of subscriber B. 4. MS calls MS across offices.
Page 84 of 273
The system architecture of the mobile subscribers calling each other across offices is shown in Fig. 8-7.
HPLMN
HLR InRoam Trunk Out Trunk In
?
GMSC/MSC-A MSC-B
?
MOC MTC
Fig. 8-7 Bill Generation for MS Calling MS Across Offices 1) MSC-A generates an MOC bill for subscriber A. 2) GMSC interacts with HLR, to generate an InRoam bill for subscriber B. 3) The call is routed from MSC-A to MSC-B, and a TrunkOut bill is generated at the MSC-A side; a TrunkIn bill is generated at the MSC-B side. 4) MSC-B generates an MTC bill of subscriber B. 5. Call Forwarding Unconditional (CFU) For instance, Subscriber A of PSTN calls mobile subscriber B, and the call is forwarded to Subscriber C of PSTN unconditionally. The bill is generated in a process shown in Fig. 8-8.
Page 85 of 273
ISDN/PSTN
? ?
HPLMN
GateIn GMSC Gate Out
?
HLR
MTFU
MOFU
MSC-B
Fig. 8-8 System Architecture of Creating Bills for Calls Forwarded Unconditionally 1) PSTN subscriber A is routed to GMSC via the PSTN gateway, and a GateIn bill is generated at the GMSC side. 2) GMSC exchanges message with HLR, to discover that MS B has activated the CFU service, and then the GMSC generates an MOFU bill for A to B and an MTFU bill for B to C. 3) The call is routed from GMSC to the PSTN gateway, and a GateOut bill will be generated at the GMSC side. 6. Conditional call forwarding (CCF) CCF (suppose PSTN Subscriber A calls MS B, and the call is forwarded to MS C conditionally) is generated in a process shown in Fig. 8-9.
Page 86 of 273
ISDN/PSTN
?
InRoam
GateIn Trunk In
?
HPLMN
HLR
?
GMSC Trunk Out

? ?
TrunkI n
Trunk Out InRoam
MSC-B
?
MSC-C
?
MTFNR
MOFNR
MTC
Fig. 8-9 Diagram of Creating the Bill for Forwarding Unconditionally 1) PSTN subscriber A is routed to GMSC via the PSTN gateway, and a GateIn bill is generated at the GMSC side. 2) GMSC exchanges message with the HLR and discovers that Subscriber B has activated the call forwarding no reply (CFNR) service. Then GMSC looks for the route of subscriber B and generates an InRoam bill of subscriber B. 3) The call is routed from GMSC to MSC-B, a TrunkOut bill is generated at the GMSC side and a TrunkIn bill is generated at the MSC-B side. 4) MSC-B confirms subscriber B makes no reply, and then generates an MTFNR bill and an MOFNR bill for subscriber B. 5) MSC-B exchanges message with HLR, and an InRoam bill of subscriber C is generated.
Page 87 of 273
6) The call is routed from MSC-B to MSC-C, a TrunkOut bill is generated at the MSC-B side and a TrunkIn bill is generated at the MSC-C side. 7) MSC-C generates an MTC bill of subscriber C. 7. Sending a short message The process of creating a subscriber bill for a short message sent to a mobile station is shown in Fig. 8-10.
HPLMN
Service Centre
?
SMSIWMSC
?
HLR SMSMOIW
MSC-A
SMSMO
Fig. 8-10 Creating a Bill for Short Message Service MSC-A generates a SMSMO bill of subscriber A. SMS-IWMSC generates a SMSMO-IW bill of subscriber A. SMS-IWMSC sends the outgoing short message to the short message center (SMC). 8. Receiving a short message Mobile Subscriber A receives a short message in a process as shown in Fig. 8-11.
Page 88 of 273
HPLMN
Service Centre
?
SMSGMSC
?
HLR
SMSMT-G MSC-A
?
SMSMT
Fig. 8-11 Generation of Bill for a Mobile Subscriber to Receive A Short Message 1) The message is routed from the SMC to the SMS-GMSC. 2) SMS-GMSC exchanges message with HLR, to generate a SMSMT-G bill for subscriber A. 3) The message is routed from SMS-GMSC to MSC-A. 4) MSC-A generates an SMSMT bill for subscriber A.
8.3
8.3.1
Operations on the Alarm Management Interface

User Logon Click the System icon on the floating menu, and you will see a pop-up interface shown as in Fig. 8-12.
Page 89 of 273
Fig. 8-12 Main Interface for the Billing Management System The interface comprises the title bar, main menu bar, shortcut menu, window and information column. In the information column at the bottom of the interface, the two indicators represent the Server-foreground communication status and local terminal-server communication status respectively. Green indicator represents normal communications, red indicator indicates interrupted communications, and gray (used only in multi-module mode) indicator indicates communications with one or a few modules are interrupted, however, not all interrupted. Operators must log in either as a system administrator (system), operator (Operator) or a guest (Guest). Menus on the main interface differ for different operation authorities. Click the Log On shortcut menu, and a dialog box will appear, as shown in Fig. 8-13.
Page 90 of 273
Fig. 8-13 Password Input After you log on as a system user (built in with a password xxxxxx), you will go to the main interface for billing management, as shown in Fig. 8-14. As the system administrator, System is with the highest authority. You may see its functions of billing management on the main menu and shortcut menu, including: bill offline, query, parameter setting, operation management etc. These features will be described in detail below:
Fig. 8-14 Main Interface of Billing Management for SYSTEM User Logon If you log in as an operator, there will be no Operation management in the main billing management interface. This shows the charging operator has no right to Delete all offline CDR files. If you log on as a Guest, tool menu items such as Parameter setting and Bill offline will be invisible from the main interface. A Guest user is only allowed to query CDR files.
Page 91 of 273
8.3.2
Operation Management The Operation management is used to control the authority of a charging operator, delete all the offline CDR files. The billing system provides a number of options, such as bill offline, setting modification and bill printing. Sometimes, different operators are required to use different functions provided by the billing system. In the ZXC10 billing management system, the authorized operator authority can add operators with different authorities through the Operation management menu by following the procedures below: Click on the Operation Management menu and then User Management, or click the User management option on the tool bar, and a dialog box will pop up, as shown in Fig. 8-15.
Fig. 8-15 Operation Management Window You may see a registered user in the billing management system now. Click the <Add> button and a dialog box will pop up, as shown in Fig. 8-16.
Page 92 of 273
Fig. 8-16 Add Operator Dialog Box Enter the name of the operator to be added, and choose OPERATOR or GUEST as the operation authority from the pull-down list. Click <OK> button, and the prompt box for the completion of adding user will pop up, as shown in Fig. 8-17.
Fig. 8-17 Adding User Complete Prompt Click the <OK> button, and the new user will appear in the Operation management window, indicating a new user is added successfully. All types of operators are added and deleted in the same way. To delete an operator, highlight the operator in the Operator list in the Operation management window. Right click this operator and click <Delete> on the pop-up shortcut menu or select the operator and then click the <Delete> button on the top of the operation management window to delete the operator. The Operation management window provides the Delete all offline CDR files option. Click the commands under Operation management to execute operations accordingly. 8.3.3 Offline Bills Bill offline is used to back up the un-offline bills (such as files prefixed with UN) to the designated storage media, and rename the file as offline CDR files (such as files prefixed with BN).
Page 93 of 273
First, you must set offline equipment: Click the Setting menu, and then click Backup device setting and go to the interface for offline device parameter setting. By default, the offline device field shows None. Thus, to create offline bills, y ou must specify offline device, as shown in Fig. 8-18.
Fig. 8-18 Backup Device Parameter Setting (1) You may also choose to download to the fixed disk, as shown in Fig. 8-19.
Fig. 8-19 Backup Device Parameter Setting (2) You may also choose to backup to the network mapped disk following the operations below: Select a shared directory of an online and accessible computer. This shared directory is read-write and mapped as network image drive, such as F: \. In this way, the bills may be backed up offline to the mapped disk. The interface is shown in Fig. 8-20.
Page 94 of 273
Fig. 8-20 Backup Device Parameter Setting (3) You may also choose to download the files to the removable disk, as shown in Fig. 8-21.
Fig. 8-21 Backup Device Parameter Setting (4) You may also choose to download the files to the tape, as shown in Fig. 822.
Fig. 8-22 Backup Device Parameter Setting (5) You may also choose to download the files to other devices, as shown in Fig. 8-23.
Page 95 of 273
Fig. 8-23 Backup Device Parameter Setting (6) After selecting the offline device, the bills can be back upped offline. Click the Bill management menu, and then click Bill offline or click the bill offline shortcut menu to go to Bill offline setting box, as shown in Fig. 824.
Fig. 8-24 Bill Offline Interface Operation: 1. Select the time segment for the CDR files to be downloaded. On this page you will see the Time before last and the Last offline time. If you select the Offline the CDR files before the specified time: option, you must input a time later than the Last offline time. To backup all the new CDR files, select the Offline all on-line CDR files option. 2. Click Offline and a confirmation box will appear, as shown in Fig. 8-25.
Page 96 of 273
Fig. 8-25 Bill Offline Confirmation Click the <Yes> button to backup the new CDR files to the backup device. Please be noted that the CDR files already made offline can no longer be operated offline. 8.3.4 Bill Browsing and Querying ZXG10 billing management system allows users to query information randomly. Go to the CDR file window, as shown in Fig. 8-23. Click the Ordinary file folder on the left pane, and all the backup CDR files under the Zxgbil directory at the server will show up in the right pane. Right click and select Refresh in the pop-up menu, to display all the new CDR files in the window. By clicking the tool menu or the pop-up menu to perform operations for bill query. The right-click menu provides two ways of CDR file arrangement: By list, and By details. Additionally, for easy query, if you click File name, Size or Time in the interface shown in Fig. 8-26, the CDR files will be rearranged in the window automatically as required for the convenience of user query. To generate and see a CDR file immediately, click bill management main menu, and then click Generate CDR file immediately submenu.
Page 97 of 273
Fig. 8-26 Bill Browsing All the created CDR files (including offline and online files) can be viewed, printed and saved. Highlight the file to be browsed and double-click it or use the key combo Ctrl + Enter or use the shortcut key F9, to display the bill contents, as shown in Fig. 8-27. You may also view multiple files at the same time by pressing the Shift or Ctrl key to select the CDR files to be queried, Press <Enter> or use <F9> to display the contents of the selected CDR files. Right click the window for opened CDR files, and a pop-up menu will appear. Select Print to print the CDR files in text format. Choose Save as to save the CDR files to a desired place. If you wish to find your desired bill from a large number of CDR files, you may first set the bill query condition and then activate the condition. Click the Query condition menu, and the setting interface shown in Fig. 8-25 will appear. Query condition contains two tabs, which allow you to set CDR type, Number, time and route respectively. After setting the query condition, click the Save button to save the settings, and click the Return button. Click Activate query condition in the shortcut menu. At this time, the words in the menu turn into Deactivate query condition and are lowered, indicating the query condition is active. Highlight the file to be browsed and
Page 98 of 273
double click it or use Ctrl + Enter or F9, to display the contents of filtered CDR files. You may also view multiple files at the same time by pressing the Shift or Ctrl key to select the CDR files to be queried, and the n press <Enter> or use <F9> to display the contents of all the filtered CDR files selected.. Click Query result shortcut menu, to display the result of the previous query. If you do not need filtering, click Deactivate query condition.
Fig. 8-27 Opened CDR File Fig. 8-28 shows the CDR type tab under querying condition setting and you may select the desired CDR type to be queried.
Page 99 of 273
Fig. 8-28 CDR Query Condition Setting (1) Fig. 8-29 shows the second tab under the query condition settings, which allows you to set the time, number and route information. Route information refers to the name of outgoing and incoming trunk.
Page 100 of 273
Fig. 8-29 CDR Query Condition Setting (2) 8.3.5 Bill Field Settings You may filter bill fields in the background to meet the requirements of different users. Choose CDR field config from the Bill management menu, to go to the interface for CRD field configuration, as shown in Fig. 8-30. Each type of bill has its respective field, which has two attributes: optional and mandatory. You may select or not select optional fields depending on needs. After optional fields are filtered, the corresponding fields contained in the bill will not be coded in the background. Therefore, be careful in using the field filtering. By default, optional field is selected. In general, use the default value. In addition, against protocol, each bill also provides the fields that are not yet available to current billing system for the purpose of extension.
Page 101 of 273
Fig. 8-30 CRD Field Configuration After configuration, save the CRD field and the confirmation message will pop up, as shown in Fig. 8-31.
Fig. 8-31 Confirmation Box for Saving Field Configuration Select <Yes>. This is to synchronize the filed configuration data to the server. After synchronization, update completion message will pop up, as shown in Fig. 8-32.
Page 102 of 273
Fig. 8-32 Prompt for Having Updated Optional Fileds 8.3.6 Setting Parameters Parameter settings include File parameter setting and Offline and delete time setting. 8.3.6.1 File Parameter Settings Select Parameter setting from Setting menu, or click the Parameter setting shortcut menu, to go to the Parameter setting interface, as shown in Fig. 8-33.
Fig. 8-33 Interface for Parameter Setting (File Tab) Parameter change setting interface includes two tabs File and Offline and Delete. The default tab is the File interface. The operation procedures are as follows: 1. CDR file control 1) Intervals of CDR files creation For example, if you set the time interval as 900s, a CDR file will be generated at an interval of 900s, but it does not necessarily mean data is
Page 103 of 273
saved at an interval of 900s; however, a file will be generated for all the bills within this period of 900s and a file name will be given to it. 2) The maximum size of the CDR file The generation of the CDR file can be also controlled by the file size in KB unit, in addition to the time interval control. If the size of the file is 1000KB, a CDR file is generated if each file reaches1000KB. In special cases, CDR fills will be generated manually. You may use Create CRD file command in the Bill management menu to manually generate a CRD file at once. Whether Ordinary bill or Hot charging bill is triggered to generate in two ways, that is, time interval and CDR file size. Thus, the settings for these two parameters are the same in substance. The only difference is that for hot charging bills, Interval and File size requires a small value accordingly. 2. Whether to support FTAM (determining the method of CDR transmission mode) Negotiate this setting with the billing center. Whether to provide another directory for FTAM files means whether the FTAM directory is required in addition to the ZXGBIL directory. 8.3.6.2 Offline and Delete Setting Switch to the Offline and Delete interface, as shown in Fig. 8-34.
Fig. 8-34 Parameter Settings (Offline and Delete Tab)
Page 104 of 273
Each item in the interface has the following meanings. 1. Interval of auto offlining files (controlling CDR file backup) To offline files, you may set an interval based on days as needed. If you choose manual offline, there is no need to set an interval. In this case, you need to offline the files manually at regular intervals, to prevent the disk space at the billing server from being too full to receive bills. You are also allowed to make a setting to delete un-offline CDR files manually. 2. Interval of auto deletion of off-line CDR files (CDR file deletion control) You may set an interval of 1~10 days for deleting the CDR files automatically. This option is only for previous offline CDR files (such as the files with a name beginning with BN). The un-offline files will not be deleted (such as the files with an initial of UN). You may also make a setting to delete off-line files manually. 3. Interval for deleting off-line CDR files automatically (controlling the deletion of CDR files) Un-offline files should be kept long enough for later query. Thus, you should set a long interval of auto deleting un-offline files based on month. You may set Manually delete. Be careful making this setting, to avoid deleting useful bills by mistake.
8.4
8.4.1
Introduction to Charge Monitoring System

Module Functions The charge monitoring function is used to achieve the following functions: 1. Bill filtering The system provides various types of bills. Some bills are not required by the billing center. These bills are called redundant bills. In order to improve the processing performance of the entire system, we may filter the redundant bills in the foreground through background configuration, so as
Page 105 of 273
to reduce communication traffic and ease the tension of background processing. 2. Counter The system provides a number of counters, such as bill quantity counter, data packet counter, and counter of operations on CDR file overstore in order for you to understand the performance of the foreground charging module during the operation of the entire system. 3. Foreground charging service observation As a debugging tool, this function allows you to observe the charging process on a real time basis, analyze and locate problems and provide parameters for the optimization of system performance.. At the present, the data areas to be observed include: foreground bill receiving buffer, overstore CDR disk storage data area, the occupation of communication link for logical bills and detailed data etc. 4. Configure foreground charging performance parameter You may modify the charging performance parameters to optimize the system performance. Foreground charging performance parameters include the size of bill buffer, the number of sent buffers (i.e. logical bill transmission link), bill transmission delay etc. 5. Bill transmission flow control When the system is busy, the bill transmission between the foreground and background will occupy a large bandwidth. If you do not control the bill transmission traffic, the foreground charging process will greatly affect the performance of the entire system. Currently, the service flow of the system is controlled by adjusting the maximum of BHCA. However, it is not advised to control the bill transmission traffic based on the BHCA value but on the current traffic, as not only traffic but also factors such as overstore CDRs will combine to determine the amount of bill transmission. During the foreground charging process, the bill communication traffic is controlled by detecting the current CPU occupation and communication traffic at regular intervals and adjusting the rate of bill transmission automatically. The rate of bill transmission can be adjusted through the
Page 106 of 273
following means in the main: modify the number of logical links for foreground-background bill transmission, or modify the bill transmission delay etc. 6. Exception handling This is mainly to process abnormal bill data and lengthy occupation of data area etc. You may clear these data manually by force, to ensure proper service operations. 7. Overstore CDR Alarm When a overstore of bills occurs in the foreground, the foreground will give an alarm message to the background. 8.4.2 Module Structure The charge monitoring module is designed in MP-Server-Client mode. To improve the performance, some changes are made to this structure. The message transfer mechanism works between the foreground and background or between the background Server and Client. The charge monitoring module works in two processes: one is control process, where the client sets foreground performance parameters (small data flow); the other is observation process, where the client observes the foreground data (large data flow). See Fig. 8-35. Message transfer in these two process is illustrated as follows: 1. Control process: background Client ? foreground. background Server ?
2. Observation process: foreground ? background Client.

Foreground
Set parameters Return observation data
Background Server 1. Set parameters 2. Log in
Return login result Background Client
Page 107 of 273
Fig. 8-35 Charge Monitoring Workflow One background client may monitor several foreground processes, but a single foreground process is monitored by only one background client. At the same time, only one background client is allowed to set foreground parameters.
8.5
8.5.1
Charge Monitoring Management

Introduction to Main Interface Click the Billing Watch icon on the floating menu, and an interface will appear, as shown in Fig. 8-36.
Fig. 8-36 Billing Watch Interface Click the Logon icon shown in Fig. 8-37, and a dialog box will pop up, as shown in Fig. 8-33.
Page 108 of 273
Fig. 8-37 the Logon Dialog Box For charge monitoring, you may log on either as system or guest, which differ in operation authority. system user has the highest authority to carry out all operations. guest user is only allowed to monitor the working state of the foreground and the server but has no right to modify foreground parameters and monitoring parameters. Thus, the guest user is allowed to logon from multiple clients. However, one charge monitoring system (monitoring server and all monitoring clients) allows only one system user to login. Otherwise, the logon operation would fail. If you logon as a system user (built in with the password xxxxxx), the main bill watch interface will be shown in Fig. 8-38.
Fig. 8-38 Main Interface For Billing Watch

Page 109 of 273
The interface consists of title bar, main menu, shortcut menu, window and information box. Select the Information column submenu under the View option on the main menu, and the information column will appear below the window, as shown in Fig. 8-34. This information column records the information returned from monitoring operations, and monitoring parameters as well as the start and recovery of alarms. In the information column at the bottom of the interface, the two indicators represent the Server-foreground communication status and Local terminal-server communication status respectively. Green indicator represents normal communications, red indicator indicates interrupted communications, and gray (used only in multi-module mode) indicator indicates communications with one or a few modules are interrupted, however, not all interrupted.. The Billing watch main interface mainly contains shortcut menus such as Co. Moni., Rec. Moni., Trans. Fit., Sync. 129 etc, involving the main monitoring operations of the monitoring module. Each main shortcut menu is designed to perform the following functions:
Serves to observe the services at foreground nodes, and monitor one or more foreground nodes.
Serves to observe and trace the receipt of bills by the billing server.
Serves to filter redundant bills according to actual requirement, so that the foreground will not transfer bills to the background, and thus ease the communication tension.
Allows you to obtain desired configuration information from 129 Server manually.
Page 110 of 273
8.5.2
Foreground Monitoring Click the Co. Moni. Shortcut menu, and a dialog box shown in Fig. 8-39 will pop up. Select the foreground nodes to be monitored from the pulldown list, to monitor the working state of the charging nodes in the foreground.
Fig. 8-39 Select Foreground Monitoring Nodes After clicking the <OK> button, the foreground monitoring interface will appear, as shown in Fig. 8-40.
Fig. 8-40 Foreground Monitoring Interface
Page 111 of 273
You may open several foreground nodes at the same time for monitoring. For each monitored node, there is a billing watch window in order for the user to monitor its status. The billing watch window includes two tabs, which will be described below separately. 8.5.2.1 Service Observation As shown in Fig. 8-40, foreground charge service observation is mainly intended to observe the foreground CDR receive buffer, the use of overstore CDR file data area, the overstore CDR send buffer and logical bill transmission line and details. For the data area, three types of information are provided: 1. If a data area is occupied and over-stored, it will be represented visually in color; 2. The size of a data area involves two cases. The size of the CRD receive buffer and CDR send buffer is always 32K, but the size of the foreground overstore CDR disk space is subject to the data obtained from the monitoring process and will be refreshed at the specified intervals; 3. Give read-write data area pointer. After receiving original CRD parameters from the s ervice module, the foreground will send them to the background through CRD receive buffer. If the communication between the foreground and background is not smooth or the link is disconnected or the number of CDRs goes beyond the processing capacity of the background instantaneously, the foreground CDRs cannot be transferred to the background in time, thus causing overstore CDRs. The overstore CDRs will be stored on MP disk in file format. Until the link is connected, the overstore CDRs will be sent to the billing 130 background via the Overstore CDR send buffer. When a data area is overstored, it will be displayed in a different color. For the transmission link between the foreground and background, you may observe the state of link, the CDR sequence number, retransmission times and transmission time flag on a real time basis. ZXG10 billing system supports multi-link bill transmission mechanism, which allows you to specify the number of links by hand. A link has two states:
Page 112 of 273
1. Wait to receive bill state indicates the link is idle and the background waits for the bills to be transmitted from the foreground. 2. Wait to answer state indicates the link is now working, waiting a response from the background bill receiving server. If the link fails to transmit bills to the background, the retransmission mechanism will apply. 8.5.2.2 Counter The Counter tab is shown in Fig. 8-41. A number of counters are available, such as bill quantity counter, data packet counter, overstore CDR counter, overstore CDR operations counter, in order for you to understand the performance of the foreground and background modules during the operation of the entire system. Click the Start button to begin counting.
Fig. 8-41 Counter
Page 113 of 273
8.5.3 8.5.3.1
Parameter Settings Foreground Parameter Settings When the system is busy, the bill transmission between the foreground and background will occupy a large bandwidth. If you do not control the bill transmission traffic, the foreground charging process will greatly affect the performance of the entire system. Currently, the service flow of the ZXG10 system is controlled by adjusting the maximum of BHCA. However, it is not advisable to control the bill transmission traffic based on the BHCA value but on the current traffic, as not only traffic but also factors such as overstore CDR will combine to determine the amount of bill transmission. The rate of bill transmission can be adjusted by modifying the number of logical links for foreground-background bill transmission, or the bill transmission delay etc. so as to control the bill transmission flow. Click the Configure foreground shortcut menu on the main interface or select the Configure foreground performance parameter command in the Monitor operation on the main menu, and the CDR Collector Setting dialog box will pop up, as shown in Fig. 8-42.
Fig. 8-42 Foreground Service Parameter Setting Select the module number and change the default bill transmission delay and the bill timeout-resend delay. The logical link for bill transmission is channel for transmitting bill parameter data to the bill receiving process at the billing server through the lower communication layer by way of TCP/IP by setting aside a memory of 2K byte in the foreground process as the cache. By default, there is only one such link. The number of links may
Page 114 of 273
range from 1 to 25 links as the case may be. After modifying the parameters, save them. 8.5.3.2 Monitoring Parameter Setting Select the Monitor parameter command from the Monitor operation main menu for charge monitoring, and the monitor parameter setting interface shown in Fig. 8-43 will appear. Monitor setting is mainly designed to set some monitoring timers, including foreground monitor parameter setting, bill receive monitoring parameter setting, and server monitor timer setting.
Fig. 8-43 Monitor Parameters Setting On this interface, you may set the timers relating to the foreground charging process. In order to improve the efficiency of the billing system and avoid affecting the speed of service processing as a result of monitoring, it is not advisable to set two small timers so as to avoid unnecessary overheads. Generally, you may use the default values without the need for any change. The functions of the main timers are described below. 1. Buffer query timer: set the time interval between the monitor foreground module to query foreground CDR receive data area and send and overstore data area. After obtaining the latest data, the monitoring process will refresh the state of background data area. 2. Link query timer: set the time interval for the monitoring module to query the bill transmission link between the foreground and background, and
Page 115 of 273
obtain the latest state of the transmission link, to decide whether it is in Idle state or Wait for billing server to answer state. 3. Counter refresh timer: set the frequency of refreshing each data recorded in charge monitoring. 4. Server check timer: set the handshake interval between the charge monitoring module and the CDR receive server process, so as to decide if the server still exists and whether the monitor connection is still active or need to be reconnected. 8.5.4 Transmission Filtering ZXG10 charge monitoring module enables you to filter foreground bills, in order to handle the unnecessary bills (also known as Redundant bill) in the background instead of transmitting them to the background, so as to reduce the traffic between the foreground and the background. Click the Transmitting filtration shortcut menu on the Billing watch main interface, and an interface will appear, as shown in Fig. 8-44.
Fig. 8-44 Transmission Filtering Select the CDRs to be filtered, save the change, and a confirmation box will pop up, as shown in Fig. 8-45.
Page 116 of 273
Fig. 8-45 Transmission Filtration Confirmation 8.5.5 Receive Monitoring Receive monitoring is designed to monitor the CDR receiving process and monitor the state of the CDR receiving server process at the client side. In the course of tracing the received and monitored CDRs, you may view the count of received CDRs. See Fig. 8-46.
Fig. 8-46 Received CDR Counter The received CDR counter includes CRD counter and packet counter. The CDR counter will display the number of various received CDRs in a real time manner, while the packet counter will record the number of packets,
Page 117 of 273
which are sent, received, acknowledged, lost, retransmitted and undergo CRC check error in the foreground and the background, as well as the number of packets, which are filtered, coded, undergo coding exception, coding error or are not coded. The CDR packet counter is important for us to discover CDR receiving exceptions and locate the fault correctly. 8.5.6 Synchronization 129 For a CDR format, the charging background needs to obtain the information such as local signaling point code, trunk group, and Msc configuration. This information is stored in the basic configuration database at 129 server. Therefore, to avoid relevant field error after coding, you are required to synchronize 129 Server manually after installing the charge system or when the basic configuration table change, in order to obtain the corresponding configuration information. Click the Sync 129 shortcut menu on the Billing Watch main interface, and a box will pop up, as shown in Fig. 8-47.
Fig. 8-47 Select the Type of Backup CDR File Naming Select <Yes> to synchronize 129 data. At the same time, the system will restart the CDR receiving process. After successful synchronization, the Synchronize 129 tables successfully message will appear in information column for charge monitoring. Please be noted that after the data tables contained in the 129 basic configuration database are modified, such as local signaling point code, trunk group, and Msc configuration, the modified data will be transmitted to the foreground and synchronized to the billing server automatically at the same time. At this point, the CDR receiving process will get restarted. In other words, unless after installing the billing system to recreate a database, it is generally not necessary to synchronize 129 data by hand .
Page 118 of 273
8.5.7
Alarm Interface The charge monitoring server serves to manage the alarm messages given by each module of the billing system and provide an interface with 129 alarm management. Charge alarm messages include: foreground alarm, CDR management alarm, billing server alarm and CDR receiving alarm. Foreground alarms mainly include the overstore CDR alarm on the foreground MP; CDR management alarms include the offline fault alarms arising from the failure in offline device. The billing server gives alarms when the monitored free space that stores CDRs and backup CDR files exceeds the threshold, and will also give alarms for the state of the link between it and the billing center. CDR receiving alarms occur when the versions of the foreground and background are inconsistent at the time of upgrading. For each charge-related alarm, you will see their respective alarm code, alarm message and alarm level as well as the generation and recove ry of alarms from the management module of 129 server. Open the information column under the main menu view, as shown in Fig. 8-48, and you may observe the real-time alarms. Mostly, you may view the history alarms in the charge log.
Page 119 of 273
Fig. 8-48 Real Time Alarm in Information Column
8.6
8.6.1
Billing System Operations

Query Bills The bill query function allows you to query CDRs with ease by user number, number of the other party, start/end time of call, call duration, and routing information or by a combination of any of the above conditions. The procedure of CDR inquiry is as follows: 1. Open the billing management client and logon the billing management as system or guest or any user. 2. Click the Query condition setting on the billing management tool bar, to set query conditions. 3. Select the bill type to be queried from the query conditions. By default, all types are selected. In generally, the default value applies.
Page 120 of 273
4. In query condition settings, set query conditions based on known conditions such as user number, number of the other party, start/end time of call, call duration or routing information. For example, to query the CDRs of a subscriber, whose number is 13907200021, just enter 13907200021 in the current subscriber number text field, and click Save to save the specified query condition. 5. After setting the query condition, close the Query condition window and return to the main interface. 6. Click Active button on the tool bar in the main interface. 7. Select one CDR file or several CDR files (using shift), and click the Query CDR button, to get the CDRs to be queried. 8.6.2 Bill Offline Bill offline is used to back up the un-offline bills to the designated storage media, and rename the CDR file as offline CDR files.. The procedure for bill offline is as follows: 1. Logon to the billing management system as system user or operator. For adding billing operators, please see. 2. For details about setting offline bill backup device, please see Section 8.3.3. 3. Click the Bill management menu and then click Bill offline or click the Bill offline menu, to go to the Bill offline setting box. 4. Select a bill offline mode. You may either offline all un-offline bills or offline the CDR files within a time period. 5. Click Offline and the confirmation box will appear, as shown in Fig. 825. Click <Yes> to back up the new CDR files to the backup device. 8.6.3 Add, Delete Billing Operator The system administrator is allowed to add and delete two kinds of billing operators: GUEST and OPERATOR. Different billing operators are granted different authorities. For details, please refer to Section 8.3.1. Add or delete a billing operator following the steps below:
Page 121 of 273
1. Logon to the billing management system as SYSTEM. 2. Click Operation management menu on the main interface, and then click User management or click User management on the tool bar, and the operation management interface will appear. 3. Click the <Add> button on the operation management interface to go to the Add operator interface. 4. Enter the operator to be added in the Add operator interface. You may choose OPERATOR or GUEST from the authority pull-down list. Click <OK>, and the message Adding user completely will pop up. 8.6.4 The Foreground Monitoring To learn about the performance of the foreground charging module in the entire system operation, carry out foreground monitoring. The function of foreground monitoring may serve to monitor the state of receive buffer, overstore CDR file, send buffer, use of resource, and bill link transmission on a real time basis, and also collect statistics of bill quantity, data packet, overstore CDR file etc. The operation procedure for foreground monitoring is as follows: 1. Open the Billing watch window and logon as system or guest. 2. On the Billing watch main interface, click the Foreground monitoring shortcut menu and the select monitoring node dialog box will pop up. Select the foreground node to be monitored from the pull-down list, to monitor the work state of the billing foreground nodes. 8.6.5 Bill Receive Monitoring The function of receive monitoring serves to monitor the bill receiving process, display the number of various bills received and the number of abnormally coded bills on a real time basis. This feature is very important for fault location. The receiving of bills is monitored in the following procedure: 1. Open the billing watch window and logon as system or guest. 2. Click the Receive monitoring shortcut menu on the Billing watch window, and the Receive monitoring main interface will pop up.
Page 122 of 273
3. You may view the count of the received bills from the Counter tab. 8.6.6 Transmission Filtering This feature may filter the unnecessary and redundant bills during the transmission between the foreground and the background instead of transmitting them to the background, so as to reduce the traffic between the foreground and the background. The operation procedure is as follows:. 1. Logon to bill monitoring as system user. 2. Click the Transmitting filtration shortcut menu on the billing watch main interface, and the CDR-Transmitting Filtration interface will appear. 3. On the interface, select the bill types to be processed for the billing system. Click <OK> to save the change, and a conformation box for modification will pop up. Click <Yes>. 8.6.7 Common Charge Alarms Recovery Methods 1. Testing alarms for whether there is overstore CDR in the foreground, or whether the overstore CDR exceeds 600M or 1.2G Currently, when the foreground bill overstores up to 16M, the foreground will send overstore CDR alarm, which is generally caused by: foregroundbackground communication interruption; abnormal receiving; insufficient background bill backup space (less than 50M). When the above symptoms take place, appropriate measures should be taken, such as restoring communication link, restarting charge receiving process, deleting overdue bill releasing space etc. After the foreground overstore CDRs are transmitted to the background, the overstock CDRs will recover automatically. 2. When the charging bill storage space is less than 200M, 100M or 50M, alarms will be given These alarms generally result from the insufficient backup space under the ZXGBIL directory. In this case, you may back up overdue bills to another device for freeing disk space. 3. When the storage space for backing up local bills is less than 200M, 100M or 50M, alarms will be given
Page 123 of 273
These alarms generally result from the insufficient backup space under the FTAM directory. In this case, you may back up overdue bills to another device for freeing disk space.
Page 124 of 273
9
9.1
9.1.1
Variable Control System

System Overview
Main Functions The security management is necessary for the entire ZXG-MSC/VLR system in order to safeguard its security, to prevent malicious attack, and to restrict unauthorized access or wrong access. The security management system safeguards the access to the network management system and sensitive PLMN data. The security management system involves mobility security management and variable control. 1. Mobility security management Radio transmission makes users vulnerable to the encroachment upon their privacy and interests. Therefore, to guarantee the rights and interests of users, the "Mobility management" subsystem is provided.. The system not only blocks the access of unauthorized users, but also protects users' communication privacy. The mobility security management of ZXG10MSS/VLR involves the following aspects: 1) User ID encryption; 2) User ID authentication; 3) Air interface data encryption. 4) Mobile equipment security. For non-roaming subscribers, it is up to the operator to decided whether to use these features. For roaming subscribers, they are mandatory, except with the approval of all related PLMN operators. 2. Variable Control The variable control mainly includes 1) A-interface variable control: for system flow control. 2) CC variable control: emergent calls and part of call service control..
Page 125 of 273
3) Number expansion variable and TM control: determining the number of digits contained in subscribers MSISDN and the mobile system version number. 4) Service control variable: to control various service performance indexes. 9.1.2 Introduction to Interfaces After the installation of ZXG10-MSC/VLR operation and maintenance system, run OSCLI.EXE under the directory C:\ZXG10. Start the security management program, and you will see a pop-up interface shown in Fig. 9-1.
Fig. 9-1 Main Interface for the ZXG10-MSS Security Management System The main interface of the ZXG10-MSS security management system consists of main menu, toolbar, window, and status bar. The tool bar contains shortcut buttons for common commands. The first six buttons are used for mobility security management, the second six buttons are for service variables, and the last button is for sending. Keep the pointer on the button for a while, and the function of this button will appear. Status bar is at the bottom of the interface. In the middle of status bar is the local terminal number; on the right of the status bar are two indicators. The left indicator shows the communication between the server and the foreground, while the right indicator shows the communication between the local terminal and the server. The red indicator means the
Page 126 of 273
communication is totally interrupted; the gray indicator appears only in the multi-module mode, where some modules communicate properly while others are disconnected; a green indicator means the communication is perfectly OK. The gray indicator appears only in a multi-module office. Keep the pointer on the indicator for about a second, and the state of this indicator will appear on the screen. Right click the indicator area, to display the details about the communication on current modules. 9.1.3 System Management The lower pane in Fig. 9-2 is the log area, where the Security management operations by operators are recorded automatically.
Fig. 9-2 ZXG10-MSS Security Management System All current operations are now displayed in the log area.
9.2
Mobility security management

One of the most important features of mobile networks is radio transmission, which tends to impair their privacy and interests. In order to prevent illegal access, and to protect users privacy, security management measures are taken in GSM, such as authentication, encryption, ID secrecy, and equipment security. The implementation of these security
Page 127 of 273
measures rests with the network operators, while ordinary users are not allowed to intervene. The Mobility security management subsystem in the Security management system is designed to implement security measures, such as authentication, encryption, ID secrecy, and equipment security. In the Mobility security management subsystem, a small number of authorized operators may decide whether to carry out such measures. 9.2.1 Basic Concepts Some of the basic concepts involved in operations on the Mobile security management interface are introduced below, such as location updating, IMSI attach etc: 1. IMSI attach IMSI, or international mobile station identifier, is used to identify the internationally universal number of a mobile subscriber, which is saved in HLR, AUC and VLR. An MS is usually in three statuses: MS ON (idle), MS OFF and MS BUSY. When a MS is switched on and stays idle, the IMSI of this subscriber will be marked with Attach; when the MS is switched on but still in the process of a conversation, the IMSI of this subscriber will be marked with Busy; when the MS is switched off, the IMSI of this subscriber will be marked with Detach;. In this way, MSC/VLR will know the MS status. 2. Location Updating When an MS roams from one location area to another, it is required to register, that is to say, once the MS discovers its own LAI differs from the newly received LAI, it will re-register with the current MSC/VLR. 3. Periodic registration Although the MS is in a blind area or it has been switched off, the IMSI is somehow not detached from MSC/VLR. In either case, if this MS is paged, the system will keep sending a paging message, resulting in useless occupation of radio resources.. In order to avoid this, GSM system imposes compulsory registration, requesting the MS to originate location updating at intervals, known as periodic registration.
Page 128 of 273
4. TMSI As IMSI is unique, its repeated use may render it vulnerable to decoding. Thus, to keep IMSI in secret, the GSM network uses TMSI. TMSI is a 4-bit BCD number temporarily assigned to a subscriber by his VLR. As you may change it often, it is not easy to get stolen. Operators are allowed to define the conditions in which subscribers are assigned with new TMSIs with their old TMSIs cancelled. This operation is called the reallocation of TMSI. In Security Management subsystem under the ZXG10-MSC/VLR operation and maintenance system, authorized operators may decide when to allocate TMSIs. 5. Authentication Authentication is intended to protect legal users, and prevent illegal users from Intrusion, and verify the identity of mobile subscribers. Such authentication uses the authentication parameter triplet saved in the HLR, The triplet is generated in AUC (authentication center) and stored in HLR. If the VLR contains only 0~2 groups (configurable), it will request an authentication parameter triplet from HLR, which will allocate 5~10 groups to HLR each time. This process is repeated. 6. IMSI re-authentication For the following reasons, legal users may also experience an authentication failure: 1) The TMSI of MS is not known to the VLR. 2) The TMSI of this subscriber has been assigned to another ISMI (due to the repeated use of TMSI). In the above two cases, the network must carry out re-authentication through open IMSI transmission. 7. Encryption Encryption is intended to prevent illegal persons or organizations from monitoring or snooping when user information and parameters are
Page 129 of 273
exchanged between the BTS and an MS. Encryption is done on radio channels, to scramble the signals at MS side and de-scramble them at the BTS side. 8. Call re-establishment A call session may, due to multiple reasons, be interrupted abruptly. In this case, the mobile station will originate a request for call re-establishment. Of course, this process of call re-establishment is Masked from users. Operators may decide whether to authenticate the subscriber during the course of call re-establishment, and the VLR will decide whether to carry out a uthentication according to the command it receives. 9. IMEI IMSI is the unique code that labels a mobile station device. It is built permanently by the manufacturer in with the mobile station, so that neither the user nor the telecom service carrier can modify it. Checking of IMEI at the network end can prevent the use of illegal mobile stations. 9.2.2 Basic Operations of VLR Module on Server Security Variables Operators authorized by the system administrator may set or modify the parameters used in the Mobility security management subsystem. As the security management is connected with offices and modules, the first step is to select an office or a module in the office in the configuration area. Mobility security management is conducted in the VLR. Thus, select VLR module in Fig. 9-1. Then, the corresponding buttons on the tool bar become active. Select the System management ? get security parameter on server or click the shortcut button , the items in the Mobility security management menu will also become active. Be sure to click System management ? Send parameter or click the Send button to transmit data to the foreground after modifying any parameter. Only in this way will the modified data take effect. The detailed operations are as follows: 1. User ID secrecy management User ID secrecy management can be operated not only by the system administrator alone, but also by any authorized ordinary system administrator.
Page 130 of 273
Select Mobility security management ? ID secrecy and you will see a pop-up menu shown in Fig. 9-3.
Fig. 9-3 ID Secrecy Management This interface allows you to decide whether to re-allocate TMSIs to mobile subscribers in the course of call services and location updating. During the course, the fact should be taken into consideration that the reassigned TMSI frequency might affect the privacy of subscribers. Setting procedure: double click a selected parameter on the interface shown in Fig. 9-3, and make the settings on the pop-up dialogue box. For instance, if you double click the MO call item, you will see a pop-up dialogue box as shown in Fig. 9-4. Check the MO call on this box indicating that re-allocation is needed. After the setting, click <OK>.
Page 131 of 273
Fig. 9-4 Set MO call Enables/Disables TMSI Reallocation . Right click the function pane shown in Fig. 9-3, and you will see a pop-up menu. You may use commands in the menu for operations. Detailed operations: in the function pane, you can check multiple items by using the shift + ?or? or Ctrl+ click .If the checked options are all preceded by v, right click here and a shortcut menu will pop up. You may see two options in the menu: Select and Deselect. These options allow you to Select all or Deselect.. Such a function applies to all function boxes, so we will not repeat it in later sections. 2. Identity authentication management GSM provides a user ID authentication system to protect the legal interests of users and prevent unauthorized applications. ZXG10MSC/VLR operation and maintenance system allows you to set the frequency and occasions of authentication in. In the window shown in Fig. 9-1, select Mobility security management ? ID authentication, and you will see a pop-up menu shown in Fig. 9-5.
Fig. 9-5 ID Authentication Management
Page 132 of 273
Functions of ID authentication: 1) Whether to exercise authentication control To authenticate users in multiple processes helps enhance the guard against unauthorized use. If encryption is necessary, authentication is required in each service visiting process. If encryption is neither required nor supported, operators may choose to carry out authentication on a specific service. 2) Reuse times Generally, each group of authentication vectors can be used only once, which will be discarded afterwards. However, you are allowed to reuse the authentication vectors when you fail to apply to the HLR for parameter authentication, thus causing authentication failures. As how many times the vectors are reused might affect the network security, it is up to the operators to control the times (by selecting Reused times in the function area and making the setting). 3) Use authentication vectors Each authentication is originated by the VLR. The authentication vectors of every subscriber are saved in the VLR, used for subscriber authentication. Operators are allowed to decide the minimum number of authentication vectors stored in VLR by selecting the Minimum number of vectors in the function area. Given the number of authentication vector ranging between 0 and 2, when the number of authentication parameters in the VLR is less than the number specified by the operator, VLR will ask the HLR for more. For example, there are 5 original authentication vectors for Subscriber A in the VLR, while you choose 1 in the Minimum number of vectors box. Then, after Subscriber A is authenticated for 4 times, only one authentication vector of Subscriber A is left in the VLR (excluding the case where vectors are re-used). In this case, the VLR will ask the HLR for authentication vectors, 5~10 for each time.. Setting procedure: Double click the selected parameter on the interface shown in Fig. 9-5, and make the settings on the pop-up dialogue box. For instance, if you double click the MO call parameter, you will see a pop-up dialogue box, as shown in figure 9-6. Select the MO call option in this
Page 133 of 273
box, indicating that the re-authentication is needed. After the setting, click <OK>.
Fig. 9-6 Set Whether to Authenticate MO Call 3. Data encryption management The data encryption management is used to encrypt the data and signaling transmitted through the air interface. The encryption process involves two important encryption algorithms: encryption algorithm A5 and Kc generation algorithm A8. In the AUC, the A8 algorithm is used to generate Kc, which is then stored in the HLR. When VLR asks for it, Kc (contained in an authentication parameter triplet) is transmitted to the VLR. As for the A5 algorithm, 7 versions are allowed in GSM, which are A5/1, A5/2, and A5/7. The operators are allowed to deliver the authorized versions to the BSS, which is required to choose one version from the list after identification. So long as BTS supports any version in the list, encryption is required. Operators can also choose whether to make the encryption. If encryption is required, before each call, VLR will deliver the Kc and A5 algorithm list to BSS, and then to the MS side. MS will scramble the information using Kc and A5 algorithm . Select Mobility security management ? Data encryption and you will see a pop-up menu shown in Fig. 9-7.
Page 134 of 273
Fig. 9-7 Data Encryption Management Interface The Encryption control parameters include: 0: not to encryp t. Whether or not there exists available A5 algorithm, encryption is not made. 1: for encryption control. If the operator selects Encrypt control, after BTS receives the version list of A5 algorithm, it will judge whether there is a version it supports. As long as one version in the list is supported, you may encrypt the information and data; if no version is supported by BTS, no encryption applies and the call will continue. After the configuration of data encryption, before each call, MSC/VLR will obtain information from the Data encryption management subsystem and process it in accordance with the settings made in the subsystem. Setting procedure: double click the selected parameter on the interface shown in Fig. 9-7, and make the settings on the pop-up dialogue box. For instance, if you double click the A5/3 encrypt algorithm item shown in Fig. 9-7, you will see a pop-up dialog box as shown in Fig. 9-8. If you select A5/3 encrypt algorithm in the dialogue box, it indicates that the network allows for this algorithm. After the setting, click <OK> button.
Page 135 of 273
Fig. 9-8 Set A5/3 Encrypt Algorithm 4. Equipment security management Equipment ID is used to check the legality of mobile equipment itself, in order to make sure legal equipment is used in the network. Each MS is equipped with a internationally unique IMEI. A list of equipment types is saved in the EIR (Equipment Identification Register), where there is a white list, a black list and a gray list. The white list specifies the numbers of all the legal mobile devices; the black list specifies all the prohibited IMEIs; the gray list records the faulty IMEIs or unauthenticated IMEIs. The network identifies equipment by requesting IMEI from the MS. It is up to the operators to decide whether to identify the equipment. In the interface shown in Fig. 9-1, select Mobility security management ? Equipment security, and a pop-up menu will appear, as shown in Fig. 9-9.
Page 136 of 273
Fig. 9-9 Equipment Security Management Setting procedure: double click the selected parameter on the interface shown in Fig. 9-9, and make the settings on the pop-up dialogue box. For instance, if you double click the Call management service parameter, you will see a pop-up dialogue box shown in Fig. 9-10. If you select Call management service in this dialogue box, this indicates that the equipment will be identified during the call service. After the setting, click the <OK> button.
Fig. 9-10 Set Call Management 9.2.3 Basic Operations of VLR Module on Foreground Security Variables Operators authorized by the system administrator are allowed to set or modify the parameters in Mobility security management subsystem.
Page 137 of 273
Like operations at the background server, select No.2 sub -module under the VLR module shown in Fig. 9-1, and select the System management ? Get foreground security parameter command or click the button. Then, the options in the Mobility security management menu will become active. All the parameters are identical to those in Section 9.2.2. The only difference is that these parameters are obtained from the foreground MP.
9.3
Variable Control
In terms of module, variable control involves MSC and VLR; variables for MSC module consists of four parts: A-interface variable control, CC variable control, number expansion variable and TM control and service variable control. VLR module is divided into two parts: number expansion variable and TM control, and service variable control. Each module involves getting service variable from the background server and from the foreground. To carry out these operations, you may select the System management ? Get service variable from server menu and the System management ? Get foreground service variable command, corresponding to the shortcut buttons and respectively. Then, relevant items in the Variable control menu wi ll become active. Likewise, you need to send parameters after modification. Background parameters are identical to foreground parameters. So, we only talk about getting service variables from the background server.
9.3.1
A-interface Variable Control on MSC Module Select Variable control ? A interface variable control in Fig. 9-1, and you will see a pop-up interface, as shown in Fig. 9-11.
Page 138 of 273
Fig. 9-11 A Interface Variable Control: Below are the meanings of parameters in the function area: 1. Whether send confuse message: after receiving abnormal messages, whether A-interface will send CONFUSION message to the BSC. If control variable of the CONFUSION message is sent, this indicates whether the foreground, after receiving an error message, will send out the confusion code. 0 for sending; 1 for not sending. 2. Number of MSC reset try: Resetting is aimed at initializing the faulty MSC. In general, only when MSC fails and all the reference information related to the processing gets lost will the MSC be reset. In abnormal cases, however, if the MSC cannot receive the Reset ack message within the specified time limit after sending the Reset message, the Reset message will be resent. Repeat times are specified in Number of MSC reset try, and at least 1 time is required. If the Reset ack is still not received when the threshold is reached, ZXG10-MSS fault management system will give a notification message. When a fixed prepaid subscriber dials 13800138000 to trigger an intelligent service, the SCP address varies with the value of this security variable . The default value is 8; if the security variable is valued 8, the
Page 139 of 273
homing SCP address of this fixed subscriber will apply; if the value is not 8, use 13800138000 to analyze the acquired SCP address. 3. Number o f MSC circuit reset try: The circuit is reset to restore the system information in MSC when failure has affected only a small part of the equipment. Similarly, the number of repetitions under abnormal conditions is subject to service operators. You may set the value in the list against the Number of circuit reset try icon. If the repeated attempts reach the set value but there is still no acknowledgement, terminate the circuit resetting process. At the same time, the ZXG10-MSS fault management system will give a notification message. 4. Whether retry on switching error: this is the identifier for whether to retry in the event of a failure to send a message, indicating whether to resend the message after failure. 5. Whether use the same cell as destination cell on retrying: this is for whether to select the same cell after switching failure. 6. Number of retries on switching error: the value ranges from 1 to 7. 7. CPU load control levels: CPU load levels and used INDEX levels are used for system flow control. The CPU load level box allows you to set the thresholds for 6 CPU load levels . For the settings, the value of a lower level should be greater than that of a higher level. So, suppose the first level is 50%, the second level should not be lower than 50%, and the remaining settings follow this rule. If the CPU load comes to a level, an alarm will be given accordingly. 8. Used INDEX level: four levels are available. The settings are the same as those made for CPU load levels. Setting procedure: double click a selected parameter on the interface shown in Fig. 9-11, and make the settings on the pop-up dialogue box. For instance, if you double click the Number of MSC reset try parameter shown in Fig. 9-11, you will see a pop-up dialogue box as shown in Fig. 912. Set the number of MSC retries in this dialogue box and then click <OK>.
Page 140 of 273
Fig. 9-12 Dialogue Box for Setting the Number of MSC Reset Retry 9.3.2 CC Variable Control for MSC Module Select variable control ? CC variable control in Fig. 9-1, and you will see a pop-up interface as shown in Fig. 9-13.
Fig. 9-13 CC Variable Control: Below are the meanings of some parameters in the function area: 1. Whether set mark of cycle resending monitoring message/CRC: this is for whether to resend the monitoring message/CRC repeatedly after local office sends the message but receives no ack message. 0 for not resending.
Page 141 of 273
2. Whether refuse to release trunk after calling: this is for whether to send blocking message to the peer office in order to block the circuit while releasing a call, and then release call resource. 0 for not refuse, while 1 for refuse. 3. Delay time gate: duration of echo. 4. Type of service key for MS: under the target network, mobile subscribers dial 13800138000 using a service key. 1) 0: IN subscribers use the subscription service key, while other subscribers use the service key for recharging number. 2) 1: PPS subscribers use service key 1, while other subscribers use the service key for recharging number. 3) Other values: all subscribers use recharging number service. Setting procedure: double click the selected parameter on the interface shown in Fig. 9-13, and make the settings on the pop-up dialogue box. For instance, if you double click the Whether exist emergency call center code option shown in Fig. 9-13, you will see a pop-up dialogue box as shown in Fig. 9-14. Check the radio button before the Whether exist emergency call center code option in the dialogue box. This indicates that there exists an emergency call center code. After the setting, click the <OK> button.
Fig. 9- 14 Set the Whether Exist Emergent Call Center Code Parameter If the emergency call center code exists, set the parameters scheme identifier, Address kind and Central code in the window shown in Fig. 9-13. Otherwise, an prompting message will pop up, as shown in Fig. 9-15.
Page 142 of 273
Fig. 9-15 Emergency Call Center Number Error Message 9.3.3 Number Expansion Variable and TM Control Select Variable control ? Number expansion variable and TM control, and you will see a pop-up interface as shown in Fig. 9-16.
Fig. 9-16 Number Expansion Variable and TM Control Below are the meanings of main parameters in the function: 1. Code number increasing status setting This parameter has three values: 1) 0: only the numbers used prior to number expansion are allowed before the start of expansion. 2) 1: transition period, when the numbers before and after number expansion are both allowed.
Page 143 of 273
3) 2: only the expanded number are allowed after the number expansion. 2. MAP Phase setting: this parameter is used for interconnection with the mobile systems of different versions. 3. TM packet side: the number of bytes each data package contains during transmission. 4. Alarm control of high protocol extension. 5. Alarm control of private extension container Setting procedure: double click the selected parameter on the interface shown in Fig. 9-16, and make the settings on the pop-up dialogue box. For instance, if you double click the Code number increasing status setting parameter in Fig. 9-16, you will see a pop-up dialogue box as shown in figure 9-17. Select the Code number increasing status setting in the dialogue box and then click <OK> .
Fig. 9-17 Code number Increasing Status Setting 9.3.4 Service Variable Control Select Variable control ? Service variable control in the window shown in Fig. 9-1, and you will see a pop-up interface as shown in figure 9-18.
Page 144 of 273
Fig. 9-18 Service Variable Control The parameter area in Fig. 9-18 shows the following parameters. 1. For instance, if you double click the Whether judge the called number for local or toll in GMSC parameter shown in Fig. 9-18, you will see a popup dialogue box as shown in Fig. 9-19. If you select the Whether judge the called number for local or toll in GMSC , and it indicates that GMSC will judge the incoming call dialing mode, the incoming call dialing mode is determined based on the setting of the local long distance area code specified in the mobile number analysis under configuration management, and a voice prompt will be given for the wrong dialing mode.
Page 145 of 273
Fig. 9-19 Whether to Judge the Dialing Mode of the Incoming Call in GMSC 2. If you double click the Mark of not supporting CUG services parameter shown in Fig. 9-18, you will see a pop-up dialogue box as shown in Fig. 920. If you check the radio button before the Mark of not supporting CUG services parameter, CUG services will not be supported.
Fig. 9-20 Mark of Not Supporting CUG Services 3. If you doub le click the Whether send ACM ahead of schedule parameter shown in Fig. 9-18, you will see a pop-up dialogue box as shown in Fig. 9-21. If you check this parameter, an ACM message will be given before ringing.
Fig. 9-21 Whether Send ACM Ahead of Schedule 4. If you double click the Whether have CW indication in ACM shown in Fig. 9-18, you will see a pop-up dialogue box as shown in Fig. 9-22.If you check the radio button in front of the Whether ACM have CW indication in ACM parameter, this indicates ACM will contain a CW indication.
Page 146 of 273
Fig. 9-22 Whether Have CW Indication in ACM If ISUP is the inter-office signaling, deselect Whether send ACM ahead of schedule in the security management variable but select the Whether have CW indication in ACM. If the called is in the local office, reserve and activate the CW service. If this subscriber has an ongoing call, when another call is coming, and you trace No.7 signaling and open the explanation of ACM entity, you are supposed to see a CW indication. However, please be noted, whether this parameter is selected or not will not affect call waiting services, and only decides whether the mark in the ACM is changed. 5. If you double click the Whether play tone when barring income calling parameter shown in Fig. 9-18, you will see a pop-up dialogue box as shown in figure 9-23. If you check the radio button in this box, a tone will be given in the case of incoming call barring.
Fig. 9-23 Whether Play Tone When Barring Income Call
Page 147 of 273
6. If you double click the The rate of barring of income calling parameter, you will see a pop-up dialogue box as shown in Fig. 9-24. After specifying a rate in this dialog box, please click <OK>.
Fig. 9-24 The Rate of Incoming Call Barring Enter this rate when incoming calls are barred. 0 indicates no barring, 1 indicates 10% of the incoming calls are barred, and 10 indicates that 100% of the incoming calls are barred (or complete barring). 7. Double click the Forbid ISUP send calling number in IAM in Fig. 9-18, and a dialog box will pop up, as shown in Fig. 9-25. Check the radio button in this box and then click the <OK> button. When ISUP is making an outgoing call, and the called sends an IAM message, this flag will be determined. In the case of 1, the IAM contains no calling number, or otherwise contains the calling number.
Fig. 9-25 Forbid ISUP Send Calling Number in IAM 8. Double click the CPU load control level 6 parameter in the interface shown in Fig. 9-18, and you will see a pop-up dialogue box as shown in
Page 148 of 273
figure 9-26. After setting the level in this dialogue box, click the <OK> button .
Fig. 9-26 CPU Load Control Level For the settings, the value of a lower le vel should be greater than that of a higher level. So, suppose the first level is 50%, the second level should not be lower than 50%, and the remaining settings follow this rule. Overload protection The program will work out the load of the current system based on the CPU load control level, maximum UB rate control level, message waiting time level, and the maximum control level for the use of CPU by service program, and then get the packet discard policy based on the loss of packet control at the corresponding level, to discard packets. Operations for the maximum UB rate control level, use of ID by session ID, and message waiting time level, are similar to those for CPU load control level. 9. MSC flow control: this parameter is to set whether to have MSC flow control at A-interface or CC; 0 means flow control at A-interface, while 1 indicates flow control at CC. Double click the MSC flow control parameter in the interface shown in Fig. 9-18, and you will see a pop-up dialogue box as shown in Fig. 9-27. Set MSC flow control in this box and then click <OK> .
Page 149 of 273
Fig. 9-27 MSC Flow Control 10. Preferential user flow control: this is used to set whether the CC controls the traffic of preferential subscribers; 0: treat preferential subscribers as ordinary subscribers, and control their flow; 1: impose no limitation on preferential subscribers. Double click the Preferential user flow control, and you will see a pop-up dialogue box as shown in Fig. 9-28. After making the setting in this dialogue box, and then click <OK>.
Fig. 9-28 Preferential User Flow Control 11. Pre-paging: double click the SuppPrePage parameter in the interface shown in Fig. 9-18 and a dialog box will pop up, as shown in Fig. 9-29. Set the SuppPrePage field as 1, and then click the click the <OK> button .
Page 150 of 273
Fig. 9-29 Support Pre-Paging Flag 12. Monitor function: used by CC, TUP, ISUP. This is to set whether to support monitoring and which monitoring function is to be used: 0: no monitoring, 1: local monitoring; 2: calling number monitoring. Whether stop call when fail to monitor: used for CC, TUP, ISUP. This feature will be determined when fail to apply for monitoring. For 1, release the call. Or continue the call. 13. Control mode of OACSU during originating call starting phase: this flag indicates when the calling CC sends an assignment request. Used for CC. 0: start the assignment of service channel after sending SETUP message; 1: control the assignment of service channel after sending CALLPROC message; 2: control the assignment of service channel after receiving StartConv message. 14. Control mode of OACSU during terminating call assignment phase: this flag indicates when the called CC sends an assignment request. Used for CC. The meanings of these values are described below: 0: in previous mode, start the assignment of service channel after receiving CallConform message; 1: control the assignment of service channel after receiving ALERTING message; 2: control the assignment of service channel after receiving CONNECT message. 15. Whether pause call protecting: used for CC, TUP, ISUP. In the case of 1, no call is protected. Otherwise, call protection applies. Call
Page 151 of 273
protection is designed to prevent the disconnection of calls established in switching and backup the data for established calls in the standby system. 16. Whether force not pass: used for ISUP. When the ISUP fails to decode a parameter or message among incoming messages, the Compatible message parameter is combined to decide how to handle this message. 17. Whether be Ericsson version: this is the flag added to previous Yugoslavia versions. It is used in almost all modules. As 1, it is regarded as a Yugoslavia version. For non-Yugoslavia versions, this flag must be set as 0. 18. Whether permit to unstable handover: this indicates whether to permit a MS to hand over in a non-calling state; 0 means not permitted; 1 means permitted. This value is usually 0 . 19. Special calling prefix: this is used for intelligent services under the target network. Currently it is used in VPMN service for called CC. When the called CC sends Setup message to a MS, this flag should be determined. If the calling number begins with this prefix, remove it. For example, if you configure the flag as 60, when the calling number is 601234, the calling number contained in the Setup message will be 1234. 20. R2 sends KB ahead of schedule, whether KB7 or KB6: (if KB is sent properly in the previous message, nothing is affected) if R2 sends KB ahead of schedule, whether it is KB7 or B6: default 0 . 0 for KB6, indicating charged; 1 for KB7, indicating free of charge. 21. Service key used for a fixed subscriber to dial 13800138000: the default value is 2. 22. Whether to inhibit CLIR invoking: used for CC. As required by the mobile company, when a subscriber subscribes to CLIR in the HLR, the calling number will be barred from being displayed according the subscription information. When the subscriber has not subscribed to CLIR in HLR, ZXG10-MSC/VLR should be able to control whether to permit the subscriber to use CLIR. As 0, this flag enables users to decide whether to bar the presentation of calling number. Otherwise, the calling number will be displayed.
Page 152 of 273
23. Send ANN or ANC when SCP plays tone: in the light of existing services, when SCP plays a tone, the calling subscriber will not be charged. So, ANN should be sent when a two-way connection is required. However, according to the SSP equipment specifications of the mobile company, the SSP is required to send ANC in conflict with existing services. To satisfy both requirements, whether to send ANN or ANC is configured in the background. Background variable: Send ANN or ANC when SCP plays tone; meanings: 0-ANN; 1-ANC. Default value: 0 24. IP phone control level: used for TUP. As required by the mobile company, to keep fixed subscribers from dialing 17951, which might increase the load for processing intelligent services, ZXG10-MSC/VLR is expected to restrict fixed subscribers from dialing 17951 to make an outgoing call. The level ranges between 1 and 10, or 10%~100%. 25. Which SCP address fixed subscribers use to dial 13800138000: used for TUP. This is used for fixed prepaid IP service. When a fixed subscriber dials 13800138000, he will use the value of this flag as the service key. 26. Greetings for international roaming subscribers: this flag is used to set whether to send a greeting short message when an international subscriber roams to local area. 1 for sending a welcome message; 0 for not sending such a message. 27. Greetings for domestic roaming subscribers: ditto.
9.4
Selecting Service Control Variable

Among the service control variables, set the SuppPrePage flag as 1, and set the Support call forwarding on no response from pre-paging flag as 0.
Page 153 of 273
10
Log Viewer
In order to better operate and manage ZXG10-MSC/VLR, ZXG10MSC/VLR operation and maintenance system allows users to view logs. Operations by operators are automatically recorded in some way, so that they can be queried in specified cases. Log files are stored at the Server, and you may view these logs from a terminal connected to this Server. Authorized operators are allowed to query, backup or delete these logs.
10.1
View Logs
Click the View logs icon on the floating bar of the ZXG10 maintenance system , to see a pop-up interface as shown in Fig. 10-1.
Fig. 10-1 ZXG10-MSS Log Viewer System The interface of ZXG10-MSS log viewer consists of menu bar, tool bar, panes and status bar. On the tool bar are shortcuts to common menus. The status bar shows the current time. The window consists of two panes: the upper pane shows all operation records, while the lower pane displays details on selected operations.
Page 154 of 273
After selecting an operation record in the upper pane, choose File ? Delete record or click the <Delete> button on the tool bar to delete this record. Select File ? Open log ? Maintenance console or click the Open button on the tool bar, and you will see a pop-up menu shown in Fig. 10-2.
Fig. 10-2 Open Maintenance Log Select the log to be viewed from the Log name pull-down list. Current log refers to the latest operation record. The selected current log files record all the operations by all operators. To view only part of the records, set the searching conditions by operator, operate terminal, module, or operate time. For example, after entering the name of an operator, click the <OK> button to display all the operations of this selected operator. After setting the name of the log to be viewed and the related searching conditions, click the <OK> button to display the contents matching these searching conditions.
Page 155 of 273
10.2
Save or Delete Logs

Select File ? Save as on the interface shown in Fig. 10-1, or click the Save as button on the tool bar, to see a pop-up menu as shown in Fig. 10-3.
Fig. 10-3 Select Saving Mode of Maintenance Console After selecting the original file name from the pull down menu of Log name or entering a new file name, click the <OK> button to save this file as the log displayed on the current window, so that it can be invoked for later query. It is necessary to delete the logs regularly because too many logs occupy the system space, which is a waste of resources. On the interface shown as in Fig. 10-1, select the File ? Delete log ? Maintenance console to pop up the interface as shown in Fig. 10-4.
Fig. 10-4 Delete Log Records Select the log name to be deleted from the pull down menu of Log name , and then click the <OK> button to delete this log.
10.3
Observe Tools
The system tools feature the following functions: 1. Select the order of observation
Page 156 of 273
The log viewer provides not only the function to select the events, but also the function of arranging the events displayed in the window in certain order. On the interface shown in Fig. 10-1, if you select View ? Later in first out, the events will be arranged in the window in a later in first out manner, i.e. newly occurring operation logs will be arranged in the front; On the interface shown in Fig. 10-1, if you select View ? First in first out, the events will be arranged in the window in a First in first out manner, i.e. newly occurring operation logs will be arranged at the back. 2. Other tools On the interface shown in Fig. 10-1, select Options ? First, and the first operation record will be highlighted in the window. On the interface shown in Fig. 10-1, select Options ? Last, and the last operation records will be highlighted in the window. On the interface shown in Fig. 10-1, select Options ? Previous, and the record previous to the current operation record will be highlighted in the window. On the interface shown in Fig. 10-1, select Options ? Next, and the record following the current operation record will be highlighted in the window.. Select the Options ? Font on the interface shown in Fig. 10-1, to select your desired font size and color.
Page 157 of 273
11
11.1
Fault Management System

System Overview
The ZXG10-MSC/VLR fault management system is capable of monitoring the operation status of the entire switch in a centralized way, displaying the rack map of the foreground module, collecting abnormal information on each board, link, database and server in a real time manner in order for operators to make analysis and decisions and thus carry out maintenance and recovery. The information collected by the fault management system includes notification, alarm and alarm recovery information. A notification message indicates irrecoverable operations or exceptions that have occurred but have no effect on the system. An alarm message indicates part of the front-end processor goes wrong. The front-end processor may recover some of the alarms automatically. Once an alarm occurs, the operator should remain calm, analyze the cause and then solve it. When the system is restored to normal, the fault management system will receive an alarm recovery message.
11.1.1
Functions The ZXG10-MSC/VLR fault management system allows you to perform the following functions: 1. Connected to the alarm panel, give audible and visible alarms. 2. Display alarms and notifications on a real time basis. 3. Display the rack map dynamically 4. Provide such functions as MP reset, active /standby switching, board status query. using man-machine commands 5. Query and print the contents of current alarms, history alarms or notifications. 6. Set alarm levels 7. Set environment alarming conditions, enable/disable infrared alarms or clear smog alarms.
Page 158 of 273
8. Mask alarms using alarm codes or board positions 9. Mask notification messages using notification codes. 10. Display information contained in alarm database; manually delete overdue data. 11. Configure remote alarm box as required. 11.1.2 Performance ZXG10-MSC/VLR system features accuracy, real time, flexibility and maintainability. 1. Accuracy The system allows you to accurately locate the faults with the front-end processor, to ensure the information is highly reliable without any missing or false alarm. 2. Real time The system is capable of processing various alarm messages that occur in the foreground of front-end processor in a very fast manner, so as to guarantee the real time synchronization between the foreground and background Servers and Client. 3. Flexibility Capable of self maintenance and expansion, the system meets the technical requirements of service providers. The alarm background works in the Client/Server mode to deliver multi-terminal query. 4. Maintainability It is suitable for offices composed of any combination of MSC/VLR, HLR and SC, or offices involving a single subsystem. It also features clear interfaces and convenient maintenance. It allows users to add new alarm codes and extend to multiple offices for centralized maintenance with ease. 11.1.3 System Architecture The fault management system works in the Client/Server mode with an architecture shown in Fig. 11-1.
Page 159 of 273
Switch foreground
Alarm database Server Background terminal Background terminal
Alarm panel
Fig. 11-1 Architecture of Fault Management System 1. The foreground alarming system of the front-end processor mainly delivers the following functions: collect and process the foreground alarm messages; execute man-machine commands in the background and return results. 2. The server alarm system provides the following functions in the main: information processing, storage and forwarding; control the alarm panel. 3. The client alarm system mainly delivers the following functions: display, query, and print alarm messages; display rack map; execute man-machine commands. 4. Alarm panel: it is a device with indicators and speakers, reporting the running status of the front-end processor..
11.2
11.2.1
Background Interface Operations

Introduction Click the Fault Management icon on the tool bar of the ZXG10MSC/VLR maintenance system, and the main interface of the fault management system will appear, as shown in Fig. 11-2.
Page 160 of 273
Fig. 11-2 Main Interface of the Fault Management System The main interface of the Fault Management System consists of the title bar, main menu bar, toolbar, configuration tree, rack map display window, alarm information display window and status bar. There are two indicators on the status bar; the left indicator shows the status of communication between the server and the foreground. When it shows green, the communication is perfect; when it turns gray, the communication is partly connected; when it is red, the communication is completely interrupted; the right indicator shows the status of communication between the local terminal and the server. When it shows green, the communication is perfect; when it turns gray, the communication is partly connected; when it is red, the communication is completely interrupted 11.2.2 Configuration Tree In the configuration tree, the offices, modules and racks serve as the nodes, so that operators may understand the configurations of the local office at a glance. The configuration information is from the OMCCFG.INI configuration file under the WINNT directory. The billing server is configured as a module.
Page 161 of 273
You can open or close the Configuration tree window using the Configuration tree option in the Setting menu. 11.2.3 Real-time Observation The Real-time observation displays information about alarms, recovery and notification in a real time manner, as shown in Fig. 11-2. Select the Real-time observation tab in the window. 11.2.4 Current Alarms Select the Query Current Alarm tab from the information display window in the main interface (see Fig. 11-2). All the current alarms will be displayed in the information window, as shown in Fig. 11-3.
Fig. 11-3 Current Alarms If you select an office node from the configuration tree, all alarms in the current office will be displayed; if you select a module node from the tree, all alarms at the current module will be displayed; if you select a rack node, all the alarms at the module of the current rack will be displayed. 11.2.5 Rack Map Select a rack node of a module in the configuration tree on the Fault management system main interface (Fig. 11-2), the related rack status will be displayed in a map, as shown in Fig. 11-4.
Page 162 of 273
Fig. 11-4 Rack Map On the top of the rack map, you may find the module number, rack name and voltage. The voltage information will be refreshed dynamically depending on foreground messages. The numbers at the top of the rack map indicate board slots. Each layer (shelf) contains 27 slots. The numbers on the right side of the rack map indicate shelf locations. Each rack has 6 shelves. The color of a board inserted in any slot indicates its running status. The meaning of each color is described below: Red: level 1 alarm Blue: level 2 alarm Green: level 3 alarm White: level 4 alarm Coffee: standby status Dark green: active status
Page 163 of 273
Black: Masked Gray: out of control. Normally, the fault occurs to a board of an upper level. 11.2.6 Man-machine Commands Click a board of the Rack map and a man-machine command dialog box will pop up, showing the alarms that exist on the board. 1. MP board Click the MP board on the rack map (Fig. 11-4), and the man-machine command dialog box will pop up, as shown in Fig. 11-5.
Fig. 11-5 MP Man-Machine Command 1) Changeover button: this button is used for MP active/standby switching (this command only applies to the master MP). 2) Reset button: this button is used to reset and restart the MP. When you reset the master MP successfully, the slave MP will be brought into the active state; when you reset the slave MP successfully, the slave MP will be reset without affecting the master MP. 3) State button: it allows you to query the state of this MP. State information includes power-on time, start time, start completion time,
Page 164 of 273
changeover times, last changeover time and cause, whether to set periodical changeover, and setting parameters. 4) Offline button: this button allows you to put the MP in an offline state (this operation only applies to the slave MP). After the slave MP goes offline, the master MP will not be monitored within 6 minutes, that is, when the master MP powers off or other faults occur, the master MP will not be changed into the master one. After 6 minutes, the offline status will be automatically removed. 5) On-line button: put the in online state. 6) Changeover setting button: click this button to display the hidden Set cyclic changeover dialog box. First set whether to perform the cyclic changeover, and then set the time for cyclic changeover. After the settings, click the <OK> button to confirm and execute the man-machine command. If the master/master MPs run normally, click this button to send the cyclic changeover command to the master MP for regular cyclic changeover. The cycle for the cyclic changeover is 24 hours. The date of cyclic changeover is the day following the input of man-machine command, and the time is a configurable parameter. 2. SYCK board. Click the SYCK board on the rack map (Fig. 11-4), and a dialog box will pop up, as shown in Fig. 11-6.
Page 165 of 273
Fig. 11-6 Man-Machine Command for SYCK Board Below are the functions of each button on the above interface: 1) Changeover button: change active state to standby state . This only applies to active state. 2)State button: return to the active/standby status, clock running mode, if clock pre-warmed, if CKI board existing, if in the manual changeover status, clock reference used, and the status of CKI clock reference.
Page 166 of 273
Fig. 11-7 Query the State Of Sync Clock Board 3) Allow to change Ref. button: it allows SYCK board to change reference. 4) Disallow to change Ref. button: it does not allow SYCK board to change reference. 5) <Select> button: click this button and a dialog box will pop up, as shown in Fig. 11-8.
Page 167 of 273
Fig. 11-8 Select SYCK Clock Reference lCheck the select SYCK running mode option, and you may choose from free running mode, fast tracking mode, tracking mode or holdover (memory) mode etc. lThe Select SYCK clock reference allows to select 4 clock references for the SYCK board. lIf you check the Select CKI clock reference option, you may choose one of the 16 CKI clock references. Click the <OK> button to complete the selection. 3. DSN board, DDSN board, and CPSN board There are three man-machine commands: changeover, reset and state. 4. DSNI, FBI, CFBI, and CKCD (clock drive board) The Changeover man-machine command is available. This command allows you change an active DSNI to an standby DSNI. This command only applies to active boards. 5. DT (digital trunk) board, DTEC echo cancellation board, SDT optical/electric trunk board, MDT16 x digital trunk board, IWF board
Page 168 of 273
Tow man-machine commands: are available: Reset and State. 11.2.7 Query Historical Alarms And Notifications Click the Query historical alarm/notification button in the main interface for the fault management system (Fig. 11-2), and an interface will pop up, as shown in Fig. 11-9.
Fig. 11-9 Setting Query Conditions Follow the steps below to query historical alarms and notifications: 1. Set query conditions Select the scope of query. Global module indicates all modules in the entire exchange office; Module refers to a specific module, as shown in Fig. 11-9. You may select the level for query mode. You are allowed to query either by level or by alarm/notification code. Levels include Levels 1, 2, 3 and 4 as well as notification; alarms and notification codes are listed in detail, as shown in Fig. 11-10.
Page 169 of 273
Fig. 11-10 Select a Query Mode Select begin time and end time of the alarm information to be queried, as shown in Fig. 11-11.
Fig. 11-11 Set the Time Period For Query
Page 170 of 273
2. After setting the query condition, click the <Query> button to show all the information that meets the condition. Click the Hide query condition command and an interface will pop up, as shown in Fig. 11-12.
Fig. 11-12 Displaying Query Results 3. Click <Query> command and a box for query condition setting will appear on the interface, as shown in Fig. 11-9. 4. Click the <Print> button, to put the alarm information in a report, as shown in Fig. 11-13.
Page 171 of 273
Fig. 11-13 Report Printing On the top of the report interface, you will find some shortcut buttons. The icons from the left to the right allow you to do the following respectively: fixed size, actual size, display by page width, to the first page, to the previous page, to next page, to last page, printer setup, start printing, save the report as a file, open the previously saved file, and close this interface. 11.2.8 Query Current Alarms Click the Query Current Alarm command in the main interface for fault management (Fig. 11-2), a dialog box will pop up for you to set the query conditions and display the queried result. Follow the same procedure as the Query Historical Alarm/Notification. 11.2.9 Set Alarm Levels Select the Settings ? Alarm level setting in the main interface for fault management (see Fig. 11-2), and a dialog box will pop up, as shown in Fig. 11-14.
Page 172 of 273
Fig. 11-14 Alarm Level Setting Select an alarm, click the Modify button, and a dialog box will pop up, as shown in Fig. 11-15.
Fig. 11-15 Modify Alarm Level Modify the alarm level, and then click the <OK> button to put the modification into effect and return to the Alarm Level Setting dialog box (Fig. 11-14). Click the <OK> button to confirm the setting. Thus, the level of all alarm information will be changed synchronously. Otherwise, the setting is invalid.
Page 173 of 273
11.2.10
Alarm Mask Settings Operators may Mask alarms as required.. When an alarm is masked, it will longer appear on the alarm panel. Alarms may be masked in two ways: by position and by alarm code. 1. Masking by position Select Settings ? Masking by position in the main interface for the fault management (see Fig. 11-2), and a dialog box will pop up, as shown in Fig. 11-16.
Fig. 11-16 Masking by Position 1) Select the position to be masked. Select module, rack, shelf and slot respectively. 2) Click the <Add> button to add the selected position into the list box on the right side, indicating the specific position to be masked. Repeat Steps (1) and (2), to mask several positions.
Page 174 of 273
3) Select a line in the list box on the right, and click the <Remove> button to cancel the masked position. 4) Click the button <OK> or the <Apply> button, to enable the setting. Otherwise, it will not be active. If the alarm exists in a masked position in the rack map, the slot will turn black. If you have masked a module but still wants to mask another, first, click the <Apply> button first. Otherwise, the previous setting will not take effect when you begin setting another module. 2. Masking by alarm code Select Settings ? Mask by alarm code in the main interface for fault management system (see Fig. 11-2), and a dialog box will pop up, as shown in Fig. 11-17.
Fig. 11-17 Masking by Alarm Code 1) Select modules and alarm codes. 2) Select an alarm code from the left list, and click the <Add> button to add the selected alarm code into the right list box. Likewise, select the
Page 175 of 273
specified alarm code in the list box on the right, and click the <Remove> button to cancel the masking of the alarm. 3) After selection, click the <OK> or the <Apply> button, to apply the masking. Otherwise, you setting will not take effect. If the masked alarm code exists in a single board, the corresponding slot in the rack map will turn black. If you have masked a module but still wants to mask another, first, click the <Apply> button first.. Otherwise, the previous setting will not take effect when you begin setting another module 11.2.11 Notification Masking Operators may mask notifications whenever necessary. Different from alarm masking, notification masking is mainly to mask background display and database writing. During setting, if necessary, you may choose to mask list during database writing (only displayed but not saved) or mask list during display (neither displayed nor saved). On the former occasion, the masked notifications will still be displayed during real-time observation but they will not be written to the database. In the latter case, however, the masked notifications will neither be displayed nor written to the database. Select Settings ? Notification masking in the main interface for fault management (see Fig. 11-2), and a dialog box will pop up, as shown in Fig. 11-18.
Page 176 of 273
Fig. 11-18 Set Notification Masking 1.Select an alarm code from the left list, and click the <Add> button to add the selected alarm code into the right list box Likewise, select the specified alarm code in the list box on the right, and click the <Remove> button to cancel the masking of the alarm. For the same notification code, you are only allowed to choose either Not save, only display or Not save, not display each time for one masking operation. 2. After selection, click the <OK> or the <Apply> button, to confirm the marking.. Otherwise, your setting will not take effect, 11.2.12 Environment Setting Environment alarms will be arise when external operating environment of ZXG10-MSC-VLR system exceeds the specified limit, including temperature alarms, humidity alarms, infrared alarms and smoking alarms. In the main interface for fault management (Fig. 11-2), select Settingenvironment setting and a dialog box will pop up, as shown in Fig. 11-19.
Fig. 11-19 Environment Settings 1. Current environment state

Page 177 of 273
Display the environmental conditions of the ZXG10-MSC/VLR system, such as temperature, humidity, and whether there are infrared and smoke alarms. 2. Set temperature and humidity range When the temperature or humidity of the environment exceeds a specified range, these alarms will arise. After setting, click the <Apply> button to confirm it. 3. Disallow to detect infrared alarm Within this specified time range, no infrared alarm is allowed. Period setting allows you to specify the start and end of each day; Designated means infrared alarm is disabled within a specified time period. This setting will not be take effect until the infrared alarm is enabled. 4. Controlling button Clear smoking alarm: when a smoking alarm occurs somewhere, alarm messages, within a period of two minutes, will be sent to the background continuously every 2 seconds. The alarm box will give alarming sounds nonstop until the system is restored to normal. The smoking alarm cannot be recovered automatically, and you must recover it manually by clicking the Clear smoking alarm button. Allow to detect infrared alarm: this button allows the system to give infrared alarms outside the period specified for disabling infrared alarms Disallow to detect infrared alarm: this button is used to clear the existing infrared alarms, and disable any more infrared alarm. 11.2.13 Set IMSI Authentication Click Settings ? Authentication Setting in the main interface for fault management (Fig. 11-2), and a dialog box will pop up, as shown in Fig. 11-20.
Page 178 of 273
Fig. 11-20 IMSI Authentication Setting IMSI is the international mobile subscriber identifier, which is unique to each subscriber. In order to guarantee the security of IMSI and to make the IMSI less likely to be stolen, try to use TMSI (a 4-digit BCD code) in the air transmission instead. IMSI is not used for authentication unless the TMSI authentication fails. Operators can choose after how many failures in IMSI authentication alarm information will arise in the IMSI authentication setting dialog box. The default value is normally 100.. 1. Set alarm threshold. For each time IMSI is used to authenticate a subscriber, a notification message will occur, if the number of messages reaches the set threshold, an alarm will be given. To validate the new threshold, click the Set alarm threshold button, and a prompting message will be given, indicating the setting is made successfully.. 2. Clear alarm The IMSI encryption failed alarm cannot be recovered automatically. To recover it, click the Clear IMSI authentication alarm button, and a prompt will be given, indicating the alarm is cleared successfully. At this time, the alarm is recovered. The system program will start counting again until the IMSI authentication reaches the threshold for times once again, thus giving an alarm.
Page 179 of 273
11.2.14
Alarm Database Select the Settings ? Database info in the main interface for fault management system (see Fig. 11-2), and a dialog box will pop up, as shown in Fig. 11-21.
Fig. 11-21 Basic Alarm Database Information The Basic info tab (Fig. 11-21) shows the alarm database space used, the oldest data in alarm database, the oldest data in inform database. The Delete data tab (Fig. 11-22) allows you to delete overdue alarms or notification data as the case may be. Below are specific operations:
Page 180 of 273
Fig. 11-22 Delete Data Follow the operations below to delete the data: 1. First select the data type to be deleted, i.e. alarm or inform data . 2. Specify the date for deleting the data . Note: after this operation, the data before this data will be deleted. 3. Click the Delete selected data button, and you will see a prompt message as shown in Fig. 11-23. To delete the selected data, click <Yes>.
Fig. 11-23 Confirm Deletion It will take some time to delete a lot of data, and the deletion progress will appear on the interface. When the operation is completed, a message will be given indicating the operation is completely successfully, as shown in Fig. 11-24.
Fig. 11-24 Deletion Operation Completed Please note that you cannot recover the data deleted after the operation. Thus, be careful with this operation. In addition, after the data are deleted, corresponding operation logs will be obtainable from the log management subsystem. 11.2.15 Other Settings Other settings contain two options: printing alarm immediately and support client-side alarm panel. The first option is used for you to print alarm messages without delay, while the second provides a remote alarm
Page 181 of 273
box, which allows you to keep informed about the alarm messages in good time even if the maintenance personnel is not present in the equipment room. In the main interface for fault management system (Fig. 11-2), select Setting ? Other settings, and you will see a pop-up dialog box shown in Fig. 11-25.
Fig. 11-25 Other Settings To configure a remote alarm box, check Support Client-side Alarm Plate, and then specify an IP address for the alarm box. You are free to configure any IP address for the alarm box so long as this IP address falls in the same network segment as any of the Ips configured with the alarm client PC. When configured with a remote alarm box, the server still can control its own alarm box. The two alarm boxes work independently. 11.2.16 Chang over Billing Server Select Settings ? Changeover billing server in the main interface for fault management and an interface will pop up, as shown in Fig. 11-26. As shown in Fig. 11-26, as no billing server is installed, neither link nor its normal state is shown in the interface; the names of the active and standby computers are displayed on the top of the interface. If changeover is not allowed, the changeover command will turn gray.
Page 182 of 273
Fig. 11-26 changeover of Dual Billing Machines
11.3
Connect Alarm panel

Alarm panel is generally configured with the server and you may also configure it at the far end. Both work independently at the same time. For configuring the remote alarm panel, please refer to Section Other settings. Below is an introduction to how to connect the alarm panel with the server. While installing the server program, the prompting message Whether control alarm box will appear. If you select <Yes> , the server will automatically connect with the alarm panel. The server is connected to the alarm panel in two ways. The server may be connected to the alarm panel via either HUB or dual network cards. In the latter case, we should assign an office ID Y to the alarm panel. If the IP address of the Server is X1.X2.X3.X4, then the IP address of the network card connected with the alarm panel will be X1.X2.Y.X4. In the omccfg.ini under the NT directory, add [AlarmPlate] Office=Y Y refers to the number of offices where the alarm box belongs. As a device used to display the running status of equipment using sound and light, the alarm panel is configured at the server in the alarm
Page 183 of 273
background. Driven by the server, the alarm panel will report alarm messages. There are five indicators and one speaker on the alarm panel. The indicators indicate alarms at Levels 1, 2, 3, 4 and 5 respectively. Level-5 alarm indicator is for the temperature and humidity only. When an indicator flashes, it indicates the occurrence of an alarm at the same level. In the meantime, depending on different alarm levels, the speakers will give different sounds alarms. In the case of no sound, no alarm occurs; in the event of Levels 3, 4 alarms or temperature or humidity alarms, the speakers give one sound; in the case of Level 2 alarms, the speakers will sound on and off; for Level-1 alarms or smoking or infrared alarms arise, the speakers will continuously. The above functions are controlled by the alarm Server. The infrared alarm and smoke alarm will not automatically disappear without using man-machine command.
11.4
Real-time Alarm Text Output

This function is only available in China Motion (Hong Kong) versions. For the purpose of this function, you need to make some manual configurations, involving the following two. You are allowed to set any path name and directory name according to need. 1. Modify configuration file: modify omccfg.ini under ZXG10 directory and add a section as follows: [AlarmToTxt] Path=c: \zxg10 2. You need to create four directories manually, to save Levels 1~4 alarms. These four directories are: C:\zxg10\alarmlevel1 C:\zxg10\alarmlevel2 C:\zxg10\alarmlevel3 C:\zxg10\alarmlevel4
Page 184 of 273
Upon completion of the settings, if a real-time occurs, a text record will be output in the corresponding directory.
11.5
11.5.1
Examples of Fault Management

Query Current Alarms Below is a description of how to query cur rent alarms. 1. Click Query current alarm button in the main interface for fault management. 2. Set the scope of query. You may select either Global module or module. Select Module to specify a specific module number. 3. Set the query mode. To query alarms by severity, select Level; if you want to query alarms by alarm code, select Alarm code. 4. Click the <Query> button, to obtain the results.
11.5.2
Query History Alarms and Notifications Below is a detailed description of the query by historical alarm and by notification. 1. Click the Query historical alarm/notification button on the main interface for fault management. 2. Specify the range of query, select Global module or Module. 3. Set the query mode. Select Level or Alarm and notification code. 4. Specify the time period for your query. 5. Click the <Query> button to obtain the results of query.
Page 185 of 273
12
Diagnosis and Test System

Diagnosis and testing are very important for the routine operation and maintenance of the ZXG10-MSC/VLR system. Maintenance personnel may check the hardware and software of the ZXG10-MSC/VLR system using the diagnosis and test system, to see if they work properly, so as to locate and shoot the faults on a timely basis, and guarantee the normal operations of the system.
12.1
System Overview
ZXG10-MSS/VLR system adopts a structure based on multi-module and fully distributed control. Each module consists of a series of basic units, including T-net, DT, DTMF, MFC, and TONE. The diagnosis and test includes the intra-module test and the inter-module test. The intra-module test is designed mainly to test if the functions of each module unit, links between the units and MPs, voice channels between the units and the switching networks are in good condition; the inter-module test is used to test the communication and voice channels between adjacent modules. The ZXC10-MSS/VLR diagnosis and test system consists of two parts: the foreground and the background, as shown in Fig. 12-1.
Foreground
Server
Client
Client
Fig. 12-1 Architecture o f the Diagnosis and Test System 1.Foreground diagnosis and test process (MP) The MPs are included in the foreground program, to achieve the following functionalities: 1)Testing functions of the units inside each module; 2)Testing links between the units and the MP
Page 186 of 273
3)Testing the voice channel between the units and T network; 4)Testing inter-module communication links and switching voice channels; 5)Receiving man-machine commands and returning test results. 2.Background interface for diagnosis and test For maintenance and operation, ZXG10-MSC/VLR system employs Client/Server LAN networking, where the background of the diagnosis and test system runs at the server and client. Server programs reside at the server for users to carry out routine tests and save the test results; Client programs run at the Client for users to carry out real-time tests, schedule routine tests and query the test results. Below are the functions: 1)Send test commands in a real time manner. 2)Receive, display, print and save test results in a real time manner. 3)Set and cancel routine tests. 4)Send routine test commands (for servers only). 5)Receive and save routine test results (for servers only). 6)Browse and print routine test results. Besides, in terms of test mode, the background diagnosis and test system is divided into intra-module real-time test, intra-module routine test, intermodule real-time test and inter-module routine test.
12.2
Basic Operations
Click the Diagnosis and test icon on the floating menu bar of the ZXG10 MSC/VLR operation and maintenance system, and you will see a pop-up interface, as shown in Fig. 12-2.
Page 187 of 273
Fig. 12-2 ZXG10-MSS Diagnosis and Test System (the Intra-Module RealTime Test) 12.2.1 Intra-module Real-Time Test The interface for intra-module real-time test is shown in Fig. 12-2. The intra-module real-time test is of the following types (subject to the configuration information of the units in the switching module): 1.Trunk unit DT: DT test 2.DTMF receiver: dual tone multi-frequency (DTMF) test. 3.MFC unit: multi-frequency compelled (MFC) transceiver test. 4.Tone unit (TONE): TONE test. 5.Switching network: T-net test 6. Links between the units and the MP: Test the communication links between the basic intra-module units and the MP. 7.Links between the units and T network: Test communication links between the basic intra-module units and T network. Below are detailed operations: 1.Select a module .
Page 188 of 273
Select the module to be tested from the left pane of the interface. 2.Set testing details Based on the actual intro-module unit configurations, the diagnosis and test program will list the test types automatically. Maintenance personnel may select an appropriate type for testing.. For the selected test type, maintenance personnel may choose to test part or all of the units. For instance, select the Link (Unit MP), and the interface shown in Fig. 12-3 will pop up .
Fig. 12-3. Links Between Units and MP: 3.Set test times Set the number of tests for the selected contents. 4.Send test commands Click the Start button shown on the interface in Fig. 12-2, to send test commands. During the testing process, the <Start> button is inactive, but the <Cancel> button becomes active. Click the <Cancel> button to cancel any on-going test. Upon conclusion of the foreground testing process, the test results will be returned to the maintenance terminal. At the same time, the <Cancel> button will be inactive, while the <Start> button will become active. Click the <Result> button to view the test results, shown as in Fig. 12-4.
Page 189 of 273
Fig. 12-4 View the Test Results The test results include basic information about the units, and the error codes that occurred when the units pass through T network and HW. It is not allowed to set test items during the execution of test commands. 12.2.2 Intra-module Routine Test For intra-module routine tests, preset the test time and items. When the predetermined time is up, the diagnosis and test program at the Server will automatically send test commands to the foreground, to test the preset items. Client/Server networking is used for routine tests. Maintenance personnel may set routine tests either at the Server or the Client side, including test type, test unit, and test time. The settings for a routine test are saved in the Server database. The diagnosis and test program on the server will check the routine test settings saved in the database. Once the preset time is up, the server will automatically send a test command to the foreground. After receiving the test command, the foreground will carry out the test, and return the test results to the database on the server.
Page 190 of 273
On the interface shown in Fig. 12-2, click the Intra-module routine test (PA-T) button, and you will see a pop-up interface, as shown in Fig. 12-5.
Fig. 12-5 The Intra-Module Routine Test 1.Set routine tests 1)Select the module number Select the number of a module to be tested in the left pane of the window shown in Fig. 12-5. 2)Set test contents. Select the options for regular testing, and make routine test settings for the unit. For instance, to test the DT unit regularly, select the DT test option, and an interface will pop up, as shown in Fig. 12-6.
Page 191 of 273
Fig. 12-6 Select Test Contents You are allowed to select any unit on the interface for testing. 3)Set the routine test time Set the test period and test time on the interface shown in Fig. 12-5. 4)Save routine test settings. After the above settings, click the <OK> button, to save the routine test settings in the server database; click the <Cancel> button, to cancel the routine test settings for a module at any time. 2.Query routine test settings This allows you to query the routine test settings saved on the Server at the client side, including module No., unit type, test period and test time. Click the <Query> button on the interface shown in Fig. 12-5, and the test contents will appear in the bottom right pane of the window, as shown in Fig. 12-7.
Fig. 12-7 Test Contents 3.View the results of routine test You may view the results of routine test from the terminal at any time. Click the <Result> button on the interface shown in Fig. 12-5, and the
Page 192 of 273
results of the test will appear in the bottom right panel of the window, as shown in Fig. 12-8.
Fig. 12-8 View the Test Results Click the <Print> button on this interface, to print the routine test results immediately. Right click the result window and a pop-up menu will appear. Choose the Delete option from this pop-up menu, to remove the test results of this module from the database. At the same time, the results displayed in the interface will also be cleared. The results of a routine test can be kept in the database of the diagnosis and test system for one month. 12.2.3 Inter-module Real-Time Test Click the Inter-module immediate test (P-R-T) button shown in Fig. 12-2, and a pop-up interface will appear, as shown in Fig. 12-9.
Page 193 of 273
Fig. 12-9 Intra-Module Real-Time Test 1.Set test contents. Select the connections in the module connection map (by clicking any connection). For example, to carry out a test between Module 2 and Module 3, select the connecting line between the two modules. 2.Set test times. Specify test times for the selected contents. 3.Send test commands. Click the <Start> button to start the inter-module test. In the course of testing, clicking the <Cancel> button to cancel any ongoing test. 4.View test results At the end of the foreground inter-module test, click the <Result> button, and the test results will appear on the bottom right pane of the window, as shown in Fig. 12-10.
Page 194 of 273
Fig. 12-10 View Test Results 12.2.4 Inter-module Routine Test Click the Inter-module immediate test (P-R-T) button shown in Fig. 12-2, and a pop-up interface will appear, as shown in Fig. 12-11.
Fig. 12-11 The Inter-Module Routine Test

Page 195 of 273
1.Set routine tests Select a connection (you want to carry out a test between these two modules) on the module connection map, and select test period. After specifying the test time, click the Setting button to save the routine test to the Server database. Click the <Cancel> button to cancel any routine test setting. 2.Query the results of a routine test Click the <Result> button, and you will see a pop-up interface shown in Fig. 12-12. On this interface, select the module to be tested and the test period. Then, the query results will appear in the bottom right pane of the window.
Fig. 12-12 View the Test Results Click the <Print> button on the interface to print the results immediately. Right click the result window and a menu will pop up. Choose the Delete option from this pop-up menu, to remove the test results of this module from the database. At the same time, the results displayed in the interface will also be cleared The results of a routine test can be kept in the database of the diagnosis and test system for one month.
Page 196 of 273
13
13.1
File Management System

System Overview
As a very important part of the equipment, the file management system mainly serves to manage and maintain files of the equipment. The file management system consists of two parts: the foreground and the background, as shown in Fig. 13-1.
MP MP Ethernet MP MP
File management console
Fig. 13-1 Architecture of the File Management System 1.Foreground process of the file system (MP end) It is intended mainly to receive background commands, return operation results, and deliver a file operation interface. 2.The background interface of the file system (WINDOWS NT end) It is intended primarily to display, copy, rename, and delete files..
13.2
Directory Structure
The following default directories will be created during initialization of the file system, in order for users to save information. 1.\DATA: This directory is used to store user data 2.\BILL: This directory is used to store billing data. 3.\CONFIG: This directory is used to store configuration information. 4.\TRACE: This directory is used to store tracing information. 5.\VERSION: This directory is used to store version information.
Page 197 of 273
For easy maintenance, you are allowed to execute at most 200 files using each command. The man-machine commands are designed mainly to read, write, delete and create the files under the above directories.
13.3
Basic Operations
Basic concepts of background interface are introduced as follows: 1.Module number: the node number of local terminal, foreground switching module or NT server. 2.Directory name: you are allowed to operate the current root directory in addition to the five default directories. 3.MP type: the foreground switching module works in a active/standby mode. MP (module processor) is of two types: active and standby. 4.File name: as the name of a file, it supports a connection to subdirectory, as well as wildcards such as * and ?. . Please follow formats or specifications to enter a file name. Click the File Management button will pop up, as shown in Fig. 13-2. on the floating menu, and a menu
Fig. 13-2 ZXG20-MSS File Management System (File List)

Page 198 of 273
The status bar on the interface of background terminal is shown in Fig. 133.
Fig. 13-3 Status Bar The local terminal number appears in the middle of the status bar. There are two indicators on the right of the bar. The left indicator shows the status of the communications between the Server and the foreground, and the right indicator shows the communications between the Server and the local terminal. An green indicator means proper communication; a gray indicator means the communication is partly interrupted; a red indicator means the communication is completely interrupted. 1.File list The File List tab is shown in Fig. 13-2. 1)Module: enter a module number (1~255) in the Module box. 2)MP type: select the MP type (master/slave). 3)Dir: the module number and the directory name combine to determine the file path. The dir pull-down list specifies all the directories of the module you selected. Please select the directory where the file is located. 4)File: enter the file name in the File field . The file name may contain sub-directory information. For example, to list all the files under the directory \data, select data as the directory name, and enter *.* as the file name. 5)Display: after you have entered the module number, directory name and file name, click the Display button to execute the display command. The file system will send the display command to the destination module. Upon receiving the command, the foreground file system on the destination module will execute an operation accordingly and return the results. 6)Result: the returned running results will appear in the Result column, including file name, file size, date and free space. 7)Help: click this button to enter the file management help system.
Page 199 of 273
8)Exit: click this button to exit the file management system. 2.File Copy Click the File copy tab in Fig 13-2, and the interface will pop up, as shown in Fig. 13-4.
Fig. 13-4 File Copy Specify a file in the Source and the Destination fields respectively, and then click the <Copy> button to copy the file. At the end of the copying process, the results will appear in the Result column.. 3.File rename Click the File Rename tab in Fig 13-2, and an interface will pop up, as shown in Fig. 13-5.
Page 200 of 273
Fig. 13-5 File Rename After specifying the Directory, Old name and New name, click the <Rename> button to change the original filename into a new one, and the running result will appear in the Result column. 4.Delete Files Click the File Delete tab in Fig. 13-2, an interface will pop up, as shown in Fig. 13-6.
Page 201 of 273
Fig. 13-6 File Delete Enter the name of a file to be deleted, and click the <Delete> button to delete this file. The result will be shown in the Result column.
13.4
Reference for Exceptions

When you are running the background interface for the file system, exceptions might take place. Possible exceptions and their meanings are defined in Table 13-1. Table 13-1 Exceptions and Their Meanings
Exception
Communication interruption File does not exist
Description
Modules cannot communication with each other properly.. The file required is not in the module. When a file is re-named, and the new file name and the existing file name are the same. The file is read-only. The specified directory is not available. MP active/standby switching occurs during the copying process, and the file fails to be copied. Other module is accessing the target file system The command you have sent returns no information.
File already exists File cannot be deleted Path does not exist.
MP active/standby switching File operation busy Time out error
Page 202 of 273
14
14.1
Version Management System

System Overview
The version management system is designed to update the main processor (MP) and the peripheral-processing units (PP) of ZXG10MSS/VLR system. MPs mainly include MSC, VLR; PP mainly includes DSN, DDSN, DTI, ASIG, IWF etc. The version management system works in a single user mode, i.e. only one user is allowed to perform version management at any time. If a user fails to communicate with the server within 300s, it will be considered that the user has exited. In this case, the server allows other users to carry out version management. MP version management is controlled manually. In other words, users may control the adding, copying or resetting of MP version. The version management of PP is fully automatic, namely, the copying of all PP versions, (the copying of the PP version of master/master MP, synchronization) as well as PP loading are running automatically at the foreground. All you need to do is set the version number being used by the current PP, and the foreground will automatically copy and load the PP version according to the version number. The version management system also provides an interface for you to force the loading of a port. Thus, users only need to select the designated port and the version file to be loaded. To upgrade the MP version using the version management system, you must place the version file of RMX running in the LOGON automatically under c:\Version\ZXG10.RUN instead of ZXG10. Besides, you must reset the version using the version resetting functionality, as you cannot correctly upgrade the version using manual resetting. It is recommended you reset the backup MP before resetting another MP when active/standby switching has occurred. Normally, do not force the loading of a board. Auto loading is recommended Instead.
Page 203 of 273
14.2
Basic Operations
The Version management subsystem is running on the following conditions: 1.Programs of both the foreground and the server are already in operation. 2.Background database has been established. 3.The communication program is in operation. Click the Version Management icon on the floating menu bar of the ZXG10-MSC/VLR operation and maintenance system and you will see a pop-up interface, as shown in Fig. 14-1.
Fig. 14-1 ZXG10-MSS Version Management System 14.2.1 MP Version Management MP version management includes 4 tabs. .They will be described below separately: 1.Version Query
Page 204 of 273
Select the MP version management on the interface shown in Fig. 14-1. Click the <Query> button, and a pop-up menu will appear, as shown in Fig. 14-2.
Page 205 of 273
Fig. 14-2 MP Version Management (Version Query) The History tab mainly allows you to query the version information copied from Server to MP for the most recent times. Select the Module, Start date, Stop time or Version you want to query, and then click the <Query> button to obtain the updates about the corresponding MP version, as shown in Fig. 14-3.
Fig. 14-3 Result of MP Version Result 2.Add a new version
Page 206 of 273
On the interface shown in Fig. 14-2, select the Add tab, as shown in Fig. 14-4.
Fig. 14-4 Add Versions This tab serves mainly to add the MP version files from the Client to the Server. Click the <Browse> button, and a pop-up dialogue box will appear, as shown in Fig. 14-5. In this box, you may open the local version file ZXG10, to add a version.
Fig. 14-5 Opening Version Files Select your desired version file you want to add to the Server. Click the <Open> button, and another interface will pop up, as shown in Fig. 14-6.
Page 207 of 273
Click the <Add> button on this interface and an interface will pop up to display the progress, as shown in Fig. 14-7. After you add the version file, a dialogue box shown in Fig. 14-8 will appear, indicating the file is added successfully.
Fig. 14-6 Add Version After Selecting A Version File
Fig. 14-7 Adding Version
Fig. 14-8 Version Successfully Added 3.Version copy
Page 208 of 273
On the interface shown in 14-2, select the Copy tab, as shown in Fig. 149.
Fig. 14-9 Copy Versions This tab serves mainly to copy MP version from the server terminal to the foreground MP. Check Select version file on server, and all the version numbers on the Server will appear in the editing box. Select the MP (master or slave) version you want to copy. Click the Copy button, to copy the version file corresponding to this version number to \Version on the destination MP, and the new file will be named ZXG10.bak. After a version is reset, the former file ZXG10.OLD will be deleted. In this case, the original version file ZXG10.RUN will be renamed ZXG10.OLD, and the new version file ZXG10.BAK will be renamed ZXG10.RUN. You are allowed to copy only two MP versions at a time, and the copying process is shown in Fig. 14-10.
Page 209 of 273
Fig. 14-10 Version Copy Progress The information of the copied MP version, such as time and version number, and the module number and location of the destination MP, will be copied to the database on the background Server. You may query details about MP loading on the history tab (Fig. 14-2). 4.Version reset On the interface shown in Fig. 14-2, select the Reset tab, as shown in Fig. 14-11.
Fig. 14-11 Reset Version This tab is mainly for you to reset an MP.
Page 210 of 273
After copying an MP version file to an MP, you cannot start this MP as a new MP version so as to replace the version. During resetting, you cannot reset the destination MP unless it contains both the current version file and the new version file. Otherwise, the MP will refuse to execute the reset command . The MP must be reset 3 minutes later than the current time.. When the MP is being reset and restarted, users are not allowed to carry out operations on this MP. Thus, try not to make other operations on this MP. It is recommended to reset the backup MP before resetting another MP following active/standby switching. Select the MP to be reset, and click the <Reset> button, and you will see a pop-up interface, as shown in Fig. 14-12. Set the reset date and time on this pop-up interface, and then click the <OK> button. Another interface will pop up, as shown in Fig. 14-13. Click the <OK> button to start resetting . The system will display the resetting progress, as in Fig. 14-14. The result of reset will be displayed after successful resetting. See Fig. 1415.
Fig. 14-12 Set Reset Time
Fig. 14-13 Version Resetting Confirmation
Page 211 of 273
Fig. 14-14 Version Resetting Progress (1)
Fig. 14-15 Version Resetting Progress (2) 14.2.2 How to Query MP Versions Follow the operation procedure below to query an MP version : 1.Go to the version management system, and open the version management interface. Select MP version management and click the Version shortcut button on the tool bar.
Page 212 of 273
2.Enter your desired Module, Start time, Stop time or Version for query in the History tab. Click the <Query> button to get information about the MP. 14.2.3 How to Add an MP Version Follow the steps below to add an MP: 1.Go to the version management system, and open the version management interface. Select MP version management and click the <Add> shortcut button on the tool bar. 2.Click the <Browse> button in the pop-up interface, to select a local MP version file. Then, click the <Add> button. 3.After the version is added, a message will pop up, indicating the version is added to the server successfully. 14.2.4 How to Copy an MP Version Follow the steps below to copy an MP: 1.After the version is added, copy the version file to the foreground using the MP version copying function. 2.Go to the version management system and open the version management view. Select MP version management and click Copy. 3.Select the number of the version file on the server. Specify the module number and master/slave location and then click Copy. You may copy a maximum of two MP versions at the same time. 4.After the version is copied, a message will pop up, indicating the version file is copied to the foreground successfully. 14.2.5 How to Reset an MP Version Follow the steps below to reset an MP version: 1.After the version is copied, reset the version to run the MP version that has been copied to the foreground. 2.Go to the version management system and open the version management view. Select MP version management and click Reset..
Page 213 of 273
3.Specify the module number and master/slave location and then click Reset. 4.Specify the reset date and time. Reset time must be 3 minutes later than the current time. Click the <OK> button to start resetting. 5.After the resetting, the version running in the foreground is the one that has been reset. 14.2.6 PP version management Select the PP version management on the interface shown in Fig. 14-1, and click the <Query> button. A pop-up menu will appear, as shown in Fig. 14-16. The MP management version of PP consists of six tabs: History, PP query, Add, Setting, Force and Unforce.
Fig. 14-16 The MP (PP) Version Management (Version query)
Page 214 of 273
1.History
Fig. 14-17 MP (PP) Version Management (History) 2.Version query The PP query tab is shown in Fig. 14-18. This tab mainly allows you to query the version copied from the server to PP most recently. Select the Module, Start time, Stop time or Version you want to query, and then click the <Query> button to display the corresponding information about PP version in Version change record list, as shown in Fig. 14-18.
Page 215 of 273
Fig. 14-18 Result of PP Version Query 3.Add a new version On the interface shown in Fig. 14-16, select the Add tab, as shown in Fig. 14-19. This tab mainly serves for you to add the MP version files from the Client to the Server.
Fig. 14-19 MP (PP) Version Management (Add) Select a PP type from the Type pull-down list. Click the Browse button to select the version file you want to copy, and then click the <Add> button.
Page 216 of 273
4.Version setting On the interface shown in Fig. 14-16, select the Setting tab, as shown in Fig. 14-20.
Fig. 14-20 MP (PP) Version Management (Setting ) Select the version number you want to load from the Set version pulldown list, and then click the Set button, to set the selected version as the current PP version. After you specify a PP version number, the background will send the current PP version number to the MP. The MP will then compare the received version number with the existing version number. If the two differ, MP will the request the background Server for the PP version file. In order to avoid such cases where the MP fails to obtain the PP version file from the background Server due to communication errors during the course of receiving, the background will, within 10 minutes after the version is specified, notify the MP to compare versions at an interval of two minutes every two. At the same time, the background server will send version information to the MP every half an hour, to ensure PP version synchronization between the foreground and the background.. After receiving the unit version, the MP will notify the related PP to get reset. After resetting, once it is found the version of PP unit is not consistent with the MP version, the information will be updated automatically. If PP loading fails, the foreground will send an alarm to the background alarm
Page 217 of 273
program. After receiving a PP unit version file, the MP will record such information as unit type, module number, version number, installation time in the background database Server, which you can query using the History tab. 5.Force load On the interface shown in Fig. 14-16, select the Force tab, as shown in Fig. 14-21.
Fig. 14-21 MP (PP) Version Management (Force) This tab mainly serves to force the loading of a designated port. The version specified in the Setting tab generally applies to all the PP ports, but the ports loaded using force are invalid. That is to say, the ports loaded using fore are not subject to Setting. You must click Exit before loading or. To select a port, check the unit type specified in the PP type tab, and select a port. The system will automatically identify the unit type corresponding to this port according to the port number. For the ports that can not be loaded, the system will not display the port type, so as to avoid mis-operations. In Force mode, if the loading fails, the system will report it to the alarm system in addition to indicating the loading failure through a pop-up dialog box.
Page 218 of 273
As Force loading is unique but not generic, it does not represent a unit type; therefore, the specific information on Force loading cannot be recorded in the database Server. The detailed operations are as follows: 1)Select a module number from the Module pull-down menu. 2)Select the destination port number from the Port pull-down list, and query the unit type of this port number on the PP query tab. 3)Click the Browse button, and select the destination version filename in the pop-up dialog box. 4)Make sure that the module No ., port No., PP type and the version filename are all correct, and click the Load button to start the forced loading. 6.Unforce load On the interface shown in Fig. 14-16, select the Unforce tab, as shown in Fig. 14-22.
Fig. 14-22 MP (PP) Version Management (Unforce) This tab serves to unforce the loading of the designated port. The detailed operations are as follows: 1)Specify the module number in the module pull-down list.
Page 219 of 273
2)Select the destination port number from the Port pull-down list, and query the unit type of this port number on the PP query tab. 3)Make sure that the module number, port number and PP type are all correct, and then click the Unforce button to cancel the loading. About 12s later, the system will pop up a dialogue box, indicating the cancellation is successful. If the messages fail to be sent to the foreground due to communication errors, the background will send the message for cancel the loading every 15s within 150s. . If the communication resumes at this time, a message will pop up 12 seconds later, indicating successful load cancellation. Otherwise, this operation will be aborted. 14.2.7 How to Query PP Version History Follow the steps below to query PP version history: 1.Go to the version management system and open the version management view. Select MP version management of PP and click History. Select the History tab and enter the module number. Click <Query>. 2.By adding an setting a PP version, the specified PP version will be listed as a history record. 14.2.8 How to Query a PP Version Follow steps below to query a PP version 1.Go to the version management system and open the version management view. Select MP version management of PP and click PP Query. Select the PP Query tab. 2.Select your desired module number and click Refresh. The PP port No., unit type, physical location, version number, load mode and running status of this module will appear on the interface. 14.2.9 How to Add a PP Version Follow the steps below to add a PP version: 1.Go to the version management system. Select MP version management of PP under the version management view. Click <Add>.
Page 220 of 273
2.Select the PP type to be added. 3.Browse to select a local version file. 4.Click <Add> to add the PP version to the server. 14.2.10 How to Set a PP Version Follow the steps below to set a PP version: 1.Go to the version management system. Select MP version management of PP under the version management view. Click Setting. 2.Select the version for PP unit setting, and click Set. 3.The version number selected is the current version of this PP unit. 14.2.11 How to Force Load of a PP Version Follow the steps below to force the load of a PP version: 1.Go to the version management system. Select MP version management of PP under the version management view. Click Force. 2.Select the module number and the port number to be loaded, and browse to select a local version file. 3.Click Force. 14.2.12 How to Change a PP Version Follow the steps below to change a version: 1.By adding a PP version, add the version to be changed to the server. 2.By setting a PP version, to set your desired version as the current version of this PP.
Page 221 of 273
15
Clock Management System

As a tool kit for developing and debugging the foreground programs, the timer and time management system may run on any background terminal. This system mainly implements the timer management and time management.
Click the Timer management icon on the floating menu bar, and you will see a pop-up interface shown as in Fig. 15-1.
Fig. 15-1 ZXG10-MSS Timer And Time Management System (Time Management)
15.1
Timer Management
The Timer management tab mainly serves to manage all the module timers of the foreground, query MP timer parameters, and modify MP timer name and current interval. The Timer management tab is shown in Fig. 15-2.
Page 222 of 273
Fig. 15-2 Timer Management Select the module number from the Module box, and then click the <Display> button to show the information about the timer of this module. Standard interval means the related timer interval stipulated in GB, and Current interval refers to the interval of the related timer in this system. See Fig. 15-3.
Fig. 15-3 Timer Management Select a module on the interface as shown in figure 15-3, and click the <Modify> button to pop up the interface, as shown in Fig. 15-4. This
Page 223 of 273
interface allows you to modify the timer interval. After modification, click the <OK> button, to display the modified timer interval in the display box. Note that it is not allowed to modify the timer unless you login as ZXG10.
Fig. 15-4 Modify Timer Parameters
15.2
Time Management
Fig. 15-1 shows the Time management tab. On this interface: 1. Display button: click this button, to display the clock of all modules in the system in the display box, including year, month, date, hour, minute, and second, as shown in Fig. 15-5.
Fig. 15-5 Time Administration 2. Synchronize button: if the clock of the modules is out of sync, click the <Synchronize> button, to use the clock of module 2 as the reference to synchronize the clock of other modules.
Page 224 of 273
3. Modify button. select a module on the interface as shown in Fig. 15-5, and click the <Modify> button. An interface will pop up, as shown in Fig. 13-6. You may modify the clock of related modules on the interface.
Fig. 15-6 Modify Clock
15.3
Exceptions and Meanings

The exceptions that might occur during the system operation are listed in Table 15-1. Table 15-1 Exceptions and Their Meanings
Exception
Module No. error Unit No. error The communication between modules is interrupted Inter-module communication overload The intra-module communication is interrupted The intra-module communication between modules is overloaded
Description
The module number selected does not exist. The unit number selected does not exist Modules cannot communication with each other. The inter-module communication load is too heavy Communication failed within a module The communication load is too heavy within a module
Page 225 of 273
16
16.1
Tone Management System

System Overview
The tone system is designed for users to edit and modify the announcements of the ZXG10-MSC/VLR system, providing such functions as tone file selection, tone playing, recording, editing and loading.. The tone system is used mainly for tone loading. During the process, Tone load in the options Choice of tone file and Load tone is used very often. Before loading tones, carry out the following operations (as the case may be) : 1. Insert a tone board to an appropriate lot in the rack. 2. Go to Basic configuration management system. Open the Physical configuration interface and configure an appropriate tone board in the frame. 3. In the Physical configuration interface, select the module number of the tone board, and add tone board configuration in module unit configuration. 4. Select Tone table configuration, and go to the Service tone type edit on tone table tab. Make the following configurations: 1) Select the lot for tone loading. 2) Select the tone subunit in the slot. After modifying, click <OK> to save the changes . At the end of version installation, you will see a sub-directory c:\zxg10\flash.This directory contains various service tone sub-directories. You may install them in turn. 5. Copy the tone file to be loaded to c:\zxg10\ and execute the script of MSC_Tone.sql in the version. 6. Go to the Tone system interface and load tones. Because the 64M tone board is used in V3.0, and all service tones are saved in the flash64.64 file, it is possible to install all service tones at one time.
Page 226 of 273
7. After loading tones, execute the script of MSC_Tone.sql once again. Click the Tone management icon on the floating menu, and you will see a pop-up interface shown as in Fig. 16-1.
Fig. 16-1 ZXG10 Tone System (Select Tone File) As shown in Fig. 16-1, the Tone system interface consists of five tabs: 1. Choice of tone file: this allows you to select a tone file. 2. Tone play: this tab allows you to play tone and change tone contents. 3. Tone record: this allows you to record and play tones etc. 4. Tone edit: this tab is for you to edit tones from various sources and replace the tones contained in the tone files. 5. Tone load: this tab allows you to generate and load tone files.
16.2
Select a Tone File

The Choice of tone file tab is shown in Fig. 16-1. Click the Select tone file button and an interface will pop up, as shown in Fig. 16-2. Click the tone file to be loaded on this interface, and click the <OK> button to create the tone file you may load.
Page 227 of 273
Fig. 16-2 File Choice The tone file of 4M tone board differs from the file of 64M tone board. Please note the difference.
16.3
Tone Play
Select the Tone play tab in Fig. 16-1, as shown in Fig. 16-3.
Fig. 16-3 Tone Playing Below is a description of the items on the interface: 1. Sequence: select the sequence number of tone file. After a tone sequence number is selected, the length and content of the tone on the interface will be updated accordingly.
Page 228 of 273
2. Play: play the tones o f tone files with specified sequence. 3. Skip: in playback mode, this button allows you to stop playing the current tone, and the system will play the next tone automatically; in play mode, the button allows you to play the next tone. 4. Playback: this tab allows you to play the tones one by one from the selected sequence. If a tone does not have any content, play the next tone until you terminate the play manually or the tone is played completely. 5. Stop: stop playing tones. 6. Update: save the changes you made to the current tone. In the case of no current tone, add the sequence number and contents. In this case, no actual tone content is available. First select a tone sequence (0~255), and the content of the corresponding tone will appear in the displa y area. You may modified the tone contents in the display area. Click the Update button to save the changes you made.
16.4
Tone Record
Select the Tone record tab in Fig. 16-1, as shown in Fig. 16-4.
Fig. 16-4 Tone Record Below is a description of the items on this interface:
Page 229 of 273
1. Sequence: after a sequence number for the tone file is selected, the length, status and content of the tone will be updated accordingly and the tone sequence number and the contents of the tones in the Tone play tab will also be updated. 2. Length: show the length of current tone. 3. Status: display the status of the current tone, including normal, empty, new tone and re-recording. 4. Content: display the contents recorded in the current tone. 5. Record. If the current tone has not been recorded, the recorded tone will be used as the current tone. If the current tone has been recorded, the recorded tone will replace the tone specified by the sequence number. 6. Play: if the current tone has not been re-recorded, play the tone in a specified sequence; If the current tone has be re-recorded, play the newly recorded tone. 7. Pause: it is used for recording only. In the pause mode, click this button to continue recording; in record mode, click this button to pause recording. 8. Stop: in recording or pausing status, this button allows you to stop the recording and save the recorded tone as a temp tone file; update the status and contents of current tone; in play status, this button is used to stop playing the tone.. Select the tone sequence number, and the length, status and contents of the current tone will appear on the interface. By recording, you may either add or modify a tone or even delete one tone or all the tones. The recorded tones are not actually saved in the tone file but in the temporary files. To replace the tones with a specified number in the tone file with the recorded tones, create tone files on the Tone load tab.
16.5
Tone Editing
This tab allows you to edit three source tones: newly recorded tones, internal tone data and external wave file. At the end of editing, you may replace the tone with a specified number in the tone file by this tone. Select the Tone edit tab in Fig. 16-5, as shown in Fig. 16-5.
Page 230 of 273
Fig. 16-5 Tone Editing (Newly Recorded Tone) 1. Choice of tone file Check the radio button in front of Newly record and the right part corresponds to the record tab. If no tone is recorded, the Play button is inactive (as shown in Fig. 16-5); if a record has been made, the Play button is active, and the tone edit button is activated, as shown in Fig. 16-6.
Fig. 16-6 Newly Record Interface After Editing Activation Check the Internal tone data option, and on the right side of the interface you will fine the tone interface corresponding to internal tone data, as shown in Fig. 16-7.
Page 231 of 273
Fig. 16-7 Internal Tone Data In Fig. 16-7, you may choose Internal tone data or Newly record. If no tone is recorded, the Newly record option is inactive; if you specify a sequence number to record the tone again, then the option will be activated, as shown in Fig. 16-8.
Fig. 16-8 Newly Record The newly recorded tone here refers to one recorded on the Tone editing tab, i.e., the newly recorded tone corresponding to the tone contained in the tone file with a specified number. After selecting the External wave file, you will be prompted to enter the name of the external tone file, as shown in Fig. 16-9.
Page 232 of 273
Fig. 16-9 Select External Tone File If the external tone file follows the audio format of the ZXG10-MSC/VLR system, on the right side of the interface, you will see the play/record options, as shown in Fig. 16-10. At this time, the Play button is active, and the Tone edit function is activated; on the contrary, this Play button is inactive and the system will return to the Newly record interface (similar to Fig. 16-5).
Fig. 16-10 External Wave File The newly record and external wave files are two sources of external tone data. Once these resources are introduced, the tone edition function will be activated in order for you to record, play or edit tones and use them to replace the tones contained in the tone file. Both are processed in the same manner. Therefore, they are referred to as external tones collectively.
Page 233 of 273
2. Tone play tab Below is a description of the meanings of the items on this interface: 1) Record: record or re-record the external tones. 2) Play: play external tones. 3) Pause: this only applies to record. In pause state, click this button to continue recording; in record state, click this button to pause recording. 4) Stop: in the recording or pause state, this button allows you to save recorded external tone and activate the functionality of tone editing; in the state of play, this button enables you to stop playing tones 3. Internal tone data tab The items on the Internal Tone Data tab have the following meanings respectively: 1) Sequence: this allows you to choose internal tone data, with their sequence numbers ranging from 0 to 255. 2) Internal tone data: it refers to the tone with a specified sequence number contained in the tone file. 3) Newly record: tones corresponding to the current sequence number that are recorded on the tone record page, which are saved in a temporary audio file. 4. Tone edit tab The meanings of the items on the tone edit tab are described as follows: 1) Play: For an internal tone data, if you check Internal tone data on the right pane, the system will play the tone with a specified sequence number; if you select a newly recorded tone from the tone file, the system will play the tone with specified sequence recorded in the Tone play tab; if you select Newly record or External wave file, the system will play the external tone. 2) Stop: stop playing.
Page 234 of 273
3) Start: you may use it to specify the starting time of a tone. You may hold down the left button and drag the mouse or use the left and right arrow keys on the keyboard to move the slide bar. 4) End: you may use it specify the ending time of a tone. You may hold down the left button and drag the mouse or use the left and right arrow keys on the keyboard to move the slide bar. 5) Sequence: you may select a tone sequence to be replaced. 6) Confirm: according to range of tone editing, extract the tone data from the external tone data, or the internal tone data, or the newly recorded tone corresponding to a specified sequence number in the tone file, and replace the tone with the specified sequence number in the tone file. The Replacing here does not mean replacing the tones in the tone file directly, instead, it cannot be actually activated unless the tone data file is created on the Tone load page.
16.6
Tone Load
Tone load allows you to save a tone you modified into a tone file of the ZXG10-MSC/VLR system, and load the tone to the tone unit of ZXG10MSC/VLR system; it allows you to edit the tone, to list the tone details and save them to a text file. The Choice of tone file tab is shown in Fig. 16-11.
Fig. 16-11 Tone Load

Page 235 of 273
Click the File generate button and an interface will pop up, as shown in Fig. 16-12.
Fig. 16-12 System Prompt for the Backup Of Original Tone Files Click the <OK> button and the interface will pop up, as shown in Fig. 1613.
Fig. 16-13 The Dialog Box for Saving Files The default names of tone files are provided according to date, month and year. Click the <Save> button to backup the original tone file, and save the modified tone data to the tone data file of the ZXG10-MSC/VLR system. According to the loading configuration of users, the tone data of the ZXG10-MSC/VLR switching system will be sent to the foreground and then loaded to the TONE unit, so as to change the tones during the operations of system. Click the Tone load button on the interface shown in Fig. 16-11, and the interface will pop up, as shown in Fig. 16-14.
Page 236 of 273
Fig. 16-14 Tone Loading The meaning of each parameter and the functions of each button are as follows: 1. Foreground main control loading module: to reduce data transfer between the foreground and background, when you load it for the first time or have changed any tone data, you must select this module at the bottom of this interface, so that this module can load the tone data to other modules; if the tone data file already exists in the main control module, you only need to specify the main control module correctly, and select the module to be loaded. Then, the main control module will load the data to other modules or subunits. For loading channels, please see Help. 2. Tone board loading mode: select the loading mode for corresponding unit. Serial means loading the tone units in the loaded module one by one; in case of multiple tone units, they can be loaded without affecting the call; parallel load means loading the tone units in the loaded module at the same time, mainly used for batch loading on production site, but serial loading still applies to the loading of multiple tone subunits within the same unit. Tone data are also loaded from the main control module to every other module in a serial manner. Each module loads tones to their internal units independently in a parallel manner. 3. Module: select the module to load the tone.
Page 237 of 273
4. Unit: select the unit to be loaded. If you load this module for the first time, or the tone data of the module where this tone unit needs to be updated, choose to load the MP of this module. 5. Subunit: this is for you to select the subunit to be loaded. 6. =>: select the loading configurations in the box to its left, and click this button to add before or during loading. 7. <=: delete the loading configuration in the box to its right. It is not allowed to delete any configuration during loading; however, you may cancel loading by right clicking the loading status box. 8. Loading status: this shows the loading status of each loading unit. For details about the system status, please see Table 16-1. Right click one of the loading statuses in the display area, and select the Stop option on the pop-up menu to stop the loading the module. If you stop loading the current module, you may discontinue all the following loads. Click Clear on the shortcut menu, to reset the loading status of an unloaded unit. 9. DB refresh: if the data administrator of the ZXG10-MSC/VLR system changes the tone unit configuration, you may click this button to update the optional loading configurations synchronously. 10. Start: click this button to start loading according to the specified loading configurations. In this event, many functions are disabled until the end of loading or loading failure after timeout. 11. Clear: if you want to reload all the loaded units, click this button, to reset the status of all the loaded units. Then, click the <Start> button. 12. Close. Click this button to close the Tone loading interface and return to Tone load tab. 13. Help: click this button to get help for the tone loading.
16.7
How to Make a Tone File

Follow the steps below to make a tone file: 1. Go to the test management interface
Page 238 of 273
2. Select the tone board file to be modified in the Choice of tone file interface; 3. Go to the Tone load tab. Select Batch output tone data, and specify the destination path for saving the output .wav file. For example, c:\tone. 4. Place the tone to be updated or a new tone under c:\tone and save it as tone***.wa v. *** refers to digits, indicating the subscript for this tone. 5. After updating, select the Batch output tone data in the Tone load tab, and specify the destination path as c:\tone. Generally, choose A for the new tone file. 6. Select the tone file newly generated in the tone load tab. By default, the new tone file will be placed under c:\zxg10. 7. Press Alt+shift+backspace in the choice of tone file interface, and the two options local and server will appear. Select local, and you may see the new tone file.
16.8
How to Load 64M Tone File to the Foreground

Follow the steps below to load 64M tone file to the foreground: 1. Copy the file flash64.64 and the corresponding file flash64.dbf to be loaded to the zxg10 directory. 2. Go to the Choice of tone file tab (Fig. 16-1) and select flash64.64 file to be loaded. 3. Go to the Tone Load tab (Fig. 16-11), and select Tone Load. Then, select some or all of the tones depending on your need, and confirm your selection. 4. Go to tone loading page (Fig. 16-14), and select the foreground main control loading module. Select Serial loading as the tone board loading model. Use => to select the MP of main control module and the 64M tone subunit of ASIG board for tone loading (physically configured), and the loading status will appear. Now, the status will be To be loaded. 5. Click the Start button in the Tone loading interface (Fig. 16-14).
Page 239 of 273
6. When a message appears indicating the completion of loading, the tone file is loaded to the foreground. 7. Execute the script file *.sql, and select a slot and subunit and check a service tone type in the subnet through Configuration management/Other data/tone table maintenance/ service type edit on tone board (such as basic tone, PPS, VPMN etc.). Then, the corresponding service tone will be played.
16.9
How to Load 4M Tone File to the Foreground

Follow the steps below to load 4M tone file to the foreground: 1. Copy the file flash.dat and the corresponding file tone.dbf o be loaded to the zxg10 directory. 2. Go to the Choice of tone file tab (Fig. 16-1) and select flash.dat to be loaded.. 3. Go to the Tone Load tab (Fig. 16-11), and select Tone Load. 4. Go to Tone loading page (Fig. 16-14), and select the foreground main control loading module. Select Serial loading as the tone board loading model. Use => to select the MP of main control module and the 4M tone subunit of ASIG board for tone loading (physically configured), and the loading status will appear. Now, the status will be To be loaded. Now, the status will be To be loaded. 5. Click the <Start> button in the Tone loading interface (Fig. 16-14). 6. When a message appears indicating the completion of loading, the tone file is loaded to the foreground. 7. Execute the script file *.sql, and select a slot and subunit and check a service tone type in the subnet through Configuration management/Other data/tone table maintenance/ service type edit on tone board (such as PPS, VPMN basic tone). Then, the corresponding service tone will be played.
Page 240 of 273
16.10
Description of Loading Status

The tone system can display the statuses of loading process. The statuses and meanings are listed in table 16-1. Table 16-1 Loading Statuses And Meanings
Status Description
Indicating the n i itial status where loading is still not started (users have not given the loading command, or the unit is in the queue for loading) Indicating a handshake link with this loading unit is being establishing or the sub-tone unit is erasing Flash. Indicating the handshake link has been established, or the tone sub-unit has been erased, and the tone subunit is being loaded. The loading process will be reported later. Indicating the unit has been successfully loaded. Indicating this unit fails to be loaded, and the cause of this failure has been prompted. Indicating that the user has cancelled loading this unit. Indicating the foreground makes no response for a long time, and the background is timed out.
To be loaded Ready for loading Starting to load Loaded successfully Loading failed Loading is cancelled by users Loading time out
16.11
Description of Error Messages

Possible error messages during tone loading are shown in Table 16-2.
Page 241 of 273
Table 16- 2 List of Errors During Tone Loading

Error message
File operation failure Communication failure Failing to send a request to MP Fails to send data to MP. Failing to send a request to PP Failing to send data to PP. Users stop transmitting. Read/write dual-port RAM error Erasing FLASH MEMORY error FLASH programmed address out of range
Cause
Fail to read/write file Communication interrupted and transmission failed. The attempt to set up a link with MP fails. This might be caused by the interruption of communication with MP or a wrong MP version. It may be caused by the interruption of communications with MP. The attempt to set up a link with PP fails. This might be caused by the interruption of communication with MP or a wrong PP version. It might be caused by the interruption of communications with PP. User cancels loading the unit. Communication between the tone loading program on PP and C50 fails, but they can communicate via the read/write dual-port RAM. It might be caused by other programs, or a failure to properly respond by C50. FLASH ROM is still not erased after a long time. C50 reports that the programmed address of FLASH is out of range. C50 reports that there is an error in FLASH byte program, it might be caused by the error of FLASH, too many times of programs or the quality problem of itself. The tone unit might be in the fault status, or the tone unit is occupied that can not be blocked or this tone unit does not exist. Maybe another tone administration terminal or the foreground is in process of loading. Please wait for a while to run it again. It might be that the user cancels the loading, or the normal loading is almost completed, the transmitting terminal sends the Stop command to the receiving terminal, but the receiver fails to make a correct response to the Stop command. It might be that the user cancels the loading, or when the normal loading is almost completed, the transmitting terminal sends the Stop command to the receiving terminal, but the receiver fails to make a correct response to the Stop command. The background has not received a loading process report from the foreground for a long time, and it is considered that the foreground has failed. Or the loading transmitting terminal or receiving terminal has not received a message from the opposite end for a long time, considering that the opposite end has failed.
Fails to write FLASH
Fails to block tone sources
Loading conflict
Failing to stop MP sending
Failing to stop PP sending
Timeout error
Page 242 of 273
17
17.1
Signaling Trace System

System Overview
Signaling tracing system is a dynamic testing and observation tool, used to observe the signaling between the local office and other offices, as well as the signaling between the individual entities inside the office. The system is composed of three parts: 1.MSC_MAP, VLR_MAP, BSSAP signaling at A interface. 2.CAS. 3.No.7 CCS. The MSC/VLR signaling tracing system includes the background maintenance program, the foreground program as well as MAP and A interface process, as shown in Fig. 17-1.
MAP process
A-interface process
Foreground program
Background maintenance process
Fig. 17-1 Architecture of MSC/VLR Signaling Tracing The logical relationship between the CAS and No.7 tracing system and the whole switching system is shown in Fig. 17-2.
Page 243 of 273
Foreground
Switch background database
Client
MP
Foreground process
Foreground
Fig. 17-2 Architecture of CAS and SS7 Signaling Tracing System 1.Background interface: Based on the background operating system Windows NT, the system displays tracing data, makes database storage, and provides tools for data parsing, analysis and database maintenance. 2.Foreground process Incorporated in the foreground program, the foreground process has the following functions: 1)Receive the background commands to control tracing, and forward tracing messages. 2) Test the links between the foreground and the background processes 3)Provide interface functions to filter signaling and send signaling information to the signaling tracing foreground selectively. Below is a description of the main functions of each part. 1.The MSC/VLR signaling tracing system is mainly to trace and display MSC_MAP signaling, VLR_MAP signaling and SCCP, BSSMAP and DTAP signaling at A interface in a real-time manner, and carries out parsing accordingly. 1)MAP signaling MAP (Mobile Application Part) is a protocol specially designed for GSM system. It transmits messages in an SCCP connectionless manner, used for communications between suc h nodes as MSC, VLR, HLR, EIR and
Page 244 of 273
AUC. In the MSC/VLR system, MAP protocol is capable of the following service types: lLocation registration and cancellation lSupplementary Service Processing l Retrieving user parameter during a call lHandover lUser management lOperation and maintenance lVLR fault recovery lAuthentication lSecurity management lIMEI management. lCAMEL service processing (CAP signaling) Main objective of MSC/VLR signaling trace: to observe the work of MAP and BSSAP signaling between offices and the work of signaling between the individual entities inside an office during commissioning test. The following signaling can be traced and observed: lMobility management lCall handling. lHandover_A (HandOver MSC A) and Handover_B (HandOver MSC B) lSS Invoking Notification lAuthentication. lShort message services lResume Call Handling lIntelligent service (CAMEL Service)
Page 245 of 273
lOther messages 2)BSSMAP signaling at A interface Used between BSS and MSC, A-interface supports the provision of all services to GSM subscribers, and allows for the allocation of radio resources within PLMN, as well as operation and maintenance on these resources. A-interface consists of the following three layers: lPhysical Layer lMTP (Message Transfer Part) and SCCP (Signaling Connection Control Part) lBSSOMAP (Base Sub-station Operation and Application Part) and BSSAP (Base Sub-station Application Part); the latter is subdivided into the following two parts: ? DTAP: it is used to transfer messages relating to MS call control and mobility management. ? BSSMAP: it supports other MS-related procedures (like resource management) between MSC and BSS In MSC/VLR signaling tracing, only the following signaling at A interface is traced: 1)SCCP signaling 2)BSSMAP signaling 3)DTAP signaling includes call service, supplementary service, mobility service, handover and short message. 2.CAS (channel associated signaling) transmits the control signals necessary for voice channel (such as occupation, acknowledgement, disconnection, dialing) using the voice channel itself or a signaling path (channel) permanently connected with the voice channel. The ZXG10-MSC/VLR CAS tracing system serves to observe and record the compelled change of the inter-office channel associated signaling in a
Page 246 of 273
real time, manner so as to provide reliable and visual references for commissioning and debugging. 3.No.7 CCS tracing is mainly to trace the signaling messages on the links, and provide corresponding explanations, so that the maintenance personnel can find out the problems of signaling interworking. There are four message types: MTP, TUP, SCCP, ISUP. MTP test messages can also be traced; in addition, after setting No .7 signaling tracing, the signaling messages discarded at MTP-3 level (except for messages discarded normally) will also appear.
17.2
17.2.1
Basic operations
Interfaces Click the signaling trace icon on the floating bar of the ZXG10MSC/VLR operation and maintenance system, and you will see a pop-up interface as shown in Fig. 17-3.
Fig. 17-3 Signaling Tracing System(Large Toolbar) The interface for the signaling tracing system consists of menu bar, tool bar, windows and status bar.
Page 247 of 273
Major commands for background signaling tracing are found in the menu bar, which is roughly divided into four parts: set/cancel signaling tracing, signaling explanation, data maintenance, and database list rebuilding. We now introduce them in detail. Select View ? Small tool bar in the window shown in Fig. 17-3, and an interface will pop up, as shown in Fig. 17-4.
Fig. 17-4 Signaling Trace System (Small Tool Bar) Meanings of the shortcut buttons in the tool bar are defined below: : Message details. It is used to view the details of the selected signaling message in the current window. : Used to view DB data, and the data flow of the selected signaling message in the current window. : View tracing information : Close current sub -window
: Cancel current tracing
Page 248 of 273
: Delete all the records in the current database : Set MSC_MAP tracing : Set VLR_MAP tracing : Set BSSAP tracing : Set CAS tracing : setss7 tracing : Set No.7 subscriber number tracing In the middle of the status bar is the current terminal number. On the right of the status bar is an indicator, indicating the status of communications between the local terminal and the foreground (MSC or VLR).The indicators appear in three colors: red, gray and green. These colors indicate the three states of communication between local terminal and the foreground respectively. Red means the communication is completely interrupted; gray indicates the communication is partly interrupted and partly normal (applicable to multi-module offices); green indicates the communication is perfectly OK. Reset the cursor on the indicator, and right click it to check the detailed status of communication between local computer and the foreground modules. 17.2.2 Signaling Trace Meanings of Module number and Target cell ID are described below : Module number: ZXG10-MSS works in a fully distributed control mode, and its MSC consists of 1~10 single modules (MPM). During commissioning, these modules are numbered, and the numbers are called module numbers. Target Cell ID: a subscriber may move from one cell to another during his call because he is moving for other reasons. In this case, the original cell of the subscriber is called the source cell, while the cell that this subscriber
Page 249 of 273
moves into is called the target cell. The identifier of the target cell is what we call the target cell ID. 17.2.2.1 MSC_MAP Signaling Tracing This function is used to trace the MAP signaling between MSC and HLR and between MSC and MSC, while the signaling between MSC and VLR is not traced (via internal interface). Click the Signal trace ? MSC_MAP in Fig. 17-3, and you will see a popup interface shown in Fig. 17-5.
Fig. 17-5 Set MSC_MAP Tracing (Trace Settings) Before activating the signaling tracing, you need to set the parameters following the steps below: 1.Set single (some) user signaling tracing parameters To trace the MAP signaling of a single subscriber, you must set necessary tracing conditions in order for the foreground to filter the tracing. For the parameter setting, please refer to Table 17-1.
Page 250 of 273
Table 17-1 Set MAP Signaling Tracing Parameters For Single (Some) Subscriber(s)
Tracing service
Call processing: Short message services Handover_A Handover_B Call transmission service Supplementary service notification Intelligent service User equipment checking BSS+ message
Parameters
MSISDN, module No. MSISDN, IMSI, module No. Target Cell ID, Module No. Target Cell ID, Module No. MSISDN, module No. MSISDN, module No. MSISDN, module No. MSISDN, module No. MSISDN, module No.
1)Trace call processing only In the Tracing mode pane shown in Fig. 17-5, check Single (partial) user option in the Tracing mode box, and check Call handling in the Trace options box. Enter the MSISDN of subscriber (the ISDN number of the called MS) in the Parameters box. The tab Select modules/current setting is shown as in Fig. 17-6. On this page, select the module to be traced, and display the current tracing settings in the Current tracing box. Finally, click the <OK> button on the Trace options tab shown in Fig. 175.
Fig. 17-6 Set MSC-MAP Tracing (Select Modules/Current Setting) On the interface shown in Fig. 17-6, you may view the communication status of each module. In Interrupted state, it indicates the
Page 251 of 273
communication link is disconnected; in Connected state, it indicates the communication in the background is normal. 2)Trace handover-A for some subscribers Handover_A is the signaling handed over to the target Cell designated in another office from the local office. To trace the MAP signaling of the handover_A service, select the Single (partial) user in the Tracing mode box shown in Fig. 17-5, and select handover MSC A from the Trace options box. Enter the ID of the target cell, to which this subscriber will be handed over, in the Parameter box. Select the module number to be traced from the interface shown in Fig. 17-6, and then click the <OK> button shown in Fig. 17-5, and the MAP process will send the handover signaling of this target cell to the signaling tracing foreground, where they will be sorted and then sent to the signaling tracing background. 3)Trace the handover-B for some subscribers Handover_B is the signaling handed over to the target Cell of designated in local office from another office. To trace the MAP signaling of the handover_B service, select the single (partial) user in the tracing mode box shown in Fig. 17-5, and select Handover MSC B from the Trace options box. Enter the ID of the target cell, to which this subscriber will be handed over in the Parameter box. Select the module number to be traced from the interface shown in Fig. 17-6, and then click the <OK> button shown in Fig. 17-5, and the MAP process will send the handover signaling of this target cell to the signaling tracing foreground, where they will be sorted and then sent to the signaling tracing background. 4)Tracing the short message service of a single subscriber To trace the short message service of a single subscriber, select the Single (partial) user in the Tracing mode box shown in Fig. 17-5, and select short message service from the Trace options box. Enter the MSISDN or IMSI (except the VMSC terminated short message service, for which the IMSI is entered) of this subscriber in the parameter box. Select the module to be traced on the interface shown in Fig. 17-6, and then click the <OK> button shown in Fig. 17-5. 5)Tracing the call transmission service of a subscriber
Page 252 of 273
To trace the call transfer service of a single subscriber, select the Single (partial) user in the Tracing mode box shown in Fig. 17-5, and select Call transfer service from the Trace options box. Enter the IMSI of this subscriber in the Parameter box. Select the module to be traced on the interface shown in Fig. 17-6, and then click the <OK> button shown in Fig. 17-5. 6)Tracing the intelligent service (CAP signaling) of a single subscriber To trace the intelligent service of a single subscriber, select the Single (partial) user in the Tracing mode box shown in Fig. 17-5, and select intelligent service from the Trace options box. Enter the IMSI of this user in the Parameter box. Select the module to be traced on the interface shown in Fig. 17-6, and then click the <OK> button shown in Fig. 17-5. CAP signaling is returned between gsmssf and gsmscf for tracing. 2.Trace the signaling of all the subscribers Select the All users in the Tracing mode box shown in Fig. 17-5, and select the service type from the trace options box. Select the module to be traced in the interface shown in Fig. 17-6, and then click the <OK> button shown in Fig. 17-5. The signaling messages of the selected service that occurs in the selected module will be sent to the signaling tracing foreground, where the signaling will be sent to the background interface. 3.Check single subscriber equipment Select the Single (partial) user in the Tracing mode box shown in Fig. 17-5, and select Check IMEI from the trace options box. Enter the IMSI number of this user in the Parameter box. Select the module number to be traced from the interface shown in Fig. 17-6, and then click the <OK> button shown in Fig. 17-5. 4.Trace BSSAP + messages Select the Single (partial) user in the Tracing mode box shown in Fig. 17-5, and select BSSAP + message from the Trace options box. Enter the IMSI number of this user in the Parameter box. Select the module to be traced from the interface shown in Fig. 17-6, and then click the <OK> button shown in Fig. 17-5.
Page 253 of 273
17.2.2.2
VLR-MAP Signaling Trace Click the Signal trace ? VLR_MAP in Fig. 17-3, and you will see a popup interface shown in Fig. 17-7.
Fig. 17-7 Set VLR_MAP Tracing (Trace Options) Before activating signaling trace, you need to set parameters following the steps as below: 1.Tracing the VLR_MAP signaling of single subscriber To trace the MAP signaling of a single subscriber, you must set necessary tracing conditions in order for the foreground to filter the tracing. For parameter settings, refer to Table 17-2.
Page 254 of 273
Table 17-2 Set VLR_MAP Signaling Trace Parameters For Individual Subscriber
Tracing service
Call processing: Supplementary services Mobility management Other messages
Parameters
IMSI and module No
If you choose to trace the VLR_MAP signaling of a single subscriber, you can trace the call processing, supplementary service, mobility management and other messages. Select the Single (partial) user in the Tracing mode box shown in Fig. 17-7, and check one or more options in the Trace options box. Enter the IMSI of this subscriber in the Parameter box. The Select modules/current setting tab is shown in Fig. 17-8. Select the module to be traced in the interface shown in Fig. 17-5, and then click the <OK> button shown in Fig. 8-7.
Fig. 17-8 Set VLR-MAP Tracing (Select Modules/Current Setting) 2. Trace VLR_MAP signaling of all subscribers Select All users from the Tracing mode on the interface shown in Fig. 17-7, and then check a trace option, and enter the parameters. Select the module to be traced from the interface shown in Fig. 17-7, and then click the <OK> button on the interface shown in Fig. 17-6 to start VLR_MAP signaling tracing. The signaling messages of the selected service that occurs in the selected module will be sent to the signaling tracing
Page 255 of 273
foreground, where they are then sent to the background interface The tracing results will be displayed on the VLR_MAP tracing interface. 17.2.2.3 Trace A-Interface Signaling Click Signal trace ? BSSAP in Fig. 17-3, and you will see a pop-up dialog box shown in Fig. 17-9.
Fig. 17-9 Set BSSAP Tracing (Trace Options) The handover_A and handover_B service shown in Fig. 17-9 are different from those in the MSC_MAP signaling tracing. The former includes both the inter-office handover signaling and the intra-office handover signaling. Handover_A indicates a handover, where this BSC serves as the originating party; Handover_B indicates a handover, where this BSC serves as the receiver. To trace a single subscriber, be sure not to select Handover-B. The Select modules/current setting tab is shown in Fig. 17-10.
Page 256 of 273
Fig. 17-10 Set BSSAP Tracing (Select Modules/Current Setting) To trace BSSAP, you must set necessary parameters shown in Table 17-3. Table 17-3 Set Tracing Parameter (3)
Tracing service
Call processing: Supplementary services handover_A Mobility management Short message services BSSMAP
Parameters
MSISDN, module No.
Module No.
1. Trace a single subscriber For individual subscriber tracing via A-interface, you may select one or more of the following services: call processing, supplementary service, handover _A, mobility management and short message service; for DTAP signaling tracing, you need to enter subscriber IMSI and the module number. Enter a module number in the same way you do for MSC-MAP and VLR-MAP. 2.Trace all signaling of all subscribers Select All users in the Tracing mode box shown in Fig. 17-9. The IMSI is not needed in the all user mode, but select the traced services only in the Trace options box, which include call processing, supplementary services, mobility management, handover_A, handover_B, short message service and A interface BSSMAP message. Select the module to be
Page 257 of 273
traced in Fig. 17-10, and then click the <OK> button shown in Fig. 17-9 to start tracing all subscribers of A interface signaling, and the tracing records will be displayed on the interface. 17.2.2.4 CAS Tracing Click the Signal trace ? CAS in Fig. 17-3, and you will see a pop-up interface shown in Fig. 17-11.
Fig. 17-11 Set CAS Tracing Enter the Office direction and Trunk group in the Parameters box, and then click the <Add> button. If the local office is a tandem office, you need to check the trace tandem outgoing trunk circuit option. After entering the Office direction and Trunk group, click the <OK> button. If you select a record from the Current setting box, and click the <Delete> button, you can delete a tracing parameter. The results returned from CAS signaling tracing are shown in Fig. 17-12. By right clicking on the interface, you may change the background color.
Page 258 of 273
Fig. 17-12 CAS Signaling Tracing Results 17.2.2.5 Tracing No. 7 CCS Signaling Select Signal Trace ? No.7 on the interface shown in Fig. 17-3, and you will see a pop-up menu shown in Fig. 17-13. Select Trace one link, Trace two links or Trace by number to trace No.7 CCS signaling .
Fig. 17-13 Select No.7 CCS Signaling Tracing Mode 1.Trace No .7 CCS by Trace one link or Trace two links
Page 259 of 273
Click the Signal trace ? No.7 ? Trace one link in Fig. 17-13, and you will see a pop-up interface shown in Fig. 17-14.
Fig. 17-14 Set No.7 Signaling Tracing Click the Signal trace ? No.7 ? Trace two links in Fig. 17-13, and you will see a pop-up interface shown in Fig. 17-14. 1)Set MTP signaling tracing On the interface shown in Fig. 17-14, select the signaling link number, and select MTP from the Service type pull-down list. Select MTP message or MTP test message (the two options can be checked at the same time) in the MTP setting box, and then click the <OK> button. The results of MTP tracing are shown in Fig. 17-15.
Page 260 of 273
Fig. 17-15 Messages Returned After MTP Tracing Select a record on this interface, and click the shortcut button for message details(this is a button on the small tool bar. Click View ? Large/small tool bar to switch between the large and the small tool bars), or double click the records an a pop-up interface will appear, as shown in Fig. 17-16.
Fig. 17-16 MTP Message Details 2)Set SCCP signaling tracing Select a signaling link number and then SCCP from the Service type pull-down list on the interface shown in Fig. 17-14. Then click the <OK> button. The results of SCCP tracing are shown in Fig. 17-17.
Page 261 of 273
Fig. 17-17 Messages Returned From SCCP Tracing Select a record on this interface, and then click the shortcut button or double click the record, and a pop-up interface will appear, as shown in Fig. 17-18.
Fig. 17-18 SCCP Message Details 3)Set TUP signaling tracing Select a signaling link number and then TUP from the Service type pulldown list on the interface shown in Fig. 17-14. Then click the <OK> button. If the message flow exceeds the limit, you may choose CIC filtering.
Page 262 of 273
The results returned from TUP tracing are shown in Fig. 17-19.
Fig. 17-19 Messages Returned From TUP Tracing Select a record on this interface, and click the shortcut button or double click the record and a pop-up interface will appear, as shown in Fig. 17-20.
Fig. 17-20 TUP Message Details
Page 263 of 273
4)Set ISUP signaling tracing Select a signaling link number and then ISUP from the Service type pull-down list on the interface shown in Fig. 17-14. Then click the <OK> button. If the message flow exceeds the limit, you may choose CIC filtering. The results of ISUP tracing are shown in Fig. 17-21.
Fig. 17-21 Messages Returned from ISUP Tracing Select a record on this interface, and click the shortcut button or double click the record and a pop-up interface will appear, as shown in Fig. 17-22.
Page 264 of 273
Fig. 17-22 ISUP Message Details 2.Trace No .7 CCS by subscriber number Click the Signal trace ? No.7 ? Trace by number in Fig. 17-13, and you will see a pop-up interface shown in Fig. 17-23.
Fig. 17-23 Set TUP/ISUP Tracing On the above interface, select the Number Type, and enter the Subscriber Number, and then click the <OK> button. For example, you enter the subscriber number 7300001, which indicates the calls using a subscriber number ending with 7300001 will be traced. The TUP or ISUP signaling messages returned are shown in Fig. 17-24.
Page 265 of 273
Fig. 17-24 ISUP Messages Returned From Tracing By Numbers Select a record on this interface, and click the shortcut button or double click the record and a pop-up interface similar to Fig. 17-22 will appear.. 17.2.3 View Message Details, Database Data and Tracing information The MSC/VLR signaling trace system allows you to view message details, DB data, and tracing information, which will be introduced separately. 1.View message details Select the desired record on the interface shown in Fig. 17-3, and then select tool ? message details. An interface will pop up, as shown in Fig. 17-25.
Page 266 of 273
Fig. 17-25 Message Analyzing In the left pane of this interface, select a data structure node, and the corresponding data type and data contents will appear in the right. The details of MTP, SCCP, TUP, and ISUP messages of No .7 CCS are shown respectively in Fig. 17-16, 17-18, 17-20 and 17-22. 2.View database data Select View ? Trace data on the interface shown in Fig. 17-3, to view the data flow of the currently selected record in the database. See Fig. 1726.
Fig. 17-26 View Database Data 3.Viewing Tracing Information Select View ? Information on the interface shown in Fig. 17-3, to view the messages being sent from the background programs to the foreground processes, as shown in Fig. 17-27.
Page 267 of 273
Fig. 17-27 Tracing Information 17.2.4 Database Tool If the database is damaged, and the data are corrupted, you may select Signal trace ? DB tool on the interface shown in Fig. 17-3. An interface will pop up, as shown in Fig. 17-28.
Fig. 17-28 DB Tool Notes: 1.After a database is recreated, the data in the original database will be lost.
Page 268 of 273
2.Before creating a table using the DB tool, you must exit the signaling tracing program first. 3.To create a new table , make sure that the files under the original database directory are not read only. 17.2.5 Cancel Tracing, Clear Record, Windows Management and Help Signaling trace system also provides the following operations: 1.Cancel tracing: in Fig. 17-3, select Tool ? Cancel tracing, you may cancel tracing the current tracing window, and the tracing window will turn into a view window; in Fig. 17-3, select Signal trace ? Cancel all trace, to cancel tracing all windows. All the tracing windows will turn into View windows. 2.Clear: clear all the tracing records in the current window. 3.Window management: it provides such functions as windows cascading/tile, icon arrangement, switch between windows, and window closing. Help: this allows you to open help files in the signaling tracing system.
Page 269 of 273
Appendix A Abbreviations
Abbreviation A-interface A3 A5/X A8 ACK ACM AE AoC AoCC AoCI ASE ASIG ASN.1 AuC B-interface BAIC BAOC BCCH BCTL BDT BFBI BHCA BIC-Roam BNET BO BOIC BOIC-exHC BS BSG BSC BSNM BSS BSSAP BSSMAP BSSOMAP BTS C-interface CAI CB CBC CBCH CBK CC CCF CCITT Cct CF CFB CFNRc Full English name A-interface Authentication algorithm A3 Encryption algorithm A5/0-7 Ciphering key generating algorithm A8 ACKnowledgement -Accumulated Call Meter -Address Complete Message Application Entity Advice of Charge Advice of Charge Charging supplementary service Advice of Charge Information supplementary service Application Service Element Analog Signalling Abstract Syntax Notation One Authentication Centre B-interface Barring of All Incoming Calls supplementary service Barring of All Outgoing Calls supplementary service Broadcast Control Channel Back Control Back Digital Trunk Back Fiber Bus Interface Busy Hour Calling Attempt Barring of Incoming Calls when Roaming outside the home PLMN country supplementary service Back Network all Barring of Outgoing call supplementary services Barring of Outgoing International Calls supplementary service Barring of Outgoing International Calls except those directed to the Home PLMN Country supplementary service -Basic Service (group) -Bearer Service Basic Service Group Base Station Controller Back S Network Base Station System Base Station System Application Part Base Station System Management Application Part Base Station System Operation and Maintenance Application Part Base Transceiver Station C-interface Charge Advice Information Cell Broadcast Cell Broadcast Centre Cell Broadcast Channel Clear Back signal -Country Code -Call Control Conditional Call Forwarding The International Telegraph and Telephone Consultative Committee Circuit all Call Forwarding services Call Forwarding on mobile subscriber Busy supplementary service Call Forwarding on mobile subscriber Not Reachable
Page 270 of 273
Abbreviation CFNRy CFU CGC CI CKDR CKI CLI CLIP CLIR CM CMD COLI COLP COLR COMM CONNACK CRC CSM CSPDN CUG CW D-interface DB DCCH DCS1800 DET DISC DL DSN DSNI DTAP DTI DTMF DPC E-interface EC EIR EPROM ETS ETSI F-interface FBI FSM Ftn G-interface G/IW MSC GMSC GRQ GSM GSM MS GSM PLMN GT HANDO HDLC HLC HLR
Full English name supplementary service Call Forwarding on No Reply supplementary service Call Forwarding Unconditional supplementary service Circuit Group Congestion signal -Cell Identity -CUG Index Clock Driver Clock Interface Calling Line Identity Calling Line Identification Presentation supplementary service Calling Line Identification Restriction supplementary service Connection Management CoMmanD COnnected Line Identity COnnected Line identification Presentation supplementary service COnnected Line identification Restriction supplementary service Communication CONNect ACKnowledgement Cyclic Redundancy Check (3 bit) Central Switching Module Circuit Switched Public Data Network Closed User Group supplementary service Call Waiting supplementary service D-interface Data Base Dedicated Control Channel Digital Cellular System at 1800MHz DETach DISConnect Data Link (layer) Digital Switching Network Digital Switching Network Interface Direct Transfer Application Part Digital Trunk Interface Dual Tone Multi-Frequency (signalling) Destination Point Code E-interface Echo Canceller Equipment Identity Register Erasable Programmable Read Only Memory European Telecommunication Standard European Telecommunications Standards Institute F-interface Fiber Bus Interface Forward Setup Message forwarded-to number Gateway/Interworking MSC Gateway Mobile-services Switching Centre General ReQuest message Global System for Mobile Communications GSM Mobile Station GSM Public Land Mobile Network Global Title HANDOver High level Data Link Control High Layer Compatibility Home Location Register
Page 271 of 273
Abbreviation HOLD HPLMN IAM IAI ID IMEI IMSI ISDN ISUP IWF IWMSC IWU Kc Ki L1 L2ML L2R L3 LA LAC LAI LAN LAPB LAPDm LCN LMSI LPLMN MAP MCC MM MMI MNC MO MON MoU MP MPM MPTY MS MSC MSISDN MSM MSRN MT MTP NCC NDC NDUB NE NF NIC NM NMC O&M OMC OMM OPC OS OSI
Full English name Call hold supplementary service Home PLMN Initial Address Message Initial Address Message with Information IDentification/IDentity/Identifier International Mobile station Equipment Identity International Mobile Subscriber Identity Integrated Services Digital Network ISDN User Part (of signalling system No.7) InterWorking Function InterWorking MSC InterWorking Unit Ciphering key Individual subscriber authentication key Layer 1 Layer 2 Management Link Layer 2 Relay Layer 3 Location Area Location Area Code Location Area Identity Local Area Network Link Access Protocol Balanced Link Access Protocol on the Dm channel Local Communication Network Local Mobile Station Identity Local PLMN Mobile Application Part Mobile Country Code Mobility Managem ent Man Machine Interface Mobile Network Code Mobile Originated Monitor Memorandum of Understanding Module Processor MSC Process Module MultiParTY (Multi ParTY)supplementary service Mobile Station Mobile Switching Centre Mobile Station International ISDN Number Message Switching Module Mobile Station Roaming Number Mobile Terminated Message Transfer Part Network (PLMN) Color Code National Destination Code Network Determined User Busy Network Element Network Function Network Independent Clocking Network Management Network Management Centre Operations & Maintenance Operations & Maintenance Centre Operate Maintenance Module Origination Point Code Operating System Open System Interconnection
Page 272 of 273
Abbreviation PCH PCM PEPD PIN PLMN POWER B PSPDN PSM PSTN PW RAND REJ REL REQ RLG RLP RR RSC SACCH SAP SC SCCP SCH SDCCH SIM SME SMEM SMS SMSCB SMS-SC SMS/PP SN SNM SPC SRES SS SSN SS7 STP SYCK TAF TCAP TCH TDMA TE TM TMN TMSI USSD VLR VMSC VPLMN VPM VM
Full English name Paging Channel Pulse Code Modulate Peripheral Environment Parameter Detection Personal Identification Number Public Lands Mobile Network Power B Packet Switched Public Data Network Peripheral Switching Module Public Switched Telephone Network Pass Word RANDom number (used for authentication) REJect (ion) RELease REQuest ReLease Guard signal Radio Link Protocol Radio Resource ReSet Circuit signal Slow Associated Control Channel Service Access Point -Service Centre (used for SMS) -Service Code Signalling Connection Control Part Synchronization Channel Stand-alone Dedicated Control Channel Subscriber Identity Module Short Message Entity Shared Memory Short Message Service Short Message Service Cell Broadcast Short Message Service - Service Centre Short Message Service/Point-to-Point Subscriber Number Switching Network Module Signalling Point Code Signed RESponse (authentication) Supplementary Service Sub-System Number Signalling System No.7 Signalling Transfer Point Sync Clock Terminal Adaptation Function Transaction Capability Application Part Traffic Channel Time Division Multiple Access Terminal Equipment Translate Module Telecommunications Management Network Temporary Mobile Subscriber Identity Unstructured Supplementary Service Data Visitor Location Register Visited MSC Visited PLMN Visitor Peripheral Module Voice Mailbox
Page 273 of 273

Zxg10-Mscvlr (v3.0) Operation Manual (Volume II)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Zxg10-Mscvlr (v3.0) Operation Manual (Volume II)

Uploaded by

Copyright:

Available Formats

ZXG10

ZXG10-MSC/VLR (V3.0) Vol ume II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

User Tracing System

Operation Manual of ZXG10-MSC/VLR Vol. II

MP NT Server User tracing process User tracing client

Fig. 6-1 Logical Relationship During User Tracing 6.1.2 Interfaces

Fig. 6-2 ZXG10-MSS User Tracing System

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Fig. 6-9 Hint Message

Fig. 6-10 Error Message (3)

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Fig. 6-16 Tracing Map with Initialization Completed

Operation Manual of ZXG10-MSC/VLR Vol. II

Fig. 6-18 Query MSC/VLR user Tracing History Information

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Service Observation System

Service observation server

Service observation workbench

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Fig. 7-7 Set Observation Intervals

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Fig. 7-19 Statistics Menu

Fig. 7-20 Deletion Menu

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Fig. 7-29 Obtaining Data from MSC Data Area

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Operation Manual of ZXG10-MSC/VLR Vol. II

Fig. 7-35 Parameter Setting For Reading Data From Files

Operation Manual of ZXG10-MSC/VLR Vol. II