ZTE ZXG10BSS V2 Base Station Subsystem Operation Manual I

ZXG10-BSS (V2)
Base Station Subsystem
Operation Manual I
ZTE CORPORATION
ZXG10-BSS (V2)
Base Station Subsystem
Operation Manual I
Manual Version
Product Version
20040331- R1.1
V2.52
Copyright 2004 ZTE Corporation

All rights reserved.
No part of this documentation may be excerpted, reproduced, translated, annotated or
duplicated, in any form or by any means without the prior written permission of ZTE
Corporation.
ZTE CORPORATION
ZTE Plaza, Keji Road South, Hi-Tech Industrial Park, Nanshan District, Shenzhen, P. R.China
Website: http://www.zte.com.cn
Postcode: 518057
Customer Support Center: (+86755) 26771900
Fax: (+86755) 26770801
Email: support@zte.com.cn
* * * *
S.N.: sjzl20040062
800-9830-9830
FAX: +86-755-26770160
Suggestions and Feedback

To improve the quality of ZTE product documentation and offer better services to our customers, we hope
you can give us your suggestions and comments on our documentation and fax this form to +86-75526770160; or mail to Marketing center 3rd floor ZTE Plaza, Keji Road South, Hi-Tech Industrial Park,
Nanshan District, Shenzhen, P. R. China. Our postcode is 518057.
Document name
ZXG10-BSS (V2) Base Station Subsystem Operation Manual I
Product version
Document version
V2.52
20040331-R1.1
Equipment installation time

Your information
Name
Company
Postcode
Company address
Telephone
E-mail
Presentation: How is information presented? (Introductions, procedures, illustrations, others)
Good
Your evaluation
of this
documentation
Fair
Average
Poor
Bad
Accessibility: Can you find the information you want? (Table of contents, Index, headings,
numbering, others)
Good
Fair
Average
Poor
Bad
Intelligibility: Can you understand it when you find it? (Language, vocabulary, readability, others)
Good
Fair
Presentation:
Your suggestions
for improvement
Accessibility:
of this
documentation
Your other
suggestions on
ZTE product
documentation
Intelligibility:
Average
Poor
Bad
Preface
ZXG10 is a GSM mobile communication system independently developed by ZTE
Corporation. It consists of the ZXG10-MSS Mobile Switching Subsystem and the
ZXG10-BSS Base Station Subsystem. The ZXG10-BSS Base Station Subsystem
provides and manages GSM radio transmission, including the ZXG10-BSC Base
Station Controller, the ZXG10-BTS Base Transceiver Station, and other equipment.
The ZXG10-BSS (V2) Base Station Subsystem consists of the ZXG10-BSC (V2) Base
Station Controller and the ZXG10-BTS Base Transceiver Station. The ZXG10-BTS is
a general term for the ZTE series of base stations. The ZXG10-OMCR (V2) is the
operation & maintenance platform of the ZXG10-BSS (V2) Base Station Subsystem.
About This Manual

ZXG10-BSS (V2) Base Station Subsystem Operation Manual introduces the ZXG10OMCR (V2) in terms of system management and monitoring, methods and examples
of data configuration, alarm management and performance management. It is a
reference manual in guiding users to use ZXG10-OMCR (V2) for the operation &
maintenance of the BSC (V2.0).
Related documentation contains:
ZXG10-BSC (V2) Base Station Controller Guide to Documentation
ZXG10-BSC (V2) Base Station Controller Technical Manual
ZXG10-BSC (V2) Base Station Controller Hardware Manual
ZXG10-BSC (V2) Base Station Controller Installation Manual (Hardware)
ZXG10-BSC (V2) Base Station Controller Installation Manual (Software)
ZXG10-BSC (V2) Base Station Controller Maintenance Manual
ZXG10-BSS (V2) Base Station Subsystem Command Manual
ZXG10-BSS (V2) Base Station Subsystem Man-Machine Interface Manual
How to Use This Manual
Chapter 1 Operation Safety describes the precautions and guidelines.

Chapter 2 Configuration Management introduces the configuration flow, logic
structure of configuration data. It also tells the reader how to make the simplest data
configuration, and describes in detail the advanced data configuration, including how
to configure different sites, external cells, relative cells, frequency hopping, EasyWay,
sub-multiplexing, O&M LAPD, power-down bypass and GPRS data. Describes how to
configure the software version via software loading and how to configure
blocking/unblocking operations via dynamic data management.
Chapter 3 Fault Management introduces display and management of alarms, trunk
node alarm management, BSC environment alarm management, BSC alarm rule
management, man-machine operations of BSC boards and test management.
Chapter 4 Performance Management introduces report creation and configuration,
report customizations and automatic report creation, measurement job management,
observation job management, signaling tracing and tracing invoke.
Chapter 5 System Management and Monitoring is about user management, grant,
user Wizard creation and cascading user management. It introduces how to view the
users operation log, monitor database tables and table space and back up database, and
how to send man-machine commands, send commands from files one by one and send
commands in big transaction mode.
Appendix A Abbreviations lists the abbreviations used in this manual.
Appendix B Index is an indexing system of the definitions and terms used in this
manual.
Conventions
1.
Notational convention
Angular brackets <and> identify names of keys and buttons, and the
information typed by an operator from a terminal
Square brackets [and] indicate a man-machine interface, menu item, data list
or field name. The symbol separates a multi-level menu, e.g., [File
New Folder] indicates the [Folder] menu item under the [New] submenu of
the menu [File].
2.
Keyboard Operation Convention
Format
Characters
within
Description
angular
Indicate a key or button name, e.g., <Enter>, <Tab>,
brackets
<Backspace>, and <a>
<Key 1+Key 2>
Press Key 1 and Key 2 at the same time.
<Key 1, Key 2>
Press Key1 first. Then release Key 1 and press Key 2
3.
Mouse Operation Convention

Format
Click
Description
Refers to clicking the primary mouse button (usually the left
mouse button) once
Double-click
Refers to quickly clicking the primary mouse button (usually the

left mouse button) twice
Right-click
Refers to clicking the secondary mouse button (usually the right

mouse button) once.
Drag
Refers to pressing and holding a mouse button and move the

mouse
4.
Danger, Warning, Caution and Note Statements

Danger,
Warning,
Caution and
Note statements
are used throughout this manual to emphasize important and critical

information. You must read these statements to help ensure safety and to prevent
product damage. The statements are defined below.
Danger:
Indicates an imminently hazardous situation which, if not avoided, will result in death
or serious injury. This signal word is to be limited to the most extreme situations.
Warning:
Indicates a potentially hazardous situation which, if not avoided, could result in death
or serious injury.
Caution:
Indicates a potentially hazardous situation which, if not avoided, could result in minor
or moderate injury. It may also be used to alert against unsafe practices.
Note:
A Note statement is used to notify people of installation, operation, or maintenance
information that is important, but not hazard-related.
Tips:
Indicates a suggestion or hint to make things easier or more productive for the reader
Statement: The actual product may differ from what is described in this
manual due to frequent update of ZTE products and fast development of
technologies. Please contact the local ZTE office for the latest updating
information of the product.
Contents
1 Operation Safety...........................................................................................................................................1
1.1 On-site Operation Descriptions ...............................................................................................................1
1.2 Usage Guide to On-site Version Functions .............................................................................................2
2 Configuration Management.........................................................................................................................1
2.1 Overview..................................................................................................................................................1
2.2 BSC Data Configuration (Basic Part)......................................................................................................2
2.2.1 Configuration Flow...................................................................................................................2
2.2.2 Data Configuration...................................................................................................................8
2.3 BSC Data Configuration (Advanced Part)............................................................................................32
2.3.1 Configuring the BTS1.0 and BTS1.0 (A) Sites......................................................................32
2.3.2 Configuring the BTS2.0 Site..................................................................................................37
2.3.3 Configuring the MB and EMB Sites......................................................................................45
2.3.4 Configuring the BS21 Site......................................................................................................47
2.3.5 Configuring the BS30 Site......................................................................................................49
2.3.6 Configuring the BS30 (V1.2) Site..........................................................................................51
2.3.7 Configuring the Cascading Site..............................................................................................55
2.3.8 Configuring the O&M LAPD of a Site..................................................................................59
2.3.9 Configuring the Site with Designated Multiplexing Mode....................................................61
2.3.10 Configuring the Site of Power-off Bypass...........................................................................63
2.3.11 Configuring the 80W Site.....................................................................................................65
2.3.12 Configure the Easy Way ......................................................................................................67
2.3.13 Configuring the Sub-multiplexing.......................................................................................69
2.3.14 Configuring the CBC............................................................................................................72
-i-
2.3.15 Configuring the Super Large Size Cell ...............................................................................75

2.3.16 Configuring the Related Cell................................................................................................79
2.3.17 Configuring the Adjacent Cell Handover and Reselection..................................................81
2.3.18 Configuring the External Cell..............................................................................................83
2.3.19 Configuring the Frequency Hopping....................................................................................85
2.3.20 Configuring the GPRS Data.................................................................................................88
2.3.21 Exporting the Configuration Data........................................................................................97
2.4 Wireless Resources Management..........................................................................................................99
2.4.1 Modifying the BSC.................................................................................................................99
2.4.2 Modifying the Parameters of the Logical Site.....................................................................103
2.4.3 Modifying the Cell Parameters.............................................................................................105
2.4.4 Modifying the Power Control...............................................................................................107
2.4.5 Modifying the Handover Control.........................................................................................109
2.5 Loading the Software...........................................................................................................................111
2.5.1 Overview of Software Loading Flow...................................................................................111
2.5.2 Selecting the Software Version.............................................................................................114
2.5.3 Storing the Software into the Database................................................................................118
2.5.4 Setting General Software......................................................................................................123
2.5.5 Loading General Software....................................................................................................126
2.5.6 Setting the Board Software...................................................................................................128
2.5.7 Loading the Board Software.................................................................................................135
2.5.8 Setting the Software Version of the Physical Site................................................................138
2.5.9 Loading the Software Version of the Physical Site..............................................................141
2.5.10 Viewing the Foreground Running Version.........................................................................144
2.5.11 Handling of FAQ in Software Loading..............................................................................146
2.6 Dynamic Data Management................................................................................................................147
2.6.1 Overview...............................................................................................................................147
-ii-
2.6.2 Querying the Dynamic Properties of the BSC.....................................................................147

2.6.3 Automatically Obtaining or Updating the Status.................................................................150
2.6.4 Blocking/Unblocking...........................................................................................................151
2.6.5 Querying the Status of the A-interface Timeslot..................................................................153
2.6.6 Performing Circuit Installation/Uninstallation of PCM.......................................................155
2.6.7 Querying the Status of the Abis-Interface Channel.............................................................156
2.6.8 Querying the N7Link Status.................................................................................................158
2.6.9 Activating /Deactivating the N7Link...................................................................................159
2.6.10 Performing the Blocking/Unblocking/Reset/Signaling Reset/Status Query of BVC........160
2.6.11 Querying the Channel Statistics of the Cell.......................................................................161
2.6.12 Querying the Channel Statistics of the Module.................................................................164
2.6.13 Querying the Instance Type of the Module........................................................................167
2.6.14 Setting the Foreground Switch Parameters........................................................................168
2.6.15 Querying the FUC Control Level of the Peripheral Module.............................................170
2.6.16 Ending the FUC Control of the Peripheral Module...........................................................173
2.6.17 Setting the FUC Control Bitmap of the Peripheral Module..............................................175
2.6.18 Performing Global Reset for Base Station.........................................................................178
2.6.19 Troubleshooting Dynamic Data Management...................................................................179
3 Fault Management........................................................................................................................................1
3.1 Overview..................................................................................................................................................1
3.2 Display and Management of Alarm.........................................................................................................3
3.2.1 Performing the Conditional Alarm Query................................................................................5
3.2.2 Viewing the Current Alarms of a Site......................................................................................9
3.2.3 Viewing the Current Alarms of a Board.................................................................................13
3.2.4 Viewing the Notification of No Traffic in the Cell from the Base Station............................15
3.2.5 Querying the History Alarms of a Board...............................................................................18
3.2.6 Viewing the History Alarms after Dump................................................................................21
-iii-
3.2.7 Statisticizing the High-frequency Alarms..............................................................................23

3.2.8 Viewing the Relevant Information of a Correlated Alarm.....................................................27
3.2.9 Acknowledging the Alarm......................................................................................................29
3.2.10 Clearing the Alarm Manually...............................................................................................31
3.2.11 Acknowledging the Notification...........................................................................................33
3.2.12 Dumping the Current Important Alarms..............................................................................35
3.2.13 Dumping the History Alarms...............................................................................................36
3.2.14 Setting the Auto Periodic Dump of Alarm Data ..................................................................37
3.2.15 Customizing the Alarm Solution and Cause........................................................................39
3.2.16 Suppressing the Alarm Display............................................................................................41
3.2.17 Redefining the Alarm Class..................................................................................................42
3.2.18 Showing the Important Alarms in Correlated Alarms..........................................................43
3.2.19 Generating a New Alarm after an Alarm Occurs a Certain Times.......................................44
3.2.20 Compressing Class 1 Alarms................................................................................................45
3.2.21 Modifying the Alarm Display Mode....................................................................................46
3.2.22 Customizing the Item Display of the Alarm List.................................................................48
3.3 Trunk Node Alarm Management...........................................................................................................49
3.3.1 Customizing the Trunk Node Alarms of a Rack at a Site......................................................50
3.3.2 Modifying the Trunk Node Template.....................................................................................53
3.3.3 Deleting the Trunk Node Template........................................................................................55
3.3.4 Setting the Level Mode of the Trunk Node............................................................................57
3.4 BSC Environment Alarm Management.................................................................................................59
3.4.1 Setting the Temperature/Humidity Parameters......................................................................59
3.4.2 Setting the Infrared Alarm Parameter.....................................................................................61
3.5 BSC Alarm Rule Management...............................................................................................................63
3.5.1 Overview.................................................................................................................................63
3.5.2 Filtering Rule Management....................................................................................................63
-iv-
3.5.3 Reclassification Rule Management........................................................................................71

3.5.4 Correlation Rule.....................................................................................................................79
3.6 Man-machine Operations of BSC Boards.............................................................................................94
3.6.1 Viewing the Master/Slave Status of the Board.......................................................................95
3.6.2 Viewing the Running Status of the Board..............................................................................97
3.6.3 Resetting the BSC Board........................................................................................................99
3.6.4 Executing the Master/Slave Board Changeover..................................................................101
3.6.5 Setting the Periodic Changeover for MP..............................................................................103
3.6.6 Executing the Offline Operation for MP..............................................................................105
3.6.7 Setting the Clock Reference of SYCK.................................................................................107
3.6.8 Setting the Clock Reference of CKI.....................................................................................110
3.6.9 Setting the Clock Mode of SYCK........................................................................................112
3.6.10 Setting Permitting the SYCK Changeover.........................................................................114
3.6.11 Resetting a Site Remotely...................................................................................................116
3.6.12 Resetting the BTS Board Remotely...................................................................................118
3.7 SMS Alarm Forward Management......................................................................................................120
3.7.1 Enabling the Alarm Forward Function of the SMS Server .................................................121
3.7.2 Disabling the SMS Alarm Forward Function.......................................................................123
3.7.3 Testing the MS Status...........................................................................................................125
3.7.4 Enabling the MS Module......................................................................................................126
3.7.5 Disabling the MS Module....................................................................................................127
3.7.6 Query the Number of the Short Message Center ................................................................128
3.7.7 Setting the Number of the Short Message Center................................................................129
3.7.8 Querying MS User information ...........................................................................................130
3.7.9 Create an MS User................................................................................................................132
3.7.10 Modifying the MS User Information.................................................................................133
3.7.11 Delete an MS User..............................................................................................................134
-v-
3.7.12 Querying All the Forward Rule Information .....................................................................135

3.7.13 Creating the Forward Rule.................................................................................................137
3.7.14 Creating a New Rule According to the Original Rule.......................................................140
3.7.15 Querying All the Forward Rule Information .....................................................................142
3.7.16 Deleting the Forward Rule Information ............................................................................144
3.7.17 Querying the Short Message Format of All the Users.......................................................145
3.7.18 Customizing the Short Message Format ...........................................................................147
3.8 Test Management.................................................................................................................................149
3.8.1 Conducting the Instant Test of Units and Multiple Units (Munit).......................................150
3.8.2 Conducting the Instant Test of the Link...............................................................................153
3.8.3 Conducting the Instant Test for E1.......................................................................................155
3.8.4 Setting the Periodic Scheduled Test.....................................................................................157
3.8.5 Suspending a Scheduled Test ..............................................................................................161
3.8.6 Restarting a Scheduled Test .................................................................................................163
3.8.7 Deleting a Scheduled Test....................................................................................................165
3.8.8 Switching the Test Mode......................................................................................................167
3.8.9 Viewing the Details of Test Results......................................................................................168
3.8.10 Re-obtaining the Test Item.................................................................................................170
3.8.11 Querying the Test Results...................................................................................................171
3.8.12 Deleting a Test Result.........................................................................................................173
-vi-
List of Figures
Fig. 2.2-1 Initial Configuration Flow ...........................................................................................................3
Fig. 2.2-2 Modification Configuration Flow ...............................................................................................4
Fig. 2.2-3 Incremental Configuration (1)......................................................................................................5
Fig. 2.2-4 Incremental Configuration (2) .....................................................................................................5
Fig. 2.2-5 Incremental Configuration (3) .....................................................................................................6
Fig. 2.2-6 Logic Structure of Data Configuration........................................................................................6
Fig. 2.2-7 Start the Integrated Configuration Management..........................................................................9
Fig. 2.2-8 Select Initial Configuration..........................................................................................................9
Fig. 2.2-9 Create a Configuration Script ...................................................................................................10
Fig. 2.2-10 Configure the MSC Equipment................................................................................................10
Fig. 2.2-11 Configure the BSC Parameters ................................................................................................11
Fig. 2.2-12 BSC Equipment Node..............................................................................................................12
Fig. 2.2-13 BSC Rack Configuration .........................................................................................................12
Fig. 2.2-14 BSC Rack ................................................................................................................................13
Fig. 2.2-15 BSC Shelf Configuration.........................................................................................................14
Fig. 2.2-16 BATC Shelf Configuration ......................................................................................................14
Fig. 2.2-17 Add A BSC Board....................................................................................................................15
Fig. 2.2-18 Configure the DRT Board .......................................................................................................15
Fig. 2.2-19 Configure the TIC Board with Abis Interface..........................................................................16
Fig. 2.2-20 Configure the TIC Board of A Interface..................................................................................17
Fig. 2.2-21 Configure the MTP Board........................................................................................................18
Fig. 2.2-22 Configure the BIPP..................................................................................................................18
Fig. 2.2-23 Configure the Physical Site - Base Station Parameters...........................................................19
-i-
Fig. 2.2-24 Configure the Physical Site - Initialization Panel ...................................................................20

Fig. 2.2-25 Configure the Physical Site - BIE Panel Configuration..........................................................20
Fig. 2.2-26 Configure the Physical Site - Rack View ................................................................................21
Fig. 2.2-27 Configure Physical Sites - Combiners and Dividers of Tru....................................................22
Fig. 2.2-28 Configure the Radio BSC - Menu Option................................................................................22
Fig. 2.2-29 Configure the Radio BSC - BSC Parameters...........................................................................23
Fig. 2.2-30 Configure Radio Sites - Menu Option.....................................................................................23
Fig. 2.2-31 Configure Radio Sites - No......................................................................................................24
Fig. 2.2-32 Configure Radio Sites - Menu Option 2 .................................................................................24
Fig. 2.2-33 Configure Radio Sites - No. 2 .................................................................................................25
Fig. 2.2-34 Configure Radio Sites - Parameter Display.............................................................................25
Fig. 2.2-35 Configure Radio Sites - Logic Site Node................................................................................26
Fig. 2.2-36 Configure Radio Cells - Menu Option.....................................................................................26
Fig. 2.2-37 Configure Radio Cells - Cell Parameters.................................................................................27
Fig. 2.2-38 Configure Carrier Frequency - Menu Option..........................................................................28
Fig. 2.2-39 Configure Carrier Frequency - Parameter Configuration........................................................28
Fig. 2.2-40 Save File (1) ............................................................................................................................29
Fig. 2.2-41 Save File (2) ............................................................................................................................29
Fig. 2.2-42 Save File (3) ............................................................................................................................29
Fig. 2.2-43 Generate Configuration Command (1)....................................................................................30
Fig. 2.3-46 Configure the BTS1.2 - Base Station Parameters....................................................................32
Fig. 2.3-47 Configure the BTSV1.0 (A) - Initialization Panel ..................................................................33
Fig. 2.3-48 Configure the BTSV1.0 (A) - BIE Panel Configuration.........................................................34
Fig. 2.3-49 Configure the BTSV1.0 (A) - Rack View ...............................................................................34
Fig. 2.3-50 Configure the BTSV1.0 (A) - [Add Rack] Menu....................................................................35
-ii-
Fig. 2.3-51 Configure the BTSV1.0 (A) - [Add Rack] Dialog Box ..........................................................35
Fig. 2.3-52 Configure the BTS1.2 - Combiners and Dividers of Tru.........................................................36
Fig. 2.3-53 Configure the BTS2.0 - Base Station Parameters....................................................................37
Fig. 2.3-54 Configure the BTS2.0 - Initialization Panel ...........................................................................38
Fig. 2.3-55 Configure the BTS2.0 - CMM Configuration.........................................................................38
Fig. 2.3-56 Configure the BTS2.0 - PCM List...........................................................................................39
Fig. 2.3-57 Configure the BTS2.0 - BTS2.0 Node Generation..................................................................40
Fig. 2.3-58 Configure the BTS2.0 - BTS2.0 Rack Generation..................................................................40
Fig. 2.3-59 Configure the BTS2.0 - [Add Rack] Menu .............................................................................41
Fig. 2.3-60 Configure the BTS2.0 - [Add BTS2.0 Assistant Rack] ..........................................................42
Fig. 2.3-61 Configure the BTS2.0 - Configuration of PCM of B TS2.0 Assistant Rack...........................42
Fig. 2.3-62 Configure the BTS2.0 - CDU Configuration...........................................................................43
Fig. 2.3-63 Configure the BTS2.0 - TRM Configuration...........................................................................44
Fig. 2.3-64 Configure the BTS2.0 - CDU Properties Display....................................................................44
Fig. 2.3-65 Configure the MB - Site Properties..........................................................................................45
Fig. 2.3-66 Configure the MB - SCU Configuration..................................................................................46
Fig. 2.3-67 Configure the MB - Rack view................................................................................................46
Fig. 2.3-68 BS21 Rack View .....................................................................................................................48
Fig. 2.3-69 Configure the BS30 - Base Station Properties.........................................................................49
Fig. 2.3-70 Configure the BS30 - CMM Panel Configuration...................................................................50
Fig. 2.3-71 Configure the BS30 - Rack view.............................................................................................50
Fig. 2.3-72 Configure the BS30 (V1.2) - Base Station Properties.............................................................51
Fig. 2.3-73 Configure the BS30 (V1.2) - CMM Panel Configuration.......................................................52
Fig. 2.3-74 Configure the BS30 (V1.2) - Rack view..................................................................................53
Fig. 2.3-75 Configure the BS30 (V1.2) TRM Panel................................................................................53
Fig. 2.3-76 Configure the Cascading Site - Add BTS ...............................................................................55
Fig. 2.3-77 Configure the Cascading Site - Site Properties Configuration ...............................................56
-iii-
Fig. 2.3-78 Configure the Cascading Site - Rack Configuration ..............................................................56

Fig. 2.3-79 Configure the Cascading Site - Select the PCM Connection Type.........................................57
Fig. 2.3-80 Configure the Cascading Site - Select the PCM......................................................................57
Fig. 2.3-81 Configure the Cascading Site - Cascading Site Generation....................................................58
Fig. 2.3-82 Configure the O&M LAPD - Site Properties...........................................................................59
Fig. 2.3-83 Configure the O&M LAPD Timeslot .....................................................................................60
Fig. 2.3-84 Configure the LAPD Multiplexing - Site Properties...............................................................61
Fig. 2.3-85 Configure the LAPD Multiplexing - Multiplexing Mode Selection.......................................62
Fig. 2.3-86 Configure the Power-off Bypass - Site Properties...................................................................63
Fig. 2.3-87 Configure Power-off Bypass - Specify Power-off Bypass......................................................64
Fig. 2.3-88 Configuring 80W (1)................................................................................................................65
Fig. 2.3-89 80W (2) Configuration ............................................................................................................66
Fig. 2.3-90 80W (3) Configuration ............................................................................................................66
Fig. 2.3-91 Configure the EasyWay - Menu Option...................................................................................67
Fig. 2.3-92 Configure the EasyWay - EasyWay Parameters......................................................................68
Fig. 2.3-93 Near Sub-multiplexing Shelf....................................................................................................69
Fig. 2.3-94 Remote Sub-multiplexing Shelf...............................................................................................70
Fig. 2.3-95 Configure the Remote Sub-multiplexing TIC Board...............................................................70
Fig. 2.3-96 Selection of [Edit CBCOP] Menu............................................................................................72
Fig. 2.3-97 [Edit CBCOP] Dialog Box ......................................................................................................73
Fig. 2.3-98 Edit X.25 Dialog Box ..............................................................................................................73
Fig. 2.3-99 Selection of Cell Support CBC ...............................................................................................74
Fig. 2.3-100 CBC Channel Configuration..................................................................................................74
Fig. 2.3-101 Modification of Cell Radio Information Menu Option.........................................................76
Fig. 2.3-102 Configure the Extension Cell.................................................................................................76
Fig. 2.3-103 Configure the Extension BCCH Carrier Frequency..............................................................77
Fig. 2.3-104 Configure non-BCCH Carrier Frequency as Extension Type ..............................................78
-iv-
Fig. 2.3-105 Configure the External Extension Cell..................................................................................78

Fig. 2.3-106 Configure the Adjacent Cell (1).............................................................................................79
Fig. 2.3-107 Configure the Adjacent Cell (2).............................................................................................80
Fig. 2.3-108 Configure Handover and Reselection Cell - Menu Option...................................................81
Fig. 2.3-109 Configure Handover and Reselection Cell--Parameter Configuration..................................82
Fig. 2.3-110 Configure the External Cell (1)..............................................................................................83
Fig. 2.3-111 Configure the External Cell (2)..............................................................................................84
Fig. 2.3-112 Configure Frequency Hopping Create the Frequency Hopping System Menu..................85
Fig. 2.3-113 Configure the Frequency Hopping System............................................................................86
Fig. 2.3-114 Configure the Frequency Hopping - Frequency Hopping Point ...........................................86
Fig. 2.3-115 Modify the Channel Parameter..............................................................................................87
Fig. 2.3-116 Dialog Box for Adding Racks................................................................................................88
Fig. 2.3-117 Add the Rack Including the GIU and the SPCU....................................................................89
Fig. 2.3-118 Configure the PUC (1)...........................................................................................................89
Fig. 2.3-119 Configure the PUC (2)...........................................................................................................90
Fig. 2.3-120 Add the FRP Board.................................................................................................................90
Fig. 2.3-121 Add the BRP Board................................................................................................................91
Fig. 2.3-122 Configure the TIC with GB Interface....................................................................................91
Fig. 2.3-123 Configure BRCH (1)..............................................................................................................92
Fig. 2.3-124 Configure BRCH (2)..............................................................................................................92
Fig. 2.3-125 Configure NSVC (1)..............................................................................................................93
Fig. 2.3-128 Configure a GPRS Cell (1)....................................................................................................94
Fig. 2.3-129 Configure a GPRS Cell (2)....................................................................................................95
Fig. 2.3-130 Configure GPRS Transceiver ................................................................................................95
Fig. 2.3-131 Configure a Dynamic Channel...............................................................................................96
-v-
Fig. 2.3-132 Menu for Data Export Configuration ....................................................................................97

Fig. 2.3-133 Configuration Database Export Interface..............................................................................98
Fig. 2.3-134 Configure the Report Export .................................................................................................98
Fig. 2.4-135 Main interface of Radio Resources Management................................................................100
Fig. 2.4-136 Modify the BSC - Menu Option..........................................................................................100
Fig. 2.4-137 Modify the BSC - GSM.......................................................................................................101
Fig. 2.4-138 Modify the BSC - GPRS......................................................................................................101
Fig. 2.4-139 Modify the BSC - Success...................................................................................................102
Fig. 2.4-140 Configure the Logical Site...................................................................................................103
Fig. 2.4-141 Successful Modification.......................................................................................................104
Fig. 2.4-142 Modify the Cell - Menu Option...........................................................................................105
Fig. 2.4-143 Modify the Cell Parameters.................................................................................................106
Fig. 2.4-144 Cell Modification Success....................................................................................................106
Fig. 2.4-145 Modify the Power Control - Menu Option..........................................................................107
Fig. 2.4-146 Modify the Power Control...................................................................................................108
Fig. 2.4-147 Power Control Modification Success...................................................................................108
Fig. 2.4-148 Modify the Handover Control - Menu Option.....................................................................109
Fig. 2.4-149 Modify the Handover Control Parameter.............................................................................110
Fig. 2.4-150 Handover Control Modification Success.............................................................................110
Fig. 2.5-151 Software Loading Flow........................................................................................................111
Fig. 2.5-152 Software Loading Main Interface........................................................................................113
Fig. 2.5-153 Software Version Information..............................................................................................114
Fig. 2.5-154 Logic View...........................................................................................................................119
Fig. 2.5-155 Load the Software................................................................................................................119
Fig. 2.5-156 Store a Single Software into the Database...........................................................................120
Fig. 2.5-157 Auto Search..........................................................................................................................121
Fig. 2.5-158 Store the Relevant BTS Software into the Database...........................................................122
-vi-
Fig. 2.5-159 Query the Version of General Software...............................................................................124

