ZTE BSS Features

ZTE Corporation
ZTE GSM OMC RAN Test Handbook

Document Version: V1.0 Date of Release:Nov. 2010
The contents of this document are protected by copyright laws and possessed by ZTE CORPORATION. Please keep it properly. Any copy, save, index or distribution of this document or any portion of this document, for any purpose in any form by any means (including, electronic, mechanic, copy, record or other forms) without the prior written consent of ZTE CORPORATION, is prohibited.
ZTE GSM OMC RAN Test Handbook

2013 ZTE Corporation. All rights reserved. ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used without the prior written permission of ZTE. Due to update and improvement of ZTE products and technologies, information in this document is subjected to change without notice.
Page 1 of 71
Version V1.0
Date 2010-11-24
Author
Approved By
Remarks
2013 ZTE Corporation. All rights reserved. ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used without the prior written permission of ZTE. Due to update and improvement of ZTE products and technologies, information in this document is subjected to change without notice.
Page 2 of 71
ZTE GSM System Test Handbook RAN OMC
Contents
Overview..........................................................................................................5 Application Range.........................................................................................5 Reference Criteria........................................................................................5 Symbol and Abbreviations ...........................................................................5 Test Condition.................................................................................................6 Test Surroundings.........................................................................................6 Test Conditions.............................................................................................6 Testing Apparatus.........................................................................................6 2. Topology Management...............................................................................7 2.1 Topology View.........................................................................................7 2.2 Key CM/FM/PM Information Display......................................................7 3. Configuration Management.......................................................................9 3.1 Configuration Management ...................................................................9 3.2 Multi-Mode Base Station Management .................................................9 3.3 Multi Configuration Sets ......................................................................10 3.4 Guide for Configuration.........................................................................11 3.5 Data Synchronization...........................................................................12 3.6 Configuration Data Availability Check..................................................13 3.7 Neighboring Cell Configuration Data Check .......................................14 3.8 Configuration Data Template (GERAN&UTRAN).................................14 3.9 Fast Commissioning of Site .................................................................15 3.10 Configuration Data Upload ................................................................16 3.11 Configuration Rack Map ....................................................................17 3.12 Status Monitoring................................................................................18 3.13 Centralized configuration Management.............................................18 3.14 Configuration import...........................................................................19 3.15 Configuration Data Collection ............................................................20 3.16 Hardware Inventory............................................................................20 4. Fault Management....................................................................................22 4.1 Alarm Monitoring...................................................................................22 Alarm and Notification Query......................................................................22 4.3 Alarm Handle........................................................................................24 Alarm clearance..........................................................................................25 Alarm export by the alarm window to client PC in the format of excel 2007/csv/html .............................................................................................26 Alarm Correlation Rule...............................................................................27 4.5 Alarm Filter Rule...................................................................................31 4.6 Current Alarm Forwarding....................................................................31 4.7 Alarm Synchronization..........................................................................32 4.8 Alarm Knowledge Database.................................................................33 4.9 Visual Alarm..........................................................................................33 4.10 Coloured and Audible Alarm...............................................................34 4.11 Alarm Box Management.....................................................................34 4.12 External Alarm Access........................................................................35 4.13 Diagnosis and Testing .......................................................................36 4.14 Alarm Severity Regrading ..................................................................37 4.17ZXO-07-03-014 VIP Site Alarm Monitoring (GERAN&UTRAN)..........38 5. Performance Management.......................................................................39 5.1 Measurement Task Management.........................................................39 5.2 KPI Management..................................................................................40
Copyright of ZTE Corporation. All Rights Reserved Page 3 of 71
5.3 QoS Monitoring.....................................................................................40 5.5 Performance Data Management..........................................................41 5.5 Performance Report.............................................................................42 5.6 Performance Data Real-time Query.....................................................43 Performance Data export...........................................................................44 User defined indicators management.........................................................45 6. Software Management.............................................................................47 6.1 Software Management.........................................................................47 6.2 Nodes SW Version Check....................................................................49 6.3 Software Installation and Upgrade.......................................................49 6.4 Software Inventory................................................................................52 7. System Management................................................................................53 7.1 Data Backup and Restore....................................................................53 7.2 Automatic data export...........................................................................53 Modify the maximum keep days of database ( For PM and FM)...............54 7.4 Evaluvate the database capacity of PM and FM .................................55 7.5Recollection of PM and FM data from a disconnected NE after reconnect.....................................................................................................55 7.6 System real time monitoring (CPu memory DB hard disk usage)........56 7.7 System Self-Monitoring .......................................................................57 7.8 Link Monitor..........................................................................................57 7.9 Time Management................................................................................58 7.10 License Management.........................................................................59 7.11 Node Hardening..................................................................................59 7.12 Base Station Re-homing....................................................................60 8.Security Management................................................................................61 8.1 User Management................................................................................61 8.2 User Authorization................................................................................62 8.3 Role Management................................................................................62 8.4 Log Management .................................................................................63 9.9. Trace Management.................................................................................65 9.1 Signaling Trace.....................................................................................65 10.10 O&M Infrastructure.............................................................................67 10.1 Telnet Access......................................................................................67 10.2 database Access................................................................................67 11.11 Tool.......................................................................................................68 11.1 NE healthy check................................................................................68 11.2 MML function......................................................................................68 11.3 Online Help.........................................................................................69 12.12 Northbound Interface.........................................................................70 12.1 Itf-N CORBA FM (GERAN &UTRAN).................................................70 12.2 Itf-N FTP PM (GERAN&UTRAN).......................................................71
Copyright of ZTE Corporation. All Rights Reserved
Page 4 of 71
Overview
Application Range Reference Criteria
Items that the following criteria contain form the items of the criteria through quotation. All versions of the criteria are valid after the publication. All criteria will be edited. All parties who use the criteria should discuss the possibility to use the latest version of the following criteria. The standard criteria are as follows: ITU-T M.3400 TMN Management Functions 3GPP TS 32.403 Telecommunication management; Performance Management (PM); Performance measurements - GSM and combined UMTS/GSM
Symbol and Abbreviations
Page 5 of 71
Test Condition
Test Surroundings
Um MS SDR Abis BSC Gb
A
Circuit Core Network
Packet Core Network
OMC Fig. 1 networking of one BSC and one SDR and OMC
Test Conditions
For apparatus test, the equipment room must meet following requirements: 1. Power supply: Rated working voltage: -48V; Max working voltage: -57V; Min working voltage: -40V 2. Grounding point is ready. 3. Temperature: Long-term working conditions: 15C ~ 30C; Short-term working condition: 0C ~ 45C; 4. Humidity: Long-term working condition: 40% ~ 65%; Short-term working condition: 20% ~ 90%
Testing Apparatus
Page 6 of 71
2. Topology Management
2.1 Topology View
Test Item Sub-Item Test Target Test Networking Precondition Test Steps 1. OMC works normally 2. Log on OMC 1. At OMC, open TOPO Management view, Click <View Table> from the toolbar and switch to tabular display; 2. Then tabular Display of Topology Nodes, such as BSC,SDR and so on, will displayed ; Selete logical View 3. Right-click a group or NE in the topology tree or topology view and from the pop-up menu, choose [topology Management->Set Member], the [Set Member] dialog box pops up, to add a member, click <Add>, [Select Nodes] dialog box will pop up, select your desired members to be added, then click <Ok> to exit 4. User also can modify and delete NE via right-click function. 1. Topology Management including the stability of the established interface towards the OMC or towards the installed nodes. 2. Can grouping of certain Nodes. Topology Management Topology Tree & Topology Map Management To verify Topology tree &Management function
Anticipative Result
Test Description Test Result
2.2 Key CM/FM/PM Information Display

Test Item Sub-Item Test Target Test Networking Precondition 1. OMC works normally 2. Log on OMC Topology Management Topology Key CM/FM/PM Information Display To verify Topology Key CM/FM/PM Information Display function
Page 7 of 71
Test Steps
Anticipative Result
1. At OMC, open TOPO Management view, select a NE, put mouse on the NE icon for a few seconds 2. Check the alarm and KPI information displayed on the showing up hint displays current alarm counts and KPI values; 1. The hint displays the alarm counts and KPI values properly 2. Please list down the KPI values displaying. 3. Should Display the alarm list of each NE when right click on that NE.
Page 8 of 71
3. Configuration Management
3.1 Configuration Management
Objectives Test Networking Precondition The purpose of this test case is to verify the functionality of Configuration management. 1. 2. 3. 4. 1. OMC works normally The link between OMC and NE is normal Log on OMC The NE Management of NE Agent is started. At OMC client, Right click [NE Agent] in [Physical View] window of [Topology Management], and select [NE ManagementConfiguration Management] to open the Configuration Management window. 2. In the [Configuration Management] window, User can manage BSC NE. 3. Create/View/Modify/Delete BSC Managed Element. 4. In the same [Configuration Management] window, User can manage SDR NE. 5. Create/View/Modify/Delete Base Station. User can manage RAN architecture NE, such as BSC, SDR All the changeable parameters can modify using this function
Test Steps
Anticipative Result Message Flow Test Description Test Result Parameters Setting
3.2 Multi-Mode Base Station Management

Objectives Test Networking Precondition The purpose of this test case is to verify the functionality of multimode NE are created/managed as separate objects 1. 2. 3. 4.
1. 2.
Test Steps
3. 4.
OMC works normally The link between OMC and NE is normal Log on OMC The NE Management of NE Agent is started At OMC client, open Topology Management view, select NE Agent Right-click NE Agent, select [NE Management>configuration Management] to open configuration management. Right Click SubNetWork -> [Create] -> [Base Station]. On the popup dialog, input parameters, click <OK> to create. Right Click SDR Management Element->Apply Mutex Right to get the Nes mutex right.
Page 9 of 71
ZTE GSM System Test Handbook RAN OMC 5.
6.
1.
Expand SDR Managed Element->Base Station Config. Right Click Base Station Config-> [Create] -> [Base Station Equipment Resource Management]. On the popup dialog, select Radio Mode as WCDMA/GSM and input other parameters, click <OK> to create. Create IUB Transmission, RF Connection Configuration, Antenna Configuration, Rack etc. under Equipment Resource. Right Click Base Station Config-> [Create] -> [Base Station Radio Resource Management]. On the popup dialog, input parameters, click <OK> to create. Create WCDMA Radio Resource, GSM Radio Resource under Radio Resource. Multimode NE can be created as separate objects.
3.3 Multi Configuration Sets

