customer change requests dn0698004x1x0xen

8/22/2019 Customer Change Requests DN0698004x1x0xen

http://slidepdf.com/reader/full/customer-change-requests-dn0698004x1x0xen 1/56

Nokia MetroSite EDGE Base Station

Test Specification for Customer Change Requests in BTS SW

Release CXM5

DN0698004Issue 1-0 en

©Nokia CorporationNokia Proprietary and Confidential

1 (56)



Test Specification for Customer Change Requests in BTS SW Release CXM5

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is intended for theuse of Nokia's customers only for the purposes of the agreement under which the document issubmitted, and no part of it may be reproduced or transmitted in any form or means withoutthe prior written permission of Nokia. The document has been prepared to be used by

professional and properly trained personnel, and the customer assumes full responsibilitywhen using it. Nokia welcomes customer comments as part of the process of continuousdevelopment and improvement of the documentation.

The information or statements given in this document concerning the suitability, capacity, orperformance of the mentioned hardware or software products cannot be considered bindingbut shall be defined in the agreement made between Nokia and the customer. However,Nokia has made all reasonable efforts to ensure that the instructions contained in thedocument are adequate and free of material errors and omissions. Nokia will, if necessary,explain issues which may not be covered by the document.

Nokia's liability for any errors in the document is limited to the documentary correction of errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDINGMONETARY LOSSES), that might arise from the use of this document or the information in it.

This document and the product it describes are considered protected by copyright accordingto the applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

Other product names mentioned in this document may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright ©Nokia Corporation 2007. All rights reserved.

Hereby, Nokia Corporation declares that this Nokia Base Station is in compliance withthe essential requirements and other relevant provisions of Directive: 1999/5/EC. Theproduct is marked with the CE marking and Notified Body number according to theDirective 1999/5/EC.

2 (56) ©Nokia CorporationNokia Proprietary and Confidential




Contents

Contents

1 About this document .............................................................................4

1.1 Scope.......................................................................................................4 1.2 Hardware requirements............................................................................5 1.3 Software requirements .............................................................................5 1.4 Specialist test equipment requirements ...................................................5

2 Test cases ...............................................................................................6 2.1 CRQ98 - Local Remote MMI Alarm [BSS20426].....................................6 2.1.1 Description of Alarm 7801 with local BTS Manager – Manual

connect.....................................................................................................7 2.1.2 Description of Alarm 7801 with local BTS Manager – Command

Line connect.............................................................................................8 2.1.3 Description of Alarm 7801 - Remote BTS Manager connected

using GCS Database..............................................................................10 2.1.4 Description of Alarm 7801 - Remote BTS Manager started from

NetAct TLUI............................................................................................11 2.1.5 Description of Alarm 7801 - Remote BTS Manager connected

using Sobriquet String............................................................................12 2.1.6 Description of Alarm 7801 - Remote BTS Manager connected

using Target String.................................................................................13 2.2 CRQ105 - Output Raw RSSI Results to MMI [BSS20694].....................15 2.2.1 Display of Raw data for RSSI values on a locally connected

BTS Manager.........................................................................................15 2.2.2 Display of Raw RSSI data on Remote BTS Manager............................17

2.2.3 Alarm handling for RSSI.........................................................................18 2.2.4 Help for Raw RSSI Comparison values on BTS Manager.....................20 2.2.5 Display of Raw data for RSSI values with old BTS SW .........................20 2.2.6 RSSI functionality with RX Diversity disabled........................................22 2.2.7 RSSI functionality with single TRX.........................................................23 2.3 RSSI Improvements [BSS20694, BSS20973]........................................24 2.3.1 CRQ156 - MMI Settable RSSI Sample Limit [BSS20694,

BSS20973].............................................................................................24

References ............................................................................................56



3 (56)




1 About this document 1.1 Scope

This document incorporates the customer Change Requests (CRQs) test phase

and defines the test cases for verifying customer CRQs of the BTS software

release CXM5 for MetroSite base stations. The purpose of the tests is to verify

that the BTS configured with the feature works as specified.

For details on the CRQ test cases for UltraSite base station, refer to Test

schedule for Customer Change Requests of BTS SW Release CX5 [1].

Note 1.

All test cases are performed using BSC SW S12 unless otherwise stated.

Note 2.

The BSC default values are to be used unless otherwise stated.

Note 3.

Throughout this document, BTS Manager SW refers to the CX5 BTS Manager

SW being tested, unless otherwise stated.

Note 4.Use GCS5.0, unless otherwise stated in the test case.

Note 5.

GCS5.0 supports the following operating systems: Windows XP Professional,

Windows 2000 Professional, Windows 2000 Server and Windows NT4.0.





About this document

Note 6.

In BTS Manager, select the Automatic BTS Connection checkbox in the LMP

tab of FileÆOptions menu if it is not selected before launching BTS

Manager.

1.2 Hardware requirements

Base stations MetroSite base stations.

Other Network Elements

• BSC

• Core Network with GPRS and EDGE capabilities

• Nokia NetAct OSS4

1.3 Software requirements

• SiteWizard 5.0

• CXM5 release containing the feature under test.

• Operating System on BTS Manager PC (Windows 2000, Windows XP or

Windows NT), Win2000/Win2003 node manager server.

1.4 Specialist test equipment requirements

The following test equipment is required in some test cases:

• Assortment of combiners

• Attenuators

• Terminators

• GSM Protocol Analyser



5 (56)




2 Test cases 2.1 CRQ98 - Local Remote MMI Alarm [BSS20426]

Due to this Change Request, alarm description for 7801 MMI CONNECTED

TO BASE STATION will now show if MMI is connected locally or remotely.

For more information, see Alarm Descriptions [2] in BTS SW release

documentation.

The following Notes apply to the test cases for CRQ 98, unless stated otherwise.

Additional Notes are included where relevant.

Note 7.

All required physical connections for the local connection are present. That is,the BTS Manager PC is connected with BTS via an LMP Cable.

Note 8.

The Enable Automatic BTS Connection checkbox in the LMP tab of File Æ

Options menu, should be unchecked before launching BTS Manager.

Note 9.

Before these test cases are executed, the tested BCF is created in the NetAct

Top Level User Interface (TLUI) of the BSC to which this BCF belongs. For more information on creating the BCF in TLUI and on checking alarms in

NetAct, refer to document Alarm Checking at NetAct .

Note 10.

In the NetHawk traces for alarm 7801, contents of the Additional Info IE are

shown as hexadecimal values in the ASCII notation for each of the characters

appearing in the string “Local MMI Connected”.





Test cases

Note 11.

BCF is in Supervisory state.

2.1.1 Descript ion of Alarm 7801 with local BTS Manager – Manualconnect

Purpose:

The purpose of this test is to check the alarm description for alarm 7801 while

BTS Manager is locally connected to the BTS.

Input Expected Output

1. Launch BTS Manager application. Nokia BTS Manager starts in disconnected state.

2. Connect BTS Manager locally to the BTS byclicking Connection Æ Connect Locally menu item.

Monitor the Abis link.

Supervision – Equipment View, Alarms and BTSEvents windows are displayed.

The status bar of the main window displays “BTSConnected” and “COM x”, where x is thecommunications port on which the BTS isconnected. The title bar of the main windowdisplays BTS Manager– BTS Events.

Verify the alarms received at the BSC, NetAct

and BTS Manager. Verify that the description of alarm 7801 reads MMI CONNECTED TO BASESTATION: Local MMI Connected.

On the Abis, verify that alarm 7801 is started.Additional Info IE of this alarm for the locallyconnected BTS Manager will be: 4C 6F 63 61 6C20 4D 4D 49 20 43 6F 6E 6E 65 63 74 65 64 2E

3. Disconnect the BTS Manager by clickingConnection Æ Connect Locally menu item.


BTS Manager is disconnected and both thewindows Supervision – Equipment View andAlarms will not be visible.