Fig. 2.5-160 Create General Software of BSC.........................................................................................125
Fig. 2.5-161 Create General Software of BTS.........................................................................................125
Fig. 2.5-162 Load General Software........................................................................................................127
Fig. 2.5-163 Browse the Software............................................................................................................129
Fig. 2.5-164 Software Setting (1).............................................................................................................130
Fig. 2.5-165 Software Setting (2).............................................................................................................131
Fig. 2.5-166 Create the BOSN Software Version.....................................................................................132
Fig. 2.5-167 DSP Software Setting...........................................................................................................133
Fig. 2.5-168 BSC Equipment Rack View.................................................................................................136
Fig. 2.5-169 Physical Site Rack View......................................................................................................136
Fig. 2.5-170 Load the Software for the Board of the Base Station Equipment.......................................137
Fig. 2.5-171 Load the Software for the Board of the Physical Site.........................................................137
Fig. 2.5-172 Software Setting of the Physical Site...................................................................................139
Fig. 2.5-173 Create the Software Version of the Physical Site.................................................................140
Fig. 2.5-174 Software Loading of the Physical Site.................................................................................142
Fig. 2.5-175 Software Loading of the Physical Site.................................................................................143
Fig. 2.5-176 Query the Foreground Running Version..............................................................................145
Fig. 2.6-177 Watch the Dynamic Properties of a Single Item..................................................................148
Fig. 2.6-178 Watch the Dynamic Properties of All Items.........................................................................149
Fig. 2.6-179 Set the Refresh Frequency...................................................................................................151
Fig. 2.6-180 Blocking/Unblocking...........................................................................................................152
Fig. 2.6-181 Query the Status of the A-interface Timeslot.......................................................................154
Fig. 2.6-182 PCM Circuit Assemble/Disassemble...................................................................................156
Fig. 2.6-183 Query the Status of the Abis-Interface Channel..................................................................157
Fig. 2.6-184 N7link Status........................................................................................................................158
Fig. 2.6-185 Activating/Deactivating........................................................................................................160
-vii-
Fig. 2.6-186 Relevant Operations of the BVC........................................................................................161

Fig. 2.6-187 Query the Channel Statistics of the Cell..............................................................................162
Fig. 2.6-188 Cell Channel Statistics Result..............................................................................................163
Fig. 2.6-189 Query the Channel Statistics of the Module........................................................................165
Fig. 2.6-190 Channel Statistics Result of the Central Module.................................................................165
Fig. 2.6-191 Channel Statistics Result of the Peripheral Module............................................................166
Fig. 2.6-192 Query the Instance Type of the Module...............................................................................167
Fig. 2.6-193 Set the Foreground Switch Parameter of the Module..........................................................169
Fig. 2.6-194 Interface for Setting the Foreground Switch Parameters.....................................................170
Fig. 2.6-195 Query the FUC Control Level (1)........................................................................................171
Fig. 2.6-196 Query the FUC Control Level (2)........................................................................................172
Fig. 2.6-197 End the FUC Control...........................................................................................................174
Fig. 2.6-198 Set the Flow Control Bitmap...............................................................................................176
Fig. 2.6-199 Window for Setting the Flow Control Bitmap.....................................................................177
Fig. 2.6-200 Global Reset.........................................................................................................................179
Fig. 3.2-201 Main Interface of Alarm Management.....................................................................................3
Fig. 3.2-202 BSC Alarm Management Rack Diagram Display...................................................................4
Fig. 3.2-203 Alarm Query Wizard 1.............................................................................................................5
Fig. 3.2-204 Alarm Query Wizard to 2.........................................................................................................6
Fig. 3.2-205 Alarm Query Wizard 3.............................................................................................................6
Fig. 3.2-206 Query Results...........................................................................................................................7
Fig. 3.2-207 Query Result Report Display...................................................................................................8
Fig. 3.2-208 Display of Current Alarms of a Site.......................................................................................10
Fig. 3.2-209 Select the Alarm Query Type.................................................................................................10
Fig. 3.2-210 Select the Alarm Query Object...............................................................................................11
Fig. 3.2-211 Select the Alarm Query Level and Alarm Code.....................................................................11
Fig. 3.2-212 Site Alarm Query Result Display...........................................................................................12
-viii-
Fig. 3.2-213 View the Current Alarms of Board.........................................................................................14

Fig. 3.2-214 Notification Query-1 .............................................................................................................16
Fig. 3.2-215 Notification Query 2 ...........................................................................................................16
Fig. 3.2-216 Notification Query-3 .............................................................................................................17
Fig. 3.2-217 Display the Notification Query Result...................................................................................17
Fig. 3.2-218 Query the Board History 1 ....................................................................................................19
Fig. 3.2-219 Query the Board History 2.....................................................................................................19
Fig. 3.2-220 Display the Query Results......................................................................................................20
Fig. 3.2-221 Select the Time Period for the Conditional Query.................................................................21
Fig. 3.2-222 Reload File Inquiry Box.........................................................................................................22
Fig. 3.2-223 Alarm Frequency Analysis - Select the Alarm Source...........................................................23
Fig. 3.2-224 Alarm Frequency Statistics - Select the Time Period for Alarm Statistics............................24
Fig. 3.2-225 Alarm Frequency Analysis - Select the Filtering Condition for Alarm Statistics.................25
Fig. 3.2-226 Alarm Frequency Analysis - Show the Alarm Statistics Result in List.................................25
Fig. 3.2-227 Alarm Frequency Analysis - Display Alarm Statistics Result in Graphical Mode................26
Fig. 3.2-228 Alarm Correlation Information Query...................................................................................27
Fig. 3.2-229 Relevant Information Display................................................................................................28
Fig. 3.2-230 Alarm Validation.....................................................................................................................29
Fig. 3.2-231 Manual Alarm Recovery........................................................................................................31
Fig. 3.2-232 Acknowledge the Operation Box...........................................................................................32
Fig. 3.2-233 Notification Acknowledgment...............................................................................................33
Fig. 3.2-234 Instant Dump of Important Alarms........................................................................................35
Fig. 3.2-235 Manual Dump.........................................................................................................................36
Fig. 3.2-236 Setting the Periodic Dump.....................................................................................................38
Fig. 3.2-237 Alarm Knowledge Base Setting.............................................................................................40
Fig. 3.2-238 Alarm Show Mode.................................................................................................................47
Fig. 3.2-239 Customize the Item Display...................................................................................................48
-ix-
Fig. 3.3-240 Trunk Node Setting................................................................................................................49

Fig. 3.3-241 Existing Template Display.....................................................................................................50
Fig. 3.3-242 Create Trunk Node Alarm Template......................................................................................51
Fig. 3.3-243 Trunk Node Alarm Setup.......................................................................................................52
Fig. 3.3-244 Modify the Trunk Node Template..........................................................................................54
Fig. 3.3-245 Delete the Trunk Node Template...........................................................................................56
Fig. 3.3-246 Mode Setting..........................................................................................................................58
Fig. 3.4-247 Temperature/Humidity Setup.................................................................................................60
Fig. 3.4-248 Environment Parameter Setting - Infrared.............................................................................62
Fig. 3.5-249 Dialog Box for Alarm Filtering Rule Management...............................................................65
Fig. 3.5-250 Dialog Box for Editing the Alarm Filtering Rule..................................................................65
Fig. 3.5-251 Rule Object Selection Dialog Box.........................................................................................66
Fig. 3.5-252 Dialog Box for Modifying the Alarm Filtering Rule.............................................................69
Fig. 3.5-253 Dialog Box for Alarm Reclassification Rule Management...................................................72
Fig. 3.5-254 Dialog Box for Creating an Alarm Reclassification Rule.....................................................73
Fig. 3.5-255 Rule Object Selection Dialog Box.........................................................................................73
Fig. 3.5-256 Dialog Box for Alarm Reclassification Rule Modification...................................................76
Fig. 3.5-257 Dialog Box for Alarm Correlation Rule Management..........................................................81
Fig. 3.5-258 Dialog Box for Suppress Rule Creation.................................................................................81
Fig. 3.5-259 Managed Object Selection Dialog Box..................................................................................82
Fig. 3.5-260 Dialog Box for New Count Rule Creation.............................................................................85
Fig. 3.5-261 Managed Object Selection Dialog Box..................................................................................85
Fig. 3.5-262 Dialog Box for Compress Rule Creation...............................................................................88
Fig. 3.5-263 Dialog Box for Suppress Rule Modification.........................................................................90
Fig. 3.5-264 Dialog Box for Count Rule Modification..............................................................................91
Fig. 3.5-265 Dialog Box for Compress Rule Modification........................................................................91
Fig. 3.6-266 Alarm Physical View Interface...............................................................................................96
-x-
Fig. 3.6-267 View the Master/Slave Status.................................................................................................96

Fig. 3.6-268 Board Status Information Display..........................................................................................98
Fig. 3.6-269 Reset Confirmation Dialog Box ..........................................................................................100
Fig. 3.6-270 Board Changeover Confirmation Dialog Box ....................................................................102
Fig. 3.6-271 Periodic Changeover Setting Dialog Box ...........................................................................104
Fig. 3.6-272 Board Off-line Confirmation Dialog Box............................................................................106
Fig. 3.6-273 Alarm Physical View............................................................................................................108
Fig. 3.6-274 Dialog Box for Setting SYCK Clock Reference.................................................................108
Fig. 3.6-275 Dialog Box for Setting CKI Clock Reference......................................................................111
Fig. 3.6-276 Dialog Box for Setting SYCK Clock Mode.........................................................................113
Fig. 3.6-277 Dialog Box for Confirming Clock Reference Permission ..................................................115
Fig. 3.6-278 Physical Site Rack View.......................................................................................................117
Fig. 3.6-279 Dialog Box for Remote Reset Confirmation........................................................................117
Fig. 3.6-280 Physical Site Rack View.......................................................................................................119
Fig. 3.6-281 Dialog Box for Board Reset Confirmation..........................................................................119
Fig. 3.7-282 SMS Alarm Forward Management Dialog Box..................................................................122
Fig. 3.7-283 Dialog Box for Server Forward Function Success..............................................................122
Fig. 3.7-286 Dialog Box For Forward Rule Management.......................................................................136
Fig. 3.7-287 Dialog Box For Forward Rule Creation...............................................................................138
Fig. 3.7-288 Rule Object Selection Dialog Box.......................................................................................138
Fig. 3.7-289 Dialog Box For Forward Rule Creation...............................................................................141
Fig. 3.7-290 Dialog Box for Modifying Forward Rule ...........................................................................143
Fig. 3.7-291 Dialog Box for Working out the Short Message Format.....................................................146
Fig. 3.7-292 Dialog Box for Customizing the Short Message Format.....................................................148
Fig. 3.8-293 Select the BSC to be Tested and Select [Instant Test] ........................................................151
-xi-
Fig. 3.8-294 Select the Units and Muints to be Tested.............................................................................151

Fig. 3.8-295 Start the Test.........................................................................................................................152
Fig. 3.8-296 Test Results of Units, Muints and Links .............................................................................153
Fig. 3.8-297 Select the Link to be Tested.................................................................................................154
Fig. 3.8-298 Select the PCM to be Tested................................................................................................156
Fig. 3.8-299 PCM Test Results.................................................................................................................156
Fig. 3.8-300 Select a BSC and [Scheduled Test]......................................................................................158
Fig. 3.8-301 Set the Test Period and Select the Object to be Tested........................................................158
Fig. 3.8-302 Window for Original Test Overwrite Confirmation.............................................................159
Fig. 3.8-303 First Scheduled Test Setup Success.....................................................................................159
Fig. 3.8-304 Main Interface Upon Completion of Scheduled Test Setup ...............................................159
Fig. 3.8-305 Suspend Scheduled Test.......................................................................................................161
Fig. 3.8-306 Suspend Test Confirmation..................................................................................................162
Fig. 3.8-307 Test after Being Suspended..................................................................................................162
Fig. 3.8-308 Restart Scheduled Test.........................................................................................................163
Fig. 3.8-309 Success of Restarting Scheduled Test..................................................................................164
Fig. 3.8-310 Test Being Restarted.............................................................................................................164
Fig. 3.8-311 Delete Scheduled Test..........................................................................................................165
Fig. 3.8-312 Confirmation of Scheduled Test Deletion............................................................................166
Fig. 3.8-313 View the Details of Test Results..........................................................................................168
Fig. 3.8-314 Details of Test Results..........................................................................................................169
Fig. 3.8-315 Refresh Confirmation...........................................................................................................170
Fig. 3.8-316 Select [Query Test Result]....................................................................................................171
Fig. 3.8-317 Set the Test Result Query Condition....................................................................................172
Fig. 3.8-318 Test Results Query/Display..................................................................................................172
Fig. 3.8-319 Select [Delete Test Result]...................................................................................................173
Fig. 3.8-320 Conditions for Deleting a Test Result..................................................................................174
-xii-
Fig. 3.8-321 Confirmation for Deleting a Test Result..............................................................................174
-xiii-
List of Tables
Table 2.5-1 List of Software ID and Usage..............................................................................................116
-i-
1Operation Safety
This chapter describes the precautions, such as scheduled test and system upgrade, that
are related to equipment performance.
1.1On-site Operation Descriptions

1.
The On-site Data Modification Guide should be strictly followed. For any data
modification, it is necessary to fill in the On-site Data Modification Record
Form as per the requirements and return it to the Technical Support Office of
Mobile Business Division of ZTE Corporation.
2.
Data modification operations permitted on-site include using the OMCR (V2)
radio resource management interface to adjust radio parameters, and using the
software loading interface for storing the software in the database and software
loading. The On-site Data Modification Record Form can be returned to
Technical Support Office of Mobile Business Division of ZTE Corporation after
the operation.
3.
For the special limitations of the current version and the stable running of the
equipment, it is necessary notify the Technical Support Office of Mobile
Business Division of ZTE Corporation in written form and get the signing
confirmation of the BSS (V2) project manager of the Technical Support Office
of Mobile Business Division of ZTE Corporation before any data
modification.(for example, use the MMI commands to modify any configuration
of BSC).
4.
It is suggested to obtain the permission of the relevant management personnel of

the Technical Support Office of Mobile Business Division of ZTE Corporation
before using software program PCanywhere.
5.
Make sure that the foreground and background data is consistent and the ZDB
file is not modified.
6.
It is forbidden to read foreground files such as PRINT, ERR, and LOG at busy
hours in the day or at night.
1
ZXG10-BSS (V2) Base Station Subsystem Operation Manual
7.
It is suggested to avoid using probes.
8.
Forbid applying the testing programs such as PPTEST in the day.
9.
It is forbidden to upgrading the version such as PPTEST in the daytime.
10. On-site personnel must use an independent user name to perform operations,
modify the ROOT right and give the right to the control of the project manager.
11. On the BSS equipment with users, the data synchronization can only be
performed during the period from 23:00 pm to 4:00 am.
12. ZDBCHK is required for data check before importing ZDB data into the
foreground.
13. Conduct the validity check after modifying radio parameters.
14. It is required to export the data out of the foreground ZDB after each
modification and use ZDBCHK to check it.
1.2Usage Guide to On-site Version Functions

1.
At present, the downlink power control function cannot be enabled (if it is

necessary to enable this function after the OMU version uses 1.60.04a, a written
application must be presented and approved before it can be performed.)
2.
The directed retry and queue functions are enabled after the network planning
personnel propose the corresponding scheme according to the network operation
requirements.
3.
Never enable the BCCH (Broadcast Channel) switching function and the
SDCCH dynamic allocation function without grant. Apply to Technical Support
Office of Mobile Business Division of ZTE Corporation in written form and get
its approval before enabling these functions.
4.
If it is necessary to enable the MP periodic switching function, a written

application must be presented to the Technical Support Office of Mobile
Business Division of ZTE Corporation.
5.
It is forbidden to use the flow control based on mobile phone priority.
6.
It is forbidden to use the project switch. It is necessary to apply to the Technical

Support Office of Mobile Business Division of ZTE Corporation in advance for
approval.
2
Chapter 1 Operation Safety
7.
It is forbidden to enable the frequency hopping function without written

application in advance.
2Configuration Management
This chapter introduces the configuration flow, logic structure of configuration data and
how to make the simplest data configuration. It describes in detail the advanced data
configuration, including how to configure different sites, external cells, relative cells,
frequency hopping, EasyWay, sub-multiplexing, CBC, O&M LAPD, power-down
bypass and GPRS data and how to configure data. It also describes how to configure
the software version via software loading and how to configure blocking/unblocking
operations via dynamic data management.
2.1Overview
The integrated configuration management is used for initial configuration and for
modification to the configuration data. It establishes for the user a flow that enables the
operation & maintenance personnel to conduct the data configuration easily via the
Wizard, and provides the user with a good graphical user interface based on the flow
for the convenient data configuration of the user.
The integrated configuration management provides the physical, radio and software
configurations. The user can only use this tool to modify the physical configuration.
For modification to the radio configuration, the radio resource management can be
used; for modification to the software configuration, the software loading can be used;
for blocking and unblocking of time slots, the dynamic data management can be used.
The integrated configuration management does not provide adjustment of detailed
radio parameters and configuration of software parameters.
The general process of data configuration is as follows: Use the integrated
configuration management to configure physical and basic radio parameters; use the
radio resource management to adjust detailed radio parameters; use the software
loading to configure the foreground software version; use the dynamic data
management to block and unblock time slots in network debugging.
The handling flow of the integrated configuration management is as follows: Read the
data in the database to the client first and send the result to the server for resolution
after the user edits the data via the Wizard. Upon successful resolution, the
1
configuration command set is generated and returned to the client for execution.
Note:
When the integrated configuration management is used for a large amount of data
configuration, it is better that one user performs operations at a time to avoid data
configuration conflict.
The configuration commands generated by the integrated configuration management
must be executed at the client. Two execution modes are available: Execution one by
one and batch execution. With slow execution speed and without rollback after an error
occurs, the first mode may easily lead to data inconsistency. So batch execution is
usually recommended. If the number of generated commands exceeds 6000 and are
sent in big transaction mode, it is recommended that the user split the command file
and send it in segments, to avoid timeout and rollback of big transactions.
2.2BSC Data Configuration (Basic Part)

2.2.1Configuration Flow
Before the configuration, first check the configuration of syscfg.ini file in the
background server. If there is the -DEBUG parameter, the configuration commands
are sent to the background database instead of being sent to the foreground; otherwise,
they are sent to the foreground. At this time, the status of the link with the foreground
should be ensured normal.
1.
Initial configuration
The configuration of MSC and BSC by using the integrated configuration
management is called initial configuration. The workfolw is shown in Fig. 2.2-1.
Chapter 2 Configuration Management
Start Integrated Configuration Management,

and choose working mode Initial Configuration
Edit graphic configuration script

(configure data with the Wizard)
Save and check the configuration script validity
Send configuration script to the server for

ICC resolution to create MML commands
Execute the returned MML command set

Fig. 2.2-1 Initial Configuration Flow
2.
Incremental configuration
Addition, deletion and modification of the existing BSC configuration data are
called incremental configuration. The workflow is shown Fig. 2.2-2.
Start Integrated Configuration Management, and

choose Configuration Modification mode
Reversed configuration script
Edit graphic configuration script

(configure data with the Wizard)
Save and check the configuration script validity
Send the script to the server for ICC

resolution to create MML commands
Execute the returned MML command set

Fig. 2.2-2 Modification Configuration Flow
Start the integrated configuration management and select the [Modification

Configuration] mode to pop up the [Reversed Configuration Script] dialog box
as shown in Fig. 2.2-3.
Fig. 2.2-3 Incremental Configuration (1)
Input the BSCID with configuration to be modified. Note that this BSCID must
exist in the system. Click <Next> to obtain the data, as shown in Fig. 2.2-4.
After this succeeds, the dialog box for entering step 2 of the Wizard will
automatically pop up, as shown in Fig. 2.2-5.
Click <Next> to enter the phase of editing the script. The operations that follow
are the same as those in the initial configuration.
3.
Logic structure of data configuration

There is a requirement on the sequence of the data configurations, as shown in
Fig. 2.2-6.
Fig. 2.2-6 Logic Structure of Data Configuration
The general configuration sequence is: First configure the physical MSC, BSC
6
BSC RACKBSC SHELFBSC BOARD; SITESITE RACKSITE

SHELFSITE PANEL; EasyWay; radio BSCradio SITECELLTRX,
FHS, adjacent cell; external cell.
[Verification]
The initial configuration and the incremental configuration can be made via the Wizard
prompt.
2.2.2Data Configuration
[Objective]
A simplest configuration is introduced as follows, including BSC, base station and
radio data configuration.
[Preliminary setup]
Determine the parameters relevant with configuration operations.
[Required steps]
1.
Configure the basic properties of MSC and BSC
2.
Configure the physical rack and frames of BSC
3.
Configure the BSC board
4.
Configure the physical site
5.
Configure the radio BSC
6.
Configure the radio site
7.
Configure the radio cell
8.
Configure the radio transceiver
9.
Save the file
10. Generate and execute the configured man-machine command set.

[Detailed procedure]
1.
Configure the basic properties of MSC and BSC

Enter the main interface of OMCR (V2) and click the [Configuration
ManagementIntegrated configuration management] menu, as shown in Fig.
2.2-7.
Fig. 2.2-7 Start the Integrated Configuration Management
First pop up the [Select Mode] interface and select [Initial Configuration], as
shown Fig. 2.2-8. Click <OK> to enter the [Graphical Script Edit] interface.
Fig. 2.2-8 Select Initial Configuration
If a configuration script exists in the current directory, the user can open it to
continue editing it. If the user wants to generate a new script, click <New>.
Take the creation of a configuration script as example, and the selection is
shown in Fig. 2.2-9.
Fig. 2.2-9 Create a Configuration Script
Click <Next> to enter [First step of Creation Wizard: Add MSC Equipment
information] interface to add an MSC. If this MSC has existed in the database,
the user can fill the same MSC No. as that in the database, as shown in Fig. 2.210. Fill any legal values for other information in the interface.
Configure the [MSC Equipment information] interface, as shown in Fig. 2.2-10.
Fig. 2.2-10 Configure the MSC Equipment
10
Click <Next> to enter [Second step of Create Wizard: Add BSC Equipment
information], as shown in Fig. 2.2-11.
.
Fig. 2.2-11 Configure the BSC Parameters
The user selects [Initialization Radio Info], and the basic radio information
corresponding to the physical BSC is automatically generated. Click <OK> to
complete editing the basic BSC information. The application automatically
generates the MSC and BSC nodes. The user can select a node and edit its
properties, but cannot modify its No. The menu is shown in Fig. 2.2-12.
11
Fig. 2.2-12 BSC Equipment Node
2.
Configure the physical rack and shelves of BSC

The BSC at this time has no rack, as shown in Fig. 2.2-12. The user selects the
[BSC Equipment] node, right-clicks and selects [Add Rack] in the popped up
menu to enter the interface, as shown in Fig. 2.2-13.
Fig. 2.2-13 BSC Rack Configuration
Click <Ok> and the basic configuration is automatically generated, as shown in

Fig. 2.2-14.
12
Fig. 2.2-14 BSC Rack
When adding the rack, select the shelf arrangement and type, as shown in Fig.
2.2-13. On the existing rack, if the lowest shelf is empty, as shown in Fig. 2.214, the user can right-click the mouse to select [Add a Shelf] and pop up the
[Add BSC shelf property], as shown in Fig. 2.2-15.
13
Fig. 2.2-15 BSC Shelf Configuration
Select a shelf type and the system will automatically add a shelf and the default
boards. Take the selection of the [ZXG10_BATC] frame for example, as shown
in Fig. 2.2-16.
Fig. 2.2-16 BATC Shelf Configuration
3.
Configure the BSC board

In the configuration script edited in graphical mode, the default boards in the
slots of different frames have been drew. The procedure of adding the
corresponding board is as follows:
1)
Click to select a board, right-click on it and select the [Add Board] menu, as
14
Fig. 2.2-17 Add A BSC Board
2)
For the DRT and TIC boards, the dialog box will pop up automatically to ask the
user to input parameters.
Configure DRT
The user selects the [DRT] board in the rack view, right-clicks it and selects
[Add Board] to pop up the dialog box shown in Fig. 2.2-18. The user can select
the DRT type, the DSP type and the DSP No.
Fig. 2.2-18 Configure the DRT Board
Configure the TIC in the ZXG10_BIF shelf

The PCM shall be configured when the TIC in the BIF shelf is configured.
Right-click on the TIC board to pop up a menu. In this menu, select the [Board
property] menu to enter the interface for setting the TIC parameters, as shown in
15
Fig. 2.2-19.
Fig. 2.2-19 Configure the TIC Board with Abis Interface
Generally, all the PCMs are allocated. If a PCM connects to the Site, the
connection information will be displayed. When this TIC panel or the PCM is
deleted in this interface, the connection information will also be deleted.
Configure the TIC board with A interface
Select the TIC in the [ZXG10_BATC] frame, right-click on it and select the
[Add Board] menu to enter the interface for setting the TIC parameters, as
16
Fig. 2.2-20 Configure the TIC Board of A Interface
The user can click an item in the N7Lik list. By selecting in the list, the user can
specify the corresponding SLC and then click <OK>.
3)
For the boards such as MTP (Message Transfer Part), GIPP (Gb Interface
Peripheral Processor), BIPP (Bis Interface Peripheral Processor), TCPP
(TransCoder unit Peripheral Processor), AIPP (A Interface Peripheral Processor),
their properties can be viewed and modified.
Configure the MTP

When a BSC rack is added, an MTP board is configured by default in type
[CMT_ZXG10_MTP], as shown in Fig. 2.2-21.
17
Fig. 2.2-21 Configure the MTP Board
If A interface is configured with 2M No. 7, the [CommType] parameter of this

MTP board is set to [CMT_ZXG10_2MMTP]. If two MTP boards are
configured, their [CommType] parameters must be consistent. This is a check
item in the validity check. A prompt will occur if the configuration is invalid.
Configure the BIPP
Right-click on the BIPP board to pop up a menu. In this menu, select the [Board
property] menu to enter the interface for setting the BIPP parameters, as shown
in Fig. 2.2-22.
Fig. 2.2-22 Configure the BIPP
18
HW1 is an odd No., and HW2 is equal to the selected HW1 value plus 1 and
cannot be modified. During the incremental configuration, the HW No. cannot
be modified because the connection has been configured.
4.
Configure the physical site
1)
Create the default rack as instructed by the Wizard.

Select the node [Physical equipment] and right-click to select [Add base station].
The Wizard shown in Fig. 2.2-23 pops up.
Fig. 2.2-23 Configure the Physical Site - Base Station Parameters
Fill parameters in the interface. Take the selection of [BTSV1.0(A)] in [Base

Station Type] for example. Click <Next> to enter the interface, as shown in Fig.
2.2-24.
19
Fig. 2.2-24 Configure the Physical Site - Initialization Panel
Select [Initialization Panel ] and click <Next> to configure the EBIE panel.
Select the connection type of PCM and click <Connect> to pop up the PCM list.
If the list is null, it is necessary to configure the upper-level PCMs. Select a
PCM. The interface is shown in Fig. 2.2-25.
Fig. 2.2-25 Configure the Physical Site - BIE Panel Configuration
The user can modify the EBIE panel type in this interface. Click <Finish>. The
system will automatically generate the default racks for the BTSV1.0 (A), as
20
Fig. 2.2-26 Configure the Physical Site - Rack View
2)
Configure the panel
Click the mouse to select [HYC] and right-click to select [Add panel] and add
the HYC panel.
Click the mouse to select [MUL] and right-click to select [Add panel] and add
the MUL panel.
Click the mouse to select [TRU] and right-click to select [Add panel]. The
corresponding interface pops up for you to configure the combiners and
dividers. Select combiners and dividers from the list, as shown in the Fig. 2.227.
After selecting the combiners and dividers, click <OK>. The system will
automatically add the TRU panel. If no PA and PSB panels are configured at this
21
time, the system will add them automatically.
Fig. 2.2-27 Configure Physical Sites - Combiners and Dividers of Tru
5.
Configure the radio BSC

Select [BSC Radio Info] in the popup menu, as shown in Fig. 2.2-28
Fig. 2.2-28 Configure the Radio BSC - Menu Option
The [Edit BSC Radio Info] pops up, as shown in Fig. 2.2-29.
22
Fig. 2.2-29 Configure the Radio BSC - BSC Parameters
Once the country code and the network code are sent, it cannot be modified. So,
they should be correct during the initial configuration.
6.
Configure radio sites

Two methods are available to configure radio sites:
One method is to select the [BSS FunctionCreate Site Manager] in
[RadioView], as shown in Fig. 2.2-30.
Fig. 2.2-30 Configure Radio Sites - Menu Option
23
Then a dialog box shown in Fig. 2.2-31 will pop up.
Fig. 2.2-31 Configure Radio Sites - No.
After inputting the logical site No., click <OK> and the system automatically
generate the corresponding radio site information.
The other method is to right-click the [Site] node in [PhyView] to pop up the
menu shown in Fig. 2.2-32.
Fig. 2.2-32 Configure Radio Sites - Menu Option 2
24
Select the [Edit Radio] menu to enter the [Wizard] interface, as shown in Fig.
2.2-33.
Fig. 2.2-33 Configure Radio Sites - No. 2
The list displays the radio information that has been configured to this site. Click
<OK> to display the interface shown in Fig. 2.2-34.
Fig. 2.2-34 Configure Radio Sites - Parameter Display
Click <Finish>, and the program will automatically add the corresponding
25
logical site into [RadioView]. Right-click on the logical site in [RadioView] to