Objectives Test Networking Precondition The purpose of this test case is to verify the functionality of Multi Configuration Sets 1. 2. 3. 4. 1. OMC works normally The link between OMC and NE is normal Log on OMC The NE Management of NE Agent is started. At OMC client, Right click [NE Agent] in [Physical View] window of [Topology Management], and select [NE ManagementConfiguration Management] to open the Configuration Management window. In the [Configuration Management] window, right-click <BSC Managed Element> to apply mutex right. Right-click the master Config set, click [Subtree Duplicate->Subtree Copy], then right-click the [BSC Managed Element], click [Subtree Duplicate->Subtree Paste]. A new Config set whose configuration data is same as the master Config Set will be generated. If the data of Master Config Set has some wrong, the user can double-click the slave Config Set, a tab page will be show in the right window, click the <Switch the Config Set to Master> button. Then the salve Config Set will be changed to the master Config Set. SDR Selection criteria : should be posible to select SDR according to the NE name, NE version,NE hardware type
Page 10 of 71
Test Steps
2. 3.
4. 5.
6.
Anticipative Result
1. 2.
etc. The system support Multi Configuration Sets ; The master Config Sets and the slave Config Sets can switch between each other.
Message Flow Test Description Test Result Parameters Setting
3.4 Guide for Configuration

Objectives Test Networking Precondition The purpose of this test case is to verify the functionality of M 1. OMC works normally 2. The link between OMC and NE is normal 3. Log on OMC 4. The NE Management of NE Agent is started. BSC: 1. Edit template file to prepare equipment's and radios configuration in offline mode, for example SDR transmission template and UtranCell configuration template. 2. At OMC client, Right click [NE Agent] in [Physical View] window of [Topology Management], and select [NE ManagementConfiguration Management] to open the Configuration Management window. 3. In Configuration Management window, right-click <BSC Managed Element> to apply mutex right. 4. Right click <BSC Config Set> to choose [Configuration Guide], then < Configuration Guide > pops up. 5. In the window, click <SDR batch import> in left list, then [SDR batch import] tab page is shown in right window. 6. In the right window, click <Read from Excel template files> and select template file in [Open] window. 7. Click <Execute> to create SDR transmission configuration. 8. During creation CM object, consistency check is run on the parameter values by OMC. 9. In the same window, click<Radio Data->Data of Radio Management Object Batch Import> in left list, then [Data of Radio Management Object Batch Import] tab page is show in right window. 10. In the right window, click <Read Data File> and select template file in [Open] window. 11. Click <Execute> to create UtranCell configuration. 12. During creation CM object, consistency check is run on
Page 11 of 71
Test Steps
Anticipative Result
the parameter values by OMC. SDR: 1. At OMC client, right click [NE Agent] in [Physical View] window of [Topology Management], and select [NE ManagementConfiguration Management] to open the Configuration Management window. 2. Click "SDR management"->"data configuration"->"Batch export Ne Data, select Ne and the export directory, click OK. 3. Click "SDR management"->"data configuration"->"batch offline reverse" ,choose the data file from the directory on step 2,input the ConfigSet Label and Subnetwork, click "OK", 4. Expand configuration resource tree node on the left-side of client and check if SDR node is created and correctly configured. BSC: 1. All equipment's configuration objects can be configured in offline mode. 2. Consistency check is run on the parameter values before these are applied on the NE. SDR: 1. SDR data off-line configuration is successful; 2. Consistency check is run before the parameters are applied on SDR, client returns the result ; 3. Parameter values in the client are in accordance with that set by XML.
3.5 Data Synchronization

Objectives Test Networking Precondition The purpose of this test case is to verify whether NE can synchronize data from OMC. 1. 2. 3. 4. 1. OMC works normally The link between OMC and NE is normal Log on OMC The NE Management of NE Agent is started. At OMC client, Right click [NE Agent] in [Ne Tree] window of [Topology Management], and select [NE Management], click [Configuration Management] to open the Configuration Management window. Select SDR Managed Element and modify SDR parameters such as local cell in OMC.
Page 12 of 71
Test Steps
2.
3. 4. 5. 6. 7. 8. 9. Anticipative Result
Execute Synchronize Modified Tables to synchronize modified data from OMC to SDR. Run LMT and connect to SDR. Check if the data in OMC and in LMT is consistent. Run LTM and connect to SDR; Modify the parameter in the configuration window. Sychronize the modified data Check if the data in OMC and in LMT is consistent.
SDR can synchronize data from OMC and the data in SDR is consistent with OMC. Once the data synchronized the uploaded configurations are activated in SDR. Previous configuration data still available in the NE and can switch to previous configuration if required Any configuration parameter can be modified.
3.6 Configuration Data Availability Check

Objectives Test Networking Precondition The purpose of this test case is to verify the functionality of Configuration Data Availability 1. 2. 3. 4. 1. OMC works normally The link between OMC and NE is normal Log on OMC The NE Management of NE Agent is started. At OMC client, Right click [NE Agent] in [Physical View] window of [Topology Management], and select [NE ManagementConfiguration Management] to open the Configuration Management window. 2. In the [Configuration Management] window, expand the node of Subnetwork. 3. Select a configuration set, then right-click it, a menu popup. 4. Click the <SubTree Validity and Relativity Check>. 5. After the command progress up to 100%, a window will be pop-up which display the result of the Configuration Data Availability Check The Configuration Data Availability Check successful and the results are correct
Test Steps
Page 13 of 71
3.7 Neighboring Cell Configuration Data Check

Objectives Test Networking Precondition The purpose of this test case is to verify the functionality of Neighboring Cell Configuration Data Check 1. 2. 3. 4. 1. 2. 3. 4. 5. Anticipative Result OMC works normally The link between OMC and NE is normal Log on OMC The NE Management of NE Agent is started. At OMC client, select [ConfigurationWireless Config ApplicationCell Tool] to open the Cell Tool window. Click [Set Attribute] and select W or GSM&W, the BSC list will be shown at right, select one or some to operate. Choose [check accord] or [check alone] at left. Click [Browse] to input the directory of saving the result. Click [Execute] to run. 1. Cells that are not configured correctly can be checked out. 2. Either GSM cell or UtranCell can be checked. 3. The file format is Excel.
Test Steps
3.8 Configuration Data Template (GERAN&UTRAN)

Objectives Test Networking Precondition The purpose of this test case is to verify the functionality of Configuration Data Template 1. OMC works normally 2. The link between OMC and NE is normal 3. Log on OMC 4. The NE Management of NE Agent is started. BSC: 1. Edit template file to prepare equipment's and radios configuration in offline mode, for example SDR transmission template and UtranCell configuration template. 2. At OMC client, Right click [NE Agent] in [Physical View] window of [Topology Management], and select [NE ManagementConfiguration Management] to open the Configuration Management window. 3. In Configuration Management window, right-click <BSC Managed Element> to apply mutex right. 4. Right click <BSC Config Set> to choose [Configuration Guide], then < Configuration Guide > pops up.
Page 14 of 71
Test Steps
5. In the window, click <SDR batch import> in left list, then [SDR batch import] tab page is shown in right window. 6. In the right window, click <Read from Excel template files> and select template file in [Open] window. 7. Click <Execute> to create SDR transmission configuration. 8. During creation CM object, consistency check is run on the parameter values by OMC. 9. In the same window, click<Radio Data->Data of Radio Management Object Batch Import> in left list, then [Data of Radio Management Object Batch Import] tab page is show in right window. 10. In the right window, click <Read Data File> and select template file in [Open] window. 11. Click <Execute> to create UtranCell configuration. 12. During creation CM object, consistency check is run on the parameter values by OMC. SDR: 1. At OMC client, right click [NE Agent] in [Physical View] window of [Topology Management], and select [NE ManagementConfiguration Management] to open the Configuration Management window. 2. Click "SDR management"->"data configuration"->"Batch export Ne Data, select Ne and the export directory, click OK. 3. Click "SDR management"->"data configuration"->"batch offline reverse" ,choose the data file from the directory on step 2,input the ConfigSet Label and Subnetwork, click "OK", Expand configuration resource tree node on the left-side of client and check if SDR node is created and correctly configured. The Configuration Data Template work successful and the results are correct.
3.9 Fast Commissioning of Site

Objectives Test Networking Precondition The purpose of this test case is to verify the functionality of Fast Commissioning of site. 1. OMC works normally 2. The link between OMC and NE is normal 3. Log on OMC
Page 15 of 71
Test Steps
4. The NE Management of NE Agent is started. SDR: 1. Xml data files prepared. 2. At OMC client, right click [NE Agent] in [Physical View] window of [Topology Management], and select [NE ManagementConfiguration Management] to open the Configuration Management window. 3. Right click the Configuration Resource Tree node, select Create -> SubNetwork , input the SubNetwork ID,then click OK. 4. Click "SDR Configuration Management"->"Batch offline reverse",choose the data files from the directory on step 1,input the ConfigSet Label and select the Subnetwork on step 3, click Selcet all ,then click "OK". 5. Expand Configuration Resource Tree node on the leftside of client ,select the SubNetwork on step 3, and check if SDR nodes are created and correctly configured. Configuration successful.
3.10 Configuration Data Upload

Objectives Test Networking Precondition The purpose of this test case is to verify the functionality of configuration data upload 1. OMC works normally 2. The link between OMC and NE is normal 3. Log on OMC 4. The NE Management of NE Agent is started. BSC: 1. At OMC client, Right click [NE Agent] in [Physical View] window of [Topology Management], and select [NE ManagementConfiguration Management] to open the Configuration Management window. 2. In Configuration Management window, right-click <BSC Managed Element> to apply mutex right. 3. Double click the node of [BSC Managed Element], the tab page shows in the right window. 4. Click the <Data Upload> button, a new Config Set will be generated. SDR: 1. At OMC client, right click [NE Agent] in [Physical View] window of [Topology Management], and select [NE ManagementConfiguration Management] to open the
Page 16 of 71
Test Steps
Configuration Management window. 2. Right click [ZXSDR ManagedElement->Base Station Configuration Wizard(SDR)], a window pop-up. 3. Select [Configure by Base Station data], then click <next>, click <yes>. 4. A new Config Set will be generated. The configuration data can be upload successful
3.11 Configuration Rack Map

Objectives Test Networking Precondition The purpose of this test case is to verify the functionality of Configuration Rack Map 1. OMC works normally 2. The link between OMC and NE is normal 3. Log on OMC 4. The NE Management of NE Agent is started. Configuration Rack Map: 1. At OMC client, Right click [NE Agent] in [Physical View] window of [Topology Management], and select [NE ManagementConfiguration Management] to open the Configuration Management window. 2. In Configuration Management window, right-click <BSC Managed Element> to apply mutex right. 3. Expand [Subnetwork->BSC ManaedElement->BSC Config Set->BSC Ground Resource Management], then double-click <RACK> to open the Configuration rack map. 4. In this rack map, user can add/modify/delete/view boards, shelf. Alarm Rack Map: 1. At OMC client, Right click [NE Agent] in [Physical View] window of [Topology Management], and expand the node of [AMO->Subnetwork->ME] 2. Right click [ME], select [Open Rack Diagram], then the Alarm RACK Map pop-up. 3. In this rack map, the state of every board will be shown; user can query the current alarm and history alarm of every board.
1. 2.
Test Steps
Anticipative Result
The user can dd/modify/delete/view boards and shelf in the configuration Rack. User can query alarm in the Alarm Rack map.
Page 17 of 71
3.12 Status Monitoring

