cxm7 functional regression specification

DN0931492 Issue 2-0 1 of 57

Functional Verification Regression Test Specification Release Delivery: CXM7 Product Family: GSM/EDGE Base Stations Product: MetroSite EDGE Base Station Release: CXM7

© Nokia Siemens Networks

DN0931492 Issue 2-0 2 of 57

Table of Contents 1. Purpose......................................................................................................................................................... 3 2. Document structure....................................................................................................................................... 3 3. Common aspects of test execution and configuration .................................................................................. 3

3.1 Prerequisites ............................................................................................................................................................ 5 3.2 Hardware Requirements .......................................................................................................................................... 5 3.3 Software Requirements............................................................................................................................................ 6 3.4 Specialist Test Equipment Requirements ................................................................................................................ 7

4. BTS Commissioning and Software Download .............................................................................................. 8 4.1 Direct SW Downloading from the BSC to the BCF................................................................................................... 8 4.2 BTS Commissioning from BTS Manager ................................................................................................................. 9 4.3 BTS SW Download from the BTS Manager to the BCF ......................................................................................... 11 4.4 Standalone Commissioning ................................................................................................................................... 12

5. Manual Configuration Change .................................................................................................................... 13 5.1 Adding new TRXs .................................................................................................................................................. 13 5.2 Site Expansion ....................................................................................................................................................... 14

6. BTS Tests.................................................................................................................................................... 16 6.1 TRX Tests .............................................................................................................................................................. 16 6.2 ABIS Loop test ....................................................................................................................................................... 20 6.3 TRX Loop Test ....................................................................................................................................................... 24

7. Object Control ............................................................................................................................................. 24 7.1 TRX Lock/Unlock and Block/Unblock..................................................................................................................... 24 7.2 BCCH Reconfiguration........................................................................................................................................... 27 7.3 BCCH reconfiguration when TSC is different from BCC ........................................................................................ 28 7.4 BTS Lock/Unlock and Block/Unblock ..................................................................................................................... 29 7.5 BCF Lock and Unlock ............................................................................................................................................ 31 7.6 BCF Reset ............................................................................................................................................................. 34 7.7 TRX Reset ............................................................................................................................................................. 35

8. Recovery for BSS and Site Synchronisation............................................................................................... 36 8.1 Site Synchronisation Recovery during start-up/resets............................................................................................ 36 8.2 Site Synchronisation recovery with GPS signal recovery....................................................................................... 37

9. BTS Manager Functionality......................................................................................................................... 41 9.1 BTS Manual Commissioning.................................................................................................................................. 41 9.2 BTS Manual Commissioning with FXC RRI ........................................................................................................... 45 9.3 BTS Manager Start-Up........................................................................................................................................... 48 9.4 FC E1/T1 and FXC E1/T1 Transmission Menus .................................................................................................... 49 9.5 Logical Objects view window handling ................................................................................................................... 51 9.6 File Menu Commands ............................................................................................................................................ 52 9.7 Objects Menu Commands...................................................................................................................................... 53

Contact:

Contact your local Nokia Siemens Networks support

Summary of changes:

15-05-2009 1.0 (2-0) Approved


DN0931492 Issue 2-0 3 of 57

1. PURPOSE

This document defines the library of test cases in order to verify the functional features of BTS software release CXM7 for NSN MetroSite Base Station.

In general, the features and test cases described herein are intended for NSN GSM 800, 900, 1800 and 1900 environments.

2. DOCUMENT STRUCTURE

This document is sectioned into major testing view: MetroSite EDGE BTS Regression. Within these sections, there are high level testing descriptions. These area’s are then structured in the following way: • Common aspects of test execution and configurations for all the features or

functional areas. The following sections detail the individual test cases: • The purpose of the test case. • Specific aspects of testing the case (if required). • A table containing the test case steps and expected outputs. Following the test

steps the table contains the channel and hardware configurations to be applied to the test case.

Repeated for each test case.

3. COMMON ASPECTS OF TEST EXECUTION AND CONFIGURATION

The following aspects shall be used and assumed if not stated in specific test cases:

Note 1. The BSC version to be used is S14, BTS Manager Version to be used is CX7, CXM7 BTS SW to be used and GCS version to be used is R6.0 unless otherwise specified.

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

Note 3. In this document, references to S14 mean any S14 generation BSC software package. The latest package and Change Delivery (CD) under test should be used. References to S13 mean any S13 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 wherever applicable. This principle is followed in the test descriptions in this document.


DN0931492 Issue 2-0 4 of 57

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 NSN MetroSite BTS, the Master TRX is by default not a BCCH TRX unless it is defined as the preferred BCCH TRX.

Note 6. A multi TRX configuration is a site having several TRXs 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 has 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.


DN0931492 Issue 2-0 5 of 57

NSN 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 NSN BTS Manager can be connected at the same time.

Note 11. An 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. GTRX=N for GSM TRXs in EDGE/GSM configuration, if EGENA needs to be enabled.

3.1 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.

3.2 Hardware Requirements

Other Network Elements BSC

Core Network with GPRS and EDGE capabilities.


DN0931492 Issue 2-0 6 of 57

Mobile Stations

Feature Specific optionsSpeech 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 BCCH Adaptive Multi-Rate AMR FR and HR General SMS, Mobile Originating (MO) & Mobile Terminating (MT) Enhanced Measurement Reports

EMR Capable

3.3 Software Requirements

- SiteWizard7.0

- Latest available Test Packet or Pre-Release of CXM7

- GCS R6.0

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

Table 1: SW Versions of Other Network Elements

Network Element SW VersionBSC S13, S14 HLR M14.1 MSC M14.1 NSN NetAct OSS4.1, OSS4.2 CD1 LMU LMU 4.4, LMUB 1.0 CD3 SGSN SG7 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, ITN C3.0 CD2, ITN C3.0 CD3

Transmission (FC E1/T1) ITN C1.0 Transmission (MetroHub) MHB C2.1, C2.2, C3.0, C3 CD1 BTS Manager PC Windows 98, Windows 2000, Windows XP,

Windows 2003 Server MetroHub SW C3 CD3

PC Applications

- Internet browser

- FTP, UDP software

- Terminal Emulator


3.4 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

- Assortment of combiners

- Attenuators

- Terminators

- Signal generator

- Spectrum analyser

- GSM Protocol Analyser

- Data Channel Simulator

- D-Bus Analyser

- Abis Breaker

DN0931492 Issue 2-0 7 of 57 © Nokia Siemens Networks

4. BTS COMMISSIONING AND SOFTWARE DOWNLOAD

4.1 Direct SW Downloading from the BSC to the BCF

Purpose:

The purpose of this test case 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 OutputThe BCF is operational (BCF is in WO state). Set up a speech call in the BCF.

Call is successful

Attach latest UltraSite SW to the BCF. 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.

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

Operation is successful.

Block the OMU link. Attach the BTS SW to be tested using MML command ‘ZEWA:

The BSC indicates that the BTS SW can’t 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 (non-volatile memory). The BCF is initialised and comes to working state with all TRXs.

Verify the end state of BTS software loaded. The end state is same as specified in the test case. The Active SW and SW in Newest Flash memory are same.

Speech 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


Input Expected Output1 3 Site chain, Multi

TRX EDGE+GSM+ EDGE/GSM

Active-CXM7 Flash-CXM7 and CXM6

Download CXM6 CD1.0

Active-CXM6 CD1.0 Flash-CXM6 CD1.0 and CXM7

64 kbps

4.2 BTS Commissioning from BTS Manager

Purpose:

The purpose of this test case is to check that BTS is commissioned successfully with EDAP configured from BTS Manager and verify that the TRX test and ABIS loop tests can be executed successfully.

Note 17.

CX7 SW must not be available in the flash/active memory of the Master TRX.

Note 18.

The acceptable tests results for TRX test are: BER = 0%, RX-Sens: -110.5 dBm (or better) for GSM 900 and GSM 800, -111 dBm (or better) for GSM 1800 and GSM 1900.

The GMSK sensitivity is typically –111 to -113 dBm, MCS-5 is –107 to -109 dBm and MCS-9 is –97 to -99 dBm.

Note 19.

Acceptable test results for Abis loop test are: BER<0.1%, FER<0.1%

Input Expected OutputCreate the BTS Site at BSC as described in the test case. Put all FU links and OMU link in WO state using MML commands ZDTC:<FU no./OMU>:WO; Unlock all TRXs and BTS

OMU and TRX Signalling link state is in BL-SYS state. The BTS and its TRXs are unlocked successfully.

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

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

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


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

Traffic Manager window gets closed and commissioning proceeds. After displaying the message “BCF in the configuring state”, commissioning fails to proceed. And 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

Click on “Cancel” button to cancel the commissioning.

A pop up window is displayed.

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

“Commissioning Report” page is displayed.

Now click on the “Finish” button to finish the commissioning process.

Commissioning wizard will be closed successfully.

Now decommission 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.

OMU link comes to working state. BTS SW downloaded successfully. Commissioning is successful.

Save the commissioning report and analyse it for TRX test and Abis loop test for each TRX.

TRX test and Abis loop test are executed successfully with acceptable test results.

Check the BTS SW at the BSC and BTS Manager

Requested SW is active.

Set up voice calls on all TRXs. All calls are successful Case Ref. BTS Type/Configuration EDAP POOL at BSC EDAP Attached

to the TRXs 1 NSN MetroSite

4+4+4(EDGE+GSM+EDGE) chained site, Combined signalling

Yes (Multiple TSs) Yes, EDAP attached to the EDGE TRXs only


4.3 BTS SW Download from the BTS Manager to the BCF

Purpose:

The purpose of this test case is to check that the BCF SW can be updated from BTS Manager and put into use successfully.

Input Expected OutputThe BCF is operational (BCF is in WO state). Set up a speech call in the BCF.

Call is successful

From BTS Manager, the BTS SW ⎪ Update command is selected. The master file for CXM7 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. The SW loading does not disturb the call.

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 SW versions are requested.

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 BCF is operational (BCF is in WO state).

A speech 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 call is not disturbed by the SW related actions.

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. Configuration 1 2+2GSM/EDGE, RF Hopping in 1st sector, 2nd sector DFCA enabled with

1 DFCA TRX


4.4 Standalone Commissioning

Purpose:

The purpose of the test case is to check that standalone site can be commissioned and after the ABIS is through, software is downloaded if activated software is not present in flash Memory. And finally the site comes up.

Input Expected OutputDisconnect the Abis The LED of the transmission card is RED.

Create the BTS Site at BSC as described in the test case. Put all FU links and OMU link in WO state using MML commands ZDTC:<FU no./OMU>:WO; Unlock all TRXs and BTS

OMU and FU link state is in BL-SYS state. The BTS and its TRXs are unlocked

Attach the BTS SW CXM7 to the BCF using MML command ZEWA. Activate the attached BTS SW using MML command ZEWV.( activated software should not be present in flash Memory )

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

Launch the BTS Manager and connect to the BTS BTS Manager is launched and connected to the BTS successfully. MMI will show “OMU is disabled”.

Start commissioning of the BTS Site.

Commissioning Started successfully

During the commissioning the warning message will pop up stating,“ Abis is not enabled and therefore the BCF is in the waiting for LAPD state Do you want to give the Use Current Command and continue commissioning without Abis connection?”

Click yes and continue commissioning. Site will be successfully commissioned.

Now click on the “Finish” button to finish the commissioning process.

Commissioning wizard will be closed successfully.

Connect the Abis MMI will show “OMU is enabled”. Unlock the BCF using MML ZEFS command at BSC.

Site will take a reset. The activated software will start downloading from BSC. Site will come up as working

Check the BTS SW CXM7 at the BSC and BTS Manager

Requested SW is active.

Set up voice calls on all TRXs. Calls are successful Case Ref. Configuration

1 4 Omni EDGE site. Transmission card is FXC E1T1


5. MANUAL CONFIGURATION CHANGE

5.1 Adding new TRXs

Purpose:

The purpose of the case is to ensure that new TRXs can be manually added to the NSN MetroSite BTS.

Input Expected OutputSpeech calls are made via the BCF in which the TRXs are to be added. The new TRXs being added do not have CXM7 in their flash.

Calls are successfulCalls are held for the whole duration of the test case

LAPD link for the new TRX is created and executed in WO state using MML command ZDTC: <FU no.>: WO; The TRX is created under the correct BCF and BTS in BSC. The TRX is in locked state after it is created.

TRX creation at the BSC is successful.

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 TRXs.

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 dropped.

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 speech calls are made via every TRX and TS (time slots).

The new TRXs is successfully initialised and made operative in the network. Calls are successful

Case Ref.

Configuration O&M and TRXSIG

Transmission Card

Sig Speed

Hopping Mode

Addition Done

1 4+2 TRX GSM (Preferred BCCH)

Combined FXC E1 (ITN C3.0 CD2)

64 kbps None 2 TRX GSM to second BTS, with 64Kbps compressed signalling

2 2+1 TRX EDGE Separate FXC E1/T1 (ITN C3.0 CD2)

32 kbps None 1 EDGE TRX to second BTS, with 32 Kbps signalling

3 2+1 TRX GSM Separate FC STM-1 (ITN C3.0 CD2)

16 kbps BB 1 EDGE TRX to second BTS, with 16 Kbps signalling


5.2 Site Expansion

Purpose:

The purpose of this test case is to ensure that the MetroSite can be extended successfully to a MetroSite chain configuration with correct BTS ID and BTS Object ID displayed at BTS Manager.

Note 20.

If the current BTS Configuration data contains a BTS ID but does not contain the BTS Object ID, value of the BTS Object ID shall be displayed as "BTS: Unknown" on the Graphical User Interface.