pup up the menu as shown in Fig. 2.2-35.
Fig. 2.2-35 Configure Radio Sites - Logic Site Node
7.
Configure the radio cell.

In [RadioView], right-click on the [BTS Site Manager1] node to pop up the
menu as shown in Fig. 2.2-36.
Fig. 2.2-36 Configure Radio Cells - Menu Option
Select [Create Cell] in the popup menu to pop up the [Create cell radio
information] interface, as shown in Fig. 2.2-37.
26
Fig. 2.2-37 Configure Radio Cells - Cell Parameters
The Location Area Code and the Cell Code are allocated by the MSC, and the
MCC+MNC+LAC+CI is unique. The cell frequency band limits the frequency
points of cells. For example, the frequency band of cells is GSM850, and the
range of frequency point is [128,251].
8.
Configure carrier frequency (configure the radio transceiver)

In [RadioView], right-click on the [Cell1] node to pop up the menu as shown in
Fig. 2.2-38..
27
Fig. 2.2-38 Configure Carrier Frequency - Menu Option
Select [Create TRX] in the pop-up menu to configure the transceiver parameters.
as shown in Fig. 2.2-39 in GSM environment.
Fig. 2.2-39 Configure Carrier Frequency - Parameter Configuration
One and only one BCCH carrier frequency must be configured in a cell.
9.
Save the file

After the configuration is finished, click <Save> on the toolbar. Then the user
will first enter the validity check phase, as shown in Fig. 2.2-40.
28
Fig. 2.2-40 Save File (1)
After <OK> is clicked, the check result list will be displayed, as shown in Fig.
2.2-41..
If the validity check result has an error prompt, please modify the configuration
according to the prompt information. When a user conducts the initial
configuration, the user needs to confirm whether the MSC will be added, as
29
10. Generate and execute the configured man-machine command set

To add MSC, click <OK>; otherwise, only BSC will be added. After the addition
is successful, the system enters step 3 of Wizard: Send the script to the server for
ICC resolution, as shown in Fig. 2.2-43.
Fig. 2.2-43 Generate Configuration Command (1)
Directly click <Next>. The script will be sent to the server, as shown in Fig. 2.244.
After the resolution succeeds, the system will automatically enter step 4, as
30
It is recommended to select [Batch]. After the command is successfully sent, the

command window will prompt: successful batch submission. Now, the initial
configuration is finished.
[Verification]
Click <Save> to pass the validity check and then send the saved result according to the
Wizard prompt to ICC for resolution. Upon resolution success, the system will return
the MML command set and execute it successfully in the way of processing a big item.
31
2.3BSC Data Configuration (Advanced Part)

2.3.1Configuring the BTS1.0 and BTS1.0 (A) Sites
[Objective]
This section introduces how to configure the BTS1.0 and BTS1.0 (A) sites.
[Preliminary setup]
1.
Confirm the configured MSC, BSC and BSC rack parameters.
2.
Determine the parameters relevant to configuration operations.
[Required steps]
1.
2.
Configure the rack.
3.
Configure the panel.
1.
Create the default rack as constructed by the Wizard.

Fig. 2.3-46 Configure the BTS1.2 - Base Station Parameters
32
Fill parameters in the interface. If the BTS1.0 (A) base station is to be

configured, select [BTSV1.0(A)] in [Base Station Type]. Take the BTSV1.0 (A)
for example:
Select [BTSV1.0(A)] in [Base Station Type] and click <Next> to enter the
interface shown in Fig. 2.3-47.
Fig. 2.3-47 Configure the BTSV1.0 (A) - Initialization Panel
Select [Initialization Panel ] and click <Next> to configure the EBIE panel.
Select the connection type of PCM and click <Connect> to pop up the PCM list.
If the list is null, it is necessary to configure the upper-level PCMs. Select a
PCM. The interface is shown in Fig. 2.3-48.
33
Fig. 2.3-48 Configure the BTSV1.0 (A) - BIE Panel Configuration
The user can modify the BIE panel type in this interface. Click <Finish>, and
the system will automatically generate the default racks for the BTSV1.0 (A), as
shown in Fig. 2.3-49..
Fig. 2.3-49 Configure the BTSV1.0 (A) - Rack View
2.
Configure the rack
34
Select the [Site] node and right-click, as shown in Fig. 2.3-50.
Fig. 2.3-50 Configure the BTSV1.0 (A) - [Add Rack] Menu
Select the [Add Rack] menu to pop up the dialog box, as shown in Fig. 2.3-51.
Fig. 2.3-51 Configure the BTSV1.0 (A) - [Add Rack] Dialog Box
Click <OK>, and the system will add the default assistant rack.
3.
Configure the panel
Click the mouse to select [HYC] and right-click to select [Add panel] and add
the HYC panel.
Click the mouse to select [MUL] and right-click to select [Add panel] and add
35
the MUL panel.

Click the mouse to select [TRU] and right-click to select [Add panel]. The
corresponding interface pops up to configure the combiners and dividers. Select
combiners and dividers from the list, as shown in the Fig. 2.3-52.
Fig. 2.3-52 Configure the BTS1.2 - Combiners and Dividers of Tru
After selecting the combiners and dividers, click <OK>. The system will
automatically add the TRU panel. If no PA and PSB panels are configured at this
time, the system will add them automatically.
[Verification]
36
2.3.2Configuring the BTS2.0 Site

[Objective]
This section introduces how to configure the data of the BTS2.0 site.
[Preliminary setup]
[Required steps]
1.
2.
Configure the BTS2.0 rack.
3.
Configure the BTS2.0 panel.
1.
Create the default rack as constructed by the Wizard.

The [Wizard] shown in Fig. 2.3-53 pops up.
Fig. 2.3-53 Configure the BTS2.0 - Base Station Parameters
Select the base station type as [BTSV2.0], configure the base station parameter,
and click <Next> to enter into the interface as shown in Fig. 2.3-54. The
37
information of the current rack will be displayed, in which the type of the rack
and that of the base station are relevant and cannot be changed.
Fig. 2.3-54 Configure the BTS2.0 - Initialization Panel
Select [Initialization Panel ] and click <Next> to enter the interface shown in
Fig. 2.3-55.
Fig. 2.3-55 Configure the BTS2.0 - CMM Configuration
Configure [PCM No.] in the interface and select [Connection Type]. Select
38
[Connect BSC] and click <Connect> to pop up the interface shown in Fig. 2.356.
Fig. 2.3-56 Configure the BTS2.0 - PCM List
The available PCM Nos. of the BSC are listed in Fig. 2.3-56. Select a PCM No.
from the list and click <OK>, and a PCM is configured.
Click <Finish> in Fig. 2.3-55, and the system will automatically generate the
basic configuration and the default rack of the BTS2.0 and a base station node
will be generated on the main interface, as shown in Fig. 2.3-57.
39
Fig. 2.3-57 Configure the BTS2.0 - BTS2.0 Node Generation
Click the mouse to select <Rack 1> node under the base station in Fig. 2.3-57,
and the rack view is shown in Fig. 2.3-58. A CMM panel will be installed by
default, and the user can add the second one.
Fig. 2.3-58 Configure the BTS2.0 - BTS2.0 Rack Generation
2.
Configure the BTS2.0 rack

40
Select the generated BTS2.0 node in Fig. 2.3-57, and right-click, as shown in
Fig. 2.3-59.
Fig. 2.3-59 Configure the BTS2.0 - [Add Rack] Menu
Select [Add Rack] to pop up the rack information interface shown in Fig. 2.3-60.
Click <OK>, and the system will automatically generate the default BTS2.0
assistant rack view and the node on the view.
41
Fig. 2.3-60 Configure the BTS2.0 - [Add BTS2.0 Assistant Rack]
3.
Configure the BTS2.0 panel
1)
Select the [CMM] panel in the BTS2.0 rack view, right-click and select the [Add
panel] menu to enter the interface as shown in Fig. 2.3-61 and configure the
PCM connecting the assistant rack to the main rack.
Fig. 2.3-61 Configure the BTS2.0 - Configuration of PCM of B TS2.0 Assistant Rack
In this interface, be sure to select [UPSITE] as the connection type of the PCM,
which means that the assistant rack can only connect to the main rack.
42
2)
Select [CDU] in the BTS2.0 rack view to add this panel. Reselect this panel to
pop up the [Panel property] menu. Click this menu to pop up the interface
shown in Fig. 2.3-62, where the panel type can be modified. If this panel is
relevant to TRM, the panel type cannot be modified.
Fig. 2.3-62 Configure the BTS2.0 - CDU Configuration
3)
Select [TRM] panel in the BTS2.0 rack view to add it. The user can configure
the connection status of TRM with the combiner and the divider in the popup
interface as shown in Fig. 2.3-63. Click <Select> in Fig. 2.3-63 to pop up the list
of configurable combiners and dividers for the user to select from it.
43
Fig. 2.3-63 Configure the BTS2.0 - TRM Configuration
After the combiner and the divider of TRM are configured, select the
corresponding combiner and divider and view the panel properties. The interface
shown in Fig. 2.3-64 will pop up to display the connection status.
Fig. 2.3-64 Configure the BTS2.0 - CDU Properties Display
[Verification]
To configure the radio information of this site, click <Save> to pass the validity check
44
and then send the saved result according to the Wizard prompt to ICC for resolution.
Upon resolution success, the system will return the MML command set and execute it
successfully in the way of processing a big item.
2.3.3Configuring the MB and EMB Sites

[Objective]
This section introduces how to configure the MB and EMB sites.
[Preliminary setup]
Confirm the configured MSC, BSC and BSC racks.
[Required steps]
1.
Create the MB and EMB default racks as instructed by the Wizard.
2.
Configure the MB and EMB panels.
1.
Create the default MB and EMB racks as instructed by the Wizard.

Fig. 2.3-65 Configure the MB - Site Properties
Select [MB/EMB] as the base station type and click <Next> to pop up the
45
interface showing the rack information. Select [Initialization Panel] and click
<Next> to enter the interface shown in Fig. 2.3-66.
Fig. 2.3-66 Configure the MB - SCU Configuration
Configure the connection status of PCM and click <Finish>. The system will
add the base station and rack nodes on the view. Select this rack, and the rack
view is shown in Fig. 2.3-67.
Fig. 2.3-67 Configure the MB - Rack view
2.
Configure the MB and EMB panels

Both the MB and the EMB can only have one rack with one TRX inside as
shown in Fig. 2.3-67. For the EMB, another TRX can be added. Select <TRX>
panel to be added, right-click and select the [Add panel] menu.
46
[Verification]
To configure the radio information of the site, click <Save> to pass the validity check
2.3.4Configuring the BS21 Site

[Objective]
This section introduces how to configure the BS21 site.
[Preliminary setup]
[Required steps]
1.
Create the default BS21 rack as instructed by the Wizard.
2.
Configure the BS21 rack.
3.
Configure the BS21 panel.
The procedure of configuring the BS21 base station is almost the same as that of
configuring the BTS2.0. in Section 2.3.2. The difference is that [BS21] is selected as
the base station type. The BS21 rack view is shown in Fig. 2.3-68.
47
Fig. 2.3-68 BS21 Rack View
[Verification]
48
2.3.5Configuring the BS30 Site

[Objective]
This section introduces how to configure the BS30 site.
[Preliminary setup]
[Required steps]
1.
2.
Configure the BS30 panel
1.
Create the default BS30 rack as constructed by the Wizard.

Fig. 2.3-69 Configure the BS30 - Base Station Properties
2.
Configure the BS30 panel

Select [BS30] in [Base station type] and click <Next> to pop up the interface
49
Fig. 2.3-70 Configure the BS30 - CMM Panel Configuration
Configure the connection status of PCM and click <Finish>, as shown in Fig.
2.3-71.
Fig. 2.3-71 Configure the BS30 - Rack view
[Verification]
50
2.3.6Configuring the BS30 (V1.2) Site

[Objective]
This section introduces how to configure the BS30 (V1.2) site.
[Preliminary setup]
[Required steps]
1.
Create the default BS30 (V1.2) rack as instructed by the Wizard.
2.
Configure the BS30 (V1.2) panel
1.

Fig. 2.3-72 Configure the BS30 (V1.2) - Base Station Properties
2.
Configure the BS30 (V1.2) panel
51
Select [BS30 (V1.2)] in [Base station type] and click <Next> to pop up the
interface shown in Fig. 2.3-73.
Fig. 2.3-73 Configure the BS30 (V1.2) - CMM Panel Configuration
Configure the connection status of PCM and click <Finish>. The rack view is
generated as shown in Fig. 2.3-74.
52
Fig. 2.3-74 Configure the BS30 (V1.2) - Rack view
Select the [TRM] panel, and right-click to select the [Add Board] menu to pop
up a dialog box as shown in Fig. 2.3-75.
Fig. 2.3-75 Configure the BS30 (V1.2) TRM Panel
The divider and the combiner of the BS30 (V1.2) can only connect to the DPM
53
at the same layer, so the ICE gives the default value as shown in Fig. 2.3-75:
Automatic addition of ICE, deletion of the DPM panel upon adding and deleting
TRM.
[Verification]
54
2.3.7Configuring the Cascading Site

[Objective]
This section introduces how to configure the cascading site.
[Preliminary setup]
Confirm the configured MSC, BSC and BSC racks/sites.
[Required steps]
1.
Add a site.
2.
Configure the connection mode of the PCM.
1.
Add a site.
The user can add another site or modify the original site and set it to a cascading
site. Take the addition of a site, as shown in Fig. 2.3-76.
Fig. 2.3-76 Configure the Cascading Site - Add BTS
Select the [Add base station] menu to pop up the dialog box and configure the
base station properties shown in Fig. 2.3-77.
55
Fig. 2.3-77 Configure the Cascading Site - Site Properties Configuration
Click <Next> to enter the dialog box in Fig. 2.3-78. Select the [Initialization
Panel] parameter to enter the [BIEPCM configuration] interface.
Fig. 2.3-78 Configure the Cascading Site - Rack Configuration
56
2.
Configure the connection mode of the PCM, as shown in Fig. 2.3-79.
Fig. 2.3-79 Configure the Cascading Site - Select the PCM Connection Type
Select <Connection Type> as <UPSITE>, and click <Connect> to pop up the

dialog box as shown in Fig. 2.3-80. The interface shows all the available PCMs
of upper-level site type.
Fig. 2.3-80 Configure the Cascading Site - Select the PCM
57
Select a PCM and return to [BIE Properties Configuration] dialog box and click
<Finish>. The base station and rack nodes will be added in [PhyView]. Select
this base station node, and the connection relationship diagram as shown in Fig.
2.3-81 will be displayed.
Fig. 2.3-81 Configure the Cascading Site - Cascading Site Generation
[Verification]
58
2.3.8Configuring the O&M LAPD of a Site

[Objective]
This section introduces how to configure the O&M LAPD of a site.
[Preliminary setup]
Confirm the configured MSC, BSC and BSC racks/sites.
[Required steps]
The O&M LAPD parameter, which is located in the [Site Properties], can be
configured by modifying the site properties.
Select the site property, as shown in Fig. 2.3-82.
Fig. 2.3-82 Configure the O&M LAPD - Site Properties
When this site is configured with the BIEPCM line, the [Specify O&MLAPD]
parameter can be selected, as shown in Fig. 2.3-83.
59
Fig. 2.3-83 Configure the O&M LAPD Timeslot
For different types of BTS, the ranges of the O&M LAPD timeslot are different. In
configuration, the system automatically provides the timeslot range to be selected
according to the base station type.
[Verification]
60
2.3.9Configuring the Site with Designated Multiplexing Mode

[Objective]
This section introduces how to configure the site with designated multiplexing mode.
[Preliminary setup]
Confirm the configured MSC, BSC and sites.
[Required steps]
The LAPD multiplexing parameter, which is located in the [Site Properties] tab, can be
Select the site property, as shown in Fig. 2.3-84.
Fig. 2.3-84 Configure the LAPD Multiplexing - Site Properties
Modify [LAPD parameter] property and select the 1:4 multiplexing or no multiplexing,
61
Fig. 2.3-85 Configure the LAPD Multiplexing - Multiplexing Mode Selection
[Verification]
62
2.3.10Configuring the Site of Power-off Bypass

[Objective]
This section introduces how to configure the site of power-off bypass.
[Preliminary setup]
[Required steps]
The power-off bypass parameter, which is located in the [Site Properties], can be
Select the site property, as shown in Fig. 2.3-86..
Fig. 2.3-86 Configure the Power-off Bypass - Site Properties
Configure [Support power-off bypass], and click <OK> as shown in Fig. 2.3-87.
63
Fig. 2.3-87 Configure Power-off Bypass - Specify Power-off Bypass
[Verification]
64
2.3.11Configuring the 80W Site

[Objective]
This section introduces how to configure the 80W site. Sites BTS1.0, BTS1.X and
BTS2.0 support the 80W configuration.
[Preliminary setup]
[Required steps]
1.
Configure the PEU.
2.
Configure the TRU.
1.
Configure the PEU

Right-click the TRU panel to pop up the menu. Select [Set PEU] from the menu,
Fig. 2.3-88 Configuring 80W (1)
65
Click, and the PEU panel shows up. Select the PEU panel and select [Add
panel], and the interface in Fig. 2.3-89 is shown.
Fig. 2.3-89 80W (2) Configuration
2.
Configure the TRU

Select the TRU panel and then the [Add panel] menu to pop up the dialog box
Fig. 2.3-90 80W (3) Configuration
The BTS2.0 80W is configured in the same way as 80W is provided in the BTS1.0 and
66
the BTS1. A. The default rack view is still TRM. After a TRM is added, it is set to
STRU or SPAU via slot to realize the configuration of the BTS2.080W.
[Verification]
2.3.12Configure the Easy Way

[Objective]
This section introduces how to configure the easy way.
[Preliminary setup]
Confirm that the MSC, BSC and BSC racks/base stations have been configured.
[Required steps]
1.
Select the [Edit EasyWay] menu.
2.
Configure the EasyWay parameter.
Right-click on the [BSC Equipment] node in [PhyView] and select [Edit EasyWay] in
the popup menu to pop up the [Edit EasyWay] interface, as shown in Fig. 2.3-91.
Fig. 2.3-91 Configure the EasyWay - Menu Option
67
First input the base station. The system will automatically input the rack No. of this
base station. Select the rack No., PCM, and TS in turn. Select the EasyWay type, for
example, the BIEPCM type is lower-level Site or hanging for PECM.
Fig. 2.3-92 Configure the EasyWay - EasyWay Parameters
[Precautions]
The failure of sending the EasyWay creation command is usually the result of the
selected time slot being occupied. The user can check the terrestrial resource allocation
via CFGVIEW and select the time slot that are not allocated.
[Verification]
68
2.3.13Configuring the Sub-multiplexing

[Objective]
This section introduces how to configure the BSC sub-multiplexing shelf. The submultiplexing shelf functions as a pure trunk in this product. At present, only the remote
configuration of the BATC layer is considered.
[Preliminary setup]
[Required steps]
1.
Configure the local sub-multiplexing shelf.
2.
Configure the remote sub-multiplexing shelf.
1.
Configure the local sub-multiplexing shelf

When adding a shelf, select [ZXG10_BSM_NM] as the shelf type. Then the
system automatically generates the near sub-multiplexing shelf and the default
boards, as shown in Fig. 2.3-93.
Fig. 2.3-93 Near Sub-multiplexing Shelf
When NSPP is added, the system allocates 8 HWs by default. The user can edit
the NSPP properties and modify HWs. The allocation rule is to select the 8
consecutive HWs with the first HW No. being odd.
Select the [TIC] board, right-click and select the [Add Board] menu to add the
TIC board.
2.
Configure the remote sub-multiplexing shelf

The remote sub-multiplexing shelf is on a rack separately. When adding a shelf,
select [ZXG10_BSM_FM] as the shelf type. Then the system automatically
69
generates the remote sub-multiplexing shelf and the default boards, as shown in
Fig. 2.3-94.
Fig. 2.3-94 Remote Sub-multiplexing Shelf
A remote sub-multiplexing shelf can manage a rack by itself, this rack can only
be configured with the [ZXG10_BATC] shelf. The FSPP board has 8 HWs to
connect the BATC shelf, so at most 4 BATC shelves can be configured. When a
BATC is added, the system allocates the HWs from the least to the greatest, and
the user can modify the HWs on TCPP on the remote BATC. But different HWs
correspond to different TIC (Trunk Interface Circuit) slots on the FM shelf. If
the configuration is wrong, the system will give a prompt.
After the FM shelf is configured, the user selects the [TIC] board on it, rightclick and select [Add Board] to pop up the interface shown in Fig. 2.3-95.
Configure the PCM, select the near TIC connected and associate the remote TIC
with the near TIC in the NM shelf.
Fig. 2.3-95 Configure the Remote Sub-multiplexing TIC Board
70
[Precautions]
The data validity check performed by the integrated configuration management during
the configuration of the remote sub-multiplexing rack:
1.
Slots 12 and 13 for the TIC in the FM shelf must be configured, which is the
basic conditions for normal operation of the rack.
2.
The No. of the rack with the remote FM ranges from 1 to 16, and other rack
Nos. range from 1 to 6.
3.
The TIC board in the FM shelf should correspond to the TIC board on the NM
shelf.
4.
Judge whether the HW allocation of the NSPP board matches the number of
PCMs.
5.
If the remote rack is only configured with an FM shelf and the connected BATC
does not exist, the following phenomenon will appear: the TIC in the FM is
configured to connect to the TIC in NM. But after the command is executed
successfully, no connection relationship exists in the reversed script. The reason
is that BATC is not configured. This case is normal, and the user can continue to
complete the configuration.
6.
It is recommended that an NM shelf correspond to an FM shelf.
[Verification]
71
2.3.14Configuring the CBC

[Objective]
This section introduces how to configure the CBCOP and the X25 of BSC.
[Preliminary setup]
[Required steps]
1.
Configure CBCOP.
2.
Configure X.25.
3.
Configure the cell to support CBC.
1.
Configure CBCOP
Select the node [BSC Equipment] in [PhyView], right-click and select [Edit
CBCOP] menu, as shown in Fig. 2.3-96.
Fig. 2.3-96 Selection of [Edit CBCOP] Menu
Edit the CBCOP record in the pop-up interface, as shown in Fig. 2.3-97.
72
Fig. 2.3-97 [Edit CBCOP] Dialog Box
2.
X.25 configuration
Select the [PCOM] board on the BSC rack. Right-click and select [Board
Properties] menu to pop up a dialog box. Select [Configure X.25 parameter], as
Fig. 2.3-98 Edit X.25 Dialog Box
Of these, the parameter [CBCAddressCount], only [Basic address of CBC]; if

the parameter [CBCAddressCount] is 2, the parameter [No. 2 address of CBC] is
also valid.
3.
Configure the cell to support CBC.
73
Select the [Cell] node in radio view, right-click and select [Cell Radio
Information] menu option.
Pops up the Properties interface of Edit cell and select the [Support CBC]
parameter, as shown in Fig. 2.3-99.
Fig. 2.3-99 Selection of Cell Support CBC
Click <OK> to save the changes. ICE will automatically changes the channel
combination type, thus satisfying the cell to support CBC, to ensure that there is
only one CBC channel in the cell, as shown in Fig. 2.3-100.
Fig. 2.3-100 CBC Channel Configuration
[Verification]
74
2.3.15Configuring the Super Large Size Cell

[Objective]
This section introduces how to configure the extended cell.
In the GSM protocol, the maximum access diameter of the GSM900 system is 35km.
To enable the common GSM mobile phone to conduct normal conversation within the
range of over 35km, the ZXG10-BSS (V2) uses the related technology, implementing
the function of extended cell.
A simple implementing method is: Complete the function of one channel using two
time slots. In this way, the coverage range of the cell can be guaranteed from 0km to
120km in the radio mode to satisfy the requirements.
If the coverage area the GSM900 system has a diameter more than 35km, the access
burst received at the base station will span two time slots upon sending the channel
request by a mobile phone. Therefore, the control channel needs to use two physical
channels, that is two consecutive time slots.
The maximum value of the advanced time TA on the radio interface for MS should be
63. When the air delay value is larger than 63, the time for signals to arrive the base
station will span two time slots, therefore, the dedicated control channel also uses two
adjacent channels. In addition, the service channel of one user also needs two adjacent
physical channels in terms of the asynchronous handover.
[Preliminary setup]
1.
Ensure that the physical and radio data of MSC, BSC, SITE have been
configured.
2.
The client communicates normally with the server.
[Required steps]
1.
Configuring cell Properties.
2.
Configuring the BCCH carrier frequency property.
3.
Configure the non-BCCH carrier frequency as extension type on demands.

75
4.
Configure the exterior extended cell on demands.
1.
Configure the cell properties

In the radio view, select the cell, right-click and select [Cell Info], as shown in
Fig. 2.3-101.
Fig. 2.3-101 Modification of Cell Radio Information Menu Option
The pop-up interface is shown in Fig. 2.3-102.
Fig. 2.3-102 Configure the Extension Cell
76
Select the cell type as the extended cell type in the interface, and configure the
allowed value Ta according to demands, which is generally 127. Since the type
of extended cell is selected, the common control channel CCCH (Common
Control Channel) structure parameter automatically becomes 1 by default.
2.
Configure the BCCH carrier frequency property.

Select the BCCH carrier frequency under this cell, right-click and select [TRX
radio information] menu option. It is found that the number of service channel
automatically becomes 3 after popping up the interface, and then the Trx type is
set to be extension, as shown in Fig. 2.3-103.
Fig. 2.3-103 Configure the Extension BCCH Carrier Frequency
3.
Configure the non-BCCH carrier frequency as extension type on demands.

Select the BCCH carrier frequency under this cell, and the edit property is
77
Fig. 2.3-104 Configure non-BCCH Carrier Frequency as Extension Type
4.
Configure the exterior extension cell on demands.

Select the exterior cell in radio view, right-click and select [External Cell Info]
menu option to pop up the interface, as shown in Fig. 2.3-105. In this interface,
modify cell type as the extension type, right-click <OK> to save the changes.
Fig. 2.3-105 Configure the External Extension Cell
[Verification]
78
2.3.16Configuring the Related Cell

[Objective]
This section introduces how to configure the related cell.
[Preliminary setup]
Confirm that the MSC, BSC, radio sites and cells have been configured.
[Required steps]
1.
Select a cell node and the [Edit AdjCell] menu.
2.
Configure the related cell
In the radio view, right-click the [Cell] node to pop up the menu as shown in Fig. 2.3106.
Fig. 2.3-106 Configure the Adjacent Cell (1)
In the right-click menu, select [Edit the adjacent cell] to pop up the interface for editing
the adjacent cell, as shown in Fig. 2.3-107.
79
Fig. 2.3-107 Configure the Adjacent Cell (2)
Which kind of related cell to be configured can be selected. A kind of related cells can
be created through the menu, such as [Create Handover and Reselection Cell] and
[Create Interference Cell].
[Verification]
80
2.3.17Configuring the Adjacent Cell Handover and Reselection

[Objective]
This section introduces how to configure the adjacent cell handover and reselection.
[Preliminary setup]
Confirm the configured MSC, BSC, BTS, wireless BSC, wireless sites and cells.
[Required steps]
Two modes are available to configure the adjacent cell handover and reselection:
1.
Configure in the related cell interface as introduced in Section 2.3.16.
2.
Create through the [Create Handover and Reselection Cell] menu.
In [RadioView], click to select the cell node and right-click, the following interface
will be shown in Fig. 2.3-108.
Fig. 2.3-108 Configure Handover and Reselection Cell - Menu Option
81
Fig. 2.3-109 Configure Handover and Reselection Cell--Parameter Configuration
The user selects [Setup opposite Handover and Reselection Cell] to right-click
<OK>, and ICE automatically configures the current cell handover as the
corresponding cell and reselect the cell.
[Verification]
82
2.3.18Configuring the External Cell

[Objective]
This section introduces how to configure the external cell.
[Preliminary setup]
Confirm that the MSC, BSC, BTS and radio BSC have been configured.
[Required steps]
1.
Select the menu option for creating external cell radio information.
2.
Edit the external cell radio information.
1.
Select the menu option for creating external cell radio information.
In the [RadioView], right-click on the [Physical equipment] node to pop up the
menu as shown in Fig. 2.3-110.
Fig. 2.3-110 Configure the External Cell (1)
2.
Edit the external cell radio information

In the pop-up menu, select [Create external cell information] to pop up the
interface for editing the external cell, as shown in Fig. 2.3-111.
83
Fig. 2.3-111 Configure the External Cell (2)
In editing the exterior cell alias, if the user input is empty, the ICE will
automatically edit the exterior cell alias as Ecell+Exterior Cell No. in saving
its records .
[Verification]
84
2.3.19Configuring the Frequency Hopping

[Objective]
This section introduces how to configure the frequency hopping.
[Preliminary setup]
Confirm the configured MSC, BSC, BTS, wireless BSC, wireless sites and cells.
[Required steps]
1.
Configure the frequency hopping system.
2.
Configure the Trx to support the frequency hopping.
3.
Configure the channel index offset value.
1.
Configure the frequency hopping system.