Objectives Test Networking Precondition The purpose of this test case is to verify the functionality of Status Monitoring 1. 2. 3. 4. 1. OMC works normally The link between OMC and NE is normal Log on OMC The NE Management of NE Agent is started. At OMC client, Right click [NE Agent] in [Physical View] window of [Topology Management], and select [NE ManagementConfiguration Management] to open the Configuration Management window. 2. In Configuration Management window, right-click <BSC Managed Element> to apply mutex right. 3. Click [BSC ManagedElement->Open BSC Configuration Centralized Management], a window pop-up. 4. In the menu of [Dynamic data management object], user can query and manage system resource, such as unit, IMAlink, PVC and so on. User can query and manage system resource in the [Dynamic data management object] interface
Test Steps
3.13 Centralized configuration Management

Objectives Test Networking Precondition The purpose of this test case is to verify the functionality of multimode NE are created/managed as separate objects 1. 2. 3. 4.
1. 2.
Test Steps
OMC works normally The link between OMC and NE is normal Log on OMC The NE Management of NE Agent is started At OMC client, open Topology Management view, select NE Agent Right-click NE Agent, select [NE Management>configuration Management] to open configuration
Page 18 of 71
3. 4. 5.
6.
management. Right Click SubNetWork -> [Create] -> [Base Station]. On the popup dialog, input parameters, click <OK> to create. Right Click SDR Management Element->Apply Mutex Right to get the Nes mutex right. Expand SDR Managed Element->Base Station Config. Right Click Base Station Config-> [Create] -> [Base Station Equipment Resource Management]. On the popup dialog, select Radio Mode as WCDMA/GSM and input other parameters, click <OK> to create. Create IUB Transmission, RF Connection Configuration, Antenna Configuration, Rack etc. under Equipment Resource. Right Click Base Station Config-> [Create] -> [Base Station Radio Resource Management]. On the popup dialog, input parameters, click <OK> to create. Create WCDMA Radio Resource, GSM Radio Resource under Radio Resource. Multimode NE can be created as separate objects.
3.14 Configuration import

Test Item Sub-Item Test Target Test Networking Precondition Configuration Management Configuration import To verify Configuration import function As shown in Fig.1 1. 2. 3. 4. RAN and core network work normally The link between OMC and NE is normal OMC works normally Log on OMC
Test Steps
Anticipative Result Test Description Test Result
1. At OMC, open Configuration Management view and select NE; 2. Choose Management-> Data Management->Data Recover, select NE and configuration set to import configuration data. Configuration data can be imported from a different path of the EMS server or from the client PC
Page 19 of 71
3.15 Configuration Data Collection

Objectives Test Networking Precondition The purpose of this test case is to verify the functionality of configuration data collection 1. 2. 3. 4. 1. OMC works normally The link between OMC and NE is normal Log on OMC The NE Management of NE Agent is started. At OMC client, Right click [NE Agent] in [Physical View] window of [Topology Management], and select [NE ManagementConfiguration Management] to open the Configuration Management window. 2. Select the node of [BSC managed Element] in the left tree, then click the menu of [BSC ManagedElement>Configuration Data Export Tool], a window pop-up. 3. In this window, user can select configuration data which need to export, then click<Export Data> button, select a path to save the files. 4. The configuration data can be export to excel 2007 or xml format. The configuration data can be exported successful
Test Steps
3.16 Hardware Inventory

Objectives Test Networking Precondition The purpose of this test case is to verify the functionality of Hardware inventory. 1. 2. 3. 4. 1. OMC works normally The link between OMC and NE is normal Log on OMC The NE Management of NE Agent is started. In the Topology Management, click[Configuration>Wireless Config Application->Inventory Management], the interface of <Inventory Management> pop-up. 2. In this interface, user can export/import the inventory information. 3. Click [View->SW/HW inventory] to query the SW/HW inventory information. 4. Click [Operation->Synchronize all/Single Subnet] to synchronize the inventory information.
Page 20 of 71
Test Steps
User can query an operation the hardware inventory information successful
Page 21 of 71
4. Fault Management
4.1 Alarm Monitoring
Test Item Sub-Item Test Target Test Networking Precondition 1. 2. 3. 4. 1. 2. RAN work normally The link between OMC and NE is normal OMC works normally Log on OMC Reset some BSC boards to generate some BSC alarm Enter Fault Management Interface, [Alarm Monitoring] view will shows default, find the alarms in the realtime alarm list Fault Management Alarm Monitoring To verify Alarm Real Time Monitor function
Test Steps
Anticipative Result
All alarms of RAN will display in Realtime Alarm Monitor, the newly generated alarms can be found in the realtime alarm list Selective options for the real time browser include NE, NE type, severity, alarm occurrence time etc And also these selected conditions can be saved as a template.
Alarm and Notification Query

Test Item Sub-Item Test Target Test Networking Precondition 1. 2. 3. 4. NEs and OSS are normal in communication OSS server and client are normal in communication Network elements has been configured There are current alarms/history alarm/notifications. Fault Management Alarm and Notification Query To verify Alarm Query function
Page 22 of 71
Test Steps
1. 2.
Open View Fault Management. Choose Query-> View Current Alarms; click the
Quick search button on the toolbar, and select conditions wanted, then Click OK. It will show the query result of the current alarms according to the query conditions. Or user can choose New to create and save a new alarm views/filters, then pick on it and click the button Execute on the toolbar. It will show the query result of the current alarms according to the filters; 3. In the window of View Current Alarms which show the query result of the current alarms, click the button Export All Columns in the toolbar, put in the file name and the path you want to save the report, select a type of file ,such as xls; 4. Back to Query-> View History Alarms; click the Quick search button on the toolbar, and select conditions wanted, then Click OK. It will show the query result of the history alarms according to the query conditions. Or user can choose New to create and save a new alarm views/filters, then pick on it and click the button Execute on the toolbar. It will show the query result of the history alarms according to the filters 5. In the window of View History Alarms which show the query result of the history alarms, click the button Export All Columns in the toolbar, put in the file name and the path you want to save the report, select a type of file ,such as .xls; 6. Back to Query-> View Notifications; click the Quick search button on the toolbar, and select conditions wanted, then Click OK. It will show the query result of the Notifications according to the query conditions. Or user can choose New to create and save a new notifications views/filters, then pick on it and click the button Execute on the toolbar. It will show the query result of the notifications according to the filters; 7. In the window of View Notifications which show the query result of the notifications, click the button Export All Columns in the toolbar, put in the file name and the path
you want to save the report, select a type of file ,such as xls;
Anticipative Result
1. 2. 3.
By step 2, step 4, step 6, the views/filters can be recalled By step 3, the files of report contain the exhaustive list of By step 5, the files of report contain the exhaustive list of
and executed successfully. current alarm information. history alarm information. By step 7, the files of report contain the exhaustive list of notifications information. Test Description Test Result
4.3 Alarm Handle

Test Item Sub-Item Test Target Test Networking Precondition 1. 2. 3. 4. 1. 2. RAN and core network work normally The link between OMC and NE is normal OMC works normally Log on OMC Enter Fault Management Interface Select an unacknowledged alarm in [Alarm Monitor],right click this alarm, select [Acknowledge] 3. Double click this alarm record ,check the acknowledge status in the pop up [Details] window 4. Select an acknowledged alarm in [Alarm Monitor],right click this alarm, select [UnAcknowledge] 5. Double click this alarm record ,check the acknowledge status in the pop up [Details] window The acknowledge status of the specified alarm change from unacknowledged to acknowledged and vise versa. Fault Management Alarm confirm To verify Alarm operation function
Test Steps
Page 24 of 71
Alarm clearance
Test Item Sub-Item Test Target Test Networking Precondition 1. 2. The communication between LMT and OMC is normal. The communication between OMC server and client is Fault Management Alarm clearance To verify if the function of alarm clearance management is supplied.
normal. Test Steps 3. 1. There are current alarms. Create an alarm in a NE. OMC will receive the alarm and displays the alarm in the alarm window. Alarm is consistent 2. 3. 4. 5. Now reset the fault in NE. now the alarm recorded in the alarm window should automatically cleared. Now the alarm can be query in the history alarms. In the [Fault Management] window, open [Query] -> Choose any alarm, click the option Clear of right
[Realtime Alarm Monitor] interface. button menu, system shoot the confirm frame which asks Are you sure to clear the selected alarms?, and click OK. 6. 7. Observe the [Realtime Current Alarm] interface, check if Observe the history alarm inspect interface [Realtime the alarm is cleared, be deleted from the current alarms list. History Alarms], check if the alarm is added to the register, and have been acknowledged. 8. Check if the cleared alarms [Restore Type] is Cleared by User, [(Un)acknowledgment Information] is Acknowledged by OMC, [(Un)acknowledged Operator] is OMC, 9. Open [Setting] -> [Management Rule Setting], in the [Management Rule Setting] window, choose "Alarm Clearing Rule" for [Rule Type], Click <New> from the toolbar. The [Alarm Clearing Rule] dialog box will pop up. 10. Input Rule Name, Description and set the selection condition for alarms wanted to be automatic cleared, and click OK.
11. Handing NE, create such alarms according to the Alarm Clearing Rule. 12. Observe this alarm, when its appeared, it will be in [Realtime Current Alarm] for a moment, and then displayed in [Realtime History Alarms] interface and have been Anticipative Result acknowledged. 1. In step 3, the alarm is cleared, be deleted from the list, and it will appear in the [Realtime History Alarm] interface, 2. by In step 5, the cleared alarms [Restore Type] is Cleared User, [(Un)acknowledgment Information] is
Acknowledged by OMC, [(Un)acknowledged Operator] is OMC. 3. In step 9, when the alarm appears, it will be cleared immediately, and then displayed in [Realtime History Alarms] interface and have been acknowledged. Test Description Test Result
Alarm export by the alarm window to client PC in the format of excel 2007/csv/html
Test Item Sub-Item Test Target Test Networking Precondition 1. 2. 3. Test Steps 4. 1. 2. 3. The communication between LMT and OMC is normal. The communication between OMC server and client is There is at least one current alarm. There are history alarms on OSS. Open OSS client and login. Open View Fault Management; Choose Query-> View Current Alarms; click the Fault Management Alarm export To verify the function of Current and history alarm list export is supplied
normal.
Quick search button on the toolbar, and select conditions wanted, then Click OK. It will show the query result of the current alarms according to the query conditions. 4. In the window of View Current Alarms which show the query result of the current alarms, click the button Export
All Columns in the toolbar. It will show the window of Save, put in the file name and path you want to save, select the Files of Type of file, such as csv, xls,htm and xml; then click Save to export. 5. Back to Query-> View History Alarms; click the Quick search button on the toolbar, and select conditions wanted, then Click OK. It will show the query result of the history alarms according to the query conditions. 6. In the window of View History Alarms which show the query result of the history alarms, click the button Export All Columns in the toolbar put in the file name and the path you want to save the report, select a type of file ,such as xls; It will show the window of Save, put in the file name and path you want to save, select the Files of Type of file ,such as csv, xls,htm and xml; Then click Save to export. 7. Back to Query-> View Notification; click the Quick search button on the toolbar, and select conditions wanted, then Click OK. It will show the query result of the notification according to the query conditions. 8. In the window of View Notification which show the query result of the notification, click the button Export All Columns in the toolbar put in the file name and the path you want to save the report, select a type of file ,such as xls; It will show the window of Save, put in the file name and path you want to save, select the Files of Type of file ,such as Anticipative Result Test Description Test Result csv, xls,htm and xml; Then click Save to export. 1. Current and history alarm list can be saved in the files type of csv, xls, htm or xml.
Alarm Correlation Rule

