Vous êtes sur la page 1sur 152

Nokia MetroSite EDGE BTS

Functional Verification
Regression Specification for BTS
SW Release CXM6

DN06103517
Issue 1-0

Nokia Siemens Networks

1 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This document is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under
which the document is submitted, and no part of it may be used, reproduced, modified or
transmitted in any form or means without the prior written permission of Nokia Siemens
Networks. The document has been prepared to be used by professional and properly trained
personnel, and the customer assumes full responsibility when using it. Nokia Siemens
Networks welcomes customer comments as part of the process of continuous development
and improvement of the documentation.
The information or statements given in this document concerning the suitability, capacity, or
performance of the mentioned hardware or software products are given as is and all liability
arising in connection with such hardware or software products shall be defined conclusively in
a separate agreement between Nokia Siemens Networks and the customer. However, Nokia
Siemens Networks has made all reasonable efforts to ensure that the instructions contained in
the document are adequate and free of material errors and omissions. Nokia Siemens
Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may
not be covered by the document.
Nokia Siemens Networks will correct errors in the document as soon as possible. IN NO
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS
DOCUMENT OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,
DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY MONETARY
LOSSES,SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE
USE OF THIS DOCUMENT OR THE INFORMATION IN IT
This document and the product it describes are considered protected by copyrights and other
intellectual property rights according to the applicable laws.
Wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of
Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright Nokia Siemens Networks 2008. All rights reserved.

2 (152)

Nokia Siemens Networks

Contents

Contents
1

Vocabulary ..............................................................................................6

2
2.1
2.2
2.3
2.4
2.5

Introduction ............................................................................................8
Scope .......................................................................................................8
Prerequisites ..........................................................................................10
Hardware Requirements ........................................................................11
Software Requirements..........................................................................12
Specialist Test Equipment Requirements ..............................................13

3
3.1
3.2
3.3
3.3.1
3.3.2
3.4
3.5
3.6
3.7

BTS Commissioning and Software Download ..................................14


Direct SW Download during Commissioning..........................................14
Direct SW Downloading from the BSC to the BCF.................................15
BTS Commissioning from BTS Manager ...............................................17
Direct SW Download during commissioning ..........................................17
BTS Commissioning from BTS Manager with EDAP configured ...........18
Background SW Download from the BSC to the BCF............................20
BTS SW Download from the BTS Manager to the BCF .........................21
BTS SW package background downloading and activation
(mass operation) ....................................................................................22
BTS Manual Commissioning ..................................................................23

4
4.1
4.2
4.3

Manual Configuration Change ............................................................25


Adding new TRXs...................................................................................25
Site Expansion .......................................................................................26
Hot-Insert TRX for Chain Configuration .................................................28

5
5.1
5.2

BTS Tests..............................................................................................30
TRX Tests ..............................................................................................30
ABIS Loop test .......................................................................................35

6
6.1
6.2
6.3
6.4
6.5

Object Control ......................................................................................38


TRX Lock/Unlock and Block/Unblock.....................................................38
BCCH Reconfiguration ...........................................................................40
BTS Lock/Unlock and Block/Unblock .....................................................41
BCF Lock and Unlock.............................................................................44
BCF Reset..............................................................................................46

7
7.1

Intelligent Coverage Enhancement ....................................................48


Intelligent Coverage Enhancement - Plus ..............................................48

8
8.1
8.2
8.3

Intelligent Shutdown for MetroSite.....................................................49


All Shutdown Mode ................................................................................52
BCCH Shutdown Mode ..........................................................................52
None Shutdown Mode............................................................................58

Nokia Siemens Networks

3 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

8.4
8.5
8.6
8.7
8.8
8.9
8.10
8.11
8.12
8.13

Repetitive Intelligent shutdown testing .................................................. 62


BCF Lock/ Unlock from the BSC ........................................................... 62
BTS Lock/Unlock from the BSC ............................................................ 64
TRX Lock/Unlock from the BSC ............................................................ 66
Site Reset from BSC and BTS Manager ............................................... 67
BCF Block/Unblock from BTS Manager ................................................ 70
BTS Block/Unblock from the BTS Manager .......................................... 71
TRX Block/Unblock from the BTS Manager .......................................... 73
BTS reset from BTS Manager ............................................................... 75
TRX Reset from BTS Manager.............................................................. 76

9
9.1
9.2

Recovery for BSS and Site Synchronisation .................................... 78


Site Synchronisation Recovery during start-up/resets........................... 78
Site Synchronisation recovery with GPS signal recovery...................... 82

10
10.1
10.2
10.3
10.4
10.5
10.6
10.7
10.8
10.9
10.10

BTS Manager Functionality ................................................................ 89


BTS Manager Start-Up .......................................................................... 89
Access Rights in Local mode ................................................................ 91
BTS SW Menu Commands ................................................................... 94
BTS Manual Commissioning ................................................................. 96
Enabling and Disabling of Abis............................................................ 101
Adjusting the DAC Word...................................................................... 103
FC E1/T1, FXC E1 and FXC E1/T1 Transmission Menus................... 103
FXC RRI Transmission Menus ............................................................ 105
Window Menu Commands .................................................................. 107
BTS Manual Commissioning with FXC RRI ........................................ 108

11
11.1
11.2
11.2.1

Remote BTS Manager ....................................................................... 112


Remote BTS Manager Start-Up .......................................................... 112
Remote BTS Manager......................................................................... 114
Remote BTS Manager Start-Up using NetAct TLUI with
configuration in GCS Database ........................................................... 114
BTS Manager command line connection to remote BTS using
Sobriquet String................................................................................... 114
BTS Manager command line connection to remote BTS using
Target String........................................................................................ 115
Remote BTS Manager Start-Up for BCF id > 255 ............................... 116

11.2.2
11.2.3
11.2.4
12
12.1
12.1.1
12.1.2

13
13.1

4 (152)

Improved TRX Test Presentation ..................................................... 118


Improved TRX Test Presentation in the TRX Test Report .................. 118
Improved TRX Test Presentation in the TRX Test Report while
TRX Test executed from BTS Manager .............................................. 118
Improved TRX Test Presentation in the TRX Test Report while
Test executed from Remote BTS Manager ......................................... 119
User Access Level Control ............................................................... 121
Remote Connection to BTS Manager with Read Only Access............ 121

Nokia Siemens Networks

Contents

13.2

13.3
13.4
13.4.1
13.4.2

Changes in Registry Key/User Priveledges for BTS Manager in


Remote mode.......................................................................................123
Changes in Registry Key when application is running in remote
scenario................................................................................................123
Changes in User Privileges when application is running in
remote scenario. ..................................................................................124
User Authentication ..............................................................................125
Enabling/Disabling UALC DURING Installation of Site Wizard ............126
UALC Enabled During SiteWizard Installation .....................................126
UALC Disabled During SiteWizard Installation.....................................128

14
14.1
14.1.1
14.1.2
14.1.3
14.2
14.2.1
14.2.2
14.3

ST-IRC .................................................................................................130
Enable/Disable ST-IRC from BSC........................................................130
Any EDGE configuration, RDIV=N, RF-Hopping..................................130
2+2 EDGE configuration ......................................................................131
4 omni EDGE configuration..................................................................132
Alarm Handling.....................................................................................134
ST-IRC in a GSM site...........................................................................134
EDGE TRX replaced by GSM TRX ......................................................136
TRX Test and TRX Loop Test ..............................................................138

15
15.1
15.1.1
15.1.2
15.1.3
15.1.4

RSSI comparison values from BTS Manager ..................................140


RX Antenna Supervision by Comparing RSSI Value ...........................140
RSSI comparison values from BTS Manager.......................................140
RSSI comparison values from BTS Manager.......................................141
Alarms from BTS Manager during RSSI comparison values test.........143
RSSI comparison values from remote BTS Manager ..........................145

16
16.1
16.2

Alarm reporting ..................................................................................146


Alarm reporting from DMC when BTS polling is used ..........................146
Alarm reporting after BCF Block / Unblock from the BTS
Manager ...............................................................................................147

17
17.1

BCCH reconfiguration........................................................................150
BCCH reconfiguration when TSC is different from BCC ......................150

13.2.1
13.2.2

Reference ............................................................................................................152

Nokia Siemens Networks

5 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Vocabulary
The following abbreviations are specific to this document

6 (152)

ARFCN

Absolute Radio Frequency Channel Number

BBU

Battery Backup Unit

BCF

Base Control Function

BSC

Base Station Controller

BTS

Base Transceiver Station

FR

Full Rate

EFR

Enhanced Full rate

HR

Half Rate

GMSK

Gaussian Minimum Shift Keying

GSM

Global System for Mobile Communication

GPRS

General Packet Radio Switching

EGPRS

Enhanced- GPRS

EDGE

Enhanced Data Rates for GSM Evolution

HW

Hardware

ICE+

Intelligent Coverage Enhancement - Plus

ITN

Integrated Transmission Node

IUO

Intelligent Underlay Overlay

MMI

Man Machine interface

PSK

Phase Shift Keying

SW

Software

TCH

Traffic Channel

TRX

Transceiver

Nokia Siemens Networks

Vocabulary

LMU

Location Management Unit

LCS

Location Service

FTP

File Transfer Protocol

UDP

User Datagram Protocol

MCS

Modulation Coding Scheme

UALC

User Access Level Control

RF TA

Radio Frequency Timing Advance Rigs

NEE

Network Element Emulator

IR/LA

Incremental Redundancy/Link Adaptation.

DFCA

Dynamic Frequency and Channel Allocation

Nokia Siemens Networks

7 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Introduction

2.1

Scope
This document defines the library of test cases in order to verify the functional features
of BTS software release CXM6 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 S13, BTS Manager Version to be used is CX6 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 S13 mean any S13 generation BSC software package.
The latest package and Change Delivery (CD) under test should be used. References
to S12 mean any S12 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 and BTSs
are referred as synonymously where ever applicable. This principle is followed in the
test descriptions in this document.
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 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.

8 (152)

Nokia Siemens Networks

Introduction

Note 6.
A multi TRX configuration is a site having several TRXs e.g. 2+2 TRXs, 4 TRXs, etc.
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.
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 first cabinet 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 BTS 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.

Nokia Siemens Networks

