functional regression dn0691353x1x0xen

7/27/2019 Functional Regression DN0691353x1x0xen

http://slidepdf.com/reader/full/functional-regression-dn0691353x1x0xen 1/121

Nokia MetroSite EDGE Base Station

Functional Regression TestSpecification for BTS SW

Release CXM5

DN0691353Issue 1-0 en

©Nokia CorporationNokia Proprietary and Confidential

1 (121)



Functional Regression Test Specification for 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 (121) ©Nokia CorporationNokia Proprietary and Confidential




Contents

Contents

1 Vocabulary ..............................................................................................5

2 About this document .............................................................................7 2.1 Scope.......................................................................................................7 2.2 Prerequisites ..........................................................................................10 2.3 Hardware requirements..........................................................................10 2.4 Software requirements ...........................................................................12 2.5 Specialist test equipment requirements .................................................12

3 BTS commissioning and sof tware download....................................14 3.1 Direct SW download during commissioning...........................................14 3.2 Direct SW downloading from the BSC to the BCF .................................15 3.3 BTS commissioning from BTS Manager................................................17 3.3.1 Direct SW Download during commissioning..........................................17 3.3.2 BTS Commissioning from BTS Manager with EDAP configured ...........18 3.4 Background SW download to the BCF from BSC ..................................20 3.5 BTS SW download from BTS Manager to the BCF................................21 3.6 BTS SW package background downloading and activation

(mass operation)....................................................................................22

4 Manual configuration change .............................................................25 4.1 Adding new TRXs...................................................................................25 4.2 Site expansion........................................................................................26 4.3 Hot-insert TRX for chain configuration...................................................27

5 BTS tests...............................................................................................29 5.1 TRX tests ...............................................................................................29 5.1.1 Autonomous TRX tests ..........................................................................35 5.2 Abis loop test..........................................................................................35

6 Object control .......................................................................................38 6.1 TRX lock/unlock and block/unblock........................................................38 6.2 BCCH reconfiguration............................................................................40 6.3 BTS lock/unlock and block/unblock........................................................42 6.4 BCF lock and unlock..............................................................................45 6.5 BCF reset...............................................................................................46

7 Intelligent Coverage Enhancement ....................................................48 7.1 Intelligent Coverage Enhancement - Plus..............................................48

8 Intelligent Shutdown for MetroSite.....................................................49 8.1 All shutdown mode.................................................................................52 8.2 BCCH shutdown mode...........................................................................53 8.3 None shutdown mode............................................................................57 8.4 BCF lock/unlock from the BSC...............................................................61



3 (121)




8.5 BTS lock/unlock from the BSC .............................................................. 62 8.6 TRX lock/unlock from the BSC ..............................................................64 8.7 Site reset from BSC and BTS Manager................................................. 65 8.8 BCF block/unblock from BTS Manager................................................. 68

8.9 BTS block/unblock from the BTS Manager ........................................... 70 8.10 TRX block/unblock from the BTS Manager...........................................72 8.11 BTS reset from BTS Manager............................................................... 73 8.12 TRX reset from BTS Manager............................................................... 75

9 Recovery for BSS and Site Synchronisation .................................... 77 9.1 Site synchronisation recovery during start-up/resets............................. 77 9.2 Site synchronisation recovery with GPS signal recovery...................... 80

10 BTS Manager functionality ................................................................. 87 10.1 BTS Manager start-up........................................................................... 87

10.2 Access rights in local mode................................................................... 88 10.3 BTS SW menu commands.................................................................... 91 10.4 BTS manual commissioning.................................................................. 93 10.5 Enabling and disabling of Abis .............................................................. 98 10.6 Adjusting the DAC word ...................................................................... 100 10.7 FC E1/T1, FXC E1 and FXC E1/T1 transmission menus....................100 10.8 FXC RRI transmission menus ............................................................. 102 10.9 Window menu commands................................................................... 104 10.10 BTS Manual Commissioning with FXC RRI ........................................ 105

11 Remote BTS Manager ....................................................................... 109 11.1 Remote BTS Manager start-up............................................................ 109

11.2 Access rights in case of Remote connection....................................... 111

12 Improved TRX Test Presentation ..................................................... 114 12.1 Improved TRX Test Presentation in the TRX Test Report .................. 114 12.1.1 Improved TRX Test Presentation in the TRX Test Report when

TRX Test is executed from BTS Manager........................................... 114 12.1.2 Improved TRX Test Presentation in the TRX Test Report when

TRX Test is executed from Remote BTS Manager............................. 115 12.1.3 Improved TRX Test Presentation in the interrupted TRX Test

Report.................................................................................................. 117 12.2 Changed Information in Online Help menu......................................... 118 12.3 Changed Information in BTS Commissioning Report.......................... 119

References ......................................................................................... 121





Vocabulary

1 Vocabulary The following abbreviations are specific to this document.

BBU Battery Backup Unit

BCF Base Control Function

BSC Base Station Controller

BTS Base Transceiver Station

DFCA Dynamic Frequency and Channel Allocation

EDGE Enhanced Data Rates for GSM Evolution

EFR Enhanced Full Rate

EGPRS Extended GPRS

FR Full Rate

FTP File Transfer Protocol

GMSK Gaussian Minimum Shift Keying

GPRS General Packet Radio Service

GSM Global System for Mobile Communication

HR Half Rate

HW Hardware

ICE+ Intelligent Coverage Enhancement - Plus

IR/LA Incremental Redundancy/Link Adaptation.

ITN Integrated Transmission Node

IUO Intelligent Underlay Overlay

LCS Location Service

LMU Location Management Unit

MCS Modulation Coding Scheme

MMI Man Machine interface

NEE Network Element Emulator



5 (121)




PSK Phase Shift Keying

RF TA Radio Frequency Timing Advance Rigs

SW Software

TCH Traffic Channel

TRX Transceiver

UALC User Access Level Control

UDP User Datagram Protocol





About this document

2 About this document 2.1 Scope

This document defines the library of test cases in order to verify the functional

features of BTS software release CXM5 for Nokia MetroSite Base Station.

In general, the features and test cases described herein are intended for Nokia

GSM 800, 900, 1800 and 1900 environments.

Note 1

The BSC version to be used is S12, SiteWizard version to be used is SiteWizard

5.0, and GCS version to be used is R5.0 unless otherwise specified.

Note 2

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

Note 3

In this section, references to S11.5 mean any S11.5 generation BSC software

package. The latest package and Change Delivery (CD) under test should be

used. References to S11 mean any S11 generation BSC software package. The

latest package and CD in general use should be used.

Note 4

At the BSC, Base Transceiver Stations (sites) are seen as BCFs. Sectors are

referred to as BTS. This principle is followed in the test descriptions in this

document.



7 (121)




Note 5

The Master TRX operates with BTS O&M and Telecom functions. The Slave

TRX operates with Telecom functions only.

Master TRX is always located in slot 1 and Slave TRXs in slots 2 and 4.

Both the Master TRX and Slave TRX can be the BCCH TRX or NON BCCH

TRX.

In Nokia MetroSite BTS, the Master TRX is by default not a BCCH TRX

unless it is defined as the preferred BCCH TRX.

Note 6

A multi TRX configuration is a site having several TRXs, for example 2+2

TRXs, 4 TRXs, and so on.

A 1-TRX configuration is a site having one TRX unit (Master TRX).

Note 7

Unless otherwise stated specifically, the signalling speed mentioned is for

TRXSIG. Such test cases will be distributed among O&M signalling speed of

16, 32 & 64 kbps.

Note 8

• VTxA: CATS, 1 W TRX for GSM 900, 1800 and 1900 bands

• HVTx: HPCATS, 5W TRX for GSM 900, 1800 and 1900 bands

• WTxA: ECATS, 5W TRX for EDGE 800 and 1900 bands

• CTxA: XPCATS, 10 W EDGE TRX for GSM 900 and 1800 bands

• VSxx: Low Power Supply unit

• HVSx/CVSx: High Power Supply unit

• HVMF: High Power Fan unit

• VMFA: Low Power Fan unit.





About this document

Note 9

The following HW configurations are used during testing:

•

GSM (VTxA, HVTx)• EDGE (WTxA, CTxA)

• GSM/EDGE (HVTx +WTxA or HVTx +CTxA in the same cabinet)

A cabinet can be configured as a dual band BCF, which can use GSM 800 +

1900 bands, or GSM 900 + 1800 bands. Each sector had to be configured with

the same band TRXs.

Note 10

Maximum number of MetroSite cabinets combined is three.

Chain Master TRX must be the HVTx/CTxA located in position 1 at the firstcabinet in line called the Master cabinet. Cabinet Master TRXs are the