Test Item Sub-Item Test Target Test Networking Precondition 4. The communication between LMT and OMC is normal.
Page 27 of 71
Fault Management Alarm Correlation Rules Verify if the Alarm correlation rule is pOMCible
5. 6.
The communication between OMC server and client is There are alarms which meeting the requirements of the
normal. rules emitting after the rules saved. Test Steps 7. 1. There are current alarms. In the [Fault Management] window, click [Setting->
Management Rule Setting] to open the [Management Rule Setting] window. 2. In the [Management Rule Setting] window, choose "Alarm Restraining Rule" for [Rule Type], and then the alarm restraining rule setup window shows. 3. 4. Click <New> from the toolbar. The [Alarm Restraining Input Rule Name, Description, click the button setting Rule] dialog box will pop up. to set the Root alarm ,and click the button New to add the Consequential alarm, select the option Show consequential alarm after root alarm restored ,then click OK to save this rule 5. 6. Create such alarms according to the Alarm Restraining Observe this alarm in the window of Realtime Alarm Rule. Monitor, when Root alarm reports first and then Consequential alarm reports, check if the Consequential alarm cant be displayed, and if the Consequential alarm could be displayed when click the symbol of correlated alarm (+) beside Root alarm. 7. Back to the [Management Rule Setting] window; choose "Alarm Merging Rule" for [Rule Type], and then the alarm merging rule setup window shows. 8. 9. Click <New> from the toolbar. The [Alarm Merging Input Rule Name, Description, set the selection condition Rule] dialog box will pop up. for alarms wanted to be merged. User should set the selection of System Type Location Alarm Code at least, then click OK to save this rule, 10. Create such alarms according to the Alarm Merging Rule. 11. Observe this alarm in the window of Realtime Alarm
Monitor, when the alarm reports first and then the same alarms reports, check if there are only the first alarm can be displayed, and if the subsequent alarm could be displayed when click the symbol of correlated alarm (+) before the first alarm. 12. Back to the [Management Rule Setting] window; choose "Alarm Delaying Rule" for [Rule Type], and then the alarm delaying rule window shows. 13. Click <New> from the toolbar. The [Alarm Delaying Rule] dialog box will pop up. 14. Input Rule Name, Description, Delay Time and set the selection condition for alarms wanted to be delayed, e.g. set delay time as 20s, select system type Managed Equipments, select alarm code 198066003 and select the Once a delayed alarm cleared, insert into history alarm database. 15. Create such alarms according to the Alarm Delaying Rule. 16. Observe this alarm, it should be restored in history alarm but wont be displayed in the [Realtime Current Alarm] list. 17. Back to the [Management Rule Setting] window; create an Alarm Merging Rule and an Alarm Counting Rule with the same selection, so these two rules will affect the same alarms. Select the Rule Type; choose the Alarm Counting Rule, click the button New on the toolbar, input the name , appoint the time and the number of alarms , and then make selection on the conditions of alarms in the Selection tab, click the OK button to create a rule; 18. Observe this alarm in the window of Realtime Alarm Monitor, when the alarm meeting these two rules reports first and then the same alarms reports, check if there are only the first alarm can be displayed, and if the subsequent alarm could be displayed when click the symbol of correlated alarm (+) before the first alarm. If there alarms meeting the counting rule are produced equal or more than the number in appointed time, a new alarm (alarm code is Frequency of warning overload(200270)) will raise up. 19. Back to the [Management Rule Setting] window; choose
"Alarm Compress Rule" for [Rule Type], and then the alarm compress rule window shows. 20. Click <New> from the toolbar. The [Alarm Compress Rule] dialog box will pop up. 21. Input Rule Name, Description, compress Time window and set the selection condition for alarms wanted to be compressed; 22. Observe alarms in the window of Realtime Alarm Monitor. Create such alarms accord to the Alarm Compress Rule, if these alarms Alarm Code, Location, Severity, Other Information are all the same and happen in a period equal the Time Window , then these alarms will be compressed into a alarm. In the details of this alarm, Anticipative Result Counter shows how many alarms compressed. 9. 1. In step 6. Event Suppression - if alarm A as Root alarm and alarm B as Consequential alarm then suppress B. If the option Show consequential alarm after root alarm restored was selected when setting the rule, then when all the Root alarm restored, the Consequential alarm will be reported all in the [Realtime Current Alarm] list. 10. In step 11. Event Compression- If many times emit the same alarms , then forward the alarms only one time 11. In step 16, when the alarm has been created for more then the delay time and not be restored, whether it is displayed in the [Realtime Current Alarm] list. 12. In step 17, when the alarm was restored within the delay time, it wont be displayed in the [Realtime Current Alarm] list, and can be finding in the history alarm 13. In step 19, new alarm is created for suppressing alarm groups. 14. In step 23, only one alarm will be showed if the same alarm occurs many times during a period. Test Description Test Result
Page 30 of 71
4.5 Alarm Filter Rule

Test Item Sub-Item Test Target Test Networking Precondition 1. RAN and core network work normally 2. The link between OMC and NE is normal 3. OMC works normally 4. Log on OMC 5. Enter Fault Management Interface 1. select [Fault->setting->rule setting] 2. Click [New-> Alarm Acknowledgement Rule] in Rule Type list 3. Create an alarm global filtering rule and set alarm type or alarm code to be filtered; 4. Make that the status of the rule is enable; Anticipative Result Test Description Test Result 5. Trigger the alarm to be filtered. 1. In [Real time Alarms] window, the alarm to be filtered will not be shown. Fault Management Alarm Filter Rule Verify if the Alarm Filter rule is possible
Test Steps
4.6 Current Alarm Forwarding

Test Item Sub-Item Test Target Test Networking Precondition 1. 2. 3. 4. 5.
1. 2. 3.
Fault Management Alarm Forwarding To verify Alarm forwarding function
Test Steps
RAN and core network work normally The link between OMC and NE is normal OMC works normally Log on OMC Enter Fault Management Interface select [Fault->setting->rule setting] Click [New-> Alarm Forwarding Rule] in Rule Type list Create an alarm forwarding rule and set alarm Action or Condition; Its possible to define different NE alarm sent to different people, and the phone list/ alarm list and be add/modify/delete. The alarm content which to be sent
4.
Page 31 of 71
can be configurable. 5. Make Email or Phone of the rule is enable; 6. Trigger the alarm to be forwarding. 7. SMS Notification forwarding via SMPP connectivity to a SMS gateway Anticipative Result Test Description Test Result 8. Email Notification forwarding via email server. Alarm forwarding rule can be setted successfully.
4.7 Alarm Synchronization

Test Item Sub-Item Test Target Test Networking Precondition Fault Management Alarm synchronization To verify Alarm synchronization function As shown in Fig.1 RAN and core network work normally 2. The link between OMC and NE is normal 3. OMC works normally 4. Log on OMC 5. Enter Fault Management Interface Manual Synchronization by users 1. Click [Alarm-> Alarm Synchronization]and then the [Alarm Synchronization Setup] dialog box pops up 2. Input system type and alarms location 3. Click[OK] to synchronize the alarm data at the specified location and alarms will be displayed in Real time Current Alarms list
1.
Test Steps
Automatic Synchronization by OMC 1. Break the link between OMC and BSC 2. Generate some BSC alarms 3. Recover the link between OMC and BSC 4. After BSC link status on OMC is normal,query the current alarm list of BSC,the newly generated alarm should be seen in the list Alarms can be synchronized/upload from NE successfully.
Page 32 of 71
4.8 Alarm Knowledge Database

Test Item Sub-Item Test Target Test Networking Precondition RAN and core network work normally The link between OMC and NE is normal 3. OMC works normally 4. Log on OMC 1. Open View Fault Management; open the Query Realtime Alarm Monitor window; Choose any alarm, double click on it, or right click on it then choose the menu Details. Click Maintenance Suggestion tab. User can input the Customized suggestions, and click the button Save to save it. 2. Choose Fault->setting->Handling Suggestion Setting 1. Alarms showing in the Realtime Alarm Monitor contain abundant information: the alarm location, alarm code, probable cause, Alarm object ID, board type, alarm happen time, acknowledgement status, Maintenance Suggestion(include Default suggestions and Customized suggestions) and so on. Choose any alarm, double click on it, or right click on it then choose the menu Details. Click Maintenance Suggestion tab. User can input the Customized suggestions, and click the button Save to save it. 2. Maintenance Suggestion Setting is the alarm dictionary. Through the column default suggestions, users can get the way to fix the problem step by step according to the alarm reason; also it gives out the probable cause for every kind of alarm clearly
1. 2.
Fault Management Alarm Knowledge Database To verify Alarm Knowledge Database function
Test Steps
Anticipative Result
4.9 Visual Alarm

Test Item Sub-Item Test Target Test Networking Precondition 1. RAN and core network work normally 2. The link between OMC and NE is normal
Page 33 of 71
Fault Management Alarm Graphic Display To verify Alarm graphic display function
Test Steps
3. 4. 1. 2.
OMC works normally Log on OMC Enter Fault Management Interface Select a NE at the topo tree, right click the NE icon, select[Fault Management -> Active Alarms] 3. Check the color of NE icon and the current alarm list The color of the NE icon is consistent with the highest level of all the current alarms
4.10 Coloured and Audible Alarm

Test Item Sub-Item Test Target Test Networking Precondition Fault Management Coloured and Audible Alarm To verify Customize Alarm monitoring interface function As shown in Fig.1 1. 2. 3. 4. 5. 1. 2. 3. RAN and core network work normally The link between OMC and NE is normal OMC works normally Log on OMC Enter Fault Management Interface In the [Fault Management] window, Monitor the alarm browser Click[Setting->Alarm sound and color setting],and then change the color of critical alarm 4. Check the critical alarm color in realtime alarm list 1. Alrm browser will display the alarm with the severity color code and sounding when an alarm recieved. 2. Alarm color will change after user modifies alarm color in [Preferences] window.
Test Steps
Anticipative Result
4.11 Alarm Box Management

Test Item Sub-Item Test Target Fault Management Alarm Box To verify Alarm Box function
Page 34 of 71
Test Networking Precondition RAN and core network work normally 2. The link between OMC and NE is normal 3. OMC works normally 4. Log on OMC 5. Enter Fault Management Interface 1. At Ems client, click [Fault->Fault Monitoring], and [Fault management] window appears. and then click [Fault>Setting-> Alarm Box Setting] to open the [Alarm Box Setting] tab page 2. Click <new> , set parameters such as IP, Initial state etc. and click <OK> Alarms can be monitored by Alarm Box.
1.
Test Steps
4.12 External Alarm Access