Status bar will display “Not Connected”.

Alarm 7801 is cancelled at the BSC and NetAct.On the Abis, verify that alarm 7801 is cancelled.Additional Info IE of this alarm for the locallyconnected BTS Manager will be: 4C 6F 63 61 6C20 4D 4D 49 20 43 6F 6E 6E 65 63 74 65 64 2E

Case Ref. Configuration

383527.02 Any Multi-TRX MetroSite Configuration



7 (56)




2.1.2 Descript ion of Alarm 7801 with local BTS Manager – CommandLine connect

Purpose:

To check the alarm description for alarm 7801 while BTS Manager is locally

connected to BTS through a command line interface. Also to verify that this

description does not affect the Additional Info of other alarms on the BTS

Manager, NetAct and BSC and vice-versa.





Test cases


1. Start the command prompt and change thedirectory to the installation path of BTSManager.

Start BTS Manager at the command promptwith the following command:

BTSManager . exe


Nokia BTS Manager starts with connection to theLocal BTS. BTS Event window shows themessage “BTS Manager Started”.

The status bar of the main window shows “BTSConnected” and “COM x”, where x is thecommunications port on which the BTS isconnected. The title bar of the main windowshows BTS Manager– BTS Events.

Verify the alarms received at the BSC, NetActand BTS Manager. Verify that the description of alarm 7801 reads MMI CONNECTED TO BASESTATION: Local MMI Connected.

On the Abis, verify that alarm 7801 is started.Additional Info IE of this alarm for the locallyconnected BTS Manager will be: 4C 6F 63 61 6C20 4D 4D 49 20 43 6F 6E 6E 65 63 74 65 64 2E

2. A TRX slave working as non-BCCH TRX isremoved.

Alarm 7606 TRX FAULTY can be seen at theBTS Manager and at the BSC. (The master TRXdetected that the connection to the slave is lost.)

Verify that the “Additional info” of alarm 7606 isdisplayed correctly and the occurrence of thisalarm does not affect the description of alarm7801.

3. The TRX is installed back. Alarm 7606 TRX FAULTY is cancelled.

The TRX returns to operational state.

4. Disconnect BTS Manager by clicking theConnection Æ Disconnect menu item.


BTS Manager will be disconnected and bothwindows Supervision – Equipment View andAlarms will not be visible.

Status bar will display Not Connected.

Alarm 7801 is cancelled at the BSC and NetAct.

On the Abis, it can be verified that alarm 7801 iscancelled. Additional Info IE of this alarm for thelocally connected BTS Manager will be: 4C 6F 6361 6C 20 4D 4D 49 20 43 6F 6E 6E 65 63 74 6564 2E


383514.02 Any Multi-TRX MetroSite configuration without BB Hopping.



9 (56)




2.1.3 Descript ion of Alarm 7801 - Remote BTS Manager connected usingGCS Database

Purpose:

To check the alarm description for alarm 7801 while BTS Manager is remotely

connected to the BTS using GCS Database.

Note 12.

LMP Cable is not connected to the BTS.

Note 13.

For defining data in GCS database and establishing Remote BTS connection,

refer to the document Establishing Remote BTS Manager Connection.


1. Connection Data is defined for the BTS in thelocal GCS Database of Node Manager, byusing Nokia Connection tool.

Connection Data can be defined and saved intothe local GCS Database of Node Manager.

2. Start BTS Manager from the Node Managerserver.

Connect BTS Manager remotely to the BTSby clicking the Connection Æ Disconnect menu item. Connection data is fetched from

the local GCS Database.


The Remote BTS Manager starts successfully.Supervision – Equipment View, Alarms andBTS Events windows are displayed.

Verify the alarms received at the BSC, NetActand Remote BTS Manager. Verify that the

description of alarm 7801 is MMI CONNECTEDTO BASE STATION: Remote MMI Connected.

On the Abis, verify that alarm 7801 is started.Additional Info IE of this alarm for the remotelyconnected BTS Manager will be: 52 65 6D 6F74 65 20 4D 4D 49 20 43 6F 6E 6E 65 63 74 6564 2E

3. Disconnect the remote BTS Manager sessionby clicking the Connection Æ Disconnect menu item.


Remote connection to BTS Manager of therequested BCF is disconnected.

Alarm 7801 is cancelled at the BSC and NetAct.

On the Abis, it can be verified that alarm 7801 iscancelled. Additional Info IE of this alarm for theremotely connected BTS Manager will be: 52 656D 6F 74 65 20 4D 4D 49 20 43 6F 6E 6E 6563 74 65 64 2E


383429.02 Any Multi-TRX MetroSite configuration





Test cases

2.1.4 Descript ion of Alarm 7801 - Remote BTS Manager started fromNetAct TLUI

Purpose:

To check the alarm description for alarm 7801 while Remote BTS Manager is

started from NetAct Top-Level User Interface (TLUI) and using connection

data from the GCS Database. To verify that this description does not effect the

Additional Info of other alarms on BTS Manager, NetAct and the BSC, and

vice-versa.

Note 14.

LMP Cable is not connected to the BTS.

Note 15.

If Remote BTS Manager is started using the NetAct TLUI, the GCS of Node

Manager Server is used.

Note 16.

For establishing remote connection using NetAct TLUI, refer to the document

Establishing Remote BTS Manager Connection.


1. Start BTS Manager from the NetAct TLUI.

Directly launch the BTS Manager applicationby right-clicking the TRE object with whichthe remote connection is to be established.Connection data is fetched from the localGCS Database.


Remote BTS Manager starts successfully.Alarm 7801 is raised at both the BSC andRemote BTS Manager.

Verify the description of alarm 7801 at RemoteBTS Manager, the BSC and NetAct. It shouldread as follows: MMI CONNECTED TO BASESTATION: Remote MMI Connected.

On the Abis, verify that alarm 7801 is started.Additional Info IE of this alarm for the remotelyconnected BTS Manager will be: 52 65 6D 6F

74 65 20 4D 4D 49 20 43 6F 6E 6E 65 63 74 6564 2E



11 (56)





2. A TRX slave working as non-BCCH TRX isremoved.

Alarm 7606 TRX FAULTY can be seen at theBTS Manager and at the BSC. (The master

TRX detected that the connection to the slave islost.)

Verify that Additional Info of alarm 7606 iscorrectly displayed and the occurrence of thisalarm does not affect the description of alarm7801.

3. The TRX is installed back. Alarm 7606 TRX FAULTY is cancelled.

The TRX returns to operational state.

4. Disconnect the remote BTS Manager sessionby clicking the Connection Æ Disconnect menu item.


Remote connection to BTS Manager of therequested BCF is disconnected. Alarm 7801 iscancelled at the BSC and NetAct.

On the Abis, verify that alarm 7801 is cancelled.Additional Info IE of this alarm for the remotelyconnected BTS Manager will be: 52 65 6D 6F74 65 20 4D 4D 49 20 43 6F 6E 6E 65 63 74 6564 2E


383507.02 Any Multi-TRX MetroSite configuration without BB Hopping

2.1.5 Descript ion of Alarm 7801 - Remote BTS Manager connected using

Sobriquet String

Purpose:

To check the alarm description for alarm 7801 while BTS Manager is remotely

connected to the BTS through a command line interface using Sobriquet String.

Note 17.

For defining data in GCS database and establishing Remote BTS connection,

refer to the document Establishing Remote BTS Manager Connection.


1. Create a Connection Node using NokiaConnection Tool parameters on a laboratory PC.

A new Connection Node is created with asobriquet string “remBTS” (a display namefor the Network Element) and stored in theGCS Database.





Test cases


2. Start the command prompt and change thedirectory to the installation path of BTS Manager.

Start BTS Manager with the following commandat the command prompt:

BTSManager . exe –sobr i quet “r emBt s”


Remote BTS Manager starts successfully.