HVTx/CTxA located in position 1 (logical TRX # 5 and 9) at the second and

third cabinets in line called slave cabinets.

Nokia Site Manager connection can be established at any one of the cabinets;

however, it is recommended to connect only to the Chain Master cabinet. Only

one Nokia Site Manager can be connected at the same time.

Note 11

A invalid BB Hopping configuration exists in a sector having TRXs of different

power types in the same hopping group, that is, GSM/EDGE HVTx (5W) +CTxA (10W) in the same BTS.

Note 12

All test cases must be performed with RX diversity enabled at the BSC unless

otherwise stated.

Note 13

A TRX test can be configured to test one or more radio time slots that are

configured for GPRS. If started, such a test will be allowed to proceed by the

BTS SW, and this is likely to cause the following behaviour for the radio time

slots:

• PCU synchronisation failure (and then re-synchronisation),

• Adverse effects to GPRS data call active on GPRS-configured radio timeslots.

Therefore, it is recommended that GPRS-configured radio time slots are not

selected for the TRX test.



9 (121)




Note 14

During the installation and commissioning of sites, help provided by ‘Help

Menu’ commands in BTS Manager should be used.

Note 15

It should be made a testing practice to use help provided in the BTS Manager

from the Help Menu or using the help button (F1).

Note 16

While testing Multi BCF with DF 6.0-3, at a S11 BSC, the SENA for master

BCF should be ‘F’ while for DF7 it should be ‘T’.

Note 17

GTRX=N for GSM TRXs in EDGE/GSM configuration, if EGENA need to be

enabled.

2.2 Prerequisites

Before the release testing can begin, there must not be any open fatal or major

faults found from the ongoing SW integration testing phases.

2.3 Hardware requirements

Base stations One of the following BTS configurations will be used for the test cases covered in this document:

• 2+2 GSM/EDGE

• 2+2 EDGE

• 2+2 GSM

• 4 Omni GSM/EDGE

• 4 Omni EDGE





About this document

• Multi TRX EDGE

• Multi TRX GSM

• 2+2 GSM+EDGE

• 1+1+1+1

• 2 GSM

• 1 TRX

• 4 Omni GSM

• Multi TRX GSM/EDGE

• 4+4+4 EDGE- Chained Configuration

• 4+4+4 GSM+EDGE+GSM/EDGE- Chained Configuration

• 4+4+4 GSM- Chained Configuration

• Talk-MetroSite

• LMU-MetroSite-MetroSite

• Talk-MetroSite-MetroSite

• LMU-Talk-MetroSite

Other Network Elements

• BSC

• Core Network with GPRS and EDGE capabilities

Mobile Stations

Feature Specific options

Speech channels FR, HR, EFR

Single data channels 9600, 14400 Non-Transparent

Multislot data channels 9600 or 14400 Non-Transparent using 1+1, 2+2 or 3+1 timeslots

GPRS Class B & Class C, Multi, PBCCH Support

EGPRS Class B & Class C, Multi, PBCCH Support

EGPRS Channel Request on PBCCH and BCCH

Adaptive Multi-Rate AMR FR and HR

General SMS, Mobile Originating (MO) & Mobile Terminating (MT)

Enhanced MeasurementReports

EMR Capable



11 (121)




2.4 Software requirements

• SiteWizard5.0

• Latest available Test Packet or Pre-Release of CXM5

• GCS R5.0

• SW versions of the other network elements are detailed in Table 1

Table 1: SW Versions of Other Network Elements

Network Element SW Version

BSC S11, S11.5, S12

Nokia NetAct OSS 3.1 ED3LMU FLY4.4, MIDGE1.0

SGSN SG3.1, SG4.0

Transmission (FXC E1, FXC E1/T1,FXC RRI, FC STM-1)

ITN C1.0, ITN C2.1-2, ITN C2.2, ITN C3.0

Transmission (FC E1/T1) ITN C1.0

Transmission (MetroHub) MHB C2.1, C2.2, C3.0

BTS Manager PC Windows 98, Windows 2000, Windows XP

PC Applications

• Internet browser

• FTP, UDP software

• Terminal Emulator

2.5 Specialist test equipment requirements

The following test equipment is required in some test cases:

• Traffic generator, preferably load tester

• 8PSK and GMSK capable RF TA rigs

• IR/LA rig

• Assortment of combiners

• Attenuators





About this document

• Terminators

• Signal generator

• Spectrum analyser

• GSM Protocol Analyser

• Data channel simulator

• D-bus analyser

• Q1 monitor/NEE

• Abis breaker



13 (121)




3 BTS commissioning and softwaredownload

3.1 Direct SW download during commissioning

Purpose:

To check that SW can be successfully downloaded directly from the BSC

during the commissioning of the site, and the site comes up in working state

with the requested SW version.

Input Expected Output

HW is installed in MetroSite. Configure the OMU

and FU links, BCF, BTS(s), TRX(s) at the BSCaccording to given configuration. CXM5 is not inthe flash.

Each BTS has required number of TRXs. The

OMU and FU state is in BL-SYS state. The BCFis in locked state.

CXM5 is attached to the BCF and then it isactivated. Execute all FU links and OMU link inWO state using MML commands

ZDTC: <FU no. / OMU>: WO;

Unlock all TRXs, BTSs and BCF at the BSC usingZERS, ZEQS and ZEFS MML commandsrespectively.

BCF unlock is not allowed as the OMU is not inworking state.

All TRXs and BTSs are unlocked successfully.

Commission the site using the BTS Manager.

Monitor the SW downloading on Abis.

The service terminal extension (using ZDDS;),RPHASESX (ZLE:P,RPHASESX) is used tomonitor the process of SW downloading of theBCF.

The OMU link comes to working state.

Unlock the BCF at the BSC. The BCF is unlocked and after reset comes tooperational state.





BTS commissioning and software download

Check the SW version using MML commandZEWO.

Requested SW, CXM5, is active.

Set up voice calls on all TRXs. Monitor the Abis. The call is set up. Values for RX Quality in both

uplink and downlink, and the UL FER shall inlaboratory conditions be predominately of value 0.

Terminate calls. All calls are terminated successfully. Releasecause is normal.

Case Ref. Configuration

1 2+2 EDGE/GSM

2 4 Omni EDGEBSC S11.5

3.2 Direct SW downloading from the BSC to the BCF

The purpose of these test cases is to verify that the SW package can be

downloaded directly from the BSC to the BCF and be activated successfully.

Extra HW/tools: D-bus analyser.


The BCF is operational (BCF is in WO state). Setup a call in the BCF.

The call is successful

BTS SW packages have been installed at theBSC. The BTS SW to be activated is attached tothe BCF(s) without being backgrounddownloaded.

Monitor the SW downloading from the BSC to theBCF on Abis. The D-Bus Analyser is used tomonitor the SW downloading from the ChainMaster TRX (TRX in position 1) to the Slave TRX(s). The service terminal extension (usingZDDS;), RPHASESX (ZLE:P,RPHASESX) isused to monitor the process of SW downloadingof the BCF.

Attach the latest UltraSite SW to the BCF. DX error BTS SITE TYPE AND BCF BUILD TYPEARE MISMATCHED can be seen at the BSC. Alsoin that case SW downloading is not started.

Block the OMU link.

Attach the BTS SW to be tested using the MMLcommand ‘ZEWA:

The BSC indicates that the BTS SW cannot beattached due to O&M link failure.



15 (121)





The MML command ‘ZEWO’ is used at the BSCto check the attached BTS SW to the BCF.

Correct BTS SW package is attached to the BCF atthe BSC.

The OMU link is unblocked, and then the MMLcommand ‘ZEWV:’ is issued.

One Slave BCCH TRX is removed and thenreinserted. SW downloading is monitored.

The command first resets the BCF and then loadsthe SW.

Slave BCCH TRX is detected, it does not disturbthe downloading.

The downloading is successful. Downloaded SW issaved to the Master TRX flash memory (non-volatile memory).

The BCF is initialised and comes to working statewith all TRXs.

Verify the end state. The end state is the same as specified in the test

case. The Active SW and SW in Newest Flash memoryare same.

Calls are made via every TRX. All calls are successful.

CaseRef.

Configuration Active SW andFlash Contents atthe Beginning

Additional Act ion End State Signallingspeed

1 2+2 EDGE/GSM Active-CXM4.1CD1.0

Flash-

CXM4.1CD1.0 andCXM4.1

Download CXM5,During SWdownload, reset theslave BCCH TRXlocally using BTSManager

Active-CXM5

Flash-CXM5 andCXM4.1CD1.0

16 kbps

2 3 Site chain, Multi TRXEDGE+GSM+EDGE/GSM

Active-CXM5

Flash-CXM5 andCXM4.1

Download CXM4.1CD1.0

Active-CXM4.1CD1.0

Flash-CXM4.1CD1.0 and CXM5

64 kbps

3 Multi TRX EDGE Active-CXM4.1

Flash-CXM4.1 andCXM4.1CD1.0

Download CXM5 Active-CXM5

Flash-CXM5 andCXM4.1

32 kbps






3.3 BTS commissioning from BTS Manager

3.3.1 Direct SW Download during commissioning

Purpose:

To check that SW can be downloaded directly from the BSC during the

commissioning of site successfully, and the BTS Site comes up in working state

with the requested SW version.

Equipment and BTS Set-Up

BTS is in uncommissioned state.


Create the BTS Site at the BSC as described inthe test case.

Put all FU links and OMU link in WO state usingMML commands


Unlock all TRXs and BTS

OMU and FU link state is in BL-SYS state.

The BTS and its TRXs are unlocked

Attach the BTS SW under test to the BCF usingMML command ZEWA.

Activate the attached BTS SW using MMLcommand ZEWV.

SW attach denied due to ‘O&M Link State’.

SW activation denied due to BCF ‘AdministrativeState’.

Launch the BTS Manager and connect to theBTS.

The BTS Manager is launched and connected tothe BTS successfully.

Commission the BTS Site using the BTSManager.

While configuring the Traffic Manager, defineEDAP (Multiple TSs) as defined in the test case.Click on the OK button to save these settings.

Monitor the SW downloading on Abis. The service terminal extension (using ZDDS;),RPHASESX (ZLE:P,RPHASESX) is used tomonitor the process of SW downloading of theBCF.

The Traffic Manager window gets closed andcommissioning proceeds.

OMU link comes to working state.

BTS SW downloaded successfully.

Commissioning is successful.

Unlock the BCF using MML command ZEFS. The BCF is unlocked and comes to operationalstate after reset.



17 (121)





Check the BTS SW packet at the BSC and BTSManager

Requested SW is active.

Set up voice calls on all TRXs. All calls are successful.

Case Ref. BTSType/Configuration

EDAP POOL at BSC EDAP at Traffi cManager

EDAP Attached tothe TRXs

1 Nokia MetroSite

4 Omni EDGE TRX

Yes Yes No

2 Nokia MetroSite

4 Omni EDGE/GSM TRX

No No No

3.3.2 BTS Commissioning from BTS Manager with EDAP conf igured

Purpose:

To check that BTS is commissioned successfully with EDAP configured from

the BTS Manager.


BTS is in uncommissioned state.


Create the BTS Site at the BSC as described inthe test case.

Put all FU links and OMU link in WO state usingMML commands


Unlock all TRXs and the BTS.

OMU and FU link state are in BL-SYS state.

The BTS and its TRXs are unlocked

Attach the BTS SW under test to the BCF usingMML command ZEWA.

Activate the attached BTS SW using MMLcommand ZEWV.

SW attach denied due to ‘O&M Link State’.

SW activation denied due to BCF ‘AdministrativeState’.

Launch the BTS Manager and connect to the BTS The BTS Manager is launched and connected tothe BTS successfully.







Start commissioning of the BTS Site.

While configuring the Traffic Manager, EDAP isnot configured. Click the OK button to save thesesettings.

The Traffic Manager window gets closed andcommissioning proceeds. After displaying the

message “BCF in the configuring state”,commissioning fails to proceed and there is noresponse from the BTS SW.

Alarm 7730 BCF CONFIGURATION FAILED.

Unlock the BCF using MML ZEFS command atthe BSC.

The Equipment View and Alarm view get closed,and the Commissioning Wizard and BTS Eventview remain open.

After some time, the BTS Manager is againconnected to the BTS and it remains in waitingstate, due to wrong traffic settings.

Click Cancel button to cancel the commissioning. A pop up window is displayed.

Click Yes on pop up window to go to the“Commissioning Report” page.

The “Commissioning Report” page is displayed.

Click the Finish button to finish the commissioningprocess.

The Commissioning wizard is closed successfully.

Uncommission the site and commission the siteagain with the correct EDAP definition in the Traffic Manager.

Monitor the SW downloading on Abis.

The service terminal extension (using ZDDS;),RPHASESX (ZLE:P,RPHASESX) is used tomonitor the process of SW downloading of theBCF.

OMU link comes to working state.

BTS SW downloaded successfully.

Commissioning is successful.

Check the BTS SW packet at the BSC and BTSManager

Requested SW is active.

Set up voice calls on all TRXs. All calls are successful.

Case Ref. BTS Type/Configuration EDAP POOL at BSC EDAP Attached tothe TRXs

1 Nokia MetroSite4 Omni EDGE TRX withEGPRS Enabled

Yes (Multiple TSs) Yes



19 (121)




3.4 Background SW download to the BCF from BSC

The purpose of these tests is to verify that the SW can be background

downloaded on the previously loaded software and activated from the BSC tothe BCF.

Extra HW/tools: D-bus analyser.


The BCF is operational (BCF is in WO state). Setup a call in the BCF.

The call is successful.

BTS SW packages have been installed at the BSC.

Monitor the SW downloading from the BSC to theBCF on Abis. The D-Bus Analyser is used to

monitor the SW downloading from the Master TRXto the Slave TRX(s). The service terminal extensionRPHASESX is use to monitor the process of SWdownloading of the BCF.

Calls are made via TRX(s) and maintained duringbackground downloading of SW. Calls are successful and continued.

Start BTS SW background downloading using MMLcommand ‘ZEWA’ as stated in respective test case.

Background SW downloading startedsuccessfully. Calls are not released duringbackground downloading.

Background downloading completed.

The BTS SW package is activated by using MML

command ‘ZEWV’.

Software is not downloaded from the BSC. The

BCF is initialised with new SW and comes toWO state. All calls are released.

Verify the end state. The end state is the same as specified in thetest case.

The Active SW and SW in Newest Flashmemory are same.

New calls are made via every TRX. All calls are successful.

Activate the software that was previously running.Calls are made via all TRXs

BCF comes to WO state.

All calls are successful.

CaseRef. Config Additional Action Active SW andFlash Contentsat theBeginning

Downloaded SW End State SigSpeed

1 Multi TRXEDGE

1Generatesome Majorand Minoralarms whichneed to besent to BSC2

Active-CXM4.1CD1.0

Flash-CXM4.1CD1.0and CXM4.1

CXM5 Active-CXM5

Flash-CXM5andCXM4.1CD1.0

16kbps







2 3 Site chain,Multi TRX,

GSM+EDGE+GSM/EDGE

None Active-CXM3.3-1

Flash-CXM3.3-1and CXM4.1

CXM5 Active-CXM5

Flash-CXM5and CXM3.3-1

64Kbps

3 2+2GSM/EDGE

None Active-CXM5

Flash-CXM5andCXM4.1CD1

CXM4.1 Active-CXM4.1

Flash-CXM4.1and CXM5

16Kbps

1Satellite Abis only.

2Major-TRX Faulty: Antenna Connection Faulty, Minor – MMI Connected to

the Base Station

3.5 BTS SW download from BTS Manager to the BCF

The purpose is to check that the BCF SW can be updated from the BTS

Manager and put under use successfully.


The BCF is operational (BCF is in WO state). Set

up a call in the BCF.

The call is successful.

From the BTS Manager, the BTS SW ⎪ Update command is selected. The master file for CXM5that is not already downloaded to the BCF isselected and loading is started.

The SW is background downloaded from thePC to the BCF.

The SW loading does not disturb the call.

SW versions are requested. The SW version report shows that the SWpackage is in the flash memory but not as the'Running Package'.

The same SW is activated at the BSC. The BCFis reset. SW versions are requested.

The BCF is reset. The SW is not downloadedfrom the BSC to the BCF. The backgrounddownloaded SW package is in the flash

memory.

The BCF is operational (BCF is in WO state).

A call is set up in the BCF. The call is successful.

From the BTS Manager, the BTS SW ⎪ Update command is selected. The master file, which isalready in the BCF as the Running Package, isselected and the loading sequence is started.

The SW downloading is not started. The user isinformed that the SW is already in the flashmemory.

The call is not disturbed by the SW relatedactions.



21 (121)





The SW versions are requested. The SW version report shows that the SWpackage is already in the flash memory as the

"Running Package".

Above steps, involving the update of the alreadyexisting SW in flash, are repeated with an attemptto download a SW package, which is already inthe BCF but not as the Running Package.

This time the SW is downloaded and is seen asthe "Newest in flash".

CaseRef .

Configuration

1. 2+2GSM/EDGE, RF Hopping in 1st sector, 2nd sector DFCA enabled with 1 DFCA TRX

3.6 BTS SW package background downloading andactivation (mass operation)

Purpose:

The purpose of the test is to ensure that the BTS SW package can be

background downloaded and activated properly from Nokia NetAct.


BTS SW package CXM4.1 CD1.0 is IN USE(running package). BTS SW package CXM4.1 isin flash memory.

From the Top Level Interface, “Utils” menu,choose “NE SW Configuration Mgmt.”. Fromthere, choose “Software ConfigurationManagement” and finally click on the “SoftwareArchive” tab.

From the Software Archive’s page, select thecurrent tested SW package, that is, CXM5 from“BS Software”.

In “Software Archive” window, from “ManagedObjects”, select all BCFs to be downloaded andactivated at the same time (mass operation), clickon “download” button to open the “TasksScheduling” window.

NOTE: The Mass Software downloads need to beperformed at least on 10 BCFs. This includesBCFs on different BSCs.







In the “Tasks Scheduling” window, select“Immediately” to download CXM5 immediately or

“later” to download with a set time, and activatethe button “Activate Software”.

SW package CXM5 is background downloaded.Right after the downloading is done, CXM5 is

activated automatically. When SW packageCXM5 is activated, the BCFs restart and initialise.

After the downloading and activation is finished,test calls are made via the BCF.

Calls can be made via the BCFs successfully.


1. Test case is executed exactly as described above with at least one BCF configured as4+4+4, chained configuration, EDGE+GSM+EDGE/GSM



23 (121)



Manual configuration change

4 Manual configuration change 4.1 Adding new TRXs

The purpose of the case is to ensure that a new TRX can be manually added to

Nokia MetroSite BTS.


Calls are made via the BCF in which the TRXsare to be added. The new TRXs being added donot have CXM4.1 in their flash.

The calls are successful.

An LAPD link for the new TRX is created andexecuted in WO state using MML commandZDTC: <FU no.>: WO;

The TRX is created under the correct BCF andBTS in the BSC. The TRX is in locked state afterit is created.

The TRX creation at the BSC is successful.

New TRXs are installed. The SW in the memoryof the new TRXs is different from the SW in theother TRXs.

When the TRX is inserted into the BTS, themaster TRX detects that the configuration haschanged. The master TRX downloads theactive SW to the new TRX.

From the BTS Manager, the Abis TS allocation isupdated with the Traffic Manager.

The Abis TS allocation can be updated withoutdisturbing other TRXs. No call is cleared.

The new TRXs are unlocked [if the new TRX is

added into a BB-hopping BTS, this BTS alsoneeds to be locked/unlocked in order to take thenew TRX into the BB-hopping sequence]. Testcalls are made via every TRX and TS (timeslot).

The new TRX is successfully initialised and

made operative in the network. The calls aresuccessful.

CaseRef.

Configuration O&M andTRXSIG

TransmissionCard

SigSpeed

HoppingMode

Addition Done

1. 2GSM Combined FXC E1, (ITNC3.0)

16 kbps RF 2 EDGE TRXs



25 (121)




2. 1 TRX GSM(PreferredBCCH)

Combined FC E1/T1 (ITNC1.0)

64 kbps - 3 TRX GSM,with 64Kbpscompressedsignalling

3. 2+1 TRXEDGE

Separate FXC E1/T1(ITN C3.0)

32 kbps - 1 EDGE TRX tosecond BTS,with 32 Kbpssignalling

4. 2 TRX GSM Combined FXC RRI (ITNC3.0)

16 kbps RF New EDGE BTSwith two TRX,with 16 Kbpssignalling

5. 3 TRX EDGE Combined FXC E1 (ITNC2.1-2)

16 kbps BB 1 EDGE TRX tosecond BTS,with 64 Kbps

signalling

6. 2+1 TRX GSM Separate FC STM-1(C3.0)

64 kbps BB 1 EDGE TRX tosecond BTS,with 16 Kbpssignalling

7. 2 TRX EDGEWith extendedBTS id

Combined FXC E1/T1(ITN C2.2)

64 kbps - 2 TRX GSM,with 16 Kbpssignalling

4.2 Site expansion

The purpose is to ensure that MetroSite can be extended successfully to a

MetroSite chain configuration.


The BCF is in operational state. The new TRXsbeing added do not have CXM5 in their flash.

The BCF is working. No alarm is present.

Calls are made on all TRXs. The calls are successful.

New LAPD link and BTSs are created at the BSC

to expand the BCF into a 1st

expansionconfiguration. Lock the BCF and power off themaster cabinet and connect the first slavecabinet.

All calls are dropped after the BCF lock.





Manual configuration change


Turn the master cabinet power on. Correspondingchanges are made in the Traffic Manager with the

BTS Manager by using the Undo-commissioningoption. Then commission the site according to thenew configuration. Unlock the BCF and newlycreated BTS and TRX(s). A new cabinet with allnewly configured TRX(s) and without atransmission card is powered up.

All BTSs come to working state. No alarms arepresent at the master BTS.

Calls are made on all TRXs of the both cabinets. The calls are successful.

A new LAPD link and BTSs are created at theBSC to expand the BCF into a 2nd expansionconfiguration. Lock the BCF and power off thecabinets and connect the second slave cabinet.

All calls are dropped.

Turn the master cabinet power on. Correspondingchanges are made in the Traffic Manager with theBTS Manager by using the Undo-commissioningoption. Then commission the site according to thenew configuration. Unlock the BCF and newlycreated BTS and TRX(s). The second and thethird cabinet with all newly configured TRXs andwithout a transmission card is also powered up.

The BCF is in working order. No alarms arepresent.

Calls are made on all TRXs on all the cabinets. The calls are successful.

Wait for at least 15 minutes. The BCF is in working order and no alarms arepresent. All calls are still ongoing.

CaseRef .

InitialConfiguration

Configuration after 1

stExpansion

Configuration after 2

ndExpansion

Initial HoppingMode

1. 2 Omni GSM 2 GSM+

4 EDGE

2 GSM +4 EDGE +4 EDGE

Non Hopping

2. 4 Omni Edge 4 EDGE +(2+2)GSM

4 EDGE +(2+2)GSM +(1+1+1)EDGE

BB Hopping

3. 2+2 GSMS11.5 (2+2) GSM +2EDGE/GSM

(2+2) GSM +2EDGE/GSM + (3+1)EDGE

1st Sector – RFhopping

2nd Sector- Non

hopping

4.3 Hot-insert TRX for chain configuration

The purpose of these test cases is to verify that a TRX can be hot-inserted to a

Master or Slave cabinet while the BCF is in supervisory state.



27 (121)





The BCF is in supervisory state. Calls are placedin the BCF.


The TRX specified in the test case is removedand behaviour is verified with Expected-Result(given in the test case).

Behaviour is as per Expected-Result.

If the removed TRX is BCCH TRX (other thanMaster TRX) then call(s) on this TRX and TRXwith reconfigured BCCH will be released.

Lock the TRX from the BSC, and a new TRX isinserted into the empty position of the previouslyremoved TRX.

Unlock the TRX.

The Chain Master TRX detects the newinserted TRX and the BTS Manager shows the TRX. The Chain Master TRX synchronises andconfigures the new inserted TRX. All are insupervisory state.

Alarms are checked at the BSC and the BTSManager. Calls are made on all TRXs.

No alarms are active and the calls aresuccessful.

Case Ref. Configuration TRX Removed Expected Result TRX Inserted

1. 3 Cabinet chain, 4 TRX each cab,Master cab(BTS1): 4TRXGSM 1800 Band,Slave 1 cab(BTS2): 4TRXGSM/EDGE 900band, Slave 2 cab(BTS3): 4TRX

EDGE 1800 band

Master TRX inSlave cabinets(TRX in position 5.Repeat for 9)

When the Master TRX in the Slavecabinet is removed,alarms 7767 BCCHMISSING and 7705LAPD LINK FAILURE are activefor the Slavecabinets.

Any

2. 3 Cabinet chain, 4 TRX GSM in eachcabinet

Slave TRX in theSlave cabinet

When the Slave TRXis removed, alarm7606 TRX Faulty isactive for theremoved TRX.

Any EDGE TRX1

3. 3 Cabinet chain, 4 TRX EDGE ineach cabinet

Slave TRX in theMaster and Slavecabinet

When the Slave TRXis removed, alarm7606 TRX Faulty isactive for theremoved TRX.

Any GSM TRX

1New inserted TRX should have CX5 SW in flash.





BTS tests

5 BTS tests 5.1 TRX tests

The purpose is to verify that the TRX test can be carried out successfully.

Note 18

Acceptable tests results are: BER =0%, RX-Sensitivity: -110.5 dBm (or better)

for GSM 900 and GSM 800, -111 dBm (or better) for GSM 1800 and GSM

1900.

The GMSK sensitivity is typically –111 to -113 dBm, MCS-5 is –107 to -109

dBm and MCS-9 is –97 to -99 dBm.

The threshold values of the TRX performance test need to be defined as the

default values.

The default threshold of the TRX performance test values for MetroSite are:

Transmitted Metro Power (PWRM) = 30dBm

Transmitted Metro HP Power (PWRH) = 37dBm

Transmitted Metro XP Power (10 W) = -40dBm

BER (BER) = 0.2000%

RX Sensitivity (MSENS) = -100 dBm

At the BSC, the current threshold values of the TRX performance test can be

verified using the MML command ‘ZUCV:TRP,CURRENT;’.

If the current threshold values are different from those stated as default, the

current values should be modified by using the MML command

‘ZUCV:TRP,MODIFY:PWRU=<pwru_val>, BER=<ber_val >,

MSENS=<msens_val>;’



29 (121)




Note 19

The expected range of the TX power level from a TRX test is the transmitted

power level – PMAX value ± 4 dBm.

Therefore for MetroSite, if the transmitted power level is 37 and PMAX is 30,

the expected power level from the TRX test is 37-30±4 that is, 3dBm to 11 dBm

range.

When the test case calls for a failure to occur during the test or a failure to start

the test, the failure reason is included in the TRX test report.

Note 20

When the test is started from the BTS Manager, the alarm 7615 RTS IS IN

TEST USE' for the used TS is started. When the BTS Manager finishes the test,

the alarm 7615 RTS IS IN TEST USE' for the used TS is cancelled.

This alarm may not be included in the alarm history at the BSC as the BSC usestime-window based filtering for alarm reporting. That is, if an alarm is started

and cancelled within 10-seconds.

Note 21

For all the tests that require a TRX test to be run, the PMAX value should be set

as Maximum (that is, '0').

Note 22

The BTS is assumed non-hopping unless otherwise stated.

Note 23

TRX test modulation(s) used for different TRXs in the stated configurations:

• GSM sector : When a TRX test is performed for a GSM TRX, bothmodulation methods are available. However when the test is startedusing the 8-PSK modulation, the BTS shall determine that the wrongmodulation type is selected for the TRX, change the TRX test to useGMSK modulation and indicate this in the report.

• EDGE sector (EGPRS enabled): When a TRX test is performed for anEDGE TRX, both the GMSK and 8-PSK modulation methods arepossible. The modulation scheme tested is indicated in the report.

• EDGE sector (EGPRS disabled): When a TRX test is performed for anEDGE TRX, both the GMSK and 8-PSK modulation methods are

possible. If a TRX test is performed from the BSC using the 8-PSK modulation scheme, the test shall be performed using the GMSK modulation as the TRXs are EGPRS disabled. The GMSK modulationscheme shall be indicated in the report.

• GSM/EDGE sector: It shall depend on whether the TRX to be tested is aGSM or EDGE configuration. Please refer to ‘GSM sector’, ‘EDGE sector(EGPRS enabled)’ and ‘EDGE sector (EGPRS disabled)’.






BTS tests


The BCF is not commissioned.

TheTests | TRX Test command is selected. The TRX Test command is not executed.Start commissioning the site with OMU Signallingblocked. The BCF is in the 'Waiting for LAPD'state and TRX(s) are in the 'SW Loading' state. TheTests | TRX Test command is selected.

The TRX Test command is not executed.

TheBTS SW | Use Current SW command isselected.

The SW is taken in use.

TheTests | TRX Test command is selected. The TRX, ARFN number, and Radio Timeslot aregiven and the test is started.

The test is started.

The test results are checked. The test results are acceptable.

The test is repeated with different TRX, TS, andchannel numbers.

The test can be executed successfully withdifferent parameters.

Case Ref. HW Type Modulation Hopping Mode

1. GSM GMSK RF-hopping

2. EDGE GMSK Non-hopping


A call is made via the TRX to be tested. The call is successful.

A TRX test is started from the BSC using the MMLcommand ‘ZUBS’. The TRX test is done for alltimeslots.

The TRX test can be started on a TCH TS thatdoes not have PBCCH, control channels, a TSreserved for GPRS as partner. The test is notstarted for control channels or channels with anactive call or a TS reserved for GPRS and theirpartner TS.

The tests results are checked using the MMLcommand ZUBP. The TX power level used isverified with a spectrum analyser.

The test results are received at the BSC alarmprinter. The test is successful and the testresults are acceptable. The TX power levelused is the same as the BCCH TX power level(power level depends on the PMAX value). Thecall is not affected.

TheFile /Options command is selected from theBTS Manager and the File Handling tab is chosen.Check the checkbox next to the Test Log option. The pop-up address window saves the log to aspecific address.

The required log file can be defined. The log fileis correctly shown in the status bar of the testwindow.



31 (121)





The TRX test is repeated with the BTS Manager,using the Tests | TRX Test command. The TRX

test is performed with all modulation methods.

When TRX test is performed for GSM TRX, thetest is started as a normal TRX test (GMSK).

The test is successful and the test results areacceptable.

When TRX test is performed for an EDGE TRX,the modulation method is selectable. When thetest is performed with GMSK method, 8 PSK MCS5 or 8 PSK MCS9 the test is successfuland the test results are acceptable.

When the test is started, the alarm RTS IS IN TEST USE for used TS is started.

When the test is done finished, the alarm RTSIS IN TEST USE for the used TS is cancelled.

When the log is on, all generated TRX testsetting and results are saved into the log file.

The test is not started for control channels orchannels with an active call.

The log file is set not to be in use (the checkbox isunchecked) from the File Handling page.

The test log file is not shown in the status bar. The file is not appended anymore.

The log file is opened from the saved location. The TRX test results are shown correctly for allmodulation methods.

For test 2, 6 hours script performing TRX test withdifferent modulation methods consecutively (first

GMSK, then 8-PSK) is used. The script tests theBCCH and Non-BCCH TRXs on both sectors. The test results and alarms are logged after eachtest.

The correct modulation scheme is used andstated in the report.

Alarms are raised and cancelled for TRX test.

The test is repeated for all unreserved TSs in the TRX.

Case Ref. Configuration ChannelConfiguration

Hopping Mode TX Power EGPRSenabled for EDGE units

3 Any Chain

configurationwith at-least 3sectors,GSM+EDGE+GSM/EDGE

MBCCH+

SDCCH+6*TCHF, some TS reserved forGPRS

None 1st sector

–minimum.2nd sector–maximum

Yes

4 2+2,GSM+EDGE, 6 hoursscript with TRX test

MBCCH+MPBCCH+SDCCH+7*TCHF

- - Yes





BTS tests


5 2+2 commonBCCH Dual

band EDGE TRX

MBCCHC+7*TCHF

1st

sector- None

2nd

sector-RF,Different no. Of frequencies in MALlist (3,20,63 etc)

- No

Purpose:

The purpose of these test cases is to verify that the TRX test fails when some

failure action is performed.


The BCF is operational. Perform the failure actionas specified in the test case.

The TRX Test is started from the BSC with theMML command ‘ZUBS’ for the TRX affected withthe failure action.

The test is started.

Abis is monitored. From the Abis trace, failure reason is seen underBTS Test Report Message.

The test results are checked from the BSC alarmprinter.

The test results are received at the BSC alarmprinter. The test results are not acceptable andare the same as mentioned in Expected Result.

Failure action is corrected and the TRXLOCK/UNLOCK command is given. The alarm is cancelled after TRX is reset.

Calls are made using all TSs on the tested TRX. All calls are successful.

All calls are terminated. The TRX test is startedfrom the BSC.

The test is successful. The test results areacceptable.



33 (121)





TRX Test is repeated with the BTS Manager,using Tests | TRX Test command. TRX test is

performed with all modulation methods.

When the TRX Test is performed for a GSM TRX,the test is started as normal a TRX test (GMSK).

The test is successful and the test results areacceptable.

When the TRX Test is performed for an EDGE TRX, the modulation method is selectable. Whentest is performed with GMSK method, 8 PSK MCS5 or 8 PSK MCS9 the test is successful andthe test results are acceptable.

When the test is started, the alarm RTS IS IN TEST USE for used TS is started.

When the test is done finished, the alarm RTS ISIN TEST USE for the used TS is cancelled.

When the log is on, all generated TRX Testsettings and results are saved into the log file.

The test is not started for control channels orchannels with an active call.

CaseRef.

Configuration Failure Action Expected result

6. Multi TRXEDGE

Remove Non-BCCH TRX antenna cable

Result printout indicates the test has failed. Alarm7606 TRX FAULTY (TRX antenna connectionfaulty) is issued at the BSC.

7. Multi TRX GSM Remove the diversity

antenna cable fromthe TRX

The failure reason (HW Failures) is included in the

BTS test report. Measurement results are alsoincluded.

8. Multi TRXEDGE

Remove Slave TRXduring the TRX Testand insert it again.EGPRS is enabledand 8-PSK modulations are inuse.

The test results are received at the BSC alarmprinter. The test result INCONCLUSIVE indicatesthe test was interrupted.

9. Multi TRXEDGE

Set up EGPRS datatransfer. Start the TRX Test from a BSC

on the same timesloton which a EGPRScall is going on

The TRX Test is not performed. The TRX Testresults show the TRX Test could not be performeddue to circuits already being in use. The EGPRS

call is not interrupted.





BTS tests

5.1.1 Autonomous TRX tests

Purpose:

To check that the autonomous TRX tests run successfully after a MetroSite is

given a reset.

Note 24

Autonomous TRX test are the TRX tests which run on a MetroSite when the

site is commissioned or given a reset. They are similar to the TRX test except

that these are triggered automatically. If for any reason these tests fail initially,

then these tests run for up to three times, at a gap of ten minutes, until they pass

or raise an alarm.


The site is in commissioned state.


A MetroSite is up and working.

The site is reset from the BSC using commandZEFR.

The site is reset successfully.

When the site has just come up again after reset,the autonomous TRX tests will run on all the TRXs. Check the BTS Manager and the Abisinterface.

The alarm 7615 RTS IN TEST USE is seen at theBTS Manager alarms window and can also beseen on the ABIS via Nethawk.

The TRX test should not fail.

Observe the behaviour of the site for about 12minutes.

No autonomous TRX tests run on the MetroSiteafter 10 minutes of coming up and no ’RTS IN TEST USE’ alarm is reported at the BTS managerand the BSC, which means the autonomous TRXtests after reset were successful.

Case Ref. Site Type Configuration

1 MetroSite 4 Omni

5.2 Abis loop test

The purpose is to verify that the Abis loop test can be carried out successfully.

Note 25

Acceptable tests results are: BER < 0.1%, FER < 0.1%.



35 (121)




Note 26

The channel configuration is not significant unless specifically mentioned.


Calls are made via BTS. The calls are successful.

Some calls are terminated. The Abis loop test isstarted from the BSC with the MML command‘ZUBK’. Several test times between minimum andmaximum are used.

The test is started successfully.

For test 3, 6 hours script performing Abis looptest. The script tests both the BCCH and Non-BCCH TRXs. The test results and alarms arelogged after each test.

The test is started successfully.

The loop test results are checked from the BSCusing the MML command ‘ZUBP’.

The test status indicates success. The test resultsare acceptable. The TSs carrying Controlchannels, Traffic and GPRS are not tested.

The calls are not affected.

Make new calls on tested TSs Calls are successful

CaseRef.

Configuration TSConfiguration

Transmission Unit

SignallingSpeed

O&M andTRXSIG

AbisConnection

1. 4 Omni EDGE1,S11.5

GPRS TS, Dy.Abis TS

FXC E1/T1,(ITN C3.0)

16 Kbps Combined Normal

2. 4 Omni TRX Normal TS,GPRS TS

FC E1/T1,(ITN C1.0)

16 kbps Combined Satelliteabis

3. Multi TRXEDGE1

6 hours using atest script thatrepeatedlycarries out Abisloop tests onone BTS

FC STM-1(ITN C3.0)

16 Kbps Separate Normal

4. Any Chainconfigurationwith at-least 3sectors,GSM+EDGE+GSM/EDGE

Several TRXsin one BTS andany GPRS TS

FXC E1(ITN C3.0)

32 Kbps Separate Normal





BTS tests


5. 2GSM+2EDGE,common BCCH

RF hopping inboth sectors

(MBCCH+SDCCH+6TCHF+8

TCHF)+(SDCCH+7TCHF+8TCHF)

FXC RRI(ITN C2.2)

64 Kbps Combined Satelliteabis

1Dynamic Abis is used

Purpose:

The purpose of the test case is to verify that the Abis loop test is stopped when

some interruption takes place and can start again.


The Abis loop test is started from the BSC withthe MML command ‘ZUBK’. The test is started.

The test is interrupted with the MML command‘ZUBK’.

The test is interrupted.

Loop test results are checked from the BSC alarmprinter.

The test status indicates inconclusive resultsbecause of the interruption.

Calls are made using the tested TS. All calls are successful.

The Abis loop test is restarted from the BSC. The test is restarted.

The loop test results are checked from the BSCusing MML commands ‘ZUBP’.

The test status indicates success. The test resultsare acceptable.

Case Ref. Configuration Transmission Unit (Release)

6. Multi TRX FXC E1/T1 (ITN C3.0)



37 (121)




6 Object control Note 27

The state of the Object (that is, TRX, BTS, BCF) is checked after every test step

with the MML command ‘ZEEI’. Alarms are checked after every test step onthe BSC alarm printer.

6.1 TRX lock/unlock and block/unblock

The purpose of these tests is to verify that the TRX can be locked/unlocked

from the BSC and block/unblocked from the BTS Manager.


PBCCH is configured. TRX transmit power levelsare checked with a spectrum analyser.

TRX transmit power levels are same as set inthe BSC.

Neighbour cells are defined. Calls are made viaevery TRX.


A TRX is locked from the BSC with the command’ZERS’. BCCH transmission is checked using aspectrum analyser.

The TRX is locked. Call(s) on the locked TRX isreleased. If the BCCH TRX is under test, BCCHtransmission stops. The calls remain ongoingon other TRXs.

The TRX is unlocked with the ‘ZERS’ command. If the BCCH TRX is under test, alarm 7767BCCH MISSING is active until the TRX isinitialised. The TRX returns to working state.

TRX transmit power levels are checked with aspectrum analyser.

The power levels before and after the TRXreset match the defined setting at the BSC.

Calls are made using every TRX. All calls are successful with good quality.





Object control


TheBlock command is given for the TRX from theBTS Manager.

Alarm 7208 LOCAL BLOCK is sent to the BSCand BTS Manager. The TRX blocked symbol is

updated into the Supervision window view.

Calls are handed over from the blocked TRX. If the BCCH TRX is blocked and reconfigurationis possible, calls are still handed over.

TheUnblock command is given for the TRX fromthe BTS Manager.

7208 LOCAL BLOCK alarm is cancelled. Theblocked symbol disappears from the TRX objectin the Supervision window view.

Alarms are checked. There are no active alarms.

Calls are made using every TRX. MO and MTGPRS calls are also made.

All calls are successful with good quality.

Case Ref. Configuration BCCH TRX TRX Locked

1. Multi TRXEDGE/GSM

- BCCH


The BCF is in Supervisory state.

Calls are made via all TRXs


TRX transmit power levels are checked withspectrum analyser.

TRX transmit power levels are the same as set atthe BSC.

An MML macro, which repeatedly locks andunlocks all TRXs, one at a time, is started.

The TRXs start up properly after every lock andunlock command.

The alarm history is checked after the macro iscomplete.

When the BCCH TRX is locked, alarm 7767BCCH MISSING is active. Other alarms do notoccur.


The power levels before and after TRX resetshould match the defined setting at the BSC.

Calls are made on all the TRXs after the test. All calls are successful.


2.

Chain configuration with 3 MetroSites (at least one EDGE and one GSM MetroSite),

PBCCH is configured. MML macro is run for 12 hours.

3. 4 TRX GSM/EDGE, DFCA enabled sector with 2 DFCA TRXs. MML macro is run for 12hours.




39 (121)





The BCF is in Supervisory state. Calls are madevia all TRXs.

Calls are successful.


TRX transmit power levels are the same as set atthe BSC.

The antenna cable is removed from the preferredBCCH TRX. PMAX is set to 0.

‘7606 TRX Faulty: Antenna Connection Faulty’alarm is generated. BCCH reconfiguration takesplace.

An MML macro, which repeatedly locks andunlocks all TRXs, one at a time, is run for 12hours.

The TRXs start up properly after every lock andunlock command. Alarm 7606 is cancelled everytime the preferred BCCH TRX is unlocked. BCCHreconfiguration takes place as the preferredBCCH TRX gets blocked because of the removedantenna cable.


When the BCCH TRX is locked, alarm 7767BCCH MISSING is active. TRX Faulty alarm forthe TRX with removed antenna cable is cancelledand generated. Other alarms do not occur.

The antenna cable is reconnected. The TRX isreset.

Alarm ‘7606 TRX Faulty: Antenna ConnectionFaulty’ gets cancelled.


The power levels before and after TRX resetshould match the defined setting at the BSC.

Calls are made on all the TRXs after the test. All calls are successful.

Case Ref. Configuration Hopping Mode

4. 2 EDGE +2 GSM 1st sector – Non Hopping, 2nd sector – RFHopping

6.2 BCCH reconfiguration

The purpose of these tests is to verify the reconfiguration of BCCH to the

preferred TRX.


PMAX is set to 0. The Abis is monitored.

An antenna cable is removed from the preferredBCCH TRX.

Alarm 7606, TRX Faulty alarm is generated.BCCH reconfiguration takes place.

The preferred BCCH TRX is locked and thenunlocked from the BSC.

Alarm 7606 is cancelled when the preferredBCCH TRX is locked. BCCH reconfigurationtakes place as the preferred BCCH TRX isblocked because of the removed antenna cable.





Object control


The antenna cable is connected. The TRX isreset.

Alarm 7606 is cancelled. The preferred BCCH TRX is configured as BCCH.


The power levels before and after the TRXreset should match the defined setting at theBSC.

Calls are made on all TRXs after the test. All calls are successful.

Case Ref. Configuration Preferred BCCH TRX Hopping Mode

1. 4 EDGE/GSM Master DFCA enabled, Slave TRXs are defined asDFCA TRX


The Abis is monitored.

Using the ZDTC command at the BSC, thepreferred BCCH TRX signalling link is blocked.

Power level is checked

BCCH reconfiguration takes place. The BCCHpower level is as configured (for both thepreferred BCCH TRX and the reconfiguredBCCH TRX).

Using the ZDTC command at the BSC, thepreferred BCCH TRX signalling link is unblocked

The preferred BCCH TRX is configured asBCCH.

Calls are made on all TRXs after the test. All calls are successful.

Case Ref . Configuration Preferred BCCH TRX Hopping Mode

2. 4 Omni EDGE Slave

BB hopping

The purpose of the test case is to verify that EGPRS can be enabled for the

Master TRX.


The Abis is monitored. EDAP and EGPRS areenabled on the BCCH TRX

The synchronisation procedure, EGPRS attachand PDP context are checked.

Using the ZDTC command at the BSC, thepreferred BCCH TRX signalling link is blocked

BCCH reconfiguration takes place. The BCCHpower level is as configured (for both thepreferred BCCH TRX and the reconfiguredBCCH TRX).

Using the ZDTC command at the BSC, thepreferred BCCH TRX signalling link is unblocked

The preferred BCCH TRX is configured asBCCH.



41 (121)






The power levels before and after the TRXreset should match the defined setting at the

BSC.

The synchronisation procedure, EGPRS attachand PDP context are checked

Case Ref. Configuration Hopping Mode Preferred BCCH

3. 4 Omni EDGE BB hopping Master TRX

6.3 BTS lock/unlock and block/unblock

The purpose of these tests is to verify that the BTS can be locked and unlocked successfully from the BSC and blocked/unblocked from the BTS Manager.

Note 28

In case a Master TRX is reset from the BTS Manager, the SW download event

will not be shown as shown in case of a slave TRX(s) reset.

Note 29

The state of the BTS is checked after every test step with the MML command

‘ZEEI’. Alarms are checked after every test step on the BSC alarm printer.


Neighbour cells are defined in the same and otherBCF. Calls are made via every TRX.


The BTS is locked with the ‘ZEQS’ command.BCCH transmission is checked with a spectrumanalyser.

Calls are handed over from the locked BTS. The BCCH transmission is stopped.

For case 2, PBCCH is configured on a BCCH TRX after locking the TRX.

The BTS is unlocked with the ‘ZEQS’ command.

The Abis is monitored.

Alarm 7767 BCCH MISSING is activated until

the BCCH TRX is initialised. The BTS is startedcorrectly and the correct system information issent. The BTS and TRXs under the BTS returnto working state. The BCCH transmissionrestarts.






Object control


TheBlock command is selected for the sectorfrom the BTS Manager.

The BTS is blocked at the BSC. Calls arehanded over from the blocked BTS. Alarm 7208

LOCAL BLOCK for the BTS is started. Theblocked sector is updated into the LogicalObjects view. The BCCH transmission isstopped.

TheBlock command is given for a TRX in theblocked BTS.

The TRX cannot be blocked.

TheReset command is given for a TRX in theblocked BTS.

The TRX is reset.

TheUnblock command is selected for the sector. The BTS becomes operational. The 7208 alarmis cancelled. The BCCH transmission restarts.

Alarms are checked. There are no active alarms.Calls are made using the BTS. All calls are successful. The quality of calls is

good.

In the BTS Manager, the File /Options commandis selected and the File Handling tab is chosen.

Check the checkbox next to the Events Logoption. The pop-up address window saves the logto a specific address.

The Events log file can be defined and iscorrectly shown in the status bar of the Eventwindow.

TheReset command is given for the sector fromthe BTS Manager.

All TRXs in the BTS are reset. This can be seenvisually and from the Supervision window viewsand the BTS Events window at the BTS

Manager.

All TRXs in the BTS enter the 'Supervisory'state.

Calls are released on the reset BTS only.

Alarms are checked. There are no active alarms.

From the BTS Manager, the TRX Test isperformed to all TRXs that belong to the BTS.

The TRX tests are successful.

The contents of the event log file are checked. When the log is on, all generated event settingsand results are saved into the log file.

The log file is set not to be in use (the checkbox isunchecked) from the File Handling page.

The log file is not shown in the status bar of theevents window. The file is not appendedanymore.

The file is opened from the saved location. The contents are the same as shown in theEvents window.

Calls are made via every TRX. In case 2, GPRScalls are made.


A BTS lock/unlock, reset and block/unblock isdone for all BTSs.



43 (121)





An MML macro, which repeatedly locks andunlocks the BCF, is started and run for 12 hours. The BCF returns to working state after everylock and unlock.


Alarm 7767 BCCH MISSING is active when theBTSs are initialised. Notice 7701 BCFINITIALIZATION is sent when the BCF isinitialised. The BTSs and TRXs under the BCFreturn to WO state. Unexpected alarms do notoccur.


Case Ref. Configuration Hopping Mode

3. 2CTxA +2 HVTx

2nd sector DFCA enabled withDFCA TRX

RF Hopping in 1st sector

6.5 BCF reset

The purpose of these tests is to verify that the site can be reset from the BSC

and the BTS Manager.

Note 30

In a chain configuration, if the master does not poll the slave cabinet for frame

clock sync, the slave must stop RF transmission after 10 minutes.



The site is reset from the BSC with the ‘ZEFR’command. BCCH transmission is checked with aspectrum analyser.

The BCF is reset. Calls are released. TheBCCH transmission is stopped. Notice 7701BCF INITIALISATION is sent during the siteinitialisation. The BCF returns to WO state

along with all the BTSs and TRXs under theBCF.


The BCF is reset from the BTS Manager with agiven option in the table below.

Calls are released. BCCH transmission isstopped. The whole BCF is reset. Notice 7701BCF INITIALISATION is sent during the siteinitialisation. The BCF returns to WO statealong with all the BTSs and TRXs under theBCF.





Intelligent Shutdown for MetroSite

8 Intelligent Shutdown for MetroSite Note 32

For all the Intelligent Shutdown test cases neighbours are defined for the BTS

under test. The neighbours defined shall not be involved within the testing of the feature other than to handle the calls once handed over by the BSC unless

otherwise stated.

Note 33

During Intelligent Shutdown, the shutdown TRXs shall get powered off. The

TRXs shall no longer report to the BTS Manager and therefore shall not be

visible on the Equipment view of the BTS Manager. The administrative state of

the TRXs in shutdown mode will be verified from the Object Property ->

Operational State, and be reported as Shutdown. And the Device State will be

reported as Missing from Configuration.The exception to this rule shall be the Master TRX. This shall remain powered

even in the shutdown mode. The Master TRX of the Master Cabinet shall also

power off the Master TRX of the Slave cabinets, if all TRXs in the Slave

cabinet are in the shutdown mode. The Master TRX, when left powered during

the shutdown mode, shall be visible on the Equipment view and could be

verified as shutdown.

The TRXs not in the shutdown mode shall be shown as supervisory.

The TRXs could be verified as being in the shutdown or supervisory mode on

the BTS Manager using the objects/properties command.

Note 34

For all the Intelligent Shutdown test cases it is assumed that the testing shall be

completed using an external BBU (EAC inputs) unless otherwise stated. The

EAC input shall need to be set as detailed below. The predefined external input

for MetroSite for the Mains fail is EAC 01.

ZEFX: <bcf _i d>: I NBR=1: ROU=MAI NS: POL=<OPEN - act i ve orCLOSED - i nact i ve>, SEV=AL3;



49 (121)




Note 35

For the Intelligent Shutdown cases RDIV=N should be used.

Note 36

For all test cases the NONE Shutdown Mode shall be used unless otherwise

stated. The timers shall be set to convenient times to allow the test case to be

performed.

‘ ZEFM: <bcf _i d>: BBU=NONE, NTI M=<NTI M_t i mer >, BTI M=<BTI M_t i mer >

; ’ .

Note 37The spectrum analyser is connected to the BCCH TRX to monitor the BCCH

Transmission during all Intelligent Shutdown test cases.

Note 38

When a BTS_CONF_DATA message is received during the intelligent

shutdown, any units in the configuration message that are in shutdown mode are

unaffected. It is to be verified that a BTS_CONF_COMPL message is sent for

the BCF in which the shutdown TRXs reside, even if the actual configuration is

skipped for these.

Note 39

The feature consists of three BTS Battery Backup procedures that may be

applied on a mains failure, these are:

• Al l shutdown mode - maintain full service,

• BCCH shutdown mode - maintain the BCCH TRXs, or

• None shutdown mode - maintain only the transmission equipment.






Note 40

It is possible to activate the Intelligent Shutdown with Timer Control with the

MML command ‘EFM’:

ZEFM: <bcf _i d>: BBU=<BTS bat t er y backupprocedure>, NTI M=1, BTI M=3;

Where:

ZEFM:<BCF identification>:BBU<BTS battery backup

procedure>, NTIM<TRX shutdown timer>, BTIM<BCCH TRX shutdown

timer> where <TRX shutdown timer> and <BCCH TRX shutdown timer> are

given as a decimal number.

NTI M=1 means that after a mains failure, there is full service on the BTS site

for one minute before the service level is changed. This can be any value from 1

minute to 600 minutes.

BTI M=3 means that the BCCH TRXs will be maintained for three minutes after

the non-BCCH TRXs are shut down, that is, until the BTIM timer expires. This

can be any value from 1 minute to 600 minutes.

Note 41

NTIM=1 and BTIM=3 should be used unless otherwise stated.

Timer 1 Timer 2 Timer 3 Timer 4 Timer 5TRXtype Power State Power State Power State Power State Power State



51 (121)




Timer 1 Timer 2 Timer 3 Timer 4 Timer 5

TRX 1 –BCCH

ON WO ON WO ON WO ON BL-SHD

OFF BL-PWR

TRX 2 - TCH

ON WO ON BL-SHD

OFF BL-PWR

OFF BL-PWR

OFF BL-PWR

TRX 3 - TCH

ON WO ON BL-SHD

OFF BL-PWR

OFF BL-PWR

OFF BL-PWR

Figure 1. TRX’s powers and operational states during shutdown procedure,when only transmission equipment is left alive

8.1 All shutdown mode

The purpose of the test cases is to verify the functionality of the ‘All shutdown

mode’, which allows all the units to remain fully operational until the battery

voltage level becomes too low.

Note 42

For all test cases relevant to the All shutdown mode, the service level is set at

the BSC accordingly using the MML command

‘ZEFM: <bcf _i d>: BBU=ALL; ’.


The site is in operational state with calls ongoingon all TRXs.


The mains breakdown alarm is generated. Alarm 7995:MAINS BREAKDOWN WITHBATTERY BACKUP is reported at the BSC andBTS Manager.

The calls remain ongoing.

The BSC does nothing in response to the

alarm.

Cancel the mains breakdown alarm after 5minutes.

Alarm 7995:MAINS BREAKDOWN WITHBATTERY BACKUP is cancelled at the BSCand BTS Manager.

All calls remain ongoing.

The process is repeated 5 times for consistency.

Case ref. Base station Type







The mains breakdown alarm is generated. Alarm 7995:MAINS BREAKDOWN WITHBATTERY BACKUP is reported at the BSC and

BTS Manager.

NTIM Timer (if set): The BSC starts the NTIM Timer. The set time for the NTIM timer expires.

The calls are handed over from the non-BCCH TRXs to the neighbour or to the BCCH TRX of the sector. When the hand-off timer started bythe BSC expires or all the calls have beenhanded off, the BSC sends theBTS_PWR_SUPPLY_CONTROL (switch off each non-BCCH TRX) message to the BTS.

BB hopping: If BB hopping, theBTS_CONF_DATA is sent which modifies thehopping groups as Non-hopping. The calls arehanded over to the neighbours.

The master TRX turns off the power of the TRXs mentioned in the‘BTS_PWR_SUPPLY_CONTROL’ message. Allthe non-BCCH Slave TRXs are put to BL-PWRstate indicating that these have been shutdown. The Master TRX and the BCCH TRXsremain operational.

Chained configuration: When all TRXs in theSlave BTSs are put to shutdown mode, theMaster TRX (Master BTS) switches off thepower to the Slave BTSs.

The state of the TRXs is verified on the BTSManager using the object/properties.

The state of the TRXs is shown as defined inNote 33

New calls are established on the BCCH TRXs. All calls are successful.

The mains breakdown alarm is cancelled whilethe site is in the ‘BCCH shutdown mode’ state.

The 7995:MAINS BREAKDOWN WITHBATTERY BACKUP is cancelled at the BSCand BTS Manager.

The BSC sends aBTS_PWR_SUPPLY_CONTROL (switch oneach non-BCCH TRX) message to the BTS.

All the non-BCCH Slave TRXs (and BTS(s)) areswitched back on. All the TRXs are initialisedand go to WO state.

All calls on the BCCH TRX remain ongoing.







New calls are established on the non-BCCH TRXs.

The new calls are successful.


Case ref. Configuration BCCH TRX Hopping Mode

1. 2+2, GSM+ EDGE1

2nd sector DFCA enabled with DFCA TRX

Master+Slave

RF hopping in 1st

sector

2. 4+4+4, GSM+EDGE+GSM/EDGE chainedconfiguration, common BCCH (BTS1 &BTS2)

Slave BB-hopping in all sectors

1 NTIM timer set using ZEFM: <bcf _i d>: NTI M=<NTI M_t i mer >;

GPRS synchronisation and data transfer in BTS


The site is in operational state. GP timeslots aredefined on a non-BCCH TRX. GPRS datatransfer is initiated using CS1 and CS2 codingschemes.

For test case 4, the GP timeslots are defined ona non-BCCH TRX of a BCCH sector and any TRX

of a non-BCCH sector.

The data transfer is successful.


NTIM Timer (if set): The BSC starts the NTIM Timer. The set time for the NTIM timer expires.

The calls are handed over from the non-BCCH TRXs to the neighbour or to the BCCH TRX of the sector. When the hand-off timer started bythe BSC expires or all the calls have been

handed off, the BSC sends the aBTS_PWR_SUPPLY_CONTROL (switch off each non-BCCH TRX) message to the BTS.


The state of the TRXs is shown as defined inNote 33.



55 (121)





The site is in a ‘BCCH shutdown mode’ state.

GPRS data transfer is initiated using CS1 andCS2 coding schemes.

The GP timeslots move to the BCCH TRX fromthe non-BCCH TRX.



The 7995:MAINS BREAKDOWN WITHBATTERY BACK-UP is cancelled at the BSCand BTS Manager.


All non-BCCH Slave TRXs (and BTS(s)) areswitched back on. All the TRXs are initialisedand go to WO state.


Caseref.

Configuration BCCH TRX

3. . 4 Omni TRX, EDGE1 Master

4. 2+2, Common BCCH1 Slave1 NTIM timer set using ZEFM: <bcf _i d>: NTI M=<NTI M_t i mer >;

EGPRS data transfer in BTS


The site is in operational state. GP timeslots aredefined on a non-BCCH TRX.

EGPRS data transfer is initiated using MCS-9coding scheme in UL/DL direction.



NTIM Timer (if set): The BSC starts the NTIM

Timer. The set time for the NTIM timer expires.

The calls are handed over from the non-BCCH TRXs to the neighbour or to the BCCH TRX of the sector. When the hand-off timer started bythe BSC expires or all the calls have beenhanded off, the BSC sends theBTS_PWR_SUPPLY_CONTROL (switch off each non-BCCH TRX) message to the BTS.









The site is in a ‘BCCH shutdown mode’ state.

For test case 5, EGPRS data transfer is initiatedusing MCS-9 coding scheme in the UL/DLdirection.

The GP timeslots move to the BCCH TRX fromthe non-BCCH TRX.

For test case 6, the GP timeslots will not moveto the BCCH TRX from the non-BCCH TRX, soEGPRS data transfer is not possible.



Alarm 7995:MAINS BREAKDOWN WITHBATTERY BACKUP is cancelled at the BSC

and BTS Manager.


All non-BCCH Slave TRXs (and BTS(s)) areswitched back on. All the TRX’ are initialisedand go to WO state.

For test case 5, the GP timeslots are back onthe TRXs for which EDAP is enabled.

EGPRS data transfer is initiated using MCS-9coding scheme in the UL/DL direction.



Caseref.

Configuration BCCH TRX EDAP enabled

5. 4 TRX Omni EDGE1

Master All TRXs

6. 4 TRX Omni EDGE1

Master TRX 3&41

NTIM timer set using ZEFM: <bcf _i d>: NTI M=<NTI M_t i mer >;

8.3 None shutdown mode

The purpose of this test case is to test the None shutdown mode without the

BTIM timer expiry.

Note 46

For all the test cases relevant to the None shutdown mode, the service level is

set at the BSC accordingly using the MML command

‘ZEFM: <bcf _i d>: BBU=NONE; ’.



57 (121)





The set time for the BTIM timer expires.

The calls are handed over from the BCCH TRXs to the neighbouring cells. When theHand-off timer started by the BSC expires or allthe calls are handed off, then the BSC sendsthe BTS_PWR_SUPPLY_CONTROL (switchOFF each TRX) message to the BTS.

The power to all the Slave TRXs is switchedOFF and the TRXs are put to BL-PWR stateindicating that these have been shutdown. TheMaster TRX remains powered but is set to BL-PWR state.

Chained configuration: When all TRXs in the

Slave BTSs are put to shutdown mode, theMaster TRX (Master BTS) switches OFF thepower to the Slave BTSs.



The mains breakdown alarm is cancelled whilstthe site is in the ‘None shutdown mode’ state.

The 7995:MAINS BREAKDOWN WITHBATTERY BACK-UP is cancelled at the BSCand the BTS Manager. The BSC sendsBTS_PWR_SUPPLY_CONTROL (switch ON all

TRXs) message to the BTS.All Slave TRXs (and BTS(s)) are switched backON. All TRXs are initialised and go to WOstate.

The calls handed over from the non-BCCH TRXs should get handed back once the TRXsare operational as handovers are in place.


All TRXs are shown as being in the supervisorymode.

New CS calls are set-up after the test case hasbeen finished.

The new calls are successful.


Case ref. Configuration Hopping Mode

3. 2 +2, EDGE+GSM RF hopping in 1st sector and BB hopping 2nd sector

4. 4+4+4 chain configuration,Common BCCH (BTS1 and BTS2)

3rd

sector DFCA enabled

RF hopping






8.4 BCF lock/unlock from the BSC

The purpose is to test the BCF lock and unlock functionality during Intelligent

Shutdown.


The site is in operational state. Make calls on all TRXs.


The mains breakdown alarm is generated. Alarm 7995:MAINS BREAKDOWN WITH

BATTERY BACKUP is reported at the BSC andBTS Manager. The NTIM timer is started. Thesite starts the shutdown procedure and entersthe ‘BCCH shutdown mode’ state. Calls fromNon-BCCH TRXs are handed over to theneighbours or a BCCH TRX.

The BCF is locked from the BSC while the site isin the ‘BCCH shutdown mode’ state.

Calls are released from the BCCH TRX(s). Thestate of the BCF is locked at the BSC.

BCCH transmission is stopped.

The state of the TRXs is verified at the BSC andat the BTS Manager (objects/properties).

All the TRXs at the BSC are shown as BL-USR.At the BTS Manager, the shutdown TRXs shall

still be reported as being in the shutdown stateas defined in Note 33.

The BCF unlock command is given. When the BCCH TRX is in a resetting state,alarm 7767 BCCH MISSING is active. Alarm7701 BCF INITIALIZATION is sent to the BSCwhile other alarms are cancelled. The BCFinitialises correctly.

After VIF and master TRXs have initialised allunits normally, alarm 7995:MAINSBREAKDOWN WITH BATTERY BACKUP isresent to the BSC and BTS Manager. The BSC

starts the NTIM timer. The NTIM timer expiresand the site enters the ‘BCCH shutdown mode’state.

New calls are established on the BCCH TRX(s). The calls are successful.


The site enters the ‘None shutdown mode’state.



61 (121)





The BCF is locked from the BSC while the site isin the ‘None shutdown mode’ state.

The state of the BCF is locked at the BSC.

The state of the TRXs is verified at the BSC andat BTS Manager (objects/properties).

All the TRXs are shown as BL-USR at the BSC.At the BTS Manager, the shutdown TRXs shallstill be reported as being in the shutdown stateas defined in Note 33.

The BCF unlock command is given. When the BCCH TRX is in a resetting state,alarm 7767 BCCH MISSING is active. Alarm7701 BCF INITIALIZATION is sent to the BSCwhile other alarms are cancelled.

The BCF initialises correctly.

After VIF and Master TRX have initialised allunits normally, alarm 7995:MAINSBREAKDOWN WITH BATTERY BACKUP isresent to the BSC and BTS Manager.

The BSC starts the NTIM timer. The NTIM timerexpires and the site enters the ‘BCCH shutdownmode’ state.

Case ref. Configuration Hopping Mode BCCH TRX

1. 4 Omni EDGE

DFCA enabledwith DFCA TRX

-Master

2. 4+4+4 chainconfiguration,Common BCCH(BTS1 andBTS2)

RF-hopping in all sectors Slave

8.5 BTS lock/unlock from the BSC

The purpose is to test the BTS lock and unlock functionality during Intelligent

Shutdown.










The mains breakdown alarm is cancelled. Alarm 7995:MAINS BREAKDOWN WITHBATTERY BACKUP is cancelled at the BSC

and BTS Manager. The BSC sends aBTS_PWR_SUPPLY_CONTROL (switch on all TRXs) message to the BCF for each BTS.

The remaining TRXs in the shutdown sectorsare restarted.

New calls are established on the unlocked TRX The calls are successful.

The unlocked TRX stays in WO.

Case ref. Config . Hopping Mode TRXLocked/

Unlocked

ShutdownMode

State

BCCHTRX

1. 2+2 EDGE RF hopping +BB

hopping

Non-BCCH2 TRX of 1

st

sector

BCCH Master

2. 2+2 EDGE

DFCA enabled with DFCA TRX

- BCCH None Slave

3. 4+4+4, Common BCCH(BTS1 and BTS2)

Non-hopping in allsectors

Non-BCCH1

BCCH Slave

1

Only test TRX in Non-BCCH BTS (Cabinet 2)2

Repeat with BCCH TRX

8.7 Site reset from BSC and BTS Manager

The purpose is to test the site reset functionality during Intelligent Shutdown.



All calls are successful



65 (121)





Shutdown mode used: BCCH

The mains breakdown alarm is generated.

Alarm 7995:MAINS BREAKDOWN WITHBATTERY BACK-UP is reported at the BSC and

BTS Manager. The site starts the shutdownprocedure and enters the ‘BCCH shutdown mode’state. Calls from Non-BCCH TRXs are handedover to the neighbours or a BCCH TRX as perNote 44.

The site is reset as detailed in the test case whilstthe site is in ‘BCCH shutdown mode’ state.

Calls are released from the BCCH TRX(s). BCCHtransmission is stopped.

When the BCCH TRX is in resetting state, alarm7767 BCCH MISSING is active. Alarm 7701 BCF

INITIALIZATION is sent to the BSC while otheralarms are cancelled.

The BCF initialises correctly.

After VIFA and Master TRX have initialised allunits normally, the alarm 7995:MAINSBREAKDOWN WITH BATTERY BACK-UP isresent to the BSC and the BTS Manager. TheBSC starts the NTIM timer. The NTIM Timerexpires and the site enters the ‘BCCH shutdownmode’ state.

The mains breakdown alarm is cancelled whilst

the site is in the ‘BCCH shutdown mode’ state.

The 7995:MAINS BREAKDOWN WITH

BATTERY BACK-UP is cancelled at the BSC andBTS Manager. The BSC sendsBTS_PWR_SUPPLY_CONTROL (switch ON all TRXs) message to the BTS.

All Slave TRXs (and BTS(s)) are switched backON. All TRXs are initialised and go to WO state.

New calls are established on all TRX(s). The calls are successful.

Shutdown mode used: None

The mains breakdown alarm is generated.

Alarm 7995:MAINS BREAKDOWN WITHBATTERY BACK-UP is reported at the BSC andBTS Manager.

The NTIM timer is started.

The set time for the NTIM timer expires.







The calls are handed over from the non-BCCH TRXs to the neighbour or to the BCCH TRX of the

sector. When the Hand-off timer started by theBSC expires or all the calls are handed off, thenthe BSC sends theBTS_PWR_SUPPLY_CONTROL (switch off eachnon BCCH TRX) message to the BTS. The BTIMtimer is started.

BB- hopping: If BB-hopping, then theBTS_CONF_DATA is sent which modifies thehopping groups as Non-hopping. The calls arehanded over to the neighbours.

The Master TRX turns off the power of the TRXs

mentioned in the‘BTS_PWR_SUPPLY_CONTROL’ message. Allnon-BCCH Slave TRXs are put to BL-PWR stateindicating that these have been shutdown. TheMaster TRX and the BCCH TRXs remainoperational.

Chained configuration: When all TRXs in theSlave BTSs are put to shutdown mode, theMaster TRX (Master BTS) switches off the powerto the Slave BTSs.

New calls are established on the BCCH TRXs. All calls are successful.


The calls are handed over from the BCCH TRXsto the neighbour cells. When the Hand-off timerstarted by the BSC expires or all the calls arehanded off then the BSC sends theBTS_PWR_SUPPLY_CONTROL (switch OFFeach TRX) message to the BTS.

The power to all the Slave TRXs is switched OFFand the TRXs are put to BL-PWR state indicatingthat these have been shutdown. The Master TRXremains powered but is set to BL-PWR state.

Chained configuration: When all TRXs in theSlave BTSs are put to shutdown mode, theMaster TRX (Master BTS) switches OFF thepower to the Slave BTSs.



67 (121)





The BCF unblock command is given from theBTS Manager.

The BCF initialises correctly. Alarm 7208LOCAL BLOCK: BCF is cancelled at the BSC

and BTS Manager.

After the VIFA and the Master TRX haveinitialised all units normally, alarm 7995:MAINSBREAKDOWN WITH BATTERY BACKUP isresent to the BSC and BTS Manager. The BSCstarts the NTIM timer. The NTIM timer expiresand the site enters the ‘BCCH shutdown mode’’state.

Case ref. Configuration Hopping Mode BCCH TRX

1. 2+2, GSM/EDGE BB hopping +RF hopping Master

2. 4+4+4 chainconfiguration,GSM+EDGE+GSM/EDGE

RF hopping in all sectors Slave

8.9 BTS block/unblock from the BTS Manager

The purpose is to test the BTS block and unblock functionality during

Intelligent Shutdown.




The mains breakdown alarm is generated. Alarm 7995:MAINS BREAKDOWN WITHBATTERY BACKUP is reported at the BSC andBTS Manager. The site starts the shutdownprocedure and enters the ‘BCCH shutdownmode’ state. Calls from Non-BCCH TRXs arehanded over to the neighbours or a BCCH TRX.

The BTS stated in the test case is blocked fromthe BTS Manager while the site is in the ‘BCCHshutdown mode’ state.

Calls are released from only the BCCH TRXunder the BTS blocked. All other calls remainongoing.

Alarm 7208 LOCAL BLOCK: BTS is sent to theBSC and BTS Manager.

The state of the affected BTS is BL-BTS at theBSC.








1. 2+2,EDGE+GSM

2nd sector DFCAenabled withDFCA TRX

RF hopping in 1st

sector BTS1 Master

2. 4+4+4 chainConfiguration

3rd sector DFCAenabled

RF hopping +BB hopping BTS31

Slave

1Repeat with BTS1 and BTS2

8.10 TRX block/unblock from the BTS Manager

The purpose is to test the TRX block and unblock functionality during

Intelligent Shutdown.




The mains breakdown alarm is generated. Alarm 7995:MAINS BREAKDOWN WITH

BATTERY BACKUP is reported at the BSC andBTS Manager. The site starts the shutdownprocedure and enters the ‘BCCH shutdownmode’ state. Calls from Non-BCCH TRXs arehanded over to the neighbours or a BCCH TRX.

The TRX stated in the test case is blocked fromthe BTS Manager while the site is in the ‘BCCHshutdown mode’ state.

Non-BCCH TRX: As the TRX is in theShutdown state, the option for TRXblock/unblock/reset is not enabled at the BTSManager.


BCCH TRX: Calls are released from only theBCCH TRX blocked. All other calls remainongoing.

Alarm 7208 LOCAL BLOCK: TRX is sent to theBSC and BTS Manager.

The state of the affected TRX is BL-TRX at theBSC.










The mains breakdown alarm is generated. Alarm 7995:MAINS BREAKDOWN WITHBATTERY BACKUP is reported at the BSC andBTS Manager. The site starts the shutdownprocedure and enters the ‘BCCH shutdownmode’ state. Calls from Non-BCCH TRXs arehanded over to the neighbours or a BCCH TRX.

BCCH Sector: The BTS comes up correctly.Only the BCCH TRX under the BTS unblockedis initialised.

The BTS reset command is given from the BTSManager for the BCCH BTS.

The BTS is not reset as all TRXs under the BTSare in the shutdown state. All the TRXs remainin the same state as before the BTS was reset.

The state of the TRXs is checked at the BTSManager (objects/properties).

At the BTS Manager, the shutdown TRXs shallstill be reported as being in the shutdown state. The BCCH TRX shall be reported asSupervisory.

New calls are established on the BCCH TRX(s). The calls are successful.



The same BTS is reset from the BTS Managerwhile the site is in the ‘None shutdown mode’state.

The BTS is not reset as all TRXs under the BTSare in the shutdown state. All the TRXs remainin the same state as before the BTS was reset.


At the BTS Manager, the shutdown TRXs shallstill be reported as being in the shutdown state

as defined in Note 33.

The test is repeated for all the BTSs.

Caseref.

Configuration Hopping Mode BCCHTRX

1. 4+4+4, common BCCH (BTS1 and BTS2) RF hopping in all sectors Master






8.12 TRX reset from BTS Manager

The purpose is to test the BCCH TRX reset functionality during Intelligent

Shutdown.


The configuration in use is as listed in the testcase.

The site is in operational state with calls ongoingon all TRXs.

The mains breakdown alarm is generated. Alarm 7995:MAINS BREAKDOWN WITHBATTERY BACKUP is reported at the BSC andBTS Manager. The site starts the shutdownprocedure and enters the ‘BCCH shutdown

mode’ state. Calls from Non-BCCH TRXs arehanded over to the neighbours or a BCCH TRX.

In case of BB hopping, calls are handed over toneighbours.

BCCH TRX: Calls are released from only theBCCH TRX reset. All other calls remainongoing.


The TRX is initialised correctly and goes to the‘WO’ state. The associated fan becomesoperational.

The TRX stated in the test case is reset from theBTS Manager while the site is in the ‘BCCHshutdown mode’ state.

Non-BCCH TRX: As the TRX is in Shutdownstate, the option for reset is not enabled at theBTS Manager.



At the BTS Manager, the shutdown TRXs shallstill be reported as being in the shutdown state.

The BCCH TRX is identified asSUPERVISORY.

New calls are established on the BCCH TRX The calls are successful.





75 (121)





The same TRX is reset from the BTS Managerwhile the site is in the ‘None shutdown mode’

state.

As the TRX is in Shutdown state, the option forreset is not enabled at the BTS Manager.


At the BTS Manager, the shutdown TRXs shallstill be reported as being in the shutdown state.

Case ref. Configuration Hopping Mode TRX Reset BCCHTRX

1. 2+2 EDGE+GSM RF BCCH Master

2. 2+2 EDGE RF hopping +BB hopping Non-BCCH of 1st sector

Master





Recovery for BSS and Site Synchronisation

9 Recovery for BSS and SiteSynchronisation

9.1 Site synchronisation recovery during start-up/resets

The purpose is to check that the base station initialises to the correct

synchronisation mode.

Note 47

Prior to S11 it was not possible for MetroSite to be synchronised from an

external LMU or base station. (Talk base stations used the jumper settings on

the BCFB to determine the sync mode when connected to a BSC running S10.)

In order for the network to recover automatically from a loss of synchronisation,

greater control is exercised by the BSC. So in S11 mode the base station is told

by the BSC in the BTS_CLOCK_REQ message which synchronisation mode it

should be in.


Define the synchronisation chain in the BSCusing the MML command:

ZEFM: <s1>: CS=LMU, SENA=T, ;

<s1> = sl ave 1 BCF number

Make the traffic channels full rate channels(TCHF). Lock all TCH channels except fortimeslot 2 on each TRX in the multi-BCFsegment.

Physically create and commission the sites.



77 (121)





Monitor the BTS Events window in the BTSManager, or the Messages and Alarms

window in the BTS MMI.

Monitor the Abis.

Reset the Slave BCF(s) using the MMLcommand:

ZEFR: <BCF No>;

The BSC sends the Slave BCF a BTS_RESET REQwith object identity =BCF.

The BCF resets and sends a BTS_OMU STARTEDmessage with synchronisation mode =as per table.

The BCF sends BTS_CONF_REQ to the BSC. TheBSC sends a BTS_LMU_FN_OFFSET COMMANDto the BCF next to the LMU. The BTS returns aBTS_LMU_FN_OFFSET_ANSWER with success-failure =success (assuming the LMU is operatingcorrectly).

The BSC sends a BTS_CLOCK_REQ to the BCFswith:

Clock sync = BTS_External

Clock output =disabled

The BSC sends the configuration of the sites inBTS_CONF_DATA messages. The BCFs come intoworking order. The BCFs send aBTS_CONF_COMPLETE. The BTS Events/MMIwindow shows that the BCF is in Slave mode andthat the LMU is Master.

Lock 8 MSs to the segment. Make 4 pairs of speech calls. Speak in both directions foreach call.

All calls set up correctly. The speech in eachdirection can be heard clearly.

The process is repeated 5 times forconsistency. The site’s behaviour is repeatable.

Case Ref. Conf ig. Sync Mode in BTS_OMU_STARTED

1. LMU+4+4 chain, RF hopping in both BTSsFigure 2..

LMU SW – FLY4.4

Independent






MASTER

BCCH

3 4

1 6

7 8

5

BTS2BTS1

LMU

SLAVE BCF1

SEGMENT

BTS 2Hop =RFMA =same as BTS 1HSN1 =same as BTS 1MAIO OFFSET =0MAIO STEP =2

BTS 1Hop =RFMA =xx (7 ARFN)HSN1 =yyMAIO OFFSET =1MAIO STEP =2

LMU – MetroSite - MetroSite

Figure 2.

The purpose is to check that a fault with a synchronisation cable does not cause

a failure beyond the site concerned. To check that once the fault has been

corrected, the site can be recovered.


Make the traffic channels full rate channels(TCHF). Lock all TCH channels except fortimeslot 7 on each TRX in the multi-BCFsegment.

ZEFM: <s1>: CS=LMU, SENA=T;

<s1> = sl ave 1 BCF number

Physically create and commission the sites, sothat they are in working order, synchronised tothe LMU.

Power off the sites.

Disconnect the LMU cable at the connectorindicated in the table.



79 (121)





Monitor the Messages and Alarms window in theBTS Events window in the BTS Manager.

Monitor the Abis. Record a trace.

Power on the BCF next to the LMU.

The BCF does not initialise and synchronise tothe LMU. The BCF comes up independently.

Record the status at the BSC using the MMLcommands:

ZEOL: <BCF number >;

ZEEI : BCF=<BCF number >;

Continue recording the Abis trace.

Re-connect the cable.

Make a note of changes in the alarm status.

The LMU clock output is switched ON.

Use LMU Manager ->Commissioning Wizard toensure that.

Power on the second cabinet.

Reset the BCF using the MML command

ZERF: <BCF number >;

The BCF comes into working ordersynchronised to the LMU.

All alarms caused by the fault are cancelled.

Check the sync mode at the BTS Manager Sync mode is slave.

Lock 8 MS to the segment. Make 4 pairs of speech calls. Speak in both directions for eachcall.


The process is repeated 5 times for consistency. The site’s behaviour is repeatable.

Case Ref. Configuration Connector to Disconnect

2. LMU+4+4 chain, RF hopping in both BTSs.Figure 2.

LMU SW – MIDGE1.0

BTS/Q1 IF

9.2 Site synchronisation recovery with GPS signal

recoveryThe purpose is to check that a previously synchronised chain behaves correctly

when the LMU’s GPS signal is lost and then returns. To check that the recovery

actions are not triggered if the GPS outage time is less than the LMU timer

period. To check that the base station responds correctly to the BSCs control

when the recovery actions are triggered by an outage longer than the LMU

timer period.







Camp 8 MSs on to the segment. Make sure theycan also see the neighbouring BTS. That is, it will

not be possible to use the MS field test softwareto lock them to the segment. Make 4 pairs of speech calls. Speak in both directions for eachcall. These calls will be left up during the testcase.

Also establish a further 2 MSs, each with a GPRStransfer ongoing.


Monitor the Q1 bus. Monitor the Abis for O&Mmessages.

Monitor the BTS Events window in the BTSManager, or the Messages and Alarms window in

the BTS MMI.Disconnect the GPS antenna from the LMU, orblock the antenna’s view of the satellite. At thesame time, start a stop-clock to monitor the lengthof time the GPS signal is missing.

The LMU sends a GPS fix lost alarm 48 on theQ1 bus. The BCF sends this up the Abis as an8048 alarm. However, the LMU does not send a1001 clock disable alarm. The BCFs continue tobe synchronised by the clock signal from theLMU.

Check the status of the calls and transfers.

Check the sync status at the BTS Manager/MMI.

Check the sync status at the BSC using the MMLcommand: ZEFL;

All calls remain up. Both GPRS transfersremain ongoing.

BCFs still show as being in slave mode.

Sync Enabled =T, Sync Mode =Sync for thesynchronisation chain.

At 3 minutes on the stop-clock, re-establish theGPS signal to the LMU.

The LMU sends an alarm 48 cancel on the Q1bus. The BCF forwards this as an 8048 cancelon the Abis. The BSC does not begin anyfurther recovery actions when it receives thisalarm.

All calls/transfers remain up. The BCFscontinue to be synchronised by the clock signalfrom the LMU.

At 4 minutes, monitor the Q1 bus. The LMU does not send any alarms. That is,the LMU timer was successfully reset.

The existing calls/transfers may be left up.Monitor the Q1 bus. Monitor the Abis for O&Mmessages.

Monitor the BTS Events window in the BTSManager, or the Messages and Alarms window inthe BTS MMI.

Disconnect the GPS antenna from the LMU, orblock the antenna’s view of the satellite. At thesame time, start a stop-clock to monitor the lengthof time the GPS signal is missing.

The LMU sends a GPS fix lost alarm 48 on theQ1 bus. The BCF sends this up the Abis as an8048 alarm. However, the LMU does not send a1001 clock disable alarm. The BCFs continue tobe synchronised by the clock signal from theLMU.







Check the status of the calls.

Check the sync status at the BTS Manager/MMI.Check the sync status at the BSC using the MMLcommand: ZEFL;

All calls remain up.

BCFs still show as being in slave mode.Sync Enabled =T, Sync Mode =Synch for thesynchronisation chain.

At 4 minutes on the stop clock, monitor the Q1bus and Abis.

The LMU sends alarm 1001 clocks outdisabled. The first BCF forwards this alarm upthe Abis to the BSC as:

Talk: 7876 LMU. External synchronisationsignals disabled.

Ultra/Metro: 7602 BCF Notification. Externalsynchronisation signals disabled. (Alarm detail=28.)

All calls hand over successfully to theneighbouring BTS. Both GPRS transferssuccessfully reselect the neighbouring BTS.

Check the status of the BCFs using the MMLcommand:

ZEEI : BCF = <BCF number >;

Immediately following the handover of calls, theBCF shows as BL-BCF or BL-SYS at the BSC.

Monitor the MMI and Abis for all of the BCF. The BSC resets the BCF in the chain. The BSCsends a BTS_CLOCK_REQ message on theAbis, with:

Clock sync =PCM_External

Clock output =Enabled.

The BCF comes into working order in mastermode.

Check the MS carrying the GPRS transfers. The MS reselects the BTS in the segment.

Check the sync status at the BSC for all BCF,using the MML command:

ZEFL;

Sync Enabled =T, Sync Mode =Unsync for allBCF in the chain.

Check for alarm 8048 GPS fix lost alarm at the

BSC using the MML command:ZEOL: < Sl ave BCF number >;

Alarm 8048 is still active.

Disconnect the calls now on the neighbour. Re-establish 4 pairs of calls on the segment. Speakin both directions for each call.




83 (121)





Monitor the Q1 bus and the Abis.

Re-establish the GPS signal to the LMU.

The LMU cancels alarm 48 on the Q1 bus andthis is forwarded by the BCF as a cancellation

of alarm 8048 on the Abis.

All calls hand over successfully to theneighbouring BTS. The GPRS transfersreselect the neighbouring BTS.

Check the status of the BCF using the MMLcommand:

ZEEI : BCF=<BCF number >;

Immediately following the handover of calls, theBCF shows as BL-BCF or BL-SYS at the BSC.

Monitor the MMI and Abis for all of the BCF. The BSC resets the first BCF in the chain. TheBSC sends a BTS_CLOCK_REQ message onthe Abis, with:

Clock sync = BTS_ExternalClock output =Disabled.

The BCF comes into working order in slavemode synchronised to the restored clock fromthe LMU.

Check the MS carrying the GPRS transfers. The MS reselects the BTS in the segment.

Check the sync status at the BSC for all BCF,using the MML command:

ZEFL;

Sync Enabled =T, Sync Mode =Sync for allBCF in the chain.

Disconnect the calls now on the neighbour. Re-establish 4 pairs of calls on the segment. Speakin both directions for each call.


Case Ref. Config.

1. LMU+4+4 in a segment, Figure 3., LMU SW – FLY4.4






MASTER

BCCH

3 4

1 6

7 8

5

BTS2BTS1

LMU

BCF 1

SLAVE

Set up hopping in the same way as in Figu re 2.

LMU – MetroSite – MetroSite + Neighbour

ADJ ACENT BCF

BTS 3 (not in sync chain)

The Segment is a neighbour of BTS 3andBTS 3 is a neighbour of the Segment.

BTS3

SEGMENT

Figure 3.

The purpose is to check that the synchronisation recovery actions are triggered

correctly by the clocks out alarm from the LMU while a different 7602 alarm is

active.


Define the synchronisation chain in the BSCusing the MML command:ZEFM: <s1>: CS=LMU, SENA=T<s1> = sl ave 1 BCF number

At LMU Manager, select View→ Advanced.Select Maintenance and open the “Clock Out Time Settings…” dialogue box. Set the Time fromfix lost to clocks out alarm to 10 sec. Set the Timefrom clocks out alarm to clock disable to 60 sec.Physically create and commission the sites so

that they are synchronised to the LMU.Cause a 7602 alarm to be raised by:

Remove the fan unit.Alarm7602 BCF Notification. Fan unit is broken is raised.

Monitor the Q1 bus. Monitor the Abis.

Block the LMU GPS antenna’s sight of thesatellites (or disconnect the GPS antenna fromthe LMU).

The LMU sends a GPS fix lost alarm 48 on theQ1 bus. The BCF sends this up the Abis as an8048 (loss of incoming signal) alarm.



85 (121)





The connection previously used on the MetroSiteBTS is changed to an UltraSite BTS.

The BTS Manager successfully restarts withouthaving to close the BTS Manager between the

BCF cable changes. The correct BCF-relatedmenu commands, toolbar buttons, and windowsare available. Alarm 7801 MMI CONNECTED TOBASE STATION is sent to BSC and MMI.

The BTS manager is disconnected.

Click on Connection -> disconnect menu item

The BTS Manager is disconnected successfully.Alarm 7801 MMI CONNECTED TO BASESTATION is cancelled at the BSC.

Case Ref. Site Type/Configuration Operating System in PC

01 Nokia MetroSite

Multi TRX EDGE/GSM

Windows 98

02 Nokia MetroSite

Multi TRX EDGE/GSM

Windows 2000

03 Nokia MetroSite

Chain Configuration

Windows XP

10.2 Access rights in local mode

Purpose:

To check that MMI users have full access to the BTS Manager commands

irrespective of the UALC feature when locally connected to the BTS.

Note 50

Under the ‘Supervision’ menu of the BTS Manager, submenus like ‘BB2-TsX

Connection’, ‘TSx Cabling’ and ‘Antenna Cabling’ are not applicable for

MetroSite.


Launch the BTS Manager application. The BTS Manager launched successfully.







Right-click on the TRX object in theequipment view.

The context menu pops up.

‘Object Reset’ menu item is enabled.Either ‘Object block’ and ‘Object Unblock’ menu items areenabled depending on the current state of the object.

Right-click on the TRX object in theLogical view.


‘Object Reset’ menu item is enabled.

Either ‘Object block’ and ‘Object Unblock’ menu items areenabled depending on the current state of the object.

Click on ‘Supervision’ menu. The Supervision menu drops down.

All submenus, that is, ‘External Devices’, ‘Show HistoryAlarms’, ‘Filter Alarms’, ‘View Site Configuration, ‘EAC

States’, IDD Information’, ’BB2-TsX Connection’, ‘TSxCabling’, ‘Antenna Cabling’, ‘RSSI Comparison value’and ‘Site Information’ are enabled.

Click on the ‘Supervision’->‘EACStates…’ menu item.

The EAC States dialog box opens

Click on the ‘Outputs’ tab. The Outputs sheet opens showing the outputs and theirstates.

The ‘Set Outputs’ button is enabled.

Click on the ‘Supervision’ ->IDDInformation menu item.

The IDD Information dialog box opens up.

‘Send IDD’ button is enabled.

Click on the ‘Test’ menu. The ‘Test’ menu drops down.

‘TRX test…’ and ‘TRX Loop test…’ menu items areenabled and TRX test is possible.

‘TRX Traffic Trace..’ menu is enabled and showingcorrect information.

Click on the ‘Tools’ menu All submenus are enabled.

Note: Some of the menu items such as Launch HubManager, or Update Abis Allocation are enableddepending on the actual configuration of the BTS.

Case Ref. Site Type/Configuration

1. Nokia MetroSite

Any





BTS Manager functionality

10.3 BTS SW menu commands

The purpose of these tests is to verify that updating the BTS SW works

correctly.


The Abis is not connected. The BCF is reset.

TheBTS SW | Update… command is selected. The master file that is not already downloaded tothe BCF (CXM5) is selected and downloading isstarted.

The SW is downloaded from the PC to the BCF.

SW versions are requested. The SW version report shows that thedownloaded SW is in the flash memory but notas the "Running Package".

The BCF is started with the new SW.

SW versions are requested. The SW version report shows that thedownloaded SW is in the flash memory as thecurrently used SW.

The SW that was locally enabled is active at theBSC. The Abis is connected and the BCF is madeoperational.

The BCF starts up. No SW downloading takesplace.

From the BTS Manager, the BTS SW | Updatecommand is selected. The master file that isalready in the BCF is selected and the loading

sequence starts.

The SW is not loaded to the BCF. The user isinformed that the SW is already in the flashmemory and the SW is taken into use from the

flash memory.From the BTS Manager, the BTS SW ⎪ Update command is selected. The file, which is not amaster file, is selected.

The user is informed that the selected file is nota master file.

From the BTS Manager, the BTS SW ⎪ Update command is selected. A master file, which hasmissing application files, is selected.

The user is informed that an application file forthe selected master file does not exist. The SWdownload is not attempted.

Calls are made and alarms are checked. No unexpected alarms are active. The calls aresuccessful.


1. Any




91 (121)





The Abis is not connected, The BCF is reset, andthe SW is started with the BTS SW | Use Current

command.

TheBTS SW ⎪ Update command is selected.

The new master file, which is not already in theBCF, is selected and loading is started.

When the SW is downloading, the BTS Managercable is disconnected for one minute and thenreconnected to the BCF.

The SW loading is interrupted when the LMPcable is removed.

The old SW is still loaded in the BCF.

SW versions are requested. The SW version report shows that the old SW isstill in the flash memory and is running thepackage.

From the BTS Manager, the BTS SW ⎪ Update command is selected.

A master file, which is for a different type of BCF,is selected (that is, a master-file for an UltraSiteBTS is attempted to be downloaded in aMetroSite BTS).

The SW loading is not started. The user isinformed that the file is not a MetroSite masterfile.

SW versions are requested. The SW version report shows that the old SW isstill in the flash memory and is the runningpackage.


2. Any

The purpose of these tests is to verify that replacing the BTS SW works

correctly.


The Abis is not connected. The BCF is reset fromthe BTS Manager.

The BCF is in the ‘Waiting for LAPD’ state.

TheBTS SW ⎪ Replace… command is selected. The master file that is not already downloaded to

the BCF is selected and downloading is started.

The SW downloading is started and the SW isdownloaded to the BCF. The BCF is initialised

with the new SW.SW versions are requested. The SW version report shows that the SW

package is in the flash memory as the "Newestin flash" and "Running package".

The BCF is reset from the BTS Manager. The BCF is initialised with the same SW.







TheBTS SW ⎪ Replace… command is selectedfrom BTS Manager.

The master file that is already downloaded to theBCF is selected and downloading is started.

When the loading is ongoing, the power cable isdisconnected and then reconnected from theBCF.

The connection to the BTS is lost when thepower cable is disconnected. The SW

downloading stops and is not restarted.

SW versions are requested. The SW version report shows that the SWpackage is in the flash memory as the "Newestin flash" and "Running package".

The BCF is reset from the BTS Manager. The state of the BCF will be “Waiting for LAPDstate”.

TheBTS SW ⎪ Replace… command is selected.

The master file that is already downloaded to theBCF is selected and downloading is started.

When the downloading is ongoing, the BTSManager cable is disconnected. The cable isreconnected.

The SW downloading is interrupted and is notresumed when the cable is reconnected.

Note: if the cable is disconnected for a veryshort time (<<1 second), the SW downloadingmay not be interrupted.

When the downloading is interrupted, the oldSW is still loaded in the BCF.

The BCF is reset from the BTS Manager. The state of the BCF will remain as “Waiting forLAPD state”.

TheBTS SW ⎪ Replace command is selected.

A master file, which is for a different type of BCF,is selected (that is, a master-file for an UltraSiteBTS is attempted to download in a MetroSiteBTS).

The SW loading is not started.

SW versions are requested. The SW version report shows that the old SW isstill in the flash memory and is the runningpackage.


3. Any

10.4 BTS manual commissioning

The purpose of these tests is to check that a BTS can be manually

commissioned with the BTS Commissioning Wizard.




93 (121)





TheObjects | Disable Abis command is selected. The BCF is reset (a warning message appearsbefore the reset) and connection to the BSC is

lost. Calls are released.

The Status bar at the bottom of the Supervisionwindow indicates: "O&M link disabled" and"Telecom not working".

The status of the LAPD Link is requested. The states of the OMUSIG and TRXSIG links arereported to be in 'Off' state.

TheObjects | Enable Abis command is selected. The BCF is reset. Abis connection is established.O&M link is enabled and Telecom is working.

The status of the LAPD Link is requested. The states of the OMUSIG and TRXSIG links arereported to be in the 'On' state.

A call is set up in the BCF. The call is successful.

From the Menu command, default option forattempting the connection is selected to allowlocal connection at start-up. The BTS Manager isclosed and restarted.

The BTS Manager is connected to the BCF afterstart-up.

The BTS Manager is ‘Disconnected’ from theMenu command. The BCF is restarted from theBSC.

The BCF comes to WO state. The BTS Managerconnection is not established.

The BTS Manager is restarted. The Objects |Disable Abis command is selected.

The BTS Manager is connected to the BCF afterstart-up. The BCF is reset (a warning messageappears before the reset) and connection to the

BSC is lost. The call is released. The Status bar at the bottom of the Supervisionwindow indicates: "O&M disabled" and "Telecomnot working".

The SW is loaded to the BCF with the BTS SW | Replace command from the BTS Manager.

The SW can be loaded to the BCF when the Abisis disabled.

The BCF is reset when the SW has beendownloaded. Abis connection is established.

The Status bar at the bottom of the Supervisionwindow indicates: "O&M enabled" and "Telecomworking".

The status of the LAPD Link is requested. The states of the OMUSIG and TRXSIG links arereported to be in the 'On' state.

Case Ref. Configuration Transmiss ion Unit

1. Any FC E1/T1 (with release ITN C1.0).

2. Any FXC E1 (with release ITN C3.0)



99 (121)




10.6 Adjust ing the DAC word

The purpose of this test is to verify that the DAC word can be adjusted

correctly.

Note 51

The 13 MHz clock output is monitored with a frequency counter.


TheObjects | Clock Control command is selected. The DAC word is adjusted and ‘Set As Current’ ischosen.

The change in frequency can be seen from thefrequency counter. The DAC word can beadjusted.

‘Use Fine Scale’ is chosen. The DAC word isadjusted and ‘Save Current Permanently’ ischosen. The window is closed and re-opened.

The DAC word can be adjusted and savedcorrectly.

TheObjects | Clock Control command is selected.‘Disable BTS adjustment’ is selected. The DACword is adjusted. The new DAC value is set asthe current value by choosing ‘Set as Current’.Now ‘Save Current Permanently’ is chosen.

The DAC word can be adjusted and savedcorrectly.

The BCF is left running for at least 20 minutes. The frequency stays constant.

The site is reset. The BTS comes up into working state. The BTSwill automatically adjust the frequency tosynchronise with the Abis.


1. Any

10.7 FC E1/T1, FXC E1 and FXC E1/T1 transmissionmenus

The purpose of these tests is to ensure that the commands in the Transmissionmenu work correctly when an FC E1/T1, FXC E1/T1 or FXC E1 transmission

card is installed in the BTS.


The BCF is operational.

TheLIF Settings command is selected. The LIF Settings dialogue contains one page foreach line interface.







The incoming LIF page is selected and CRC isset not to be used.

The 8179 FAR-END alarm is started.

The Alarms command is selected from the Transmission menu.

Alarm 8179 is shown for the correct location.

TheLIF Settings command is selected and CRCset to be in use.

Alarm 8179 is cancelled.


Alarm 8179 is not shown.

Some test calls are made. The calls are successful.

TheSynchronisation command is selected fromthe Transmission menu. An interface, which is notused, is selected to be the interface for

synchronisation. (For the FXC tests, the secondpriority 2 option for synchronisation must be set to‘Internal Timing’.) The Alarms command isselected from the Transmission menu.

Alarm 8112 is started after some time.

TheSynchronisation command is selected andthe used interface is selected to be the interfacefor synchronisation.

Alarm 8112 is no longer shown.

The test is repeated for all interfaces. Thisrequires the Synchronisation, LIF, and TrafficManager settings to be redefined and the BCF tobe reset.

ConfigurationCase Ref. Transmission Card Transmiss ion SW

4. Any1 FC E1/T1 ITN C1.0

5. Any FXC E1/T1 ITN C3.0

6. Any FXC E1 ITN C3.01

The Synchronisation command is not executed for an FC transmission card.

10.8 FXC RRI transmission menus

The purpose of these tests is to ensure that the commands in the Transmission

menu work correctly when an FXC RRI transmission card is installed in the

BTS.









TheUnit Settings command is selected. The Unit Settings dialogue contains pages forthe Flexibus interface(s) and Platform Interface.

The incoming Flexibus page is selected, and theinterface is set not to be used.

Alarm 8125 loss of synchronisation signal isstarted.



TheUnit Settings command is selected, and theincoming interface is set to be used.

Alarm 8125 is cancelled. Alarm 8081 LOSS OFFRAME ALIGNMENT might be started andcancelled.



Case Ref. Configuration Transmiss ion Unit Transmiss ion SW

1. Any FXC RRI ITN C3.0



TheUnit Settings command is selected. The Unit Settings dialogue contains pages forthe Flexibus interface(s) and Platform Interface.

The Platform Interface page is selected and, forthe incoming Platform Interface, the CRC is setnot to be used (from the CRC in USE column with

the right mouse button).

Alarm 8179 FAR-END ALARM is started.



TheUnit Settings command is selected and CRCis set to be in use again.

Alarm 8179 is cancelled.



TheSynchronisation command is selected fromthe Transmission menu.

An interface, which is not used, is selected to be

the interface for synchronisation (for the FXCtests, the second priority 2 option forsynchronisation must be set to ‘Internal Timing’).

Alarm 7601 BCF OPERATION DEGRADED is

started after some time.


Alarm 8112 FREQUENCY ERROR is shown.

TheSynchronisation command is selected andthe used interface is selected to be the interfacefor synchronisation.

Alarm 7601 is cancelled after some time.



103 (121)







The test is repeated for different interfaces. Thisrequires the Synchronisation, LIF and TrafficManager settings to be redefined and the BCF tobe reset.

Configuration Transmission Unit Transmiss ion SWCase Ref.

2. Any FXC RRI ITN C3.0

10.9 Window menu commands

The purpose of this test is to ensure that the commands in the Window menu

work correctly. The Window menu commands pertain to the administration of

the various windows in the PC application, and to the functionality of the BCF.



The main application window, BTS Events,Alarms, and Supervision windows aremanipulated in different ways. The windows aremoved, resized, minimised or maximiseddifferently.

The administration of the different windowsworks correctly.

The BTS Manager is closed and then restarted. All windows are located as they were when theBTS Manager was closed.

Each type of window is activated one by one fromthe Window menu.

The selected window is activated.

The Arrange command is selected from theWindow menu.

The windows are arranged inside the mainapplication window at the default positions.

The BTS Manager is closed and then restarted. All windows are located as they were when theBTS Manager was closed.

ConfigurationCase Ref.

1. Any






10.10 BTS Manual Commissioning with FXC RRI

Purpose:The purpose of the test is to check that a BTS can be manually commissioned

with FXC RRI with FlexiHoppers in both flexbus interfaces with the BTS

Commissioning Wizard.

Extra HW/Tools :

MetroHub


The BTS is not commissioned.

The BCF, BTS, and TRX objects are created inthe BSC. The D–channels are unblocked by MMLcommands.

The D–channels are not in WO–EX state sincethe BTS is un-commissioned.

TheCommissioning Wizard command is selectedfrom the BTS Manager.

The Manual Commissioning method is selectable,but the Undo Commissioning method cannot beselected from the BTS Commissioning Wizardpage.

The Manual Commissioning method is selectedand the Next button is pressed.

The Site Name, Site ID, BCF ID and BSC IDvalues are given.

The Site and BSC identification data can beentered.

The LIF Settings command is selected and thecorrect unit settings are given.

The Settings dialog box is opened and it containsFlexbus page for each flexbus interface and thePlatform Interface page. The Unit settings aresent to the transmission unit.

The Synchronization command is selected andthe correct synchronization settings are given.

The synchronization settings are sent to thetransmission unit.

The Next command is selected.

The Radio Link Settings page is open and theNext button is disabled until at least radio hop isset ready with Radio Hops command.

The Radio Hops command is selected. The Flexbus Settings page is opened. The indoorunit type is shown correctly (FXC RRI). Flexbus1and Flexbus 2 units are shown correctly.

For used flexbus or flexibuses the correctcapacity is selected and the Next command isgiven.

The Flexbus <n>– FlexiHopper Settings page isopen.

The value of <n>in the title of the page dependson which flexbus interface is undercommissioning.



105 (121)





The correct TX Frequency and Maximum TX andthe TX Power On are given.

The Next command is selected. The MonitoringHop page is open.

The BER value and status for outdoor unit(s) areshown correctly.

The Report command is selected. The content of the report is correct.

The Next button is selected. The test continues.

The Transmission Configuration page is open. The Back button is enabled until the Abis TSallocation has been given in the Traffic Managerdialog box.

The Traffic Manager command is selected andthe Abis timeslot allocation is entered.

The timeslot allocation can be made with the Traffic Manager.

The correct Abis timeslot allocation is entered andapplied with OK.

The Traffic Manager dialog is closed. The Nextand Back buttons cannot be selected in the Transmission Configuration page.

The BCF initialisation begins. The connectionbetween the BTS and BSC is established, the SWis loaded from the BSC if necessary andconfiguration data and system information isreceived from the BSC.

The BTS initialisation progress can be seen fromthe Transmission Configuration page. The showninformation is checked.

Finally the BCF enters the 'Configuring' state.

The BTS Test Reporting page is automaticallyopened when the commissioning tests arestarted. The TRX tests and Abis loop tests arerun automatically by the BSC. The test progresscan be followed and the results can be seen inthe BTS Test Reporting page.

The BTS HW Information is requested from theBTS. The BCF enters the 'Supervisory' state andthe BTS Manager waits for possible alarms for awhile. These events can be seen in the BTS TestReporting page. The Next button is disabled untilall these events have occurred.

The Next command is selected. The EAC Input Settings page is opened.

The used EAC inputs are marked as 'in use'. Thestate of EAC inputs are changed.

When the functionality of in-use EAC inputs isverified, they are marked as 'checked'.

When the EAC input changes this is reflected onthe EAC Input Settings page.

The EACs can be marked as 'checked' when theyare marked as 'in-use'.

The Next command is selected. The EAC Output Settings page is opened.







The used EAC outputs are marked as "in use". The EAC output states are changed using the Set

Outputs button.

When the functionality of all in-use EAC outputsare verified they are marked as "checked".

When the state of the EAC output is changed it isreflected on the EAC output.

The EAC output can be marked as 'checked'when they are marked as 'in-use'.

The Next command is selected. The BTS Commissioning Report page is opened.

The commissioning report is checked and the filename is defined.

The contents of the commissioning report arecorrect.

The contents of the report are the following:

– Commissioning mode and network time

– BTS logical configuration

– Telecom status in TRXs

– HW versions and SW versions

– EAC inputs and outputs test

– LIF and Synchronization settings

– Timeslot allocation

– BTS test results

– BTS alarms test (unexpected alarms)

– External TREs in Q1 port

The commissioning report header contains timestamps based on the PC time. BSS/NSS time isincluded in the commissioning report in theNetwork Time field.

The Finish command is selected. The commissioning report is saved to the definedlocation with the specified name. The manualcommissioning procedure is finished.

The contents and format of the commissioningreport file is checked.

TheObject Properties command is selected. The TRXs are 'Waiting for System Info' andlocked.

The TRXs, BTS(s) and BCF are unlocked fromthe BSC.

The BCF becomes operational with all configured TRXs and BTS(s).

Test calls are made in all timeslots of all TRXs. The test calls are successfully carried out.

All BTS logical objects (BCF, BTS, and TRX) arein state WO in the BSC.

The D–channels are in state WO–EX in the BSC.

Case Ref. Transmission Configuration



107 (121)





1. FXC RRI with FlexiHoppers in both flexbus interfaces, FXC RRI SW ITN C3.0, MetroHubSW MHB C3.0





Remote BTS Manager

11 Remote BTS Manager 11.1 Remote BTS Manager start-up

The purpose of these test cases is to verify that the Remote BTS Manager can

successfully be started. It is accessible if a correct NMS password is provided

and can only be used with the CX family BTSs. Also, only one BTS Manager

connection is accessed at a time and a local connection has higher priority over

a remote connection.


Automatic connection option is disabled. RemoteBTS Manager connection is made from a PC viaNetAct and BSC using the Nokia GCS connection

tool.

The Remote BTS Manager starts successfully.

Remote connection to BTS Manager of therequested BCF is disconnected. Alarm ‘7801REMOTE MMI CONNECTED TO BASESTATION’ is cancelled at the BSC.

Remote BTS manager is disconnected.

Click on ‘Connection’ ->disconnect menu item.

When the connection dialogue window appears,incorrect password for the NMS is given. All theremaining data in the connection and nodewindows is correct.

The Remote BTS Manager is not started, as thepassword for the NMS must be given correctlyto start the BTS Manager remotely.

The Remote BTS Manager connection is retriedwith an incorrect Q1 address with the remaining

correct data.

The Remote BTS Manager is not started, as theQ1 address must be given correctly to start the

BTS Manager remotely. The connection is tried with the correct passwordand with the correct Q1 address. The Q1 addressvalue can be observed with the ZQWL commandat the BSC (default is 4001).

The remote connection to the BTS Manager of the requested BCF is established. Alarm 7801MMI CONNECTED TO BASE STATION israised at both the BSC and the Remote BTSManager.



109 (121)





The Remote BTS Manager is disconnected.

Click on ‘Connection’ ->disconnect menu item.

The remote connection to the BTS Manager of the requested BCF is disconnected. Alarm 7801

MMI CONNECTED TO BASE STATION iscancelled at the BSC.

The BTS Manager is started from a remote PCvia NetAct and BSC. The correct data is given inthe connection window and the node window.

The remote connection to the BTS Manager of the requested BCF is established.

A second remote connection to the BTS Managerof the same BCF is started.

The second remote connection to the BTSManager is unsuccessful.

The BTS Manager of the same BCF is startedlocally.

The local BTS Manager is started and thecurrent Remote BTS Manager is cancelled.

Another remote connection to the BTS Managerof the same BCF is started.

The Remote BTS Manager is unsuccessful andthe local BTS Manager stays connected.

Case Ref. Configuration Operating System in PC

1. Multi TRX EDGE/GSM Windows 2000

2. 3 Cabinets in chain Windows 2000

3. Multi TRX EDGE/GSM Windows XP


Automatic connection option is disabled. TheRemote BTS Manager connection is made from aPC via NetAct and BSC.


The Remote BTS Manager application is closedfromFile|Exit. The Remote BTS Managerapplication is started again.

The Remote BTS Manager starts successfully.Connection to the BCF is made successfully.

Reset the BCF. During the reset, the BCF connection is lost andis regained when the BCF comes into workingstate.

Manually disconnect the BCF connection from theBTS Manager application.

Reset the BCF.

The Remote BTS Manager connection to the BCFis not established even after the BCF comes intothe working state.

Enable the automatic local connection feature onthe Remote BTS Manager and terminate theapplication. Restart the Remote BTS Managerapplication.

As there is no connection at local port, ‘NoConnection to the BCF’ is displayed.

Connect the application as remote connection, tothe BCF.


ConfigurationCase Ref. Transmiss ion Unit Transmission SW

4. Any FC E1/T1 ITN C1.0





Remote BTS Manager


5. Any FXC E1/T1 ITN C3.0

11.2 Access rights in case of Remote connection

Purpose:

To check that the BTS Manager grants full access to all its read and writes

operations to the MMI user in case Remote connection is established with the

BTS and UALC is disabled.

Note 52

Under the ‘Supervision’ menu of the BTS Manager, submenus like ‘BB2-TsX

Connection’, ‘TSx Cabling’ and ‘Antenna Cabling’ are not applicable for

MetroSite.


The User Access level Control feature is disabled

Launch the BTS Manager application andestablish remote connection to the BTS.

The BTS Manager is launched successfully.

The remote BTS gets connected and the BTSManager shows the Equipment view, alarms viewand Events Window.

Click on the File ->Options menu item The Options dialog box opens up.

Tab for setting ‘BTS Password’ is available andthe checkbox ‘Use BTS password’ is enabled.

Check the commissioning menu to do thecommissioning.

The Commissioning menu is disabled.

Click on the menu item ‘BTS SW’ The BTS SW drop-down menu appears.

Submenus ‘Use Current’, ‘Update…’, and

‘Replace…’ are disabled.

Click on the ‘Object’ menu. The Object drop-down menu appears.

‘Clock Control’ is enabled and working properly.

‘Enable Abis’ ‘Disable Abis’ menu items aredisabled.



111 (121)





Click on Objects ->Properties menu item The Object Properties dialog box opens upshowing the various properties of the BCF.

The ‘Reset’ button is enabled and workingproperly.

‘Object block’ and ‘Object Unblock’ menu itemsare disabled.

Right-click on the TRX object in the equipmentview.


The ‘Object Reset’ menu item is enabled andworking properly.

‘Object block’ and ‘Object Unblock’ menu itemsare disabled.

Right-click on the TRX object in the Logical view. The context menu pops up.

The ‘Object Reset’ menu item is enabled andworking properly.

Object block’ and ‘Object Unblock’ menu itemsare disabled.

Click on the ‘Supervision’ menu. The Supervision drop-down menu appears.

All submenus, that is, ‘External Devices’, ‘ShowHistory Alarms’, ‘Filter Alarms’, ‘View SiteConfiguration, ‘EAC States’, IDD Information’,’BB2-TsX Connection’, ‘TSx Cabling’, ‘AntennaCabling’, ‘RSSI Comparison value’, and ‘Site

Information’ are enabled and working.Click on the ‘Supervision’->‘EAC States…’ menuitem.

The EAC States dialog box opens

Click on the ‘Outputs’ tab. The Outputs sheet opens showing the outputsand their states.

The ‘Set Outputs’ button is enabled.

Click on the ‘Supervision’ ->IDD Informationmenu item.

The IDD Information dialog box opens up.

‘Send IDD’ is enabled and working.

Click on the ‘Tests’ menu. The ‘Tests’ drop-down menu appears.

‘TRX test…’ and ‘TRX Loop test…’ menu itemsare enabled and working.

The ‘TRX Traffic Trace’ menu is enabled andworking.

Click on the ‘Tools’ menu. All submenus are enabled, provided respectivehardware is connected. Otherwise they aredisabled.

Case Ref. Site Type/Configuration





Remote BTS Manager


01 Nokia MetroSite

Any



113 (121)




12 Improved TRX Test Presentation Note 53

In the Improved TRX Test Presentation feature the representation of the string

‘Main Sensitivity’ & ‘Diversity Sensitivity’ of TRX Test dialog, TRX Testreport, commissioning report, BTS events window and Online help menu is

changed to ‘Main Rx Results’ & ‘Diversity Rx Result’, respectively.

12.1 Improved TRX Test Presentation in the TRX TestReport

12.1.1 Improved TRX Test Presentation in the TRX Test Report when TRX

Test is executed from BTS Manager

Purpose

To check that the TRX Test dialog box, BTS events window and TRX Test

report showing the changed TRX Test presentation and TRX test is successful

while the TRX test is executed from the BTS Manager.


All TRXs to be tested are in supervisory state.

A call is made using the TRX and TS to be tested. The call is successful and audio quality is good. The BTS Manager application is launched. The BTS Manager application is launched

successfully.

Click on the “File->Options…” menu. The BTS Manager application displays Options dialog box.

Select the File Handling tab and check the UseTest Log check box.

The BTS Manager application displays select LogFile name dialog box.





Improved TRX Test Presentation


Create the log file at a particular path & click on thesave button.

The BTS Manager application closes select LogFile name dialog box.

Click the OK button of the Options dialog box. The BTS Manager application closes Options dialog box.

Select the 'TRX Test…' menu item from the 'Tests' pull down menu on the main menu bar.

The BTS Manager application displays the TRXTest dialog box.

‘Main RX Results’ & ‘Diversity RX Results’ can beseen in place of ‘Main RX Sensitivity’ & ‘DiversityRX Sensitivity’, respectively, in the TRX Test dialog box.

Check the “Display Also in BTS Events window”check box and select the TRX from the TRX No. combo box and time slot from the Radio Timeslotcombo box. Click on the start button of the TRX Test dialog box.

The BTS Manager application runs the TRX Test. The TRX Test is successful and results areshown correctly, that is, the correct stringinformation (Main Rx Result & Diversity RxResult) is displayed in the BTS Events window.

Open the Test Log file. The Test Log file opens displaying the correctstrings for ‘Main Rx Result’ & ‘Diversity RxResult’ in place of ‘Main Sensitivity’ & ‘DiversitySensitivity’, respectively.

A call is made using the tested TRX and TS. The call is successful and audio quality is good.

The test is to be carried out for all TRXs

BTS Type/ConfigurationCaseRef.

1 Nokia MetroSite

Multi TRX

12.1.2 Improved TRX Test Presentation in the TRX Test Report when TRXTest is executed from Remote BTS Manager

Purpose:

To check that the TRX Test dialog box, BTS events window and TRX Testreport show the changed TRX Test presentation and the TRX test is successful

when the TRX Test is executed from the Remote BTS Manager.

Note 54

Either UALC should be disabled or the user should have full access rights.




115 (121)




12.1.3 Improved TRX Test Presentation in the interrupted TRX TestReport

Purpose:

To check that the TRX test results are correctly shown even on interruption and

to verify the functionality of the Improved TRX Test Presentation feature at the

BTS Manager.


All TRXs are in supervisory state.

Calls are made on the TRX be tested. The calls are successful and audio quality isgood.

The BTS Manager application is launched The BTS Manager application is launchedsuccessfully.

Click on the “File->Options…” menu. The BTS Manager application displays theOptions dialog box.

Select the File Handling tab and check the Use TestLog check box.

The BTS Manager application displays theselect Log File name dialog box.

Create the log file at a particular path & click on thesave button.

The BTS Manager application closes ‘selectLog File name’ dialog box.

Click the OK button of the Options dialog box. The BTS Manager application closes theOptions dialog box.

Select the 'TRX Test…' menu item from the 'Tests'pull down menu on the main menu bar.

The BTS Manager application displays theTRX Test dialog box.

Changed strings information displays ‘MainRX Results’ & ‘Diversity RX Results’ in placeof ‘Main RX Sensitivity’ & ‘Diversity RXSensitivity’ respectively in the TRX test dialogbox.

Check the “Display Also in BTS Events window”check box and select the TRX from the TRX No. combo box and time slot from the Radio Timeslot combo box. Click on the start button of the TRX Test

dialog box.

The BTS Manager application runs the test.

The TRX test is interrupted as defined in the Testcases

TRX Test Failed.

See the BTS events window. The test result shows ‘Failed’ and displays thecorrect string information ‘Main Rx Result’ &‘Diversity Rx Result’.



117 (121)





Open the Test Log file. The test result shows ‘Failed’

TheTest Log file opens and displays thecorrect string for ‘Main Rx Result’ & ‘DiversityRx Result’ in place of ‘Main Sensitivity’ &‘Diversity Sensitivity’, respectively.

Failure Action is removed and TRX lock/unlockcommand is given for the TRX under test. Calls aremade on the tested TRX.

Calls are successful. Audio quality is good.

Case Ref. BTS Type/Configuration Failure Acti on

Nokia MetroSite

Multi TRX

Remove the Diversity Rx cable from the TRX1

12.2 Changed Information in Online Help menu

Purpose:

To check that the BTS Manager Online Help correctly displays the changed

TRX Test presentation.

Input Expected Output The BCF is operational.

Click on the “Help Æ Nokia BTS Manager…”menu item in the BTS Manager

The BTS Manager window is displayed.

Select Testing and click open. The Testing window is displayed.

Select Testing TRXs and click display. The Testing TRXs window is displayed.

Online help on the TRX Test can be seen.

Search for word ‘Rx Result’ and select topic‘Testing TRXs’.

The correct string information for ‘Main RxResult’, ‘Diversity Rx Result’ and ‘Rx Result’ aredisplayed.

Case Ref. BTS Type/Configuration

1 Nokia MetroSite

Any






12.3 Changed Information in BTS CommissioningReport

Purpose:

To check that the BTS Manager application correctly displays the change string

information in the BTS commissioning report.


Site is created in the BSC.

The BTS Manager application is launched for anun-commissioned BTS.

The BTS Manager application is launchedsuccessfully for the un-commissioned BTS.

Click the Commissioning menu of the main menu

bar and select Wizard.

The BTS Commissioning wizard, with the manual

commissioning radio button selected, isdisplayed.

Click the Next button. The “Set Transmission Parameters” wizard isdisplayed.

Set the Transmission parameter and click theNext button of the wizard.

The “Set Intelligent downlink diversity” page of thewizard is displayed.

Click the Next button. The “Transmission Configuration” page of theCommissioning wizard is displayed.

Set the Transmission configuration parameter. The “BTS Test reporting” page (with the correctstring information for ‘Main RX Result and

Diversity RX Result’) of the Commissioningwizard is displayed.

Click the Next button. The “EAC Input setting” page of theCommissioning wizard is displayed.

Click the Next button. The “EAC Output setting” page of theCommissioning wizard is displayed.

Click the Next button. The “BTS Commissioning Report” page (with thecorrect string information for ‘Main RX Result’ andDiversity RX Result’) of the Commissioningwizard is displayed.

Click the To File button and save the

commissioning report.

Click the Finish button.

The BTS is commissioned successfully and the

Commissioning wizard closes.

Open the saved commissioning report. Correct string information is displayed for ‘MainRX Result’ and ‘Diversity Rx Result’ in place of ‘Main RX sensitivity’ and ‘Diversity RX sensitivity’,respectively, in the commissioning report.

CaseRef.

BTS Type/ Configuration



119 (121)





1 Nokia MetroSite

Any



functional regression dn0691353x1x0xen

Documents