Objectives Test Networking Precondition The purpose of this test case is to verify the functionality of External Alarm Access 1. OSS works normally 2. The link between OSS and NE is normal 3. OMCB runs properly; 1. At OSS clientselect the Fault -> Setting -> Alarm Code Description Setting menu to open the Alarm Code Description Setting window. 2. Select an SDRII or SDR type User-defined dry contact alarm code number, double click it, and fill the blank of Modified Name and select the severity of Modified Severity. Then a new dry contract alarm has been defined in OSS. 3. Define the dry contact alarm description in OMCB: Login to the OMCB Client, Click view -> Fault Management, then select the Setting -> Alarm Code Description Setting menu to define an new dry contact alarm, make sure that the Alarm code , Custom Description, System Type of this alarm must be consistent with the information of the dry contact alarm you have just defined in the OSS. 4. At OSS client, open Topology Management view, select NE Agent, right-click it, select [NE Management->Start
Page 35 of 71
Test Steps
5.
6.
7.
8. 9. Anticipative Result 1. 2. Message Flow
NE]. After the NE has started, right-click it, select [NE Management->configuration Management] to open configuration management. Right Click the NE Management Element, Select Apply Mutex Right item to get the NEs mutex right. Select the main configset, double click the Equipment object-> Dry contact device object to open the Dry contact device object window. Click the Create MO Object icon in the menu bar, create an Self-defined dry contact in the prompt window. Choose the self-defined dry contact alarm if the field of Is selfdefined dry contact or not is Y. Right Click the SDRII Management Element, click the Synchonize Modified Tables item. When the SDRII trigger an dry contact alarm, it can be displayed in the Fault->Alarm Monitoring window. Consistency check is run on the input parameter values while Using LMT to modify parameters; The modification will be effective on OSS.
4.13 Diagnosis and Testing

Test Item Sub-Item Test Target Test Networking Precondition 1. 2. 3. 4. 1. RAN and core network work normally The link between OMC and NE is normal OMC works normally Log on OMC Right click [BSC ID] in [Physical View] window of [Topology Management], and select [NE Management>Test Management] to open the [test Management] window 2. Click [Test Management->Add Test Task] and Device Test dialog appears In the dialog, select [Information] [Period][Test Item]and click <OK >. Verify each kind of test type one by one Ensure each test type can be performed and test result can be displayed in the test result window. Fault Management Diagnosis Test To verify Diagnosis Test function
Test Steps
Anticipative Result Test Description
Page 36 of 71
Test Result
4.14 Alarm Severity Regrading

Test Item Sub-Item Test Target Test Networking Precondition 1. 2. 3. 4. 5. 6. 1. All network elements follow global precondition. OSS works normally. The communication between NE and OSS is normal; The communication between LMT and OSS is normal. The communication between OSS server and client is There are current alarms. In the [Fault Management] window, click [Setting-> Fault Management Alarm Severity Regrading Verify if the function of alarm reclassification is possible
normal. Test Steps
Severity Regarding Setting] to open the [Severity Regarding Setting] window. 2. Choose any alarm, click the list of [New severity], select new severity, and corresponding alarms modification status will have a mark of sketch, and then click the [save] in toolbar. This change is effective for later alarms. 3. Check if the status of the new coming current alarm is reclassified into new level which alarm code is the same as user has defined in step 2. Observe current alarm code list; check if all of alarms which correspond this alarm code have been changed to new severity. 4. Repeat the step1-step4, modify and delete severity regarding. 1. Alarm reclassification have been changed successfully, new severity can be display right in the window. All of alarms which occurred after setting the severity correspond this alarm code have been changed to new severity. Test Description Test Result
Anticipative Result
Page 37 of 71
4.17ZXO-07-03-014 VIP Site Alarm Monitoring (GERAN&UTRAN)

Objectives Test Networking Precondition The purpose of this test case is to verify the functionality of VIP Site Alarm Statistics 1. OSS works normally 2. The link between OSS and NE is normal 3. Log on OSS 1. At OSS clientselect the Fault -> VIP Site Alarm Statistic menu to open the VIP Site Alarm Statistics window which has been divided into 6 parts to display the statistics in 6 periods of time. 2. Verify that all the VIP sites (including SDR and SDRII) have been listed in the window, check that every site alarm statistic of each level in each period is consistent with the current and history alarm record. 3. At OSS clientSelect the Configuration->Wireless Config Application ->VIP NodeB Priority Query and Set, then select the aim AMO, in the prompt window, select a Normal NE record, right click it and select VIP item, then select the execute button, if the Result is Success, then the site has been changed into a VIP site, check that this new VIP site has been listed in the VIP Site Alarm Statistics window. If a VIP site has been set into a normal site, it will not been displayed in the VIP Site Alarm Statistics window. 4. Trigger some alarm in a VIP site, then check the alarm statistics of this site has been refreshed. 1. All VIP sites can be displayed in this window 2. All the alarm statistics data is correct according to different periods of time.
Test Steps
Anticipative Result
Page 38 of 71
5. Performance Management
5.1 Measurement Task Management
Test Item Sub-Item Test Target Test Networking Precondition 1. 2. 3. 4. 5. 1. RAN and core network work normally The link between OMC and NE is normal OMC works normally Log on OMC Enter Performance Management Interface Click [Performance Management-> Measurement Task Performance Management Measurement Task Management To verify Measurement Task Management function
Test Steps
Management] and then the [measurement task management] window opens

2.
Click <Create task> button on the toolbar and then Set basic task information, such as Task name NE
[Create task : measurement task] dialog box pops up

3.
typeObject typeMeasure type and collection granularity, and so on

4.
Set collection object in the [Task measurement object] Click <OK> to create a measurement task Click [Performance Management -> Performance Data
tab page.
5. 6.
Query] to Query pm data, in this page users can see all counters, and query the value of counters. 7. 8. 1.
2.
Double click the created measurenet tast, then click Delete the new created measurement task after testing. Measurement tasks can be created successfully During the creation of measurement task, Measure type At step 6, the operator can see all counters, and query the
<modify> Anticipative Result
can be set
3.
value of counters. Test Description Test Result
Page 39 of 71
5.2 KPI Management

Test Item Sub-Item Test Target Test Networking Precondition 1. 2. 3. 4. 5. 1. RAN and core network work normally The link between OMC and NE is normal OMC works normally Log on OMC Enter Performance Management Interface Click [Performance -> Counter and Index Management] and then the [Counter and Index management] window opens KPIs are displayed in the left of Index list Right click on the index item to view its detailed information, such as formula Click[New Index]on the toolbar and then the [New Index] window pops up After choosing NE Type and MO Type, input index name and choose[Edit]button to edit a new index formula Click [OK] and the OMC will create a performance index that user customizes Standard KPI can be displayed normally New KPI can be customized successfully Performance Management KPI and formula To verify KPI and formula function
Test Steps
2. 3. 4. 5. 6. Anticipative Result Test Description Test Result 1. 2.
5.3 QoS Monitoring

Test Item Sub-Item Test Target Test Networking Precondition 1. 2. 3. 4. 5. RAN and core network work normally The link between OMC and NE is normal OMC works normally Log on OMC Enter Performance Management Interface Performance Management QoS Task Management To verify QoS Task Management function
Page 40 of 71
Test Steps
1. 2.
3.
4.
5. 6. 7. Anticipative Result
Click [Performance -> Threshold Task Management] and then the [Threshold task management] window opens Click <Create threshold task> button on the toolbar and then [Create threshold task : QoS task] dialog box pops up Set basic task information, such as NE Type and MO Type. Select object in the [Threshold Task] tab page.Click Add index button , Select index and set alarm threshold in the [Modify threshold] tab page. Click <OK> to create a measurement task Delete threshold task
Qos tasks can be created successfully.When the QOS exceeds specified threshold, new alarm will be generated. And when QOS below the threshold, alarm will clear. When modify the task, new alarms will generate with the new threshold. When the threshold measurement task deeted no any alarm will generate even the QOS above the threshold
5.5 Performance Data Management

Test Item Sub-Item Test Target Test Networking Precondition Performance Management The integrity of performance data To verify Data availability and integrity function As shown in Fig.1 1. 2. 3. 4.
5.
Test Steps
1. 2. 3. 4.
RAN and core network work normally The link between OMC and NE is normal OMC works normally Log on OMC Enter Performance Management Interface Click [Performance -> Integrality Report] and then the [Integrality Report] window pops up Select the NE type, MO type, location selection,time selection Click[OK] to check the integrality The daily collection statistics is displayed on the left and the right part is blank. Click an item on the left to display the query results of all time segments in this day on the right
Page 41 of 71
5. If performance data was delayed by certain reason such as the abnormity of blade server ,OMC will display in different color in list The correct integrality query results are displayed successfully
5.5 Performance Report

Test Item Sub-Item Test Target Test Networking Precondition Performance Management Data collection and display To verify Data collection and display function As shown in Fig.1 RAN and core network work normally The link between OMC and NE is normal OMC works normally Blade server for performance management works normally 5. Log on OMC 6. Enter Performance Management Interface 1. Log on OSS with a PM user(user only has Performance Management access privileges) 2. 3. 4. 5. 6. Click [Performance Management-> Performance Data In [Query Index] tab page, select correct Ne Type, In [Query Time] tab page, select query begin/end time In [Query Object] tab page, select Ne location and Click [OK] button on the condition dialog after setting Query] and then the [Query] window pops up Object Type, KPI Index/counters and select query granularity. measure object those conditions described above, then the dialog will be closed and a progress dialog will be prompted 7. 8. 9. Results are shown in list In [Query Result] window, you can click [table or chart] If selected [chart], you can click [chart setting] on the
Page 42 of 71
1. 2. 3. 4.
Test Steps
on the toolbar in bottom window toolbar, and then [chart setting] dialog box pops up
10. In [chart setting] window, you can set measure object and index/counter, to modify the graphs 11. Click [Performance Management-> Query Template management] and then the [Query Template management] window pops up 12. Click <Create Template> button on the toolbar and then [Create Template] dialog box pops up
13.
Set basic task information, such as template name NE
type Object type and select index/counter for the standard set of reports 14. log on OSS with another user has Performance Management access privileges
15.
Click [Performance Management-> Performance Data
Query-by template] and then the [Query by user template] window pops up 16. In [Query Template] tab page, select correct Ne Type and template created by other user, set query time and query object 17. New user cannot modify the template created by the PM User. If new user needs to change the setting he has to save the template in a new name. Anticipative Result Test Description Test Result 18. Click [OK], Results are shown in list Selected counters can be reported instantly Queried result can be displayed in line/bar/pie charts.
5.6 Performance Data Real-time Query