Select the cell node, right-click to select the [Create Frequency Hopping] menu
option, as shown in Fig. 2.3-112.
Fig. 2.3-112 Configure Frequency Hopping Create the Frequency Hopping System Menu
85
The dialog box pops up, as shown in Fig. 2.3-113, edit the properties of the
frequency hopping group, right-click <OK> to save the changes, and add this
frequency hopping group node under this cell of the radio view.
Fig. 2.3-113 Configure the Frequency Hopping System
2.
Configure the Trx frequency hopping.

Select the non-BCCH transceiver under this cell, select the parameter
[Frequency Hopping], and select the hopping frequency group number, as
Fig. 2.3-114 Configure the Frequency Hopping - Frequency Hopping Point
86
3.
Configure the channel index offset value.

Select a piece of record from the channel list, right-click <Modify>, as shown in
Fig. 2.3-115:
Fig. 2.3-115 Modify the Channel Parameter
[Verification]
87
2.3.20Configuring the GPRS Data

[Objective]
This section introduces how to configure the GPRS data.
[Preliminary setup]
[Required steps]
1.
Configure the GPRS shelf
2.
Configure the BRCH.
3.
Configure the NSE and NSVC.
4.
Configure the GPRS cell
5.
Configure the GPRS transceiver
1.
Configure the GPRS shelf

In [PhyView], select the base station equipment and select the [Add Rack] menu
in the pop-up menu to pop up the dialog box shown in Fig. 2.3-116.
Fig. 2.3-116 Dialog Box for Adding Racks
88
Select the GIU and SPCU shelf and then click <OK> as shown in Fig. 2.3-117.
Fig. 2.3-117 Add the Rack Including the GIU and the SPCU
In Fig. 2.3-117, right-click the PUC board, as shown in Fig. 2.3-118.
Fig. 2.3-118 Configure the PUC (1)
In the pop-up menu, select the [Add Board] menu to pop up the dialog box as
89
Fig. 2.3-119 Configure the PUC (2)
In Fig. 2.3-117, right-click the FRP, as shown in Fig. 2.3-120. In the pop-up
menu, select the [Add Board] menu. Then the FRP board can be added.
Fig. 2.3-120 Add the FRP Board
In Fig. 2.3-120, right-click the BRP, as shown in Fig. 2.3-121. In the pop-up
menu, select the [Add Board] menu. Then the BRP board can be added.
90
Fig. 2.3-121 Add the BRP Board
2.
Configure the BRCH

Configure the TIC and the BRCH of the Gb. Select the TIC of the GIU shelf,
and right-click to select the [Add Board] menu to pop up a dialog box as shown
in Fig. 2.3-122.
Fig. 2.3-122 Configure the TIC with GB Interface
Click [Configure BRCH] to display the following dialog box, as shown in Fig.
2.3-123.
91
Fig. 2.3-123 Configure BRCH (1)
Select [PUC Location of BRCH] as shown in Fig. 2.3-124.
Fig. 2.3-124 Configure BRCH (2)
3.
Configure the NSE and the NSVC

In [PhyView], right-click on the [BSC Equipment] node to pop up the menu as
92
Fig. 2.3-125 Configure NSVC (1)
In the right-click menu, select [Edit NSVC] menu to pop up a dialog box for
editing the NSE, as shown in Fig. 2.3-126.
Click the [Add NSVC] button to pup up a dialog box for editing NSVC, as
93
4.
Configure the GPRS cell

Select the [Logic Site] node, and right-click to select the [Cell Info] as shown in
Fig. 2.3-128. If the cell serves as a GPRS cell, select [Support GPRS].
Fig. 2.3-128 Configure a GPRS Cell (1)
In this way, the relevant parameters of the GPRS cell can be configured. The
GPRS cell option page is shown in Fig. 2.3-129.
94
Fig. 2.3-129 Configure a GPRS Cell (2)
5.
Configure the GPRS Transceiver

Right-click the [Cell] node to pup up the menu. Select the [Edit TRX radio
information] menu to edit the relevant parameters of the GPRS Transceiver, as
Fig. 2.3-130 Configure GPRS Transceiver
Select a piece of record from the channel list, right-click <Modify>, and the
interface for modifying the channel property pops up. The [TCH/F] can be set as
dynamic channel, as shown in Fig. 2.3-131.
95
Fig. 2.3-131 Configure a Dynamic Channel
[Verification]
96
2.3.21Exporting the Configuration Data

[Objective]
This chapter introduces how to export the configuration data required by the physical,
radio, software and network rule.
[Preliminary setup]
1.
Confirm that the data have been configured in the system.
2.
[Required steps]
1.
Select the configuration for export menu.
2.
Select the table to be exported.
3.
Export data.
1.
Select the configuration for export menu.

Select the [CM Database export] menu, as shown in Fig. 2.3-132.
Fig. 2.3-132 Menu for Data Export Configuration
2.
Select the table to be exported.

Click to select the menu, and the [Configuration database export] interface pops
up, as shown in Fig. 2.3-133.
97
Fig. 2.3-133 Configuration Database Export Interface
Select the BSC and table name to be exported.

3.
Export data
Click <Print Report> to export the configuration data, as shown in Fig. 2.3-134.
Fig. 2.3-134 Configure the Report Export
[Verification]
Correctly generate the configuration report.
98
2.4Wireless Resources Management

The radio resource management provides the detailed radio parameter configuration
interface.
The objects of radio resources in the BSC system are as follows: Base Station
Controller (BSC), Site, Base Transceiver Station (BTS), Transceiver (TRX), Radio
Carrier, Logic Traffic Channel (CHANNEL), Handover Control parameter (HOC),
Power Control parameter (POC), Adjacent Handover Cell (AHANDOVERCELL),
Adjacent Reselection Cell (ARESELECTCELL), Adjacent Handover & Reselection
Cell (AHO&RESELECTCELL), Interference Cell (ICELL), External Cell (ECELL),
Logic PCM (PCMCIRCUIT), Logic LAPD Link (LAPDLINK) and Frequency
Hopping System (FHS).
2.4.1Modifying the BSC

[Objective]
This section introduces how to use the radio resource management to modify the BSC
parameters.
[Preliminary setup]
Confirm that the MSC and BSC have been configured.
[Required steps]
1.
Enter the main interface for radio resource management.
2.
Select the menu option.
3.
Modify parameters.
4.
Save the changes.
1.

On the OMCR (V2) main interface, select the [Configuration Management
Radio Resource Management] option, and the system will enter the [ZXG10
Radio Resource Management] interface, as shown in Fig. 2.4-135.
99
Fig. 2.4-135 Main interface of Radio Resources Management
2.
Select the menu option

Right-click on [BSCModify], as shown in Fig. 2.4-136.
Fig. 2.4-136 Modify the BSC - Menu Option
3.
Modify the parameters and save the changes

The [Basic Properties] setting of the BSC in GSM is shown in Fig. 2.4-137 and
that in GPRS is shown in Fig. 2.4-138.
100
Fig. 2.4-137 Modify the BSC - GSM
Fig. 2.4-138 Modify the BSC - GPRS
4.
Save the changes

Click <OK> to save the changes. The interface shown in Fig. 2.4-139 will pop
up upon success.
101
Fig. 2.4-139 Modify the BSC - Success
[Verification]
View the modified data.
102
2.4.2Modifying the Parameters of the Logical Site

[Objective]
This section introduces how to use the radio resource management to modify the
parameters of the logical site.
[Preliminary setup]
1.
Confirm that the MSC, BSC, SITE, radio BSC and logical sites have been
configured.
2.
[Required steps]
1.
2.
Modify and save the parameter.
1.

Select the logical site node to be modified in the navigation tree, right-click and
select the [Modify] menu to pop up the interface, as shown in Fig. 2.4-140.
Fig. 2.4-140 Configure the Logical Site
103
2.
Modify and save the parameter.

Modify the parameter, click <OK> to save the changes, and the interface for
prompting modification success, as shown in Fig. 2.4-141.
Fig. 2.4-141 Successful Modification
[Verification]
104
2.4.3Modifying the Cell Parameters

[Objective]
This section introduces how to modify the cell parameters.
[Preliminary setup]
1.
Confirm the configured MSC, BSC, SITE, wireless BSC, logical sites and cells.
2.
[Required steps]
1.
2.
Modify parameters.
3.
Save the changes.
In the navigation tree, select the cell node to be modified, right-click and select the
[Modify] menu, as shown in Fig. 2.4-142.
Fig. 2.4-142 Modify the Cell - Menu Option
105
Modify the parameters, as shown in Fig. 2.4-143.
Fig. 2.4-143 Modify the Cell Parameters
Click <OK> to save the changes. The interface shown in Fig. 2.4-144 will pop up upon
success.
Fig. 2.4-144 Cell Modification Success
[Verification]
106
2.4.4Modifying the Power Control

[Objective]
This section introduces how to modify the power control.
[Preliminary setup]
1.
2.
[Required steps]
1.
2.
Modify the power control parameter
3.
Save the changes.
1.

In the navigation tree, select the power control parameter to be modified, rightclick and select the [Modify] menu, as shown in Fig. 2.4-145.
Fig. 2.4-145 Modify the Power Control - Menu Option
107
2.
Modify the power control parameter

Modify the power control parameter, as shown in Fig. 2.4-146.
Fig. 2.4-146 Modify the Power Control
3.
Save the changes

up upon success.
Fig. 2.4-147 Power Control Modification Success
[Verification]
108
2.4.5Modifying the Handover Control

[Objective]
This section introduces how to use the radio resource management to modify the
handover control parameter.
[Preliminary setup]
1.
2.
[Required steps]
1.
2.
Modify the handover control parameter
3.
Save the changes.
1.

In the navigation tree, select the handover control to be modified, right-click and
select the [Modify] menu, as shown in Fig. 2.4-148.
Fig. 2.4-148 Modify the Handover Control - Menu Option
109
2.
Modify the handover control parameter,

Fig. 2.4-149 Modify the Handover Control Parameter
3.
Save the changes.

up upon success.
Fig. 2.4-150 Handover Control Modification Success
[Verification]
110
2.5Loading the Software

The software loading provides upgrade and loading of the board software in the
ZXG10-BSC, ZXG10-BTSV1.0, ZXG10-BTSV1.0(A), ZXG10-BTSV2.0, ZXG10
BS21, ZXG10 BS30, ZXG10 BS30V1.2 and ZXG10-MB/EMB, making it unnecessary
to upgrade and load the software on site. It facilitates management of the GSM
equipment, provides the software version management function and has the concurrent
processing capability. Multiple boards can be loaded simultaneously, thus greatly
reducing the loading time and expedite the loading of boards.
2.5.1Overview of Software Loading Flow

The client software loading is a flow comprised of the operations such as selecting the
software version, storing the software into the database, setting general software
(including creation, modification and deletion), setting the software of a single board
(including creation, modification and deletion), loading general software, loading the
board software and querying the foreground running software.
Software loading flow is shown in Fig. 2.5-151.
Fig. 2.5-151 Software Loading Flow
1.
Select the software version

Select the software version according to different needs. The software version
information includes software ID and software version No.
2.
Storing software
111
The software must be stored first, and then it can be loaded. . When the software
is put into the database, the corresponding software should be saved under the
directory with the shared name "Version" on the OMCR (V2) server and copied
to the MP of the corresponding BSC module. The related version information is
written in the foreground and background databases.
3.
Set general software

Setting the general software is to create, delete or modify the software version
record of general software. After general software is set, the software loading
operation can be performed on the same type of software.
4.
Load general software

Notify the MP of loading general software to all boards running this software so
that all boards run this type of software, thus greatly improving the software
loading efficiency. To enhance the speed in software loading, the files stored on
the MP will be used in priority during the loading of the BSC board, BTS and
MB equipment. Only when the MP does not contain the required files, will the
files be requested from the background server.
After version updating, if the new version can not correctly started or has serious
faults due to some reasons, the system might break down. Therefore, the old
version should be saved before updating the version. When the above situation
occurs, use the old version to restore the system.
5.
Set the board software.

Setting the board software is to create, modify or delete the board software
version of a destination board. This record is the foundation for loading the
software of a single board.
6.
Load the board software.

Notify the MP of loading the set board software to a specified destination board
so that this software is run. The board software has a higher priority than general
software. When the board has been loaded with general software, if the board
software is loaded, the board will run the loaded board software.
After the board software is loaded, if it is necessary to run the type of software
loaded before, just delete the board software of this board.
7.
View the foreground running software

112
It transmits the query command to a foreground board, and the board returns its
operation version No. to the OMCR (V2) server, which will be transferred and
displayed on the client by the server.
After the user succeeds in log-on, he /she can select the [Configuration
ManagementSoftware Loading] on the main interface to access the main
interface for software loading, as shown in Fig. 2.5-152.
Fig. 2.5-152 Software Loading Main Interface
1)
The menus on the menu-bar are:
Operation: This is a dynamic menu, and the menus vary with the contents
clicked by the mouse, including [Load software to database], [Delete Stored
Software], [Create Version], [Modify Version], [Query Version], [Delete
Version], [Load Version].
View: [Logical View], [PhyView], [Toolbar], [Status Bar], [Command Box],
[Unfold], [Fold], [Unfold All], [Fold All], and [Refresh].
Help: [Software Loading Help], [Directory and Index], [About].
2)
The tool buttons from left to right on the toolbar are: [Handover View],
[Unfold], [Fold], [Unfold All], [Fold All], [Refresh], [Help] and [Exit]. All the
buttons on the toolbar have the corresponding options in the menu.
113
3)
The navigation tree is shown on the left of the main window. After the
navigation tree is unfolded, in the physical view, all [BSC Equipment] and racks
under [GSM Equipment] and [Physical Site] and racks managed under the NM
domain are displayed; in the logic view, the two subnodes: [Version Stored in
Database] and [General software] under [GSM Equipment] node managed under
the NM domain are displayed.
4)
The command box (the character input interface) is in the lower part of the
interface, and the user can directly input the MML command in it to complete
some operations. When the interface operation is performed, the relevant MML
command will be displayed in the command box. It is necessary to point out,
except the multiplexing command, only the command related to the software
loading can be input in the software loading application window.
2.5.2Selecting the Software Version

The version information includes software ID and software version. Use the tool such
as UltraEdit to edit the hexadecimal software file. Open a software file to be stored in
the database, and the final part of the file is the software version information, as shown
in Fig. 2.5-153.
Fig. 2.5-153 Software Version Information
114
BSC_BOSN in the file is software ID, and 02.50.01.05 is the software version. When
the software is stored in the database, its version information can also be known from
the interface (see Fig. 2.5-157).
2.5.2.1Software ID
The software ID is used to indicate the software usage, defined in prefix_usage
mode. The prefix includes BSC and BTS, indicating whether this software belongs to
BSC or BTS; the fields hereinafter indicates where this software is used, which is
usually represented by board name, as shown in Table 2.5-1.
115
Table 2.5-1 List of Software ID and Usage

Software ID
Purpose
BTS_BIE
Physical site interface equipment unit
BTS_CHP
Channel processor
BTS_CKU
Clock panel
BTS_CMM
Common management module
BTS_CUI
CF interface
BTS_EAM
Environment alarm panel
BTS_DSP0
Micro cell: DSP0, belonging to TRU panel
BTS_DSP1
Micro cell: DSP1, belonging to TRU panel
BTS_FUC
Frame unit controller
BTS_RCU
Micro cell:RF interface unit
BTS_SCU
Micro cell: Signaling control unit board
BTS_OMU
Operation and maintenance unit software
BTS_CHP
Channel processor software
BSC_EDRT
Enhanced DRT
BSC_EFREN
The DSP version on EDRT
BTS_FUC
Frame unit controller software
BSC_MP
Module processor software
BSC_SMB
Submiltiplexing board software
BSC_SMT1
Submiltiplexing board 1 software
BSC_SMT2
Submiltiplexing board 2 software
BSC_DRT
Dual rate transcoder board software
BSC_DTI
Digital trunk software
BSC_FR
Full-rate voice-coded DSP algorithm
BSC_HR
Half-rate voice-coded DSP algorithm
BSC_EFR
Enhanced full-rate voice/data circuit
BSC_MTPEN
Enhanced No.7 signaling board
BSC_IPCBEN
The MPPP communication board on ECOM board
BSC_GPP
General peripheral processor
BSC_BOSN
Bit oriented switching network
BSC_LAPDEN
Enhanced LAPD signaling board
116
2.5.2.2Software Version
The software version is formed by four fields, and each field contains two digitals,
appeared as HH.VV.FF.XX.
Meanings of each field are as follows:
1.
HH: A number related to the hardware platform, ranging from 00 to 99. For
certain software, the HH value will keep constant unless the software is
modified due to the modification of the hardware platform on which it is
running.
2.
VV: The version number independent of the hardware platform, ranging from 00
to 99. The value of VV defines main functions of the software. If there is
structural adjustment in software, VV should be updated.
3.
FF: The version number independent of the hardware platform, ranging from 00
to 99.FF value defines the local functional features of the software, if they are
added or modified, FF will be upgraded.
4.
XX: The version number independent of the hardware platform, ranging from 00
to 99. If the software itself remains unchanged both structurally and
functionally, and only some errors and BUGs are corrected, XX should be
upgraded.
5.
In the interface for storing the software in the database (as shown in Fig.2.5-7),
HH.VV.FF is displayed in the left of the corresponding version No. box in the
interface, and XX is displayed in the right of the version No. box. The meaning
of XX is indicated by letters. For example, XX indicates a when assuming
00, XX indicates b when assuming 01,XX indicates z when
assuming 25, XX indicates A when assuming 26, XX indicates Z
when assuming 51, XX indicates formal version when assuming 99. The
numbers from 52 to 98 are undefined.
For example, the software version of the BOSN is 02.50.01.05 as shown in
Fig. 2.5-153, but the software version No. shown on the interface is 02.50.01f,
as shown in Fig.2.5-7.
117
2.5.3Storing the Software into the Database

[Objective]
Associate BSC, DSP and GPRS with BTS (including ZXG10-BTSV1.0 and ZXG10BTSV1.0).
(A) Store the software of the ZXG10-BTSV2.0, ZXG10-BS21, ZXG10-BS30, ZXG10BS30V1.2 and ZXG10-MB/EMB into the corresponding module, which is the basis for
setting general software and the board software.
[Preliminary setup]
1.
The client communicates normally with the server. So does the BSC in the
foreground and the background servers.
2.
The software relevant to BSC, DSP, GPRS and BTS to be stored into the
database is available.
[Required steps]
1.
Click the [Version Stored into Database] node on the navigation tree in the logic
view or the node of the software that has been stored into the database and select
the [Store Software].
2.
In the window popped up, select the needed interface for storing the software
into the database.
3.
Browse different software versions and store the software into the database.
1.
Start the software loading and switch to the logic view, as shown in Fig. 2.5-154.
118
Fig. 2.5-154 Logic View
Select the [ZTE CorporationDomainGSM EquipmentVersion Stored into

Database] node on the navigation tree in the left of the view, right-click and
select [Store Software] to pop up all windows for storing the software into the
database, as shown in Fig. 2.5-155.
Fig. 2.5-155 Load the Software
Alternatively, right-click on the node of the software that has been stored into
the database under [Version Stored into Database] and select [Store Software] to
119
pop up the window for storing this software into the database, as shown in Fig.
2.5-156.
Fig. 2.5-156 Store a Single Software into the Database
2.
In the interface for storing the software into the database, according to different
requirements as shown in Fig. 2.5-155, select the tabs for storing the BSC
software, DSP software, new GPRS software or relevant BTS software
(including the BTSV1.0/BTSV1.0A software, BTSV2.0/BS21/BS30/ software
and MB/EMB software) into the database. Each tab has upper and lower
windows. In the upper window, the user can browse the software directories and
search the software under them; in the lower window, the user can browse the
directory of a single software and select a version.
3.
Because the software of the same type of boards is usually saved in the same
path, the path of the software of the same type of boards can be selected in the
upper window. Click <Auto Search>, the relevant software under this path will
be searched out and the corresponding version No. and path will be shown in the
lower window. The operations are as below:
1)
First select the check box of the software to be searched in the upper window,
then click <Browse> on its right to find the root path where the software version
is located, and add it to the [Root Path] text box.
2)
Click <Auto Search> on the interface, the system will search on the basis of the
root path in the upper window and configure the searched software version to
the relevant board as shown in Fig. 2.5-157.
120
Fig. 2.5-157 Auto Search
Due to the auto-search, the system will configure the first searched suitable
software version to the relevant board; but, there may be more suitable software
versions under the root directory, so you can modify a certain software
separately and manually in the lower window, or click <Browse> and select the
actual path to find out the software version that really needs storing.
3)
Alternatively, directly click <Browse> in the lower window to select the

corresponding software under the specific path and then judge whether the
shown version No. corresponds to the requirement.
4)
The module No. of the new BSC, DSP and GPRS software does not need to be
selected since it is specified to 1. In the case of the BTS, the modules to be
configured also need to be selected to determine the applicable scope of the
software, as shown in Fig. 2.5-158.
121
Fig. 2.5-158 Store the Relevant BTS Software into the Database
5)
Finally, click <Store Software> and a prompt will be given for either success or
failure.
6)
Click <Exit> to return to the software loading interface. The versions of the
software that have been stored into the database can be seen with the version
browsing.
[Verification]
122
2.5.4Setting General Software

[Objective]
Setting the versions of general software is to create, modify or delete the software
versions of the same type, which is the basis for loading general software. Loading of
general software is to load the software in batch for all boards using this software.
[Preliminary setup]
1.
2.
The software version to be set has been stored into the database.
[Required steps]
1.
Query the software version recorded in the database.
2.
Select the node of general software in the logic view.
3.
Create general software.
4.
If general software has been created, select such operation as [Modify Version].
1.
Start the software loading, switch to the logic view and select the [ZTE
CorporationDomainGSM EquipmentGeneral Software] node on the
navigation tree on the left in the view to browse the version information of all
the existing types of software, including BSC No., big type, board type, software
version and module No., as shown in Fig. 2.5-159.
123
Fig. 2.5-159 Query the Version of General Software
2.
Right-click on the [General Software] node and select the [Create Version] menu
to pop up the window for creating general software, as shown in Fig. 2.5-160.
1)
Select the big types (inclduing BSC_PP, BSC_DSP and BTS_SITE).
2)
Select the board type (equal to software ID).
3)
Select the software version that will be set on the selected module in BSC.
4)
In the case of the BTS software, select the module No. and site type also, as
5)
Click <Create> to create the selected software version. If the create operation is
successful, the server will send a broadcast message, notifying all clients of the
successful creation; otherwise, the system will give a prompt of failure in the
interface. Click <Return> to return to the interface shown in Fig. 2.5-159.
124
Fig. 2.5-160 Create General Software of BSC
Fig. 2.5-161 Create General Software of BTS
3.
After the version of general software is created, click the node of the type of
software on the navigation tree and right-click. Two menus are available,
including [Modify Version] and [Load Version]. Their interfaces are similar to
those in Fig.2.5-10. The difference is that <Create>changes to <Modify> or
<Load>. Click the button to complete the corresponding operation.
[Verification]
125
2.5.5Loading General Software

[Objective]
Loading general software is to load the software in batch for all boards using this type
of software so that they run the same type of software.
[Preliminary setup]
1.
2.
The version of general software has been correctly set, including creation (or
modification) of the version of general software.
[Required steps]
1.
In the logic view, select the node of general software to be loaded.
2.
Select the [Load Version] operation.
1.
Start the software loading, switch to the logic view and select the [ZTE
CorporationDomainGSM EquipmentGeneral Software] node on the
navigation tree on the left in the view. If the type of software has been set, the
three subnodes are [BSC_PP], [BSC_DSP] and [BTS_SITE]. The subnodes
shown under the three subnodes indicate that the software ID of the type of
software has been set, as shown in Fig. 2.5-159.
2.
Right-click on the software ID node of general software to be loaded and select

the [Load Version] menu to pop up the window for loading the type of software,
126
Fig. 2.5-162 Load General Software
Click <Load> to complete the corresponding operation. The corresponding

prompt will be given for either success or failure.
[Verification]
127
2.5.6Setting the Board Software

[Objective]
Creating, deleting or modifying the board software version for a designated destination
board is the basis for loading the board software.
[Preliminary setup]
1.
2.
The board software to be set has been stored into the database.
[Required steps]
1.
2.
Select the board under the base station equipment or physical site.
3.
Download the board software.
4.
If the board software has been created, the operation such as [Modify Version],
[Delete Version] and [Query Version] can be selected.
1.

Double click the [ZTE CorporationDomainGSM EquipmentVersion
Stored into Database] node on the navigation tree in the logic view, and the
software versions recorded in the database will be shown in the right list. Select
the node of software stored into the database under the [Version Stored in
Database] node, the corresponding software version information will be shown
in the right list, as shwon in Fig. 2.5-163. View the software version information
of BSC_GPP.
128
Fig. 2.5-163 Browse the Software
In this window are listed the information of the software stored into the
database, such as module No., file name (software ID), software version, file
length and file path. If the software to be set is not stored in the database, it shall
be first stored.
2.
The software versions of the boards on the BSC and the physical site are directly
set in the rack view. Only after the board software version of the designated
board is created, can the software version be queried, modified or deleted and
can the software be loaded for this board.
The system provides the rack views of the BSC and the physical site, select the
[ZTE CorporationDomainGSM EquipmentBSC EquipmentRack] or
[ZTE CorporationDomainGSM EquipmentPhysical SiteRack] node on
the navigation tree on the left in the physical view, the corresponding rack view
is shown in the right interface, as shown in Fig. 2.5-164. Select the board for
software setting in the rack view.
1)
The BSC (V2.0) rack contains the following boards for software setting: AIPP,
BIPP, NSPP, FSPP, TCPP, BOSN, DRT, GIPP, BRP, FRP and PUC.
2)
BTSV1.0 and BTSV1.0A racks contain the following boards for software
setting: OMU and TRU.
3)
BTSV2.0, BS21, BS30, and BS30V1.2 racks contain the following boards for
software setting: CMM and TRM.
129
4)
MB and EMB racks contain the SCU boards for software setting.
3.
Right-click on the board to be stored into the database. If this board has no
software setting (as shown in Fig. 2.5-164.), select the [Create Version] menu for
creation; otherwise, the [Modify Version], [Query Version], [Delete Version] and
[Load Version] menus would be shown for the corresponding operations of
modifying, deleting and querying the software version, as shown in Fig. 2.5-165.
Fig. 2.5-164 Software Setting (1)
130
Fig. 2.5-165 Software Setting (2)
The interfaces for creating, modifying and deleting the board software versions
are basically the same. Their difference is that <Create>, <Modify> and
<Delete> are used as the operation buttons. The board software setting is
introduced below with the BOSN and DRT boards used as examples.
131
1)
BOSN software setting

Right-click on the BOSN board. If its board software is not created yet, the
[Create Version] and [Query Running Version] menus are popped up in the
interface; otherwise, the [Modify Version], [Query Version], [Delete Version],
[Load Version] and [Query Running Version] menus would be shown. Take an
example for the case that the board software is not created yet. Select the [Create
Version] menu to pop up the window, as shown in Fig. 2.5-166(only one
diagram is provided because the interfaces for creation, modification, deletion
and loading are the same and only their command buttons are different).
Fig. 2.5-166 Create the BOSN Software Version
The information of the selected board in the rack view (here is the selected
BOSN board) is presented at the upper part of the window, including [BSC ID],
[Module No.], [Munit No.], [Unit No.], [Port No.], [Type], [Rack No.], [Shelf
No.] and [Slot No.]. The current configuration software version of this board is
given in the [Current Version] box.
Select the version to be updated in the [Update Version] box in the lower part of
the window, and click <Create>. The new software version can thus be created.
132
If the create operation is successful, the system will send a broadcast message,
notifying all workstations in the system that this software version is successfully
created; if the create operation fails, the system will give a prompt of failure in
the interface.
Click <Return> to return to the rack view interface shown in Fig. 2.5-164.
2)
DSP software setting

Except the board software, the DSP board software should also be set for the
DRT and BRP boards. Right-click on the DRT or BRP board. If the DSP
software is not set, the [Create Version], [Query Running Version], [Create DSP
Version] and [Query Current DSP Version] menus will be shown. If the DSP
software has been created, the [Modify DSP Version], [Query DSP Version],
[Delete DSP Version], [Load DSP Version] and [Query Current DSP Version]
menus will be shown. Take an example for the case that the DSP software is not
created. Select the [Create Version] menu to pop up the [DSP Software Setting]
window, as shown in Fig. 2.5-167 (only one diagram is provided because the
interfaces for creation, modification, deletion and loading are the same and only
their command buttons are different).
Fig. 2.5-167 DSP Software Setting
133
The software information is presented at the upper part of the interface,

including [BSC ID], [Module No.], [Munit No.], [Unit No.], [Rack No.], [Shelf
No.] and [Slot No.].
Select the DSP No., and the current version information of this DSP will be
shown under it. Select the version to be updated in the [Update Version] box in
the lower part of the window, and click <Create>. The new software version can
thus be created. If the create operation is successful, the system will send a
broadcast message, notifying all workstations in the system that this software
version is successfully created; if the create operation fails, the system will give
a prompt of failure in the interface. Click <Return> to return to the rack view
interface as shown in Fig. 2.5-164.
4.
After the version is created, click this board and right-click. The right-click
menu is shown in Fig. 2.5-165. The [Modify Version], [Query Version], [Delete
Version] and [Load Version] menus are available to perform other setting
operations. For detailed procedures, refer to the operation of creating the version
in step 3.
[Verification]
134
2.5.7Loading the Board Software