Supervision – Equipment View, Alarms andBTS Events windows are displayed.

Verify the alarms received at the BSC,NetAct and Remote BTS Manager. Verifythat the description of alarm 7801 readsMMI CONNECTED TO BASE STATION:Remote MMI Connected.

On the Abis, verify that alarm 7801 isstarted. Additional Info IE of this alarm forthe remotely connected BTS Manager willbe: 52 65 6D 6F 74 65 20 4D 4D 49 20 436F 6E 6E 65 63 74 65 64 2E

3. Disconnect the remote BTS Manager session byclicking the Connection Æ Disconnect menuitem.


Remote connection to BTS Manager of therequested BCF is disconnected.

Alarm 7801 is cancelled at the BSC andNetAct.

On the Abis, it can be verified that alarm7801 is cancelled. Additional Info IE of thisalarm for the remotely connected BTSManager will be: 52 65 6D 6F 74 65 20 4D4D 49 20 43 6F 6E 6E 65 63 74 65 64 2E



2.1.6 Descript ion of Alarm 7801 - Remote BTS Manager connected usingTarget String

Purpose:

To check the alarm description for alarm 7801 in the following cases:

• When BTS Manager is remotely connected to the BTS through a

command line interface using Target String.

• When a Local BTS Manager connection is started while Remoteconnection is already running.

Note 18.

LMP cable is connected to the BTS.



13 (56)




Note 19.

For the proper activation and cancellation of alarm 7801at the BSC, the

following MML command needs to be given at the BSC:

ZEOM: 7801: MOD=CDL, TI ME=0;


1. Enter the command Prompt on the laboratory PCand change the directory to the installation pathof BTS Manager.

Start BTS Manager with the following commandat the command prompt:

BTSManager . exe –t arget

“WP=SOCKET, HOST= <i p_addr ess_of _OSSser ver >, PORT=7878, WP=BSC,USER=<user name f or OSS ser ver >,PSW=<Passwor d f or OSS ser ver >,BSCI D=<c_number _of _BSC>,BUSI D=0, TI ME=10000, WP=BTS,BCFI D=<bcf _i d>, TRXI D=0, TI ME=100000, WP=NEQ1,ADDR=4001”


The Remote BTS Manager startssuccessfully.

Supervision – Equipment View, Alarms andBTS Events windows are displayed.

The title bar of the main window showsRemote BTS Manager BSC ID =x, BCF ID =

y – BTS Events. Where x and y are thecorresponding BSC and BCF IDs.

Verify the alarms received at the BSC, NetActand Remote BTS Manager. Verify that thedescription of alarm 7801 is MMICONNECTED TO BASE STATION: RemoteMMI Connected.

On the Abis, verify that alarm 7801 is started.Additional Info IE of this alarm for theremotely connected BTS Manager will be: 5265 6D 6F 74 65 20 4D 4D 49 20 43 6F 6E 6E65 63 74 65 64 2E

2. The BTS Manager of the same BCF is startedlocally.


The local BTS Manager is started and thecurrent remote BTS Manager connection iscancelled, giving the following message:Remote session has been terminated by theBTS because an MMI application hasconnected locally.

Verify that the description of alarm 7801 onthe local connection and at the BSC andNetAct is MMI CONNECTED TO BASESTATION: Local MMI Connected.

On the Abis, verify that alarm 7801 is first

cancelled. Additional Info IE of this alarm forthe remotely connected BTS Manager will be:52 65 6D 6F 74 65 20 4D 4D 49 20 43 6F 6E6E 65 63 74 65 64 2E

Again on the Abis, verify that alarm 7801 isstarted again. Additional Info IE of this alarmfor the locally connected BTS Manager willbe: 4C 6F 63 61 6C 20 4D 4D 49 20 43 6F 6E6E 65 63 74 65 64 2E






Test cases



2.2 CRQ105 - Output Raw RSSI Results to MMI[BSS20694]

The following Notes apply to the test cases for this CRQ, unless otherwise

stated. Additional Notes are included where necessary.

Note 20.

RX Diversity is set ON and all the required diversity cables are properly

connected.

Note 21.

A new table (Raw) has been added in the RSSI Comparison Values dialog that

reports the RSSI values obtained every 10 minutes. For more information, see

Feature Descriptions for Nokia MetroSite EDGE Base Station [3].

Note 22.

The antenna can only be supervised reliably if the BCCH power level is within

the acceptable range of power levels 0 to 6.

Note 23.

Hopping is not used unless otherwise stated.

Note 24.

Site is in Supervisory state.

2.2.1 Display of Raw data for RSSI values on a locally connected BTSManager

Purpose:

To check that Raw values are displayed on the RSSI Comparison Values Dialog

of a locally connected BTS Manager for different configurations.



15 (56)




Note 25.

When the site is reset or commissioned, a TRX test is carried out for all the

TRXs. This results in some RSSI values being calculated and displayed after

first 10 minutes in the Raw table.

The RSSI values being calculated and displayed after the first 10 minutes in the

Raw table gets automatically removed in the next reading of the Raw table for

those TRXs that are not carrying any traffic or idle.

Note 26.


Equipment and BTS setupAs defined in the test case below.


1. Site is reset.

BTS Manager application is launched andconnected to the BTS locally.

Site comes to Supervisory state.

BTS Manager starts successfully.

2. Call(s) are made on the BTS so as high trafficsituation is met.

Call(s) should remain active throughout theduration of the test case.

Call(s) are successful.

3. Before 10 minutes have elapsed since the sitewas reset, click Supervision Æ RSSIComparison Values menu item in BTSManager to check the RSSI results.

RX antenna supervision is performed. All thetables (that is, Raw, Newest and Reliable)are blank in the RSSI Comparison Valuesdialog.

4. After 10 minutes of the call(s) being made, clickSupervision Æ RSSI Comparison Values menu item in BTS Manager to check the RSSIresults.

RX antenna supervision is performed. Rawvalues are displayed in the RSSIComparison Values dialog.

Main and Diversity RX levels (these valueswill be in the range from ‘0’ to ‘-110’), TRXBranch difference (this should be thedifference between main and diversityantenna values) and RX Relative difference(only for UltraSite) values are displayed for TRX(s) on which call(s) are made.

The tables Newest and Reliable are blank.





Test cases


5. Click the Refresh button in the RSSIComparison Values dialog after every 10

minutes and verify the results.

The date in the Raw table should getrefreshed. This means that the data

available at that time on the BTS should bedisplayed in the table.

The tables Newest and Reliable remainblank.

6. Antenna supervisory timer expires after 1 hour.RSSI Results are checked from BTS Manager.

All (Raw, Newest and Reliable) valuesshould be displayed for the TRX(s) on whichcall(s) are made.

7. Click the Save As button in the RSSIComparison Values dialog. Give the name of thefile to store the table data.

All the tables’ data should be saved correctlyinto the file specified.

Verify the contents of the file with the dataavailable on all the tables(Newest/Reliable/Raw).

8. Check the RSSI values in the Site Info and verifytheir contents.

Newest and Reliable values are displayedcorrectly in the Site Info, but Raw values arenot displayed in the Site Info.


390211.03 Multi-TRX sector (without IDD)

390211.04 Single sector with IDD Enabled (Main TRXs – 1 and 2, Aux. TRXs – 3 and 4)

2.2.2 Display of Raw RSSI data on Remote BTS Manager Purpose:

To check that Raw values are displayed in the RSSI Comparison Values dialog

when the BTS is remotely connected.

Note 27.

LMP cable is not connected to the BTS.

Equipment and BTS setup

As defined in the test case below.


1. Site is reset.

BTS Manager is remotely connected to the BTSusing the GCS Database of the local laboratoryPC.





17 (56)





2. Call(s) are made on the BTS so as high trafficsituation is met. Call(s) should remain active

throughout the duration of the test case.