Test Item Sub-Item Test Target Test Networking Precondition Performance Management Performance Data Real-time Query To verify Performance Data Real-time Query function As shown in Fig.1 1. 2. 3. 4. RAN and core network work normally The link between OMC and NE is normal OMC works normally Blade server for performance management works normally 5. Log on OMC
Page 43 of 71
6. Enter Performance Management Interface Test Steps Click [Performance ->] and then the [Realtime Date Query] window opens 2. Create Realtime Date Query, such as NE Type and MO Type, Selected Counter, Selected Location. 3. After the task is created successfully, insure that the status of the task is active 4. Wait for a period of time e.g. 30 minutes if collection granularity is 15 minutes 5. Click [Performance Management-> Performance Data Query-by Task] and then the [Query by task condition] window opens 6. Select correct NE location and then select the task you want to query data, e.g. the task in step2 7. Select correct begin time and end time, then in [Measure Object/Counter] tab page of the query condition dialog, choose objects and counters 8. Click [OK] button on the condition dialog after setting those conditions described above, then the dialog will be closed and a progress dialog will be prompted 9. Performance data results are shown in Query Result list and chick [chart] to display 10. The query results can be saved automatically. Performance data can be Statistic Analysis successfully
1.
Performance Data export

Test Item Sub-Item Test Target Test Networking Precondition 1. 2. 3. 4. RAN and core network work normally The link between OMC and NE is normal OMC works normally Blade server for performance management works normally 5. Log on OMC 1. Enter Performance Management Interface
Page 44 of 71
Performance Management Performance Data export To verify Export Performance Data from report function
Test Steps
1.
2.
Click [Performance Management-> Performance Data Query] and then the [Query] window pops up In [Query Index] tab page, select correct Ne Type, Object Type, then there lists all Indexes/counters of the specified Ne Type and objected Type. However, you can choose 300 indexes/counters at most once.
3.
In [Query Time] tab page, select query begin/end time and query granularity. In [Query Object] tab page, select Ne location and measure object Click [OK] button on the condition dialog after setting those conditions described above, then the dialog will be closed and a progress dialog will be prompted
4. 5.
6.
7.
Results are shown in list Click [Export] on the toolbar and then [export setting] dialog box pops up Select specified columns, choose CSV file type click[OK].and the[Save] dialog box pops up Specify the storage location, filename, click <Save> to export the KPI or raw PM data. Export performance data from report function is supplied. Save in the client PC in file format excel 2007, html,csv,text
8.
9.
10.
Anticipative Result
1. 2.
User defined indicators management

Test Item Sub-Item Test Target Test Networking Precondition 1. 2. 3. 4. RAN and core network work normally The link between OMC and NE is normal OMC works normally Blade server for performance management works normally
Page 45 of 71
Performance Management
User defined Indicators management
To verify User defined Indicators can be created/modified/ deleted function.
Test Steps
5. Log on OMC 6. Enter Performance Management Interface 1. Click [Performance Management-> Index Management] and then the [Index management] window opens
2.
Indexes are displayed in the Index list Right click on the index item to view its detailed information, such as formula Click [Create Index]on the toolbar and then the [Create Index] window pops up Input index name, select value type ,index type and threshold information in the [Basic information] tab page Click [Formula information] tab page, choose correct NE Type and Object Type, you can select raw counters to edit a new index formula. Or click[Import existing index formula] , the [Import existing index formula] windows pops up, displays the index include standard indicators and user defined indicators, you can select the index and click [Import] to edit a new index formula
3.
4.
5.
6.
7. 8. Anticipative Result 1.
Click [OK] and the OSS will create a performance index that user customizes Right click on the index item you can select modify or delete the index that user customized. New index can be customized successfully, user defined indicators could be created from raw counters standard indicators, user defined indicators or a mix of these 3 types.
2. Test Description Test Result
User can create, modify or delete the index that user customized.
Page 46 of 71
6. Software Management
6.1 Software Management
Test Item Sub-Item Test Target Test Networking Precondition Software Management Software updates process and software management To verify Software updates process and software management function As shown in Fig.1 1. 2. 3. 4. 5. 1. BSC and core network work normally The link between OMC and NE is normal OMC works normally Log on OMC The NE Management of NE Agent is started At OMC client, Right click [NE Agent] in NE Tree window of [Topology Management], and select [NE Management->Software Management] to open the Software Management window. For BSC 2. From the left view in the Software management window, right click [BSC SoftWarePack Management],select [Creat Version Pack],and select [Choose File Folder],and then click [OK], the managed NE software version management tab page appears in left of the window. 3. Right the version,and select [Download] to download the version into RNC and the result dialog pops up. 4. Check the version in the Operation Result of the [Pack Log]. 5. Right the version,and select [Active] to download the version into BSC and the result dialog pops up. SW/HW create for BTS 1. At EMS client, select a NE of the OMCB,and open Topology Management view, then select NE Agent 2. Right click [NE Agent]; select [NE Management->Base Station Software Management] In Topo tree to open the Base Station Software Management window. 3. From the left view in the Base Station Software management window, Expand [SDR Software Version Management] tree node to [SDR Software Version Package Management] for SW create or [SDR BootEpld Version Package Management] for FW create. 4. For SW create: Right click [SDR Software Version Package Management], on the Popup menu, Select the [Create] -> [Base Station Version Package].
Page 47 of 71
Test Steps
5.
Anticipative Result
For FW create: Right click [SDR BootEpld Version Package Management], on the Popup menu, Select the [Create] -> [BootEpld Version Package]. 6. The Version Package file path window pops up, Select the correct Version Package file. 7. Click <OK > and when the operation is finished, the result will be shown. SW/HW download for BTS 1. Double-click the version package file that had been created. In the version package file property page. Select toolbar button [Package Download] 2. Popup the Package Download window, from the view, select the NEs that link state is normally connected, Right click the selected NEs, Popup menu, and right click the blank of the left window, select [Firmware Version Package Download]. 3. When the operation is finished, the result will be shown. SW/HW activate for BTS 1. Double-click the version package file that had been created and downloaded to the NEs. In the version package file property page. Select toolbar button [Direct Package Activation] 2. Popup the Package Activation window, from the left view, select the NEs that link state is normally connected, Right click the selected NEs, Popup menu Right click the blank of the left window, and select [Firmware Version Package Activation]. 3. When the operation is finished, the result will be shown. 1. BSC and BTS version files put into Lib successfully. 2. Download processing successfully and version is correctly as predefine one. 3. For BSC, after Version Switching, the board will restart and be updated to new version. 4. For BTS, after [Firmware Version Package Activation], the BTS will restart and be updated to new version. 5. Confirm relevant alarm can prompt out during package activation and disappear on finished 6. Confirm the activation time can finished in a reasonable time.
Page 48 of 71
6.2 Nodes SW Version Check

Test Item Sub-Item Test Target Test Networking Precondition 1. 2. 3. 4. 1. EMS works normally The link between EMS and NE is normal Log on EMS The NE Management of NE Agent is started At OMC client, Right click [NE Agent] in [Physical View] window of [Topology Management], and select [NE ManagementSoftware Management] to open the Software Management window. From the left view in the Software management window, click [BSC managed NEXX->BSC software management NEXX], open [BSC software management NEXX] window. Click [All version consistency check] button on the toolbar and software consistency comparison window pops up. Select <Version Check Result> tab page then the comparison result (Version Accord or Version Disaccord) is shown on the top list. Software version consistency check can be done successfully. via GUI Software version consistency check result can be shown via GUI. Software Management Nodes SW Version Check The purpose of this test case is to verify the functionality of software version consistency check via GUI.
Test Steps
2.
3.
4.
Anticipative Result
1. 2.
6.3 Software Installation and Upgrade

Test Item Sub-Item Test Target Test Networking
Software Management Software Installation and Upgrade The purpose of this test case is to verify the functionality of remote NE SW upgrade function.
Precondition
1. 2. 3. 4.
EMS works normally The link between EMS and NE is normal Log on EMS The NE Management of NE Agent is started
Test Steps
For BSC At EMS client, Right click [NE Agent] in [NE Tree] window of [Topology Management], and select [NE Management>Software Management] to open the Software Management window. From the left view in the Software management window, right BSC SoftWare Pack Management->Create Version Pack,and [Create Version Pack] dialog pops up, select one pack fileclick OK to start create version pack; Select the created version pack ,right-click Download , select online BSC Management, click OK , to download version to BSC; Select the created version pack ,right-click Active , select version file in dialog Choose Version Pack , select online BSC Management, click OK , to active version ; Double-click [BSC managed NEXX ->BSC UE software version management [XX]] ,and the managed NE software version management tab page appears in right of the window. In [Rack view] tab page, rack will display, select ROMB, right click<Check board version information >, and [Board version] dialog pops up. In the dialog, Select <Running version> to check the running version, Then select <Backup version > , all backup version will display, And then select the special version file, click <Activate ver> , and [OMP version switch] dialog pops up , select Whether reset at once as YES, select left or right board, click OK , to change the OMP version;. After OMP reset successful, then At EMS client, Right click [NE Agent] in [NE Tree] window of [Topology Management], and select [NE Management->Configuration Management] to open the Configuration Management window. Right click BSC Management ElementXX->Apply Mutex Right; Double click [UTRAN SubNetworkXX->BSC Managed Element$XX ->BSC Config SetXXX->BSC Ground Resource ManagementXX]; On the right window, click [BSC Reset] icon ,input verify code, then reset the BSC; Click <OK > and when the operation is finished, the result will be shown. SW create for SDR
Page 50 of 71
Anticipative Result
At EMS client, open Topology Management view, select NE Agent Right click [NE Agent] and select [NE Management->Base Station Software Management] In Topo tree to open the Software Management window. From the left view in the Software management window, Expand [Base Station Software Version Management] -> [SDR Software Version Package Management] for SW create. Right click [SDR Base Station Version Package Management], on the Popup menu, Select the [Create] -> [Base Station Version Package]. The Version Package file path window pops up, Select the correct Version Package file. Click <OK > and when the operation is finished, the result will be shown. SW download for SDR Double-click the version package file that had been created. In the version package file property page. Select toolbar button [Package Download] Popup the Package Download window, From the left view, select the NEs that link state is normally connected, Right click the selected NEs, Popup menu, Select the menu [Package Download]. When the operation is finished, the result will be shown. SW activate for SDR Double-click the version package file that had been created and downloaded to the NEs. In the version package file property page. Select toolbar button [Package Activation] Popup The Package Activation window, From the left view, select the NEs that link state is normally connected, Right click the selected NEs, Popup menu Select the menu [Package Activation]. When the operation is finished, the result will be shown. BSC and BTS version files put into Lib successfully. Download processing successfully and version is correct as predefine one. For BSC, after Version Switching, the board will restart and be updated to new version. For Node B, after [Package Activation], the Node B will restart and be updated to new version. Confirm relevant alarm can prompt out during package activation and disappear on finished

6.4 Software Inventory