[Objective]
Notify MP of loading the set board software to a designated destination board. The
priority of the board software is higher than general software. If a board is loaded with
the board software after being loaded with general software, the board software will be
run.
[Preliminary setup]
1.
2.
The software version has been set for the board to be loaded with software.
[Required steps]
1.
In [PhyView], click the rack node of the base station equipment or physical site,
and select the board to be loaded in the rack view.
2.
Right-click and select the [Load Version] menu to perform the loading
operation.
1.
In [PhyView], select [ZTE CorporationDomainGSM EquipmentBSC

EquipmentRack]
or
[ZTE
CorporationDomainGSM
EquipmentPhysical SiteRack] node, and the rack view of the base station
equipment as shown in Fig. 2.5-168 or physical site as shown in Fig. 2.5-169
will be shown. Select the board to be loaded in the rack view.
135
Fig. 2.5-168 BSC Equipment Rack View
Fig. 2.5-169 Physical Site Rack View
2.
Right-click on the board and select the [Load Version] menu to perform the
loading operation. The pop-up window for the board of the base station
equipment is shown in Fig. 2.5-170, and that for the board of the physical site is
136
shown in Fig. 2.5-171. Select <Load> in the loading window. A prompt will be
given for either success or failure.
Fig. 2.5-170 Load the Software for the Board of the Base Station Equipment
Fig. 2.5-171 Load the Software for the Board of the Physical Site
[Verification]
137
2.5.8Setting the Software Version of the Physical Site

[Objective]
The software version setting of the physical site provides a convenient interface to
conduct the software version setting for the boards of all racks under this site, leaving
out the board selection.
[Preliminary setup]
1.
2.
[Required steps]
1.
Select the [Physical Site] node on the navigation tree on the left in the physical
view and select the [Create Version] menu.
2.
Select a different version to create the board software under the physical site.
3.
After the board software is created, select the modification or deletion operation.
1.
The software loading of the physical site (including the microcell physical site)
is different from that of the BSC. Select the [ZTE CorporationDomainGSM
EquipmentPhysical Site] node on the navigation tree in the physical view,
right-click and select the [Create Version] menu. The interface is shown in Fig.
2.5-172.
138
Fig. 2.5-172 Software Setting of the Physical Site
2.
The [Software Info] box on the upper right part of the interface shows the BSC
number, site number and site alias of the selected physical site, while the
[Current Version] box on the lower right of the interface shows information
about the software versions currently used by it.
Select the version to be updated in the [New Version] box, and click the check
box corresponding to this software, as shown in Fig. 2.5-173. Click <Create> to
create all the board software of this physical site. A prompt will be given for
either success or failure.
139
Fig. 2.5-173 Create the Software Version of the Physical Site
3.
After the version is created, select the [ZTE CorporationDomainGSM

EquipmentPhysical Site] node on the navigation tree in the physical view.
Right-click and the [Modify Version] and [Delete Version] menus can be
selected for other setting operations. The interfaces for modification and deletion
are similar to those in Fig. 2.5-173, and the difference is that <Create> changes
to <Modify> or <Delete>.
[Verification]
140
2.5.9Loading the Software Version of the Physical Site

[Objective]
The software loading of the physical site provides a convenient interface to conduct the
board software loading for the boards of all racks under this site, leaving out the board
selection.
[Preliminary setup]
1.
2.
The board software version has been set for the physical site.
[Required steps]
1.
Select the [Physical Site] node on the navigation tree on the left, right-click and
select the [Load Version] menu.
2.
Select a different version (has been set) for software loading.
1.
The software loading of the physical site (including the microcell physical site)
is different from that of the BSC. Select the [ZTE CorporationDomainGSM
EquipmentPhysical Site] node on the navigation tree in the physical view,
right-click and select the [Load Version] menu. The interface is shown in Fig.
2.5-174.
141
Fig. 2.5-174 Software Loading of the Physical Site
2.
The [Software Info] box on the upper right part of the interface shows the BSC
number, site number and site alias of the selected physical site, while the
[Current Version] box on the lower right of the interface shows information
about the software versions currently used by it.
Select the board software version to be loaded in the [New Version] box, and
meanwhile selecting the check box corresponding to this software, as shown in
Fig. 2.5-175. And then click <Load> to load all the board software of this
physical site. A prompt will be given for either success or failure.
142
Fig. 2.5-175 Software Loading of the Physical Site
[Verification]
143
2.5.10Viewing the Foreground Running Version

[Objective]
Query the current foreground version run by the board, and observe whether the
software loading is normal and whether the version complies with the requirement.
[Preliminary setup]
1.
2.
General Software or the board software has been loaded.
[Required steps]
1.
Switch to the physical view, click the rack view of the base station equipment or
physical site.
2.
On the board with the software loading function, right-click to select [Query
Running Version].
1.
Select
the
[ZTE
EquipmentRack]
or
[ZTE
EquipmentBSC
EquipmentPhysical SiteRack] node on the navigation tree on the left in the

physical view, and the corresponding rack view will be shown in the right
interface, as shown in Fig. 2.5-14.
2.
Select the board for software loading in the rack view.
1)
The BSC (V2.0) rack contains the following boards for software setting: AIPP,
BIPP, NSPP, FSPP, TCPP, BOSN, DRT, GIPP, BRP, FRP and PUC.
2)
BTSV1.0 and BTSV1.0A racks contain the following boards for software
setting: OMU and TRU.
3)
BTSV2.0, BS21, BS30 and BS30V1.2 racks contain the following boards for
software setting: CMM and TRM.
4)
MB and EMB racks contain the SCU boards for software setting.
Right-click on the board with the software loading function. If this board has
been successfully loaded with general software or the board software, [Query
144
Running Version] is shown at the lowest part of the menu. Click it to query the
current running version of the board. If the query succeeds, the returned window
is shown in Fig. 2.5-176. If the query fails, the communication may be abnormal
or an error occurs in loading.
Fig. 2.5-176 Query the Foreground Running Version
[Verification]
145
2.5.11Handling of FAQ in Software Loading

The software loading is a complex task that involves the database operation, the
communication between the foreground and the background, and the version
management; it is required the excessive cooperation, thus, it can be brought into play
normally. Below are the problems easily occurred in the software loading:
1.
Unable to create or find files

The operations of software storing and loading are performed in a specified path
on the server. The specified path is designated by the client. A file directory
(usually tmp/ftp/version) needs to be created in advance during the
commissioning. If the version directory does not exist, all operations of software
storing cannot be completed, and the directory shall be created manually.
Sometimes, if the program is aborted abnormally (e.g., sudden power failure,
and restart), there is no time to close the files opened, some errors (e.g., files
cannot be created or some files cannot be deleted) may occur. At the time, you
can first get rid off the share from the relevant directory on the server, then, set it
as the share again.
2.
No response from the foreground or too many communication errors

Software loading needs to be implemented with the cooperation of both the
foreground and the background. Sometimes if the corresponding process in the
foreground has not been started or has errors, or a certain board is not plugged
firmly, or the power has not been turned on, it will be possible that the
foreground gives no response to the background messages. Another common
reason for this error is that the equipment data have not been configured
properly, i.e., the data in the database do not conform to the actual equipment in
the rack.
3.
The software loading failed again and again

The most possibility is in the board software itself that is unable to run normally,
or in the hardware failure. In this case, try other versions.
4.
An error message of Version ID or version No. is inconsistent with files is

displayed during the storing
146
To avoid loading a wrong version, the corresponding identification information

is also added to the version files, and this information will be checked during
storing or initializing version settings. If the files to be stored are inconsistent
with the inputted version ID or the version No., this error message will appear.
So this problem may be eliminated by entering the correct version information
and using the right version files.
5.
Data synchronization failure during software loading or storing

In this case, first check whether the communication link with MP is through. If it
is, then it is possible that the master MP is synchronizing data to the slave MP.
You need to wait for a while before performing operations.
2.6Dynamic Data Management

2.6.1Overview
The dynamic data management is to provide the function of dynamically managing
terrestrial and radio resources at the ZXG10-OMCR(V2) client to realize the dynamic
management of the terrestrial and radio resources statuses, including query, blocking,
unblocking, activation, deactivation, circuit installation, circuit uninstallation, reset,
channel statistics, functions related to FUC control and the operations related to GPRS
such as BVC blocking, BVC unblocking, BVC reset, BVC signaling reset and BVC
status query. Because most dynamic data management directly communicates with the
foreground, the background server needs to communicate well with the foreground.
2.6.2Querying the Dynamic Properties of the BSC

[Objective]
Query the dynamic properties of objects includes management status, operation status,
use status and tracing status
[Preliminary setup]
1.
2.
The foreground BSC communicates normally with the background server.
[Required steps]
1.
Select the object node with dynamic properties on the navigation tree.
147
2.
Select [Watch] in the corresponding right list.
1.
Select the terrestrial or radio resources under the [ZTE CorporationDomain]

on the navigation tree on the left at the client of dynamic data management. If
the list of dynamic properties is shown in the right interface, the resource has
dynamic properties and the query operation can be performed.
2.
Select a item in the right list, as shown in Fig. 2.6-177, right-click and select
[Watch]. If the operation is successful, the dynamic properties of the resource
are shown in the list; otherwise, an error message would be returned.
Alternatively, select all items in the list, right-click and select [Watch], as shown
in Fig. 2.6-178. If the operation is successful, the dynamic properties of all
selected resources are shown in the list.
Fig. 2.6-177 Watch the Dynamic Properties of a Single Item
148
Fig. 2.6-178 Watch the Dynamic Properties of All Items
The dynamic properties include management status, operation status, use status
and tracing status. The management status indicates the blocking/unblocking
status of the resources, the operation status indicates the enabling/disabling
status of the resources, the use status indicates whether the resources are usable,
and the tracing status indicates the dynamic observance of the resources.
149
2.6.3Automatically Obtaining or Updating the Status

[Objective]
Automatically obtain and query the dynamic properties of the resources or show the
statuses of the dynamic properties of the resources in the interface for auto periodic
update.
[Preliminary setup]
1.
2.
[Required steps]
1.
Select [Auto Obtain Status ] in the menu to set the auto obtain status.
2.
Select [Auto Update Status] in the menu to set the auto update status.
3.
Select [Refresh Frequency] in the menu to set the refresh frequency.
1.
Select [OptionAuto Obtain Status] in the main menu to set the auto obtain
status function. When the selection is made in the navigation tree on the left in
the interface, the corresponding resources in the right list will automatically
obtain the statuses of the dynamic properties if available and show them in the
list.
2.
Select [OptionAuto Update Status] in the menu to set the auto status update
function, if the list of resources with dynamic properties is shown in the right of
the interface, the statuses of the resources can be automatically and periodically
updated.
3.
The cycle of the auto status update can be set in the [OptionRefresh
Frequency] with the default cycle (the minimum cycle) being set to 10s, as
150
Fig. 2.6-179 Set the Refresh Frequency
2.6.4Blocking/Unblocking
[Objective]
Block or unblock the objects to be operated, and observe its change of dynamic
properties
[Preliminary setup]
1.
2.
[Required steps]
1.
Select the corresponding object node with blocking/unblocking on the

navigation tree and [Block] or [UnBlock] in the right list.
2.
Select [Watch] and observe the changes to dynamic properties.
1.
Blocking/unblocking serves to modify the management status bit of the

terrestrial and radio resources with dynamic properties such as BSC, BTS, and
TRX. Take the channel for example. Select [ZTE CorporationDomainBSS
FunctionBTS Site ManagerCellTRX] on the navigation tree on the left in
the interface, and select the channel to be blocked/unblocked under the
transceiver in the right list, right-click and select [Block] or [UnBlock] key in
the popup menu to initiate the operation of modifying the management status, as
151
Fig. 2.6-180 Blocking/Unblocking
2.
After the successful blocking/unblocking, the modified management statuses

will be shown in the corresponding list; otherwise, an error message would be
shown. At this time, you can also select the [OperationWatch] menu to
observe the changes to dynamic properties.
152
2.6.5Querying the Status of the A-interface Timeslot

[Objective]
Query the statuses of all A-interface timeslots, including the statuses of TIC unit, DRT
unit, switching network unit and trunk circuit.
[Preliminary setup]
1.
2.
[Required steps]
1.
Select the object node of the PCM on the navigation tree.
2.
In the right list, there are upper and lower boxes. Right-click on the lower part
and select [Refresh].
1.
Select
[ZTE
EquipmentBSC
EquipmentModule 1Munit] on the navigation tree on the left in the main

interface and view whether the unit under the munit is the AIPP unit. If yes,
select
the
[ZTE
EquipmentBSC
EquipmentModule 1MunitUnit [EXTERNALTIC]PCM] node.

2.
Select the list in the lower right part, right-click and select [Refresh] in the
popup menu. Click it to query the statuses of all A-interface timeslots, as shown
in Fig. 2.6-181.
153
Fig. 2.6-181 Query the Status of the A-interface Timeslot
We can judge whether the timeslot is normal by observing the status of the A-interface
timeslot and then remove the fault by means of signaling tracing and other tools.
154
2.6.6Performing Circuit Installation/Uninstallation of PCM

[Objective]
Perform the circuit installation/uninstallation for the A-interface PCM.
[Preliminary setup]
1.
2.
[Required steps]
1.
Select the object node of the EXTERNAL TIC unit on the browse tree.
2.
Select the PCM in the right list and then [Install Circuit] or [Uninstall Circuit].
1.
Select
[ZTE
EquipmentBSC
EquipmentModule 1Munit] on the navigation tree on the left in the main

interface, and view whether the unit under the munit is the AIPP unit. If yes,
select
the
[ZTE
EquipmentBSC
EquipmentModule 1MunitUnit [EXTERNALTIC]] node.

2.
Select the corresponding PCM in the right list of the interface, right-click and
select [Install Circuit] or [Uninstall Circuit] key in the popup menu to initiate the
operation of installing or uninstalling the PCM, as shown in Fig. 2.6-182. A
prompt will be given for either success or failure.
155
Fig. 2.6-182 PCM Circuit Assemble/Disassemble
2.6.7Querying the Status of the Abis-Interface Channel

[Objective]
Query the statuses of all Abis-interface channels, including dynamic properties,
channel combining mode, sub-channel status, whether being the PS channel or not,
uplink and downlink PS channels status and number of instances occupied by uplink
and downlink PS channels.
[Preliminary setup]
1.
2.
[Required steps]
1.
Select the object node of the transceiver that the cell belongs to under the logical
site on the navigation tree.
2.
In the right list, there are upper and lower boxes. Select [Refresh] in the lower
part.
1.
Select the [ZTE CorporationDomainBSS FunctionBTS Site Manager

CellTRX] node on the navigation tree on the left in the main interface;
156
2.
The right list contains upper and lower boxes. The upper box shows the dynamic
properties observance of all channels under the transceiver, and the lower box
shows the channel statuses. Right-click on the lower box and select [Refresh] in
the popup menu to query the statuses of all Abis-interface channels. The result is
Fig. 2.6-183 Query the Status of the Abis-Interface Channel
From the result, we can observe the information of all channels under this
transceiver such as dynamic properties, channel combining mode, sub-channel
status, whether being the PS channel or not, uplink and downlink PS channels
status and number of instances occupied by uplink and downlink PS channels.
At this time, we can judge the cause for the channel fault by means of signaling
tracing and other tools.
157
2.6.8Querying the N7Link Status

[Objective]
Watch the N7LINK status, including group No., code, module No., slot No., STB link
No. and status.
[Preliminary setup]
1.
2.
[Required steps]
1.
Select the LINKID object node on the navigation tree.
2.
In the lower right list, right-click and select [Refresh] operation.
1.
Select
the
[ZTE
EquipmentBSC
EquipmentLINKID] node on the navigation tree on the left.

2.
The right list contains upper and lower boxes, with the upper being the dynamic
properties observance box of N7Link and the lower showing the N7Link
statuses. Right-click to select [Refresh], as shown in Fig. 2.6-184.
Fig. 2.6-184 N7link Status
158
The N7LINK status includes group No., code, module No., slot No., STB link
No. and status. We can obtain the information of the No. 7 signaling and judge
whether it is normal or not according to these information.
2.6.9Activating /Deactivating the N7Link

[Objective]
Activate or deactivate the N7Link object and observe the changes to its dynamic
properties.
[Preliminary setup]
1.
2.
[Required steps]
1.
Select the LINKID object node on the navigation tree.
2.
Right-click on the corresponding object in the upper right list, and select
[Activate] or [Deactivate].
1.
Select
the
[ZTE
EquipmentBSC
EquipmentLINKID] node on the navigation tree on the left.

2.
Select the LINKID to be activated/deactivated in the upper right list, right-click

and select [Activate] or [Deactivate] in the popup menu to initiate the operation
of activating/deactivating the N7LINK, as shown in Fig. 2.6-185. A prompt will
be given for either success or failure.
159
Fig. 2.6-185 Activating/Deactivating
2.6.10Performing the Blocking/Unblocking/Reset/Signaling Reset/Status Query

of BVC
[Objective]
Perform the relevant operations of BVC to the cell, including blocking, unblocking,
reset, signaling reset and status query.
[Preliminary setup]
1.
2.
3.
The server supports GPRS.
[Required steps]
1.
Select the object node of the logical site on the navigation tree.
2.
The contents of the cell are shown in the upper right list. Click the
corresponding object node and select the relevant operations of BVC.
1.
Select the [ZTE CorporationDomainBSS FunctionLogic Site] node on

the navigation tree on the left in the main interface.
160
2.
Select the cell to be operated in the upper right list, right-click and the relevant
operations of the BVC in the menu can be seen. Select the [BVC Block], [BVC
Unblock], [BVC Reset], [BVC Signaling Reset] or [BVC State Query] menu to
query or modify the relevant dynamic properties of the BVC, as shown in Fig.
2.6-186.
Fig. 2.6-186 Relevant Operations of the BVC
2.6.11Querying the Channel Statistics of the Cell

[Objective]
Query the channel statistics of the cell, including the configuration, blocking, and
idle/occupied status of TCH, the configuration, blocking and idle/occupied status of
SDCCH and the configuration and use condition of the PS channel.
[Preliminary setup]
1.
2.
[Required steps]
1.
Select the object node of the cell on the navigation tree.
2.
Right-click on the node to select [Query the statistics of channel].
161
1.
Select
the
[ZTE
CorporationDomainBSS
FunctionBTS
Site
ManagerCell] node on the navigation tree on the left in the main interface.
2.
Right-click on the node and select [Query the statistics of channel ] in the popup
menu to initiate the cell channel statistics, as shown in Fig. 2.6-187.
Fig. 2.6-187 Query the Channel Statistics of the Cell
If the query is successful, the channel statistics result is popped up, as shown in
Fig. 2.6-188. The information of the cell is statisticized, including the
configuration, blocking, and idle/occupied status of TCH, the configuration,
blocking and idle/occupied status of SDCCH and the configuration and use
condition of the PS channel.
162
Fig. 2.6-188 Cell Channel Statistics Result
163
2.6.12Querying the Channel Statistics of the Module

[Objective]
Query the channel statistics of the central and peripheral modules. The channel
statistics of the central module includes the configuration, blocking, and idle/occupied
status of TCH; the channel statistics of the peripheral module includes the
configuration, blocking and idle/occupied status of SDCCH and the configuration and
use condition of the PS channel except the contents statisticized by the central module.
[Preliminary setup]
1.
2.
[Required steps]
1.
Select the object node on the navigation tree for the module.
2.
Right-click on the node to select [Query the statistics of channel].
1.
Select
[ZTE
EquipmentBSC
EquipmentModule] on the navigation tree on the left in the main interface.

2.
As shown in Fig. 2.6-189, right-click and select the [Query the statistics of
channel] menu to query the channel statistics of the module. For the central
module (with the module No. being 1), the result is shown in Fig. 2.6-190, and
the configuration, blocking, and idle/occupied status of the A-interface TCH of
the central module are statisticized. For the peripheral module (with the module
No. being 1), the result is shown in Fig. 2.6-191, and the configuration,
blocking, and idle/occupied status of TCH and SDCCH, and the configuration
and use condition of the PS channel are statisticized.
164
Fig. 2.6-189 Query the Channel Statistics of the Module
Fig. 2.6-190 Channel Statistics Result of the Central Module
165
Fig. 2.6-191 Channel Statistics Result of the Peripheral Module
166
2.6.13Querying the Instance Type of the Module

[Objective]
Query the instance type and the number of traffic instances of the module.
[Preliminary setup]
1.
2.
[Required steps]
1.
Select the object node on the navigation tree for the module.
2.
Right-click on the lower right list to select [Refresh].
1.
Select [ZTEDomainGSM EquipmentBSC EquipmentModule] on the

navigation tree on the left in the main interface.
2.
There are upper and lower lists in the right of the interface. Right-click on the
lower list and select [Refresh] in the popup menu to query the number of
instances of the module, as shown in Fig. 2.6-192.
Fig. 2.6-192 Query the Instance Type of the Module
167
2.6.14Setting the Foreground Switch Parameters

[Objective]
Setting the contents in the switch parameter R_OPTION table in the foreground
module is to set the switches for ETSI flow control, central flow control, carrier backup
and dynamic SDCCH allocation.
[Preliminary setup]
1.
2.
[Required steps]
1.
Select the module node on the navigation tree.
2.
Right-click on the node to select [Foreground Switch Parameter] and modify the
corresponding contents in the pop-up window for setting the foreground switch.
1.
Select [ZTEDomainGSM EquipmentBSC EquipmentModule] on the

navigation tree on the left in the main interface.
2.
Right-click and select the [Foreground Switch Parameter] menu (as shown in
Fig.2.6-17) to set the foreground switch parameters. If the query is successful,
the queried foreground switch parameters are returned, as shown in Fig.2.6-18.
168
Fig. 2.6-193 Set the Foreground Switch Parameter of the Module
Modify the corresponding contents in the window for setting the foreground
switch parameters as necessary. Click <Modify> to complete the modification.
Setting the switch parameters is to set the switches for ETSI flow control,
central flow control, carrier backup and dynamic SDCCH allocation and the
corresponding parameters when the switches are turned on. The settings of these
switch parameters are important to the foreground operation, so they should be
modified by professional personnel.
169
Fig. 2.6-194 Interface for Setting the Foreground Switch Parameters
2.6.15Querying the FUC Control Level of the Peripheral Module

[Objective]
Query whether the FUC (Frame Unit Controller) flow control strategy and the
corresponding FUC control level are implemented in the peripheral module.
[Preliminary setup]
1.
2.
[Required steps]
1.
Select the object node for the peripheral module of the base station equipment
on the navigation tree.
2.
Right-click on the node to select [Query FUC Control Level].
1.
Select the peripheral module node through [ZTE CorporationDomainGSM

EquipmentBSC EquipmentModule]. Note that the module No. should be
more than 1.
2.
Right-click on the node and select the [Query FUC Control Level] menu, as
shown in Fig. 2.6-195. Query the FUC control level. The returned result can be
seen in the character terminal at the lower part of the interface, as shown in Fig.
170
2.6-196. If the returned flow control level is 0, the system does not implement
the FUC control policy. If it is larger than 0, the system has implemented the
FUC control policy and set the corresponding flow control level. At this time,
the specific FUC control policy can be queried by querying the flow control
bitmap.
Fig. 2.6-195 Query the FUC Control Level (1)
171
Fig. 2.6-196 Query the FUC Control Level (2)
172
2.6.16Ending the FUC Control of the Peripheral Module

[Objective]
End the FUC control of the peripheral module.
[Preliminary setup]
1.
2.
[Required steps]
1.
Select the object node for the peripheral module of the base station equipment
on the navigation tree.
2.
Right-click on the node to select [End FUC Control].
1.
Select the peripheral module node through [ZTE CorporationDomainGSM

EquipmentBSC EquipmentModule]. Note that the module No. should be
more than 1.
2.
Right-click and select the [End FUC Control] menu to end the FUC control of
the corresponding peripheral module at the foreground, as shown in Fig. 2.6197. A prompt will be given for either success or failure.
173
Fig. 2.6-197 End the FUC Control
174
2.6.17Setting the FUC Control Bitmap of the Peripheral Module

[Objective]
Set the contents of the corresponding FUC control bitmap field in the foreground
module to set 11 levels for different flow control reasons for different flow control,
thus optimizing the system function.
[Preliminary setup]
1.
2.
[Required steps]
1.
Select the object node of the peripheral module on the navigation tree, rightclick on it and select [Setup Flow Control Bitmap].
2.
Modify the corresponding contents in the pop-up window for setting the flow
control bitmap.
3.
Save the modified contents to a file or open the saved file for modification.
1.
Select the peripheral module node (with the module No. being larger than 1)
through
[ZTE
EquipmentBSC
EquipmentModule] on the navigation tree on the left in the main interface.

Right-click on it and select the [Setup Flow Control Bitmap] menu to set the
flow control module bitmap of the foreground peripheral module, as shown in
Fig. 2.6-198.
175
Fig. 2.6-198 Set the Flow Control Bitmap
2.
In the window popped up for setting the flow control bitmap (as shown in Fig.
2.6-199), modify the corresponding contents. Seven different flow control
reasons are shown in the rows of the list in the window: Emergent call, call reestablishment, answer to paging, caller, position update, GPRS service and
reserved service. 11 flow control levels are shown in the columns of the list.
176
Fig. 2.6-199 Window for Setting the Flow Control Bitmap
In the list items of the corresponding flow control reason and flow control level,
the flow control percentage of this level to the corresponding flow control
reason can be modified and the corresponding bitmap information is shown in
the fine tune check box of the flow control bitmap on the right of the list. The bit
in the bitmap information can be selected to fine tune the flow control
percentage in the list of the bitmap information.
3.
In Fig. 2.6-199, click <Refresh> to obtain the settings at the foreground anew, or
click <Save> to save the modified contents to a file, or click <Open> to open a
saved file and then modify it.
177
2.6.18Performing Global Reset for Base Station

[Objective]
Performing global reset for base station
[Preliminary setup]
1.
2.
[Required steps]
1.
Select the object node of the base station equipment on the navigation tree.
2.
Right-click on the node to select [Global Reset].
1.
Select
the
[ZTE
Equipment]
or
[ZTE
CorporationDomainGSM EquipmentBSC Equipment] node on the

navigation tree on the left.
2.
As shown in Fig. 2.6-200, right-click and select [Global Reset] in the popup
menu to perform the global reset. A prompt will be given either success or
failure.
178
Fig. 2.6-200 Global Reset
2.6.19Troubleshooting Dynamic Data Management

The dynamic data management is a multi-aspect and multi-module complex task that
involves the database operation, the background MO operation, the communication
between the foreground and the background, and the foreground operation. It needs the
cooperation between many aspects to operate normally. The following problems are
easily seen during the dynamic data management:
1.
The dynamic data management serves to manage the terrestrial and radio
resources with dynamic properties. Any resource without the dynamic property
will not be embodied in the dynamic management interface.
2.
The dynamic data management serves to modify the state of terrestrial and radio
resources with dynamic properties at the foreground, so the operation must be
initiated to the foreground. The communication between the foreground and
background must be ensured normal.
3.
The operation of the dynamic data management will affect the state of terrestrial
and radio resources, so it will affect the conversation. Be careful when using it.
4.
The foreground environment has a big effect on the operation of dynamic data
management. Any error of the foreground operation will possibly be embodied
by operation failure of the dynamic data management.
179
3Fault Management
This chapter describes display and management of alarm, trunk node alarm
management, BSC environment alarm management and alarm rule management, manmachine operations of boards and test management.
3.1Overview
The fault management is to provide the management functions such as detection, report
and handling for the abnormalities of a telecom network and its environment. Its
functions are realized through fault alarm and fault diagnosis. The fault management is
also a main management function of the Telecom Network Management (TMN). It
provides the following management services specified in M.3400:
1.
Creation quality assurance.
2.
Alarm detection
3.
Fault location
4.
Troubleshooting.
5.
Test
6.
Fault (report) management.
The foremost objective of the fault management is to restore services in case of failure.
The second objective is to find out the root of each fault, including the minimum
repairable network part in the fault. The third objective is to recover the fault in a
timely and effective way, and automatically isolate it before recovery to minimize its
affection. In general, the fault management course includes the following three steps:
1.
Find the fault
2.
Analyze the fault cause.
3.
Remove the fault if possible.
The main features of the fault management include:
Real-time: Monitor the states and changes of NEs in the whole system and report any
abnormality in time.
Accurate: Report abnormalities accurately without any alarm unreported or any false
alarm.
Automatic: The system has the function of processing faults in somewhat intelligent
and automatic mode. Besides the mode in which an operator gives the fault handling
command, the system has partial capabilities of automatic control, such as automatic
fault isolation, prevention of faults from diffusing, starting of backup resource and
automatic recovery.
The fault management includes alarm management and test management.
Chapter 3 Fault Management
3.2Display and Management of Alarm

The display and management of alarm is to perform the operations on the alarm
generated by the BSC and BTS equipment such as conditional query, display in list and
management. It includes alarm query, alarm clearance acknowledgment, alarm dump
and alarm statisticizing.
Upon successful login to the OMCR system, select [Fault ManagmementAlarm
Management] from the OMCR main interface to enter the main interface for alarm
management, as shown in Fig. 3.2-201.
Fig. 3.2-201 Main Interface of Alarm Management
This is the logic display list of alarm management. The left window in the middle of
the interface is the navigation tree, including the current configuration information. The
list of unrecovered alarms of the system is shown in the upper right part, and the
notification list is shown in the lower right part. Select the [ViewRefresh] menu to
refresh the current alarms displayed in the list.
Click the [ViewPhyView] menu to view the physical rack view display of alarms and
observe the fault conditions of different boards, as shown in Fig. 3.2-202.
Fig. 3.2-202 BSC Alarm Management Rack Diagram Display
Select the nodes on the navigation tree on the left to view the conditions of different
BSC or BTS racks. The rack view in the right part shows the alarm information of each
board. The color of the round status indictor on the board indicates the status of this
board: Alarm or normal.
For the implications of various colors, please refer to the legend on the right of the rack
diagram.
1.
When an alarm occurs currently to a board, the color of the alarm status
indicator is that of the alarm of the highest class.
2.
When an unacknowledged alarm occurs to a board, its status indicator flashes.