Input Expected OutputBCF is in operational state. The new TRXs being added do not have CXM7 S/W in their flash.

BCF is working with no active alarms reported at both BSC and BTS Manager except for alarm "7801: MMI connected to Base Station".

Speech 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, which is also in powered off state.

All Calls are dropped after BCF lock.

Turn the master cabinet power ON. Update Traffic Manager using Transmission menu | Traffic Manager according to new configuration. Turn the slave cabinet power ON. Unlock the BCF, newly created BTS and TRX(s).

All BTSs come to working state with no active alarms reported at both BSC and BTS Manager except for alarm "7801: MMI connected to Base Station".

Speech 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. EDAP is created at the BSC. Attach EDAP to all EDGE TRXs.

All Calls are dropped. EDAP is successfully created. EDAP is successfully attached to the TRXs

Turn the master cabinet power ON. Update Traffic Manager using Transmission menu | Traffic Manager according to new configuration with correct EDAP definition in the Traffic Manager. 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.


Speech calls are made on all TRXs for 15 minutes on all the Cabinets.



Input Expected OutputCheck the BTS ID and BTS Object ID in the Objects Properties view of the BTS Manager for each BTS.

The BTS ID and BTS Object ID information is displayed as “Sector: X – BTS: Y”, where X is the value of the BTS ID and Y is the value of the BTS Object ID for every BTS

Case Ref.

Initial Configuration

Configuration after 1st Expansion

Configuration after 2nd Expansion

Initial Hopping Mode

1 (2+2) EDGE (common BCCH)

(2+2) EDGE (common BCCH)+ 4 Omni GSM

(2+2) EDGE (common BCCH)+(4 GSM+ 4 EDGE) with common BCCH with EDAP attach to all EDGE TRXs.

BB Hopping

Input Expected OutputBCF is in operational state. The new TRXs being added do not have CX7 S/W in their flash.


Speech calls are made on all TRXs. Calls are successful

New LAPD link, BTSs and TRXs are created at the BSC to expand the BCF such that a new sector (1800 Band) is made in the slave cabinet with 2 TRXs (5 &6) and Other two TRXs(7 & 8) (900 band) of the slave cabinet are added to the second sector, which is in Master cabinet to make it 4 Omni..

Operation successful.

Lock the BCF and power off the Master cabinet and connect the first slave cabinet, which is also in powered off state

All Calls are dropped after BCF lock.

Turn the master cabinet power ON. Update Traffic Manager using Transmission menu | Traffic Manager according to new configuration. Unlock the TRX(s) , newly created BTS and BCF. A new cabinet with all newly configured TRX(s) (without Transmission card) are powered up.

All BTSs come to working state with no active alarms reported at both BSC and BTS Manager except for alarm "7801: MMI connected to Base Station".

Speech calls are made on all TRXs of the both cabinets.


Case Ref.

Initial Configuration

Configuration After Expansion Initial Hopping Mode

2 (2+2) EDGE, 900 Band

(2+4) EDGE, 900 Band + 2 EDGE, 1800 Band

Non Hopping


6. BTS TESTS

6.1 TRX Tests

Purpose:

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

Note 21.

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

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 22.

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-30±4 i.e. 3dBm to 11 dBm range.

When the test case calls for a failure to occur during the test or a failure to start the test then the failure reason is included in the TRX test report.

Note 23.

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 time-window based filtering for alarm reporting. That is, if an alarm is started and cancelled within 10-seconds.

Note 24.

For all tests that require TRX test to be run, the PMAX value should be set as Maximum (i.e. '0').

Note 25.

The BTS is assumed non-hopping unless otherwise stated.


Note 26.

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-PSK-modulation 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 OutputA speech call is made via the TRX to be tested. The call is successful

TRX test is started from the BSC using the MML command ‘ZUBS’.

The TRX test can be started on TCH TS that does not have BCCH, 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.

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.


Input Expected OutputTRX 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 7615 RTS IS IN TEST USE for used TS is started. When the test is done finished, the alarm 7615 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.

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

The result should be correct for all TRXs

After the completion of the test case set the PMAX value back to 30

Operation successful.

Case Ref.

Configuration Channel Configuration

Hopping Mode

TX Power EGPRS enabled for EDGE units

1. 2+2 common BCCH Dual band EDGE TRX with STIRC enabled

MBCCHC+ TCHD 1st sector- None 2nd sector-RF, Different no. Of frequencies in MAL list (3,20,63 etc)

-Any No


Purpose: The purpose of this test case is to verify that ARFN text box in the TRX test dialog box is enabled when TRXs are in configuring state.

Site is configured as per the test case. TRX1 is made as preferred BCCH TRX.

The site is in supervisory state with no active alarms reported at both BSC and BTS Manager except for alarm "7801: MMI connected to Base Station".

TRX 3 is locked from BSC using MML command ZERS:BTS=<bts no>, TRX=<trx no>:L;

TRX3 shall get locked from BSC.

TRX3 is given reset from BTS Manager. TRX 3 shall take a reset and stays in configuring state.

OMU link is blocked from BSC using MML command ZDTC:<OMU>:BL;

The OMU link shall get disabled. TRX3 shall remain in configuring state. BCF and remaining TRXs shall be in supervisory state.

The Tests | TRX Test command is selected from BTS manager. ARFN text box corresponding to TRX3 is checked.

TRX Test dialog box is opened. On the TRX Test dialog box the ARFN text box is enabled for TRX3

ARFN of TRX3 is changed to a value other than defined in BSC. TRX Test is started on TS2 of TRX3

TRX test shall get started on modified ARFN for TRX3. When TRX test started, alarm 7615 “RTS IS IN TEST USE”, for the used TS and for its partner TS shall be raised. When TRX test is finished, the alarm 7615 “RTS IS IN TEST USE” for the used TS and its partner TS shall get cancelled.

The colour of TSxx and BB2x LEDs at the BTS and BTS manager shall be red during the test and return back to original colour when test finishes.

On the TRX Test dialog box TRX 4 is selected. ARFN text box corresponding to TRX4 is checked.

On the TRX Test dialog box the ARFN text box shall be disabled for TRX4.

OMU link is enabled from BSC using MML command ZDTC:<OMU>:WO;

The OMU link shall get enabled. The site will come in supervisory state with no active alarms reported at both BSC and BTS Manager except for alarm "7801: MMI connected to Base Station".

TRX3 is unlocked from BSC using MML command ZERS:BTS=<bts no>, TRX=<trx no>:U;

TRX3 shall get unlocked from BSC.

The Tests | TRX Test command is selected from BTS manager. TRX3 ARFN in the TRX Test dialog box. is checked

TRX Test dialog box shall get opened. The TRX3 ARFN shall be the same as configured at the BSC.

Speech calls are made on all TRX. All calls are successful


Case Ref Configuration

2. 4 Omni

6.2 ABIS Loop test

Purpose:

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

Note 27.

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

Note 28.

The channel configuration is not significant unless specifically mentioned.

Note 29.