3. Before 10 minutes have lapsed since the sitewas reset, click Supervision Æ RSSIComparison Values menu item in BTSManager to check the RSSI results.

RX antenna supervision is performed. All thetables (that is, Raw, Newest and Reliable)are blank in the RSSI Comparison Valuesdialog.

4. After 10 minutes of the call being made, clickSupervision Æ RSSI Comparison Values menu item in BTS Manager to check the RSSIresults.


Main and Diversity RX levels (these valueswill be in the range from ‘0’ to ‘-110’), TRXBranch difference (this should be the

difference between main and diversityantenna values) and RX Relative difference(only for UltraSite) values are displayed for TRX(s) on which call(s) are made.


5. Click the Refresh button in the RSSIComparison Values dialog after every 10minutes and verify the results.

The data in the Raw table should getrefreshed. This means that the dataavailable at that time on the BTS should bedisplayed in the table.

The tables Newest and Reliable remainblank.


All (Raw, Newest and Reliable) valuesshould be displayed for the TRX(s) on whichcall(s) are made.

7. Click the Save As button in the RSSIComparison Values dialog. Give the name of thefile to store the table data.

All the tables’ data should be saved correctlyinto the file specified.


8. Check the RSSI values in the Site Info and verifytheir contents.

Newest and Reliable values are displayedcorrectly in the Site Info, but Raw values arenot displayed in the Site Info.


390209.02 Multi-TRX sector

2.2.3 Alarm handling for RSSI

Purpose:





Test cases

To check that alarms are properly handled for RSSI after implementing the Raw

table in the RSSI Comparison Values dialog.

Note 28.

The value of RXDL at the BSC is set as 10 with the following MML command:

ZEFM: <bcf no. >: RXDL=10;

Equipment and BTS Set-Up

A 20dB attenuator is inserted on any one antenna line.


1. Site is reset.




2. Calls are made on all TRXs in the BTS so ashigh traffic situation is met. Calls shouldremain active throughout the duration of thetest case.

Calls are successful.

3. Antenna supervisory timer expires after 1hour. RSSI Results are checked from BTSManager. Alarms are checked at the BSC andBTS Manager.


RX antenna supervision is performed.

RSSI Results can be requested from BTSManager. BTS Manager displays Raw, Newestand Reliable values.

Main and diversity RX levels (these values willbe in the range from ‘0’ to ‘-110’), TRX Branchdifference (this should be the differencebetween main and diversity antenna values)and RX Relative difference (only for UltraSite)values are displayed for all TRXs.

All TRXs in the sector report RX Branchdifference value greater than the ‘RXDifference Limit’ value set at the BSC.

The following alarms are seen at the BSC andBTS Manager: alarm 7607 TRX OPERATIONDEGRADED (Rx levels differ too muchbetween main and diversity antennas),thereafter alarm 7601 BCF OPERATIONDEGRADED (Rx levels differ too muchbetween main and diversity antennas).

This alarm is also visible on the Abis interface.

4. The 20dB attenuator is removed.

Calls are made via each TRX in the BTS soas high traffic situation is met.




19 (56)





5. Antenna supervisory timer expires after 1hour. RSSI Results are checked from BTS

Manager. Alarms are checked at the BSC andBTS Manager.

Monitor the Abis link

RX antenna supervision is performed.

RSSI Results can be requested from BTSManager. BTS Manager displays the Raw,Newest and Reliable values. Main anddiversity RX levels, TRX Branch difference,and RX Relative difference values aredisplayed for the TRX having high traffic. Alarm7607 and 7601 are cancelled at the BSC aswell as on BTS Manager.

Verify the cancellation of alarms on the Abisinterface.


390208.02 2 TRX Omni (TRX1 & TRX2)

2.2.4 Help for Raw RSSI Comparison values on BTS Manager

Purpose:

To verify the contents of the Help for Raw RSSI Comparison Values in BTS

Manager.




1. Site is in Supervisory state.



2. Click Supervision Æ RSSI Comparison Values menu item in BTS Manager.

RSSI Comparison Values dialog is opened.

3. Click the Help button of the RSSI Comparisonvalues dialog or press F1 and verify the contentsof the Help page.

The Help dialog is launched and it containsinformation on the Raw, Newest andReliable RSSI values.


390212.02 Multi-TRX sector

2.2.5 Display of Raw data for RSSI values with old BTS SW

Purpose:





Test cases

To check that Raw values are not displayed on the RSSI Comparison Values

dialog when an older version (CXM4.1) of BTS SW is used.

Note 29.

Old BTS SW (CXM4.1) to be used. CXM5 BTS Manager SW to be used.




1. Site is reset.

The BTS Manager application is launched and

connected to the BTS locally.



2. Call(s) are made on the BTS so as high trafficsituation is met.

Call(s) should remain active throughout theduration of the test case.


3. After 10 minutes of the call(s) being made, clickthe Supervision Æ RSSI Comparison Values menu item in BTS Manager to check the RSSIresults.

RX antenna supervision is performed. Rawvalues are displayed in the RSSIComparison Values dialog and Raw table of RSSI comparison dialog will display thefollowing message: “Raw RSSI values arenot supported with the current version of BTS SW”.

Also verify that the following message is notdisplayed in the Events window:“Requesting RSSI Comparison values(Raw)”.

4. Verify the Raw RSSI data at each 10 minutes of time by doing refresh.

The Raw table should always display thefollowing message: “Raw RSSI values arenot supported with the current version of BTS SW”.


Newest and Reliable values should bedisplayed for the TRX(s) on which call(s) aremade.

The Raw table still displays the followingmessage: “Raw RSSI values are notsupported with the current version of BTSSW”.

6. Click Save As button of RSSI ComparisonValues dialog. Give the name of the file to storethe table data.

All the table data should be saved correctlyinto the file specified.




21 (56)






390210.02 Multi-TRX sector with GPRS enabled.

2.2.6 RSSI functionality with RX Diversity disabled

Purpose:

To check that RSSI is not performed in a sector when RX Diversity is disabled.

Note 30.

RX Diversity is set OFF for the sector in the BSC.

Note 31.

All the required diversity cables are properly connected.




1. Site is reset.




2. Call(s) are made on the BTS so as high trafficsituation is met. Call(s) should remain activethroughout the duration of the test case.


3. Check the RSSI results by clicking theSupervision Æ RSSI Comparison Values menu item in BTS Manager.

All the three output tables (Newest, Reliableand Raw) in the RSSI Comparison Valuesdialog are empty.

4. After 10 minutes of the call(s), check the RSSIresults again.

‘n/a’ will appear in Newest table, and Rawtable Reliable table still empty in the “RSSIComparison Values”

5. Click the Refresh button of the RSSIComparison Values dialog after every 10minutes interval until one hour is complete.

All the three output tables (Newest, Reliableand Raw) will remain ‘n/a’ in the RSSIComparison Values dialog. This indicatesthat RSSI is not performed even whenphysical diversity path is present, but RXdiversity is not defined in the BSC.





Test cases



390213.02 2-TRX Omni (TRX 1&2)

2.2.7 RSSI functionality with single TRX

Purpose:

To check that RSSI is not performed in sector with only one TRX (that is,

where the second TRX is not present to provide diversity).




1. Site is reset.




2. Call(s) are made on the BTS so as hightraffic situation is met. Call(s) should remainactive throughout the duration of the testcase.


3. Check the RSSI results by clicking theSupervision Æ RSSI Comparison Values menu item in BTS Manager.

All the three output tables (Newest, Reliable andRaw) in the RSSI Comparison Values dialog areempty.

4. After 10 minutes of the call(s), check theRSSI results again.

Raw and Newest values will be displayed as“n/a” in the RSSI Comparison Values dialog.Reliable table will be empty.

5. Click the Refresh button of RSSIComparison Values dialog after every 10minutes.