The status indicator will not flash any more only when all the alarms of the
board are acknowledged.
3.2.1Performing the Conditional Alarm Query

[Objective]
According to the users requirements, query the recovered history alarms, current
alarms, general notification, and instant dump alarm, and list them to the user.
[Preliminary setup]
1.
Ensure that the whole system is running normally and the BSC is normally
connected with the OMCR.
2.
The alarm management interface has started running and the links to the servers
are normal.
[Required steps]
1.
Select the menu for the query operation from the alarm management interface.
2.
Perform the conditional query operation according to the prompt of the alarm
query Wizard.
3.
Click <Finish> to complete the operation and view the result.
1.
Select the [FileHistory Query] menu from the alarm management interface.
2.
Enter the [Query Wizard] dialog box, as shown in Fig. 3.2-203.
Fig. 3.2-203 Alarm Query Wizard 1
Click <Next> to enter the query Wizard 2 , as shown in Fig. 3.2-204.
Fig. 3.2-204 Alarm Query Wizard to 2
Select one or multiple alarm objects to be queried.

Click <Next> to enter the query Wizard 3 , as shown in Fig. 3.2-205.
Fig. 3.2-205 Alarm Query Wizard 3
To query by alarm type, select among the types in query Wizard 1, including
receovered history alarm, current unrecovered alarm, general notification and
instant dump alarm.
To query by time, set the query start time and the query end time in the time
period in query Wizard 1. The time period cannot be set for the query of current
unrecovered alarms.
6
To query by alarm severity level, select [Alarm Class] in [Select] in query

Wizard 2 and the level to be queried in <Select Alarm Class> and click <All> to
select all levels.
To query by alarm category (by alarm code), select [Alarm Code] in [Select] in
query Wizard 2 and then select the alarm code to be queried from the list of all
alarm codes in the [Select Alarm Code] box in the right side of the dialog box to
the right list.
3.
Click <Finish> to complete the operation, and the query result will be displayed,
Fig. 3.2-206 Query Results
Click <Report> to output the query results from the report form to the Microsoft
Excel format through a series of report Wizard settings. The alarm query result
report in Excel format is shown in Fig. 3.2-207.
Fig. 3.2-207 Query Result Report Display
Further modification, typesetting and printing of the report can be made in

Excel.
[Verification]
The query result will be shown on the interface upon operation success or the dialog
box indicating operation failure will be shown together with the failure cause.
3.2.2Viewing the Current Alarms of a Site

[Objective]
View the alarm details of a site.
[Preliminary setup]
1.
2.
are normal.
[Required steps]
Method 1:
In the logic view interface of the alarm management, select the site to be viewed on the
navigation tree on the left and observe the list on the right.
Method 2:
1.
Select the [History Query] menu in the alarm management interface.
2.
Use the conditional query of alarm to complete the operation.
3.
Check the result.
Method 1:
In the logic view interface of the alarm management, click the site to be viewed on the
navigation tree on the left and observe the list on the right, as shown in Fig. 3.2-208.
Fig. 3.2-208 Display of Current Alarms of a Site
Method 2:
1.
Select the [FileHistory Query] menu in the alarm management interface.
2.
Enter the interface for conditional alarm query for parameter setting.
1)
Select [Current Alarm] as the query type, as shown in Fig. 3.2-209.
Fig. 3.2-209 Select the Alarm Query Type
2)
Select the site to be viewed as the alarm source, as shown in Fig. 3.2-210.
10
Fig. 3.2-210 Select the Alarm Query Object
3)
Select <All> as the alarm class, as shown in Fig. 3.2-211.
Fig. 3.2-211 Select the Alarm Query Level and Alarm Code
3.
Click <Finish> to finish the operation.
4.
The query result is shown in Fig. 3.2-212,
11
Fig. 3.2-212 Site Alarm Query Result Display
[Verification]
12
3.2.3Viewing the Current Alarms of a Board

[Objective]
View the current alarms of a board on the rack.
[Preliminary setup]
1.
2.
are normal.
[Required steps]
Method 1:
As shown in Section 3.2.2, use the conditional alarm query to complete the operation.
Method 2:
Switch to [PhyView] in the alarm management interface.
Click the board to be viewed and view the result shown in the list.
Method 1:
This method is as described in the above section. Just replace the alarm source with the
board to be viewed.
Method 2:
1.
Select the [ViewPhyView] menu in the alarm management interface and

switch to the physical rack view.
2.
Click the board to be viewed and view the result shown in the list, as shown in
Fig. 3.2-213.
13
Fig. 3.2-213 View the Current Alarms of Board
[Verification]
The current alarm information will be shown on the interface upon operation success or
no information will be shown upon operation failure.
14
3.2.4Viewing the Notification of No Traffic in the Cell from the Base Station
[Objective]
View the notification of no traffic in the cell from the base station.
[Preliminary setup]
1.
2.
are normal.
[Required steps]
1.
Enter the interface for conditional alarm query.
2.
Select the notification code to be queried.
3.
View the query result.
1.
Select the [FileHistory Query] menu in the alarm management interface to

enter the interface for the conditional alarm query.
2.
Select the notification to be queried.
1)
Select general notification as the query type and the time period to be queried, as
15
Fig. 3.2-214 Notification Query-1
2)
Select the OMCR background notification as the notification source and then the
Domain to be queried, as shown in Fig. 3.2-215.
Fig. 3.2-215 Notification Query 2
3)
Select 65488 as the notification code to be queried, as shown in Fig. 3.2-216.
16
Fig. 3.2-216 Notification Query-3
3.
Click <Finish> to finish the operation.
4.
The query result is shown in Fig. 3.2-217.
Fig. 3.2-217 Display the Notification Query Result
[Verification]
17
3.2.5Querying the History Alarms of a Board

[Objective]
Query the recovered history alarms of a board.
[Preliminary setup]
1.
2.
are normal.
[Required steps]
1.
Switch to the physical rack view display interface in the alarm management
interface.
2.
Select the board to be queried and enter the interface for querying the history
alarms of the board.
3.
Set the query parameters to complete the operation.
4.
Check the result.
1.
Select the [ViewPhyView] menu in the alarm management interface to enter

the rack view display interface.
2.
Select the board to be queried, right-click to enter the interface for querying the
history alarms of the board, as shown in Fig. 3.2-218.
18
Fig. 3.2-218 Query the Board History 1
3.
Set the time period for query and click <Query> to complete the operation, as
Fig. 3.2-219 Query the Board History 2
4.
The query result is shown in Fig. 3.2-220.
19
Fig. 3.2-220 Display the Query Results
[Verification]
20
3.2.6Viewing the History Alarms after Dump

[Objective]
Query the recovered history alarms after dump.
[Preliminary setup]
1.
2.
are normal.
[Required steps]
1.
Select the [History Query] menu in the alarm management interface to enter the
interface for conditional alarm query.
2.
Select the time period with dump alarms for the conditional query.
3.
Confirm reloading the file for query to complete the operation.
1.
Select the [FileHistory Query] menu in the alarm management interface to

enter the interface for conditional alarm query.
2.
Select the time period with dump alarms for the conditional query, as shown in
Fig. 3.2-221.
Fig. 3.2-221 Select the Time Period for the Conditional Query
For the conditional query operation, refer to Section 3.2.1.

21
3.
Confirm reloading the file for query to complete the operation.

After the conditional query is completed, the dialog box shown in Fig. 3.2-222
shows up for querying whether to reload the file.
Fig. 3.2-222 Reload File Inquiry Box
After it is confirmed that the file in the dialog box has been copied to the
designated directory of the server ($OMCHOME/bak/fm/reload), click <OK> to
complete the query of the dumped history alarms.
[Verification]
22
3.2.7Statisticizing the High-frequency Alarms

[Objective]
Statisticize the high-frequency alarms in a time period and list them for analysis and
comparison.
[Preliminary setup]
1.
2.
are normal.
[Required steps]
1.
Select the [Statistics Analysis] menu from the alarm management interface.
2.
Enter the interface for alarm statistics analysis to select parameters.
3.
Click <OK> to complete the operation and view the result.
1.
Select the [FileStatistics AnalysisAlarm Frequency Analysis] menu from

the alarm management interface.
2.
Enter the interface for alarm frequency analysis to select parameters.
1)
Select the alarm source, as shown in Fig. 3.2-223.
Fig. 3.2-223 Alarm Frequency Analysis - Select the Alarm Source
23
Select the Domain to be operated from the [Domain] pull-down list box.
Select the alarm object to be statisticized from the left side to move it to the box
of selected objects, as shown in Fig. 3.2-223. The items marked with deep colors
indicate selected alarm sources, those marked with light colors indicate that the
alarm sources in its subtrees are not completely selected, and those not marked
with colors indicate unselected alarm sources. The selected objects are on the
right side.
2)
Select the time period, as shown in Fig. 3.2-224.
Fig. 3.2-224 Alarm Frequency Statistics - Select the Time Period for Alarm Statistics
The above figure indicates that the user select the time period for alarm
statistics. The user shall select the start time and the stop time to decide the
upper and lower ranges of the time for alarm statistics. The user can also select
to statisticize all alarms or N high-frequency alarms.
3)
Select the filtering condition for alarm statistics, as shown in Fig. 3.2-225.
24
Fig. 3.2-225 Alarm Frequency Analysis - Select the Filtering Condition for Alarm Statistics
The figure above indicates that the user designates the filtering condition for
alarm statistics. Note that at least one item must be selected in each group.
3.
Click <OK> to complete the operation and view the result, as shown in Fig. 3.2226.
Fig. 3.2-226 Alarm Frequency Analysis - Show the Alarm Statistics Result in List
The alarms are arranged based on their frequencies as shown in Fig.3.2-26. The
user can double click an alarm to query its details.
Click <View Graph> to change the display mode of the statistics result, as
25
Fig. 3.2-227 Alarm Frequency Analysis - Display Alarm Statistics Result in Graphical Mode
The graph borders can be customized according to the users requirements.

Scroll the scroll bar under the statistics chart to view the alarm statistics
unshown. Select [List] to change to the mode of displaying in list, and select
[Report] to call the report output Wizard to output the report.
[Verification]
26
3.2.8Viewing the Relevant Information of a Correlated Alarm

[Objective]
View the relevant information of a main correlated alarm.
[Preliminary setup]
1.
2.
are normal.
[Required steps]
1.
In the main interface for alarm management, select the alarms marked with +.
2.
Click [Correlation Query] to finish the operation.
3.
Check the result.
1.
In the main interface for alarm management, select the alarms marked with +,
Fig. 3.2-228 Alarm Correlation Information Query
27
2.
Right-click and select the [Correlation Query] menu to complete the operation.
3.
View result: In the query result are shown the original alarm of this correlated
alarm and the details of the correlation rules applied by this alarm, as shown in
Fig. 3.2-229.
Fig. 3.2-229 Relevant Information Display
[Verification]
28
3.2.9Acknowledging the Alarm

[Objective]
Acknowledge the alarm, indicating that the user has known about this fault and hopes
the alarm box connected to the client no longer makes a sound because of this alarm.
[Preliminary setup]
1.
2.
are normal.
3.
Connect the alarm box normally to the client.
[Required steps]
1.
Select the alarm to be acknowledged in the main interface for alarm

management.
2.
Click [OK] to finish the operation.
1.
Select the alarm to be acknowledged in the main interface for alarm

management, and right-click, as shown in Fig. 3.2-230.
Fig. 3.2-230 Alarm Validation
29
2.
[Verification]
The alarm icon in the interface no longer flashes and the alarm box connected to the
client no longer makes an audio or visual alarm upon operation success or the dialog
30
3.2.10Clearing the Alarm Manually

[Objective]
Clear the alarm manually from the client so that this alarm is no longer shown in the
alarm interface and the alarm box connected to the client no longer gives out an audio
or visual alarm.
[Preliminary setup]
1.
2.
are normal.
3.
Connect the alarm box normally to the client.
[Required steps]
1.
Select the alarm to be cleared in the main interface for alarm management.
2.
Click [Manual Recover] menu to finish the operation.
1.
Select the alarm to be cleared in the main interface for alarm management and
right-click, as shown in Fig. 3.2-231.
Fig. 3.2-231 Manual Alarm Recovery
31
2.
Click the [Manual Recovery] menu to display the dialog box for deletion
acknowledgment, and click <OK> to complete the operation, as shown in Fig.
3.2-232.
Fig. 3.2-232 Acknowledge the Operation Box
[Verification]
The alarm is no longer shown in the interface and the alarm box connected to the client
no longer makes a sound because of this alarm upon operation success or the dialog
32
3.2.11Acknowledging the Notification

[Objective]
Acknowledge the notification, indicating that the content of this notification has been
known.
[Preliminary setup]
1.
2.
are normal.
[Required steps]
1.
Select the notification to be acknowledged in the main interface for alarm

management.
2.
1.
Select the notification to be acknowledged in the main interface for alarm

management and right-click, as shown in Fig. 3.2-233.
Fig. 3.2-233 Notification Acknowledgment
2.
33
[Verification]
34
3.2.12Dumping the Current Important Alarms

[Objective]
Dump the current important alarms to back them up.
[Preliminary setup]
1.
2.
are normal.
[Required steps]
1.
Select the alarms to be dumped in the alarm interface and right-click.
2.
Select [Immediate Store] to finish the operation.
1.
Select the alarms to be dumped in the alarm interface and right-click, as shown
in Fig. 3.2-234.
Fig. 3.2-234 Instant Dump of Important Alarms
2.
Select [Immediate Store] to finish the operation.
[Verification]
35
The dialog box indicating operation success will be shown in the interface or the dialog
3.2.13Dumping the History Alarms

[Objective]
Dump the recovered history alarms N days ago.
[Preliminary setup]
Ensure that the whole system is running normally and the BSC is normally connected
with the OMCR.
[Required steps]
Input the manual dump command on the command box at the character terminal or
alarm interface.
Input the manually dumped command on the command box at the character terminal or
alarm interface. For example, to dump the recovered alarms 30 days ago, key in the
following command, as shown in Fig. 3.2-235:
Fig. 3.2-235 Manual Dump
[Verification]
The dialog box indicating operation success will be shown or the dialog box indicating
operation failure will be shown together with the failure cause.
36
3.2.14Setting the Auto Periodic Dump of Alarm Data

[Objective]
Set the system to automatically dump the recovered history alarms, including setting
the dump cycle, number of dump days and dump time.
[Preliminary setup]
with the OMCR.
[Required steps]
1.
Select the menu for the periodic dump operation from the alarm management
interface.
2.
Set such information as dump cycle in the periodic dump window.
3.
Click <Setup> to finish the operation.
1.
Select the [SetupPeriodic Dump Setting] menu from the alarm management
interface.
2.
Enter the periodic dump dialog box, as shown in Fig. 3.2-236. The parameter
setting means to set the auto dump operation at 6:00 a.m. every 7 days and store
the restored history alarms 30 days ago. To select the [Start periodic dump] box
is that this periodic dump rule will take effect, to select the [Close periodic
dump] means that this periodic dump rule does not take effect.
37
Fig. 3.2-236 Setting the Periodic Dump

[Verification]
38
3.2.15Customizing the Alarm Solution and Cause

[Objective]
According to the users knowledge about the alarm information, customize his own
alarm solution and cause.
[Preliminary setup]
1.
2.
are normal.
[Required steps]
1.
Select the [Knowledge Base Management] menu from the alarm management
interface.
2.
Enter the interface for setting the knowledge base to customize its contents.
3.
Click <OK> to finish the operation.
1.
Select the [FileKnowledge Base Management] menu from the alarm

management interface.
2.
Enter the dialog box for setting the knowledge base, as shown in Fig. 3.2-237.
39
Fig. 3.2-237 Alarm Knowledge Base Setting
1)
Select the NM domain to be operated from the [Domain] pull-down list box.
2)
Select to customize the alarm code or the alarm reason code.
3)
Click the alarm code or reason code to be modified in the list box of alarm
contents or alarm reasons.
4)
Input the content customized by the user in the [Alarm Handling Methods
Provided by User Based on Experience] edit box for reference when this alarm
occurs again in the future.
3.
[Verification]
40
3.2.16Suppressing the Alarm Display

[Objective]
Suppress the alarm display on the interface or the alarm storage.
[Preliminary setup]
1.
2.
are normal.
[Required steps]
Suppressing the alarm display can be realized through setting the alarm filtering rule.
1.
Watch the alarm information to be suppressed in the interface and acknowledge

the type, position, code or level of the alarm to be suppressed.
2.
Acknowledge whether to suppress the alarm display - display filtration set in the
rule
or to suppress the alarm storage and display - database filtration set in the rule.
3.
Change to the interface for filtering rule management to set the rule. For details,
refer to the description of the alarm filtering rule in the Section 3.5.2.
[Verification]
The set rule functions for the subsequent alarms, and the suppressed alarms will no
longer be shown or stored.
41
3.2.17Redefining the Alarm Class

[Objective]
Redefine the level of an alarm.
[Preliminary setup]
1.
2.
are normal.
[Required steps]
The alarm class can be redefined through setting the alarm reclassification rule.
1.
Watch the alarm information for which the level shall be redefined in the
interface, and fix the code, type and position of the alarm to be redefined.
2.
Fix the level to be redefined and switch to the interface for reclassification rule
management for the rule setting. For details, refer to the description of the alarm
reclassification rule in the Section 3.5.3.
[Verification]
The set rule functions for the subsequent alarms, and the level of this type of alarms is
shown according to the setting.
42
3.2.18Showing the Important Alarms in Correlated Alarms

[Objective]
Show the important alarms in correlated alarms and suppress the display of subordinate
alarms.
[Preliminary setup]
1.
2.
are normal.
[Required steps]
Set the suppress rule in the correlation rules.
1.
Acknowledge the alarm information of the correlated alarm - including position

and alarm code and acknowledge which are the main alarms to be shown and
which are the subordinate alarms not to be shown.
2.
Switch to the interface for correlation rule management for setting the suppress
rule. For details, refer to the description of the alarm suppress rule in the
Section3.5.4.1.
[Verification]
The set rule functions for the subsequent alarms, and only the important alarms in
correlated alarms are shown in the interface while the subordinate alarms are
suppressed.
43
3.2.19Generating a New Alarm after an Alarm Occurs a Certain Times

[Objective]
Some minor alarms are handled only after occurring multiple times in a certain time
period. New alarms of a higher level is prompted after these alarms occur multiple
times.
[Preliminary setup]
1.
2.
are normal.
[Required steps]
Set the count rule in the correlation rules.
1.
Acknowledge the information of the original alarm that occurs frequently and
for which a new alarm needs to be generated: including the position, alarm code,
frequency and time interval.
2.
Switch to the interface for correlation rule management for setting the count
rule. For details, refer to the description of the alarm count rule in the
Section3.5.4.2.
[Verification]
The set rule functions for the subsequent alarms. After the alarm set in the rule occur N
times within a time period, the new alarms set by the rule will be shown in the
interface. This new alarm can only be manually recovered, instead of being
automatically recovered.
44
3.2.20Compressing Class 1 Alarms

[Objective]
Combine class 1 alarms and only show the information of an alarm in the interface.
[Preliminary setup]
1.
2.
are normal.
[Required steps]
Set the compress rule in the correlation rules.
1.
Determine the alarms of which alarm code are to be compressed.
2.
Switch to the interface for correlation rule management for setting the compress
rule. For details, refer to the description of the alarm compress rule in the
section.
[Verification]
The set rule functions for the subsequent alarms. For the alarms set in the rule, only the
earliest alarm will be shown, and the subsequent alarms will no longer be shown until
the rule is deleted. The shown alarm is not cleared from the interface when being
recovered and is only restored only after all compressed alarms are recovered.
45
3.2.21Modifying the Alarm Display Mode

[Objective]
Modify the alarm display mode, including the flash frequency of the icon in the alarm
interface and the sound reported by the alarm.
[Preliminary setup]
1.
2.
are normal.
[Required steps]
1.
Select the [Alarm Display Mode] menu in the alarm interface.
2.
Enter the interface for setting the alarm display mode to perform the relevant
setting.
3.
1.
Select the [SetupAlarm Display Mode] menu in the alarm interface.
2.
Enter the interface for setting the alarm display mode to perform the relevant
setting, as shown in Fig. 3.2-238.
46
Fig. 3.2-238 Alarm Show Mode
Select the alarm class and click <Load> to load different sound files to
customize the sounds for different levels of alarms.
3.
[Verification]
Click <Test> to test whether the setting is successful.
47
3.2.22Customizing the Item Display of the Alarm List

[Objective]
Customize the item display of the alarm list, only the items the user needs are
displayed.
[Preliminary setup]
1.
2.
are normal.
[Required steps]
1.
Right-click on the alarm list of main interface or the title bar of the board alarm
list.
2.
Select [Hide column] or the item to be displayed in the right-click menu.
1.
Right-click on the alarm list of main interface or the title bar of the board alarm
list to pop up the right-click menu, as shown in Fig. 3.2-239.
Fig. 3.2-239 Customize the Item Display
2.
Select the [Hide column] in the right-click menu, and the column where the
mouse is will be hidden, or select the [Show column] in the right-click menu,
and select the item required to be displayed in the pop-up submenu, the ticked
items will be displayed.
[Verification]
The alarm list displays the items customized by the user.
48
3.3Trunk Node Alarm Management

The trunk node alarm management is to customize the trunk node alarms of each rack
in the site and complete the operation by establishing different templates. At most 12
trunk node alarms can be defined for each rack of each site. The definition of the trunk
node alarm includes the classes and contents of alarms.
At different sites, the same or different templates of trunk node alarm can be applied.
1.
Different sites can have different trunk node alarm settings.
2.
Some sites can have the same trunk node alarm settings as others.
Select the [SetupTrunk Node AlarmSet Trunk Node Alarm] menu in the alarm
management interface to pop up the main interface for trunk node alarm management,
where the trunk node alarm can be set and the trunk node template can be created,
modified and deleted, as shown in Fig. 3.3-240.
Fig. 3.3-240 Trunk Node Setting
49
3.3.1Customizing the Trunk Node Alarms of a Rack at a Site

[Objective]
Customize the trunk node alarms of a rack at a site, including selecting the template
and setting the template used by the rack.
[Preliminary setup]
1.
2.
The alarm management interface has started running and is connected normally
to the server.
[Required steps]
1.
Select the [Node Alarm Setting] menu from the alarm management interface.
2.
View whether there is a suitable template. Create one if not.
3.
Select the template suitable for this rack and set it.
4.
1.
Click the [SetupTrunk Node AlarmSet Trunk Node Alarm] menu in the
alarm management interface.
2.
Select an existing template from the right pull-down box in the interface for
trunk node setting and view whether its information satisfies the requirements,
as shown in Fig. 3.3-241..
Fig. 3.3-241 Existing Template Display
50
If the existing templates do not satisfy the requirements, click <New> to enter
the interface for creating the new template, as shown in Fig. 3.3-242.
Fig. 3.3-242 Create Trunk Node Alarm Template
1)
Enter the module No. different from that of the existing template, and press
<Enter>.
2)
Customize the contents of different trunk node alarms and the alarm classes,
which is not obligatory for each node.
3)
4)
Upon creation success, return to the interface for setting the trunk node alarm.
At the time, the new template has been listed in the pull-down list of the new
template selection box.
3.
In the interface for trunk node setting, select in turn the NM domain, base station
subsystem, site and rack of the trunk node alarm, and then the template No. to be
set in the pull-down list, as shown in Fig. 3.3-243.
51
Fig. 3.3-243 Trunk Node Alarm Setup
4.
[Verification]
52
3.3.2Modifying the Trunk Node Template

[Objective]
Modify the existing trunk node template to satisfy the new requirements.
[Preliminary setup]
1.
2.
are normal.
3.
The trunk node template has existed.
[Required steps]
1.
Select the [Trunk Node Alarm Setup] menu from the alarm management
interface.
2.
Enter the node setting interface and select <Modify>.
3.
Enter the interface for modifying the template and input the contents to be
modified.
4.
1.
Select the [SetupTrunk Node AlarmSet Trunk Node Alarm] menu from the
2.
Enter the trunk node setting interface and select <Modify>.
3.
Enter the interface for modifying the template, select the template No. to be
modified and enter the contents to be modified, as shown in Fig. 3.3-244.
53
Fig. 3.3-244 Modify the Trunk Node Template
4.
[Verification]
54
3.3.3Deleting the Trunk Node Template

[Objective]
Delete the trunk node template no longer used.
[Preliminary setup]
1.
2.
are normal.
3.
The trunk node template is no longer used.
[Required steps]
1.
Select the [Trunk Node Alarm Setting] menu from the alarm management
interface.
2.
Enter the trunk node setting interface and select <Delete>.
3.
Select the template to be deleted from the pull-down list box of the templates no
longer used.
4.
Click <Delete> to finish the operation.
1.
Select the [SetupTrunk Node AlarmSet Trunk Node Alarm] menu from the
2.
Enter the trunk node setting interface and select <Delete>.
3.
Select the template to be deleted from the pull-down list box of the templates no
longer used, as shown in Fig. 3.3-245.
55
Fig. 3.3-245 Delete the Trunk Node Template
4.
Click <Delete> to finish the operation.
[Verification]
56
3.3.4Setting the Level Mode of the Trunk Node

[Objective]
Modify the default level mode of the trunk node.
[Preliminary setup]
1.
2.
are normal.
[Required steps]
1.
Select the [Setup Alarm On-Off Mode] menu from the alarm management
interface.
2.
Enter the mode setting interface to customize the mode.
3.
1.
Select the [SetupTrunk Node AlarmSet Alarm On-Off Mode] menu from
the alarm management interface.
2.
Enter the mode setting interface, and select in turn the NM domain, base station
subsystem, site and rack of the on-off mode, and then the on-off mode of the
corresponding trunk node based on requirements, as shown in Fig. 3.3-246.
57
Fig. 3.3-246 Mode Setting
3.
[Verification]
58
3.4BSC Environment Alarm Management

Environment alarm refers to the alarm generated when the external running
environment goes beyond the designated range. Environment alarm includes
temperature/humidity alarm, and infrared alarm.
The environment alarm management is to control the generation of alarms through the
setting of environment parameters which can only be performed to the BSC.
3.4.1Setting the Temperature/Humidity Parameters

[Objective]
Set the temperature/humidity conditions suitable for the equipment room so that the
necessary alarm information is generated when the temperature/humidity goes beyond
the permitted range to facilitate maintenance and management of the environment in
the equipment room.
[Preliminary setup]
1.
2.
The temperature/humidity sensor has been connected to the rack and works
normally.
3.
to the server.
[Required steps]
1.
Select the [Environment Setup] menu from the alarm management interface.
2.
Set the parameter information as required.
3.
1.
Select the [SetupEnvironment Alarm] menu from the alarm management

interface.
2.
59
Select one SCM/RRM of BSC in the navigation tree on the left and click the
[Temperature and Humidity] tab to set temperature/humidity parameters. The
dialog box is shown in Fig. 3.4-247.
Fig. 3.4-247 Temperature/Humidity Setup
Input the upper and lower limits of temperature and humidity respectively.
Temperature lower than the lower limit or higher than the upper limit are both
abnormal, and alarms will occur. The maximum scope of temperature setting: 0
0
C ~ 45 0C.
The maximum scope of humidity setting: 20% ~ 80%.

3.
[Verification]
60
3.4.2Setting the Infrared Alarm Parameter

[Objective]
Set the parameters of infrared detection, such as start status and start time to maintain
the environment in the equipment room.
[Preliminary setup]
1.
2.
The infrared sensor has been connected to the rack and works normally.
3.
to the server.
[Required steps]
1.
Select the [Environment Setting] menu from the alarm management interface.
2.
3.
1.
Select the [SetupEnvironment Alarm] menu from the alarm management

interface.
2.

Select one SCM/RRM of the BSC in the navigation tree on the left and click the
[Infrared] tab to set infrared parameters. The dialog box is shown in Fig. 3.4248.
61
Fig. 3.4-248 Environment Parameter Setting - Infrared
If the infrared alarm function is to be started, select the [Enable Infrared Alarm]
check box; otherwise the system generates no infrared alarm;
If the time segment of [Infrared Alarm Disable] is set in the [Disable Time
Segment] box, then no infrared alarm will be generated in this time segment.
There are two modes: periodical setting and specific interval setting.
If the [Period Setup] check box is selected, then only the hour, minute and
second of the start time and that of stop time can be set. When the infrared alarm
is enabled, the infrared alarm is prohibited to be carried out in the interval
between the start time and the end time of each day. If the [Period Setup] check
box is not selected, it means that the interval shall be specified. Then you need
to set the start date and time. When the infrared alarm is enabled, the infrared
alarm is forbidden during the set interval.
3.
[Verification]
62
3.5BSC Alarm Rule Management