The TSs carrying Control channels, Traffic and GPRS are not tested in ABIS loop test.

Extra HW/Tools: a test script that repeatedly carries out Abis loop tests

Input Expected OutputCS 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

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

The test status indicates success. The test results are acceptable. The calls are not affected.

Make new speech calls on tested TSs Calls are successful Case Ref.

Configuration TS Configuration

Transmission Unit

Signalling Speed

O&M and TRXSIG

Abis Connection

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

FC STM-1 ITN C3 CD2

16 Kbps Separate Normal

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

FC STM-1 ITN C3 CD3



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

Several TRXs in one BTS and any GPRS TS

FXC E1 ITN C3 CD2


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

Several TRXs in one BTS and any GPRS TS

FXC E1 ITN C3 CD3


5 2GSM+2EDGE, common BCCH RF hopping in both sectors

(MBCCH+SDCCH+6TCHF+8TCHF)+(SDCCH+7TCHF+8TCHF)

FXC RRI ITN C3

64 Kbps Combined Satellite abis



FXC RRI ITN C3 CD3




FXC RRI (ITN C3.0 CD2)


1 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 OutputThe 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.

Speech 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.

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

Case Ref. Configuration Transmission Unit (Release) 8 Multi TRX FXC E1/T1 ITN C3 CD2

9 Multi TRX FXC E1/T1 ITN C3 CD3


Input Expected Output10 Multi TRX FC E1/T1 ITN C1.0

Purpose: The purpose of these test cases is to verify that dynamic Abis loop tests are successful on all RTSLs.

Note 30.

Before running an Abis loop test, delete any test report using the MML command ZUBD:AL:BTS=<Bts id>;, which may have been generated earlier at the BSC for the BTS under test.

Input Expected OutputSite is configured as per the test case. DAP is attached to all TRXs and EGENA is enabled at the site.


Dynamic Abis TRX loop test is initiated on TRXs in the sector using MML command ZUBK: TEST:BTS=<Bts id>,TRX=<Trx No>:<RTSL>:SEL=1:ATSL=<DAP TSL on Abis>:;

Command is executed successfully.

Abis loop test report is printed at the BSC using the MML command ZUBP:AL:BTS=<Bts id>;

Report states that the loop test has passed.

Test report is deleted from the BSC.

The Abis loop test report generated earlier is cleared from the BSC.

Calls are made on all TRXs All calls are successful

Dynamic Abis TRX loop test is performed on all the other RTSLs in the BTS.

Loop tests on all TSs pass, except those on control channels and busy traffic channels.

Calls are made on all TRXs

All calls are successful

Case Ref BTS Configuration Channel Configuration

Hopping

Call Type

11. 4 Omni, EDGE MBCCH + SDCCH + TCHD

RF AFS and AHS

12. 4 Omni, EDGE MBCCHC + SDCCB on CH3 + TCHH

None HR and AHS


Purpose: To verify that dynamic Abis loop tests are not successful when BER is introduced to cause LAPD failure.

Test Tool: Data Channel Simulator

Input Expected OutputSite is configured as per the test case. DAP is attached to all TRXs and EGENA is enabled at the site.


Dynamic Abis TRX loop test is initiated on TRXs in the sector using MML command ZUBK: TEST:BTS=<Bts id>,TRX=<Trx No>:<RTSL>:SEL=1:ATSL=<DAP TSL on Abis>:;



Report states that the loop test has passed.

Test report is deleted from the BSC.

The Abis loop test report generated earlier is cleared from the BSC.

Calls are made on all TRXs All calls are successful Dynamic Abis TRX loop test is performed on all the other RTSLs in the BTS.

Loop tests on all TSs pass, except those on control channels and busy traffic channels.

The BER (Bit Error Ratio) is set with the Data Channel Simulator to desired error level. The error is generated in the downlink direction, then in uplink direction and then simultaneously in both directions. Alarms are checked at the BSC and BTS manager.

When alarm limits are reached, alarms get raised at the BSC and the BTS Manager. For BER greater than 1E-3 the alarm 8099 BIT ERROR RATE (BER) > 1E-3 is raised. For BER greater than 1E-6 and less than 1E-3, the alarm 8102 BIT ERROR RATE (BER) > 1E-6 is raised. When the BER is greater than or equal to 1E-3, calls may get released.

Dynamic Abis TRX loop test is initiated on all TRXs in the BTS from the BSC



Report states that the loop test has failed

Case Ref BTS Configuration Channel Configuration

BER

13. 2 Omni, EDGE MBCCHC + TCHF 1E-3


6.3 TRX Loop Test

Purpose: The purpose of this test case is to check that TRX loop test can be executed successfully on TRXs of ST-IRC enabled sector Equipment and BTS Set-Up Site is configured as per the test case.

Input Expected OutputSTIRC is enabled in the sector using MML command ZEQM: BTS=<BTS ID>: STIRC=Y;

STIRC gets enabled successfully.

A-bis interface is monitored. BTS_CONF_DATA is sent to BTS by BSC containing STIRC mode as ON. The BTS sends ACK on BTS_BSC_ACK to the BSC.

Trace Master is used to check whether STIRC is enabled or not.

The INI message contains the STIRC option as enabled

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

The test gets started.

TRX loop test is stopped from BTS manager.

Test is stopped and results are acceptable.

Test is repeated for GMSK CS1 and 8PSK MCS9.

Test results are acceptable

Case Ref. Configuration 1 Any, EDGE

7. OBJECT CONTROL

Note 31.

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.

7.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 OutputTRX transmit power levels are checked with spectrum analyser.

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

Neighbour cells are defined. Speech calls are made via every TRX of the test sector.


TRX of the sector is locked from the BSC. If locked TRX is BCCH TRX then the transmission is checked using a spectrum analyser.

The TRX is locked. Calls on the locked TRX are released. If the locked TRX happens to be the BCCH one then the BCCH transmission stops and Alarm 7767 :”BCCH MISSING” is raised at the BSC. Calls remain ongoing on other TRXs.

TRX is unlocked from BSC. If the BCCH TRX is under test, Alarm 7767 “BCCH MISSING” remains active until the TRX returns to working state.

TRX transmit power levels are checked with spectrum analyser.

The power levels match the defined setting at the BSC.

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

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 blocked TRX is BCCH one, then CCH reconfiguration takes place..

Unblock command is given for the TRX from the BTS Manager.

The 7208 LOCAL BLOCK alarm gets cancelled. The blocked symbol disappears from the TRX object in the Supervision window view.

Alarms are checked at BSC and BTS Manager. There are no active alarms reported at both BSC and BTS Manager except for "7801: MMI connected to Base Station"

Speech calls are made via every TRX. GPRS calls are also made.

All calls are successful.

Case Ref.

Configuration TRX Locked/ Blocked

1 Multi TRX, EDGE/GSM BCCH

2 Multi TRX, EDGE/GSM1 ALL 1 Idle channel interference is checked for all the TRxs before and after lock/unlock & block/unblock that can be seen showing 0 interference level at BSC and shows the value 1 for all the idle timeslots of the TRXs at Abis interface.