9 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Note 11.
A invalid BB Hopping configuration exists in a sector having TRX`s of different power
types in the same hopping group, ie 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 time slots.
Therefore it is recommended that GPRS-configured radio time slots are not selected
for TRX test.
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 BTS manager from Help
Menu or using help button (F1).
Note 16.
While testing Multi BCF with DF 6.0-3, at S13 BSC, the SENA for master BCF should
be F while for DF7 onwards 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.

10 (152)

Nokia Siemens Networks

Introduction

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

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.

Nokia Siemens Networks

11 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

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

EGPRS

Class B & Class C, Multi


EGPRS Channel Request on PBCCH and BCCH

Adaptive Multi-Rate

AMR FR and HR

General

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

Enhanced Measurement
Reports

EMR Capable

2.4

Software Requirements
-

SiteWizard5.0

Latest available release containing the feature under test.

GCS R5.0

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


Table 1: SW Versions of Other Network Elements

12 (152)

Network Element

SW Version

BSC

S12, S13

HLR

M13

MSC

M13

Nokia NetAct

OSS4.1, OSS4.2

LMU

LMU 4.4, LMUB 1.0 CD1

SGSN

SG5

Transmission (FXC E1, FXC E1/T1,


FXC RRI, FC STM-1)

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


ITN C3.0 CD1

Transmission (FC E1/T1)

ITN C1.0

Nokia Siemens Networks

Introduction

Network Element

SW Version

Transmission (MetroHub)

MHB C2.1, C2.2, C3.0, C3 CD1

BTS Manager PC

Windows 98, Windows 2000, Windows XP,


Windows 2003 Server

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 & GMSK capable RF TA Rigs

IR/LA Rig

Assortment of combiners

Attenuators

Terminators

Signal generator

Spectrum analyser

GSM Protocol Analyser

Data Channel Simulator

D-Bus Analyser

Q1 Monitor/NEE

Abis Breaker

CMU

Nokia Siemens Networks

13 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

BTS Commissioning and Software


Download

3.1

Direct SW Download during Commissioning


Purpose:
To check that SW can be downloaded directly from BSC during commissioning of Site
successfully and 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 BSC
according to given configuration. CXM6 is not in
the flash

Each BTS has required number of TRXs. OMU


and FU state is in UA state. BCF is in locked
state.

CXM6 is attached to the BCF using MML ZEWA


and then it is activated using MMl ZEWV. Execute
all FU links and OMU link in WO state using MML
commands

BCF unlock is not allowed as OMU is not in


working state.
All TRXs and BTSs are unlocked successfully.

ZDTC:<FU no./OMU>:WO;
Unlock all TRXs, BTSs and BCF at BSC using
ZERS, ZEQS and ZEFS MML commands
respectively.
Commission the site using BTS manager.

OMU link comes to working state.

Monitor the SW downloading on Abis.


The service terminal extension (using ZDDS;),
RPHASESX (ZLE:P,RPHASESX) is used to
monitor the process of SW downloading of the
BCF.
Unlock the BCF at BSC.

14 (152)

Nokia Siemens Networks

BCF is unlocked and after reset comes to


operational state.

BTS Commissioning and Software Download

Check the SW version using MML commands


ZEWO.

Requested SW, CXM6, 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 in
laboratory conditions be predominately of value 0

Terminate calls.

All calls are terminated successfully. Release


cause is normal.

Case Ref.

Configuration

O&M Signalling

2+2 EDGE/GSM

32Kbps

4 Omni EDGE

Combined Signalling

3.2

Direct SW Downloading from the BSC to the BCF


Purpose:
The purpose of these test cases is to verify that the SW package can be downloaded
directly from the BSC to the BCF and can be activated successfully.
Extra HW/Tools: D-Bus Analyser

Input

Expected Output

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


up a call in the BCF.

Call is successful

BTS SW packages have been installed at the


BSC. BTS SW to be activated is attached to the
BCF(s) without being background downloaded.

Monitor the SW downloading from the BSC to the


BCF on Abis. The D-Bus Analyser is used to
monitor the SW downloading from the Chain
Master TRX (TRX in position 1) to the Slave
TRX(s). The service terminal extension (using
ZDDS;), RPHASESX (ZLE:P,RPHASESX) is
used to monitor the process of SW downloading
of the BCF.
Attach latest UltraSite SW to the BCF.

Nokia Siemens Networks

DX error BTS SITE TYPE AND BCF BUILD TYPE


ARE MISMATCHED can be seen at the BSC. Also
in that case SW downloading is not started.

15 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

Block the OMU link.


Attach the BTS SW to be tested using MML
command ZEWA:

The BSC indicates that the BTS SW cant be


attached due to O&M link failure.

The MML command ZEWO is used at BSC to


check the attached BTS SW to BCF.

Correct BTS SW package is attached to the BCF at


the BSC.

The OMU link is unblocked, and then the MML


command ZEWV: is executed.

The command first resets the BCF and then loads


the SW

One Slave BCCH TRX is removed and then


reinserted. SW downloading is monitored.

Slave BCCH TRX is detected, it does not disturb


the downloading.
The downloading is successful. Downloaded SW is
saved to the Master TRX flash memory (nonvolatile memory).
The BCF is initialised and comes to working state
with all TRXs.

Verify the end state

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


The Active SW and SW in Newest Flash memory
are same.

Calls are made via every TRX.

All calls are successful.

Case
Ref.

Configuration

Active SW and
Flash Contents at
the Beginning

Additional Action

End State

Signalling
speed

2+2 EDGE/GSM

Active-CXM5CD1.0

Download CXM6,
In the test step 6
during SW
download, reset
the slave BCCH
TRX locally using
BTS Manager

Active-CXM6

16 kbps

Download CXM5
CD1.0

Active-CXM5
CD1.0

Flash-CXM5CD1.0
and CXM5

3 Site chain, Multi


TRX
EDGE+GSM+
EDGE/GSM

Active-CXM6

Multi TRX EDGE

Active-CXM5

Flash-CXM6 and
CXM5

Flash-CXM5 and
CXM5CD1.0

16 (152)

Nokia Siemens Networks

Flash-CXM6
and
CXM5CD1.0

64 kbps

Flash-CXM5
CD1.0 and
CXM6
Download CXM6

Active-CXM6
Flash-CXM6
and CXM5

32 kbps

BTS Commissioning and Software Download

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 BSC during commissioning of Site
successfully and BTS Site comes up in working state with the requested SW version.
Equipment and BTS Set-Up
BTS is in uncommissioned state

Input
Create the BTS Site at BSC as described in the
test case.

Expected Output

Put all FU links and OMU link in WO state using


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

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

Unlock all TRXs and BTS


Attach the BTS SW under test to the BCF using
MML command ZEWA.
Activate the attached BTS SW using MML
command ZEWV.
Launch the BTS Manager and connect to the BTS

The BTS and its TRXs are unlocked


SW attach denied due to O&M Link State.

Commission the BTS Site using BTS Manager.


While configuring the Traffic Manager, define
EDAP (Multiple TSs) as defined in the test case.
Click on OK button to save these settings.
Monitor the SW downloading on Abis.
The service terminal extension (using ZDDS;),
RPHASESX (ZLE:P,RPHASESX) is used to
monitor the process of SW downloading of the
BCF.

Nokia Siemens Networks

SW activation denied due to BCF Administrative


State.
BTS Manager is launched and connected to the
BTS successfully.
Traffic Manager window gets closed and
commissioning proceeds.
OMU link comes to working state.

BTS SW downloaded successfully.


Commissioning is successful.

17 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

Unlock the BCF using MML command ZEFS.

BCF is unlocked and after reset comes to


operational state.

Check the BTS SW packet at the BSC and BTS


Manager
Set up voice calls on all TRXs.

Requested SW is active.

Case Ref.

13-435458.01

All calls are successful.

BTS
Type/Configuration

EDAP POOL at BSC

EDAP at Traffic
Manager

EDAP
Attached to
the TRXs

Nokia MetroSite

Yes

Yes

No

No

No

No

4 Omni EDGE TRX


13-435458.02

Nokia MetroSite
4 Omni EDGE/GSM
TRX

3.3.2

BTS Commissioning from BTS Manager with EDAP configured


Purpose:
To check that BTS is commissioned successfully with EDAP configured from BTS
Manager.
Equipment and BTS Set-Up
BTS is in uncommissioned state.

Input
Create the BTS Site at BSC as described in the
test case.

Expected Output

Put all FU links and OMU link in WO state using


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

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

Unlock all TRXs and BTS


Attach the BTS SW under test to the BCF using
MML command ZEWA.
Activate the attached BTS SW using MML
command ZEWV.
Launch the BTS Manager and connect to the BTS

The BTS and its TRXs are unlocked


SW attach denied due to O&M Link State.

18 (152)

Nokia Siemens Networks

SW activation denied due to BCF Administrative


State.
BTS Manager is launched and connected to the
BTS successfully.

BTS Commissioning and Software Download

Input
Start commissioning of the BTS Site.
While configuring the Traffic Manager, EDAP is
not configured. Click on OK button to save these
settings.

Expected Output
Traffic Manager window gets closed and
commissioning proceeds. After displaying the
message BCF in the configuring state,
commissioning fails to proceed there is no
response from the BTS SW.

Unlock the BCF using MML ZEFS command at


BSC.

Equipment View and Alarm view get closed, and


Commissioning Wizard and BTS Event view
remain open.
After some time BTS Manager is again connected
to BTS and it remains in waiting state, due to
wrong traffic settings.
Alarm 7730 BCF CONFIGURATION FAILED is
reported at the BSC
A pop up window is displayed.

Click on Cancel button to cancel the


commissioning.
Press Yes on pop up window to go to the
Commissioning Report page.
Now click on the Finish button to finish the
commissioning process.
Now uncommission the site and commission the
site again with 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 to
monitor the process of SW downloading of the
BCF.
Check the BTS SW packet at the BSC and BTS
Manager
Set up voice calls on all TRXs.
Case Ref.

13-435462.01

Commissioning Report page is displayed.


Commissioning wizard will be closed
successfully.
OMU link comes to working state.

BTS SW downloaded successfully.


Commissioning is successful.

Requested SW is active.
All calls are successful.

BTS Type/Configuration

EDAP POOL at BSC

EDAP Attached to
the TRXs

Nokia MetroSite

Yes (Multiple TSs)

Yes

Yes (Multiple TSs)

Yes, EDAP
attached to the
EDGE TRXs only

Yes (Multiple TSs)

Yes

4 Omni EDGE TRX with


EGPRS Enabled
13-435462.02

Nokia MetroSite
4+4+4(EDGE+GSM+EDGE)
chained site

13-435462.03

Nokia MetroSite
4 Omni EDGE TRX with BB
hopping

Nokia Siemens Networks

19 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

3.4

Background SW Download from the BSC to the


BCF
Purpose
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 to the BCF.
Extra HW/Tools:
D-Bus Analyser

Input

Expected Output

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


up a call in the BCF.

Call is successful.

BTS SW packages have been installed at the BSC.


Monitor the SW downloading from the BSC to the
BCF on Abis. The D-Bus Analyser is used to
monitor the SW downloading from the Master TRX
to the Slave TRX(s). The service terminal extension
RPHASESX is use to monitoring the process of SW
downloading of the BCF.
Calls are made via TRX(s) and maintained during
background downloading of SW

Calls are continued

Start BTS SW background downloading using MML


command ZEWA as stated in respective test case.

Background SW downloading started


succssfully. Calls are not released during
background downloading.
Background downloading completed.

The BTS SW package is activated by using MML


command ZEWV.

Software is not downloaded from BSC. The BCF


is initialised with new SW and comes to WO
state. All calls are released.

Verify the end state

The end state is same as specified in the test


case.
The Active SW and SW in Newest Flash
memory are same.

New calls are made via every TRX.

All calls are successful.

Activate the software that was previously running.

BCF comes to WO state.

Calls are made via all TRXs

All calls are successful.

Case
Ref.

20 (152)

Configuration

Additional Action

Nokia Siemens Networks

Active SW and
Flash Contents
at the
Beginning

Downlo
aded
SW

End State

Sig
Speed

BTS Commissioning and Software Download

Input
1

Expected Output
Multi TRX
EDGE1

3 Site chain,
Multi TRX,
GSM+EDGE+
GSM/EDGE
BCCH on TRX
no. 2, 6 & 10.
RF hopping in
sector2 and
BB hopping in
sector3.

1
2

2+2
GSM/EDGE

Generate some
Major and Minor
alarms which need
to be sent to BSC2

ActiveCXM5CD1.0

After fifth step


"Check for BCCH
transmission in
each sector using
spectrum
analyser".

Active-CXM4.1

CXM6

Active-CXM6
Flash-CXM6
and
CXM5CD1.0

FlashCXM5CD1.0
and CXM5
CXM6

Flash-CXM4.1
and CXM5

Active-CXM6
Flash-CXM6
and CXM4.1

16
kbps

64
Kbps

Enable/Disable
STIRC during
background
downloading
None

Active-CXM6

CXM5

Flash-CXM6
and CXM5CD1

Active-CXM5
Flash-CXM5
and CXM6

16
Kbps

Satellite Abis only


Major TRX Faulty and Antenna Connection Faulty, Minor MMI Connected to the Base Station

3.5

BTS SW Download from the BTS Manager to the


BCF
Purpose:
To check that the BCF SW can be updated from BTS Manager and put into use
successfully.

Input

Expected Output

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


up a call in the BCF.

Call is successful.

From BTS Manager, the BTS SW Update


command is selected. The master file for CXM6
that is not already downloaded to the BCF is
selected and loading is started.

The SW is background downloaded from the PC


to the BCF.

Nokia Siemens Networks

The SW loading does not disturb the call.

21 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

The SW versions are requested.

The SW version report shows that the SW


package is in the Newest flash memory but not as
'Running Package'.

The same SW is attached and activated at the


BSC.

The BCF is reset. The SW is not downloaded


from the BSC to BCF. The background
downloaded SW package is in the flash memory.

The SW versions are requested.

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


A call is set up in the BCF.

Call is successful.

From BTS Manager, the BTS SW Update


command is selected. The master file, which is
already in BCF as Running Package, is selected
and the loading sequence is started.

The SW downloading is not started. The user is


informed that the SW is already in flash memory.

The SW versions are requested.

The SW version report shows that the SW


package is already in the flash memory as
"Running Package".

Above steps involving the update of already


existing SW in flash, are repeated, with attempt to
download a SW package, which is already in the
BCF, but not as Running Package.

This time the SW is downloaded and is seen as


"Newest in flash".

Case Ref.
1

3.6

The call is not disturbed by the SW related


actions.

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

BTS SW package background downloading and


activation (mass operation)
Purpose:
The purpose of the test is to ensure that the BTS SW package can be background
downloaded and activated properly from the Nokia NetAct.

Input

Expected Output

BTS SW package CXM5 CD1.0 is IN USE


(running package). BTS SW package CXM5 is in
flash memory.

22 (152)

Nokia Siemens Networks

BTS Commissioning and Software Download

Input

Expected Output

From the Top Level Interface, Utils menu,


choose NE SW Configuration Mgmt.. From
there, choose Software Configuration
Management and finally click on the Software
Archive tab.
From the Software Archives page, select the
current tested SW package i.e. CXM6 from BS
Software.
In Software Archive window, from Managed
Objects, select all BCFs to be downloaded and
activated at the same time (mass operation), click
on download button to open Tasks Scheduling
window.
NOTE: The Mass Software downloads need to be
performed at least on 10 BCFs. This includes
BCFs on different BSCs.
In Tasks Scheduling window, select
Immediately to download CXM6 immediately or
later to download with a set time, and activate
the button Activate Software.

SW package CXM5 is background downloaded.


Right after the downloading is done, CXM6 is
activated automatically. When SW package
CXM6 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.

Case Ref.
1.

3.7

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

BTS Manual Commissioning


Purpose:
The purpose of these tests is to check that a BTS can be manually commissioned with
the BTS Commissioning Wizard.

Input

Expected Output

The BCF is un-commissioned and is in the


"Commissioning" state.
The BTS Commissioning Wizard is started and
Manual Commissioning is selected.

Nokia Siemens Networks

23 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

The Cancel command is selected on every page


of the BTS Commissioning Wizard except the
BTS Commissioning Report page.

If the cancelling is done before the Abis TS


allocation has been given, then the Wizard is
exited. The BCF is in the 'Commissioning' state.

The Manual Commissioning is re-started in the


cases when the Wizard is exited.

If the cancelling is done after the Abis TS


allocation has been given, the message box is
shown for the user to verify cancellation and the
BTS Commissioning Report page is opened.
From the report it can be detected that
commissioning was cancelled.

The Undo Commissioning command is selected


in the Commissioning Wizard.

The BCF is reset and enters the "Commissioning"


state.

The BTS Commissioning Wizard is started and


Manual Commissioning is selected.
The Cancel command is selected on the BTS
Commissioning Report page.

The message box is shown for the user to verify


the cancelling. The Wizard is exited without
saving the commissioning report.

The BCF is operational. BTS software release


CXM6 is used.
The Commissioning Wizard command is
selected.

The Undo Commissioning method is selectable,


but the Manual Commissioning method cannot be
selected from the BTS Commissioning Wizard
page.

The Undo Commissioning method is selected and


the Next button is pressed.

Window pop-up with message This command will


force BTS into the non-commissioned state. Do
you want to continue?

Select OK.

The BCF is reset and commissioning data is


deleted from BTS.

Case Ref.

Configuration

Transmission Unit

Transmission SW

Operating System in PC

2+2 HVTP

FXC E1/T1

ITN C2.2

Windows 2000

24 (152)

Nokia Siemens Networks

Manual Configuration Change

Manual Configuration Change

4.1

Adding new TRXs


Purpose:
The purpose of the case is to ensure that a new TRX can be manually added to the
Nokia MetroSite BTS.

Input

Expected Output

Calls are made via the BCF in which the TRXs


are to be added. The new TRXs being added do
not have CXM6 in their flash.

Calls are successful

LAPD link for the new TRX is created and


executed in WO state using MML command
ZDTC: <FU no.>: WO;

TRX creation at the BSC is successful.

The TRX is created under the correct BCF and


BTS in BSC. The TRX is in locked state after it is
created.
New TRXs are installed. The SW in the memory
of the new TRXs is different from the SW in the
other TRXs.

When the TRX is inserted into the BTS, the


Master TRX detects that the configuration has
changed. The Master TRX downloads the active
SW to the new TRX.

From BTS Manager Abis TS allocation is updated


with the Traffic Manager.

Abis TS allocation can be updated without


disturbing other TRXs. No call gets cleared.

The new TRXs are unlocked. [If the new TRX is


added into a BB-hopping BTS, then this BTS also
needs to be locked/unlocked in order to take the
new TRX into the BB-hopping sequence]. Test
calls are made via every TRX and TS (time slots).

The new TRX is successfully initialised and made


operative in the network. Calls are successful.

Case
Ref.

Configuration

O&M and
TRXSIG

Transmissio
n Card

Sig
Speed

Hopping
Mode

Addition Done

2GSM

Combined

FXC E1, (ITN


C3.0)

16 kbps

RF

2 EDGE TRXs

Nokia Siemens Networks

25 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

1 TRX GSM
(Preferred
BCCH)

Combined

FC E1/T1
(ITN C1.0)

64 kbps

None

3 TRX GSM, with


64Kbps
compressed
signalling

2+1 TRX EDGE

Separate

FXC E1/T1
(ITN C3.0)

32 kbps

None

1 EDGE TRX to
second BTS, with
32 Kbps signalling

2 TRX GSM

Combined

FXC RRI
(ITN C3.0)

16 kbps

RF

New EDGE BTS


with two TRX, with
16 Kbps signalling

3 TRX EDGE

Combined

FXC E1 (ITN
C2.1-2)

16 kbps

BB

New EDGE BTS


with one TRX,, with
64 Kbps signalling

2+1 TRX GSM

Separate

FC STM-1
(C3.0)

64 kbps

BB

1 EDGE TRX to
second BTS, with
16 Kbps signalling

2 TRX EDGE
With extended
BTS id

Combined

FXC E1/T1
(ITN C2.2)

64 kbps

None

2 TRX GSM, with


16 Kbps signalling

4.2

Site Expansion
Purpose:
To ensure that the MetroSite can be extended successfully to a MetroSite chain
configuration.

Input

Expected Output

BCF is in operational state. The new TRXs being


added do not have CXM6 in their flash.

BCF is working. No unexpected alarm is present.

Calls are made on all TRXs.

Calls are successful..

New LAPD link and BTSs are created at the BSC


to expand the BCF into 1st expansion
configuration. Lock the BCF and power off the
Master cabinet and connect the first slave
cabinet.

All Calls are dropped after BCF lock.

26 (152)

Nokia Siemens Networks

Manual Configuration Change

Input

Expected Output

Turn the master cabinet power ON.


Corresponding changes are done in Traffic
Manager using BTS Manager by using Undocommissioning option and then commission the
site according to new configuration. Unlock the
BCF and newly created BTS and TRX(s). A new
cabinet with all newly configured TRX(s) and
without Transmission card are powered up.

All BTSs come to working state. No alarms are


present at the Master BTS.

Calls are made on all TRXs of the both cabinets.

Calls are successful.

New LAPD link and BTSs are created at the BSC


to expand the BCF into 2nd expansion
configuration. Lock the BCF and power OFF the
cabinets and connect the second slave cabinet.

All Calls are dropped.

Turn the master cabinet power ON.


Corresponding changes are done in Traffic
manager using BTS Manager by using Undocommissioning option and then commission the
Site according to new configuration. Unlock the
BCF and newly created BTS and TRX(s). Second
and the third cabinet with all newly configured
TRXs and without Transmission card are
powered up.

BCF is in working state. No alarms are present.

Calls are made on all TRXs on all the Cabinets.

Calls are successful.

Wait for at least 15 minutes.

The BCF is in working order and no alarms are


present. All calls are still on going.

Case
Ref.

Initial
Configuration

Configuration
after 1st
Expansion

Configuration after 2nd


Expansion

Initial Hopping Mode

2 Omni GSM

2 GSM+

2 GSM + 4 EDGE + 4
EDGE

Non Hopping

4 EDGE
2

4 Omni EDGE

4 EDGE + (2+2)
GSM

4 EDGE + (2+2) GSM +


(1+1+1) EDGE

BB Hopping

4 Omni EDGE

4 EDGE + (2+2)
GSM 1

4 EDGE + (2+2) GSM +


(1+1+1) EDGE

BB Hopping

4 Omni EDGE 2

4 EDGE + (2+2)
GSM

4 EDGE + (2+2) GSM +


(1+1+1) EDGE

BB Hopping

2+2 GSMS12

(2+2) GSM + 2
EDGE/GSM

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

1st Sector RF
hopping
2nd Sector- Non
hopping

1
2

Use BTS id greater than 1000. Use RF hopping for the GSM sectors with MAL length greater than 16.
Perform the test case with CX(M)5 BTS Manager.

Nokia Siemens Networks

27 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

4.3

Hot-Insert TRX for Chain Configuration


Purpose:
The purpose of these test cases is to verify that TRX can be hot-inserted to a Master or
Slave cabinet while BCF is in supervisory state.

Input

Expected Output

The BCF is in supervisory state. Calls are placed


in the BCF.

Calls are successful.

TRX specified in the test case is removed and


behaviour is verified with Expected-Result (given
in the test case).

Behaviour is as per Expected-Result.

Lock the TRX from BSC and new TRX is inserted


into the empty position of the previously removed
TRX.

The Chain Master TRX detects new inserted TRX


and BTS Manager shows the TRX. The Chain
Master TRX synchronises and configures new
inserted TRX. All are in supervisory state.

Unlock the TRX.


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

If the removed TRX is BCCH TRX (other than


Master TRX) then call(s) on this TRX and TRX
with reconfigured BCCH will be released.

No alarms are active and calls are successful.

Case Ref.

Configuration

TRX Removed

Expected Result

TRX-Inserted

1.

3 Cabinet chain, 4 TRX


each cab, Master cab
(BTS1): 4TRX GSM 1800
Band, Slave 1 cab
(BTS2): 4TRX
GSM/EDGE 900 band,
Slave 2 cab (BTS3):
4TRX EDGE 1800 band

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

When the Master


TRX in the Slave
cabinet is removed,
alarms 7767 BCCH
MISSING and 7705
LAPD LINK
FAILURE are active
for the Slave
cabinets.

Replace the
removed TRX
with any of the
same freq band

2.

3 Cabinet chain, 4 TRX


GSM in each cabinet

Slave TRX in the


Slave cabinet

When the Slave


TRX is removed,
alarm 7606 TRX
Faulty is active for
the removed TRX.

Replace the
removed TRX
with any EDGE
TRX1 of the
same freq band

28 (152)

Nokia Siemens Networks

Manual Configuration Change

Input

Expected Output

3.

3 Cabinet chain, 4 TRX


EDGE in each cabinet. ,
Master cab (BTS1): 4TRX
EDGE 1900 Band, Slave
1 cab (BTS2): 4TRX
EDGE 800 band, Slave 2
cab (BTS3): 4TRX EDGE
1800 band
1

Slave TRX in the


Master and Slave
cabinet

When the Slave


TRX is removed,
alarm 7606 TRX
Faulty is active for
the removed TRX.

Replace the
removed TRX
with any GSM
TRX of the
same freq band

New inserted TRX should have CX6 SW in flash.

Nokia Siemens Networks

29 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

BTS Tests

5.1

TRX Tests
Purpose: To verify that the TRX test can be carried out successfully.
Note 18.
Acceptable tests results are: BER =0%, RX-Result: -110.5 dBm (or better) for GSM 900
and GSM 800, -111 dBm (or better) for GSM 1800 and GSM 1900.
The GMSK RX-Result 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 TRX performance test need to be defined as the default
values.
The default threshold of TRX performance test values for MetroSite are:Transmitted MetroSite XP Power (10 W)

= 40dBm

BER (BER)

= 0.2000%

RX -Result (MSENS)

= -100 dBm

At the BSC, the current threshold values of TRX performance test can be verified using
the MML command ZUCV:TRP,CURRENT;.
If the current threshold values are different to 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>;
Note 19.
The expected range of TX power level from a TRX test is transmitted power level
PMAX value 4 dBm.
Therefore for MetroSite, if the transmitted power level is 37 and PMAX is 30, then
expected power level from TRX test is 37-304 i.e. 3dBm to 11 dBm range.

30 (152)

Nokia Siemens Networks

BTS Tests

When the test case calls for a failure to occur during the test or a failure to start the test
then the failure reason is included in the TRX test report.
Note 20.
When the test is started from BTS Manager, the alarm 7615 RTS IS IN TEST USE' for
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. Alarm may persist if TRXs are in Configuring
mode.
This alarm may not be included in the alarm history at the BSC as the BSC uses timewindow based filtering for alarm reporting. That is, if an alarm is started and cancelled
within 10-seconds.
Note 21.
For all tests that require TRX test to be run, the PMAX value should be set as
Maximum (i.e. '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 TRX test is performed from BSC for GSM
TRX, both the modulation methods are available. However when
the test is started using the 8-PSK modulation, the BTS shall
determine that the wrong modulation type is selected for the TRX,
change the TRX test to use GMSK modulation and indicate this in
the report.8-PSK modulation methods option is not available when
TRX test is performed from BTS Manager for GSM TRX.

EDGE sector (EGPRS enabled): When TRX test is performed for


EDGE TRX, both the GMSK and 8-PSK modulation methods are
possible. The modulation scheme tested is indicated in the report.

EDGE sector (EGPRS disabled): When TRX test is performed for


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

GSM/EDGE sector: It shall depend on whether the TRX to be


tested is GSM or EDGE configuration. Refer to GSM sector,
EDGE sector (EGPRS enabled) and EDGE sector (EGPRS
disabled).

Input

Expected Output

The BCF is not commissioned.

Nokia Siemens Networks

31 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

The Tests | TRX Test command is selected.

The TRX Test command is not executed.

Start Commission the Site with OMU Signalling


blocked. The BCF is in the 'Waiting for LAPD'
state and TRX(s) are in the 'SW Loading' state.
The Tests | TRX Test command is selected.

The TRX Test command is not executed.

After completing the commissioning process, the


BTS SW | Use Current SW command is given.

The SW is taken in use.

The Tests | TRX Test command is selected. The


TRX, ARFCN number, and Radio Timeslot are
given 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, and


channel numbers.

The test can be executed successfully with


different parameters.

Case Ref.

HW Type

Modulation

Hopping Mode

GSM

GMSK

RF-hopping

EDGE (with
STIRC enabled)

GMSK

Non-hopping

Input

Expected Output

A call is made via the TRX to be tested.

The call is successful.


The TRX test can be started on TCH TS that
does not have PBCCH, control channels, TS
reserved for GPRS as partner. The test is not
started for control channels or channels with an
active call or TS reserved for GPRS and their
partner TS.

TRX test is started from the BSC using the MML


command ZUBS.

The tests results are checked using the MML


command ZUBP. The TX power level used is
verified with the spectrum analyser.

The test results are received at the BSC alarm


printer. The test is successful and the test results
are acceptable. The TX power level used is the
same as the BCCH TX power level (power level
depends on PMAX value). The call is not
affected.

The File /Options command is selected and the


File Handling tab is chosen. Check the checkbox
next to Test Log option. The popup address
window saves the log to a specific address.

The required log file can be defined. The log file is


correctly shown in the status bar of the Test
window.

32 (152)

Nokia Siemens Networks

BTS Tests

Input

Expected Output

TRX Test is repeated with BTS Manager, using


Tests | TRX Test command. TRX test is
performed with all modulation methods.

When TRX test is performed for GSM TRX, the


test is started as normal TRX test (GMSK). The
test is successful and the test results are
acceptable.
When TRX test is performed for EDGE TRX, the
modulation method is selectable. When test is
performed with GMSK method, 8 PSK MCS5 or 8
PSK MCS9 the test is successful and 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 RTS IS
IN TEST USE for the used TS is cancelled.
When the log is on, all generated TRX test setting
and results are saved into the log file.
The test is not started for control channels or
channels with an active call.

The log file is set not to be in use (Checkbox is


unchecked) from the File Handling page.

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


File is not appended any more.

The log file is opened from the saved location.

The TRX test results are shown correctly for all


modulation method.

For test 2, 6 hours script performing TRX test with


different modulation methods consecutively (first
GMSK, then 8-PSK) is used. The script tests the
BCCH and Non-BCCH TRXs on both sectors.
The test results and alarms are logged after each
test.

The correct modulation scheme is used and


stated 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

Channel
Configuration

Hopping
Mode

TX Power

EGPRS enabled
for EDGE units

3.

Any Chain
configuration
with at-least 3
sectors,
GSM+EDGE+
GSM/EDGE

MBCCH+ SDCCH+
6*TCHF, some TS
reserved for GPRS

None

1st sector
minimum.
2nd sector
maximum

Yes

4.

2+2,GSM+ED
GE, 6 hours
script with
TRX test

MBCCH+
+SDCCH+TCHF

None

-Any

Yes

Nokia Siemens Networks

33 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input
5.

Expected Output
2+2 common
BCCH Dual
band EDGE
TRX with
STIRC
enabled

MBCCHC+ TCHD

1st sectorNone

-Any

No

2nd sectorRF, Different


no. Of
frequencies
in MAL list
(3,20,63 etc)

Purpose:
The purpose of these test cases is to verify that the TRX test fails when some failure action is
performed.
Input

Expected Output

BCF is operational. Perform the failure action as


specified in the test case.
TRX Test is started from the BSC with the MML
command ZUBS for the TRX affected with the
failure action.

The test is started.

Abis is monitored.

From the Abis trace, failure reason is seen under


BTS Test Report Message.

The test results are checked from the BSC alarm


printer.

The test results are received at the BSC alarm


printer. The test results are not acceptable and
are same as mentioned in Expected Result.

Failure action is corrected and the TRX


LOCK/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 started


from the BSC.

The test is successful. The test results are


acceptable.

34 (152)

Nokia Siemens Networks

BTS Tests

Input

Expected Output

TRX Test is repeated with BTS Manager, using


Tests | TRX Test command. TRX test is
performed with all modulation methods.

When TRX test is performed for GSM TRX, the


test is started as normal TRX test (GMSK). The
test is successful and the test results are
acceptable.
When TRX test is performed for EDGE TRX, the
modulation method is selectable. When test is
performed with GMSK method, 8 PSK MCS5 or 8
PSK MCS9 the test is successful and 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 RTS IS
IN TEST USE for the used TS is cancelled.
When the log is on, all generated TRX test setting
and results are saved into the log file.
The test is not started for control channels or
channels with an active call.

Case
Ref.

Configuration

Failure Action

Expected result

6.

Multi TRX EDGE

Remove Non-BCCH
TRX antenna cable

Result printout indicates the test has failed.


Alarm 7606 TRX FAULTY (TRX antenna
connection faulty) is issued at the BSC.

7.

Multi TRX GSM

Remove the diversity


antenna cable from the
TRX

The failure reason (HW Failures) is included in


the BTS test report. Measurement results are
also included.

Multi TRX EDGE

Set up EGPRS data


transfer. Start TRX test
from BSC on the same
timeslot on which
EGPRS call is going on

TRX test is not performed. TRX test results


show the TRX test could not be performed due
to circuits already being in use. EGPRS call is
not interrupted.

5.2

ABIS Loop test


Purpose: To verify that the Abis loop test can be carried out successfully.

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

Nokia Siemens Networks

35 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Note 25.
The channel configuration is not significant unless specifically mentioned.
Input

Expected Output

Calls are made via BTS.

The calls are successful.

Some calls are terminated. The Abis loop test is


started from the BSC with the MML command
ZUBK. Several test times between minimum and
maximum are used.

The test is started successfully

For test 1 and 2, 6 hours script performing Abis


loop test. The script tests the BCCH and NonBCCH both TRXs. The test results and alarms
are logged after each test.

The test is started successfully

The loop test results are checked from the BSC


using MML command ZUBP.

The test status indicates success. The test results


are acceptable. The TSs carrying Control
channels, Traffic and GPRS are not tested.
The calls are not affected.

Make new calls on tested TSs

Calls are successful.

Case
Ref.

Configuration

TS
Configuration

Transmissi
on Unit

Signalling
Speed

O&M and
TRXSIG

Abis
Connectio
n

Multi TRX
EDGE1

6 hours using a
test script that
repeatedly
carries out Abis
loop tests on
one BTS

FC STM-1
(ITN C3.0
CD1)

16 Kbps

Separate

Normal

Multi TRX
EDGE1

6 hours using a
test script that
repeatedly
carries out Abis
loop tests on
one BTS

FC STM-1
(ITN C1.0)

16 Kbps

Separate

Normal

Any Chain
configuration
with at-least 3
sectors,
GSM+EDGE+G
SM/EDGE

Several TRXs
in one BTS and
any GPRS TS

FXC E1
(ITN C2.2)

32 Kbps

Separate

Normal

36 (152)

Nokia Siemens Networks

BTS Tests

Input

Expected Output

Any Chain
configuration
with at-least 3
sectors,
GSM+EDGE+G
SM/EDGE

Several TRXs
in one BTS and
any GPRS TS

FXC E1
(ITN C2.1-2)

32 Kbps

Separate

Normal

2GSM+2EDGE,
common BCCH

(MBCCH+SDC
CH+6TCHF+8
TCHF)+(SDCC
H+7TCHF+8T
CHF)

FXC RRI
(ITN C2.1-2)

64 Kbps

Combined

Satellite
abis

RF hopping in
both sectors

Dynamic 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.
Input

Expected Output

The Abis loop test is started from the BSC with


the 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 alarm


printer.

The test status indicates inconclusive results


because 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 BSC


using MML commands ZUBP.

The test status indicates success. The test results


are acceptable.

Case Ref.

Configuration

Transmission Unit (Release)

Multi TRX

FXC E1/T1 (ITN C2.2)

Multi TRX

FXC E1/T1 (ITN C2.1-2)

Nokia Siemens Networks

37 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Object Control
Note 26.
The state of the Object (i.e. TRX, BTS, BCF) is checked after every test step with the
MML command ZEEI. Alarms are checked after every test step on the BSC alarm
printer.

6.1

TRX Lock/Unlock and Block/Unblock


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

Input

Expected Output

TRX transmit power levels are checked with


spectrum analyser.

TRX transmit power levels are same as set in the


BSC.

Neighbour cells are defined. Calls are made via


every TRX.

Calls are successful.

The TRX is locked from the BSC with the


command ZERS. BCCH transmission is checked
using a spectrum analyser.

The TRX is locked. Call(s) on the locked TRX is


released. If the BCCH TRX is under test, BCCH
transmission stops. Calls remain ongoing on
other TRXs.

TRX is unlocked with the ZERS command.

If the BCCH TRX is under test, Alarm 7767 BCCH


MISSING is active until the TRX is initialised. The
TRX returns to working state.

TRX transmit power levels are checked with


spectrum analyser.

The power levels before and after TRX reset


match the defined setting at the BSC.

Calls are made using every TRX.

All calls are successful with good quality.

38 (152)

Nokia Siemens Networks

Object Control

Input

Expected Output

The Block command is given for the TRX from the


BTS Manager.

The alarm 7208 LOCAL BLOCK is sent to BSC


and BTS Manager. The TRX blocked symbol is
updated into the Supervision window view.
Calls are handed over from the blocked TRX. If
BCCH TRX is blocked and reconfiguration is
possible, calls are still handed over.

The Unblock command is given for the TRX from


the BTS Manager.

The 7208 LOCAL BLOCK alarm is cancelled. The


blocked symbol disappears from the TRX object
in the Supervision window view.

Alarms are checked.

There are no active alarms.

Calls are made using every TRX. MO&MT GPRS


calls are also made.

All calls are successful with good quality.

Case Ref.

Configuration

TRX Locked

Multi TRX EDGE/GSM-

BCCH

Input

Expected Output

BCF is in Supervisory state.

All calls are successful.

Calls are made via all TRXs


TRX transmit power levels are checked with
spectrum analyser.

TRX transmit power levels are same as set at the


BSC.

An MML macro, which repeatedly locks and


unlocks all TRXs, one at a time, is started.

The TRXs start up properly after every lock and


unlock command.

The alarm history is checked after the macro is


complete.

When the BCCH TRX is locked, alarm 7767


BCCH MISSING is active. - Other alarms do not
occur.

TRX transmit power levels are checked with


spectrum analyser.

The power levels before and after TRX reset


should match the defined setting at the BSC.

Calls are made on all the TRXs after the test.

All calls are successful.

Case Ref.

Configuration

Chain configuration with 3 MetroSites (at least one EDGE and one GSM MetroSite),
PBCCH is configured. MML macro is run for 12 hours.

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

Input

Expected Output

BCF is in Supervisory state. Calls are made via


all TRXs.

Calls are successful.

Nokia Siemens Networks

39 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

TRX transmit power levels are checked with


spectrum analyser.

TRX transmit power levels are same as set at the


BSC.

Antenna cable is removed from preferred BCCH


TRX. PMAX is set to 0.

7606 TRX Faulty: Antenna Connection Faulty


alarm is generated. BCCH reconfiguration takes
place.

An MML macro, which repeatedly locks and


unlocks all TRXs, one at a time, is run for 12
hours.

The TRXs start up properly after every lock and


unlock command. Alarm 7606 is cancelled every
time the preferred BCCH TRX is unlocked. BCCH
reconfiguration takes place as the preferred
BCCH TRX gets blocked because of removed
antenna cable.

The alarm history is checked after the macro is


complete.

When the BCCH TRX is locked, alarm 7767


BCCH MISSING is active. TRX Faulty alarm for
the TRX with removed antenna cable is cancelled
and generated. Other alarms do not occur.

The antenna cable is reconnected. The TRX is


reset.

Alarm 7606 TRX Faulty: Antenna Connection


Faulty gets cancelled.

TRX transmit power levels are checked with


spectrum analyser.

The power levels before and after TRX reset


should 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

2 EDGE +2 GSM

6.2

1st sector Non Hopping, 2nd sector RF


Hopping

BCCH Reconfiguration
Purpose:
The purpose of these tests is to verify the reconfiguration of BCCH to preferred TRX.

Input

Expected Output

PMAX is set to 0. Abis is monitored.


Antenna cable is removed from preferred BCCH
TRX.

Alarm 7606, TRX Faulty alarm is generated.


BCCH reconfiguration takes place.

The preferred BCCH TRX is locked and then


unlocked from BSC.

Alarm 7606 is cancelled when the preferred


BCCH TRX is locked. BCCH reconfiguration
takes place as the preferred BCCH TRX gets
blocked because of removed antenna cable.

40 (152)

Nokia Siemens Networks

Object Control

Input

Expected Output

The antenna cable is connected. The TRX is


reset.

Alarm 7606 gets cancelled. Preferred BCCH TRX


gets configured as BCCH.

TRX transmit power levels are checked with


spectrum analyser.

The power levels before and after TRX reset


should match the defined setting at the BSC.

Calls are made on all the TRXs after the test.

All calls are successful.

Case Ref.

Configuration

Preferred BCCH TRX

DFCA Mode

4 EDGE/GSM

Master

DFCA enabled, Slave TRXs


are defined as DFCA TRX

Purpose:
The purpose of the test case is to verify that EGPRS can be enabled for Master TRX.
Input

Expected Output

Abis is monitored. EDAP and EGPRS enabled on


BCCH TRX
Synchronisation procedure, EGPRS attach and
PDP context is checked.
Using ZDTC command at BSC, the preferred
BCCH TRX signalling link is blocked

BCCH reconfiguration takes place. BCCH power


level is as set at the BSC (for both the TRXs,
preferred BCCH TRX and reconfigured BCCH
TRX).

Using ZDTC command at BSC, the preferred


BCCH TRX signalling link is unblocked

Preferred BCCH TRX gets configured as BCCH.

TRX transmit power levels are checked with


spectrum analyser.

The power levels before and after TRX reset


should match the defined setting at the BSC.

Synchronisation procedure, EGPRS attach and


PDP context is checked
Case Ref.

Configuration

Hopping Mode

Preferred BCCH

4 Omni EDGE

BB Hopping

Master TRX

6.3

BTS Lock/Unlock and Block/Unblock


Purpose:
The purpose of these tests is to verify that the BTS can be locked and unlocked
successfully from BSC and Blocked/unblocked from BTS manager.

Nokia Siemens Networks

41 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Note 27.
In case a Master TRX is reset from BTS Manager, SW download event should not be
shown as shown in case of Slave TRX(s) reset.
Note 28.
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.

Input

Expected Output

Neighbour cells are defined in the same and other


BCF. Calls are made via every TRX.

All calls are successful.

The BTS is locked with the ZEQS command and


use forced handover parameter (FHO) at BSC.
BCCH-transmission is checked with the spectrum
analyser.

Calls are handed over from the locked BTS.


BCCH transmission is stopped.

For case 2, PBCCH is configured on BCCH TRX


after locking the TRX.
The BTS is unlocked with the ZEQS command.
Abis is monitored.

Alarm 7767 BCCH MISSING is activated until


BCCH-TRX is initialised. The BTS is started
correctly and the correct system information is
sent. The BTS and TRXs under BTS return to
working state. BCCH transmission restarts.

Calls are made via every TRX.

All calls are successful.

The Block command is selected for the sector


from BTS Manager.

The BTS is blocked at the BSC. Calls are


dropped from the blocked BTS. The alarm 7208
LOCAL BLOCK for BTS is started. The blocked
sector is updated into the Logical Objects view.
The BCCH transmission is stopped.

The Block command is given for a TRX in the


blocked BTS.

The TRX cannot be blocked.

The Reset command is given for a TRX in the


blocked BTS.

The TRX is reset.

The Unblock command is selected for the sector.

The BTS becomes operational. The 7208 alarm is


cancelled. BCCH transmission restarts.

Alarms are checked.

There are no active alarms.

Calls are made using the BTS.

All calls are successful. Quality of calls is good

In BTS Manager, the File /Options command is


selected and the File Handling tab is chosen.
Check the checkbox next to Events Log option.
The popup address window saves the log to a
specific address.

42 (152)

Nokia Siemens Networks

The Events log file can be defined and is correctly


shown in the status bar of the Event window.

Object Control

Input

Expected Output

The Reset command is given for the sector from


BTS Manager.

All TRXs in the BTS are reset. This can be seen


visually and from the Supervision window views
and the BTS Events window at BTS Manager.
All TRXs in the BTS enters the 'Supervisory'
state.
Calls are released on reset BTS only.

Alarms are checked.

There are no active alarms.

From BTS Manager, the TRX Test is performed


to on 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 events setting


and results are saved into the log file.

The log file is set not to be in use (Checkbox is


unchecked) from the File Handling page.

The log file is not shown in the status bar of the


events window. File is not appended any more.

The file is opened from the saved location.

The contents are same as shown in Events


window.

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


calls are made.

All calls are successful.

BTS lock/unlock, reset and block/unblock is done


for all BTSs.
Case Ref.

Configuration

TRXSIG and
TCH Signalling

BTS Block from BTS


Manager

Hopping mode

3 Cabinets Chain

Separate

Logical Objects View,


Sector pop-up menu

BB

Compressed

Objects | Properties

RF hopping in 1st
sector.

4+4+4,
GSM+EDGE+GSM/
EDGE with STIRC
enable in sector 2
2+21 TRX,
CTxA+HVTx

2nd sector DFCA


enabled with 1
DFCA TRX.
1

BCF with extended BTS id

Input

Expected Output

A TRX is removed.

TRX Faulty alarm is generated for the TRX.

Nokia Siemens Networks

43 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

An MML macro, which repeatedly locks and


unlocks the BTSs, is started and run for required
time. Rx Diversity must be OFF before start
Macro.

The BTS returns to the working state after every


lock and unlock. TRX Faulty alarm is cancelled
when the BTS with the removed TRX is locked
and is raised again when unlocked. Hopping
reconfiguration takes place in case of BB
hopping.

The alarm history is checked after the macro is


completed.

Alarm 7767 BCCH MISSING is active while the


BTS is initialising. The BTS and TRX under the
BTS return to the WO state. TRX faulty and its
cancellation is seen after BTS unlock/lock. Other
alarms do not occur.

Calls are made via every TRX.

All calls are successful.

Case Ref.

Configuration

MML Macro Run time

Hopping Mode

EDGE (CTxA)+EDGE/GSM

12 Hrs

BB hopping in 1st sector

2nd sector DFCA enabled


with DFCA TRX

6.4

BCF Lock and Unlock


Purpose:
The purpose of these tests is to verify that the BCF can be locked and unlocked from
the BSC.

Input

Expected Output

Calls are made using every BTS in the BCF.

Calls are successful.

The BCF is locked with the ZEFS command.


BCCH transmission is checked with the spectrum
analyser.

All calls are released. The BCF gets locked.


BCCH transmission is stopped.

44 (152)

Nokia Siemens Networks

Object Control

Input

Expected Output

The BCF is unlocked with the ZEFS command.


The BTS Manager is monitored.

During the BCF reset, the connection between


BCF and BTS Manager is lost. The only available
menus are File, Tools, Connection, Window, and
Help menu. All toolbar icons are disabled except
icon that activates command from Help menu,
Tools & Connection.
The Supervision and Alarms window disappear
and the only visible window is the BTS Events
window. 'No connection to BTS is displayed in
the BTS Events window.
When the connection is re-established, the
Equipment view reappears showing the correct
information. The Alarm window reappears.
Notice 7701 BCF INITIALISATION is sent during
site initialisation. Alarm 7767 'BCCH MISSING is
active until BCCH TRX is operational. The BCF
returns to the WO state along with all of the BTSs
and TRXs under the BCF.Alarm 7801 Local MMI
CONNECTED TO BTS is active at the BSC and
BTS Manager.

Using the Spectrum Analyser, the frequency


transmission is monitored for all the TRXs

Only BCCH frequency is being transmitted. No


TCH TRX is making any transmission.

Both circuit switched and packet switched calls


are made via PBCCH and non PBCCH TRX.
(Make both MO&MT calls)

All calls are successful. Quality of calls is good.

Power level is monitored for the BCCH TRX(s)


when the call is going on by changing the PMAX
at BSC. At least three PMAX values between 230 are tested.

The power level is according to the PMAX value


set.

Case Ref.

Configuration
1

O&M and TRXSIG

Hopping Mode

2+2 TRX, HVTx,

Separate

None

3 cabinet chain with STIRC enabled.

Combined

RF Hopping+BB
hopping+None

Use extended BCF and BTS id

Input

Expected Output

An MML macro, which repeatedly locks and


unlocks the BCF, is started and run for 12 hours.

The BCF returns to the working state after every


lock and unlock.

Nokia Siemens Networks

45 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

The alarm history is checked after the macro is


complete.

Alarm 7767 BCCH MISSING is active when the


BTSs are initialised. Notice 7701 BCF
INITIALIZATION is sent when the BCF is
initialised. The BTSs and TRXs under the BCF
return to the WO state. Unexpected alarms do not
occur.

Calls are made via every TRX.

All calls are successful.

Case Ref.

Configuration

Hopping Mode

2CTxA +2 HVTx

RF Hopping in 1st sector

2nd sector DFCA enabled


with DFCA TRX

6.5

BCF Reset
Purpose:
The purpose of these tests is to verify that the site can be reset from the BSC and BTS
Manager.
Note 29.
In Chain configuration, if Master does not poll slave cabinet for frame clock sync, slave
must stop RF transmission after 10 minutes.

Input

Expected Output

Calls are made via every TRX.

All calls are successful.

The site is reset from the BSC with the ZEFR


command. BCCH transmission is checked with
the spectrum analyser.

The BCF is reset. Calls are released. BCCH


transmission is stopped. Notice 7701 BCF
INITIALISATION is sent during site initialisation.
The BCF returns to the WO state along with all of
the BTSs and TRXs under the BCF.

Calls are made via every TRX.

All calls are successful

BCF is reset from BTS manager with specified


option in the test case.

Calls are released. BCCH transmission is


stopped. The whole BCF is reset. Notice 7701
BCF INITIALISATION is sent during site
initialisation. The BCF returns to the WO state
along with all of the BTSs and TRXs under the
BCF.

Calls are made via every TRX.

All calls are successful.

46 (152)

Nokia Siemens Networks

Object Control

Input

Expected Output

Case
Ref.

Configuration

O&M and
TRXSIG

Hopping
mode

Reset BCF from BTS Manager

3 cabinet chain
configuration

Combined

BB Hopping in
any of one
sector

From Objects | Properties

2EDGE+2GSM

Separate

RF hopping in
2nd sector

From Logical Objects View, BCF


pop-up menu

1st sector DFCA


enabled with DFCA
TRX and STIRC
enabled

Nokia Siemens Networks

47 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Intelligent Coverage Enhancement

7.1

Intelligent Coverage Enhancement - Plus


Purpose:
The purpose of these test cases is to verify the functions of intelligent coverage
enhancement plus (ICE+) feature.
Note 30.
The BCCH must be configured in one of the high power TRXs, preferred BCCH TRX
feature can be used to ensure this.

Input

Expected Output

BTS configuration is followed as shown in the test


case. The number of TRX is equally divided
between coverage and capacity areas.

Configuration is successfull. BTS come into WO


state without any alarm.

Test calls are made. The calls are triggered to


handover between coverage and capacity areas
by varying signal strength.

Calls are handed over between coverage and


capacity areas without any problems.

Case Ref.

Configuration

Coverage
TRX

Capacity TRX

BCCH TRX

Hopping (Coverage/
Capacity)

4 Omni

CTDA

HVTD

Master

BB/None

4 Omni

CTxx

HVTx

Slave

RF/RF

4 Omni

CTxx

HVTx

Master

BB/BB

48 (152)

Nokia Siemens Networks

Intelligent Shutdown for MetroSite

Intelligent Shutdown for MetroSite


Note 31.
For all Intelligent Shutdown test cases neighbours are defined for BTS under test.
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 32.
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 will be reported as
Shutdown. And the Device Administrative State will be reported as Missing .
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 shutdown mode shall be visible on
the equipment view and could be verified as shutdown.
The TRXs not in shutdown mode shall be shown as supervisory.
The TRXs could be verified as being in shutdown or supervisory mode on the BTS
Manager using the objects/properties command.
Note 33.
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_id>:INBR=1:ROU=MAINS:POL=<OPEN - active or CLOSED inactive>,SEV=AL3;

Note 34.
For Intelligent Shutdown cases RDIV=N should be used.

Nokia Siemens Networks

49 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Note 35.
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_id>:BBU=NONE,NTIM=<NTIM_timer>,NTIM2=<NTIM_timer2>,NTI
M3=<NTIM_timer3>,BTIM=<BTIM_timer>;.
Note 36.
Spectrum analyser is connected to the BCCH TRX to monitor the BCCH Transmission
during all Intelligent Shutdown test cases.
Note 37.
When BTS_CONF_DATA message is received during 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 shutdown
TRXs reside, even if the actual configuration is skipped for these.
Note 38.
The feature consists of three BTS Battery Backup procedures that may be applied on
mains failure, these are:

All shutdown mode - maintain full service,

BCCH shutdown mode - maintain the BCCH TRXs,

None shutdown mode - maintain only the transmission equipment.

Note 39.
It is possible to Activate Intelligent Shutdown with Timer Control with the MML
command EFM:
ZEFM:<bcf_id>:BBU=<BTS battery backup procedure>,NTIM=1,BTIM=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.
NTIM=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.
BTIM=3 means that the BCCH TRXs will be maintained for three minutes after the nonBCCH TRXs are shut down, that is, until the BTIM timer expires. This can be any
value from 1 minute to 600 minutes (integer value only).
With BSS13, a new functionality has been added to the intelligent shutdown feature.
With this functionality the TRXs can be grouped together and then NTIM can be
defined for individual groups.
To define a TRX in a particular group use the following command
ZERM:BTS=<bts id>,TRX=<trx id>::SDG=X;

50 (152)

Nokia Siemens Networks

Intelligent Shutdown for MetroSite

Where X is the value of the TRX shutdown group, its value can vary from 1 to 4
The NTIM for each such group can be defined using following command
ZEFM:<bcf_id>:BBU=<BTS battery backup procedure>,NTIM=x,NTIM2=y,NTIM3=z;
Where x, y and z can have values from 1 minute to 600 minutes (integer value only).
By default all TRXs are defined in group 0.
Each shutdown group TRX will shutdown after the expiry of the respective timer.
Note 40.
NTIM=1 and BTIM=3 should be used unless otherwise stated

TRX type

Timer 1
Power State

Timer 2
Power State

Timer 3
Power
State

Timer 4
Power State

Timer 5
Power State

TRX 1
BCCH
TRX 2 - TCH

ON

WO

ON

WO

ON

WO

ON

OFF

ON

WO

ON

OFF

ON

WO

ON

BLPWR
BLPWR

OFF

TRX 3 - TCH

BLSHD
BLSHD

OFF

OFF

BLSHD
BLPWR
BLPWR

OFF
OFF

BLPWR
BLPWR
BLPWR

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

Nokia Siemens Networks

51 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

8.1

All Shutdown Mode


Purpose:
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 41.
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_id>:BBU=ALL;.

Input

Expected Output

The Site is in operational state. Make calls on all


TRXs.

All calls are successful.

The mains breakdown alarm is generated.

Alarm 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP is reported at the BSC and
BTS Manager.
The calls remain ongoing.
The BSC does nothing in response to the alarm.

After 5 minutes, cancel the mains breakdown


alarm.

The Alarm 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP is cancelled at the BSC and
the BTS Manager.
All calls remain ongoing.

Make new calls on all TRXs

All calls are successful.

The process is repeated 5 times for consistency.


Case ref.

Configuration

4+4+4, EDGE chained configuration

8.2

BCCH Shutdown Mode


Purpose:
The purpose of the test cases is to verify the functionality of the BCCH shutdown
mode, which allows all the BCCH TRXs and all units required to sustain BCCH
transmission to remain operational. All non-BCCH TRXs are shutdown.
Note 42.
For all test cases relevant to the BCCH Shutdown Mode the service level is set at the
BSC accordingly using the MML command ZEFM:<bcf_id>:BBU=BCCH;.

52 (152)

Nokia Siemens Networks

Intelligent Shutdown for MetroSite

Note 43.
After the site enters the BCCH Shutdown mode, the calls are handed over to the
neighbour/BCCH TRX and there are no calls left on the BCCH TRX in case BB
Hopping is activated in the sector. In case of Non/RF Hopping calls on BCCH TRX will
remain active.
Note 44.
In cases with BCCH Shutdown Mode were the BCCH is on Slave TRX the Master TRX
will also go into BL-PWR State but the Master TRX functionality will still be active.
Note 45.
NTIM timer is set using MML
ZEFM:<bcf_id>:NTIM=<NTIM_timer>NTIM2=<NTIM_timer2>,NTIM3=<NTIM_time
r3>;

Input

Expected Output

The Site is in operational state. Make calls on all


TRXs.

All calls are successful.

Nokia Siemens Networks

53 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

The mains breakdown alarm is generated.

Alarm 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP 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 by the
BSC expires or all the calls have been handed off
then the BSC sends the
BTS_PWR_SUPPLY_CONTROL (switch off each
non BCCH TRX) message to the BTS.
BB hopping: If BB-hopping then the
BTS_CONF_DATA is sent which modifies the
hopping groups as Non-hopping. The calls are
handed over to the neighbours.
The Master TRX turns off the power of the TRXs
mentioned in the
BTS_PWR_SUPPLY_CONTROL message. All
non-BCCH Slave TRXs are put to BL-PWR state
indicating that these have been shutdown. The
Master TRX and the BCCH TRXs remain
operational.
Chained configuration: When all TRXs in the
Slave BTSs are put to shutdown mode, the
Master TRX (Master BTS) switches off the power
to the Slave BTSs.

The state of the TRXs is verified on the BTS


Manager using the object/properties.

The state of the TRXs is shown as defined in


Note 32.

New calls are established on the BCCH TRXs.

All calls are successful.

54 (152)

Nokia Siemens Networks

Intelligent Shutdown for MetroSite

Input

Expected Output

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 and
BTS Manager.
The BSC sends BTS_PWR_SUPPLY_CONTROL
(switch ON each non BCCH TRX) message to the
BTS.
All Non-BCCH Slave TRXs (and BTS(s)) are
switched back ON. All TRXs are initialised and
go to WO state.
All calls on the BCCH TRX remain ongoing.
BB hopping: If BB-hopping then the
BTS_CONF_DATA is sent which modifies the
hopping groups. The calls are handed over to the
neighbours.

New calls are established on the Non-BCCH


TRXs.

New Calls are successful.

The process is repeated 5 times for consistency.


Case ref.

Configuration

BCCH TRX

Hopping Mode

2+2, GSM+ EDGE

Master+Slave

RF hopping in 1st sector

2nd sector DFCA enabled with DFCA


TRX
2

4 Omni EDGE

Slave

BB hopping

1+1+1+1 EDGE

Master

None

4+4+4, GSM+EDGE+GSM/EDGE
chained configuration, common BCCH
(BTS1 & BTS2)

Slave

BB-hopping in all sectors

4+4+4, GSM+EDGE+GSM/EDGE
chained configuration, common BCCH
(BTS1 & BTS2) with TSC of Non BCCH
TRXs different from the BCC

Master as
Preferred
BCCH

RF-hopping in 3rd sector

GPRS Synchronisation and Data transfer in BTS


Input

Expected Output

The Site is in operational state. GP timeslots are


defined on non-BCCH TRX using MML
ZEQV:BTS=<bts_id>:BFG=2;.
GPRS data transfer is initiated using CS1 and
CS2 coding schemes.

Nokia Siemens Networks

Data transfer is successful.

55 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

The mains breakdown alarm is generated.

Alarm 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP 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 Data Transfer is handed over from the nonBCCH TRXs to the neighbour (GPRS enabled) or
to the BCCH TRX of the sector. When the Handoff timer started by the BSC expires or all the
Data Transfer have been handed off then the
BSC sends the BTS_PWR_SUPPLY_CONTROL
(switch OFF each non BCCH TRX) message to
the BTS.

The state of the TRXs is verified on the BTS


Manager using the object/properties.

The state of the TRXs is shown as defined in


Note 32

Site is in BCCH shutdown mode state.

GP timeslots moves to BCCH TRX from nonBCCH TRX.

GPRS data transfer is initiated using CS1 and


CS2 coding schemes.
The mains breakdown alarm is cancelled whilst
the site is in the BCCH shutdown mode state.

Data transfer is successful.

The 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP is cancelled at the BSC and
BTS Manager.
The BSC sends BTS_PWR_SUPPLY_CONTROL
(switch on each non BCCH TRX) message to the
BTS.
All Non-BCCH Slave TRXs (and BTS(s)) are
switched back on. All TRXs are initialised and go
to WO state.

The process is repeated 5 times for consistency.


Case
ref.

Configuration

BCCH TRX

4 Omni TRX, EDGE

Master

56 (152)

Nokia Siemens Networks

Intelligent Shutdown for MetroSite

EGPRS Data Transfer in BTS


Input

Expected Output

The Site is in operational state. GP timeslots are


defined on non-BCCH TRX.
EGPRS data transfer is initiated using MCS-9
coding scheme in UL/DL direction.
Data transfer is successful.
The mains breakdown alarm is generated.

Alarm 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP 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 Data Transfer is handed over from the nonBCCH TRXs to the neighbour (EGPRS enabled)
or to the BCCH TRX of the sector. When the
Hand-off timer started by the BSC expires or all
the data Transfer have been handed off then the
BSC sends the BTS_PWR_SUPPLY_CONTROL
(switch OFF each non BCCH TRX) message to
the BTS.

The state of the TRXs is verified on the BTS


Manager using the Object/Properties.

The state of the TRXs is shown as defined in


Note 32.

Site is in BCCH shutdown mode state.

GP timeslots moves to BCCH TRX from nonBCCH TRX.


For test case 6, GP timeslots will not move to
BCCH TRX from non-BCCH TRX, so EGPRS
data transfer is not possible.

For test case 7, EGPRS data transfer is initiated


using MCS-9 coding scheme in UL/DL direction.

Nokia Siemens Networks

Data transfer is successful.

57 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

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 and
BTS Manager.
The BSC sends BTS_PWR_SUPPLY_CONTROL
(switch on each non BCCH TRX) message to the
BTS.
All Non-BCCH Slave TRXs (and BTS(s)) are
switched back on. All TRXs are initialised and go
to WO state.
For Test Case 5,GP timeslots are back on TRXs
for which EDAP is enabled.

EGPRS data transfer is initiated using MCS-9


coding scheme in UL/DL direction.

Data Transfer is successful.

The process is repeated 5 times for consistency.


Case
ref.

Configuration

BCCH TRX

EDAP enabled

4 Omni TRX, EDGE

Master

All TRXs

8.3

None Shutdown Mode


Purpose:
The purpose of the test case is to test the None Shutdown Mode without the BTIM
Timer expiry.
Note 46.
For all test cases relevant to the NONE Shutdown Mode the service level is set at the
BSC accordingly using the MML command ZEFM:<bcf_id>:BBU=NONE;.

Input

Expected Output

The Site is in operational state. Make calls on all


TRXs.

All calls are successful.

The mains breakdown alarm is generated.

Alarm 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP is reported at the BSC and
BTS Manager.

58 (152)

Nokia Siemens Networks

Intelligent Shutdown for MetroSite

Input

Expected Output
The calls are handed over from the BCCH/nonBCCH TRXs to the neighbour. When the Handoff timer started by the BSC expires or all calls
have been handed off then the BSC sends the
BTS_PWR_SUPPLY_CONTROL (switch OFF
each TRX) message to the BTS.
The power to all the Slave TRXs is switched OFF
and the TRXs are put to BL-PWR state at the
BSC, indicating that these have been shutdown.
The Master TRX remains powered but is set to
BL-PWR state.

The state of the TRXs is verified on the BTS


Manager using the object/properties.

The state of the TRXs is shown as defined in


Note 32.

The mains breakdown alarm is cancelled whilst


the site is in the None shutdown mode state.

The 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP is cancelled at the BSC and
BTS Manager. The BSC sends
BTS_PWR_SUPPLY_CONTROL (switch ON
each TRX) message to the BTS.
All Slave TRXs are switched back ON. All TRXs
are initialised and go to WO state.

The state of the TRXs is verified on the BTS


Manager using the object/properties.

All TRXs are shown as being in the supervisory


mode.

New calls are established on the TRXs.

New Calls are successful.

The process is repeated 5 times for consistency.


Case
ref.

Configuration

NTIM timer enabled

Hopping Mode

Multi TRX EDGE 1

NTIM timer is configured

RF hopping

Perform the test case with BCCH once on Master TRX. Repeat it with BCCH on a Slave TRX

Purpose:
The purpose is to test the None Shutdown Mode with the Timers, NTIM and BTIM.
This is to test the correct operation when the Timer NTIM and BTIM expire.

Nokia Siemens Networks

59 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

The Site is in operational state. Make calls on all


TRXs.

All calls are successful.

The intelligent shutdown with both timers is


activated for the NONE Shutdown mode.

ZEFM:<bcf_id>:NTIM=<NTIM_timer>,BTIM
=<BTIM_timer>;
The mains breakdown alarm is generated.

Alarm 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP is reported at the BSC and
BTS 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 the
BSC expires or all the calls are handed off then
the BSC sends the
BTS_PWR_SUPPLY_CONTROL (switch off each
non BCCH TRX) message to the BTS. The BTIM
timer is started.
BB- hopping: If BB-hopping then the
BTS_CONF_DATA is sent which modifies the
hopping groups as Non-hopping. The calls are
handed over to the neighbours.
The Master TRX turns off the power of the TRXs
mentioned in the
BTS_PWR_SUPPLY_CONTROL message. All
non-BCCH Slave TRXs are put to BL-PWR state
indicating that these have been shutdown. The
Master TRX and the BCCH TRXs remain
operational.
Chained configuration: When all TRXs in the
Slave BTSs are put to shutdown mode, the
Master TRX (Master BTS) switches off the power
to the Slave BTSs.

The state of the TRXs is verified on the BTS


Manager using the Object/Properties.

The state of the TRXs is shown as defined in


Note 32.

New calls are established on the BCCH TRXs.

All calls are successful.

60 (152)

Nokia Siemens Networks

Intelligent Shutdown for MetroSite

Input

Expected Output
The set time for the BTIM timer expires.
The calls are handed over from the BCCH TRXs
to the neighbour cells. When the Hand-off timer
started by the BSC expires or all the calls are
handed off then the BSC sends the
BTS_PWR_SUPPLY_CONTROL (switch OFF
each TRX) message to the BTS.
The power to all the Slave TRXs is switched OFF
and the TRXs are put to BL-PWR state indicating
that these have been shutdown. The Master TRX
remains powered but is set to BL-PWR state.
Chained configuration: When all TRXs in the
Slave BTSs are put to shutdown mode, the
Master TRX (Master BTS) switches OFF the
power to the Slave BTSs.

The state of the TRXs is verified on the BTS


Manager using the Object/Properties.

The state of the TRXs is shown as defined in


Note 32.

The mains breakdown alarm is cancelled whilst


the site is in the None shutdown mode state.

The 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP is cancelled at the BSC and
BTS Manager. The BSC sends
BTS_PWR_SUPPLY_CONTROL (switch ON all
TRXs) message to the BTS.
All Slave TRXs (and BTS(s)) are switched back
ON. All TRXs are initialised and go to WO state.
The calls handed over from the non-BCCH TRXs
should get handed back once the TRXs are
operational as handovers are in place.

The state of the TRXs is verified on the BTS


Manager using the Object/Properties.

All TRXs are shown as being in the supervisory


mode.

New CS calls are set-up after the test case has


been finished.

The New calls are successful.

The process is repeated 5 times for consistency.


Case ref.

Configuration

Hopping Mode

2 +2, EDGE+GSM

RF hopping in 1st sector and BB hopping 2nd


sector

4+4+4 chain configuration,


Common BCCH (BTS1 and BTS2)

RF hopping

3rd sector DFCA enabled

Nokia Siemens Networks

61 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

8.4

Repetitive Intelligent shutdown testing


Purpose:
The purpose is to test the stability of the intelligent shutdown when continuously
triggered.
The site is setup with the None shutdown mode.

Input

Expected Output

Any Multi TRX configuration is in use.


A script, which simulates mains failure with calls
being made before the mains failure, after
different shutdown levels, and after mains
recovery is used.
The test is left ongoing for 24hrs.

All calls are successful.


When mains breakdown failure triggered the
intelligent shutdown is started successfully. All
levels are triggered as requested by script and
site recovers fully after mains recovery.

A-bis, DBUS, and I2C bus are recorded


throughout test case.

BTS_CONF_DATA being sent successfully, even


for TRXs in shutdown mode. TRXs to be
shutdown are being sent shutdown request in
correct order.

BSC and BTS manager alarms history is viewed


for the period of the test case.

No unwanted alarms are raised (e.g. 76xx


alarms) or unexpected object restarts occur (e.g.
TRX resetting).

Case Ref.

Configuration

Any Multi TRX

8.5

BCF Lock/ Unlock from the BSC


Purpose:
The purpose is to test the BCF Lock and Unlock functionality during Intelligent
Shutdown.

62 (152)

Nokia Siemens Networks

Intelligent Shutdown for MetroSite

Input

Expected Output

The Site is in operational state. Make calls on all


TRXs.

All calls are successful.

The mains breakdown alarm is generated.

Alarm 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP is reported at the BSC and
BTS Manager. The NTIM timer is started. The
site starts the shutdown procedure and enters the
BCCH shutdown mode state. Calls from NonBCCH TRXs are handed over to the neighbours
or BCCH TRX

The BCF is locked from the BSC whilst the site is


in the BCCH shutdown mode state.

Calls are released from the BCCH TRX(s). The


state of the BCF is locked at the BSC.
BCCH transmission is stopped.

The state of the TRXs is verified at the BSC and


at 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 shutdown state as defined
in Note 32.

The BCF unlock command is given.

When the BCCH TRX is in resetting state, alarm


7767 BCCH MISSING is active. Alarm 7701 BCF
INITIALIZATION is sent to the BSC while other
alarms are cancelled. The BCF initialises
correctly.
After VIF and Master TRXs have initialised all
units normally, the alarm 7995:MAINS
BREAKDOWN WITH BATTERY BACK-UP is
resent to the BSC and BTS Manager. The BSC
starts the NTIM timer. The NTIM Timer expires
and the site enters the BCCH shutdown mode
state.

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

The calls are successful.


The set time for the BTIM timer expires.
The site enters the None shutdown mode state.

The BCF is locked from the BSC whilst the site is


in 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 and


at the BTS Manager (Objects/Properties).

All the TRXs are shown as BL-USR at the BSC.


At the BTS Manager the shutdown TRXs shall still
be reported as being in shutdown state as defined
in Note 32.

Nokia Siemens Networks

63 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

The BCF unlock command is given.

When the BCCH TRX is in resetting state, alarm


7767 BCCH MISSING is active. Alarm 7701 BCF
INITIALIZATION is sent to the BSC while other
alarms are cancelled.
The BCF initialises correctly.
After VIF and Master TRX have initialised all units
normally, the alarm 7995:MAINS BREAKDOWN
WITH BATTERY BACK-UP is resent to the BSC
and the BTS Manager.
The BSC starts the NTIM timer. The NTIM Timer
expires and the site enters the BCCH shutdown
mode state.

Case ref.

Configuration

Hopping Mode

BCCH TRX

1.

4 Omni EDGE

None

Master

DFCA enabled with DFCA TRX


2.

4+4+4 chain configuration,


Common BCCH (BTS1 and
BTS2)

RF-hopping in all sectors

Slave

4+4+4 chain configuration,


Common BCCH (BTS1 and
BTS2)

BB-hopping in all sectors

Slave

4+4+4 chain configuration,


Common BCCH (BTS1 and
BTS2), use compressed
signalling

RF-hopping in all sectors

Master as Preferred
BCCH

8.6

BTS Lock/Unlock from the BSC


Purpose:
The purpose is to test the BTS Lock and Unlock functionality during Intelligent
Shutdown.

Input

Expected Output

The Site is in operational state. Make calls on all


TRXs.

All calls are successful.

64 (152)

Nokia Siemens Networks

Intelligent Shutdown for MetroSite

Input

Expected Output

The mains breakdown alarm is generated.

Alarm 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP is reported at the BSC and
BTS Manager. The site starts the shutdown
procedure and enters the BCCH shutdown mode
state. Calls from Non-BCCH TRXs are handed over
to the neighbours or BCCH TRX

The BTS stated in the test case is Locked from


the BSC whilst the site is in the BCCH
shutdown mode state.

The BTS is successfully locked and the state of the


affected BTSs is locked at the BSC.

The state of the TRXs is verified at the BSC and


at the BTS Manager (Objects/Properties).

All the TRXs for the locked BTS are shown as BLUSR at the BSC. At the BTS Manager the
shutdown TRXs shall still be reported as being in
shutdown state as defined in Note 32.

The BTS unlock command is given.

All the TRXs are initialised correctly and go to the


WO state. The alarm 7995:MAINS BREAKDOWN
WITH BATTERY BACK-UP is not cancelled and is
still present at the BSC and BTS Manager.

New calls are established on all TRX(s).

The calls are successful.

BCCH BTS-BCCH shutdown mode state: Calls


are released from only the BCCH TRX(s) under the
BTSs Locked. All other calls remain ongoing.
BCCH transmission is stopped. The affected
BCCH TRX is set to BL-USR state.

Unlocked BTS Stays in WO.


The mains breakdown alarm is cancelled.

The 7995:MAINS BREAKDOWN WITH BATTERY


BACK-UP is cancelled at the BSC and BTS
Manager.
All the TRXs are remain in WO state.

New calls are established on all TRX(s).

The calls are successful.


Unlocked BTS Stays in WO.

Case
ref.

Configuration

Hopping Mode

BTS
Locked/
Unlocked

Shutdown
mode state

BCCH TRX

1.

2+2 EDGE

RF hopping + BB hopping

BTS11

BCCH

Master

2.

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

None

BTS2

None

Slave

3rd sector DFCA


enabled with
DFCA TRXs
1

Repeat for Both BTSs

Nokia Siemens Networks

65 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

8.7

TRX Lock/Unlock from the BSC


Purpose:
The purpose is to test the TRX Lock and Unlock functionality during Intelligent
Shutdown.

Input

Expected Output

The Site is in operational state. Make calls on all


TRXs.

All calls are successful.

The mains breakdown alarm is generated.

Alarm 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP is reported at the BSC and
BTS Manager. The site starts the shutdown
procedure and enters the BCCH shutdown mode
state. Calls from Non-BCCH TRXs are handed
over to the neighbours or BCCH TRX

The TRX stated in the test case is locked.

The TRX is successfully locked. (If the locked


TRX is the BCCH TRX then the calls on BCCH
TRX are handed over to the neighbours.)

The state of the TRXs is verified at the BSC and


at the BTS Manager (objects/properties).

The TRX locked is shown as BL-USR at the BSC.


At the BTS Manager the shutdown TRXs shall still
be reported as being in shutdown state.

The TRX unlock command is given.

The TRX is initialised correctly and goes to the


WO state.
The alarm 7995:MAINS BREAKDOWN WITH
BATTERY BACK-UP is not cancelled and is still
present at the BSC and BTS Manager.

New calls are established on the unlocked


TRX(s).

The calls are successful.

The mains breakdown alarm is cancelled.

The 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP is cancelled at the BSC and
BTS Manager. The BSC sends
BTS_PWR_SUPPLY_CONTROL (switch on all
TRXs) message to the BCF for each BTS.

Unlocked TRX Stays in WO.

The remaining TRXs in the shutdown sectors are


restarted.
New calls are established on all TRX

The calls are successful.


Unlocked TRX Stays in WO.

Case
ref.

66 (152)

Configuration

Hopping Mode

Nokia Siemens Networks

TRX Locked/
Unlocked

Shutdown
Mode
State

BCCH
TRX

Intelligent Shutdown for MetroSite

Input

Expected Output

1.

2+2 EDGE

RF hopping +BB
hopping

Non-BCCH2
TRX of 1st
sector

BCCH

Master as
Preffered
BCCH

2.

4+4+4, Common BCCH


(BTS1 and BTS2)

Non-hopping in all
sectors

Non-BCCH1

BCCH

Slave

1
2

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


Repeat with BCCH TRX

8.8

Site Reset from BSC and BTS Manager


Purpose:
The purpose is to test the Site Reset functionality during Intelligent Shutdown.

Input

Expected Output

The Site is in operational state. Make calls on all


TRXs.

All calls are successful.

Shutdown mode used: BCCH

Alarm 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP is reported at the BSC and
BTS Manager. The site starts the shutdown
procedure and enters the BCCH shutdown mode
state. Calls from Non-BCCH TRXs are handed
over to the neighbours or BCCH TRX as per Note
43

The mains breakdown alarm is generated.

The site is Reset as detailed in the test case


whilst the site is in BCCH shutdown mode state.

Calls are released from the BCCH TRX(s). BCCH


transmission is stopped.
When the BCCH TRX is in resetting state, alarm
7767 BCCH MISSING is active. Alarm 7701 BCF
INITIALIZATION is sent to the BSC while other
alarms are cancelled.
The BCF initialises correctly.
After VIFA and Master TRX have initialised all
units normally, the alarm 7995:MAINS
BREAKDOWN WITH BATTERY BACK-UP is
resent to the BSC and the BTS Manager. The
BSC starts the NTIM timer. The NTIM Timer
expires and the site enters the BCCH shutdown
mode state.

Nokia Siemens Networks

67 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

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 and BTS
Manager. The BSC sends
BTS_PWR_SUPPLY_CONTROL (switch ON all
TRXs) message to the BTS.
All Slave TRXs (and BTS(s)) are switched back
ON. 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

Alarm 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP is reported at the BSC and
BTS Manager.

The mains breakdown alarm is generated.

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 the
BSC expires or all the calls are handed off then
the BSC sends the
BTS_PWR_SUPPLY_CONTROL (switch off each
non BCCH TRX) message to the BTS. The BTIM
timer is started.
BB- hopping: If BB-hopping then the
BTS_CONF_DATA is sent which modifies the
hopping groups as Non-hopping. The calls are
handed over to the neighbours.
The Master TRX turns off the power of the TRXs
mentioned in the
BTS_PWR_SUPPLY_CONTROL message. All
non-BCCH Slave TRXs are put to BL-PWR state
indicating that these have been shutdown. The
Master TRX and the BCCH TRXs remain
operational.
Chained configuration: When all TRXs in the
Slave BTSs are put to shutdown mode, the
Master TRX (Master BTS) switches off the power
to the Slave BTSs.
New calls are established on the BCCH TRXs.

68 (152)

Nokia Siemens Networks

All calls are successful.

Intelligent Shutdown for MetroSite

Input

Expected Output
The set time for the BTIM timer expires.
The calls are handed over from the BCCH TRXs
to the neighbour cells. When the Hand-off timer
started by the BSC expires or all the calls are
handed off then the BSC sends the
BTS_PWR_SUPPLY_CONTROL (switch OFF
each TRX) message to the BTS.
The power to all the Slave TRXs is switched OFF
and the TRXs are put to BL-PWR state indicating
that these have been shutdown. The Master TRX
remains powered but is set to BL-PWR state.
Chained configuration: When all TRXs in the
Slave BTSs are put to shutdown mode, the
Master TRX (Master BTS) switches OFF the
power to the Slave BTSs.

The site is Reset as detailed in the test case


whilst the site is in None shutdown mode state.

The site starts resetting.


The BCF initialises correctly.
After VIFA and Master TRX have initialised all
units normally, the alarm 7995:MAINS
BREAKDOWN WITH BATTERY BACK-UP is
resent to the BSC and the BTS Manager. The
BSC starts the NTIM timer. The NTIM Timer
expires and the site enters the BCCH shutdown
mode 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 and BTS
Manager. The BSC sends
BTS_PWR_SUPPLY_CONTROL (switch ON all
TRXs) message to the BTS.
All Slave TRXs (and BTS(s)) are switched back
ON. All TRXs are initialised and go to WO state.

New calls are established on all TRX(s).

All calls are successful.

Case ref.

Configuration

Hopping Mode

Site Reset

BCCH TRX

1.

2+2 EDGE/GSM

BB-hopping +RF
hopping

BSC - <ZEFS> MML


command

Master

2.

4+4+4, Common BCCH


(BTS1 and BTS2)

RF-hopping in all
sectors

BTS Manager
Object/Properties/BCF
Reset

Slave

Nokia Siemens Networks

69 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

8.9

BCF Block/Unblock from BTS Manager


Purpose:
The purpose is to test that the correct operation is being performed when
blocking/Unblocking objects from the BTS Manager during intelligent shutdown
procedure.

Input

Expected Output

The Site is in operational state. Make calls on all


TRXs.

All calls are successful.

The mains breakdown alarm is generated.

Alarm 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP is reported at the BSC and
BTS Manager. The site starts the shutdown
procedure and enters the BCCH shutdown mode
state. Calls from Non-BCCH TRXs are handed
over to the neighbours or BCCH TRX.

The BCF is blocked from the BTS Manager whilst


the site is in BCCH shutdown mode state.

Calls are released from the BCCH TRX(s). The


state of the BCF is BL-BCF at the BSC. The
alarm 7208 LOCAL BLOCK: BCF is sent to BSC
and BTS Manager. BCCH transmission is
stopped.

The state of the TRXs is verified at the BSC and


at the BTS Manager (objects/properties).

All the TRXs are shown as BL-BCF at the BSC.


At the BTS Manager the shutdown TRXs shall still
be reported as being in shutdown state as defined
in Note 32.

The BCF unblock command is given from the


BTS Manager.

The BCF initialises correctly. The alarm 7208


LOCAL BLOCK: BCF is cancelled at the BSC and
at the BTS Manager.
After VIFA and the Master TRX have initialised all
units normally, the alarm 7995:MAINS
BREAKDOWN WITH BATTERY BACK-UP is
resent to the BSC and the BTS Manager. . The
BSC starts the NTIM timer. The NTIM Timer
expires and the site enters the BCCH shutdown
mode state.

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

The calls are successful.


The set time for the BTIM timer expires.
The site enters the None shutdown mode state.

The BCF is blocked from the BTS Manager whilst


the site is in None shutdown mode state.

70 (152)

Nokia Siemens Networks

The state of the BCF is blocked at the BSC. The


alarm 7208 LOCAL BLOCK: BCF is sent to BSC
and BTS Manager.

Intelligent Shutdown for MetroSite

Input

Expected Output

The state of the TRXs is verified at the BSC and


at the BTS Manager (Objects/Properties).

All the TRXs are shown as BL-BCF at the BSC.


At the BTS Manager the shutdown TRXs shall still
be reported as being in shutdown state as defined
in Note 32.

The BCF unblock command is given from the


BTS Manager.

The BCF initialises correctly. The alarm 7208


LOCAL BLOCK: BCF is cancelled at the BSC and
at the BTS Manager.
After VIFA and the Master TRX have initialised all
units normally, the alarm 7995:MAINS
BREAKDOWN WITH BATTERY BACK-UP is
resent to the BSC and the BTS Manager. The
BSC starts the NTIM timer. The NTIM Timer
expires and 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 chain
configuration,
GSM+EDGE+GS
M/EDGE

RF hopping in all sectors

Slave

8.10

BTS Block/Unblock from the BTS Manager

Purpose:
The purpose is to test the BTS block and Unblock functionality during Intelligent
Shutdown.

Input

Expected Output

The Site is in operational state. Make calls on all


TRXs.

All calls are successful.

The mains breakdown alarm is generated.

Alarm 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP is reported at the BSC and
BTS Manager. The site starts the shutdown
procedure and enters the BCCH shutdown mode
state. Calls from Non-BCCH TRXs are handed
over to the neighbours or BCCH TRX

Nokia Siemens Networks

71 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

The BTS stated in the test case is blocked from


the BTS Manager whilst the site is in BCCH
shutdown mode state.

Calls are released from only the BCCH TRX


under the BTS Blocked. calls on BCCH TRX of
other BTSs remain ongoing.
The alarm 7208 LOCAL BLOCK: BTS is sent to
the BSC and the BTS Manager.
The state of the affected BTS is BL-BTS at the
BSC.
BCCH transmission is stopped.

The state of the TRXs is verified at the BSC and


at the BTS Manager (Objects/Properties).

At the BTS Manager the shutdown TRXs shall still


be reported as being in shutdown state as defined
in Note 32.
At the BSC the affected BCCH TRX is set to BLBTS state at the BSC and the Non-BCCH TRXs
are shown as BL-PWR.

The BTS unblock command is given from the


BTS Manager.

The alarm 7208 LOCAL BLOCK: BTS is


cancelled at the BSC and at the BTS Manager.
When the BCCH TRX is initialised, alarm 7767
BCCH MISSING is active. Alarm 7767 is
cancelled when BCCH TRX goes to WO state.
BTS comes up correctly. Only the BCCH TRX
under the BTS unblocked is initialised.

The state of the TRXs is checked at the BTS


Manager (Objects/Properties).

At the BTS Manager the shutdown TRXs shall still


be reported as being in shutdown state as defined
in Note 32.

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

The calls are successful.


The set time for the BTIM timer expires.
The site enters the None shutdown mode state.

The same BTS is Blocked from the BTS Manager


whilst the site is in None shutdown mode state.

The state of the BTS is BL-BTS at the BSC. The


alarm 7208 LOCAL BLOCK: BTS is sent to BSC
and BTS Manager. All the TRXs remain in the
same state as before the BTS was blocked.

The BTS unblock command is given from the


BTS Manager.

The BTS is reset but all the TRXs stay in the


shutdown state.
The alarm 7208 LOCAL BLOCK: BTS is
cancelled at the BSC and at the BTS Manager.
The TRXs are not initialised.

The state of the TRXs is checked at the BTS


Manager (Objects/Properties).

72 (152)

Nokia Siemens Networks

At the BTS Manager the shutdown TRXs shall still


be reported as being in shutdown state..

Intelligent Shutdown for MetroSite

Input

Expected Output

Case ref.

Configuration

Hopping Mode

BTS Blocked/
Unblocked

BCCH TRX

1.

2+2, EDGE+GSM

RF hopping in 1st
sector

BTS1

Master

RF hopping +BB
hopping

BTS31

Slave

2nd sector DFCA


enabled with DFCA
TRX
2.

4+4+4 chain
Configuration
3rd sector DFCA
enabled

Repeat with BTS1 and BTS2

8.11

TRX Block/Unblock from the BTS Manager

Purpose:
The purpose is to test the TRX block and Unblock functionality during Intelligent
Shutdown.
Input

Expected Output

The Site is in operational state. Make calls on all


TRXs.

All calls are successful.

The mains breakdown alarm is generated.

Alarm 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP is reported at the BSC and
BTS Manager. The site starts the shutdown
procedure and enters the BCCH shutdown mode
state. Calls from Non-BCCH TRXs are handed
over to the neighbours or BCCH TRX

Nokia Siemens Networks

73 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

The TRX stated in the test case is blocked from


the BTS Manager whilst the site is in BCCH
shutdown mode state.

Non-BCCH TRX: As the TRX is in Shutdown


State the option for TRX block/unblock/reset is
not enable at BTS Manager.
All calls remain ongoing.
BCCH TRX: Calls are released from only the
BCCH TRX blocked. All other calls remain
ongoing.
The alarm 7208 LOCAL BLOCK: TRX is sent to
the BSC and to the BTS Manager.
The state of the affected TRX is BL-TRX at the
BSC.
BCCH transmission is stopped.

The state of the TRXs is checked at the BTS


Manager (Objects/Properties).

At the BTS Manager the shutdown TRXs shall still


be reported as being in shutdown state as defined
in Note 32.

BCCH TRX test cases: The TRX unblock


command is given from the BTS Manager.

BCCH TRX: The TRX is initialised correctly and


goes to the WO state The alarm 7208 LOCAL
BLOCK: TRX is cancelled at the BSC and at the
BTS Manager.

The state of the TRXs is checked at the BTS


Manager (objects/properties).

At the BTS Manager the shutdown TRXs shall still


be reported as being in shutdown state as defined
in Note 32.

New calls are established on the BCCH TRX

The calls are successful.


The set time for the BTIM timer expires.
The site enters the None shutdown mode state.

Block the same TRX from BTS Manager whilst


the site is in None shutdown mode state.

As the TRX is in Shutdown State the option for


TRX block/unblock/reset is not enable at BTS
Manager.

The state of the TRXs is checked at the BTS


Manager (Objects/Properties).

At the BTS Manager the shutdown TRXs shall still


be reported as being in shutdown state as defined
in Note 32.

Case ref.

Configuration

Hopping Mode

TRX Blocked/
Unblocked

BCCH TRX

1.

4+4+4 chain
configuration

RF hopping +BB
hopping+None

Non-BCCH1

Master

74 (152)

Repeat with BCCH TRX

Nokia Siemens Networks

of 1st and 3rd


sector

Intelligent Shutdown for MetroSite

8.12

BTS reset from BTS Manager

Purpose:
The purpose is to test the BTS reset being performed from the BTS Manager during
Intelligent Shutdown.
Input

Expected Output

The Site is in operational state. Make calls on all


TRXs.

All calls are successful.

The mains breakdown alarm is generated.

Alarm 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP is reported at the BSC and
BTS Manager. The site starts the shutdown
procedure and enters the BCCH shutdown mode
state. Calls from Non-BCCH TRXs are handed
over to the neighbours or BCCH TRX

The BTS reset command is given from the BTS


Manager for BCCH BTS.

BCCH Sector: BCCH Sector: BTS comes up


correctly. Only the BCCH TRX under the BTS
unblocked is initialised.
The BTS is not reset as all TRXs under BTS are
in shutdown state. All the TRXs remain in the
same state as before the BTS was reset.

The state of the TRXs is checked at the BTS


Manager (Objects/Properties).

At the BTS Manager the shutdown TRXs shall still


be reported as being in shutdown. The BCCH
TRX shall be reported as Supervisory.

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

The calls are successful


The set time for the BTIM timer expires.
The site enters the None shutdown mode state.

The same BTS is reset from the BTS Manager


whilst the site is in None shutdown mode state.

The BTS is not reset as all TRXs under BTS are


in shutdown state. All the TRXs remain in the
same state as before the BTS was reset.

The state of the TRXs is checked at the BTS


Manager (Objects/Properties).

At the BTS Manager the shutdown TRXs shall still


be reported as being in shutdown state as defined
in Note 32.

The test is repeated for all the BTSs.


Case
ref.
1.

Configuration

Hopping Mode

BCCH TRX

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

RF-hopping in all sectors

Master

Nokia Siemens Networks

75 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

8.13

TRX Reset from BTS Manager

Purpose:
The purpose is to test the BCCH TRX Reset functionality during Intelligent Shutdown.
Input

Expected Output

The configuration in use is as listed in the test


case.
The Site is in operational state with calls ongoing
on all TRXs.
The mains breakdown alarm is generated.

Alarm 7995:MAINS BREAKDOWN WITH


BATTERY BACK-UP is reported at the BSC and
BTS Manager. The site starts the shutdown
procedure and enters the BCCH shutdown mode
state. Calls from Non-BCCH TRXs are handed
over to the neighbours or BCCH TRX
In case of BB hopping calls are handed over to
neighbours.

The TRX stated in the test case is reset from the


BTS Manager whilst the site is in BCCH
shutdown mode state.

BCCH TRX: Calls are released from only the


BCCH TRX reset. All other calls remain ongoing.
BCCH transmission is stopped.
The TRX is initialised correctly and goes to the
WO state. The associated Fan becomes
operational.
Non-BCCH TRX: As the TRX is in Shutdown
State the option for reset is not enable at BTS
Manager.
All calls remain ongoing.

The state of the TRXs is checked at the BTS


Manager (Objects/Properties).

At the BTS Manager the shutdown TRXs shall still


be reported as being in shutdown state.
The BCCH TRX is identified as SUPERVISORY.

New calls are established on the BCCH TRX

The calls are successful.


The set time for the BTIM timer expires.
The site enters the None shutdown mode state.

Reset the same TRX from BTS Manager whilst


the site is in None shutdown mode state.

76 (152)

Nokia Siemens Networks

As the TRX is in Shutdown State the option for


reset is not enable at BTS Manager.

Intelligent Shutdown for MetroSite

Input

Expected Output

The state of the TRXs is checked at the BTS


Manager (Objects/Properties).

At the BTS Manager the shutdown TRXs shall still


be reported as being in shutdown state.

Case ref.

Configuration

Hopping Mode

TRX Reset

BCCH TRX

1.

2+2 EDGE+GSM

RF hopping

BCCH

Master

Nokia Siemens Networks

77 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Recovery for BSS and Site


Synchronisation

9.1

Site Synchronisation Recovery during startup/resets


Purpose:
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.

Input
Define the synchronization chain in the BSC
using the MML command:
ZEFM:<s1>:CS=LMU,SENA=T, ;
<s1> = slave 1 BCF number
Make the traffic channels full rate channels
(TCHF). Lock all TCH channels except
timeslot 2 on each TRX in the multi-BCF
segment.
Physically create and commission the sites.

78 (152)

Nokia Siemens Networks

Expected Output

Recovery for BSS and Site Synchronisation

Input
Monitor the BTS Events window in BTS
Manager, or the Messages and Alarms
window in BTS MMI.
Monitor the Abis.
Reset the Slave BCF(s) using the MML
command:
ZEFR:<BCF No>;

Lock 8 MS to the segment. Make 4 pairs of


speech calls. Speak in both directions for
each call.
The process is repeated 5 times for
consistency.
Case Ref.
1

Expected Output
The BSC sends the Slave BCF a BTS_RESET REQ
with object identity = BCF.
The BCF resets and sends a BTS_OMU STARTED
message with synchronization mode = as per table.
The BCF sends BTS_CONF_REQ to the BSC. The
BSC sends a BTS_LMU_FN_OFFSET COMMAND to
the BCF next to the LMU. The BTS returns a
BTS_LMU_FN_OFFSET_ANSWER with successfailure = success (assuming the LMU is operating
correctly).
The BSC sends a BTS_CLOCK_REQ to the BCFs
with:
Clock sync = BTS_External
Clock output = disabled
The BSC sends the configuration of the sites in
BTS_CONF_DATA messages. The BCFs come into
working order. The BCFs send a
BTS_CONF_COMPLETE. The BTS Events/MMI
window shows that the BCF is in Slave mode and that
the LMU is Master.
All calls set up correctly. The speech in each direction
can be heard clearly.
The sites behaviour is repeatable.

Configuration
LMU+4+4 chain, RF Hopping in both BTS
Figure 2.
LMU SW 4.4
LMU+4+4+4 chain, RF Hopping in all BTS
Figure 3.
LMU SW 4.4
LMU+4+4 chain, RF Hopping in both BTS
Figure 2.
LMU SW 4.4, Use boundary value (lowest)
for Q1 Address (LMU) i.e 0

Nokia Siemens Networks

Sync Mode in BTS_OMU_STARTED


Independent

Independent

Independent

79 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Figure 2.
MASTER
LMU
SLAVE BCF1
BTS1

BTS2

B
C
C
H

BTS 1
Hop = RF
MA = xx (7 ARFCN)
HSN1 = yy
MAIO OFFSET = 1
MAIO STEP = 2

SEGMENT

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

LMU MetroSite - MetroSite

Figure 3.
MASTER
LMU
SLAVE BCF1
BTS1

BTS2

BTS3

11

12

10

B
C
C
H

BTS 1
Hop = RF
MA = xx (7 ARFCN)
HSN1 = yy
MAIO OFFSET = 1
MAIO STEP = 2

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

LMU MetroSite - MetroSite - MetroSite


80 (152)

Nokia Siemens Networks

SEGMENT

BTS 3
Hop = RF
MA = same as BTS 1
HSN1 = same as BTS 1
MAIO OFFSET = 3
MAIO STEP = 2

Recovery for BSS and Site Synchronisation

Purpose:
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.

Input
Make the traffic channels full rate channels
(TCHF). Lock all TCH channels except timeslot 7
on each TRX in the multi-BCF segment.

Expected Output

ZEFM:<s1>:CS=LMU,SENA=T;
<s1> = slave 1 BCF number
Physically create and commission the sites, so
that they are in working order, synchronised to
the LMU.
Power OFF the sites.
Disconnect the LMU cable at the connector
indicated in the test case.
Monitor the Messages and Alarms window in the
BTS Events window in the BTS Manager.
Monitor the Abis. Record a trace.
Power ON the cabinet next to the LMU.
Record the status at the BSC using MML
commands:
ZEOL:<BCF number>;
ZEEI:BCF=<BCF number>;
Continue recording an A-bis trace.
Re-connect the cable.
Make a note of changes in alarm status.
Power ON the 2nd cabinet
Reset the BCF using the MML command:

Check the sync mode at the BTS Manager


Lock 8 MS to the segment. Make 4 pairs of
speech calls. Speak in both directions for each
call.
The process is repeated 5 times for consistency.
Case Ref.
4

The BCF does not initialise and synchronise to


the LMU.BCF come up independently.

The LMU clock output is switched ON.


Use LMU Manager -> Commissioning Wizard to
ensure that.
The BCF comes into working order synchronised
to the LMU.
All alarms caused by the fault are cancelled.
Sync mode is slave.
All calls set up correctly. The speech in each
direction can be heard clearly.
The sites behaviour is repeatable.

Configuration
LMU+4+4 chain configuration, RF Hopping
in both BTS. Figure 2.
LMUB C1.0 CD1
LMU+4+4 chain configuration, RF Hopping
in both BTS. Figure 2.
LMUB SW 1.0. Use boundary value
(highest) for Q1 Address (LMU) i.e 3999

Nokia Siemens Networks

Connector to Disconnect
BTS/Q1 IF

BTS/Q1 IF

81 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input
6

Expected Output
LMU+4+4 chain configuration, RF Hopping BTS/Q1 IF
in both BTS. Figure 2
LMU SW 4.4

9.2

Site Synchronisation recovery with GPS signal


recovery
Purpose:
To check that a previously synchronised chain behaves correctly when the LMUs
GPS signal is lost and then returns. To check that the recovery actions are not
triggered if the GPS outage is less time 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.
Note 48.
With S11 the LMU has an internal timer. If the GPS fix is lost for less than the timer
period the LMU continues to send its clock signal. The synchronisation chain of BCFs
continues to be synchronised by the LMU as if nothing had happened.
After the LMUs timer has expired it sends alarm 1001 clock out disabled. It is this
alarm, which triggers the recovery procedure when it is received at the BSC.
Note 49.
It will be necessary to perform this test either in a screen room, or by fully cabling the
Mobile Stations to the Base Stations. This is because the MS must be able to see, and
hand over to, a neighbouring cell, and cannot therefore be locked onto the segment
being used for test.

Input

82 (152)

Expected Output

Nokia Siemens Networks

Recovery for BSS and Site Synchronisation

Input
Make the traffic channels full rate channels
(TCHF). Lock all TCH channels except timeslot 2
on each TRX in the multi-BCF segment.

Expected Output

Also unlock timeslot 7 on TRX4 in each BTS in


the segment. Make this a dedicated GP timeslot.
Ensure there is a neighbouring BTS to which calls
on the synchronised BCFs may be handed over.
Set the BTS power level of the neighbouring BTS
much lower than the segment so that MS prefer
the segment.
Define the synchronization chain in the BSC
using the MML command:
ZEFM:<s1>:CS=LMU,SENA=T
<s1> = slave 1 BCF number
Select View Advanced. Select Maintenance.
Open the Clock Out Time Settings dialogue
box. Set the Time from fix lost to clocks out alarm
to 240 sec. Set the Time from clocks out alarm to
clock disable to 60 sec.

Physically create and commission the sites, so


that they are in working order, synchronised to
the LMU.
Camp 8 MSs on to the segment. Make sure they
can also see the neighbouring BTS. i.e. it will not
be possible to use the MS field test software to
lock them to the segment. Make 4 pairs of speech
calls. Speak in both directions for each call.
These calls will be left up during the test case.

When The BCF resets it sends a BTS_OMU


STARTED message with synchronisation mode =
slave, regardless of the setting in HW
configuration file.
All calls set up correctly. The speech in each
direction can be heard clearly.

Also establish a further 2 MS, each with a GPRS


transfer ongoing.

Nokia Siemens Networks

83 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input
Monitor the Q1 bus. Monitor the Abis for O&M
messages.
Monitor the BTS Events window in BTS Manager,
or the Messages and Alarms window in BTS MMI.
Disconnect the GPS antenna from the LMU, or
block the antennas view of the satellite. At the
same time start a stop-clock to monitor the length
of time the GPS signal is missing.
Check the status of the calls and transfers.
Check the sync status at BTS Manager / MMI.
Check the sync status at the BSC using the MML
command: ZEFL;
At 3 minutes on the stop-clock, re-establish the
GPS signal to the LMU.

At 4 minutes monitor the Q1 bus.

Expected Output

The LMU sends a GPS fix lost alarm 48 on the


Q1 bus. The BCF sends this up the Abis as an
8048 alarm. However, the LMU does not send a
1001 clock disable alarm. The BCFs continue to
be synchronised by the clock signal from the
LMU.
All calls remain up. Both GPRS transfers remain
ongoing.
BCFs still show as being in slave mode.
Sync Enabled = T, Sync Mode = Sync for the
synchronisation chain.
The LMU sends an alarm 48 cancel on the Q1
bus. The BCF forwards this as an 8048 cancel on
the Abis. The BSC does not begin any further
recovery actions when it receives this alarm.
All calls/transfers remain up. The BCFs continue
to be synchronised by the clock signal from the
LMU.
The LMU does not send any alarms. i.e. the LMU
timer was successfully reset.

The existing calls/transfers may be left up.


Monitor the Q1 bus. Monitor the Abis for O&M
messages.
Monitor the BTS Events window in BTS Manager,
or the Messages and Alarms window in BTS MMI.
Disconnect the GPS antenna from the LMU, or
block the antennas view of the satellite. At the
same time start a stop-clock to monitor the length
of time the GPS signal is missing.

The LMU sends a GPS fix lost alarm 48 on the


Q1 bus. The BCF sends this up the Abis as an
8048 alarm. However, the LMU does not send a
1001 clock disable alarm. The BCFs continue to
be synchronised by the clock signal from the
LMU.

Check the status of the calls.

All calls remain up.

Check the sync status at BTS Manager / MMI.

BCFs still show as being in slave mode.

Check the sync status at the BSC using the MML


command: ZEFL;

Sync Enabled = T, Sync Mode = Synch for the


synchronisation chain.

84 (152)

Nokia Siemens Networks

Recovery for BSS and Site Synchronisation

Input
At 4 minutes on the stop clock monitor the Q1 bus
and Abis.

Check the status of the BCFs using MML


command:
ZEEI:BCF = <BCF number>;
Monitor the MMI and Abis for all of the BCF.

Check the MS carrying the GPRS transfers.


Check the sync status at the BSC for all BCF,
using the MML command:
ZEFL;
Check for alarm 8048 GPS fix lost alarm at BSC
using MML command:
ZEOL:< Slave BCF number>;
Disconnect the calls now on the neighbour. Reestablish 4 pairs of calls on the segment. Speak
in both directions for each call.
Monitor the Q1 bus and the Abis.
Re-establish the GPS signal to the LMU.

Check the status of the BCF using MML


command:
ZEEI:BCF=<BCF number>;

Nokia Siemens Networks

Expected Output
The LMU sends alarm 1001 clocks out disabled.
The first BCF forwards this alarm up the Abis to
the BSC as:
Talk: 7876 LMU. External synchronisation signals
disabled.
Ultra/Metro: 7602 BCF Notification. External
synchronisation signals disabled. (alarm detail =
28)
All calls hand over successfully to the
neighbouring BTS. Both GPRS transfers
successfully reselect the neighbouring BTS.
Immediately following the handover of calls, the
BCF show as BL-BCF or BL-SYS at the BSC.
The BSC resets the BCF in the chain. The BSC
sends a BTS_CLOCK_REQ message on the
Abis, with:
Clock sync = PCM_External
Clock output = Enabled.
The BCF comes into working order in master
mode.
The MS reselect the BTS in the segment again.
Sync Enabled = T, Sync Mode = Unsync for all
BCF in the chain.
8048 alarm is still active.

All calls set up correctly. The speech in each


direction can be heard clearly.
The LMU cancels alarm 48 on the Q1 bus and
this is forwarded by the BCF as a cancellation of
alarm 8048 on the Abis.
All calls hand over successfully to the
neighbouring BTS. The GPRS transfers reselect
the neighbouring BTS.
Immediately following the handover of calls, the
BCF show as BL-BCF or BL-SYS at the BSC.

85 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input
Monitor the MMI and Abis for all of the BCF.

Expected Output
The BSC resets the first BCF in the chain. The
BSC sends a BTS_CLOCK_REQ message on
the Abis, with:
Clock sync = BTS_External
Clock output = Disabled.
The BCF comes into working order in slave mode
synchronised to the restored clock from the LMU.

Check the MS carrying the GPRS transfers.


Check the sync status at the BSC for all BCF,
using the MML command:
ZEFL;
Disconnect the calls now.
Re-establish 4 pairs of calls on the segment.
Speak in both directions for each call.

The MS reselect the BTS in the segment again.


Sync Enabled = T, Sync Mode = Sync for all BCF
in the chain.
All calls set up correctly. The speech in each
direction can be heard clearly.

Case Ref.
1

Configuration.
LMU+4+4 in a segment, , LMU SW 4.4

LMU+4+4 in a segment, Figure 4, LMUB C1.0 CD1

86 (152)

Nokia Siemens Networks

Recovery for BSS and Site Synchronisation

Figure 4.
MASTER
LMU
SLAVE

ADJACENT BCF

BCF 1
BTS3
BTS1

BTS 3 (not in sync chain)


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

B
C
C
H

BTS2

SEGMENT

Set up hopping in the same way as in Figure 2

LMU MetroSite MetroSite + Neighbour

Nokia Siemens Networks

87 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Purpose:
To check that if synchronisation recovery actions are triggered correctly by the clocks
out alarm from the LMU whilst a different 7602 alarm is active.

Input
Define the synchronization chain in the BSC
using the MML command:
ZEFM:<s1>:CS=LMU,SENA=T
<s1> = slave 1 BCF number

Expected Output

At LMU Manager, Select View Advanced.


Select Maintenance and open the Clock Out
Time Settings dialogue box. Set the Time from
fix lost to clocks out alarm to 10 sec. Set the
Time from 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.

Alarm 7602 BCF Notification. Fan unit is broken is


raised.

Monitor the Q1 bus. Monitor the A-bis.


Block the LMU GPS antennas sight of the
satellites (or disconnect the GPS antenna from
the LMU)
After 10 seconds.

Check the status of the BCF using MML


command:
ZEEI:BCF = <BCF number>;
Monitor the MMI and Abis for all of the BCF.

Case Ref.
3

88 (152)

The LMU sends a GPS fix lost alarm 48 on the


Q1 bus. The BCF sends this up the Abis as an
8048 (loss of incoming signal) alarm.
The LMU sends alarm 1001 clocks out disabled.
The BCF forwards this alarm up the Abis to the
BSC as:
7602 BCF Notification. External synchronisation
signals disabled. (Alarm detail = 28)
The BCF show as BL-BCF or BL-SYS at the
BSC.
The BSC resets the BCF in the chain. The BSC
sends a BTS_CLOCK_REQ message on the
Abis, with clock sync value = PCM_External and
clock_output = Enabled. The BCF does not come
into working order in master mode.

Config
LMU+4+4 chain, RF Hopping in both sector

Nokia Siemens Networks

BTS Manager Functionality

10

BTS Manager Functionality

10.1

BTS Manager Start-Up

Purpose:
To check that the BTS Manager can be successfully started.

Input

Expected Output

The PC has SiteWizard of previous main release


installed.
Using SiteWizard of New release, BTS Manager
is installed to the PC.
The BTS Manager of new release is started.
Version is checked from Help | About Nokia BTS
Manager command.
The LMP cable between the PC and The BCF is
removed.

The BTS Manager starts successfully. Version is


correct. Alarm 7801 MMI CONNECTED TO
BASE STATION is sent to BSC and BTS
Manager.
The only available menus are File, Tools,
Window, Connection and Help menus. All toolbar
icons are disabled except icon that activates
command from Help menu.
The only visible window is the BTS Events
window. 'No connection to BTS is repeatedly
displayed in the BTS Events window.
Alarm 7801 MMI CONNECTED TO BTS is
cancelled at the BSC.

The connection is changed to another MetroSite


BTS.

Nokia Siemens Networks

The BTS Manager successfully restarts without


having to close the BTS Manager between the
BCF cable changes. The correct BCF related
menu commands, toolbar buttons, and windows
are available. Alarm 7801 MMI CONNECTED TO
BASE STATION is sent to BSC and MMI.

89 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

The connection previously used on the MetroSite


BTS is changed to an UltraSite BTS.

The BTS Manager successfully restarts without


having to close the BTS Manager between the
BCF cable changes. The correct BCF related
menu commands, toolbar buttons, and windows
are available. Alarm 7801 MMI CONNECTED TO
BASE STATION is sent to BSC and MMI.

BTS manager is disconnected.

BTS Manager is disconnected successfully.


Alarm 7801 MMI CONNECTED TO BASE
STATION is cancelled at the BSC.

Click on Connection -> disconnect menu item


Case Ref.

Site Type/Configuration

Operating System in PC

01

Nokia MetroSite

Windows 98

Multi TRX EDGE/GSM


02

Nokia MetroSite

Windows 2000

Multi TRX EDGE/GSM


03

Nokia MetroSite

Windows XP

Chain Configuration
04

Nokia MetroSite

Windows 2003

Multi TRX EDGE/GSM

Input

Expected Output

The PC has SiteWizard of previous main release


installed.
Using SiteWizard of New release, BTS Manager
is installed to the PC.
The BTS Manager of new release is started.
Version is checked from Help | About Nokia BTS
Manager command.
The LMP cable between the PC and The BCF is
removed.

The BTS Manager starts successfully. Version is


correct. Alarm 7801 MMI CONNECTED TO
BASE STATION is sent to BSC and BTS
Manager.
The only available menus are File, Tools,
Window, Connection and Help menus. All toolbar
icons are disabled except icon that activates
command from Help menu.
The only visible window is the BTS Events
window. 'No connection to BTS is repeatedly
displayed in the BTS Events window.
Alarm 7801 MMI CONNECTED TO BTS is
cancelled at the BSC.

90 (152)

Nokia Siemens Networks

BTS Manager Functionality

Input

Expected Output

The connection is changed to another MetroSite


BTS.

The BTS Manager successfully restarts without


having to close the BTS Manager between the
BCF cable changes. The correct BCF related
menu commands, toolbar buttons, and windows
are available. Alarm 7801 MMI CONNECTED TO
BASE STATION is sent to BSC and MMI.

The connection previously used on the MetroSite


BTS is changed to an UltraSite BTS.

The BTS Manager successfully restarts without


having to close the BTS Manager between the
BCF cable changes. The correct BCF related
menu commands, toolbar buttons, and windows
are available. Alarm 7801 MMI CONNECTED TO
BASE STATION is sent to BSC and MMI.

BTS manager is disconnected.

BTS Manager is disconnected successfully.


Alarm 7801 MMI CONNECTED TO BASE
STATION is cancelled at the BSC.

Click on Connection -> disconnect menu item


Case Ref.

Site Type/Configuration

Operating System in PC

01

Nokia MetroSite

Windows 98

Multi TRX EDGE/GSM


02

Nokia MetroSite

Windows 2000

Multi TRX EDGE/GSM


03

Nokia MetroSite

Windows XP

Chain Configuration
04

Nokia MetroSite

Windows 2003

Multi TRX EDGE/GSM

10.2

Access Rights in Local mode

Purpose:
To check that MMI Users have Full Access to the BTS Manager Commands
irrespective of UALC feature when locally connected to BTS.
Note 50.
Under Supervision menu of BTS Manager submenus like BB2-TsX Connection, TSx
Cabling and Antenna Cabling are not applicable for MetroSite.

Nokia Siemens Networks

91 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

Launch BTS Manager application.

BTS Manager launched successfully.

Establish a local BTS connection from


BTS Manager.

Local BTS gets connected to the BTS Manager


successfully.
The BTS Manager shows COM Port connected and
Connection Speed on the status bar.
All functionality of BTS Manager is available irrespective
of User privilege.

Click on File ->Options menu item

Options dialog box opens up.


Tab for setting BTS Password is available and the
checkbox Use BTS password is enabled.

Check the commissioning menu to do the


commissioning.

The Commissioning menu is enabled.

Note: This step can also be realized by


checking the commissioning button on
the toolbar.
Click on the menu item BTS SW

BTS SW menu drop down appears.

Note: In case Metrosite BTS is connected


then Use Current SW menu Is also
available on right clicking the BCF object
on the equipment/logical view.
Disable A-bis command is given from
menu Object.

Submenus Use Current, Update, and Replace are


enabled.

The Use Current SW command is given.


The BTS SW | Versions command is
selected.

The BCF is initialised for SW loading and operational


state of BCF changes to Supervisory. There is no
change take placed in the SW files and versions shown
in the running, newest, and oldest package.

Enable A-bis command is given from


menu Object.

BCF comes to operational state.

Click on the menu Object.

Object menu drop down appears.

BCF will be reset during this operation and operational


state of BCF changes to Software Loading.

Submenus Clock Control is enabled.


.

Either Enable Abis or Disable Abis submenu is enabled


and the other one disabled depending on the actual state
of Abis.

Click on Objects ->Properties menu item

Object Properties dialog box opens up showing the


various properties of the BCF.
Reset button is enabled and objects reset is possible.
Either Block or Unblock button is enabled depending
on the state of object and objects block/unblock is
possible.

92 (152)

Nokia Siemens Networks

BTS Manager Functionality

Input

Expected Output

Right Click on the TRX object in the


equipment view.

Context menu pops up.


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

Right click on the TRX object in the


Logical view.

Context menu pops up.


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

Click on Supervision menu.

Supervision menu drops down.


All submenus i.e. External Devices, Show History
Alarms, Filter Alarms, View Site Configuration, EAC
States, BB2-TsX Connection, TSx Cabling, Antenna
Cabling, RSSI Comparison value, Site Information are
Enabled and IDD Information is disabled.

Click on Supervision-> EAC States


menu item.

EAC States dialog box opens

Click on the Outputs tab.

Outputs sheet opens showing the outputs and their


states.
The button to Set Outputs is enabled.

Click on Supervision -> IDD Information


menu item.

IDD Information dialog box opens up.

Click on menu Test

Test menu drops down.

Send IDD button is enabled.

TRX test and TRX Loop test menu items are


enabled and TRX test is possible.
TRX Traffic Trace.. menu is enabled and showing
correct information.
Click on menu Tools

All submenus are enabled.


Note: Some of the menu items such as Launch Hub
Manager, or Update Abis Allocation are enabled
depending on the actual configuration of the BTS

Case Ref.

Site Type/Configuration

1.

Nokia MetroSite
Any
Nokia MetroSite

Any 1
1

Perform the test case by connecting the BTS Manager via USB port

Nokia Siemens Networks

93 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

10.3

BTS SW Menu Commands

Purpose:
The purpose of these tests is to verify that updation of BTS SW works correctly.
Input

Expected Output

Abis is not connected. The BCF is reset.


BTS SW | Update command is selected. The
master file that is not already downloaded to the
BCF (CXM6) is selected and downloading is
started.

The SW is downloaded from the PC to the BCF.

SW versions are requested.

The SW version report shows that the


downloaded SW is in the flash memory but not as
"Running Package".

The BCF is started with the new SW.


SW versions are requested.

The SW version report shows that the


downloaded SW is in the flash memory as
currently used SW.

The SW that was locally enabled is active at the


BSC. Abis is connected and the BCF is made
operational.

The BCF starts up. No SW downloading takes


place.

From BTS Manager, the BTS SW | Update


command is selected. The master file that is
already in the BCF is selected and the loading
sequence starts.

The SW is not loaded to the BCF. The user is


informed that the SW is already in flash memory
and the SW is taken into use from the flash
memory.

From BTS Manager, the BTS SW Update


command is selected. The file, which is not a
master file, is selected.

The user is informed that the selected file is not a


master file.

From BTS Manager, the BTS SW Update


command is selected. A master file, which has
missing application files, is selected.

The user is informed that an application file for


the selected master file does not exist. The SW
download is not attempted.

Calls are made and alarms are checked.

No unexpected alarms are active. Calls are


successful.

Case Ref..

Configuration

Any

94 (152)

Nokia Siemens Networks

BTS Manager Functionality

Input

Expected Output

Abis is not connected, The BCF is reset, and the


SW is started with the BTS SW | Use Current
command.
The BTS SW Update command is selected.
The new master file, which is not already in the
BCF, is selected and loading is started.
When the SW is downloading, the BTS Manager
cable is disconnected for 1 minute and then
reconnected to the BCF.

The SW loading is interrupted when the LMP


cable is removed.

SW versions are requested.

SW version report shows that the old SW is still in


flash memory and is running the package.

From BTS Manager, the BTS SW Update


command is selected.

The SW loading is not started. The user is


informed that the file is not a MetroSite master
file.

A master file, which is for a different type of BCF,


is selected (i.e., a master-file for UltraSite BTS is
attempted to download in a MetroSite BTS).
SW versions are requested.
Case Ref.
2

The old SW is still loaded in the BCF.

SW version report shows that the old SW is still in


flash memory and is the running package.

Configuration
Any

Purpose:
The purpose of these tests is to verify that replacing the BTS SW works correctly.
Input

Expected Output

Abis is not connected. The BCF is reset from BTS


Manager.

The BCF is in the Waiting for LAPD state.

BTS 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 is


downloaded to the BCF. The BCF is initialised
with the new SW.

The SW versions are requested.

The SW version report shows that the SW


package is in flash memory as "Newest in flash"
and "Running package".

The BCF is reset from BTS Manager.

The BCF is initialised with the same SW.

Nokia Siemens Networks

95 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

The BTS SW Replace command is selected


from BTS Manager.

The connection to BTS is lost when the power


cable is disconnected. The SW downloading
stops and is not restarted.

The master file that is already downloaded to the


BCF is selected and downloading is started.
When the loading is ongoing, the power cable is
disconnected and then reconnected from the
BCF.
The SW versions are requested.

The SW version report shows that the SW


package is in flash memory as "Newest in flash"
and "Running package".

BCF is reset from the BTS Manager.

State of BCF will be Waiting for LAPD state

The BTS SW Replace command is selected.

The SW downloading is interrupted and is not


resumed when the cable is reconnected.

The master file that is already downloaded to the


BCF is selected and downloading is started.
When the downloading is ongoing, the BTS
Manager cable is disconnected. The cable is
reconnected.

Note: if the cable is disconnected for a very short


time (<< 1 second), the SW downloading may not
be interrupted.
When the downloading is interrupted, the old SW
is still loaded in the BCF.

BCF is reset from the BTS Manager.

State of BCF will remain same as Waiting for


LAPD state.

The BTS SW Replace command is selected.

The SW loading is not started.

A master file, which is for a different type of BCF,


is selected (i.e., a master-file for UltraSite BTS is
attempted to download in a MetroSite BTS).
SW versions are requested.
Case Ref.

Configuration

Any

10.4

The SW version report shows that the old SW is


still in flash memory and is the running package.

BTS Manual Commissioning

Purpose:
The purpose of these tests is to check that a BTS can be manually commissioned with
the BTS Commissioning Wizard.

96 (152)

Nokia Siemens Networks

BTS Manager Functionality

Input

Expected Output

Following steps are grouped as A


The BTS is not commissioned.
The BCF, BTS, and TRX objects are created in
the BSC. The Dchannels are unblocked by MML
commands.

The Dchannels are not in WOEX state since


the BTS is un-commissioned.

The Commissioning Wizard command is selected


from BTS Manager.

The Manual Commissioning method is selectable,


but the Undo Commissioning method cannot be
selected from the BTS Commissioning Wizard
page.

The Manual Commissioning method is selected


and the Next button is pressed.

In case of MetroSite BTS with FC type of TRE


unit: The test case is continued from part B.

The Site Name, Site ID, BCF ID and BSC ID


values are given.

The Site and BSC identification data can be


entered.

The LIF Settings command is selected and the


correct unit settings are given.

In case of E1/T1: The LIF Settings dialog is


opened and it contains page for each line
interface. The LIF settings are sent to the
transmission unit.
In case of RRI: The Settings dialog box is opened
and it contains Flexibus page for each flexibus
interface and the Platform Interface page. The
Unit settings are sent to the transmission unit.

The Synchronization command is selected and


the correct synchronization settings are given.

The synchronization settings are sent to the


transmission unit.

The Next command is selected.

In case of E1/T1: The test case is continued from


part F.
In case of RRI: The test case is continued from
part B.

Following steps are grouped as B


The Radio Link Settings page is open and the
Next button is disabled until at least radio hop is
set ready with Radio Hops command.
The Radio Hops command is selected.

Nokia Siemens Networks

The Flexibus Settings page is opened. The indoor


unit type is shown correctly (FXC RRI). Flexbus1
and Flexibus 2 unit are shown correctly.

97 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

For used flexibus or flexbuses the correct


capacity is selected and the Next command is
given.

If the Flexbus1 unit is the FlexiHopper the test


continues from sequence C. If the Flexbus1 unit
is not installed and Flexibus 2 unit is FlexiHopper
the test continues from sequence C.
If the Flexbus1 unit is the MetroHopper the test
continues from sequence D. If the Flexibus 1 unit
is not installed and the Flexibus 2 unit is
MetroHopper the test continues from sequence D.

Following steps are grouped as C


The Flexibus <n> FlexiHopper Settings page is
open.

The value of <n> in the title of the page depends


which flexibus interface is under commissioning.

The correct TX Frequency and Maximum TX and


the TX Power On are given.
The Next command is selected.

If another flexibus interface is not used, the test is


continued from sequence E.
If another flexibus interface is in use and it is
FlexiHopper, this sequence is repeated.
If another flexibus interface is in use and it is
MetroHopper, the test is continued from
sequence D.

Following steps are grouped as D


The Flexibus <n> MetroHopper General
Settings page is open.

The value of <n> in the title of the page depends


on which flexibus interface is under
commissioning.

The correct Hop Mode and Temporary Hop ID are


given. The Manual Channel Selection is selected
and the Next command is given.

The Flexibus <n> - MetroHopper Manual Channel


Selection page is opened.

The correct channel is selected and the Measure


command is selected.

The Measured values for signal strength are


updated for selected channel.

The Next command is selected.

If another flexibus interface is not used, the test is


continued from sequence E.
If another flexibus interface is in use and it is
MetroHopper, this sequence is repeated.
If another flexibus interface is in use and it is
FlexiHopper, the test is continued from sequence
C.

Following steps are grouped as E


The Monitoring Hop page is open.

The BER value and status for outdoor unit(s) are


shown correctly.

The Report command is selected.

The content of the report is correct.

98 (152)

Nokia Siemens Networks

BTS Manager Functionality

Input

Expected Output

The Next button is selected.

The test continues from sequence F.

Following steps are grouped as F


The Transmission Configuration page is open.

The Back button is enabled until the Abis TS


allocation has been given with the Traffic
Manager dialog box.

The Traffic Manager command is selected and


Abis timeslot allocation is entered.

The timeslot allocation can be made with the


Traffic Manager.

The correct Abis timeslot allocation is entered and


applied with OK.

The Traffic Manager dialog is closed. The Next


and Back buttons cannot be selected in the
Transmission Configuration page.
The BCF initialisation begins. The connection
between BTS and BSC is established, SW is
loaded from BSC if necessary and configuration
data and system information is received from
BSC.
The BTS initialisation progress can be seen from
the Transmission Configuration page. The shown
information is checked.
Finally the BCF enters to the 'Configuring' state.
The BTS Test Reporting page is automatically
opened when the commissioning tests are
started. The TRX tests and Abis loop tests are
run automatically by the BSC. The test progress
can be followed and the results can be seen in
the BTS Test Reporting page.
The BTS HW Information is requested from BTS.
The BCF enters to the 'Supervisory' state and the
BTS Manager waits for possible alarms for a
while. These events can be seen in the BTS Test
Reporting page. The Next button is disabled until
all 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'. The


state of EAC inputs are changed.

When the EAC input changes this is reflected on


EAC Input Settings page.

When the functionality of in-use EAC inputs is


verified, they are marked as 'checked'.

The EACs can be marked as 'checked' when they


are 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 state of EAC output is changed it is


reflected on EAC output.

When the functionality of all in-use EAC outputs


are verified they are marked as "checked".

Nokia Siemens Networks

The EAC output can be marked as 'checked'


when they are marked as 'in-use'.

99 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

The Next command is selected.

The BTS Commissioning Report page is opened.

The commissioning report is checked and file


name is defined.

The contents of the commissioning report are


correct.
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 time


stamps based on the PC time. BSS/NSS time is
included in the commissioning report in the
Network Time field.
The Finish command is selected.

The commissioning report is saved into the


defined location and name. The manual
commissioning procedure is finished.
The contents and format of the commissioning
report file is checked.

The Object Properties command is selected.

The TRXs are in the 'Waiting for System Info' and


locked.

The TRXs, BTS(s) and BCF are unlocked from


BSC.

The BCF becomes operational with all configured


TRXs and BTS(s).

The 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) are
in state WO in the BSC.
The Dchannels are in state WOEX in the BSC.

Case Ref.

Transmission Unit

Transmission
SW

Sequence to
be Followed

Operating
System

FC E1/T1

ITN C1.0

A, F

Windows XP

FXC E1/T1

ITN C3.0

A, F

Windows 2000

ITN C3.0

A, F

Windows 2000

100 (152)

FXC E1/T1

Nokia Siemens Networks

BTS Manager Functionality

Input

Expected Output

FXC RRI with Flexihopper XC in both


flexibus interfaces with FHXC 1.2 and
FHXC2.2 SW

ITN C3 CD1

A, B, C, E, F

Windows 2000

FXC RRI with MetroHoppers in both


flexibus interfaces

ITN C2.2

A, B, C, D, E,
F

Windows XP

FXC RRI with MetroHoppers in both


flexibus interfaces with C3.1 and C4.0
SW

ITN C3 CD1

A, B, C, D, E,
F

Windows XP

FXC RRI with FlexiHopper in flexibus


1 and MetroHopper in flexibus 2

ITN C3.0

A, B, C, D, E,
F

Windows 2000

Verify Site information and Commissioning Report contents properly.

10.5

Enabling and Disabling of Abis

Purpose:
The purpose of these tests is to verify that the enabling and disabling of Abis works
correctly.
Input

Expected Output

BTS Manager 6.0 in installed on the PC for the


first time. BTS Manager is started.

The BTS Manager is connected locally.

BCF is commissioned. Calls are set up in the


BCF.

The BCF is operational. Calls are successful.

BTS Manager is closed by selecting Exit from File


menu.

BTS Manager is closed successfully.

BTS Manager is restarted. From Menu command,


default option for attempting the connection is
observed.

It is started successfully. Connection is made to


the BTS connected locally. The default option is
to attempt local connection on start-up.

From Menu command, default option for


attempting the connection is selected so that local
connection at start-up is not allowed. BTS
Manager is closed and restarted.

BTS Manager is not connected to BTS after startup.

BTS Manager is connected locally. The Objects |


Enable Abis command is selected.

The command Enable Abis is greyed out and


cannot be selected. Only the Disable Abis is
available.

Nokia Siemens Networks

101 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

The Objects | Disable Abis command is selected.

The BCF is reset (a warning message appears


before the reset) and connection to the BSC is
lost. Calls get released.
The Status bar at the bottom of the Supervision
window 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 are


reported to be in 'Off' state.

The Objects | 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 are


reported to be in the 'On' state.

A call is set up in the BCF.

The call is successful.

From Menu command, default option for


attempting the connection is selected to allow
local connection at start-up. BTS Manager is
closed and restarted.

BTS Manager is connected to BCF after start-up.

BTS Manager is Disconnected from Menu


command. BCF is restarted from BSC.

BCF comes to WO state. BTS Manager


connection is not established.

BTS Manager is restarted. Objects | Disable Abis


command is selected.

BTS Manager is connected to BCF after start-up.


The BCF is reset (a warning message appears
before the reset) and connection to the BSC is
lost. Call gets released.
The Status bar at the bottom of the Supervision
window indicates: "O&M disabled" and "Telecom
not working".

The SW is loaded to the BCF with the BTS SW |


Replace command from the BTS Manager.

SW can be loaded to the BCF when the Abis is


disabled.
The BCF is reset when the SW has been
downloaded. Abis connection is established.
The Status bar at the bottom of the Supervision
window indicates: "O&M enabled" and "Telecom
working".

The status of the LAPD Link is requested.

The states of the OMUSIG and TRXSIG links are


reported to be in the 'On' state.

Case Ref..

Configuration

Transmission Unit

1.

Any

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

2.

Any

FXC E1 (with release ITN C3.0)

102 (152)

Nokia Siemens Networks

BTS Manager Functionality

10.6

Adjusting the DAC Word

Purpose:
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.

Input

Expected Output

The Objects | Clock Control command is


selected. The DAC word is adjusted and Set As
Current is chosen.

The change in frequency can be seen from the


frequency counter. The DAC word can be
adjusted.

Use Fine Scale is chosen. The DAC word is


adjusted and Save Current Permanently is
chosen. The window is closed and it is opened
again.

The DAC word can be adjusted and saved


correctly.

The Objects | Clock Control command is


selected. Disable BTS adjustment is selected.
The DAC word is adjusted. The new DAC value is
set as current value by choosing Set as Current.
Now Save Current Permanently is chosen.

The DAC word can be adjusted and saved


correctly.

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 BTS


will automatically adjust the frequency to
synchronise with the Abis.

Case Ref..

Configuration

Any

10.7

FC E1/T1, FXC E1 and FXC E1/T1 Transmission


Menus

Purpose:
The purpose of these tests is to ensure that the commands in the Transmission menu
work correctly when the FC E1/T1, FXC E1/T1 or FXC E1 transmission card is installed
to the BTS.
Input

Expected Output

The BCF is operational.

Nokia Siemens Networks

103 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

The LIF Settings command is selected.

The LIF Settings dialog contains one page for


each line interface.

The incoming LIF page is selected and the


interface is set to not used (used if BSC doesnt
support CRC).

Alarms 7767 BCCH MISSING, 7706 BTS O&M


LINK FAILURE, and 7704 PCM FAILURE are
activated at the BSC.

The Alarms command is selected from the


Transmission menu.

Alarms are shown in the alarm window.

The LIF Settings command is selected, and the


incoming interface is set to used.

The alarm 8081 LOSS OF FRAME ALIGNMENT


might be started and cancelled. The BCF
becomes operational. No unexpected alarms are
seen in BTS Manager or BSC.

The Abis cable is removed from the transmission


card.

The alarm 8050 or 8048 LOSS OF INCOMING


SIGNAL is started in the BTS Manager.
Alarms 7767 BCCH MISSING, 7706 BTS O&M
LINK FAILURE and 7704 PCM FAILURE are
activated at the BSC.

The Alarms command is selected from


Transmission menu.

The alarm 8050 or 8048 LOSS OF INCOMING


SIGNAL is shown in the alarm window.

The Abis cable is reconnected to the transmission


card.

The alarm 8050 or 8048 LOSS OF INCOMING


SIGNAL is cancelled. The alarm 8081 LOSS OF
FRAME ALIGNMENT might be started and
cancelled. The BCF becomes operational. No
unexpected alarms are seen in BTS Manager or
BSC.

The Alarms command is selected from


Transmission menu.

No alarm is shown in the alarm window.

Case Ref.

Configuration

Transmission Unit

Transmission SW

Any

FC E1/T1

ITN C1.0

Any

FXC E1/T1

ITN C3.0

Any

FXC E1

ITN C2.1-2

Input

Expected Output

The BTS is in un-commissioned state.


The correct LIF Settings and Synchronisation
values are given.
The Traffic Manager command is selected.

The Traffic Manager dialog box is opened.

Different branching tables are generated and


taken into use. Abis TS allocation is entered and
taken into use.

The BTS is initialised correctly. The BCF is


operational.

104 (152)

Nokia Siemens Networks

BTS Manager Functionality

Input

Expected Output

The LIF Settings command is selected.

The LIF Settings dialog contains one page for


each line interface.

The incoming LIF page is selected and CRC is


not set to be used.

The 8179 FAR-END alarm is started.

The Alarms command is selected from


Transmission menu.

The alarm 8179 is shown for correct location.

The LIF Settings command is selected and CRC


set to be in use.

The alarm 8179 is cancelled.

The Alarms command is selected from


Transmission menu.

The alarm 8179 s not shown.

Some test calls are made.

Calls are successful.

The Synchronisation command is selected from


the Transmission menu. An interface, which is not
used, is selected to be the interface for
synchronisation. (For the FXC tests, the second
priority 2 options for synchronisation must be set
to Internal Timing). The Alarms command is
selected from the Transmission menu.

The alarm 8112 is started after some time.

The Synchronisation command is selected and


the used interface is selected to be the interface
for synchronisation.

The 8112 alarm is no longer shown.

The test is repeated for all interfaces. This


requires the Synchronisation, LIF, and Traffic
Manager settings are be redefined and the BCF is
to be reset.
Case Ref..

Configuration

Transmission Card

Transmission SW

Any

FXC E1/T1

ITN C3.0

10.8

FXC RRI Transmission Menus

Purpose:
The purpose of these tests is to ensure that the commands in the Transmission menu
work correctly when the FXC RRI transmission card is installed to the BTS.
Input

Expected Output

The BCF is operational.


The Unit Settings command is selected.

Nokia Siemens Networks

The Unit Settings dialog contains pages for


Flexibus interface(s) and Platform Interface.

105 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

The incoming Flexibus page is selected, and the


interface is set to be not used.

The alarm 8125 loss of synchronisation signal


started.

The Alarms command is selected from the


Transmission menu.

The 8125 alarm is shown for correct location.

The Unit Settings command is selected, and the


incoming interface is set to be used.

The alarm 8125 is cancelled. The alarm 8081


LOSS OF FRAME ALIGNMENT might be started
and cancelled.

The Alarms command is selected from the


Transmission menu.

The 8125 alarm is not shown.

Case Ref.

Configuration

Transmission Unit

Transmission SW

Any

FXC RRI

ITN C3.0

Input

Expected Output

The BCF is operational.


The Unit Settings command is selected.

The Unit Settings dialog contains pages for


Flexibus interface(s) and Platform Interface.

The Platform Interface page is selected and, for


the incoming Platform Interface, the CRC is set to
be not used (from the CRC in USE column with
the right mouse button).

The alarm 8179 FAR-END ALARM is started.

The Alarms command is selected from the


Transmission menu.

The alarm 8179 is shown for correct location.

The Unit Settings command is selected and CRC


is set to be in use again.

The alarm 8179 is cancelled.

The Alarms command is selected from the


Transmission menu.

The 8179 alarm is not shown.

The Synchronisation command is selected from


the Transmission menu.
An interface, which is not used, is selected to be
the interface for synchronisation (for the FXC
tests, the second priority 2 option for
synchronisation must be set to Internal Timing).

The alarm 7601 BCF OPERATION DEGRADED


is started after some time.

The Alarms command is selected from


Transmission menu.

The 8112 FREQUENCY ERROR alarm is shown.

The Synchronisation command is selected and


the used interface is selected to be the interface
for synchronisation.
The Alarms command is selected from
Transmission menu.

The alarm 7601 is cancelled after some time.

106 (152)

Nokia Siemens Networks

The alarm 8112 is not shown.

BTS Manager Functionality

The test is repeated for different interfaces. This


requires the Synchronisation, LIF and Traffic
Manager settings to be redefined and the BCF to
be reset.
Case Ref.

Configuration

Transmission Unit

Transmission SW

Any

FXC RRI

ITN C3.0

10.9

Window Menu Commands

Purpose:
The purpose of this test is to ensure that the commands in the Window menu work
correctly. Window menu commands pertain to the administration of the various
windows in the PC application, and to the functionality of the BCF.
Input

Expected Output

The BCF is operational.

The administration of the different windows works


correctly.

The main application window, BTS Events,


Alarms, and Supervision windows are
manipulated in different ways. The windows are
moved, resized, minimised or maximised
differently.
The BTS Manager is closed and then restarted.

All windows are located as they were when BTS


Manager was closed.

Each type of window is activated one- by- one


from Window menu.

The selected window is activated.

The Arrange command is selected from Window


menu.

The windows are arranged inside the main


application window at the default positions.

The BTS Manager is closed and then restarted.

All windows are located as they were when BTS


Manager was closed.

Case Ref.

Configuration

Any

4+4+4 chained configuration

Nokia Siemens Networks

107 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

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
Input

Expected Output

The BTS is not commissioned.


The BCF, BTS, and TRX objects are created in
the BSC. The Dchannels are unblocked by MML
commands.

The Dchannels are not in WOEX state since


the BTS is un-commissioned.

The Commissioning Wizard command is selected


from BTS Manager.

The Manual Commissioning method is selectable,


but the Undo Commissioning method cannot be
selected from the BTS Commissioning Wizard
page.

The Manual Commissioning method is selected


and the Next button is pressed.
The Site Name, Site ID, BCF ID and BSC ID
values are given.

The Site and BSC identification data can be


entered.

The LIF Settings command is selected and the


correct unit settings are given.

The Settings dialog box is opened and it contains


Flexbus page for each flexbus interface and the
Platform Interface page. The Unit settings are
sent to the transmission unit.

The Synchronization command is selected and


the correct synchronization settings are given.

The synchronization settings are sent to the


transmission unit.

The Next command is selected.


The Radio Link Settings page is open and the
Next button is disabled until at least radio hop is
set ready with Radio Hops command.
The Radio Hops command is selected.

The Flexbus Settings page is opened. The indoor


unit type is shown correctly (FXC RRI). Flexbus1
and Flexbus 2 unit are shown correctly in case of.

For used flexbus or flexibuses the correct


capacity is selected and the Next command is
given.
The Flexbus <n> FlexiHopper Settings page is
open.
The correct TX Frequency and Maximum TX and
the TX Power On are given.

108 (152)

Nokia Siemens Networks

The value of <n> in the title of the page depends


which flexbus interface is under commissioning.

BTS Manager Functionality

Input

Expected Output

The Next command is selected. The Monitoring


Hop page is open.

The BER value and status for outdoor unit(s) are


shown 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 TS


allocation has been given with the Traffic
Manager dialog box.

The Traffic Manager command is selected and


Abis timeslot allocation is entered.

The timeslot allocation can be made with the


Traffic Manager.

The correct Abis timeslot allocation is entered and


applied with OK.

The Traffic Manager dialog is closed. The Next


and Back buttons cannot be selected in the
Transmission Configuration page.
The BCF initialisation begins. The connection
between BTS and BSC is established, SW is
loaded from BSC if necessary and configuration
data and system information is received from
BSC.
The BTS initialisation progress can be seen from
the Transmission Configuration page. The shown
information is checked.
Finally the BCF enters to the 'Configuring' state.
The BTS Test Reporting page is automatically
opened when the commissioning tests are
started. The TRX tests and Abis loop tests are
run automatically by the BSC. The test progress
can be followed and the results can be seen in
the BTS Test Reporting page.
The BTS HW Information is requested from BTS.
The BCF enters to the 'Supervisory' state and the
BTS Manager waits for possible alarms for a
while. These events can be seen in the BTS Test
Reporting page. The Next button is disabled until
all 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'. The


state of EAC inputs are changed.

When the EAC input changes this is reflected on


EAC Input Settings page.

When the functionality of in-use EAC inputs is


verified, they are marked as 'checked'.

The EACs can be marked as 'checked' when they


are marked as 'in-use'.

The Next command is selected.

The EAC Output Settings page is opened.

Nokia Siemens Networks

109 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

The used EAC outputs are marked as "in use".


The EAC output states are changed using the Set
Outputs button.

When the state of EAC output is changed it is


reflected on EAC output.

When the functionality of all in-use EAC outputs


are verified they are marked as "checked".

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 file


name is defined.

The contents of the commissioning report are


correct.
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 time


stamps based on the PC time. BSS/NSS time is
included in the commissioning report in the
Network Time field.
The Finish command is selected.

The commissioning report is saved into the


defined location and name. The manual
commissioning procedure is finished.
The contents and format of the commissioning
report file is checked.

The Object /Properties command is selected.

The TRXs are in the 'Waiting for System Info' and


locked.

The TRXs, BTS(s) and BCF are unlocked from


BSC.

The BCF becomes operational with all configured


TRXs and BTS(s).

The 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) are
in state WO in the BSC.
The Dchannels are in state WOEX in the BSC.

Case Ref.

110 (152)

Transmission Configuration

Nokia Siemens Networks

BTS Manager Functionality

Input

Expected Output

FXC RRI with FlexiHoppers FH3.3.4 in both flexbus interfaces, FXC RRI SW ITN C2.1,
MetroHub SW C2.1

FXC RRI with FlexiHoppers FH5.2.4 in both flexbus interfaces, FXC RRI SW ITN C2.2,
MetroHub SW C2.2

FXC RRI with Flexihopper Plus FHP2.7 in both flexbus interfaces, FXC RRI SW ITN C3
CD1, MetroHub SW C3 CD1

Nokia Siemens Networks

111 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

11

Remote BTS Manager

11.1

Remote BTS Manager Start-Up

Purpose:
The purpose of these test cases is to verify that the Remote BTS Manager can
successfully be started when using various different configurations. It is accessible if
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 local connection
has higher priority over remote connection.
Input

Expected Output

Automatic connection option is disabled. Remote


BTS Manager connection is made from a PC via
NetAct and BSC using the Nokia GCS connection
tool.

The Remote BTS Manager starts successfully.

Remote BTS manager is disconnected.

Remote connection to BTS Manager of the


requested BCF is disconnected. Alarm 7801
REMOTE MMI CONNECTED TO BASE
STATION is cancelled at the BSC.

Click on Connection -> disconnect menu item.

When the connection dialog window appears,


incorrect password for the NMS is given. All
remaining data in the connection and node
windows is correct.

The Remote BTS Manager is not started, as the


password for the NMS must be given correctly to
start the BTS Manager remotely.

Remote BTS Manager connection is reinitiated


with incorrect Q1 address with the remaining
correct data.

The Remote BTS Manager is not started, as the


Q1 address must be given correctly to start the
BTS Manager remotely.

Now Connection is initiated with the correct


password and with the correct Q1 address. Q1
address value can be observed with ZQWL
command at BSC (default is 4001).

Remote connection to BTS Manager of the


requested BCF is established. Alarm 7801
REMOTE MMI CONNECTED TO BASE
STATION is raised at both the BSC and the
Remote BTS Manager.

112 (152)

Nokia Siemens Networks

Remote BTS Manager

Input

Expected Output

Remote BTS manager is disconnected.

Remote connection to BTS Manager of the


requested BCF is disconnected. Alarm 7801
REMOTE MMI CONNECTED TO BASE
STATION is cancelled at the BSC.

Click on Connection -> disconnect menu item.

The BTS Manager is started from a remote PC


via NetAct and BSC. The correct data is given in
the connection window and the node window.

Remote connection to BTS Manager of requested


BCF is established.

A second remote connection to BTS Manager of


the same BCF is started.

The second remote connection to BTS Manager


is unsuccessful.

The BTS Manager of the same BCF is started


locally.

The local BTS Manager is started and the current


remote BTS Manager is cancelled.

Another remote connection to BTS Manager of


the same BCF is started.

The remote BTS Manager is unsuccessful and


the local BTS Manager stays connected.

Case Ref.

Configuration

Operating System in PC

Multi TRX EDGE/GSM

Windows 2000

3 Cabinets in chain

Windows 2000

Multi TRX EDGE/GSM

Windows XP

Input

Expected Output

Automatic connection option is disabled. Remote


BTS Manager connection is made from a PC via
NetAct and BSC.

The Remote BTS Manager starts successfully.

Remote BTS Manager application is closed from


File|Exit. Remote BTS Manager application is
started again.

The Remote BTS Manager starts successfully.


Connection to BCF is made successfully.

Reset the BCF.

During the reset, the BCF connection is lost and


is regained when the BCF comes into working
state.

Manually disconnect the BCF connection from


BTS Manager application.

The Remote BTS Manager connection to the BCF


is not established even after the BCF comes into
the working state.

Reset the BCF.


Close the Remote BTS Manager application and
reopen it. Now enable the automatic local
connection feature on the Remote BTS Manager
and terminate the application. Restart the Remote
BTS Manager application.

As there is no connection at local port, No


Connection to the BCF is displayed.

Connect the application as remote connection, to


the BCF.

The Remote BTS Manager starts successfully.

Case Ref.

Configuration

Transmission Unit

Transmission SW

Any

FXC E1/T1

ITN C3.0

Nokia Siemens Networks

113 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

11.2

Remote BTS Manager

11.2.1

Remote BTS Manager Start-Up using NetAct TLUI with


configuration in GCS Database

Purpose:
The purpose of this test case is to verify that the Remote BTS Manager can successfully be
started from NetAct TLUI using connection data from GCS database.

Note 52.
In case of Remote BTS Manager Start-Up using NetAct TLUI, GCS of Node Manager
Server is used.

Input

Expected Output

The BTS Manager is started from a NetAct TLUI.


Directly launch the BTS Manager application by
right clicking on the TRE object with which remote
connection is to be established. Connection data
is fetched from local GCS database.

The Remote BTS Manager starts successfully.


Alarm 7801 MMI CONNECTED TO BASE
STATION is raised at both the BSC and the
Remote BTS Manager.

Remote BTS manager is disconnected using


Disconnect option in Connection menu item.

Remote connection to BTS Manager of the


requested BCF is disconnected. Alarm 7801 MMI
CONNECTED TO BASE STATION is cancelled
at the BSC.

The Remote BTS Manager is again started.

Remote connection to BTS Manager of requested


BCF is established. Alarm 7801 MMI
CONNECTED TO BASE STATION is raised at
both the BSC and the Remote BTS Manager

A second remote connection to BTS Manager of


the same BCF is started.

The second remote connection to BTS Manager


is unsuccessful giving error message Cannot
connect to the Remote BTS because another
remote connection to the same BTS exists.

Case Ref.

Configuration

13-368141.2

Any Multi TRX Metro Site Configuration

11.2.2

BTS Manager command line connection to remote BTS using


Sobriquet String

Purpose:

114 (152)

Nokia Siemens Networks

Remote BTS Manager

To check that the Remote Connection to a BTS on BTS Manager command line start up using
sobriquet string.

Input

Expected Output

Create a Connection Node using Nokia


Connection tool parameters.

A new Connection node is created with a


sobriquet string remBTS (Display name for
Network element) and stored in the GCS
Database.

Go to the command Prompt and change the


directory to the installation path of BTS Manager.

Nokia BTS Manager starts with connection to


Remote BTS. BTS Event window shows the
message BTS Manager Started followed by
message Remote BTS Connected.

Execute BTS Manager with following command at


the command prompt.

BTSManager.exe sobriquet remBts.

Status bar of main window shows Remote BTS


Connected, LAN Connection and Access
Rights (Full Access Rights if User has full
access or Read Only Access Rights- if User has
Read Only Access). Title bar of main window
shows Remote BTS Manager BSC ID = x, BCF
ID = y BTS Events. Where x and y are
corresponding BSC and BCF IDs.
The Disconnect and Connect Locally submenu item of Connection menu should be
enabled now; Connect menu item should be
disabled (greyed).

Case Ref.

Site

Configuration

13-368271.2

Metro site

Any Multi TRX configuration

11.2.3

BTS Manager command line connection to remote BTS using


Target String

Purpose:
To check that the Remote Connection to a BTS on BTS Manager command line start
up using target string.is successful.

Input

Expected Output

Nokia Siemens Networks

115 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

Go to the command Prompt and change the


directory to the installation path of BTS Manager.

Nokia BTS Manager starts with connection to


Remote BTS. BTS Event window shows the
message BTS Manager Started followed by
message Remote BTS Connected.

Execute BTS Manager with following command at


the command prompt.
BTSManager.exe target
WP=SOCKET, HOST= < ip_address_of_oss
server>, PORT=7878, WP=BSC,
USER=<username for OSS server>,
PSW=<Password for Oss server>,
BSCID=<c_number_of_BSC>,
BUSID=0,TIME=10000,WP=BTS,
BCFID=<bcf_id>,
TRXID=0,TIME=100000,WP=NEQ1,
ADDR=4001

Status bar of main window shows Remote BTS


Connected, LAN Connection and Access
Rights (Full Access Rights if User has full
access or Read Only Access Rights- if User has
Read Only Access). Title bar of main window
shows Remote BTS Manager BSC ID = x, BCF
ID = y BTS Events. Where x and y are
corresponding BSC and BCF IDs.
The Disconnect and Connect Locally submenu item of Connection menu should be
enabled now; Connect menu item should be
disabled (greyed).

Case Ref.

Configuration

13-368169.2

Any Multi TRX MetroSite configuration

11.2.4

Remote BTS Manager Start-Up for BCF id > 255

Purpose:
To check that the Remote BTS Manager can successfully be started for BCF ID greater than
255.

Input

Expected Output

Site is created with BCF id > 255.

Site is up & running

The BTS Manager is started from a remote PC


via NetAct and BSC using the Nokia GCS
connection tool.

The Remote BTS Manager starts successfully.


Alarm 7801 MMI CONNECTED TO BASE
STATION is raised at the BSC & BTS Manager.

Remote BTS manager is disconnected, using the


disconnect option in Connection menu.

Remote connection to BTS Manager of the


requested BCF is disconnected. Alarm 7801 MMI
CONNECTED TO BASE STATION is cancelled
at the BSC.

The BTS Manager is started from a remote PC


via NetAct and BSC..

Remote connection to BTS Manager of requested


BCF is established. Alarm 7801 MMI
CONNECTED TO BASE STATION is raised at
the BSC & BTS Manager

116 (152)

Nokia Siemens Networks

Remote BTS Manager

Input

Expected Output

A second remote connection to BTS Manager of


the same BCF is started.

The second remote connection to BTS Manager


is unsuccessful giving error message Cannot
connect to the Remote BTS because another
remote connection to the same BTS exists.

The BTS Manager of the same BCF is started


locally.

The local BTS Manager is started and the current


remote BTS Manager is cancelled giving
message Remote session has been terminated
by the BTS because an MMI application has
connected locally

Another remote connection to BTS Manager of


the same BCF is started.

The remote BTS Manager connection is


unsuccessful giving error message Cannot
connect to the Remote BTS because of an
existing local MMI connection. The local BTS
Manager stays connected.

Case Ref.

Configuration

13-368347.2

Any Multi TRX Metro Site Configuration

Nokia Siemens Networks

117 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

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 Test report, commissioning
report, BTS events window and On line help menu is changed to Main Rx Results &
Diversity Rx Result respectively.

12.1

Improved TRX Test Presentation in the TRX Test


Report

12.1.1

Improved TRX Test Presentation in the TRX Test Report while TRX
Test executed from BTS Manager

Purpose:
To check that TRX Test dialog box, BTS events window and TRX Test report showing
the changed TRX Test presentation and TRX test is successful while TRX test is
executed from BTS Manager.

Input

Expected Output

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.

BTS Manager application is launched

BTS Manager application is launched


successfully.

Clicks on the File->Options menu.

BTS Manager Application displays Options dialog


box.

Select the File Handling tab and check the Use


Test Log check box.

BTS Manager Application displays select Log File


name dialog box.

118 (152)

Nokia Siemens Networks

Improved TRX Test Presentation

Input

Expected Output

Creates the log file at a particular path & click on


the save button.

BTS Manager Application closes select Log File


name dialog box.

Clicks on the OK button of the Options dialog box.

BTS Manager Application closes options dialog


box.

Selects the 'TRX Test' menu item from the 'Tests'


pull down menu on the main menu bar.

BTS Manager Application displays the TRX Test


dialog box.
Main RX Results & Diversity RX Results can be
seen in place of Main RX Sensitivity & Diversity
RX Sensitivity respectively in the TRX test dialog
box.

Checks the Display Also in BTS Events window


check box and Now 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.

BTS Manager Application runs the TRX Test,


TRX Test is successful and results are shown
correctly. Displays the correct string information
(i.e. Main Rx Result & Diversity Rx Result) in the
BTS Events window.

Open the Test Log file.

Test Log File opens displaying the correct string


Main Rx Result & Diversity Rx Result in place
of Main Sensitivity & Diversity Sensitivity
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


Case
Ref.

BTS Type/Configuration

Nokia MetroSite
Multi TRX

12.1.2

Improved TRX Test Presentation in the TRX Test Report while Test
executed from Remote BTS Manager

Purpose:
To check that TRX Test dialog box, BTS events window and TRX Test report showing
the changed TRX Test presentation and TRX test is successful while TRX Test is
executed from Remote BTS Manager.
Note 54.
Either UALC should be disabled or User should have Full Access rights

Nokia Siemens Networks

119 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

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.

Remote BTS Manager application is launched

Remote BTS Manager application is launched


successfully.

Clicks on the File->Options menu.

BTS Manager Application displays Options dialog


box.

Select the File Handling tab and check the Use


Test Log check box.

BTS Manager Application displays select Log File


name dialog box.

Creates the log file at a particular path & click on


the save button.

BTS Manager Application closes select Log File


name dialog box.

Clicks on the OK button of the Options dialog box.

BTS Manager Application closes options dialog


box.

Selects the 'TRX Test' menu item from the


'Tests' pull down menu on the main menu bar.

BTS Manager Application displays the TRX Test


dialog box.
Main RX Results & Diversity RX Results can be
seen in place of Main RX Sensitivity & Diversity
RX Sensitivity respectively in the TRX test dialog
box.

Checks the Display Also in BTS Events window


check box and Now 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.

BTS Manager Application runs the TRX Test,


TRX Test is successful and results are shown
correctly. Displays the correct string information
(i.e. Main Rx Result & Diversity Rx Result) in the
BTS Events window.

Open the Test Log file.

Test Log File opens displaying the correct string


Main Rx Result & Diversity Rx Result in place
of Main Sensitivity & Diversity Sensitivity
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 each TRX


Case
Ref.

BTS Type/Configuration

Nokia MetroSite
Multi TRX

120 (152)

Nokia Siemens Networks

User Access Level Control

13

User Access Level Control

13.1

Remote Connection to BTS Manager with Read


Only Access

Purpose:
To check that the BTS Manager grants Read Only Access to the MMI user in case
Remote connection is established with the BTS.
Note 55.
User should have Read Only access.
Note 56.
For MetroSite Site Specific Notepad command is not available.

Input

Expected Output

Launch BTS Manager application and establish


remote connection to the BTS.

BTS Manager launched successfully.


Remote BTS gets connected and BTS Manager
shows the Equipment view, alarms view and
Events Window.
The status bar of the BTS Manager shows
Read Only.

Click on File ->Options menu item

Options dialog box opens up.


Tab for setting BTS Password is available and
the checkbox Use BTS password is disabled.

Check the commissioning menu to do the


commissioning.

Nokia Siemens Networks

The Commissioning menu is disabled.

121 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

Click on the menu item BTS SW

BTS SW menu drop down appears.


Submenus Use Current, Update, and
Replace are disabled.

Click on the menu Object.

Object menu drop down appears.


Submenus RTC Configure and

(Submenu RTC Configure is not applicable for


MetroSite)
Click on Objects ->Properties menu item

Clock Control are disabled.


Enable Abis Disable Abis menu are disabled.
Object Properties dialog box opens up showing
the various properties of the BCF.

Reset button is disabled.

Block or Unblock button are disabled.


Right Click on the TRX object in the equipment
view.

Context menu pops up.


Object Reset menu item is disabled.

Object block and Object Unblock menu items


are disabled.
Right click on the TRX object in the Logical view.

Context menu pops up.


Object Reset menu item is disabled.

Object block and Object Unblock menu items


are disabled.
Click on Supervision menu.

Supervision menu drops down.

( Submenus BB2-TsX Connection, TSx Cabling,


Antenna Cabling, does not available for
MetroSite )

All submenus i.e. External Devices, Show


History Alarms, Filter Alarms, View Site
Configuration, EAC States, IDD Information,
BB2-TsX Connection, TSx Cabling, Antenna
Cabling, RSSI Comparison value, Site
Information are Enabled.

Click on Supervision-> EAC States menu


item.

EAC States dialog box opens

Click on the Outputs tab.

Outputs sheet opens showing the outputs and


their states.

The button to Set Outputs is disabled.

122 (152)

Nokia Siemens Networks

User Access Level Control

Input

Expected Output

Change the state of any one of the Output


buttons of the Output sheet and then switch to the
input tab and then again come back to the Output
sheet. (Applicable only for Ultra site)

The state of the output button does not changed


to the state which was set before switching to the
input tab.

Click on Supervision -> IDD Information menu


item.

IDD Information dialog box opens up.

IDD info is available in BTS Manager from


ver5(Build 5.0.5).

Send IDD and Set/Reset 4UD buttons are


disabled.

(Set/Reset 4UD is not applicable for Metrosite.)


Click on menu Tests

Tests menu drops down.

TRX test and TRX Loop test menu items


are disabled.
TRX Traffic Trace menu is enabled.
Click on menu Tools

Tools menu drops down.


Update Abis Allocations submenu is disabled.

Click on Tools->Site Specific Notepad.

Site Specific Notepad dialog box opens up.


The Send button is disabled

Write something in the Notepad area.

Send button remains disabled.

Click on the cancel button of the site-specific


notepad.

The message box with the message Information


has been changed. Do you want to save changes
to the File? appears.

Case Ref.

Site Type/Configuration

13-366702.01

Nokia MetroSite
Any

13.2

Changes in Registry Key/User Priveledges for


BTS Manager in Remote mode.

13.2.1

Changes in Registry Key when application is running in remote


scenario.

Nokia Siemens Networks

123 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Purpose:
The purpose of this test case is to verify that behaviour of the application should be
proper when the registry key is modified at run time.
Note 57.
To disable UALC feature set the value of Registry Key Access Levels under
HKEY_LOCAL_MACHINE/Software/Nokia/2G_Managers is to Off.

Input

Expected Output

Connect the BTS Manager application remotely


with the BTS in Read only mode.

Remote BTS gets connected to the BTS


successfully with the Access permission Read
Only in the Status Bar.

Disable the UALC feature by changing the value


of Registry Key Access Levels under
HKEY_LOCAL_MACHINE/Software/Nokia/2G_M
anagers to Off.

BTS Manager remains connected with the Same


Access permission as Read Only in the status
bar. There is no impact on the access permission
of the already running application.

Close the BTS Manager application by clicking on


the File/Exit menu item.

BTS manager closed successfully.

Launch BTS Manger and establish Remote BTS


connection.
Case Ref.

Site Type/Configuration

13-355917.01

Nokia MetroSite

Remote BTS gets connected to the BTS


successfully with the Access permission Full
Control in the Status Bar.

Any

13.2.2

Changes in User Privileges when application is running in remote


scenario.

Purpose:
The purpose of this test case is to verify that behaviour of the application is proper
when the User Privilege is modified at run time.

Input

Expected Output

Connect the BTS Manager application remotely


with the BTS in Read only mode.

Remote BTS gets connected to the BTS


successfully with the Access permission Read
Only in the Status Bar.

124 (152)

Nokia Siemens Networks

User Access Level Control

Input

Expected Output

Make the user a member of the


NokiaBTS_Admins group.

BTS Manager remains connected with the Same


Access permission as Read Only in the status
bar. There is no impact on the access permission
of the already running application.

Close the BTS Manager application by clicking on


the File/Exit menu item.

BTS manager closed successfully.

Launch BTS Manger and establish Remote BTS


connection.
Case Ref.

Site Type/Configuration

13-355972.01

Nokia MetroSite

Remote BTS gets connected to the BTS


successfully with the Access permission Full
Control in the Status Bar.

Any

13.3

User Authentication

Purpose:
To check that when a user access is changed from Full Access to Read Only the
user is properly authenticated and also that the user is barred from using certain
commands.
Note 58.
User should have Full Control Access rights.

Input

Expected Output

Launch BTS Manager application.

BTS Manager start running successfully.

Establish a Remote BTS connection from BTS


Manager.

Remote BTS gets connected to the BTS Manager


successfully.
The BTS Manager shows Full Control on the
status bar.

Select Tests-> TRX Test.. , And run TRX Test for


any TRX.

TRX test
displayed.

Select File-> Exit from Menu Command.

BTS Manager is closed successfully.

Move Currently Logged user from


NokiaBTS_Admins Group to MMI User Group.

user is successfully moved to MMI User Group.

Nokia Siemens Networks

run

successful

and

results

are

125 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

Launch BTS Manager application.

BTS Manager start running successfully.

Establish a Remote BTS connection from BTS


Manager.

Remote BTS gets connected to the BTS Manager


successfully.
The BTS Manager shows
status bar.

Read Only on the

Select Tests-> Attempt TRX Test.

TRX test is not available in Read Only mode.

Case Ref.

Site Type/Configuration

13-366659.01

MetroSite
Any

13.4

Enabling/Disabling UALC DURING Installation of


Site Wizard

13.4.1

UALC Enabled During SiteWizard Installation

Purpose:
To check that during installation of the SiteWizard5.0, User Access Level Control
feature can be enabled successfully.
Note 59.
To install SiteWizard5.0 on a PC/Laptop User must have Windows Administrative
rights.
Note 60.
SiteWizard5.0 Setup files must be stored at Local PC/Laptop or LAN (Local Area
Network).
Input

Expected Output

Select Start->Settings->Control Panel

Control Panel Application running successfully.

Select Add or Remove Programs in Control


Panel

Add or Remove Programs application running


successfully.

126 (152)

Nokia Siemens Networks

User Access Level Control

Input

Expected Output

Select Add New Programs

Windows will ask from where you want to add new


programs
-Add a program from CD-ROM or floppy disk
-Add a program from Microsoft
-Add a program from your network

Press CD-ROM or Floppy Button

A Pop-up message to insert program CD appears.

Press Next Button

Pop-up message, asking for setup file will appears.

Enter/Browse SiteWizards5.0 Setup file and


Press Finish.

SiteWizard5.0 installation wizard will starts.

Follow the instructions during installation wizard


and enter/provide required information.

Installation wizard progress.

During Installation wizard progress select UALC


as Enabled in UALC Enable/Disable window.

SiteWizard5.0 installation completes successfully.

Restart the PC/Laptop having SiteWizard5.0


installed on it.

PC/Laptop boots/starts successfully.

Log on to PC as Windows Administrator.

Log on Prompts for User ID and Password.

Windows Authenticate user successfully and user


get Log on to PC/Laptop successfully.

Add a user to NokiaBTS_Admins Group.

User is added
successfully.

to

NokiaBTS_Admins

Log off as current user

Logged off successfully.

Log on using User ID and Password belonging


to NokiaBTS_Admins Group

Authenticated & logged on successfully.

Launch BTS Manager application.

BTS Manager start running successfully.

Establish a Remote BTS connection from BTS


Manager.

Remote BTS gets connected to the BTS Manager


successfully.
The BTS Manager shows
status bar.

Group

Full Control on the

Select Tests-> TRX Test.. , And run TRX Test


for any TRX.

TRX test run successful and results are displayed.

Select File-> Exit from Menu Command.

BTS Manager is closed successfully.

Log off as current user

Logged of successfully.

Log on using User ID and Password (User-ID


belonging to MMI User Group)

Authenticated & logged on successfully.

Launch BTS Manager application.

BTS Manager start running successfully.

Nokia Siemens Networks

127 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

Establish a Remote BTS connection from BTS


Manager.

Remote BTS gets connected to the BTS Manager


successfully.
The BTS Manager shows
status bar.

Read Only on the

Select Tests-> TRX Test.. , And run TRX Test


for any TRX.

TRX test is not available in Read Only mode.

Select File-> Exit from Menu Command.

BTS Manager is closed successfully.

Case Ref.

Site Type/ Configuration

13-366671.01

MetroSite
Any

13.4.2

UALC Disabled During SiteWizard Installation

Purpose:
To check that during installation of the SiteWizard5.0, User Access Level Control
Feature can be disabled successfully.
Note 61.
To install SiteWizard5.0 on a PC/Laptop User must have Windows Administrative
rights.
Note 62.
SiteWizard5.0 Setup files must be stored at Local PC/Laptop or LAN (Local Area
Network).

Input

Expected Output

Select Start->Settings->Control Panel

Control Panel Application running successfully.

Select Add or Remove Programs in Control


Panel

Add or Remove Programs application running


successfully.

128 (152)

Nokia Siemens Networks

User Access Level Control

Input

Expected Output

Select Add New Programs

Windows will ask from where you want to add new


programs
1. Add a program from CD-ROM or floppy
disk
2. Add a program from Microsoft
3. Add a program from your network

Press CD or Floppy Button

A Pop-up message to insert program CD appears.

Press Next Button

Pop-up message, asking for setup file will appears.

Enter/Browse SiteWizards5.0 Setup file and


Press Finish.

SiteWizard5.0 installation wizard will starts.

Follow the instructions during installation wizard


and enter/provide required information.

Installation wizard progress.

During Installation wizard progress select UALC


as disable in UALC feature Enable/Disable
window.

SiteWizard5.0 installation completes successfully.

Restart the PC/Laptop having SiteWizard5.0


installed on it.

PC/Laptop boots/starts successfully.

Enter User ID and Password for Log on. (UserID and Password belonging to MMI User Group)

Log on Prompts for User ID and Password.

Windows Authenticate user successfully and user


get Log on to PC/Laptop successfully.

Launch BTS Manager application.

BTS Manager start running successfully.

Establish a Remote BTS connection from BTS


Manager.

Remote BTS gets connected to the BTS Manager


successfully.
The BTS Manager shows
status bar.

Full Control on the

Select Tests-> TRX Test.. , And run TRX Test


for any TRX.

TRX test run successful and results are displayed.

Select File-> Exit from Menu Command.

BTS Manager is closed successfully.

Case Ref.

Site Type/ Configuration

13-366667.01

MetroSite, Any

Nokia Siemens Networks

129 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

14

ST-IRC

14.1

Enable/Disable ST-IRC from BSC

Purpose:
To confirm that ST-IRC can be enabled/disabled successfully.
Note 63.
All test cases shall be performed using BSC SW S12 unless otherwise stated.
Note 64.
For Metrosite, use EDGE TRXs unless otherwise stated.
Equipment and BTS Set-Up
Site - as per configuration defined in test case.

14.1.1

Any EDGE configuration, RDIV=N, RF-Hopping

Input

Expected Output

Enable ST-IRC in the sector by MML command


ZEQM: BTS=<BTS ID>: STIRC=Y;
A-bis interface is monitored.

ST-IRC is enabled successfully.

Trace master is used to monitor the UC-DSP


traces.
Make call as defined in the table.
In case of GPRS call transfer a file of 200 kb in
UL and DL direction.

130 (152)

Nokia Siemens Networks

BTS_CONF_DATA is sent to BTS by BSC


containing ST-IRC mode as enabled.
The BTS sends ACK, on BTS_BSC_ACK to the
BSC.
STIRC information is sent to the EQDSP in the
INI message for both the sectors.
Call is successful.
In case of GPRS, file transfer is successful.

ST-IRC

Input

Expected Output

Disable ST-IRC in the sector by MML command


ZEQM: BTS=<BTS ID>: STIRC=N;
A-bis interface is monitored.

ST-IRC is disabled successfully.

Trace master is used to monitor the UC-DSP


traces.
Make calls as defined in the table on all the
TRXs.
In case of GPRS call, transfer a file of 200 kb.

BTS_CONF_DATA is sent to BTS by BSC


containing ST-IRC mode as disabled.
The BTS sends ACK, on BTS_BSC_ACK to the
BSC.
STIRC information is sent to the EQDSP in the
INI message for both the sectors.
Calls are successful.
In case of GPRS, file transfer is successful.

Case Ref.

Type of Call

Configuration

13-355736.05

FR

Any, RDIV=N, RF-Hopping (Metro)

13-355736.06

HR

2+2 (Metro)

13-355736.07

GPRS

4 omni (Metro)

13-355736.08

FR

4+4+4 Chaining configuration (Metro)

14.1.2

2+2 EDGE configuration

Input

Expected Output

Enable ST-IRC in the sector by MML command


ZEQM: BTS=<BTS ID>: STIRC=Y;
A-bis interface is monitored.

ST-IRC is enabled successfully.

Trace master is used to monitor the UC-DSP


traces.
Make call as defined in the table.
In case of GPRS call transfer a file of 200 kb in
UL and DL direction.
Disable ST-IRC in the sector by MML command
ZEQM: BTS=<BTS ID>: STIRC=N;
A-bis interface is monitored.

Trace master is used to monitor the UC-DSP


traces.
Make calls as defined in the table on all the
TRXs.
In case of GPRS call, transfer a file of 200 kb.

Nokia Siemens Networks

BTS_CONF_DATA is sent to BTS by BSC


containing ST-IRC mode as enabled.
The BTS sends ACK, on BTS_BSC_ACK to the
BSC.
STIRC information is sent to the EQDSP in the
INI message for both the sectors.
Call is successful.
In case of GPRS, file transfer is successful.
ST-IRC is disabled successfully.
BTS_CONF_DATA is sent to BTS by BSC
containing ST-IRC mode as disabled.
The BTS sends ACK, on BTS_BSC_ACK to the
BSC.
STIRC information is sent to the EQDSP in the
INI message for both the sectors.
Calls are successful.
In case of GPRS, file transfer is successful.

131 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

Case Ref.

Type of Call

Configuration

13-355736.05

FR

Any, RDIV=N, RF-Hopping (Metro)

13-355736.06

HR

2+2 (Metro)

13-355736.07

GPRS

4 omni (Metro)

13-355736.08

FR

4+4+4 Chaining configuration (Metro)

14.1.3

4 omni EDGE configuration

Input

Expected Output

Enable ST-IRC in the sector by MML command


ZEQM: BTS=<BTS ID>: STIRC=Y;
A-bis interface is monitored.

ST-IRC is enabled successfully.

Trace master is used to monitor the UC-DSP


traces.
Make call as defined in the table.
In case of GPRS call transfer a file of 200 kb in
UL and DL direction.
Disable ST-IRC in the sector by MML command
ZEQM: BTS=<BTS ID>: STIRC=N;
A-bis interface is monitored.

Trace master is used to monitor the UC-DSP


traces.
Make calls as defined in the table on all the
TRXs.
In case of GPRS call, transfer a file of 200 kb.

BTS_CONF_DATA is sent to BTS by BSC


containing ST-IRC mode as enabled.
The BTS sends ACK, on BTS_BSC_ACK to the
BSC.
STIRC information is sent to the EQDSP in the
INI message for both the sectors.
Call is successful.
In case of GPRS, file transfer is successful.
ST-IRC is disabled successfully.
BTS_CONF_DATA is sent to BTS by BSC
containing ST-IRC mode as disabled.
The BTS sends ACK, on BTS_BSC_ACK to the
BSC.
STIRC information is sent to the EQDSP in the
INI message for both the sectors.
Calls are successful.
In case of GPRS, file transfer is successful.

Case Ref.

Type of Call

Configuration

13-355736.05

FR

Any, RDIV=N, RF-Hopping (Metro)

13-355736.06

HR

2+2 (Metro)

13-355736.07

GPRS

4 omni (Metro)

13-355736.08

FR

4+4+4 Chaining configuration (Metro)

132 (152)

Nokia Siemens Networks

ST-IRC

Nokia Siemens Networks

133 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

14.2

Alarm Handling

14.2.1

ST-IRC in a GSM site

Purpose:
To verify that ST-IRC cannot be enabled for a GSM site and correct alarm is reported.
Note 65.
All test cases shall be performed using BSC SW S12 unless otherwise stated.
Note 66.
For Metrosite, use EDGE TRXs unless otherwise stated.
Equipment and BTS Set-Up
Site - as per configuration defined in test case.

Input

Expected Output

Enable ST-IRC by MML command


ZEQM: BTS=<BTS ID>: STIRC=Y;
A-bis interface is monitored.

Trace master is used to monitor the UCDSP traces.


Lock the BTS.

ST-IRC is enabled successfully.


BTS_CONF_DATA is sent to BTS by BSC
containing ST-IRC mode as enabled.
The BTS sends ACK, on BTS_BSC_ACK to the
BSC.
STIRC information is sent to the EQDSP in the
INI message for both the sectors.

Replace one BB2E card with BB2A and


unlock the BTS.

Alarm 7606 Non-Edge TRX accidentally used in


Edge capable mode is reported on BTS Manager
and on BSC. Alarm 7603 for the sector appeared.

Reset the sector.


Disable ST-IRC by MML command:

Alarms are cancelled and then reported again.

ZEQM: BTS=<BTS ID>: STIRC=N;

134 (152)

Nokia Siemens Networks

ST-IRC

Input

Expected Output

A-bis interface is monitored.

Trace master is used to monitor the UCDSP traces.


Lock/unlock the sector.
Speech calls are made.
Case Ref

Input

BTS_CONF_DATA is sent to BTS by BSC


containing ST-IRC mode as disabled.
The BTS sends ACK, on BTS_BSC_ACK to the
BSC.
STIRC information is sent to the EQDSP in the
INI message for both the sectors.
All the Alarms are cancelled and BTS comes up
in WO state.
Calls are successful.
Configuration

Expected Output

Enable ST-IRC by MML command


ZEQM: BTS=<BTS ID>: STIRC=Y;

For MetroSite Alarm 7606 Non-Edge TRX


accidentally used in Edge capable mode is
reported on BTS Manager and on BSC for all the
GSM TRXs except for one TRX.
For UltraSite Alarm 7606 Non-Edge TRX
accidentally used in Edge capable mode is
reported on BTS Manager and on BSC for all the
GSM TRXs.
In case of multi sector BCF, alarm 7603 for the
sector is reported.
In case of BCF having only one sector, alarm
7600 BCF faulty will be reported.

Reset the sector in case of 7603 alarm or


reset the BCF in case of 7600 alarm.
Disable ST-IRC by MML
command:ZEQM: BTS=<BTS ID>:
STIRC=N;
Reset the sector in case of 7603 alarm or
reset the BCF in case of 7600 alarm.

Alarms are cancelled and then reported again.

Speech calls are made.

Calls are successful.

Case Ref
13-355752.03

Configuration
GSM (Metro)

Input

All the Alarms are cancelled and BTS comes up


in WO state.

Expected Output

Nokia Siemens Networks

135 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

Any configuration is used.

BCF is in supervisory state.

Enable ST-IRC by MML command


ZEQM: BTS=<BTS ID>: STIRC=Y;
A-bis interface is monitored.

ST-IRC is enabled successfully.

Trace master is used to monitor the UCDSP traces.


Replace EDGE TRX by GSM TRX.

Lock/unlock the sector.


Disable ST-IRC by MML command:
ZEQM: BTS=<BTS ID>: STIRC=N;
A-bis interface is monitored.

Trace master is used to monitor the UCDSP traces.


Lock/unlock the sector.
Speech calls are made.
Case Ref.
13-355752.05

14.2.2

BTS_CONF_DATA is sent to BTS by BSC


containing ST-IRC mode as enabled.
The BTS sends ACK, on BTS_BSC_ACK to the
BSC.
STIRC information is sent to the EQDSP in the
INI message for the sector.
Alarm 7606 Non-Edge TRX accidentally used in
Edge capable mode is reported on BTS Manager
and on BSC for the TRX.
Alarm is cancelled and then reported again.

BTS_CONF_DATA is sent to BTS by BSC


containing ST-IRC mode as disabled.
The BTS sends ACK, on BTS_BSC_ACK to the
BSC.
STIRC information is sent to the EQDSP in the
INI message for the sector.
All the Alarms are cancelled and BTS comes up
in WO state.
Calls are successful.
Configuration
EDGE (Metro)

EDGE TRX replaced by GSM TRX

Purpose:
To verify that ST-IRC cannot be enabled for a GSM site and correct alarm is reported.
Note 67.
All test cases shall be performed using BSC SW S12 unless otherwise stated.
Note 68.
For Metrosite, use EDGE TRXs unless otherwise stated.
Equipment and BTS Set-Up
Site - as per configuration defined in test case.

136 (152)

Nokia Siemens Networks

ST-IRC

Input

Expected Output

Enable ST-IRC by MML command


ZEQM: BTS=<BTS ID>: STIRC=Y;

For MetroSite Alarm 7606 Non-Edge TRX


accidentally used in Edge capable mode is
reported on BTS Manager and on BSC for all the
GSM TRXs except for one TRX.
For UltraSite Alarm 7606 Non-Edge TRX
accidentally used in Edge capable mode is
reported on BTS Manager and on BSC for all the
GSM TRXs.
In case of multi sector BCF, alarm 7603 for the
sector is reported.
In case of BCF having only one sector, alarm
7600 BCF faulty will be reported.

Reset the sector in case of 7603 alarm or


reset the BCF in case of 7600 alarm.
Disable ST-IRC by MML
command:ZEQM: BTS=<BTS ID>:
STIRC=N;
Reset the sector in case of 7603 alarm or
reset the BCF in case of 7600 alarm.
Speech calls are made.

Alarms are cancelled and then reported again.

Case Ref
13-355752.03

Configuration
GSM (Metro)

Input

All the Alarms are cancelled and BTS comes up


in WO state.
Calls are successful.

Expected Output

Any configuration is used.

BCF is in supervisory state.

Enable ST-IRC by MML command


ZEQM: BTS=<BTS ID>: STIRC=Y;
A-bis interface is monitored.

ST-IRC is enabled successfully.

Trace master is used to monitor the UCDSP traces.


Replace EDGE TRX by GSM TRX.

Lock/unlock the sector.


Disable ST-IRC by MML command:
ZEQM: BTS=<BTS ID>: STIRC=N;
A-bis interface is monitored.

BTS_CONF_DATA is sent to BTS by BSC


containing ST-IRC mode as enabled.
The BTS sends ACK, on BTS_BSC_ACK to the
BSC.
STIRC information is sent to the EQDSP in the
INI message for the sector.
Alarm 7606 Non-Edge TRX accidentally used in
Edge capable mode is reported on BTS Manager
and on BSC for the TRX.
Alarm is cancelled and then reported again.

BTS_CONF_DATA is sent to BTS by BSC


containing ST-IRC mode as disabled.
The BTS sends ACK, on BTS_BSC_ACK to the
BSC.

Nokia Siemens Networks

137 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input

Expected Output

Trace master is used to monitor the UCDSP traces.


Lock/unlock the sector.
Speech calls are made.
Case Ref.
13-355752.05

14.3

STIRC information is sent to the EQDSP in the


INI message for the sector.
All the Alarms are cancelled and BTS comes up
in WO state.
Calls are successful.
Configuration
EDGE (Metro)

TRX Test and TRX Loop Test

Purpose:
To check that TRX loop test can be executed successfully on TRXs of ST-IRC enabled sector
Note 69.
All test cases shall be performed using BSC SW S12 unless otherwise stated.
Note 70.
For Metrosite, use EDGE TRXs unless otherwise stated.
Equipment and BTS Set-Up
Site - as per configuration defined in test case.

Input

Expected Output

Enable ST-IRC in the sector by MML


command ZEQM: BTS=<BTS ID>:
STIRC=Y;
A-bis interface is monitored.

See the traces using Trace master.


TRX loop test is started from the BTS
Manager Tests/TRX Loop Test. Select
TRX Number, time slot, Loop back points
and modulation method.
TRX loop test is stopped from BTS
manager.

138 (152)

ST-IRC is enabled successfully.

BTS_CONF_DATA is sent to BTS by BSC


containing ST-IRC mode as enabled.
The BTS sends ACK, on BTS_BSC_ACK to the
BSC.
The INI message contains the ST-IRC option as
enabled.
The test is started.

Test is stopped and results are acceptable.

Nokia Siemens Networks

ST-IRC

Input

Expected Output

Test is repeated for GMSK CS1 and


8PSK MCS9.
Case Ref.

Configuration

13-365522.02

Any EDGE (Metro)

Nokia Siemens Networks

139 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

15

RSSI comparison values from BTS


Manager

15.1

RX Antenna Supervision by Comparing RSSI


Value

15.1.1

RSSI comparison values from BTS Manager

Purpose:
To verify that RSSI comparison values feature is switched on/off as specified.
Note 71.
PMAX1 and PMAX2 parameters are set to 6 (ZEUG:<BTS>:PMAX1=6:PMAX2=6), RX
Diversity (ZEQM:<BTS>:RDIV) and RX Diversity Limit (ZEFM:<BCF>:RXDL) values
are set as described in the test case table below. Nokia O&M Abis is monitored during
the BCF reset.
Note 72.
Antenna supervision timer expires after every hour. This means that the RSSI
measurement values are requested by the BSC from the TRXs once an hour.
Note 73.
The antenna can only be supervised reliably if the BCCH power level is within the
acceptable range of power levels 0 to 6.
Note 74.
In order to trigger this feature, the number of samples must be 160000 per TRX in
one hour period This can be achieved by one continuous phone call over one hour
period, or 8 continuous phone calls in 10 minutes time per sector.

140 (152)

Nokia Siemens Networks

RSSI comparison values from BTS Manager

Equipment and BTS Set-Up


2+2 GSM/EDGE Metrosite BTS and 4 Mobile Stations. At least 1 sector contains 5W
and 10W TRXs. 20dB Attenuator connected to 1 antenna.
PC: MML connection, SiteWizard CX4.1, GSM Protocol Analyser.
BSC: S9 or above

Input
Reset BCF
Establish calls via all TRXs
Antenna supervisory timer expires after 1 hour.
Results are checked from the BTS Managers
Site Information and RSSI comparison values
menu. Alarms are checked from the BSC and
BTS Manager.

Case Ref.

RDIV

RXDL

Expected Values

.01

64

N/A

.02

64

N/A

.03

10

N/A

.04

10

Newest and Alarm

15.1.2

Expected Output
RX diversity selection and RX Difference Limit
values are seen in Abis trace as set on BSC.
Calls are successful
RX antenna supervision is performed. Results
can be requested from the BTS Manager. All
TRXs report RX RSSI value with Difference,
Frames and Time Stamp information. Alarm
7601 BCF OPERATION DEGRADED (Rx levels
differ too much between main and diversity
antennas) is seen in Test Case 4.

RSSI comparison values from BTS Manager

Purpose:
To verify that RSSI comparison values feature is switched on/off as specified.
Note 75.
PMAX1 and PMAX2 parameters are set to 6 (ZEUG:<BTS>:PMAX1=6:PMAX2=6), RX
Diversity (ZEQM:<BTS>:RDIV) and RX Diversity Limit (ZEFM:<BCF>:RXDL) values
are set as described in the test case table below. Nokia O&M Abis is monitored during
the BCF reset.
Note 76.
Antenna supervision timer expires after every hour. This means that the RSSI
measurement values are requested by the BSC from the TRXs once an hour.

Nokia Siemens Networks

141 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Note 77.
The antenna can only be supervised reliably if the BCCH power level is within the
acceptable range of power levels 0 to 6.
Note 78.
In order to trigger this feature, the number of samples must be 160000 per TRX in
one hour period This can be achieved by one continuous phone call over one hour
period, or 8 continuous phone calls in 10 minutes time per sector.
Equipment and BTS Set-Up
2+2 GSM/EDGE Metrosite BTS and 4 Mobile Stations. At least 1 sector contains 5W
and 10W TRXs. 20dB Attenuator connected to 1 antenna.
PC: MML connection, SiteWizard CX4.1, GSM Protocol Analyser.
BSC: S9 or above

Input
Reset BCF
Establish calls via all TRXs
Antenna supervisory timer expires after 1 hour.
Results are checked from the BTS Managers
Site Information and RSSI comparison values
menu. Alarms are checked from the BSC and
BTS Manager.

Case Ref.

RDIV

RXDL

Expected Values

.01

64

N/A

.02

64

N/A

.03

10

N/A

.04

10

Newest and Alarm

142 (152)

Nokia Siemens Networks

Expected Output
RX diversity selection and RX Difference Limit
values are seen in Abis trace as set on BSC.
Calls are successful
RX antenna supervision is performed. Results
can be requested from the BTS Manager. All
TRXs report RX RSSI value with Difference,
Frames and Time Stamp information. Alarm
7601 BCF OPERATION DEGRADED (Rx levels
differ too much between main and diversity
antennas) is seen in Test Case 4.

RSSI comparison values from BTS Manager

15.1.3

Alarms from BTS Manager during RSSI comparison values test

Purpose:
To verify that RSSI feature is switched on when RX diversity is on and RX difference
parameter is switched on (value between 0-63 dB). Also, with 20dB attenuation on 1
antenna, RX level differs too much alarm is seen.
Note 79.
PMAX1 and PMAX2 parameters are set to 6 (ZEUG:<BTS>:PMAX1=6:PMAX2=6), RX
Diversity (ZEQM:<BTS>:RDIV) and RX Diversity Limit (ZEFM:<BCF>:RXDL) values
are set as described in the test case table below. Nokia O&M Abis is monitored during
the BCF reset.
Note 80.
Antenna supervision timer expires after every hour. This means that the RSSI
measurement values are requested by the BSC from the TRXs once an hour.
Note 81.
The antenna can only be supervised reliably if the BCCH power level is within the
acceptable range of power levels 0 to 6.
Note 82.
In order to trigger this feature, the number of samples must be 160 000 per TRX in
one hour period This can be achieved by one continuous phone call over one hour
period, or 8 continuous phone calls in 10 minutes time per sector.
Equipment and BTS Set-Up
2+2 GSM/EDGE Metrosite BTS, 4 Mobile Stations. 20dB Attenuator connected to 1
antenna.
PC: MML connection, SiteWizard CX4.1, GSM Protocol Analyser.
BSC: S9 or above

Input
Reset BCF
Establish calls via all TRXs

Nokia Siemens Networks

Expected Output
RX diversity selection and RX Difference Limit
values are seen in Abis trace as set on BSC.
Calls are successful.

143 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Antenna supervisory timer expires after 1 hour.


Results are checked from the BTS Managers
Site Information and RSSI comparison values
menu. Alarms are checked from the BSC and
BTS Manager.

RX antenna supervision is performed. Results


can be requested from the BTS Manager. All
TRXs report RX RSSI value with Difference,
Frames and Time Stamp information. Alarm
7607 TRX OPERATION DEGRADED (Rx levels
differ too much between main and diversity
antennas) is seen.

TRXs 2 and 4 are removed and installed back


after 1.5 hours from the beginning of the test.

Calls via TRXs 2 and 4 are released. Counter in


TRXs 2 and 4 starts.

Calls via TRXs 2 and 4 are re-established.

Calls are successful.

After 2 hours from the beginning of the test


results are checked from the BTS Managers Site
Information and RSSI comparison values menu.
Alarms are checked from the BSC and BTS
Manager.

RX antenna supervision is performed. Results


can be requested from the BTS Manager. All
TRXs report RX RSSI value with Difference,
Frames and Time Stamp information. Alarm
7607 TRX OPERATION DEGRADED (Rx levels
differ too much between main and diversity
antennas) is seen. TRX 2 and 4 have
approximately half the sample frames compared
to amount of frames in TRXs 1 and 3.

DIV OUT and DIV IN cables on TRXs 3 and 4 are


removed.

7604 BTS OPERATION DEGRADED alarm is


seen after next report.

DIV OUT and DIV IN cables on TRXs 1 and 2 are


removed.
All cables on TRXs are installed back.

7601 BCF OPERATION DEGRADED alarm is


seen and alarm 7604 is cancelled after next
report.

All alarms are cancelled after next report.


Calls are successful.

Establish calls via all TRXs.


Antenna supervisory timer expires after 1 hour.
Results are checked from the BTS Managers
Site Information and RSSI comparison values
menu. Alarms are checked from the BSC and
BTS Manager.

RX antenna supervision is performed. Results


can be requested from the BTS Manager. All
TRXs report RX RSSI value with Difference,
Frames and Time Stamp information. Alarm
7607 TRX OPERATION DEGRADED (Rx levels
differ too much between main and diversity
antennas) is seen.

Case Ref.

RDIV

RXDL

Expected Values

.01

10

RSSI comparison values and expected alarms

144 (152)

Nokia Siemens Networks

RSSI comparison values from BTS Manager

15.1.4

RSSI comparison values from remote BTS Manager

Purpose:
To verify that RSSI values can be requested using remote BTS Manager.
Note 83.
PMAX1 and PMAX2 parameters are set to 6 (ZEUG:<BTS>:PMAX1=6:PMAX2=6), RX
Diversity (ZEQM:<BTS>:RDIV) and RX Diversity Limit (ZEFM:<BCF>:RXDL) values
are set as described in the test case table below. Nokia O&M Abis is monitored during
the BCF reset.
Note 84.
Antenna supervision timer expires after every hour. This means that the RSSI
measurement values are requested by the BSC from the TRXs once an hour.
Note 85.
The antenna can only be supervised reliably if the BCCH power level is within the
acceptable range of power levels 0 to 6.
Note 86.
In order to trigger this feature, the number of samples must be 160 000 per TRX in
one hour period This can be achieved by one continuous phone call over one hour
period, or 8 continuous phone calls in 10 minutes time per sector.
Equipment and BTS Set-Up
2+2 GSM/EDGE Metrosite BTS and 4 Mobile Stations. 20dB Attenuator connected to 1
antenna.
PC: MML connection, SiteWizard CX4.1, GSM Protocol Analyser.BSC: S9 or above

Input
Reset BCF
Establish calls via all TRXs
Antenna supervisory timer expires after 1 hour.
Results are checked from the BTS Managers
Site Information and RSSI comparison values
menu. Alarms are checked from the BSC and
remote BTS Manager.

Case Ref.

RDIV

RXDL

Expected Values

.01

10

Newest and Alarm

Nokia Siemens Networks

Expected Output
RX diversity selection and RX Difference Limit
values are seen in Abis trace as set on BSC.
Calls are successful
RX antenna supervision is performed. Results
can be requested from the remote BTS
Manager. All TRXs report RX RSSI value with
Difference, Frames and Time Stamp
information. Alarm 7601 BCF OPERATION
DEGRADED (Rx levels differ too much between
main and diversity antennas) is seen.

145 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

16

Alarm reporting

16.1

Alarm reporting from DMC when BTS polling is


used

Purpose:
The purpose of the test case is to verify that BTS is correctly reporting the alarms from
the DMC in case of BTS polling is in use.

Input
Any Metrosite configuration is in use with CX(M)6
Add both the DMC on the BSC, with
ZQWA:BCF=47:DMR=INDEX:Q1PORT:;
Check the Q1 management on BTS Manager
(Transmission -Q1 Management) and switched
ON the "InternalToExternal" relay.
BTS polling is in use and we can see both the
DMR equipment in ZQWL:BCF=# command
output.
Make a call on the BTS.
Disconnect the physical tributary unit from the
DMC.
Reconnect the physical tributary unit which was
disconnected in step2.
Switch OFF one of the DMR units in DMC setup.

Switch ON the DMR unit that has been switched


OFF in test step 4.

146 (152)

Nokia Siemens Networks

Expected Output
Metrosite with DMC setup is working fine. No
unexpected alarm is observed on the BTS
Manager and the BSC.
Call is ongoing.

Alarm 8061 is reported on BSC and BTS


manager. No disturbance on ongoing call.
Alarm 8061 is cancelled from both BSC and
BTS manager. No disturbance on ongoing call.
Alarm 8081, 8099 are reported with severity
Critical and Alarm 8102 is reported with severity
Major on BSC and BTS manager. No
disturbance on ongoing call.
All the alarm gets cancelled both on BTS
Manager and BSC.
On BTS Manager alarm 8081 and 8099 are
cancelled with severity Critical and alarm 8102 is
cancelled with severity major. No disturbance on
ongoing call.

Alarm reporting

Input

Expected Output

Case Ref.
1

16.2

Configuration

Any Configuration

Alarm reporting after BCF Block / Unblock from


the BTS Manager

Purpose:
The purpose of these test cases is to verify that alarm 7801 MMI Connected to Base
Station: Local MMI Connected is cancelled and reported correctly after BCF Block /
Unblock from the BTS Manager

Input
Configure the site as given in the test case.
BTS SW Used: CXM6.
MMI is connected to the base station and BTS
manager is launched. Use latest version of the
CXM6 MMI SW.

The Block command is given for the BCF from the


BTS Manager.

The Unblock command is given for the BCF from


the BTS Manager.

Calls are made on every TRXs.


Case Ref.

Configuration

2+2 GSM/EDGE

Nokia Siemens Networks

Expected Output
The BCF is in supervisory state. No unexpected
alarms are observed on the BSC.
BTS Manager is successfully connected to the
base station.
The alarm 7801 MMI Connected to Base
Station: Local MMI Connected is reported at the
BTS Manager and BSC
The alarm 7208 LOCAL BLOCK: BCF is sent to
BSC and BTS Manager.
The alarm 7801 MMI Connected to Base
Station: Local MMI Connected is cancelled
properly with complete description.
The BCF initialises correctly. The alarm 7208
LOCAL BLOCK: BCF is cancelled at the BSC
and at the BTS Manager.
BCF comes in supervisory state.
The alarm 7801 MMI Connected to Base
Station: Local MMI Connected is reported again
correctly at the BTS manager and BSC.
All calls are successful.

147 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Input
Configure the site as given in the test case.
BTS SW Used: CXM6.
MMI is connected to the base station. Use latest
version of the CXM6 MMI SW.

Enable the STIRC feature for sector-1 by giving


the following MML command:
ZEQM:BTS=<BTS No.>:STIRC=Y;
The Block command is given for the GSM TRX
from the BTS Manager.

The Unblock command is given for the blocked


TRX from the BTS Manager.

Enable the STIRC feature for sector-2 by giving


the following MML command:
ZEQM:BTS=<BTS No.>:STIRC=Y;

The Block command is given for the sector 2 from


the BTS Manager.

The Unblock command is given for the sector 2


from BTS Manager.

Expected Output
The BCF is in supervisory state. No unexpected
alarms are observed on the BSC.
BTS Manager is successfully connected to the
base station.
The alarm 7801 MMI Connected to Base
Station: Local MMI Connected is reported at the
BTS Manager and BSC.
STIRC is enabled successfully.
Alarm 7606: Non EDGE TRX device type used
accidentally in EDGE Capable Mode is reported
for GSM TRX.
Alarm 7208 LOCAL BLOCK: is reported.
Alarm 7606: Non EDGE TRX device type used
accidentally in EDGE Capable Mode is
cancelled for GSM TRX.
Alarm 7208 LOCAL BLOCK:is cancelled.
Alarm 7606: Non EDGE TRX device type used
accidentally in EDGE Capable Mode is reported
again for GSM TRX.
STIRC is enabled successfully.
Alarm 7606: Non EDGE TRX device type used
accidentally in EDGE Capable Mode is reported
for TRX 3 followed by 7603: Non EDGE TRX
device type used accidentally in EDGE Capable
Mode for sector-2.
Alarm 7208 LOCAL BLOCK: is reported.
Alarm 7603: Non EDGE TRX device type used
accidentally in EDGE Capable Mode for Sector2 and alarm 7606: Non EDGE TRX device type
used accidentally in EDGE Capable Mode for
TRX-3 are cancelled.
Alarm 7208 LOCAL BLOCK: is cancelled.
Alarm 7606: Non EDGE TRX device type used
accidentally in EDGE Capable Mode for TRX-3
and 7603: Non EDGE TRX device type used
accidentally in EDGE Capable Mode for Sector2 are reported again.

Case Ref.

Configuration

2(GSM/EDGE)+2(GSM)

148 (152)

Nokia Siemens Networks

Alarm reporting

Input
Configure the site as given in the test case.
BTS SW Used: CXM6.
MMI is connected to the base station. Use latest
version of the CXM6 MMI SW.

Enable the STIRC feature for both sectors by


giving the following MML command:
ZEQM:BTS=<BTS No.>:STIRC=Y,;

The Block command is given for the BCF from the


BTS Manager.
The BCF is unlocked from the BTS Manager.

Expected Output
The BCF is in supervisory state. No unexpected
alarms are observed on the BSC.
BTS Manager is successfully connected to the
base station
The alarm 7801 MMI Connected to Base
Station: Local MMI Connected is reported at the
BTS Manager and BSC.
STIRC is enabled successfully for both sectors.
Alarm 7606: Non EDGE TRX device type used
accidentally in EDGE Capable Mode is reported
for TRX 1 followed by 7603: Non EDGE TRX
device type used accidentally in EDGE Capable
Mode for sector-1.
Alarm 7606: Non EDGE TRX device type used
accidentally in EDGE Capable Mode is reported
for TRX-3 and finally BCF level alarm 7600:
Non EDGE TRX device type used accidentally in
EDGE Capable Mode is raised.
Alarm 7208 LOCAL BLOCK: is reported.
All alarms on BTS Manager are cancelled.
Alarm 7208 LOCAL BLOCK:is cancelled.
BCF initialises and comes in supervisory state.
Alarm 7606: Non EDGE TRX device type used
accidentally in EDGE Capable Mode is reported
for TRX 1 followed by 7603: Non EDGE TRX
device type used accidentally in EDGE Capable
Mode for sector-1.
Alarm 7606: Non EDGE TRX device type used
accidentally in EDGE Capable Mode is reported
for TRX-3 and finally BCF level alarm 7600:
Non EDGE TRX device type used accidentally in
EDGE Capable Mode is raised again.

Case Ref.

Configuration

2+2 GSM

Nokia Siemens Networks

149 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

17

BCCH reconfiguration

17.1

BCCH reconfiguration when TSC is different from


BCC

Input
The site is configured as given in the test case.
BTS SW Used: CXM6.
Master TRX is set as the preferred BCCH TRX
using the MML command ZERM.
Calls are made on all the TRXs.
Using MML command ZDTC at BSC, the
preferred BCCH TRX signalling link is blocked so
that BCCH reconfiguration is performed, on the
TRX mentioned in the table.
MML command ZERO is used to verify the TSC
values for the TRXs at the BSC.
Calls are made on all the TRXs.
Using MML command ZDTC at BSC, the
preferred BCCH TRX signalling link is unblocked.
The command ZERO is used to verify the TSC
values for the TRXs at the BSC
Calls are made on all TRXs at least twice.
Calls are made on all the timeslots of the TRX
used for reconfiguration.
The A-bis TRX signalling links are followed during
the calls.
Case Ref.

150 (152)

BCF Configuration

Nokia Siemens Networks

Expected Output
The BCF is in supervisory state. No unexpected
alarms are observed on the BSC and BTS
Manager.
Master TRX is configured as preferred BCCH
TRX.
All calls are successful.
BTS_CONF_DATA is sent for the BCCH
reconfiguration. This should now detail the new
BCCH TRX as having the same TSC as the
BCC. Calls remain unaffected on the TRXs,
which are not getting reset.
The reconfigured BCCH TRX should contain the
TSC same as BCC.The faulty TRX should have
the TSC other than BCC.
All calls are successful.
The preferred BCCH TRX returns to the working
state and it is reconfigured as the BCCH TRX.
The reconfigured BCCH TRX should have the
TSC same as BCC.The non-BCCH TRXs should
have the TSC other than BCC.
Calls on all TRXs are successful.
All calls are successful
A-bis Measurement Result message values for
RX Qual in both uplink and downlink, and the UL
FER shall in laboratory conditions are
predominately of value 0.
TRX used for reconfiguration

BCCH reconfiguration

Input
1

Expected Output
4 Omni GSM/EDGE with GSM TRX as
Master TRX.

Nokia Siemens Networks

TRX 2

151 (152)

Functional Verification Regression Specification for BTS SW Release CXM6

Reference
1.

152 (152)

Functional Regression Test Specification for BTS SW CXM5 for MetroSite

Nokia Siemens Networks