3.5.1Overview
Alarm rules include alarm filtering rule, alarm reclassification rule and alarm
correlation rule. The alarm rule management is responsible for providing such
operations as the query, addition, deletion, modification, enabling and disabling of
alarm rules (filtering rule, reclassification rule and correlation processing rule).
The alarm filtering rule permits the user to filter alarms or automatically acknowledge
them. In this way, some unimportant or uninterested alarms can be filtered so that the
real important alarms can be discovered in time.
The alarm reclassification rule is to emphasize or weaken some MO or class 1 alarms
(alarm codes). Affected by the factors such as the equipment use time and the specific
network condition, the alarms vary in their effects on the network operation. The alarm
reclassification permits the user to redefine the alarm classes.
The alarm correlation is to find the correlation between alarms to find the real fault
source. Usually, there are many alarms in the whole network and in practice, a fault
often results in multiple alarms in time and space. For example, in the case of link
interruption, the equipment at both ends of the link will generate a communication fault
alarm, but only one fault is presented before users, thus greatly reducing the operators
labor intensity.
The processing sequence of filtering, reclassification and correlation of the alarm is:
first the filtering, then reclassification and finally correlation.
Alarm correlation processing, in combination with alarm filtering, can be used to
effectively decrease the number of alarms presented before users and find out the
fundamental cause of a fault conveniently.
3.5.2Filtering Rule Management

The filtering principle management includes: creation, modification and deletion of the
filtering rule.
The alarm filtering enables users to set an alarm as not being displayed in the alarm
real-time observation interface or not being written to an alarm database. The filtering
63
conditions may be the filtering of a specific MO (a logic entity or physical entity), that
of some alarm classes and that of some type of alarms.
3.5.2.1Creating a Filtering Rule
[Objective]
Create an alarm filtering rule. For example, create the rule to filter the alarms of cell 1
with the alarm code being 123 and suppress the alarms meeting the condition.
[Preliminary setup]
with the OMCR.
[Required steps]
1.
Start the client interface for alarm management.
2.
Enter the alarm filtering rule setting interface.
3.
Enter the dialog box for filtering rule creation.
4.
First select the object on which the filtering rule is acted.
5.
Select the filtering rule mode, filtering method and others.
6.
Click <OK> to send the command and complete the operation.
1.
Start the client interface for alarm management

Upon successful login, select [Fault ManagmementAlarm Management] from
the OMCR main interface to enter the main interface for alarm management.
2.
Enter the alarm filtering rule setting interface

Select [SetupAlarm RuleAlarm Filtering Rule] from the main interface for
alarm management to enter the dialog box for alarm filtering rule management,
64
Fig. 3.5-249 Dialog Box for Alarm Filtering Rule Management
3.
Enter the dialog box for alarm filtering rule creation

Click <New Alarm Filtering Rule> on the toolbar in the dialog box for alarm
filtering rule management to enter the dialog box for editing the alarm filtering
rule, as shown in Fig. 3.5-250.
Fig. 3.5-250 Dialog Box for Editing the Alarm Filtering Rule
4.
First select the object on which the filtering rule is acted.

Click <Rule Object> to enter the [Select Object] dialog box, as shown in Fig.
3.5-251.
65
Fig. 3.5-251 Rule Object Selection Dialog Box
Select an object from the object navigation tree in the object selection dialog
box. The selected object will be shown in the upper single-line box. Click <OK>
to configure the object selection and return to the dialog box shown in Fig. 3.5250.
5.

Then, select a filtering rule mode. There are three modes: object, object + alarm
code and object + alarm class. If object + alarm code is selected, an alarm code
shall be selected in the [Alarm Code] box; if object + alarm class is selected, an
alarm class shall be selected.
Then, select a filtering mode. The alarm filtering is divided into database
filtering and display filtering. The database filtering indicates the alarm will be
discarded completely, which means that neither is it stored into the database nor
is it processed. The display filtering is only to prevent the alarms from being
shown in the alarm list. Users can view the alarm information by query if
necessary.
If the display filtering mode is selected, the acknowledgment mode should also
be selected. The alarm acknowledgment is to mark that this alarm information
has been read. The acknowledgment modes include Unacknowledge,
Acknowledge and Clear acknowledgment. An acknowledgment mode can
66
be selected based on the importance of display filtering alarm. An alarm after

display filtering still can be queried and viewed. Unacknowledged filtering
alarm is in the unacknowledged status in query. It can be manually
acknowledged by the users. Therefore, users can easily detect the occurrence of
the alarm in query, which can be used for important filtering alarm.
Acknowledge means that the system acknowledges the receipt after receiving
the alarm, which can be used in unimportant filtering alarm. Clear
acknowledgment means that the system acknowledges the clearance
automatically after the alarm is recovered, which can be used in rather important
filtering alarm.
Finally select a rule status. The rule status includes active and inactive, and only
those rules in active status can be applied.
6.
Click <OK> to send the command and finish the operation.

Click <OK> to acknowledge a created filtering rule and return to the dialog box
[Verification]
The dialog box indicating operation success will be shown in the interface. In this case,
the created filtering rule will be listed in an alarm filtering rule list.
or the dialog box indicating operation failure will be shown together with the failure
cause.
67
3.5.2.2Modifying a Filtering Rule

[Objective]
The created alarm filtering rule can be modified.
[Preliminary setup]
1.
2.
The alarm filtering rule has been created before.
[Required steps]
1.
2.
3.
Enter the dialog box for filtering rule modification.
4.
5.
1.

2.

3.
Enter the dialog box for filtering rule modification

In the dialog box for alarm filtering rule management, click <Modify Alarm
Filtering Rule> on the toolbar to enter the dialog box for editing the alarm
filtering rule, as shown in Fig. 3.5-252.
68
Fig. 3.5-252 Dialog Box for Modifying the Alarm Filtering Rule
4.

In the filtering rule modification, only the filtering rule, acknowledge mode and
rule status can be modified. Refer to the description in section for details.
5.

Click <OK> to acknowledge the changes and return to the dialog box for alarm
filtering rule management shown in Fig. 3.5-249.
[Verification]
The corresponding dialog box indicating operation success will be shown. In this case,
the filtering rule will be listed according to the modified contents in the alarm filtering
rule list.
cause.
69
3.5.2.3Deleting a Filtering Rule

[Objective]
The created alarm filtering rule can be deleted.
[Preliminary setup]
1.
2.
The alarm filtering rule has been created before.
[Required steps]
1.
2.
Enter the alarm filtering rule setting window.
3.
Select the filtering rule to be deleted.
4.
1.

Upon successful login, select [Fault ManagementAlarm Management] from
the OMC-R main interface to enter the main interface for alarm management.
2.
Enter the alarm filtering rule setting window

as shown in Fig.3.5-1.
3.
Select the filtering rule to be deleted and execute the deletion operation.
In the dialog box for alarm filtering rule management, select the filtering rule to
be deleted, and click <Delete Alarm Filtering Rule> on the toolbar.
4.
[Verification]
the created filtering rule will be deleted from the alarm filtering rule list.
70
cause.
3.5.3Reclassification Rule Management

The reclassification rule management include: creation, modification and deletion of
the reclassification rule.
The alarm reclassification process is used to reclassify the alarms satisfying specific
conditions to a new alarm class. This can be used to enhance or weaken this type of
alarm. The conditions for selecting the reclassified alarms include: designated alarms
of class 1 objects; designated alarms of a specific object; designated alarms with a
specific alarm code.
The alarm reclassification only affects the level of the alarms reclassified by the user,
instead of the alarm class set at the system initialization. After the alarm
reclassification, both the original and the new alarm classes are written into the alarm
database and the display in the alarm interface is refreshed correspondingly.
3.5.3.1Creating a Reclassification Rule
[Objective]
Create an alarm reclassification rule.
[Preliminary setup]
with the OMCR.
[Required steps]
1.
2.
Enter the interface for setting alarm reclassification rules.
3.
Enter the dialog box for alarm reclassification rule creation.
4.
Select the object on which the rule is acted.
5.
Select the alarm code, alarm class and rule status.
6.
1.

71

2.

Select [SetupAlarm RuleAlarm Reclassification Rule] from the menu in the
main interface for alarm management to enter the dialog box for alarm
reclassification rule management, as shown in Fig. 3.5-253.
Fig. 3.5-253 Dialog Box for Alarm Reclassification Rule Management
3.
Enter the dialog box for alarm reclassification rule creation.

Click <Alarm Reclassification Rule Editor> on the toolbar in the dialog box for
alarm reclassification rule management to enter the dialog box for creating an
alarm reclassification rule, as shown in Fig. 3.5-254.
72
Fig. 3.5-254 Dialog Box for Creating an Alarm Reclassification Rule
4.
Select the object on which the filtering rule is acted.

This step is optional. If it is necessary to apply the rule to the designated object,
select the [Rule Object] check box and click <Rule Object...> to enter the dialog
box for object selection, as shown in Fig. 3.5-255.
box. The selected objected will be shown in the upper single-line box. Press
<OK> to acknowledge object selection and return to the dialog box as shown in
Fig. 3.5-254.
73
5.

All alarm codes are listed in the selection box of the alarm code box and an
alarm code can be selected as required. An alarm class box displays the original
class and the reclassification class is set by a user.
Rule status can be a new active status or inactive status and only the rule in
active status can be applied.
6.

reclassification rule management shown in Fig. 3.5-253 .
[Verification]
the alarm reclassification rule list will display the new reclassification rule. The rules in
activated status will be applied while those inactivated will not be applied but only
listed.
cause.
74
3.5.3.2Modifying a Reclassification Rule

[Objective]
Modify the created alarm reclassification rule.
[Preliminary setup]
1.
2.
The alarm reclassification rule has been created.
[Required steps]
1.
2.
3.
Enter the interface for alarm reclassification rule modification.
4.
5.
1.

2.

reclassification rule management, as shown in Fig. 3.5-253.
3.
Enter the dialog box for alarm reclassification rule modification.

To select the reclassification rule to be modified in the dialog box for alarm
reclassification rule management, click <Modify Alarm Reclassification Rule>
on the toolbar to enter the dialog box for editing the alarm reclassification rule,
75
Fig. 3.5-256 Dialog Box for Alarm Reclassification Rule Modification
4.
Modify the alarm class and the rule status

Only the reclassification level and the rule status can be modified. Modify the
new reclassification level and the new rule status to activated or inactivated.
5.

reclassification rule management shown in Fig. 3.5-253.
[Verification]
The corresponding dialog box indicating operation success will be shown in the
interface. In this case, the alarm reclassification rule list will display the modified
reclassification rule. The rules in activated status will be applied while those
inactivated will not be applied but only listed.
cause.
76
3.5.3.3Deleting a Reclassification Rule

[Objective]
The created alarm reclassification rule can be deleted.
[Preliminary setup]
1.
2.
The alarm reclassification rule has been created before.
[Required steps]
1.
2.
3.
Select the reclassification rule to be deleted and execute the deletion operation.
4.
1.

2.

reclassification rule management, as shown in Fig. 3.5-253 .
3.
Select the reclassification rule to be deleted and execute the deletion operation
In the dialog box for alarm reclassification rule management, select the rule to
be deleted, and click <Delete Alarm Reclassification Rule> on the toolbar.
4.

Click <OK> to complete the deletion operation.
[Verification]
interface. In this case, this rule will be deleted from the alarm reclassification rule list,
77
cause.
78
3.5.4Correlation Rule
The alarm correlation rule includes: decreasing the alarms presented before users;
process multiple correlated alarms as one alarm; hiding minor alarms when important
alarms are activated.
The alarm correlation rule includes suppress rule, count rule and compress rule. The
correlation rule management includes: creation, modification and deletion of the
correlation rule.
1.
Suppress rule
Suppress rule: When two different alarms caused by the same cause occur
simultaneously, the main alarm will substitute for the subordinate one to display.
When the main alarm instead of the subordinate one is cleared, users can select
whether to display the latter.
2.
Count rule
Count rule: Some unimportant alarms, when occurring once or twice, do not
count. However, if there are so many alarms occurring frequently within a short
period of time and are automatically recovered rapidly, it shows that there is a
serious fault and a new alarm will occur. The new alarm has its alarm code,
alarm class and alarm information, all of which can be defined by users
themselves.
3.
compress rule
Multiple alarms caused by the same reason have different objects but the same
alarm code. They can be combined into one alarm.
The user can query correlated alarms to view all source alarms. Users can finally see
the following information: alarms upon correlation processing, source alarms and
details of the applied correlation rule. A new alarm, after correlation processing, will be
displayed in the alarm list of the alarm main interface.
79
3.5.4.1Creating a Correlation Suppression Rule

[Objective]
Create a correlation suppress rule.
[Preliminary setup]
with the OMCR.
[Required steps]
1.
2.
Enter the interface for alarm correlation rule management.
3.
Enter the dialog box for alarm correlation rule creation.
4.
Set the objects and the alarm codes for the main and subordinate alarms.
5.
Select whether to show the subordinate alarm after the main alarm is cleared.
6.
1.

2.
Enter the interface for alarm correlation rule management

Select [SetupAlarm RuleAlarm Correlation Rule] from the main interface
for alarm management to enter the dialog box for alarm correlation rule
80
Fig. 3.5-257 Dialog Box for Alarm Correlation Rule Management.
3.
Enter the dialog box for alarm correlation rule creation

Click <Alarm Correlation Rule Editor> on the toolbar in the dialog box for
alarm correlation rule management to enter the dialog box for creating an alarm
correlation rule, as shown in Fig. 3.5-258. Select the suppression rule as the rule
type.
Fig. 3.5-258 Dialog Box for Suppress Rule Creation
4.
Set the objects and the alarm codes for the main and subordinate alarms
81
Select <Managed Object> from the main alarm part to enter the object selection
dialog box shown in Fig. 3.5-259.
Fig. 3.5-259 Managed Object Selection Dialog Box
box. The selected objected will be shown in the upper single-line box. Press
<OK> to acknowledge object selection and return to the dialog box as shown in
Fig. 3.5-258.
Select the alarm code for the main alarm from the pull-down box.
Select <Managed Object> from the subordinate alarm part to enter the object
selection dialog box shown in Fig. 3.5-259. The operation is the same as that of
selecting the object for the main alarm.
Select the alarm code for the subordinate alarm from the pull-down list box.
5.
Select whether to show the subordinate alarm after the main alarm is cleared
Select to activate or inactivate the rule. Only those activated rules can be
applied.
Select whether to show the subordinate alarm after the main alarm is cleared.
6.

correlation rule management shown in Fig. 3.5-257.
82
[Verification]
interface. In this case, the alarm correlation rule list will list the created correlation
suppress rule. When two different alarms with the same cause appear at the same time,
the main alarm will be shown instead of the subordinate one.
cause.
83
3.5.4.2Creating a Correlation Count Rule

[Objective]
Create a correlation count rule.
[Preliminary setup]
with the OMCR.
[Required steps]
1.
2.
3.
4.
Set the contents of the new alarm.
5.
Select the property such as rule status.
6.
1.

2.

3.

correlation rule, as shown in Fig. 3.5-260. Select the account rule as the rule
type.
84
Fig. 3.5-260 Dialog Box for New Count Rule Creation
4.
Set the contents of the new alarm

Select <Managed Object> from the main alarm part to enter the object selection
dialog box shown in Fig. 3.5-261.
Fig. 3.5-261 Managed Object Selection Dialog Box
85
box. The selected objected will be shown in the upper single-line box. Click
<OK> to configure the object selection and return to the dialog box shown in
Fig. 3.5-260.
Select the alarm code for the main alarm from the pull-down box.
In the new alarm part, set the count number and interval of the main alarm. The
new alarm is generated when the alarm frequency reaches the set count number
within the set count interval. Set the alarm class, alarm code and alarm contents
for the new alarm.
5.
Select the property such as rule status

applied.
Input the comments of this rule.
6.

[Verification]
count rule. When the main alarm totals the set number of count within the set count
interval, a new alarm will occur.
cause.
86
3.5.4.3Creating a Correlation Compress Rule

[Objective]
Create a correlation compress rule.
[Preliminary setup]
with the OMCR.
[Required steps]
1.
2.
3.
4.
Set the alarm code for the main alarm.
5.
Set the property such as rule status.
6.
1.

2.

3.

correlation rule, as shown in Fig. 3.5-262. Select the compress rule as the rule
type.
87
Fig. 3.5-262 Dialog Box for Compress Rule Creation
4.
Set the alarm code for the main alarm

In the main alarm part, select the alarm code for the main alarm from the pulldown list box.
5.
Set the property such as rule status

applied.
Input the comment of this created rule in the rule comment text box.
5.

[Verification]
compress rule. The alarm with the same alarm code after the compressing will be
compressed in the alarm list of the main interface into an alarm. That is to say, only the
first primary alarm not recovered will be displayed.
88
cause.
3.5.4.4Modifying a Correlation Rule
[Objective]
The created alarm correlation rule can be modified.
[Preliminary setup]
1.
2.
The alarm correlation rule has been created.
[Required steps]
1.
2.
Enter the alarm correlation rule setting interface.
3.
4.
Modify the contents of the correlation rule.
5.
1.

2.
Enter the alarm correlation rule setting interface

3.

In the dialog box for alarm correlation rule management, select the rule to be
modified, and click <Modify Alarm Correlation Rule> on the toolbar to enter the
dialog box for editing the alarm correlation rule.
4.
Modify the contents of the correlation rule
89
The status of any correlation rule can be modified to activated or inactivated to

decide whether this rule is applied or not.
A suppress rule can be modified in terms of its rule status, whether the
subordinate alarm is displayed and the rule comments are modified after the
main alarm is cleared, as shown in Fig. 3.5-263.
Fig. 3.5-263 Dialog Box for Suppress Rule Modification
For a count rule, the following information can be modified such as the count
No. and the count interval of the main alarm, the alarm class and alarm code of
the new alarm, the displayed alarm contents, and rule comments, as shown in
Fig. 3.5-264.
90
Fig. 3.5-264 Dialog Box for Count Rule Modification
A compress rule can only be modified in terms of its rule status and rule
comment, as shown in Fig. 3.5-265.
Fig. 3.5-265 Dialog Box for Compress Rule Modification
91
5.

[Verification]
interface. In this case, the alarm correlation rule list will list the created correlation rule
based on the modified contents. It is up to the modified rule status whether this rule is
applied or not.
cause.
92
3.5.4.5Deleting a Correlation Rule

[Objective]
The created alarm correlation rule can be deleted.
[Preliminary setup]
1.
2.
The alarm correlation rule has been created.
[Required steps]
1.
2.
Enter the alarm correlation rule setting interface.
3.
Select the correlation rule to be deleted and execute the deletion operation.
4.
1.

2.
Enter the alarm correlation rule setting interface

3.
Select the correlation rule to be deleted and execute the deletion operation
In the dialog box for alarm correlation rule management, select the rule to be
deleted, and click <Delete Alarm Correlation Rule> on the toolbar.
4.

correlation rule management shown in Fig. 3.5-257
[Verification]
93
rule, or the dialog box indicating operation failure will be shown together with the
failure cause.
3.6Man-machine Operations of BSC Boards

Users with corresponding right can perform man-machine command operations on
some BSC boards. The man-machine commands are divided into the following types
according to their functions
1.
Board status query (MP, SYCK, AIPP, BIPP, FSPP, NSPP, TCPP, COMI, TIC,
SMB, DRT, EDRT, DTI).
2.
Master/slave changeover (master MP, SYCK, DSNI, BOSN, AIPP, BIPP, FSPP,
NSPP, TCPP, COMI).
3.
Reset (master MP, BOSN, AIPP, BIPP, FSPP, NSPP, TCPP, COMI, TIC, SMB,
DRT, EDRT, DTI).
4.
Offline and cancellation of offline (slave MP)
5.
Changeover enable and changeover disable (SYCK).
6.
Set clock reference (SYCK,CKI).
7.
Set clock mode (SYCK)
8.
Set periodic changeover and cancellation periodic changeover (master MP)
94
3.6.1Viewing the Master/Slave Status of the Board

[Objective]
View the master/slave status of the board.
[Preliminary setup]
1.
2.
This operation is applicable to such boards of the BSC as MP, SYCK, AIPP,
BIPP, FSPP, NSPP, TCPP, COMI, BOSN, DSNI and such boards of the BTS as
EBIE, BIEP, OMU, CKU, CMM.
[Required steps]
1.
2.
Enter the rack view and select the board.
3.
Right-click to view the master/slave status of the board.
1.

2.
Enter the rack view and select the board.

In the main interface for alarm management, select the rack to be viewed on the
navigation tree. For example, query the master/slave status of the master MP of
the BSC. Select [ViewPhyView] from the main interface to enter the rack
view, as shown in Fig. 3.6-266.
95
Fig. 3.6-266 Alarm Physical View Interface
3.
Execute the board status query operation.

Right-click the board in the BSC rack view and its master/slave status can be
seen in the shortcut menu, as shown in Fig. 3.6-267.
Fig. 3.6-267 View the Master/Slave Status
[Verification]
If the board is in master status, the master status will be shown in the right-click menu;
if the board is in slave status, the slave status will be shown.
96
3.6.2Viewing the Running Status of the Board

[Objective]
View the running status of the BSC board.
[Preliminary setup]
1.
2.
This operation is applicable to the master MP, SYCK, AIPP, BIPP, FSPP, NSPP,
TCPP, COMI, BOSN, DTI, TIC, EDRT, DRT, SMB.
[Required steps]
1.
2.
Enter the BSC rack view and select the board.
3.
1.

2.

navigation tree. You can select [ViewPhyView] from the main interface to
enter the BSC rack view, as shown in Fig. 3.6-266.
3.

Right-click the board in the BSC rack view and select [Query Board Status] in
the shortcut menu.
[Verification]
97
Fig. 3.6-268 Board Status Information Display
The properties of the board are shown in the dialog box. The properties vary with
different board types and reflect the contents of some properties of the COMI board.
cause.
98
3.6.3Resetting the BSC Board

[Objective]
Execute the BSC board reset operation
[Preliminary setup]
1.
2.
BIPP, FSPP, NSPP, TCPP, COMI, BOSN, DTI, TIC, EDRT, DRT, SMB.
[Required steps]
1.
2.
3.
Execute the board reset operation
1.

2.

enter the BSC rack view and select the board to be reset, as shown in Fig. 3.6266.
3.

Right-click the board in the BSC rack view and select [Reset] in the shortcut
menu. The acknowledgment dialog box pops up, as shown in Fig. 3.6-269. Click
<OK> to complete the operation.
99
Fig. 3.6-269 Reset Confirmation Dialog Box
[Verification]
The command box will show the information indicating command execution success
or the dialog box indicating operation failure together with the failure cause will be
shown, accompanied by failure information in the command box.
100
3.6.4Executing the Master/Slave Board Changeover

[Objective]
Execute the master/slave board changeover.
[Preliminary setup]
1.
2.
BIPP, FSPP, NSPP, TCPP, COMI, BOSN, DTI, TIC, EDRT, DRT, and SMB.
[Required steps]
1.
2.
3.
Execute the master/slave board changeover.
1.

2.

In the main interface for alarm management select the rack to be viewed on the
enter the BSC rack view and select the board for which the master/slave
changeover shall be executed, as shown in Fig. 3.6-266.
3.
Execute the master/slave board changeover

Right-click the board in the BSC rack view and select [Master/Slave
Changeover] in the shortcut menu. The confirmation dialog box pops up, as
shown in Fig. 3.6-270. Click <OK> to complete the operation.
101
Fig. 3.6-270 Board Changeover Confirmation Dialog Box
[Verification]
The command box will show the information indicating command execution success.
102
3.6.5Setting the Periodic Changeover for MP

[Objective]
Set the periodic changeover for MP.
[Preliminary setup]
1.
2.
This operation is only applicable to the master MP.
[Required steps]
1.
2.
Enter the BSC rack view and select the master MP.
3.
Set the periodic changeover for MP
1.

2.
Enter the BSC rack view and select the master MP.
In the main interface for alarm management select the rack to be viewed on the
enter the BSC rack view, as shown in Fig. 3.6-266. Select the master MP in the
figure.
3.
Set the periodic changeover for MP

Right-click the MP board in the BSC rack view and select [Setup Periodic
Changeover] in the shortcut menu. The board command parameter setting dialog
box pops up, as shown in Fig. 3.6-271.
103
Fig. 3.6-271 Periodic Changeover Setting Dialog Box
Select the changeover time and click <OK>.

[Verification]
Upon operation success, the changeover for the master MP will be executed at the
specified time.
cause.
104
3.6.6Executing the Offline Operation for MP

[Objective]
Execute the off-line operation for the slave MP. An offline operation is generally used
for maintenance.
[Preliminary setup]
1.
2.
This operation is only applicable to the slave MP board.
[Required steps]
1.
2.
Enter the BSC rack view and select the slave MP board.
3.
Execute the offline operation.
1.

2.
Enter the BSC rack view and select the slave MP board.
enter the BSC rack view, as shown in Fig. 3.6-266. Select the slave MP in the
figure.
3.
Execute the offline operation for MP

Right-click the slave MP board in the BSC rack view and select [Off-Line] in
the shortcut menu. The confirmation dialog box pops up, as shown in Fig. 3.6272.
105
Fig. 3.6-272 Board Off-line Confirmation Dialog Box
[Verification]
After the slave MP is offline, the slave MP will not monitor the master MP within 6
minutes. That is, the power-off of the master MP will not lead to the slave MP being an
master one. If the offline mode is not cancelled after 6 minutes, the offline mode of
the slave MP will be cancelled automatically and change to the online status.
cause.
106
3.6.7Setting the Clock Reference of SYCK

[Objective]
Set the clock reference of SYCK.
[Preliminary setup]
1.
2.
This operation is only applicable to SYCK boards.
[Required steps]
1.
2.
Enter the BSC rack view and select the SYCK board.
3.
Set the clock reference
4.
Click <OK> to complete the operation.
1.

2.
Enter the BSC rack and select the SYCK board.

enter the BSC rack view, as shown in Fig. 3.6-273. Select the SYCK.
107
Fig. 3.6-273 Alarm Physical View
3.
Set the clock reference

Right-click the SYCK board in the BSC rack view and select [Setup SYCK
Clock Reference] in the shortcut menu. The board parameter setting dialog box
pops up, as shown in Fig. 3.6-274.
Fig. 3.6-274 Dialog Box for Setting SYCK Clock Reference
Select a clock reference.

4.
108
[Verification]
The clock reference of this SYCK is set and the command box will show information
indicating command execution success.
cause.
109
3.6.8Setting the Clock Reference of CKI

[Objective]
Set the clock reference of CKI.
[Preliminary setup]
1.
2.
The SYCK board is normal. This command operates and sends commands
through the SYCK board.
[Required steps]
1.
2.
3.
4.
1.

2.

enter the BSC rack view, as shown in Fig. 3.6-273. Select the SYCK board.
3.

Right-click the SYCK board in the BSC rack view and select [Setup CKI Clock
Reference] in the shortcut menu. The board parameter setting dialog box pops
up, as shown in Fig. 3.6-275.
110
Fig. 3.6-275 Dialog Box for Setting CKI Clock Reference
Select a clock reference.

4.
[Verification]
The clock reference of this CKI is set and the command box will show information
cause.
111
3.6.9Setting the Clock Mode of SYCK

[Objective]
Set the clock mode of SYCK
[Preliminary setup]
1.
2.
[Required steps]
1.
2.
3.
Set the SYCK clock mode.
4.
1.

2.

enter the BSC rack view, as shown in Fig. 3.6-273. Select the SYCK as shown
in the figure.
3.
Set the clock mode of SYCK

Right-click the SYCK board in the BSC rack view and select [Setup SYCK
Clock Mode] in the shortcut menu. The board command parameter setting
dialog box pops up, as shown in Fig. 3.6-276.
112
Fig. 3.6-276 Dialog Box for Setting SYCK Clock Mode
Select a clock mode from the list.

4.
[Verification]
If the operation is successful, the clock mode of this SYCK is set and the command
box will show information indicating command execution success.
cause.
113
3.6.10Setting Permitting the SYCK Changeover

[Objective]
Set permitting the SYCK changeover.
[Preliminary setup]
1.
2.
[Required steps]
1.
2.
3.
Execute the operation of permitting the SYCK changeover.
1.

2.

enter the BSC rack view, as shown in Fig. 3.6-273. Select the SYCK as shown
in the figure.
3.
Execute the operation of permitting the SYCK changeover

Right-click the SYCK board in the BSC rack view and select [Enable SYCK
clock reference changeover] in the shortcut menu. The confirmation dialog box
pops up, as shown in Fig. 3.6-277. Click <OK> to complete the operation.
114
Fig. 3.6-277 Dialog Box for Confirming Clock Reference Permission
[Verification]
If the operation is successful, the clock reference of this SYCK is switched over and
the command box will show the information indicating command execution success.
cause.
115
3.6.11Resetting a Site Remotely

[Objective]
Reset a site remotely.
[Preliminary setup]
Ensure that the whole system is running normally, and the BSC is normally connected
to OMCR and the BTS.
[Required steps]
1.
2.
Enter the physical site rack view and select the board according to the site type.
3.
Reset the site remotely.
1.

2.
Enter the physical site rack view and select the board.
Select the physical site rack to be viewed on the navigation tree in the main
interface for alarm interface. For the BTS1.0 and BTSV1.0 (A), select the OMU
board; for the BTSV2.0, BS21 and BS30, BS30V1.2, select the CMM board; for
the MB/EMB, select the SCU board. Take an example for resetting the BTSV1.0
(A). Select [ViewPhyView] in the main interface and enter the physical site
rack view, and select the OMU board, as shown in Fig. 3.6-278.
116
3.