Purpose:

The purpose of this test case is to check that BCCH transmission does not start from the faulty sector when non-BCCH TRX is blocked / unblocked

Input Expected OutputSite is configured as per the test case. The site is in supervisory with no active

alarms reported at both BSC and BTS Manager except for alarm "7801: MMI connected to Base Station".

STIRC is enabled for the first sector and BCCH transmission is monitored using a spectrum analyser.

Alarm 7606 "TRX FAULTY: Non EDGE TRX device type used accidentally in Edge Capable Mode" shall be reported for TRX 1 both at BSC and BTS Manager and all the TRXs of this sector shall go to BL-TRX state at BSC. Alarm "7603 BTS FAULTY: Non EDGE TRX device type used accidentally in Edge Capable Mode" shall be reported both at BSC and BTS Manager after some time. The BTS shall come in BL-BTS state at BSC. BCCH transmission from the sector under test shall get stopped after some time.

Non BCCH TRX of the first sector is blocked and then unblocked from BTS Manager and BCCH transmission is monitored for the sector using a spectrum analyser.

BCCH transmission from the sector under test starts and then stops after around 20 seconds.

BCCH transmission from the first sector is kept under observation for next few minutes.

The sector under test shall not transmit.

STIRC is disabled for the first sector. All the TRXs as well as the sector under test shall come to working state.

Calls are made on all the sectors. All calls are successful.

Case Ref. Configuration

3. 2+2, GSM


7.2 BCCH Reconfiguration

Purpose:

The purpose of these tests is to verify that reconfiguration of BCCH to preferred TRX is successful and EGPRS data transfer is successful on BCCH TRX.

Input Expected OutputAbis is monitored. EGPRS enabled on BTS. Attach DAP pool with BCCH TRX. Synchronisation procedure, EGPRS attach and PDP context is checked. EGPRS data transfer is done on both uplink and downlink direction on BCCH TRX.

Data transfers are successful.

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. EGPRS data transfer is done on both uplink and downlink direction on BCCH TRX.

Data transfers are successful.

Case Ref.

Configuration Hopping Mode Preferred BCCH

1 4 Omni EDGE. GP capacity defined on BCCH TRX using BFG parameter.

BB Hopping Master TRX

2 4 Omni EDGE1 BB Hopping Master TRX 1 check idle channel interference for all TRxs before and after BCCH reconfiguration that can be seen showing 0 interference level at BSC and shows the value 1 for all the idle timeslots of the TRXs at Abis interface.


7.3 BCCH reconfiguration when TSC is different from BCC

Purpose:

The purpose of these tests is to verify the reconfiguration of BCCH to preferred TRX when TSC is different from BCC.

Input Expected OutputThe site is configured as given in the test case. BTS SW Used: CXM7.

The BCF is in supervisory state. No active alarms are observed on the BSC and BTS Manager except for "7801: MMI connected to Base Station".

Speech calls are made on all the TRXs. All calls are successful 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.

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.

MML command ‘ZERO’ is used to verify the TSC values for the TRXs at the BSC.

The reconfigured BCCH TRX should contain the TSC same as BCC. The faulty TRX should have the TSC other than BCC.

Speech calls are made on all the TRXs. All calls are successful Using MML command ZDTC at BSC, the preferred BCCH TRX signalling link is unblocked.

The preferred BCCH TRX returns to the working state and it is reconfigured as the BCCH TRX.

The command ‘ZERO’ is used to verify the TSC values for the TRXs at the BSC

The reconfigured BCCH TRX should have the TSC same as BCC. The non-BCCH TRXs should have the TSC other than BCC.

Speech calls are made on all TRXs at least twice. Calls on all TRXs are successful Speech calls are made on all the timeslots of the TRX used for reconfiguration. The A-bis TRX signalling links are followed during the calls.

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.

Case Ref. BCF Configuration TRX used for reconfiguration

1 4 Omni GSM/EDGE with GSM TRX as Master TRX. Non BCCH TRXs should have different TSC than BCC.

TRX used for reconfiguration is TRX 2. And master TRX is set as the preferred BCCH TRX


7.4 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.

Note 32.

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 33.

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.

Note 34.

For test case 1 the BTS ID and BTS object ID are checked at the BTS Manager before/after BTS lock & unlock is performed

Input Expected OutputNeighbour cells are defined in the same and other BCF. Speech calls are made via every TRX.

All calls are successful

For test case 2 Idle channel interference is checked for all the TRXs both at BSC using ZEEI command and in RF Resource indication message on A-bis interface.

Zero interference level will be shown at BSC and value 1 for all the idle timeslots of the TRXs at Abis interface.

The BTS is locked from BSC using ‘ZEQS’ command and forced handover parameter (FHO) is also used. BCCH-transmission is checked with the spectrum analyser.

Calls are handed over from the locked BTS. BCCH transmission shall be stopped.

The BTS is unlocked from BSC using ‘ZEQS’ command. Abis is monitored.

Alarm 7767 BCCH MISSING shall get activated till 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.

For test case 2, the Idle channel interference is checked for all the TRXs both in BSC using ZEEI command and in RF Resource indication message on A-bis interface.



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 shall not get blocked.

The Reset command is given for a TRX in the blocked BTS.

The TRX will get reset.


Input Expected OutputThe Unblock command is selected for the sector. The BTS becomes operational. The 7208 alarm

shall get cancelled. BCCH will start transmitting.

Alarms are checked. There are no active alarms except for "7801: MMI connected to Base Station".

For test case 2, the Idle channel interference is checked for all the TRXs both in BSC using ZEEI command and in RF Resource indication message on A-bis interface.


Speech calls are made using the BTS. All calls are successful

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

Action successfully performed.

Check the checkbox next to Events Log option. The popup address window saves the log to a specific address.

The Events log file can be defined and is correctly shown in the status bar of the Event window.

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 except for "7801: MMI connected to Base Station".

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.


All above test steps are executed for all the BTS if exist.

Operation successfully performed.

Case Ref.

Configuration TRXSIG and TCH Signalling

BTS Block from BTS Manager

Hopping mode

1 3 Cabinets Chain 4+4+4, GSM+EDGE+GSM/EDGE with STIRC enable in sector 2

Separate Logical Objects View, Sector pop-up menu

BB

2 4 Omni, EDGE Compressed Objects | Properties RF


7.5 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 OutputSpeech calls are made using every BTS in the BCF.


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.

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 BCCH and non BCCH 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 2-30 are tested.

The power level is according to the PMAX value set.

Case Ref.

Configuration O&M and TRXSIG Hopping Mode

1 (2+2+2) 3 cabinet chain with STIRC enabled.

Combined RF Hopping+BB hopping+None


Purpose:

The purpose of this test case is to check that calls are possible on all the working TRXs in the sector after BCF lock/unlock in fault condition.

Input Expected OutputSite is configured as per the test case. Site is in supervisory state with no active