Test Item Sub-Item Test Target Test Networking Precondition 1. 2. 3. 4. 1. OMC works normally The link between OMC and NE is normal Log on OMC The NE Management of NE Agent is started. At OMC client, Right click [NE Agent] in [Physical View] window of [Topology Management], and select [ViewConfiguration Report] to open the Configuration Report window. In Configuration Report window, right click [SOFTWARE] and select [File Report] to open Get Report window. Select BSC Managed Element, choose XML file type and click [OK]. Report files are list in the sheet and exported to file. Double click the file record and open the report file. Repeat step 1~2; Select [SDRManagedElement], then choose the SDR site which is belong to BSC, then choose XML file type and click [OK]. Report files are list in the sheet and exported to file. Double click the file record and open the report file. Software inventory can be displayed in GUI. Software inventory can be exported to file. Software Management Software Inventory The purpose of this test case is to verify the functionality of software inventory is available and can be exported.
Test Steps
2.
3. 4. 5. 6. 7.
8. 9. 1. 2.
Page 52 of 71
7. System Management
7.1 Data Backup and Restore
Test Item Sub-Item Test Target Test Networking Precondition Test Steps OMC system ready.
1.
System management Test Data Backup and Restore The purpose of this test case is to verify the functionality of Database Management
2.
3. 4.
5.
Anticipative Result
1.
2.
Click [Maintenance->Task Management], In the system management tree on the left view and choose any Task Management Click [Modify] and resetting . Click [Save] Click [restore] and choose the path of data, Click [Sace]. In the [View Database resources] dialog, user can observe DB resource status. In [Table collection operations] dialog, user can manager database table cleaning, database maintenance task, database timed maintenance task etc. Database can back and restore successfully.
7.2 Automatic data export

Alarm auto export (current and history alarms) to a EMS server path (format CSV) - should be configurable PM data auto export (selective PM tasks) to a EMS server path (format CSV) - should be configurable System management Test Item
Sub-Item Test Target Test Networking Precondition
Test Management The purpose of this test case is to verify the functionality of data export automaticly OMC system ready.
Page 53 of 71
ZTE GSM System Test Handbook RAN OMC Test Steps 1.
2.
3.
4.
Click [Maintenance-> Test Management] , In the test management tree on the left view and choose [PM Data Backup and Deletion Task] , on the right view and choose [backup Description] menu items. PM data auto export (selective PM tasks) to a EMS server path (format CSV) Click [Maintenance-> Test Management] , In the test management tree on the left view and choose [Alarm Data Backup and Deletion Task] , on the right view and choose [backup Description] menu items,choose history Alarm Table or Notification Table Alarm auto export (current and history alarms) to a EMS server path (format CSV)
Anticipative Result
Alarm auto export (current and history alarms) to a EMS server path (format CSV) - should be configurable PM data auto export (selective PM tasks) to a EMS server path (format CSV) - should be configurable
Modify the maximum keep days of database ( For PM and FM)

Test Item Sub-Item Test Target Test Networking Precondition Test Steps
System management System backup and deletion data The purpose of this test case is to verify the functionality of System Management OMC system ready.
1.
2. 3.
Click [Maintenance->System backup and restore] , In the system management tree on the left view and choose [Backup and Deletion Alarm Data] , modify [Delete Filter Type] menu items. Set the maximum keep days of databasefor FM. In the system management tree on the left view and choose [Backup and Deletion PM Data] , modify
Page 54 of 71
4.
[Delete Filter Type] menu items. Set the maximum keep days of databasefor PM.
Anticipative Result
Modify the maximum keep days of database ( for PM and FM)will be triggered.
7.4 Evaluvate the database capacity of PM and FM

System management System Monitoring The purpose of this test case is to verify the functionality of Server System Management OMC system ready. Click [Maintenance->System Monitor] ,In the system management tree on the left view and choose [oracle:sid@IP] , Click [View Database Resources Oracle] menu items in the right. 2. You can evaluvate the database capacity of PM and FM according to the RFP In FM databases FM data can keep for 30 days.
1.
7.5Recollection of PM and FM data from a disconnected NE after reconnect.

Test Item Sub-Item Test Target Test Networking Precondition 1. 2. RAN and core network work normally The link between OMC and NE is normal
Page 55 of 71
Fault Management and Performance Management Alarm synchronization and To verify Alarm synchronization function and recollect data of PM data
Test Steps
3. OMC works normally 4. Log on OMC 5. Enter Fault Management Interface Manual Synchronization by users 1. Click [Alarm-> Alarm Synchronization]and then the [Alarm Synchronization Setup] dialog box pops up 2. Input system type and alarms location 3. Click[OK] to synchronize the alarm data at the specified location and alarms will be displayed in Real time Current Alarms list Automatic Synchronization by OMC 1. Break the link between OMC and BSC 2. Generate some BSC alarms 3. Recover the link between OMC and BSC 4. After BSC link status on OMC is normal,query the current alarm list of BSC,the newly generated alarm should be seen in the list 5. Click [Performance->Integrity Report] , Create New Data Integrity Query will open ,right clink to choose recollect data.
Recollection of PM and FM data from a disconnected NE after reconnect.
7.6 System real time monitoring (CPu memory DB hard disk usage)
Test Item Sub-Item Test Target Test Networking Precondition
System management System real time Monitoring The purpose of this test case is to verify the functionality of Server System Management OMC system ready.
Page 56 of 71
ZTE GSM System Test Handbook RAN OMC Test Steps
Anticipative Result
Click [Maintenance->System Monitor] , In the system management tree on the left view and choose [AppServer] , Click [View Application Server Performance] menu items. 2. View CPU, RAM and HD monitoring usage. 3. In the system management tree on the left view and choose [oracle:sid@IP] , Click [View Database Resources Oracle] menu items in the right. 4. You can see DB usage View CPu memory DB hard disk usage in real time is successful.
1.
7.7 System Self-Monitoring

System management System Self-Monitoring The purpose of this test case is to verify the functionality of Server System Management OMC system ready. 1. Click [Maintenance->System Monitor] , In the system management tree on the left view and choose [AppServer] , Click [Configure Performance Monitor] menu items. Set CPU, RAM and HD monitoring threshold, and then click <save>.
2.
Anticipative Result
When CPU, RAM or HD usage exceed monitoring threshold, the alarm will be triggered.
7.8 Link Monitor

Test Item System Management
Page 57 of 71
Sub-Item Test Target Test Networking Precondition
Link Monitor Verify the function of BSC <-> EMS-platform link failure alarms 1. 2. OMC runs normally NE and OMC are normal in communication Login OMC Client and Open [Fault Management] view Make BSC <-> EMS-platform link failure See whether there are new alarms displays in the Realtime Alarm Monitor windows. Alarm mean there is a link failure between BSC and OMC-platform.
Test Steps
1. 2. 3.
By step 3, users can see the link failure alarms-.
7.9 Time Management

Test Item Sub-Item Test Target Test Networking Precondition 1. 2. 3. 4. 5. 1. OSS works normally The link between OSS and NE is normal Log on OSS SNTP server works normally The NE Management of NE Agent is started At OSS client, Right click [NE Agent] in [Physical View] window of [Topology Management], and select [NE ManagementConfiguration Management] to open the Configuration Management window. Right click [BSC Managed Element] and select [Apply mutex right] to get mutex right. In Configuration Management window, double click [BSC Ground Resource Management] to open BSC Ground Resource Management page. Click [Modify] on toolbar to set SNTP server IP address in BSC Ground Resource Management page. Synchronize modified tables to NE in BSC Managed
Page 58 of 71
Time Management Synchronize all network elements clock to be the same time automatically
Test Steps
2. 3.
4. 5.
6.
7. Anticipative Result 1.
Element page. Click [Synchronize NEs Clock] on the toolbar of BSC Ground Resource Management page and then a confirm dialog pops up. Click [OK] to synchronize with NE. When the summer time begins, the time of new alarm and performance data reported from NE is accord with summer time. When the summer time is past, the time of new alarm and performance data reported from NE is accord with normal time. Time Synchronization with NE is successful.
2.
7.10 License Management

Test Item Sub-Item Test Target Test Networking Precondition 1. 2. 3. 4. EMS works normally The link between EMS and NE is normal Log on EMS The NE Management of NE Agent is started System Management License Management Know license information
Test Steps
1. Select [Help->license information->Show license] 2. The [License Information] window opens 3. Check the license item and license value. 4. View license of a single NE/ multiple NE 5. Add/distribute license to single NE/ multiple NE 6. Deactivate licence from a single NE/ multiple NE License management is successful.
7.11 Node Hardening

Test Item Sub-Item Test Target Test Networking
Node Hardening Node Hardening

To verify Hardware and platform function As shown in Fig.1
Page 59 of 71
Precondition Test Steps
None 1. Suggest that OMC server installs on Solaris and OMC client on windows xp/windows vista/windows 7 system client software Same user can login in separate PCs at same time simultaneously Two different users can login to client software at same time simultaneously in a one PC.
2.
OMC system runs normally. Multiple user Multiple session binding is possible.
7.12 Base Station Re-homing

Objectives Test Networking Precondition The purpose of this test case is to verify the functionality of Base Station Re-homing 1. 2. 3. 4. 1. OSS works normally The link between OSS and NE is normal Log on OSS The NE Management of NE Agent is started. Filling in Template before Base Station Transfer, the template is under ERT\zxwomc-R3.09.******\umsclnt\deploy\template\rnc\template_EN, and its name is wplan.xls. 2. In the Topology Management, click[Configuration>Wireless Config Application->Transfer Site] 3. Click the Select button from the Transfer Base Station dialog box, and select the template file (wplan.xls) from the Open window popped up. 4. From the Transfer Base Station dialog box, Select Online Transfer and deselect Bind OMCB. User can select and deselect Delete Site as needed. 5. Click Execute to start transferring, and printing hints and transferring progress are displayed on the interface. The Base Station Re-homing successful
Test Steps
Page 60 of 71
8.
Security Management
8.1 User Management

Test Item Sub-Item Test Target Test Networking Precondition 1. 2. 3. 4. EMS works normally The link between EMS and NE is normal Log on EMS The NE Management of NE Agent is started Security Management User Management Creating, modifying, and deleting users are supported.
Test Steps
Creating 1. 2. Login OMC client and open the [Security Management] Choose [Security Management Tree->User Management], click Create User on the pop-menu of User Management. 3. Input the parameters, such as user name(must unique), password, phone, email in the Basic Information tab, set the Password Validity(days) in Advanced Information tab, choose the role(s)/role set(s) for user in Role tab, and also, set a department in User Department tab, set Work Time in Login tab. 4. Press OK button to save parameters.
Modification 1. Login OMC client and open the [Security Management] 2. Choose [Security Management Tree->User Management], and choose one of users in the user list on the right. (PS: these users are allowed to modify by this login user, or they are created by login user. Administrator can modify each user). 3. 4. Click Modify on the pop-menu of this chosen user.
Could modify this users properties except user name and press OK to save parameters. Deletion 1. Login OMC client and open the Security Management sub view 2. Choose [Security Management Tree->User
Page 61 of 71
Management], and then choose one of users in the user list on the right. 3. Anticipative Result Test Description Test Result Click Delete on the pop-menu of this chosen user.
Creating, modifying, and deleting users are success
8.2 User Authorization

Test Item Sub-Item Test Target Test Networking Precondition 1. 2. 3. 4. EMS works normally The link between EMS and NE is normal Log on EMS The NE Management of NE Agent is started Security Management User Authorization Verify the function of Users Operation Authentication
Test Steps
1. Login the client as a certain user 2. The user executes some operation and the system authenticates the operation
The User can operate the modules or NE(s) in client only when the user has these authorities.
8.3 Role Management