Right-click the OMU board in the physical site rack view and select [Remote
Reset] in the shortcut menu. The confirmation dialog box pops up, as shown in
Fig. 3.6-279. Click <OK> to complete the operation.
Fig. 3.6-279 Dialog Box for Remote Reset Confirmation
[Verification]
If the operation is successful, the site is reset and the command box will show the
information indicating command execution success.
117
3.6.12Resetting the BTS Board Remotely

[Objective]
Reset the BTS board remotely.
[Preliminary setup]
1.
Ensure that the whole system is running normally, and the BSC is normally
connected to OMCR and the BTS.
2.
This operation is applicable to the boards on the BTS rack such as TRU, OMU,
EBIE, CKU, EAM.
[Required steps]
1.
2.
3.
Execute the remote resetting operation.
1.

2.
enter the physical site rack view to select the boards needed to be reset, as
118
3.

Right-click the board in the physical site rack view and select [Remote Reset] in
the shortcut menu. The confirmation dialog box pops up, as shown in Fig. 3.6281. Click <OK> to complete the operation.
Fig. 3.6-281 Dialog Box for Board Reset Confirmation
[Verification]
The command box will show the information indicating command execution success.
119
3.7SMS Alarm Forward Management

SMS alarm forward management means that upon setting the corresponding forward
rule by the user, the system reports the alarm to the user, who may be the system
administrator, that is, the MS user mentioned below, in the form of mobile short
message when the system generates the alarm that meets the condition in this regard.
The following operations are allowed by the alarm forward management.
1.
Enable and disable the alarm forward function of the SMS server .
2.
The management of mobile short message consists of the testing, enabling and
disabling of MS module and the querying and setting of the short message
centre number.
3.
The management of MS user consists of the query, addition, modification and

deletion of the MS user.
4.
The SMS alarm forward rule management consists of the query, creation,
creation by rule, modification and deletion of the alarm forward rule.
5.
The customization of the short message format includes the customization,

default setting and query of the user short message format.
120
3.7.1Enabling the Alarm Forward Function of the SMS Server .

[Objective]
Enabling the Alarm Forward Function of the SMS Server .
[Preliminary setup]
Make sure that the whole system runs normally and the client communicates with the
server normally,
[Required steps]
1.
2.
Enter the alarm forward rule setting interface.
3.
Perform the enabling operations.
1.

2.

Select [SetupAlarm RuleAlarm Forward Rule] from the main interface for
alarm management to enter the dialog box for alarm forward management, as
121
Fig. 3.7-282 SMS Alarm Forward Management Dialog Box
3.
Enabling the Alarm Forward Function of the Server .

Select the [Start server forward function] box in the alarm forward management
dialog box.
[Verification]
If the operation is successful, the system will prompt the enabling success, as shown in
Fig. 3.7-283.
Fig. 3.7-283 Dialog Box for Server Forward Function Success
cause.
122
3.7.2Disabling the SMS Alarm Forward Function

[Objective]
Enabling the SMS Alarm Forward Function of the Server .
[Preliminary setup]
server normally,
[Required steps]
1.
2.
3.
Execute the disabling operations.
1.

2.

alarm management to enter the dialog box for alarm forward rule management,
123
3.
Disable the Alarm Forward Function of the Server.

Cancel the selection of the [Start server forward function] box in the alarm
forward management dialog box.
[Verification]
If the disabling operation is successful, the system will prompt the disabling success.
cause.
124
3.7.3Testing the MS Status

[Objective]
Test the MS status.
[Preliminary setup]
1.
Make sure that the whole system runs normally and the client communicates
with the server normally,
2.
The mobile short message module and the serial port are available.
[Required steps]
1.
2.
3.
Execute the detecting operations.
1.

2.

and select the [MS Management] tab, as shown in Fig. 3.7-284.
3.
Test the MS status.

Click <Test> in the alarm forward management dialog box.
[Verification]
If the MS is online, the system will select <MS Online> selection box.
cause.
125
3.7.4Enabling the MS Module

[Objective]
Enable the MS module.
[Preliminary setup]
1.
with the server normally.
2.
The MS Is online, the serial port is available, and the MS is in disabling status.
[Required steps]
1.
2.
3.
Perform the enabling operations.
1.

2.

3.
Enable the MS module.

Click <Enable> in the alarm forward management dialog box.
[Verification]
If the operation is successful, the MS module is successfully enabled, the command
box shows the information indicating command execution success.
cause.
126
3.7.5Disabling the MS Module

[Objective]
Disable the MS module.
[Preliminary setup]
1.
2.
The MS Is online, the serial port is available, and the MS is in enabling status.
[Required steps]
1.
2.
3.
Execute the disabling operation.
1.

2.

and select [MS Management] tab, as shown in Fig. 3.7-284.
3.
Disable the MS module.

Click <Disable> in the alarm forward management dialog box.
[Verification]
If the operation is successful, the MS module is disabled successfully, and the
command box will show information indicating command execution success.
cause.
127
3.7.6Query the Number of the Short Message Center

[Objective]
Query the number of the short message center.
[Preliminary setup]
1.
with the server normally.
2.
MS module is online and the serial port is available.
[Required steps]
1.
2.
3.
Perform the querying operations.
1.

2.

3.
Set the number of the short message center

Click <Query> in the alarm forward management dialog box.
[Verification]
If the operation is successful, the interface shows the SMC number queried, and the
command box shows the prompt information indicating command execution success.
cause.
128
3.7.7Setting the Number of the Short Message Center

[Objective]
Set the number of the short message center.
[Preliminary setup]
1.
2.
MS module is online and the serial port is available.
[Required steps]
1.
2.
3.
Execute the setting operation.
1.

2.

and select [MS Management], as shown in Fig. 3.7-284.
3.
Set the number of the short message center

Fill in the number of the short message centre to be set in the alarm forward
management dialog box, and click <Setup>.
[Verification]
If the operation is successful, the number of the short message center is set and the
command box will show the information indicating command execution success.
cause.
129
3.7.8Querying MS User information

[Objective]
Query MS user information
[Preliminary setup]
server normally,
[Required steps]
1.
2.
3.
1.

2.

130
3.
Query the MS user information

Click <Query> in the dialog box for alarm forward user management.
[Verification]
If the operation is successful, all the queried user information will be listed in the
dialog box tab for alarm forward user management, and the mobile phone number and
alias of this user can be queried through the use of user ID. In the command box, the
prompt information indicating command execution success will be displayed.
cause.
131
3.7.9Create an MS User
[Objective]
Create an MS user .
[Preliminary setup]
server normally,
[Required steps]
1.
2.
3.
Execute the creating operation.
1.

2.

3.
Create an MS user
Select the user ID as [Create User] in the dialog box for alarm forward
management, fill in the mobile phone number and alias in the users mobile
phone number and alias to select whether to activate them, and then click
<Create>.
[Verification]
If the operation is successful, the new user is created, and a new user ID will be in the
ID list. The command box displays the prompt information indicating command
execution success.
cause.
132
3.7.10Modifying the MS User Information

[Objective]
Modify the user information
[Preliminary setup]
server normally.
[Required steps]
1.
2.
3.
Perform the modifying operations.
1.

2.

and select [MS User Management] tab, as shown in Fig. 3.7-285.
3.
Modify the MS user information

Select the user to be modified in the user ID list, modify the mobile phone
number and alias or whether to activate them, and then click <Modify>.
[Verification]
If the operation is successful, the user information is modified, and the command box
displays the prompt information indicating command execution success.
cause.
133
3.7.11Delete an MS User
[Objective]
Deleting MS users
[Preliminary setup]
server normally.
[Required steps]
1.
2.
3.
Perform the deleting operations.
1.

2.

3.
Delete MS users
Select the user ID to be deleted in the user ID list, and click <Delete>.
[Verification]
If the operation is successful, the user information is deleted, and the command box
displays the prompt information indicating command execution success.
cause.
134
3.7.12Querying All the Forward Rule Information

[Objective]
Query the forward rule information.
[Preliminary setup]
server normally.
[Required steps]
1.
2.
3.
1.

2.

and select the [Edit forward rule] tab, as shown in Fig. 3.7-286.
135
Fig. 3.7-286 Dialog Box For Forward Rule Management
3.
Query the forward rule information

Click <Query> in the [Edit forward rule] tab.
[Verification]
If the operation is successful, the queried information of all the user forward rule is
displayed in the list box, and the command box displays the prompt information
cause.
136
3.7.13Creating the Forward Rule

[Objective]
Create the Forward Rule.
[Preliminary setup]
server normally.
[Required steps]
1.
2.
3.
Execute the creating operation.
1.

2.

3.
Enter the dialog box for alarm forward rule creation

Click <Create> in the [Edit forward rule] tab to pop up the dialog box for
creating the forward rule, as shown in Fig. 3.7-287.
137
Fig. 3.7-287 Dialog Box For Forward Rule Creation
4.
Fill in the user ID and the rule object.

In the dialog box of forward rule creation, select the use ID via the user ID pulldown box. Click <Rule Objects> to pop up a dialog box for rule object
selection, as shown in Fig. 3.7-288, and select the corresponding rule object, and
then click <OK>.
138
5.
Select the rule condition.

In the [Select Condition] combination box, select the match based on alarm class
or alarm code. If matching the alarm based on alarm class, select the
corresponding alarm class in the [Forward Alarm Class]; if on alarm code, select
the corresponding alarm code or notification code in the [Forward
Alarm/Notification Code] combination box.
6.
Select the time period.

In the [Forward Time Period] combination box, select <Periodic Setting>
selection box, and select the start and end time; if an infinite setting is expected,
select <Not limit> selection box.
7.
Select whether to activate the rule or forward the alarm recovery message.
In the dialog box for creating forward rule, if immediate activation of the rule is
expected, select <Activate Rule> selection box; and if the alarm recovery
message forward is expected, select the <Alarm Recovery Message also
Forward> selection box.
8.
Create the forward rule.

In the dialog box for creating forward rule, completely fill in the rule
information according to the above steps, and click <OK>.
[Verification]
If the operation is successful, the corresponding rule is created, and displayed in the
rule list box. The command box displays the prompt information indicating command
execution success.
cause.
139
3.7.14Creating a New Rule According to the Original Rule

[Objective]
Create the new forward rule according to the original forward rule.
[Preliminary setup]
server normally.
[Required steps]
1.
2.
3.
Perform the creating operations.
1.

2.

3.
Create the forward rule.

Select one or more rules in the [Edit forward rule] tab, and select a user in the
[Please select user] (not the same as the user corresponding to the selected rule),
as shown in Fig. 3.7-289, and click <Create>.
140
Fig. 3.7-289 Dialog Box For Forward Rule Creation
[Verification]
If the operation is successful, the selected rule is create in a similar way, and the
cause.
141
3.7.15Querying All the Forward Rule Information

[Objective]
Modifying the forward rule information.
[Preliminary setup]
server normally.
[Required steps]
1.
2.
3.
Perform the modifying operations.
1.

2.

3.
Modifying the forward rule information.

Select the rule to be modified in the rule list, or double-click the rule to be
modified and click <Modify> in the tab, as shown in Fig. 3.7-290. Modify the
corresponding contents of the rule and click <OK>.
142
Fig. 3.7-290 Dialog Box for Modifying Forward Rule
[Verification]
If the operation is successful, the corresponding contents of the rule is modified, and
the command box will show the information indicating command execution success.
cause.
143
3.7.16Deleting the Forward Rule Information

[Objective]
Deleting the forward rule information.
[Preliminary setup]
server normally.
[Required steps]
1.
2.
3.
Perform the deleting operations.
1.

2.

and select the [Edit forward rule], as shown in Fig. 3.7-286.
3.
Deleting the forward rule information.

Select one or more rules in the rule list, and click <Delete>.
[Verification]
If the operation is successful, the corresponding rule is deleted, and the command box
will show information indicating command execution success.
cause.
144
3.7.17Querying the Short Message Format of All the Users

[Objective]
Querying the short message format of all the users
[Preliminary setup]
server normally.
[Required steps]
1.
2.
3.
Execute the operation of querying short message format.
1.

2.

and select [Alarm message format customize] tab, as shown in Fig. 3.7-291.
145
Fig. 3.7-291 Dialog Box for Working out the Short Message Format
3.
Querying alarm message format information of the user.

Click <Query> in the [Alarm message format customize] tab.
[Verification]
If the operation is successful, the system obtains the short message format definitions
of all the users successfully. Select the user to query the definitions of this users short
message format, and the command box displays the prompt information indicating
command execution success.
cause.
146
3.7.18Customizing the Short Message Format

[Objective]
Customize the short message format of a user.
[Preliminary setup]
server normally.
[Required steps]
1.
2.
3.
Execute the operation of customizing short message format.
1.

2.

and select [Alarm message format customize] tab, as shown in Fig. 3.7-291.
3.
Customize the short message format of a user.

Select a user in the [Alarm message format customize] tab, the system displays
the current short message format definition of the user, as shown in Fig. 3.7-292,
modify the items in it and click <Customize>. If the format definition by default
by the system is used, just click <Default setting>.
147
Fig. 3.7-292 Dialog Box for Customizing the Short Message Format
[Verification]
If the operation is successful, the short message format of the user is modified, and the
cause.
148
3.8Test Management
The test management is responsible for the scheduled and instant tests of the Base
Station Subsystem (BSS) and ensures that the whole system runs normally and stably.
In daily maintenance, the test management can test the physical equipment and
communication links through the scheduled test to discover the hidden dangers in time
before the faults occur and adopt suitable measures to prevent the faults from
occurring. When the fault occurs, the test management can use the instant test to help
engineering personnel find out the fault cause as early as possible, locate the fault and
remove the fault as soon as possible. After the troubleshooting, the engineering
personnel can use the test management to test whether the physical equipment and the
system have recovered to normal and ensure that the whole system runs normally and
stably.
The test management includes testing the munits of the BSC, the boards under the unit
and the communication links between the central module MP and the peripheral
module MP and between MP and the main control units of munits, and loops (E1 lines)
between the BSC and the BTS.
The test management provides users with the functions such as scheduled test items,
test interval, test time, pause scheduled test, start scheduled test, delete scheduled test,
create instant test and query and deletion of test results.
149
3.8.1Conducting the Instant Test of Units and Multiple Units (Munit)

[Objective]
The objective of this task is to conduct the instant test for the units and Muints of the
BSC and view the test results to know whether the board works normally and locate the
fault point in time.
The units and Muints of the BSC include:
1.
BOSN unit.
2.
AIPP Muint.
3.
BIPP Muint.
4.
TCPP Muint.
[Preliminary setup]
1.
2.
The test management client has been started and is normally linked to the server.
[Required steps]
1.
Enter the test management main interface and select the instant test.
2.
Create the instant test task for the units and the Muints.
3.
Start the test.
1.
Enter the main interface for test management, select a BSC to be tested instantly
on the navigation tree on the left in the interface and select [Test ModeInstant
Test], as shown in Fig. 3.8-293.
150
Fig. 3.8-293 Select the BSC to be Tested and Select [Instant Test]
2.
Create the instant test task for the units and Muints
Select the [Instant TestCreate Test Task] menu and the units and Muints to be
tested in the window popped up for test objects, as shown in Fig. 3.8-294.
Fig. 3.8-294 Select the Units and Muints to be Tested
The left side of the page is various multiple units, which are generated based on
the configuration of this BSC. After a Muint is selected, all its subordinate
Muints and their Muint Nos. will be correspondingly displayed in the display
box, which is in the middle of the dialog box. After a Muint in the middle
display box is selected, units under the Muint and their Muint Nos. and unit Nos.
will be displayed in the display box, which is on the right of the dialog box. (for
example, 3-0 indicates that the Muint No. is 3 and the unit No. is 0). One
multiple unit or several multiple units can be selected. Once a certain multiple
151
unit is selected, its subordinate units are all selected. After the selection, click
<OK>.
3.
Start the test

The created instant test task will be shown in the task bar on the upper right of
the main interface. Now, select the [Instant TestStart Test] menu option to
start executing the instant test. The test task status will change with the test
progress, as shown in Fig. 3.8-295.
Fig. 3.8-295 Start the Test
[Verification]
The test results can be seen in the box for test results of units and Muints in the
152
Fig. 3.8-296 Test Results of Units, Muints and Links
3.8.2Conducting the Instant Test of the Link

[Objective]
This task is to conduct the instant test for the links of the BSC and view the test results
to know whether the link works normally and locate the fault point in time.
The links of the BSC include:
1.
The link from MP to the Muint.
2.
The link from MP to the peripheral MP.
[Preliminary setup]
1.
2.
[Required steps]
1.
Enter the test management main interface and select instant test.
2.
Create the instant test task for links
3.
Start the test.
153
1.
2.
Create the instant test task for E1s

Select [Instant TestCreate Test task] menu and the link to be tested in the popup window for tested objects, as shown in Fig. 3.8-297.
Fig. 3.8-297 Select the Link to be Tested
On the left side of the tab are shown links, which are generated based on the
configuration of this BSC. After a link is selected, all links under it will be
correspondingly displayed in the display box which is in the middle of the
dialog box. One link or several links can be selected. Once a link is selected, its
subordinate units are all selected. After the selection, click <OK>.
3.
Start the test

The created instant test task will be shown in the task bar on the upper right of
the main interface. Now, select the [Instant TestStart Test] menu option to
start executing the instant test. The test task bar will change with the test
progress.
[Verification]
The test results are shown in the box for test results of units and Muints in the main
154
3.8.3Conducting the Instant Test for E1

[Objective]
E1 is also called PCM and is replaced by PCM hereafter.
This task is to conduct the instant test for one or several PCMs under a rack of a site of
the BSC and view the test results to know whether the PCM works normally and locate
the fault point in time.
[Preliminary setup]
1.
2.
[Required steps]
1.
Enter the test management main interface and select instant test.
2.
Create the instant test task for E1s.
3.
Start the test
1.
2.
Create the instant test task for E1s

Select the [Instant TestCreate Test Task] menu and the information of the
PCM to be tested in the pop-up window of tested objects, including the site No.,
rack No., line No., self-loop mode, as shown in Fig. 3.8-298.
155
Fig. 3.8-298 Select the PCM to be Tested
3.
Start the test

The created instant test task will be shown in the test task bar on the upper right
of the main interface. Now, select the [Instant TestStart Test] menu option to
start executing the instant test. The test task bar will change with the test
progress.
[Verification]
The test results are shown in the box for test results of the PCM at the lower right part
of the main interface, as shown in Fig. 3.8-299.
Fig. 3.8-299 PCM Test Results
156
3.8.4Setting the Periodic Scheduled Test

[Objective]
It is to set the periodic scheduled test task.
The tested objects include:
1.
BOSN unit.
2.
AIPP Muint.
3.
BIPP Muint.
4.
TCPP Muint.
5.
The link from MP to the Muint.
6.
The link from MP to the peripheral MP.
[Preliminary setup]
1.
2.
[Required steps]
1.
Enter the test management main interface and select scheduled test.
2.
Create a scheduled test.
3.
Set the test period and time.
4.
Start the test.
1.
Select a BSC to be tested according to schedule on the navigation tree on the left
in the interface and select [Test ModeInstant Test], as shown in Fig. 3.8-300.
157
Fig. 3.8-300 Select a BSC and [Scheduled Test]
2.
Create a scheduled test

Select the [Scheduled TestCreate Test Task] menu and set the test period and
time in the pop-up window of tested objects, and select the units and Muints to
be tested, as shown in Fig. 3.8-301.
Fig. 3.8-301 Set the Test Period and Select the Object to be Tested
158
3.
Confirm the scheduled test:

If there is a scheduled test originally, click <OK> in step 2 and a window will
pop up for users to confirm whether to overwrite the original test, as shown in
Fig. 3.8-302. Otherwise, click <OK> in the window in the above step and the
window for setting success will pop up, as shown in Fig. 3.8-303.
Fig. 3.8-302 Window for Original Test Overwrite Confirmation
Fig. 3.8-303 First Scheduled Test Setup Success
4.
The created scheduled test task will be shown in the test task bar on the upper
right of the main interface, as shown in Fig. 3.8-304.
Fig. 3.8-304 Main Interface Upon Completion of Scheduled Test Setup
159
[Verification]
When the test time is reached, the system automatically call the scheduled test
according to the set cycle and time.
160
3.8.5Suspending a Scheduled Test

[Objective]
This task is to temporarily suspend the scheduled test.
[Preliminary setup]
1.
2.
3.
There is already a created scheduled test.
[Required steps]
Select [Suspend Scheduled Test] in the [Scheduled Test] menu
1.
Select a BSC for which the scheduled test shall be suspended on the navigation
tree on the left in the interface and select [Scheduled Test task Suspend
Scheduled Test], as shown in Fig. 3.8-305.
Fig. 3.8-305 Suspend Scheduled Test
161
2.
After the above step is executed, a window will pop up for confirmation, as
Fig. 3.8-306 Suspend Test Confirmation
[Verification]
The system temporarily suspends the periodic scheduled test, as shown in Fig. 3.8-307.
Fig. 3.8-307 Test after Being Suspended
162
3.8.6Restarting a Scheduled Test

[Objective]
This task is to restart the paused scheduled task.
[Preliminary setup]
1.
2.
3.
The scheduled test has been paused.
[Required steps]
Select [Restart Scheduled Test] in the [Schedule Test] menu.
1.
Select a BSC for which the scheduled test shall be restarted on the navigation
tree on the left in the interface and select [Scheduled TestRestart Schedule
Fig. 3.8-308 Restart Scheduled Test
163
2.
A message window pops up and the user confirm to restart the scheduled test, as
Fig. 3.8-309 Success of Restarting Scheduled Test
[Verification]
The scheduled test task is restarted, and the system starts conducting the scheduled test
periodically, as shown in Fig. 3.8-310.
Fig. 3.8-310 Test Being Restarted
164
3.8.7Deleting a Scheduled Test

[Objective]
This task is to delete the existing scheduled test.
[Preliminary setup]
1.
2.
3.
There is already a created scheduled test.
[Required steps]
Select [Delete Scheduled Test] in the [Scheduled Test] menu.
1.
Select a BSC for which the scheduled test shall be deleted on the navigation tree
on the left in the interface and select [Scheduled TestDelete Scheduled Test]
menu, as shown in Fig. 3.8-311.
Fig. 3.8-311 Delete Scheduled Test
165
2.
A window pops up for confirmation by the user, as shown in Fig.3.8-20.
Fig. 3.8-312 Confirmation of Scheduled Test Deletion
[Verification]
The scheduled test is deleted and the box of scheduled tests at the upper right part of
the main interface is empty.
166
3.8.8Switching the Test Mode

[Objective]
This task is to switch between instant test and scheduled test when viewing or creating
a test task.
[Preliminary setup]
1.
2.
[Required steps]
Select [Instant Test] or [Scheduled Test] in the [Test Mode] menu, or click <Scheduled
Test> or <Instant Test> in the toolbar.
1.
Switch to scheduled test

Select [Test ModeScheduled Test] or click <Scheduled Test> in the toolbar, as
2.
Switch to instant test

Select [Test ModeInstant Test] or click <Instant Test> in the toolbar, as shown
in Fig. 3.8-293.
[Verification]
After the above steps, the corresponding [Scheduled Test] or [Instant Test] menu
becomes available.
167
3.8.9Viewing the Details of Test Results

[Objective]
This task is to view the details of test results, such as number of test codes and BER
number.
[Preliminary setup]
1.
2.
[Required steps]
Select a test result in the test results box and right-click.
1.
Select a test result in the test results box, right-click and select [Details], as
Fig. 3.8-313 View the Details of Test Results
168
2.
The window showing the details of test results pops up, as shown in Fig. 3.8314.
Fig. 3.8-314 Details of Test Results
[Verification]
The details of the selected test results can be seen in the window.
169
3.8.10Re-obtaining the Test Item

[Objective]
This task is to obtain the latest test item according to the current system configuration
so that the test item is consistent with the current system configuration.
[Preliminary setup]
1.
connected to the OMCR.
2.
[Required steps]
Select [ViewRefresh] or click <Refresh> in the toolbar.
1.
Select [ViewRefresh] or click <Refresh> in the toolbar.
2.
A window pops up for the user to confirmation, as shown in Fig. 3.8-315.
Fig. 3.8-315 Refresh Confirmation
[Verification]
After the refresh confirmation, the system reobtains the domain information in the
navigation tree on the left and the test items of the corresponding test objects.
170
3.8.11Querying the Test Results

[Objective]
This task is to view the test results of one or several test objects and test types if
necessary.
[Preliminary setup]
1.
2.
3.
The test result is already available in the database.
[Required steps]
1.
Select [Query Test Result] in the test result menu.
2.
Set the query conditions.
3.
Start the query.
1.
Select the [Test ResultQuery Test Result] menu, as shown in Fig. 3.8-316.
Fig. 3.8-316 Select [Query Test Result]
2.
A window of query conditions pops up. The user can query the test results by
test object, test type, test mode, test result type and test time, as shown in Fig.
3.8-317.
171
Fig. 3.8-317 Set the Test Result Query Condition
After the query conditions are set, click <OK>.

3.
The test results are shown in the test results box at the lower right part of the
main interface, as shown in Fig. 3.8-318.
Fig. 3.8-318 Test Results Query/Display
[Verification]
The results will be shown in the test result box.
172
3.8.12Deleting a Test Result

[Objective]
This task is to delete the test result satisfying a certain conditions, such as the test result
of an object or a type.
[Preliminary setup]
1.
2.
3.
The test result is already available in the database.
[Required steps]
1.
Delete a test result
2.
Set the deletion conditions.
3.
Click <OK> to delete it.
1.
Select the [Test ResultsDelete Test Results] menu, as shown in Fig. 3.8-319.
Fig. 3.8-319 Select [Delete Test Result]
2.
The [Delete conditions] window pops up. The user can query the test results by
test object, test type, test mode, test result type and test time, as shown in Fig.
3.8-320.
173
Fig. 3.8-320 Conditions for Deleting a Test Result
3.
Click <OK> to pop up the window for confirmation by the user, as shown in
Fig. 3.8-321.
Fig. 3.8-321 Confirmation for Deleting a Test Result
[Verification]
If the user clicks <OK>, the test result meeting the deletion conditions will be deleted.
If the user clicks <Cancel>, the test result will still be reserved.
174

ZTE ZXG10BSS V2 Base Station Subsystem Operation Manual I

Uploaded by

Document Information

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

ZTE ZXG10BSS V2 Base Station Subsystem Operation Manual I

Uploaded by

Copyright:

Available Formats

ZXG10-BSS (V2)

Base Station Subsystem

Copyright 2004 ZTE Corporation

Suggestions and Feedback

ZXG10-BSS (V2) Base Station Subsystem Operation Manual I

Equipment installation time

About This Manual

How to Use This Manual

Chapter 1 Operation Safety describes the precautions and guidelines.

Keyboard Operation Convention

Indicate a key or button name, e.g., <Enter>, <Tab>,

<Backspace>, and <a>

<Key 1+Key 2>

Press Key 1 and Key 2 at the same time.

<Key 1, Key 2>

Press Key1 first. Then release Key 1 and press Key 2

Mouse Operation Convention

Refers to quickly clicking the primary mouse button (usually the

Refers to clicking the secondary mouse button (usually the right

Refers to pressing and holding a mouse button and move the

Danger, Warning, Caution and Note Statements

are used throughout this manual to emphasize important and critical

2.3.15 Configuring the Super Large Size Cell ...............................................................................75

2.6.2 Querying the Dynamic Properties of the BSC.....................................................................147

3.2.7 Statisticizing the High-frequency Alarms..............................................................................23

3.5.3 Reclassification Rule Management........................................................................................71

3.7.12 Querying All the Forward Rule Information .....................................................................135

Fig. 2.2-24 Configure the Physical Site - Initialization Panel ...................................................................20

Fig. 2.3-78 Configure the Cascading Site - Rack Configuration ..............................................................56

Fig. 2.3-105 Configure the External Extension Cell..................................................................................78

Fig. 2.3-132 Menu for Data Export Configuration ....................................................................................97

Fig. 2.5-159 Query the Version of General Software...............................................................................124

Fig. 2.6-186 Relevant Operations of the BVC........................................................................................161

Fig. 3.2-213 View the Current Alarms of Board.........................................................................................14

Fig. 3.3-240 Trunk Node Setting................................................................................................................49

Fig. 3.6-267 View the Master/Slave Status.................................................................................................96

Fig. 3.8-294 Select the Units and Muints to be Tested.............................................................................151

Fig. 3.8-321 Confirmation for Deleting a Test Result..............................................................................174

1.1On-site Operation Descriptions

It is suggested to obtain the permission of the relevant management personnel of

ZXG10-BSS (V2) Base Station Subsystem Operation Manual

It is suggested to avoid using probes.

Forbid applying the testing programs such as PPTEST in the day.

It is forbidden to upgrading the version such as PPTEST in the daytime.

1.2Usage Guide to On-site Version Functions

At present, the downlink power control function cannot be enabled (if it is

If it is necessary to enable the MP periodic switching function, a written

It is forbidden to use the flow control based on mobile phone priority.

It is forbidden to use the project switch. It is necessary to apply to the Technical

Chapter 1 Operation Safety

It is forbidden to enable the frequency hopping function without written

ZXG10-BSS (V2) Base Station Subsystem Operation Manual

2.2BSC Data Configuration (Basic Part)

Chapter 2 Configuration Management

Start Integrated Configuration Management,

Edit graphic configuration script

Save and check the configuration script validity

Send configuration script to the server for

Execute the returned MML command set

ZXG10-BSS (V2) Base Station Subsystem Operation Manual

Start Integrated Configuration Management, and

Reversed configuration script

Edit graphic configuration script

Save and check the configuration script validity