Calls are made on all TRXs. All calls are successful TRX2 and TRX4 are removed from the cabinet. Alarm 7606 "TRX FAULTY: Master TRX

detected that connection to Slave TRX is lost " and alarm 7705 ”LAPD failure” shall get reported on BTS manager and BSC for TRX 2 and TRX 4. Site reconfiguration shall takes place and site comes up with the working TRXs.

Calls are made on both the sectors. All calls are successful BCF is locked from the BSC using the MML command ZEFS: <BCF_NO>: L;

BCF gets locked.

BCF is unlocked from the BSC using MML command ZEFS: <BCF_NO>: U;

BCF gets unlocked and site comes to supervisory state. After sometime alarm 7606 "TRX FAULTY: Master TRX detected that connection to Slave TRX is lost" and alarm 7705”LAPD failure” shall get reported on BTS manager and BSC for TRX 2 and TRX 4.

Calls are made on all the working TRXs All calls are successful Case Ref. Configuration BCCH TRX Hopping

2. 2+2 GSM/EDGE, Master BB, both sectors

Input Expected OutputSite is configured as per the test case. Site is in supervisory state with no active


Calls are made on all TRXs. All calls are successful Non-BCCH TRX of the first sector is removed from the cabinet.

Alarm 7606 "TRX FAULTY: Master TRX detected that connection to Slave TRX is lost" and alarm 7705”LAPD failure” shall get reported on BTS manager and BSC for pulled out TRX. Sector reconfiguration shall takes place and sector comes up with the working TRX.

Calls are made in the sector. All calls are successful


Input Expected OutputBCF is reset from BTS Manager.

BCF gets reset and site comes to supervisory state. After sometime alarm 7606 "TRX FAULTY: Master TRX detected that connection to Slave TRX is lost” and alarm 7705”LAPD failure” shall get reported on BTS manager and BSC for pulled out TRX.

Calls are made on all the working TRXs. All calls are successful Non-BCCH TRX of the second sector is removed from the cabinet.

Alarm 7606 "TRX FAULTY: Master TRX detected that connection to Slave TRX is lost” and alarm 7705”LAPD failure” shall get reported on BTS manager and BSC for pulled out TRX. Sector reconfiguration shall takes place and sector comes up with the working TRX.

Calls are made in the sector All calls are successful Second BTS is locked from the BSC using MML command ZEQS:BTS = <BTS_NO>: L;

BTS gets locked.

Second BTS is unlocked from the BSC using MML command ZEQS:BTS = <BTS_NO>: U;

BTS gets unlocked and sector comes to supervisory state. After sometime alarm 7606 "TRX FAULTY: Master TRX detected that connection to Slave TRX is lost” and alarm 7705”LAPD failure” shall get reported on BTS manager and BSC for pulled out TRX.

Calls are made on all the working TRXs. All calls are successful Case Ref. Configuration BCCH TRX Hopping

3. 2+2, EDGE Master BB


7.6 BCF Reset

Purpose:

The purpose of this test is to verify that the site can be reset from the BSC and BTS Manager.

Input Expected OutputSpeech calls are made via every TRX. All calls are successful

Idle channel interference is checked for all the TRXs both at BSC using ZEEI command and in RF Resource indication message on A-bis interface.


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

The BCF shall get reset. Calls will be released. BCCH transmission shall get stopped. Notice 7701 BCF INITIALISATION shall be sent during site initialisation. The BCF shall return to the WO state along with all of the BTSs and TRXs under the BCF.




BCF is reset from BTS manager with specified option in the test case.

BCF shall get reset. Calls will be released. BCCH transmission shall get stopped. Notice 7701 BCF INITIALISATION shall be sent during site initialisation. The BCF shall return to the WO state along with all of the BTSs and TRXs under the BCF.




Case Ref.

Configuration O&M and TRXSIG

Hopping mode

Reset BCF from BTS Manager

1 3 cabinet chain configuration, EDGE

Combined BB Hopping in any of one sector

From Objects | Properties


7.7 TRX Reset

Purpose:

The purpose of this test is to verify that the BTS faulty alarm is re-raised following a reset if the fault condition remains.

Input Expected OutputSite is configured as per the test case. The site is in supervisory state with no active


Antenna connection fault is generated for TRX 1TRX test is run on TRX1 from the BTS Manager.

The TRX test will fail with alarm 7606 TRX FAULTY “TRX test result antenna connection faulty” for TRX1.

TRX 2 is removed from the cabinet Alarm 7603 BTS FAULTY “Master TRX detected that connection to slave TRX is lost, shall get reported for sector 1.

Antenna connection fault is generated for TRX 3 Alarm 7603 BTS FAULTY “Antenna connection fault” shall be raised for sector 2

Antenna connection fault is generated for TRX 4 Alarm 7600 BCF FAULTY “Antenna connection is faulty” shall be reported for the BCF

Antenna connection for TRX3 is restored and TRX3 is reset.

Alarm 7600 BCF FAULTY shall get cancelled. Alarm 7603 BTS FAULTY for sector 2 shall also get cancelled The BCF will return to a working state and alarm 7606 “master TRX detected that connection to slave TRX is lost” shall be observed for TRX 1, 2 & 4 on BSC and BTS Manager. Alarm 7603 BTS FAULTY “Antenna connection faulty” shall be reported for sector 3 and sector 1.

TRX 2 is locked from the BSC .TRX 2 is installed in the cabinet and is unlocked from the BSC. Antenna connections for TRX 1 and TRX 4 are restored and site is reset.

There are no active alarms reported at both BSC and BTS Manager except for alarm "7801: MMI connected to Base Station".

Calls are made on working TRXs. All calls are successfu Case Ref. Configuration

1 2+1+1


8. RECOVERY FOR BSS AND SITE SYNCHRONISATION

8.1 Site Synchronisation Recovery during start-up/resets

Purpose:

The purpose of these test cases is to check that the Base Station initialises to the correct synchronisation mode.

Note 35.

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 Expected OutputSynchronization chain is defined in the BSC using the MML command: ZEFM:<s1>:CS=LMU,SENA=T, ; <s1> = slave 1 BCF number Traffic channels are made as full rate channels (TCHF). All TCH channels are locked except timeslot 2 on each TRX in the multi-BCF segment. Site is physically created and commissioned.

The site is successfully commissioned.

BTS Events window in BTS Manager is monitored. Slave BCF(s) are reset using the MML command: ZEFR:<BCF No>; Abis interface is monitored.

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 the test case 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 success-failure = 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.

8 MSs are locked to the segment. 4 pairs of speech calls are made. Speak in both directions for each call.

All calls are successful. The speech in each direction can be heard clearly.


Input Expected OutputThe process is repeated 5 times for consistency. For test case 4 the steps 1 to 3 are repeated 10 times.

The site’s behaviour is repeatable.

Case Ref.

Configuration Sync Mode in BTS_OMU_STARTED

1 LMU+4+4+4 chain, RF Hopping in all BTS Figure 1. LMUB SW1.0