Test Item Sub-Item Test Target Test Networking Precondition 1. 2. 3. 4. EMS works normally The link between EMS and NE is normal Log on EMS The NE Management of NE Agent is started
Page 62 of 71
Security Management Role Management Verify the function of role creation, Modification, Deletion
Test Steps
Creation: 1. Login EMS client and open the [Security Management] 2. Choose [Security Management Tree->Role Management], click Create Role on the pop-menu of Role Management. 3. Input the parameters, such as input role name(must unique), description in the Basic Information tab, authorize rights of operations and resources in Access Rights tab, set login IP range in Login Address tab, and also, choose user(s) for role in User tab. 4. Press OK button to save parameters.
Modification: 1. Login OMC client and open the [Security Management] 2. Choose [Security Management Tree->Role Management], and choose one of roles in the role list on the right. (PS: these roles are allowed to modify by this login user, or they are created by login user. Administrator can modify each role). 3. 4. Click Modify on the pop-menu of this chosen role.
Could modify this roles properties except role name and press OK to save parameters. Deletion: 1. Login OMC client and open the Security Management sub view. 2. Select [Security Management Tree->Role Management], and then choose one of roles in the role list on the right. 3. Click Delete on the pop-menu of this chosen role.
Anticipative Result
1. New role is created and role's properties are same as parameters that are set before. 2. EMS saves the roles information to database. 3. Users who only assign this role will be deleted 4. Role list is refreshed.
8.4 Log Management

Test Item Sub-Item Test Target Test Networking Precondition
Security Management Log Management Verify operation log, system log, and security log are supported 1. 2. 3. 4. EMS works normally The link between EMS and NE is normal Log on EMS The NE Management of NE Agent is started
Test Steps
1. Login EMS client and open the [Security Management] 2. Choose [Security->Log Management]. 3. Select type of logs subcontent, such as [All Operation Log],[All Security Log],[All System Log],and so on.,then double-click it. 4. All log will display. The system queries the qualified logs in the database and displays them in the log records list of Log Management.
Page 64 of 71
9. 9. Trace Management
9.1 Signaling Trace
Objectives Test Networking Precondition Test Steps To verify Central Call Trace Activation and Management function 1. 2. 1. 2. RAN network and core network work normally The link between LMT and NE is normal Run rct.bat to open Call Trace System window.
Click [File->Connect] and then the Communicating address setting dialog box pops up and set BSC s IP and port to make Signal Trace System connect with BSC successfully
3.
4.
Click [Task Manage] to pop up task winodw; Click [Create new task] to select MS type to create signal trace task for signal collection and input task name and ImsiId etc;
5. 6. 7. 8.
Click [Create new task] to select CELL type to create signal trace task for signal collection. After the tasks are created, start the task and make a call using WCDMA system Observe the window, signal data will be reported from NE and displayed in the window You can select the created task ,select one imsi id or cell id , click [stop Trace] on the right menu, then the signal collection about this task will stop
9.
Select the created task ,select one imsi id or cell id , click [start Trace] on the right menu, then the signalling collection about this task will start again
10. Select the created task ,select one imsi id or cell id ,click [Delete] on the right menu, task will disappear in the window 11. 11. Trace result can save in client PC. 12. Following traces can taken from the EMS. Interface traces (A,A -bis, A-ter)
Page 65 of 71
Anticipative Result
1. Signaling Tracing
System
collects
and
displays
signaling data normally 2. Addition and deletion of a UE in the list can be done without any outage 3. Addition and deletion of a cell in the list can be done without any outage 4. Create or delete task ,activation or deactivation task successfully 5. Save the trace is successful.
Page 66 of 71
10. 10 O&M Infrastructure

10.1 Telnet Access
Test Item Sub-Item Test Target Test Networking Precondition Test Steps Anticipative Result Test Description Test Result O&M Infrastructure Telnet Access To verify Remote Access function As shown in Fig.1 Prepare a remote client A remote client connect OMC server The remote client will access system successfully.
10.2 database Access

System management Database Access The purpose of this test case is to verify the functionality of database Access OMC system ready. Click [Maintenance->System Monitor] , In the system management tree on the left view and choose [oracle:sid@IP] , Click [View Database Resources Oracle] menu items in the right. 2. You can database Access database Access
1.
Page 67 of 71
11. 11 Tool
11.1 NE healthy check
Test Item Sub-Item Test Target Test Networking Precondition Tool NE healthy check The purpose of this test case is to check the healthy information of the NE. As shown in Fig.1 1. 2. 3. 4. 1. OMC works normally The link between OMC and NE is normal Log on OMC The NE Management of NE Agent is started.
Test Steps
At OMC client, click [View -> Configuration Report] to open the Configuration report window. 2. Click IBSCMEID, the pop-up tree, right click one nod, choose File Report, in the pop-up window, choose file type XML and IBSC Managed ID, then click [OK] button. 3. Then wait for a while, the result information will be Displayed when whole process is completed. NEs health information is generated as xml file type, and the information is according with the NE current running status.
11.2 MML function

Test Item Sub-Item Test Target Test Networking Precondition Test Steps Tools MML function To verify the function of MML As shown in Fig.1 1. OMC works normally 2. Log on OMC 1.Login OMC client. 2.In the main menu, click [ViewMML Terminal] 3.Select an element on the MML-tree: NetNumen>Performance Management->Measure Task->Get Measure Task List, 4.Choose ALL(All Task) in the list box on the right sub
Page 68 of 71
Anticipative Result
window. 5.Click the button Execute(F5) The MML command can be executed correctly. User can see all the pm tasks of the system in the Command Execute Result window.
11.3 Online Help

Test Item Sub-Item Test Target Test Networking Precondition Tool Online Help To verify Online Help function As shown in Fig.1 1. OMC works normally 2. Log on OMC 1. At OMC, click [help] on menu and open help window. 2. On left part of help window, managed object tree will display, and help description on the right. Help description is exact and correct.
Test Steps
Page 69 of 71
12. 12 Northbound Interface

12.1 Itf-N CORBA FM (GERAN &UTRAN)
Objectives Test Networking Precondition The purpose of this test case is to verify the functionality of Configuration Data Availability 1. OMC works normally 2. The link between OMC and NE is normal 3. Log on OMC 4. The NE Management of NE Agent is started. Output: At OMC client, Right click [NE Agent] in [Physical View] window of [Topology Management], and select [NE ManagementConfiguration Management] to open the Configuration Management window. Select the node of [BSC managed Element] in the left tree, then click the menu of [BSC ManagedElement->Configuration Data Export Tool], a window pop-up. In this window, user can select configuration data which need to export, then click<Export Data> button, select a path to save the files. Input: Export the [Export Input Radio Parameter] via the method of Output. Modify some parameters or add some records. If you want to modify parameters, the field of MODIND must set to M; if you want to add some records, the field of MODIND must set to A; if you want to delete some record, the field of MODIND must set to D; After the input file has been prepared, click [BSC ManagedElement->Configuration Guide], select the Managed Element ID and Config Set ID. Click OK. Click [Radio Data->Data of Radio Management Object Batch Import], a tab page show in the right window. Click [Read Data File] to select the input file, then click [execute] button to execute. The result will be shown in the message area. The configuration can be exported successful. The configuration can be imported successful.
Test Steps
Page 70 of 71
12.2 Itf-N FTP PM (GERAN&UTRAN)

Objectives Test Networking Precondition The purpose of this test case is to verify the functionality of Neighboring Cell Configuration Data Check 1. OMC works normally 2. The link between OMC and NE is normal 3. Log on OMC 4. The NE Management of NE Agent is started. Configure the query model, timing task and other configuration parameter of the CSV interface file in configuration file. implement manually the command generating performance file There will be file generated at the default directory, and the data is intact with customized data.
Test Steps
Page 71 of 71

ZTE BSS Features

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ZTE BSS Features

Hochgeladen von

Copyright:

Verfügbare Formate

ZTE Corporation

ZTE GSM OMC RAN Test Handbook

ZTE GSM OMC RAN Test Handbook

ZTE GSM System Test Handbook RAN OMC

ZTE GSM System Test Handbook RAN OMC

Copyright of ZTE Corporation. All Rights Reserved

ZTE GSM System Test Handbook RAN OMC

Symbol and Abbreviations

Copyright of ZTE Corporation. All Rights Reserved

ZTE GSM System Test Handbook RAN OMC

Um MS SDR Abis BSC Gb

Packet Core Network

Copyright of ZTE Corporation. All Rights Reserved

ZTE GSM System Test Handbook RAN OMC

Test Description Test Result

2.2 Key CM/FM/PM Information Display

Copyright of ZTE Corporation. All Rights Reserved

ZTE GSM System Test Handbook RAN OMC

Test Description Test Result

Copyright of ZTE Corporation. All Rights Reserved

ZTE GSM System Test Handbook RAN OMC

3.2 Multi-Mode Base Station Management

Copyright of ZTE Corporation. All Rights Reserved

ZTE GSM System Test Handbook RAN OMC 5.

3.3 Multi Configuration Sets

Copyright of ZTE Corporation. All Rights Reserved

ZTE GSM System Test Handbook RAN OMC

Message Flow Test Description Test Result Parameters Setting

3.4 Guide for Configuration

Copyright of ZTE Corporation. All Rights Reserved

ZTE GSM System Test Handbook RAN OMC

Message Flow Test Description Test Result Parameters Setting

3.5 Data Synchronization

Copyright of ZTE Corporation. All Rights Reserved

ZTE GSM System Test Handbook RAN OMC

Message Flow Test Description Test Result Parameters Setting

3.6 Configuration Data Availability Check

Copyright of ZTE Corporation. All Rights Reserved

ZTE GSM System Test Handbook RAN OMC

3.7 Neighboring Cell Configuration Data Check

Message Flow Test Description Test Result Parameters Setting

3.8 Configuration Data Template (GERAN&UTRAN)

Copyright of ZTE Corporation. All Rights Reserved

ZTE GSM System Test Handbook RAN OMC

3.9 Fast Commissioning of Site

Copyright of ZTE Corporation. All Rights Reserved

ZTE GSM System Test Handbook RAN OMC

3.10 Configuration Data Upload

Copyright of ZTE Corporation. All Rights Reserved

ZTE GSM System Test Handbook RAN OMC

3.11 Configuration Rack Map

Copyright of ZTE Corporation. All Rights Reserved

ZTE GSM System Test Handbook RAN OMC

Message Flow Test Description Test Result Parameters Setting

3.12 Status Monitoring

3.13 Centralized configuration Management

Copyright of ZTE Corporation. All Rights Reserved

ZTE GSM System Test Handbook RAN OMC

3.14 Configuration import

Anticipative Result Test Description Test Result

Copyright of ZTE Corporation. All Rights Reserved

ZTE GSM System Test Handbook RAN OMC

3.15 Configuration Data Collection

3.16 Hardware Inventory