Raw and Newest values will still display “n/a” inthe RSSI Comparison Values dialog. Reliabletable will be empty.

6. Antenna supervisory timer expires after 1

hour. RSSI Results are checked from BTSManager.

Raw and Newest values will still display “n/a” in

the RSSI Comparison Values dialog. Thisindicates that RSSI cannot be performed in theabsence of a diversity path. Reliable table willstill be empty.


390214. 02 1-TRX sector



23 (56)




2.3 RSSI Improvements [BSS20694, BSS20973]

2.3.1 CRQ156 - MMI Settable RSSI Sample Limit [BSS20694, BSS20973]

The following Notes apply to all the test cases for this CRQ, unless otherwise

stated.

Note 32.

RX Diversity is set ON and all the required diversity cables are properly

connected.

Note 33.

Hopping is not used unless otherwise stated.

Note 34.

The number of samples for each TRX in the one-hour period can be seen in the

Frames column in the RSSI Comparison Values section of the site

information report.

Note 35.

Site is in Supervisory state and the value of the RXDS parameter is set as per

the test case.

Note 36.

Value of the RXDL parameter at the BSC is set as per the test case using the

following MML command:

ZEFM: <bcf no. >: RXDL=<val ue>;

Note 37.

Intra-cell handovers should be disabled on the sector(s).

Note 38.

A sample collected for a TRX will be considered as a reliable sample for RSSI

calculation if the minimum Rx level is –100dBm for CX(M)4.1 releases or

above, and –95dBm for releases prior to CX(M)4.1.





Test cases

Note 39.

The antenna can only be supervised reliably if the BCCH power level is within

the acceptable range of power levels 0 to 6.

2.3.1.1 Disp lay and Set up of RXDS parameter on BTS Manager

Purpose:

To verify that the value of the RXDS parameter can be displayed and set up

from BTS Manager, and it is also available in the Site Information report.

Note 40.

Site is in Supervisory state and is connected to BTS Manager as per the test case

setup described below.




1. Make a BTS Manager connection as per thetest case (local / remote).

See the BTS Manager connection columnbelow for more information.

BTS Manager is successfully connected tothe BTS.

2. Click the Supervision Æ RSSI ComparisonValues menu item.

RSSI Comparison Values dialog is displayed.

3. Click the RXDS button in the RSSIComparison Values dialog.

RXDS Value dialog is opened.

4. Check theCurrent value displayed in theRXDS value dialog.

It will either be 80,000, 160,000, 350,000 or750,000.

5. From the drop down menu of the New value combo box, select the RXDS value as definedin the test case. See the RXDS value columnbelow for more information.

Click the Set button.

Four values are available in the drop downmenu: 80,000, 160,000, 350,000 and750,000.

The RXDS parameter value is set and is

displayed in the Current value.

6. Close the RXDS value and RSSI ComparisonValues dialogs.

Both dialogs are closed.

7. Click the Click theSupervision Æ SiteInformation menu item.

Site Information dialog will be displayed.

8. Check that the RXDS parameter value ispresent in the site information.

Value of RXDS parameter is present in thesite information.



25 (56)





9. Close the BTS Manager connection andreconnect it as per the test case (local /

remote).

See the BTS Manager connection columnbelow for more information.

BTS Manager is successfully connected tothe BTS.

10. Check the current value of the RXDSparameter by repeating steps 2, 3 and 4.

The RXDS value is same as set in step 5.

Case Ref. BTS Configuration BTS Manager connection RXDS value

411605.09 2+2 Local 80,000

411605.10 4 TRX Omni with GPRS enabled Local 160,000

411605.11 Single sector with IDD enabled

(main TRX- 1&2, Aux. TRX- 3&4)

Local 350,000

411605.12 2+2 Local 750,000

411605.13 2+2 Remote (from local lab PC)with Full Access

80,000

411605.14 4 TRX Omni with GPRS enabled Remote (from local lab PC)with Full Access

160,000

411605.15 Single sector with IDD enabled(main TRX- 1&2, Aux. TRX- 3&4)

Remote (from Node Manager)with Full Access

350,000

411605.16 2+2 Remote (via NetAct TLUI)with Full Access

750,000

2.3.1.2 RSSI feature w.r.t. value of RXDS parameter

Purpose:

To verify that in RX Antenna Supervision by the RSSI feature, the BTS will

take samples from a TRX as ‘Reliable’ if the number of samples in the one-hour

period is greater than or equal to the value of RXDS parameter.

Note 41.

Site is in Supervisory state and the value of RXDS parameter is set as described

in the test case below.








Test cases


1. Site is reset.




2. Call(s) are made on the TRX(s) for the durationso that the number of samples per TRX in one-hour period is less than the value of RXDSparameter.


3. After 10 minutes of the call(s) being made, clickthe Supervision Æ RSSI Comparison Values menu item in BTS Manager to check RSSIresults.


Main and Diversity RX levels, TRX Branchdifference (this should be the differencebetween main and diversity antenna values)and RX Relative difference (only forUltraSite) values are displayed for all the TRXs on which call(s) are made.


4. Antenna supervisory timer expires after 1 hour.RSSI Results are checked from the BTSManager.

Raw and Newest values will be displayed forthe TRX(s) on which call(s) are made.

The Reliable table will be blank.

5. Increase the number of calls and their durationso that the number of samples per TRX in thenext one-hour period is equal to or greater than

the value of the RXDS parameter.

The new call(s) are successful.

6. Antenna supervisory timer expires again after 1hour. RSSI Results are checked again from BTSManager.

All values (Raw, Newest and Reliable) willbe displayed for the TRX(s) on which call(s)are made.

Case Ref. BTS Configuration RXDS Value

411609.05 2+2 80,000

411609.06 4 TRX Omni with GPRS enabled 160,000

411609.07 Single sector with IDD enabled (main TRX-1&2, Aux. TRX- 3&4) 350,000

411609.08 4 TRX Omni 750,000

2.3.1.3 Setting and Resetting of RSSI related alarms after RXDS implementation

Purpose:

To verify that even after implementation of the RXDS parameter, RSSI-related

alarms are raised in BTS Manager and the BSC, if ‘TRX Branch Difference’ is

greater than the RX Diversity Limit. Also to check that alarms will be cancelled

if the ‘TRX Branch Difference’ falls below the RX Diversity Limit.



27 (56)




Note 42.

Value of the RXDL parameter at the BSC is set as per the test case using the

following MML command:

ZEFM: <bcf no. >: RXDL=<val ue>;


Attenuation is provided when the site is in supervisory state, in the mentioned

antenna path (RX Main or RX Div.) as per the test case.


1. Site is reset.

BTS Manager is launched and connected to theBTS locally.



2. Calls are made on all the TRXs for the durationso that the number of samples per TRX in one-hour period is equal to or greater than the valueof RXDS parameter.






Test cases



Alarms are checked at the BSC and BTSManager.


RX antenna supervision is performed. RSSIResults can be requested from BTS

Manager.

BTS Manager displays ‘Raw’, ‘Newest’ and‘Reliable’ values. Main and diversity RXlevels, TRX Branch difference (this shouldbe the difference between main anddiversity antenna values) and RX Relativedifference (only for UltraSite) values aredisplayed for all TRXs.

For MetroSite test cases 411611.06 and411611.08:

TRX 1 & 2 of sector(s) in which attenuationis provided, reports RX Branch differencevalue greater than ‘RX Difference Limit’value set at the BSC. Alarm 7607 TRXOPERATION DEGRADED (Rx levels differtoo much between main and diversityantennas) is seen at the BSC and BTSManager for these TRXs.

For MetroSite test case 411611.05:

TRXs of sector in which attenuation is

provided, reports RX Branch differencevalue greater than ‘RX Difference Limit’value set at the BSC. Alarm 7604 BTSOPERATION DEGRADED (Rx levels differtoo much between main and diversityantennas) is seen at the BSC and BTSManager for this sector.