Independent

2 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

Independent

3 LMU+Talk+4+4 chain, RF Hopping in both BTS Figure 3 LMU SW 4.4 with Talk DF7 Master, Use boundary value (lowest) for Q1 Address (LMU) i.e 0

Independent

4 LMU+4+4+4 chain, RF Hopping in all BTS Figure 1, LMU SW – 4.4

Independent

8.2 Site Synchronisation recovery with GPS signal recovery

Purpose: The purpose of these test cases is to check that a previously synchronised chain behaves correctly when the LMU’s GPS signal is lost and when returns and to check that the recovery actions are not triggered if the GPS outage is less time than the LMU timer period.and 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 36.

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 LMU’s 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 37.

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.

Test tools required: Q1 bus monitoring tool


Input Expected OutputMake the traffic channels full rate channels (TCHF). Lock all TCH channels except timeslot 2 on each TRX in the multi-BCF segment. 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 get 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.

All the full rate TCH channels of all the TRXs except timeslot 2 are locked. Timeslot 7 of TRX 4 of each BTS in the segment is made dedicated GP timeslot. Neighbour BTS is successfully defined.

Physically create and commission the sites, so that they are in working order, synchronised to the LMU.

BCF gets reset and it sends a BTS_OMU STARTED message with synchronisation mode = slave, regardless of the setting in HW configuration file.

Lock 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. Also establish a further 2 MS, each with a GPRS transfer ongoing.

All calls set up correctly. The speech in each direction is being heard clearly.

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 antenna’s 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. Alarm 8048:”Loss of incoming signal” is reported both at the BTS Manager and BSC. . However, the LMU does not send a 1001 clock disable alarm. The BCFs continue to be synchronised by the clock signal from the LMU.


Input Expected OutputCheck 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;

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.

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

The LMU sends an alarm 48 cancel on the Q1 bus. Alarm 4048:”Loss of incoming signal” is cancelled both at the BTS Manager and BSC. 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.

At 4 minutes monitor the Q1 bus. 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 antenna’s 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. Alarm 8048:”Loss of incoming signal” is reported both at the BTS Manager and BSC. . 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. Check the sync status at BTS Manager / MMI. Check the sync status at the BSC using the MML command: ZEFL;

All calls remain up. BCFs still show as being in slave mode. Sync Enabled = T, Sync Mode = Synch for the synchronisation chain.

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

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.

Check the status of the BCFs using MML command: ZEEI:BCF = <BCF number>;

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


Input Expected OutputMonitor the MMI and Abis for all of the BCF. 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.

Check the MS carrying the GPRS transfers. The MS reselect the BTS in the segment again. Check the sync status at the BSC for all BCF, using the MML command: ZEFL;

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

Check for alarm 8048 GPS fix lost alarm at BSC using MML command: ZEOL:< Slave BCF number>;

8048 alarm is still active.

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

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

Monitor the Q1 bus and the Abis. Re-establish the GPS signal to the LMU.

The LMU sends an alarm 48 cancel on the Q1 bus. Alarm 4048:”Loss of incoming signal” is cancelled both at the BTS Manager and BSC. All calls hand over successfully to the neighbouring BTS. The GPRS transfers reselect the neighbouring BTS.

Check the status of the BCF using MML command: ZEEI:BCF=<BCF number>;

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

Monitor the MMI and Abis for all of the BCF. The BSC resets the first BCF in the chain. 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. The MS reselect the BTS in the segment again. Check the sync status at the BSC for all BCF, using the MML command: ZEFL;

Sync Enabled = T, Sync Mode = Sync for all BCF in the chain.

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

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

Case Ref.

Configuration. TRE address

1 LMU+4+4 in a segment, LMU SW –4.4 5

2 LMU+4+4 in a segment, LMU SW –4.4 7


9. BTS MANAGER FUNCTIONALITY

9.1 BTS Manual Commissioning

Purpose:

The purpose of this test is to check that a BTS can be manually commissioned with the BTS Commissioning Wizard.

Extra HW/Tools: Metrohopper

Input Expected OutputFollowing steps are grouped as ‘A’

The BTS is not commissioned. BTS is in uncommissioned state.

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

The D–channels are not in WO–EX 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.

Operation Successful

The Radio Hops command is selected. The Flexibus Settings page is opened. The indoor unit type is shown correctly (FXC RRI). Flexbus1 and Flexibus 2 unit are shown correctly.


Input Expected OutputFor 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.

Operation Successful.

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 Setting’s 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.

The Next button is selected. The test continues from sequence F.

Following steps are grouped as ‘F’


Input Expected OutputThe 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 functionality of in-use EAC inputs is verified, they are marked as 'checked'.

When the EAC input changes this is reflected on EAC Input Settings page. 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 functionality of all in-use EAC outputs are verified they are marked as "checked".

When the state of EAC output is changed it is reflected on EAC output. The EAC output can be marked as 'checked' when they are marked as 'in-use'.

The Next command is selected. The BTS Commissioning Report page is opened.


Input Expected OutputThe 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 [Error! Reference source not found.] carried out. All BTS logical objects (BCF, BTS, and TRX) are in state WO in the BSC. The D–channels are in state WO–EX in the BSC.

Case Ref.

Transmission Unit Transmission SW

Sequence to be Followed

Operating System

1 FXC RRI ITN C3 CD3 with MetroHoppers in both flexibus interfaces with C3.1 and C4.0 SW

ITN C3 CD1 A, B, C, D, E, F

Windows XP


9.2 BTS Manual Commissioning with FXC RRI

Purpose:

The purpose of these tests 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, Flexihopper

Input Expected OutputThe BTS is not commissioned. BTS is in uncommissioned state

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

The D–channels are not in WO–EX 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. Operation Successful

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 value of <n> in the title of the page depends which flexbus interface is under commissioning.

The correct TX Frequency and Maximum TX and the TX Power On are given.


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


Input Expected OutputThe 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 functionality of in-use EAC inputs is verified, they are marked as 'checked'.

When the EAC input changes this is reflected on EAC Input Settings page. 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 functionality of all in-use EAC outputs are verified they are marked as "checked".

When the state of EAC output is changed it is reflected on EAC output. The EAC output can be marked as 'checked' when they are marked as 'in-use'.

The Next command is selected. The BTS Commissioning Report page is opened.


Input Expected OutputThe 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 D–channels are in state WO–EX in the BSC.

Case Ref.

Transmission Configuration

1 FXC RRI with FlexiHoppers FHP2.7 and Flexihopper Plus FHP2.7.1, FXC RRI SW ITN C3 CD2, MetroHub SW C3 CD2

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

3 FXC RRI with FlexiHoppers FH3.3.4 in both flexbus interfaces, FXC RRI SW ITN C3 CD3, MetroHub SW C3 CD3


9.3 BTS Manager Start-Up

Purpose:

The purpose of these test cases is to check that the BTS Manager can be successfully started.

Precondition:

1. The PC has SiteWizard of previous main release installed.

2. Using SiteWizard of new release, BTS Manager is installed to the PC.

Input Expected OutputThe BTS Manager version 7.0 is started. Version is checked from Help | About BTS Manager command.

The BTS Manager starts successfully. Version is correct. Alarm 7801 MMI CONNECTED TO BASE STATION is reported to BSC and BTS Manager.

The LMP cable between the PC and the BCF is removed.

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 BASE STATION is cancelled at the BSC.

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 reported to BSC and BTS Manager.

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 reported to BSC and BTS Manager.

BTS manager is disconnected via Connection’ -> disconnect menu item

BTS Manager is disconnected successfully. Alarm 7801 MMI CONNECTED TO BASE STATION is cancelled at the BSC.

Case Ref. Configuration Operating System in PC

1 Multi TRX, EDGE/GSM Windows Vista

2 Multi TRX, EDGE/GSM Windows XP

3 4+4 1 Windows XP 1 Connection to BTS Manager is done using serial to USB converter (any brand)


9.4 FC E1/T1 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 or FXC E1/T1 transmission card is installed to the BTS.

Input Expected OutputThe site is configured as per the test case. The site is in supervisory state with no active


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 doesn’t 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 active alarms reported at both BSC and BTS Manager except for alarm "7801: MMI connected to Base Station".

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 with no active alarms reported at both BSC and BTS Manager except for alarm "7801: MMI connected to Base Station".


No alarm is shown in the alarm window.

Case Ref.

Configuration Transmission Unit Transmission SW

1 Any FC E1/T1 ITN C1.0 Pre condition: The BTS is in un-commissioned state.


Input Expected OutputThe correct LIF Settings and Synchronisation values are given.

Step is executed successfully

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.

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.

Alarm 8179:” FAR-END ALARM” will get raised.


Alarm 8179 is shown for correct location.

The LIF Settings command is selected and CRC set to be in use.

Alarm 8179:” FAR-END ALARM” gets cancelled.


Alarm 8179 is 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 as 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.

Alarm 8112 will get raised after some time.

The Synchronisation command is selected and the used interface is selected as the interface for synchronisation.

Alarm 8112 will no longer appear.

The test is repeated for all interfaces. This requires the Synchronisation, LIF, and Traffic Manager settings to be redefined and the BCF to get reset.

Case Ref.

Configuration Transmission Card Transmission SW

2 Any FXC E1/T1 ITN C3.0


9.5 Logical Objects view window handling

Purpose:

The purpose of this test case is to check that Logical Objects view window does not re-appear (while the Logical Objects view button and its menu item is unselected) after unselecting the Supervision-Equipment view in maximized state.

Input Expected OutputSite is configured as per the test case. The site is in supervisory state with no active

alarms reported at both BSC and BTS Manager.

BTS Manager is connected. BTS Manager is connected successfully. Alarm. "7801: MMI connected to Base Station" is raised both at BSC and BTS Manager.

Logical Objects view is enabled and set to maximized state.

Logical Objects view gets enabled and is maximized.

Logical Objects view window is closed. Logical view button is disabled. Logical Objects view option is disabled in menu commands too.

Supervision-Equipment view window is maximized. Supervision Equipment view gets maximized.Supervision-Equipment view window is closed. Supervision-Equipment view disappears.

Logical Objects view does not re-appear and Logical Objects view button on toolbar is disabled.

Logical Objects view is enabled from the menu Logical Objects view gets enabled Supervision-Equipment view is enabled from the menu and set to maximized state.

Supervision-Equipment view gets enabled and is maximized.

Supervision-Equipment view window is closed. Supervision-Equipment button is disabled. Supervision-Equipment view option is disabled in menu commands too.

Logical Objects view window is maximized. Logical Objects view gets maximized. Logical Objects view window is closed. Logical Objects view disappears.

Supervision-Equipment view does not re-appear and Supervision-Equipment view button on toolbar is disabled.

Repeat the test case 10 times. Also repeat the test case 10 times from toolbar button.

Output is same as observed in the above steps.

Case Ref. Configuration Connection type

1. Any Remote


9.6 File Menu Commands

Purpose:

The Purpose of this test case is to verify that option, save as, Print and Exit commands in the File menu of the BTS manager work correctly.

Input Expected OutputThe Equipment view is activated and the Save As command is selected from the File menu. This is repeated for Logical Objects view.

The Save As command cannot be selected for Equipment View and Logical object view.

The Print command is selected from the File menu. This is repeated for Logical Objects view.

The Print command cannot be selected for Equipment View and logical object view.

The BTS Events window is activated. BTS Events window is successfully activated.

The Save As/BTS Events command is selected from the File menu. This is repeated with the Save As/BTS Events command button in the active window.

The standard Save As dialog is shown; this saves the data in the active window to the specified file.

The Print/BTS Events command is selected from the File menu. Print to various printers. This is repeated with the Print Events command icon in the active window.

The standard print dialog is shown; this prints the active window to the printer. The printing works correctly for different types of printers.

The case is repeated for Alarms window (commands are then: Save As and Print).

The Exit command is selected from the File menu.

The BTS Manager is terminated.

The alarm 7801, MMI CONNECTED TO BASE STATION is cancelled at the BSC.

Case Ref.

Configuration Operating System in PC

1. Any Configuration1 Windows Vista 1 Also verify all the commands of commissioning dropdown menu and SW dropdown menu.


9.7 Objects Menu Commands

Purpose:

The purpose of this test case is to verify that the enabling and disabling of Abis works correctly.

Input Expected OutputBTS Manager 7.0 in installed on the PC for the first time. BTS Manager is started.

The BTS Manager is connected locally. Alarm. "7801: MMI connected to Base Station" is raised both at BSC and BTS Manager.

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 start-up.

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.

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.


Input Expected OutputBTS 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 Operating System in PC

1. Any1 FXC E1 (with release ITN C3.0) Window Vista 1 Also verify all the commands of commissioning dropdown menu and Windows dropdown menu.

Figure 1.

BCCH

3 4

1 6

7 8

5

BTS2 BTS1

LMU

MASTER

SLAVE BCF1

SEGMENT

BTS3

9 10

12 11

LMU – MetroSite - MetroSite - MetroSite

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

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

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


Figure 2.

BCCH

3 4

1 6

7 8

5

BTS2 BTS1

LMU

MASTER

SLAVE BCF1

SEGMENT

LMU – MetroSite - MetroSite




Figure 3.

BCCH

3 4

1 6

7 8

5

BTS2 BTS1

LMU MASTER

SLAVE BCF1

SEGMENT

BCCH

2

4 3



LMU –Talk - MetroSite - MetroSite


Disclaimer

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation 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 documentation 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 documentation 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 and finally 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 this documentation as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY 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 documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The 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 2009. All rights reserved.


cxm7 functional regression specification

Documents

bts commissioning

bts manager

bts tests

bts sw download

trx loop test

abis loop test

software requirements

software download