For MetroSite test case 411611.07:

All TRXs in sector reports RX Branchdifference value greater than ‘RX Difference

Limit’ value set at the BSC. Alarm 7601 BCFOPERATION DEGRADED (Rx levels differtoo much between main and diversityantennas) is seen at the BSC and BTSManager.

These alarms are also visible on the Abisinterface.

4. Calls are terminated. Calls are successfully terminated.



29 (56)





5. Attenuation provided in the mentioned path isremoved. Calls are again made on all the TRXs

for the duration such that the number of samplesper TRX in one-hour period is equal to or greaterthan the value of RXDS parameter.


6. Antenna supervisory timer again expires after 1hour. RSSI Results are checked from the BTSManager. Alarms are checked at the BSC andBTS Manager.


RX antenna supervision is performed. RSSIResults can be requested from BTSManager. BTS Manager displays ‘Raw’,‘Newest’ and ‘Reliable’ values.

Main and diversity RX levels, TRX Branchdifference (this should be the differencebetween main and diversity antenna values)values are displayed for all TRXs.

Alarms that were generated in Step 3 arecancelled at BSC as well as in BTSManager.

Cancellation of alarms is also visible on theAbis interface.

Case Ref. BTS Configuration RXDL Attenuation RXDS Value

411611.05 2+2 5 15db (RX Div.Path of TRX3 of sector-2)

80,000

411611.06 4 TRX Omni with GPRSenabled

15 20db (RX Mainpath of TRX1)

160,000

411611.07 Single sector with IDDenabled (main TRX-1&2,Aux. TRX- 3&4)

5 15db (RX Div.Path of TRX1)

350,000

411611.08 4 TRX Omni 10 20db (RX Mainpath of TRX3)

750,000

2.3.1.4 Default value of RXDS is used when the site is first commissioned

Purpose:

To verify that the default value of the RXDS parameter is set as 160,000 when

the site is first commissioned.

Note 43.

The site is in un-commissioned state.







Test cases


1. Commission the site. Site is successfully commissioned andcomes to Supervisory state.

2. Click the Supervision Æ RSSI ComparisonValues menu item of BTS Manager.

RSSI Comparison Values dialog will bedisplayed.

3. Click the RXDS button in the RSSI ComparisonValues dialog.


4. Check the current value displayed in the RXDSvalue dialog.

It will be 160,000.

5. Close the RXDS value and RSSI ComparisonValues dialogs.


6. Call(s) are made on the TRX(s) for the durationso that the number of samples per TRX in one-

hour period is equal to or greater than the valueof the RXDS parameter, that is, 160,000.


7. After 10 minutes of the call(s) being made, clickSupervision Æ RSSI Comparison Values menu item of BTS Manager to check RSSIresults.

RX antenna supervision is performed. Rawvalues are displayed on RSSI ComparisonValues Dialog.

Main and Diversity RX levels, TRX Branchdifference (this should be the differencebetween main and diversity antenna values)values are displayed for all the TRXs onwhich call(s) are made.

The ‘Newest’ and ‘Reliable’ tables are blank.


All (Raw, Newest and Reliable) values willbe displayed for the TRX(s) on which call(s)are made.

Case Ref. BTS Configuration

411739.02 MetroSite 2+2

2.3.1.5 Decommission ing of Site resets RXDS parameter

Purpose:

To verify that RXDS value is correctly set back to default value (160,000) when

the site is first decommissioned and then commissioned again.

Note 44.

Site has been set with RXDS limit of 350,000 and is in Supervisory state.





31 (56)





1. BTS Manager application is launched andconnected to the BTS locally.


2. Decommission the site. Site is decommissioned.

3. Commission the site again. Site is successfully commissioned and comes toSupervisory state.

4. Click the Supervision Æ RSSI ComparisonValues menu item of BTS Manager.

RSSI Comparison Values dialog will be displayed.


RXDS Value dialog is launched

6. Check the current value displayed in theRXDS Value dialog.

It will be 160,000.

7. Close the RXDS value and RSSIComparison Values dialogs. Both dialogs are closed.

Case Ref. Type of BTS BTS Configuration

411741.02 MetroSite 2+2

2.3.1.6 Non-Volat ile RXDS parameter on BCF reset from BSC

Purpose:

To verify that after a BCF reset is performed from the BSC, the value of the

RXDS parameter remains unchanged and RSSI samples are considered reliable

as per the RXDS value.




1. BTS Manager application is launched andconnected to BTS locally.

BTS Manager application is successfullyconnected to the BTS.

2. Click the Supervision Æ RSSIComparison Values menu item of BTS

Manager.





It will be same as mentioned in the test case.

5. Close the RXDS value and RSSIComparison Values dialogs.






Test cases


6. Reset the BCF from the BSC with thefollowing command:

ZEFR: <BCF Number >: ;

Site is reset and comes to Supervisory state.

7. Click the Supervision Æ RSSIComparison Values menu item of BTSManager.








11. Call(s) are made on the TRX(s) for theduration so that the number of samples per TRX in one-hour period is equal to orgreater than the value of RXDS parameteras mentioned in the test case.


12. After 10 minutes of the call(s) being made,click the Supervision Æ RSSIComparison Values menu item of BTSManager to check RSSI results.

RX antenna supervision is performed. Rawvalues are displayed on RSSI Comparison ValuesDialog. Main and Diversity RX levels, TRX Branchdifference (this should be the difference betweenmain and diversity antenna values) values aredisplayed for all the TRXs on which call(s) aremade.


13. Antenna supervisory timer expires after 1hour. RSSI Results are checked from BTSManager.

All (Raw, Newest and Reliable) values will bedisplayed for the TRX(s) on which call(s) aremade.

Case Ref. Type of BTS BTS Configuration RXDS

411742.02 MetroSite 4+4 (2 cabinets in chain) 80,000

2.3.1.7 Non-Volat ile RXDS parameter on BCF reset from BTS Manager

Purpose:

To verify that after a BCF reset is performed from BTS Manager, the value of the RXDS parameter remains unchanged and RSSI samples are considered

reliable as per the RXDS value.





33 (56)















6. Click the Object Æ Properties menu item

of BTS Manager.

Object Properties dialog will be displayed.

7. Select BCF in the Object Properties dialogand click the Reset button. Click OK on theconfirmation dialog.

Site is reset and comes to Supervisory state.





10. Check the current value displayed in the

RXDS Value dialog.




12. Call(s) are made on the TRX(s) for theduration such that the number of samplesper TRX in one-hour period is equal to orgreater than the value of RXDS parameteras mentioned in the test case.




The ‘Newest’ table shows ‘N/A’ for all these fieldsand the ‘Reliable’ table is blank.

14. Antenna supervisory timer expires after 1hour. RSSI Results are checked from theBTS Manager.

Now, all (Raw, Newest and Reliable) values willbe displayed for the TRX(s) on which call(s) aremade.





Test cases



411744.02 MetroSite 4 TRX Omni 350,000

2.3.1.8 Non-Volatile RXDS parameter on BTS reset from BSC

Purpose:

To verify that after a BTS reset is performed from the BSC, value of RXDS

parameter remains unchanged and RSSI samples are considered reliable as per

the RXDS value.














6. Reset the BTS(s) (both in case of MetroSite) by locking and unlocking it fromthe BSC.

BTS(s) are reset and come to Working state.



8. Click the RXDS button in the RSSI

Comparison Values dialog.








35 (56)





11. Call(s) are made on the TRX(s) for theduration such that the number of samples

per TRX in one-hour period is equal to orgreater than the value of RXDS parameteras mentioned in the test case.








411746.02 MetroSite 2+2 750,000

2.3.1.9 Non-Volat ile RXDS parameter on BTS reset from BTS Manager

Purpose:

To verify that after a BTS reset is performed from BTS Manager, the value of

the RXDS parameter remains unchanged and RSSI samples are considered







2. Click the Supervision Æ RSSI

Comparison Values menu item of BTSManager.












Test cases


6. Click on theObject Æ Properties menuitem of BTS Manager.


7. Select Sector in the Object Propertiesdialog and click Reset.

Click OK in the confirmation dialog.

The sector is reset and comes to Working state.












RX antenna supervision is performed. Rawvalues are displayed on RSSI Comparison ValuesDialog. Main and Diversity RX levels, TRX Branchdifference (this should be the difference between

main and diversity antenna values) values aredisplayed for all the TRXs on which call(s) aremade.

The ‘Newest’ table shows ‘N/A’ for all these fieldsand the ‘Reliable’ table is blank.




411749.02 MetroSite 4 TRX Omni with EGPRS enabled 80,000

2.3.1.10 Non-Volatile RXDS parameter on OMU block/unblock

Purpose:

To verify that after an OMU link is blocked/unblocked from the BSC, the value

of the RXDS parameter remains unchanged and RSSI samples are considered






37 (56)







2. Site is reset. Site comes to Supervisory state.









7. Block the OMU link from the BSC usingMML command ZDTC.

OMU link is blocked.

8. Unblock the OMU link from the BSC usingMML command ZDTC.

OMU link is unblocked and comes to Workingstate.



10. Click theRXDS button in the RSSIComparison Values dialog.


11. Check the current value displayed in the

RXDS Value dialog.






14. After 10 minutes of the call(s) being made,click Supervision Æ RSSI ComparisonValues menu item of BTS Manager to

check RSSI results.

RX antenna supervision is performed. Rawvalues are displayed on RSSI Comparison ValuesDialog. Main and Diversity RX levels, TRX Branch

difference (this should be the difference betweenmain and diversity antenna values) values aredisplayed for all the TRXs on which call(s) aremade.









Test cases


411906.01 MetroSite 2+2 80,000

2.3.1.11 Non-Volat ile RXDS parameter on TRX reset from BSC

Purpose:

To verify that after a TRX reset is performed from the BSC, the value of the

RXDS parameter remains unchanged and RSSI samples are considered reliable

as per the RXDS value.












5. Close the RXDS value and RSSI

Comparison Values dialogs.


6. Reset any TRX of the BCF by locking andunlocking it from the BSC.

TRX is reset and comes to Working state.













39 (56)





12. After 10 minutes of the call(s) being made,click the Supervision Æ RSSI

Comparison Values menu item of BTSManager to check RSSI results.

RX antenna supervision is performed. Rawvalues are displayed on RSSI Comparison Values

Dialog. Main and Diversity RX levels, TRX Branchdifference (this should be the difference betweenmain and diversity antenna values) values aredisplayed for all the TRXs on which call(s) aremade.

The ‘Newest’ table shows ‘N/A’ for all these fieldsand ‘Reliable’ table is blank.





2.3.1.12 Non-Volat ile RXDS parameter on TRX reset from BTS Manager

Purpose:

To verify that after a TRX reset is performed from BTS Manager, the value of

the RXDS parameter remains unchanged and RSSI samples are considered















6. Click on theObject Æ Properties menuitem of BTS Manager.






Test cases


7. Select any TRX in the Object Propertiesdialog and click the Reset button.

Click OK in the confirmation dialog.

TRX is reset and comes to Working state.

















411765.02 MetroSite Single sector with IDD enabled (Main TRX –1&2, Aux. TRX – 3&4)

750,000

2.3.1.13 Non-Volatile RXDS parameter on power reset

Purpose:

To verify that after a power reset is performed, the value of the RXDS

parameter remains unchanged and RSSI samples are considered reliable as per

the RXDS value.





41 (56)





1. BTS Manager application is launched andconnected to BTS locally. BTS Manager application is successfullyconnected to the BTS.









6. Give a power reset to the site. Site is reset and comes to Supervisory state.


















750,000





Test cases

2.3.1.14 Non-Volatile RXDS parameter on BTS reconfiguration

Purpose:

To verify that after a BTS reconfiguration is performed, the value of the RXDS

parameter remains unchanged and RSSI samples are considered reliable as per the RXDS value.














6. Remove any one TRX from the working site

and verify that the site goes forreconfiguration.

Check for ‘BTS Conf Data’ on the Abistraces.

Site goes for reconfiguration and comes to

Supervisory state with only 3 TRXs.‘BTS Conf Data’ is visible on the Abis traces.













43 (56)













411775.02 MetroSite 4 TRX Omni with BB Hopping 80,000

2.3.1.15 Non-Volatile RXDS parameter on software upgrade

Purpose:

To verify that after the downloading and activation of new BTS software is

performed from the BSC, the value of the RXDS parameter remains unchanged

and RSSI samples are considered reliable as per the RXDS value.


As described in the test case below.












6. Download BTS software to the BCF fromthe BSC with MML command ZEWA.

Software is downloaded successfully.





Test cases


7. Activate the newly downloaded BTSsoftware from the BSC with MML command

ZEWV.

Site is reset and comes to Supervisory state withBTS software.


















350,000

2.3.1.16 Non-Volatile RXDS parameter on Abis break fault

Purpose:

To verify that after the BCF has been reset due to a fault (Abis break), the value

of the RXDS parameter remains unchanged and RSSI samples are considered



As described in the test case below.



45 (56)















6. Disconnect the Abis cable between the

BSC and BTS.

Alarms 7767 BCCH MISSING and 7704:PCM

FAILURE can be seen at the BSC.

Alarm 8050 LOSS OF INCOMING 2M SIGNALcan be seen at BTS Manager.

7. Reconnect the Abis cable between theBSC and BTS.

BCF is initialised and returns to Operational state. The alarms are cancelled.




















Test cases


14. Antenna supervisory timer expires after 1hour. RSSI Results are checked from the

BTS Manager.

Now, all (Raw, Newest and Reliable) values willbe displayed for the TRX(s) on which call(s) are

made.



2.3.1.17 RSSI not performed with RDIV disabled

Purpose:

To verify that even with the implementation of the RXDS parameter, RSSI is

not performed when RDIV is disabled.

Note 45.

RX Diversity is set OFF for the sector in the BSC.

Note 46.

All the required diversity cables are properly connected.




1. Site is reset.






3. After 10 minutes of the call(s) being made,

click the Supervision Æ

RSSIComparison Values menu item of BTSManager to check RSSI results.

All the three output tables (Newest, Reliable and

Raw) in the RSSI Comparison Values dialog areempty.


All the three output tables (Newest, Reliable andRaw) in the “RSSI Comparison Values” dialog arestill empty.

This indicates that RSSI is not performed evenwhen the physical diversity path is present but RXdiversity is not defined in the BSC.



47 (56)







2.3.1.18 Backward compatibility with old BTS software

Purpose:

To verify that when CX(M)5 SW is in use, then old BTS SW [CX(M)4.1] can

be downloaded and activated. Also to verify that this disables the RXDS button

in the RSSI Comparison Values dialog of BTS Manager, and RSSI samples are

considered reliable as per the sample value of CX(M)4.1 (that is, 160,000).






2. Download CX(M)4.1 SW to the BCF fromthe BSC with MML command ZEWA.

Software is downloaded successfully

3. Activate the newly downloaded CX(M)4.1software from the BSC with MML commandZEWV.

Site is reset and comes to Supervisory state withCX(M)4.1 software.





6. Close the RSSI Comparison Values dialog. RSSI Comparison Values dialog is closed.

7. Call(s) are made on the TRX(s) for theduration such that the number of samplesper TRX in one-hour period is equal to orgreater than 160,000 but less than thevalue of the RXDS parameter as defined inthe test case.






Test cases


8. Antenna supervisory timer expires after 1hour.

RSSI Results are checked from BTSManager by clicking the Supervision Æ RSSI Comparison Values menu item.

RX antenna supervision is performed. ‘Newest’and ‘Reliable’ values are displayed on the RSSI

Comparison Values dialog. Main and Diversity RXlevels, TRX Branch difference (this should be thedifference between main and diversity antennavalues) values are displayed for all the TRXs onwhich call(s) are made.

Raw table will display the following message:“Raw RSSI values are not supported with thecurrent version of BTS SW.”


411828.02 MetroSite 2+2 350,000

2.3.1.19 Forward compatibil ity of CX(M)4.1 with CX(M)5 BTS sof tware

Purpose:

To verify that when CX(M)4.1 SW is in use, then new BTS SW [CX(M)5] can

be downloaded and activated. Also to verify that this enables the RXDS button

in the RSSI Comparison Values dialog of BTS Manager, and RSSI samples are

considered reliable as per the newly implemented RXDS value.

Note 47.

This value for RXDS (160,000) would depend on the BTS not previously

having a CX(M)5 software loaded/activated and a different RXDS value being

set. (CX(M)4.1 does not read from flash for RXDS value but a non-default

RXDS value could reside in flash and this value would be read when CX(M)5 is

loaded.)


CX(M)4.1 software is the active software on the BCF and CX(M)5 software is

not attached to the BCF at the BSC.

CX(M)5 BTS Manager software is in use.


1. Bring the site to Supervisory state withCX(M)4.1 BTS software.




3. Download CX(M)5 SW to the BCF from theBSC with MML command ZEWA.

Software is downloaded successfully.



49 (56)





4. Activate the newly downloaded CX(M)5software from the BSC with MML command

ZEWV.

Site is reset and comes to Supervisory state withCX(M)5 software.



6. Check the RXDS button in the RSSIComparison Values dialog.

RXDS button is enabled.

7. Click the RXDS button and check the‘current value’ displayed in the RXDS valuedialog.

RXDS value dialog is opened and the ‘currentvalue’ is displayed as 160,000.

8. From the drop down menu of the New

value combo box, select the RXDS valueas defined in the test case and click Set.

RXDS value is set as mentioned in the test case

and is displayed in ‘current value’.



10. Call(s) are made on the TRX(s) for theduration such that the number of samplesper TRX in one hour period is equal to orgreater than value of the RXDS parameteras defined in the test case but less than160,000.





12. Antenna supervisory timer expires after 1hour. RSSI Results are checked from BTSManager.



411836.02 MetroSite 2+2 80,000

2.3.1.20 Backward compatibil ity with old BTS Manager sof tware

Purpose:

To verify that an older version [CX(M)4.1] of BTS Manager does not affect

RSSI functionality with the latest version of BTS software.





Test cases

Note 48.





1. BTS Manager application [CX(M)5] islaunched and connected to BTS locally.


2. Set the value of the ‘RXDS’ parameter asmentioned in the test case, in RXDS Valuedialog.

The RXDS value is set as mentioned in the testcase and is displayed in ‘current value’.

3. Close the BTS Manager application. BTS Manager application is closed.

4. Install CX(M)4.1 version of BTS Manageron the PC.

CX(M)4.1 version of BTS Manager is installedsuccessfully.

5. Launch CX(M)4.1 version of BTS Managerand connect to the BTS locally.

BTS Manager application is successfullyconnected to the BTS



7. Verify that there is no RXDS buttonavailable in the RSSI Comparison Values

dialog.

The RXDS button is not available.

8. Close the RSSI Comparison Values dialog. RSSI Comparison Values dialog is closed.

9. Reset the site from the BSC. Site is reset and comes back to Supervisorystate.

10. Call(s) are made on the TRX(s) for theduration such that the number of samplesper TRX in one-hour period is equal to orgreater than the value of the RXDSparameter as mentioned in the test casebut less than 160,000.


11. Antenna supervisory timer expires after 1hour.

RSSI Results are checked from the BTSManager by clicking the Supervision Æ RSSI Comparison Values menu item.

RX antenna supervision is performed. Newestand Reliable values are displayed on the RSSIComparison Values dialog. Main and Diversity RXlevels, TRX Branch difference (this should be thedifference between main and diversity antennavalues) values are displayed for all the TRXs onwhich call(s) are made.

There is no Raw table available in the RSSIComparison Values dialog.




51 (56)





411846.02 MetroSite 2+2 80,000

2.3.1.21 Unable to set RXDS parameter on Remote BTS Manager wi th read-only access

Purpose:

The purpose of this test case is to verify that the SET button in the RXDS Value

dialog box is disabled in case of remote BTS Manager connection, with read-

only access.




1. Make a Remote BTS Manager connectionwith read-only access, to the BTS.

Remote BTS Manager is successfully connectedto the BTS.






4. Check the SET button in the RXDS Valuedialog.

The SET button is disabled.


411851.02 MetroSite 4 TRX Omni

2.3.1.22 Unable to set RXDS parameter when site is not in Supervisory state

Purpose:

To verify that the value of the RXDS parameter cannot be set if the site is not in

the Supervisory state.










Test cases


2. Reset the site. Site is being reset.

3. When the site is being reset, click theSupervision Æ RSSI Comparison Values menu item.

RSSI Comparison Values dialog is displayed



5. From the drop-down menu of the Newvalue combo box, select any RXDS valueother than the ‘current value’ and click theSet button.

A pop-up appears stating that ‘Setting RXDSvalue failed. Invalid BTS state’.

‘Current value’ of RXDS is not changed.


411859.02 MetroSite 2+2

2.3.1.23 Help for RXDS

Purpose:

To verify the contents of the help for RXDS button added in the RSSI

comparison values and RXDS Value dialogs.




1. BTS Manager application is launched andconnection is made to the BTS locally.

BTS Manager is successfully connected to theBTS.

2. Click on Supervision Æ RSSIComparison Values menu item.


3. Click the Help button or press F1. The Online Help dialog opens up and it containsinformation regarding the RXDS button.

4. Close Online Help dialog. Online Help dialog is closed.




6. Press F1. Online Help for RXDS Value dialog is launched,describing this dialog box and all the fields in it.

7. Close the Online Help dialog. Online Help dialog is closed.


411867.02 MetroSite 4 TRX Omni



53 (56)




2.3.1.24 Runtime change of RXDS parameter

Purpose:

To verify that the value of the RXDS parameter can be changed during ongoing

calls, and samples from a TRX will be considered as reliable if the number of samples in the one-hour period is greater than or equal to the new value of the

RXDS parameter.

Note 49.

Site is in Supervisory state and the value of RXDS parameter is set as 750,000.






2. Reset the site. Site comes to Supervisory state.

3. Call(s) are made on the TRX(s) for theduration such that the number of samplesper TRX in one hour period is equal to orgreater than the value of the RXDSparameter as mentioned in the test case

(80,000) but less than 750,000 (currentvalue of RXDS).





5. Click the RXDS button and check the‘current value’ displayed in the RXDS valuedialog.

RXDS value dialog is launched and the ‘currentvalue’ displayed is 750,000.

6. From the drop-down menu of the Newvalue combo box, select the RXDS valueas mentioned in the test case (80,000) andclick the Set button.

RXDS value is set as mentioned in the test case(80,000) and is displayed in ‘current value’ of theRXDS value dialog.







Test cases


8. Antenna supervisory timer expires after 1hour. RSSI Results are checked from BTS

Manager.

Now, all (Raw, Newest and Reliable) values willbe displayed for the TRX(s) on which call(s) are

made.

Case Ref. Type of BTS BTS Configuration New RXDS value




55 (56)




References

1. Test Specification for Customer Change Requests of BTS SW Release

CX5, dn0691159, issue 1-0.

2. Alarm Descriptions, dn04195989, issue 3-0.

3. Feature Descriptions for Nokia MetroSite EDGE Base Station,

dn04196267, issue 4-0.

customer change requests dn0698004x1x0xen

Documents