cxm7 system regression specification

7/28/2019 CXM7 System Regression Specification

http://slidepdf.com/reader/full/cxm7-system-regression-specification 1/54

Sys tem Ver i f i c a t i on Regress i onTes t Spec i f i c a t i on

Release Delivery: CXM7Product Family: GSM/EDGE Base StationsProduct: MetroSite EDGE Base StationRelease: CXM7

©Nokia Siemens Networks Company Confidential 1 (51)

MENU



1. PURPOSE

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

In general, the features and test cases described herein are intended for 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 thenstructured in the following way:

• Common aspects of test execution and configurations for all the features orfunctional 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 tothe 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 CXM7, CXM7BTS SW to be used and GCS version to be used is R6.0 unless otherwise specified.

Note 2.

This document contains the test cases for the impacted regression functionality of theMetroSite EDGE BTS due to the new features of CXM7.

Note 3.

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

Note 4.

At the BSC, Base Transceiver Stations (Sites) are seen as BCFs. Sectors are referredto as BTS. This principle is followed in the test descriptions in this document.

Note 5.

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

DN06103498 Issue 2-0


MENU



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 isdefined 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 had to be configured withthe same band TRXs.

Note 10.

Maximum number of MetroSite cabinets combined.

Chain Master TRX must be the HVTx/CTxA located in position 1 at the first cabinet inline called the Master cabinet. Cabinet Master TRXs are the HVTx/CTxA located inposition 1 (logical TRX #5 and 9) at the second and third cabinets in line called Slavecabinets.

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

DN06103498 Issue 2-0


MENU



Note 11.

A invalid BB Hopping configuration exists in a sector having TRXs of different powertypes in the same hopping group, i.e. GSM/EDGE HVTx (5W) + CTxA (10W) in thesame BTS

Note 12.

All test cases must be performed with RX diversity enabled at the BSC unlessotherwise stated.

Note 13.

EGPRS and CS 3&4 in GPRS cannot be used without Dynamic Abis being configured.

Note 14.

A TRX test can be configured to test one or more radio time slots that are configured forGPRS. If started, such a test will be allowed to proceed by the BTS SW, and this islikely 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 should not beselected for TRX test.

Note 15.

During the installation and commissioning of Sites, help provided by ‘Help Menu’commands in BTS Manager should be used.

Note 16.

It should be made a testing practice to use help provided in BTS manager from HelpMenu or using help button (F1).

Note 17.

TRXs need to be set to PMAX of 0dB or 2 dB in order to generate the ‘Antennaconnection faulty’ alarm.

Note 18.

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

Note 19.

Test cases with chaining sites are to be performed with setup having VIFA version 205or later.

3.1 Prerequisites

Before the release testing can begin, there must not be any open fatal or major faultsfound from the ongoing SW integration testing phases.

3.2 Hardware Requirements

Base Stations

DN06103498 Issue 2-0


MENU



One of the following BTS configurations will be used for the test cases covered in thisdocument.

• 2+2 GSM/EDGE

• 2+2 EDGE

• 2+2 GSM

• Omni GSM/EDGE

• Omni EDGE

• Multi TRX EDGE

• Multi TRX GSM

•

2+2 GSM+EDGE• 1+1+1+1

• 2 GSM

• 1 TRX

• Omni GSM

• Multi TRX GSM/EDGE

• 4+4+4 EDGE Chained Configuration

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

• 4+4+4 GSM Chained Configuration

• LMU-MetroSite-MetroSite

• Talk-MetroSite-MetroSite

Other Network Elements

BSC

Core Network with GPRS and EDGE capabilities.

DN06103498 Issue 2-0


MENU



Mobile Stations

Table 1: GSM Mobile HandsetsFeature Specific options

Speech channels FR, HR, EFR

Single data channels 9600, 14400 Non-Transparent

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

GPRS Class B & Class C, Multislot

EGPRS Class B & Class C, Multislot

Adaptive Multi-Rate AMR FR and HR

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

EnhancedMeasurement Reports EMR Capable

3.3 Software Requirements

- SiteWizard7.0

- Latest available Test Packet or Pre-Release of CXM7

- GCS R6.0

- BTS Manager PC (running Windows XP or Windows Vista), Win2003 nodemanager server.

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

Table 2: SW Versions of Other Network Elements

Network Element SW Version

BSC S13, S14

HLR M14.1

MSC M14.1

NSN NetAct OSS4.2 CD Set 1, OSS5.1 CD Set 1

LMU LMU 4.4, LMUB 1.0 CD3

SGSN SG7 Transmission (ITN) ITN C1.0, ITN C2.1-2, ITN C2.2, ITN C3.0,

ITN C3.0 CD1, ITN C3.0 CD2, ITN C3.0CD3

BTS Manager PC Windows XP, Windows 2003 Server,Windows Vista

PC Applications

- Internet browser

- FTP, UDP software

- Terminal Emulator

DN06103498 Issue 2-0


MENU



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

- IR/LA Rig

- Assortment of combiners

- Attenuators

- Terminators

- Signal generator

- Spectrum analyser

- GSM Protocol Analyser

- Data Channel Simulator

- D-Bus Analyser

- Q1 Monitor/NEE

- Abis Breaker

DN06103498 Issue 2-0


MENU



4. OBJECT CONTROL AND RADIO NETWORK MANAGEMENT

4.1 Common BCCH on Chained MetroSite Conf iguration

Purpose:

The purpose is to check that a chained MetroSite Base Station can be configured withsegments and brought into working order. To check that Site reset, BTS lock/unlock &auto-reconfiguration operates correctly.

Test Tool: Spectrum analyser

Input Expected Output

Create the chained configuration as specified inthe test case at the BSC. Use the TRX type asspecified in the test case.Physically create the Base Station. Commissionthe Site.

Commissioning successful.

Check the status at the BSC using MMLcommand:ZEEI: BCF=<bcf number>;Unlock TRX, BTS and BCF if they are locked

The BCF, BTS and TRX are all in WO state.

Check for alarms at the BSC using MML

command:ZEOL: <bcf number>;

There are no unwanted alarms except for ‘7801:

MMI connected to Base Station’.

A call is established on each TRX and speech ismaintained

All calls are successful. Abis links for respective TRX should show measurements correspondingto a call with good quality

Reset the Site using MML command:ZEFR:<bcf number>;Check for alarms at the BSC using MMLcommand:ZEOL:<bcf number>;

The Site resets.Alarm 7767 ‘BCCH MISSING’ is reported at BSC.

Check the status at the BSC using MMLcommand:ZEEI:BCF=<bcf number>;

The BCF, BTS and TRX are all in WO state.

Check for alarms at the BSC using MMLcommand:ZEOL:<bcf number>;

There are no active alarms reported at BSCexcept for ‘Alarm 7801: MMI connected to BaseStation’..

Lock BTS 1 using MML command:ZEQS:BTS=<bts number>:L;

BTS1 is locked.

Check the status of the LEDs on the front of the TRX units.

The LEDs of the locked TRXs show amber.


The BTS 2 and 3 are Unlocked. BTS 1 is Locked.

Make speech calls as before. All calls are successful and assigned to TRXs inBTS 2 and 3.

Unlock BTS 1 using MML command:ZEQS:BTS=<bts number>:U; BTS 1 resets.

DN06103498 Issue 2-0


MENU





All objects are Unlocked and in WO state.

Lock BTS 3 using MML command:ZEQS:BTS=<bts number>:L;

BTS3 is locked




The BTS 1 and 2 are Unlocked. BTS 3 is Locked.

Make speech calls as before. All calls are successful and assigned to TRXs inBTS 1 and 2.

Unlock BTS 3 using MML command:ZEQS:BTS=<bts number>:U;

BTS 3 resets.



Lock the BCCH BTS using MML command:ZEQS:BTS=<bts number>:L;

The BCCH BTS is Locked.




The BCCH BTS is Locked. The non-BCCH BTSsare Unlocked.

Check the status of BCCH transmission usingSpectrum Analyser.

There is no BCCH transmission present.

Unlock the BCCH BTS using MML command:ZEQS:BTS=<bts number>:U;

The BCCH BTS resets.



Make speech calls as before. Calls are assigned to TRX in all BTS. All calls aresuccessful

Monitor the Base Station using BTS Manager.Check the status of BCCH transmission usingSpectrum Analyser.

Use BTS Manager to block the BTS 2. The BCCH transmission is no longer present.Unblock the BTS 2 BTS 2 is unblocked successfully.Check the status of BCCH transmission usingSpectrum Analyser.

The BCCH transmission has been restored.


All TRX are in WO except the original BCCH TRXthat was blocked.

A call is established on each TRX. All calls are successful. Abis links for respective TRX should show measurements correspondingto a call with good quality

DN06103498 Issue 2-0


MENU




Case Ref. TRXType

BTS 1 BTS 2 BTS 3 STIRC

1WTxx 1900

2 TRX, Non-Hopping

8006TRX, BBHopping,BCCH BTS,BCCH TRX –Slave TRX

19002 TRX, RF Hopping

ON

2CTxx 1800

2 TRX, Non-Hopping

9006TRX, BBHopping,BCCH BTS,BCCH TRX –

Slave TRX


ON

3HVTx 1800

2 TRX, Non-Hopping

9006TRX, BBHopping,BCCH BTS,BCCH TRX –Slave TRX


OFF

4.2 Recovery After Power Breakdown - Chained MetroSite Conf iguration

Purpose:

The purpose of these tests is to verify that the BCF starts up automatically after a powerbreakdown.


BCF is Operational. There are no active alarms except for ‘7801: MMIconnected to Base Station’.

Calls are made on the all cabinets in the chain. Calls are successfulSecond Slave cabinet is powered OFF. The power shut down has no impact on other

cabinets in chain. Calls remain on going in theother cabinets while this Slave cabinet is powered

OFF. Alarms 7606 ‘TRX Faulty’ is reported to theBSC and the BTS Manager for all except 1 TRXin a BTS and for the last TRX the alarm getstranslated to 7603 ‘BTS Faulty’ alarm and isreported at the BTS manager and the BSC.

First Slave cabinet is powered OFF. The power shut down has no impact on Mastercabinet. Calls remain on going in the Mastercabinet while this Slave cabinet is powered OFF.Alarms 7606 ‘TRX Faulty’ is reported to the BSCand the BTS Manager for all except 1 TRX in aBTS and for the last TRX the alarm getstranslated to 7603 ‘BTS Faulty’ alarm which isreported at the BTS manager and the BSC..

Master cabinet is powered OFF Alarm 7706 ‘BTS O&M LINK FAILURE’, 7704‘PCM FAILURE’ is reported to the BSC.

DN06103498 Issue 2-0


MENU




The Master cabinet in the chain is powered ON. The Master TRX of the master cabinet performsclock synchronization and returns to operationalstate.

First Slave cabinet is powered ON. The Master TRX of the First Slave cabinetperforms synchronization by the Chain Master TRX and returns to operational state.

Second Slave cabinet is powered ON. The Master TRX of Second Slave automaticallydetects Slave TRXs and performssynchronization. All cabinets return to operationalstate.

Calls are made on each BTS. Calls are successful. There are no active alarmsexcept for ‘7801: MMI connected to Base Station’.

Case Ref. Configuration Power Supply unit

1 Chain configuration with 3 MetroSites, Multi TRX EDGE/GSM+EDGE+GSM,RF Hopping+BB Hopping+DFCA

CVSx+CVSx+HVSx


Configure the site as per test case configuration. Site is in supervisory state. There are noactive alarms except for ‘7801: MMI connectedto Base Station’.

Switch off power supply of slave and mastercabinets respectively.

Restore power for Master cabinet only.

After around 6-7 mins, power on the slave cabinets.

The site is shutdown.

Master cabinet is in supervisory state. Thiswould take around 6-7 mins.Slave cabinets returned to operational state.

Switch off power supply of slave and mastercabinets respectively.

Restore power supply of master and slave cabinetsrespectively

The site is shutdown.

Site comes up in supervisory state afterrestoring power. There are no active alarmsexcept for ‘7801: MMI connected to BaseStation’.

Make calls on all sectors Calls are successfulRepeat Step 2 for ten times. The site is shutdown. On powering on of

master, it comes up successfully. This would

take around 6-7 mins.Slave cabinets returned to operational state. There are no active alarms except for ‘7801:MMI connected to Base Station’.

Case Ref. BCF Configuration

2 4+4+4 (800+1900+1900) EDGE+GSM+GSM/EDGE

DN06103498 Issue 2-0


MENU



4.3 BSS Restart

Purpose:

The purpose of the test is to verify that the BCF starts up automatically after a BSSrestart.


The BSS is restarted with the MML command‘ZUSS: SYM:C=DSK’ .

All BCFs start up automatically after the BSSrestart.

Check the status of BCFs All BCFs are in supervisory state.Alarms are checked and calls are made via everyBCF.

There are no active alarms except for ‘7801: MMIconnected to Base Station’. All calls are

successfulCase Ref. Configuration

1Various configurations including at least 3 cabinet chain configurations (Multi TRXGSM, 2+2 EDGE with Dynamic Abis, 2 EDGE+2GSM, EGPRS are defined) and atleast one UltraSite.

4.4 Backup of System Data

Purpose:

The purpose of the test is to verify that the system data is transferred from the Master TRX to the Slave TRXs. The D-bus is monitored during the test.

Test Tool: D-Bus analyser


The BCF is in operational state and Master TRXis set as Preferred BCCH TRX.

Site is in supervisory state.

The Master TRX is removed from slot 1. When the Master TRX is removed, alarm 7767‘BCCH MISSING’ and 7705 ‘LAPD FAILURE’alarms for TRXs and 7706 ‘BTS O&M LINK FALURE’ are active. Reconfiguration cannot take

place because the O&M link is not in workingstate.

TRX1 is locked. Slave TRX is removed from slot2 and installed into slot 1.TRX1 is unlocked. Afterthis operation, one TRX is missing. The D-bus ismonitored. Calls are made via every TRX

Since, the Slave TRX has backup of the systemdata, there is no SW Download observed on theD-bus monitor for the installed TRX. When it isinstalled into the position of the Master TRX, itinitialises successfully and starts to operate as theMaster TRX. The BTS starts up automatically.Alarm 7606 ‘TRX FAULTY’ is active for themissing TRX. All calls are successful

TRX2 is locked. A Slave TRX from an un-commissioned BTS is installed into slot 2. TRX2is unlocked. The D-bus is monitored. Calls aremade via every TRX

The system data is sent from the new Master TRXto the new Slave TRX. The new Slave TRX isinitialised correctly and alarms are cancelled atthe BSC. All calls are successful

DN06103498 Issue 2-0


MENU




The new Master TRX from slot 1 is removed. When the Master TRX is removed, alarm 7767‘BCCH MISSING’ and 7705 ‘LAPD FAILURE’alarms for TRXs and 7706 ‘BTS O&M LINK FALURE’ are active. Reconfiguration cannot takeplace because the O&M link is not in workingstate.

TRX1 is locked. The Slave TRX is installed fromslot 2 into slot 1. TRX1 is unlocked. After thisoperation one TRX is missing. The D-bus ismonitored. Calls are made via every TRX

Since, the Slave TRX has backup of the systemdata, there is no SW Download observed on theD-bus monitor for the installed TRX. When it isinstalled into the position of the Master TRX, itinitialises successfully and starts to operate as theMaster TRX. The BTS starts up automatically.Alarm 7606 ‘TRX FAULTY’ is active for the

missing TRX. All calls are successful TRX2 is locked. The TRX that was first removedfrom slot 1 at the beginning of this procedure isinstalled into slot 2. TRX2 is unlocked. The D-busis monitored. Calls are made via every TRX

The system data from the Master TRX is sent tothe Slave TRX in slot 2. The TRX is initialisedcorrectly and alarms are cancelled at the BSC. Allcalls are successful

Case Ref. Configuration BCCH TRX

1 2 Omni, TRXs in slot 1 and 2. Master

5. ALARM HANDLING

5.1 Unit Failures: Loss of Input Power Supply

Purpose:

The purpose of these tests is to verify that unit faults are handled correctly, alarms aresent to the BSC and the BTS Manager, and that the equipment view is properlydisplayed at the BTS Manager.

Note 20.

Neighbours are defined for each BTS.

Note 21.

Alarms are checked from the BSC and from the BTS Manager after every test step. Thestate of the BCF is checked from the BSC with the MML command ZEEI.

Note 22.

MetroSite configurations stated in the test cases can be powered from the followingMetroSite power supply units:

For AC supply CVSA, CVSG, HVSA, & CVSB

For DC supply HVSD, CVSD

Note 23.

Brown Out – A condition where the voltage supplied to the system falls below the

specified operating range but above 0V.Black Out – Complete loss of power

DN06103498 Issue 2-0


MENU



Note 24.

Using the California Instruments 5001 (test equipment) the drop-out voltage of the BTSPSU is established, turning down from operational voltage to drop-out voltage. Thefollowing values provide a testing guide and estimation of the expected dropout voltagefor the MetroSite power supplies used in the test cases as specified in Note 23.

AC 240V CVSA – (160V AC dropout)AC 150-300V CVSG – (132V AC dropout)AC 240V HVSA – (141V AC dropout)AC input 83-300V AC CVSB – (76V AC dropout)DC input 48V HVSD - (24V DC dropout)DC input 24-48VDC CVSD – (26V DC dropout)


Configure the site as per test case configuration

The ‘California Instruments 5001’ Power unit isplaced in series with the input supply voltage, andMetroSite power supply unit.

Site is in supervisory state. There are no activealarms except for ‘7801: MMI connected to BaseStation’.

Activate the service terminal extension.ZDDS:OMU; 00-MAN>KM:xx; (xx=BCF)

Connect Abis monitoring between BCF and theBSC

Monitor BTS alarms.

Abis monitoring is running.

Establish power supply dropout voltage asdescribed in [Note 24], set this voltage on theCalifornia Instrument.Select appropriate duration time of interruptedmains break to achieve ‘brown out’ (approx 0.020– 0.060 seconds)Note: Ensure to set time duration so with everyinterruption a ‘brown out’ occurs.

‘Brown out’ condition is achieved, site does notreset but incoming power lost alarm 7620‘Incoming power lost’ is enabled and cancelled,observed on Abis and service terminal.Alarms are checked at BSC and alarm 7620 isnot active at BSC.

With the test conditions set above repeat the testgenerating a number of ‘brown outs ‘wait at least3 seconds between activations.

It is observed on service terminal and Abis Alarm7620 ‘Incoming power lost’ is enabled andcancelled after each activation.Alarms are checked at BSC 7620 ‘Incomingpower lost’ is not active at BSC.

Create a ‘blackout’ by removing the power input tothe MetroSite PSU (switching of output of California instrument)

Alarm 7620 ‘Incoming power lost’ alarm isobserved on service terminal and Abis.Alarm is active at BSC.

Switch power back on. MetroSite returns to working order alarm 7620‘incoming power lost’ cancels

Make a speech call

Check alarms at BSC

Call is successful

There are no active alarms except for ‘7801: MMIconnected to Base Station’.

DN06103498 Issue 2-0


MENU




Case Ref. BCF Configuration

1 4 Omni MetroSiteAny suitable AC PSU to support the TRX configuration GSM or EDGE.

5.2 LAPD Failure - BER Introduced

Purpose:

The purpose of these tests is to verify that the LAPD link failures are handled correctlyat different BER.

Note 25.

When Abis is disconnected between the BSC and BTS, alarm 7704 ‘PCM FAILURE’ israised instead of alarm 7705 ‘LAPD FAILURE’.

Note 26.

For the period of each test case the 13 MHZ clock is monitored from the clock outputlocated on the VIFA unit with the help of Frequency counter.

Test Tool: Data Channel Simulator


A Multi TRX,(16Kbits/s (TRX Signalling speed))Configuration is set-up..

Site is in supervisory state with no active alarmsreported at both BSC and BTS manager exceptfor ‘Alarm 7801: MMI connected to Base Station’.

Calls are made on every timeslot of all the TRXs. All calls are successfulAll but one call is cleared. Call is left ongoingthroughout the test case.

Operation is successful.

The BER (Bit Error Ratio) is set with the DataChannel Simulator to desired BER level. TheBER is generated in the downlink direction, thenin uplink direction and then simultaneously in both

directions. Alarms are checked both at the BSCand BTS manager.

When alarm limits are reached, alarms is raisedat the BSC and the BTS Manager. For BERgreater than 1E-3 the alarm 8099 ‘BIT ERRORRATE (BER) >1E-3 is raised.

When the BER is greater than or equal to 1E-3,call may get released.Calls are made on every timeslot of all the TRXs. All calls are successful

Case Ref. BER

1 1E-3

2 1E-31

1Use GSM HW

DN06103498 Issue 2-0


MENU



5.3 LAPD Failure - LAPD Blocked using MML Command

Purpose:

The purpose of these tests is to verify that the LAPD link failures are handled correctlywhen the LAPD link is blocked.

Note 27.

The time of the link break varies between 1 and 20 minutes in the different cases.

Note 28.

Alarms are checked at the BSC and the BTS Manager after every test step. The stateof the BCF is checked from the BSC with MML command ZEEI.

Note 29.

Neighbours are defined for the BTS.

Test Tool: Spectrum Analyser


Alarms are checked after every test step both atthe BSC and BTS Manager.

There are no active alarms reported at both BSCand BTS manager except for ‘Alarm 7801: MMI

connected to Base Station’.Calls are made via all TRXs. Calls are successful The O&M Signalling link is blocked using MMLcommand ‘ZDTC’.

Alarm 7706 BTS O&M LINK FAILURE is raised atthe BSC. All calls remain ongoing

The status of the LAPD link is requested with the LAPD Link Status command from the BTSManager.

The state of the OMUSIG link is OFF in the LinkStatus window. The state of the TRXSIG link isON in the Link Status window. The Status bar at the bottom of the Supervisionwindow indicates: "O&M disabled" and "Telecomworking".

Slave TCH TRX is removed from the cabinet.

The O&M Signalling link is unblocked from the

BSC. Alarms are checked at the BSC. The time between establishing the O&M LAPDlink and sending alarms to the BSC is checkedfrom the Abis.

Slave TCH TRX is removed from the cabinetsuccessfully.Calls will get released from the TRX. Rest of the

calls remain ongoing. The O&M Signalling link is established and alarm7706 is cancelled and alarm 7606 TRX FAULTYfor the missing TRX becomes active.If the BSC does not acknowledge the alarm, theBCF sends it again after ten seconds.

For test case 1 and 3 removed TRX is lockedfrom the BSC. For test case 2 BTS is locked fromthe BSC. TRX is reinstalled. TRX/BTS isunlocked from the BSC

For test case 2 calls are made on the working TRXs.

TRX is initialised correctly and alarm 7606 getscancelled. Existing calls remain ongoing for testcase 1& 3. For test case 2 all calls will get handedover to the neighbour BTS.

Calls are successful

DN06103498 Issue 2-0


MENU




The BCCH TRX signalling link is blocked with theMML command ‘ZDTC’. The status of the LAPDlink is requested with the LAPD Link Status command from the BTS Manager.

For test case 1, Traffic Trace at BTS Manager ismonitored during BCCH reconfiguration.

When the BCCH TRX Signalling link is blocked,alarm 7705 LAPD FAILURE is activated and the TRX is blocked from the BSC. Calls on BCCH TRX will get released.BCCH reconfiguration is performed. All calls via TCH TRX, which would be configured as BCCH TRX, are handed over before reconfigurationoccurs. The state of the OMUSIG link is ON in theLink Status window. The TRXSIG link of theblocked BCCH TRX Signalling is reported to be in'OFF' state. The state of the TRXSIG link for restof the TRXs is ON in the Link Status window. The Status bar at the bottom of the Supervision

window indicates: "O&M enabled" and "Telecompartially working" (Multiple TRX configuration).

During BCCH reconfiguration former BCCH TRX’s BCCH timeslot will go into idle state, andafter BCCH reconfiguration, newly configuredBCCH TRX’s BCCH timeslot will come into activestate.

For test case 1 BCCH TRX signalling link isblocked for the newly configured BCCH TRX andits transmission is checked at BTS manager( Tests-> Traffic Trace)

Alarm ‘7600 BCF FAULTY’ with description‘LAPD failure is raise for BCF at both BSC andBTS Manager. All calls get released. The BCCH timeslot of the TRX in traffic trace willno longer be highlighted that means it goes from

active state to idle state. TRX(s) Signalling link is(are) unblocked. TRX(s) Signalling link is(are) re-established and

the TRX(s) returns to working state as a TCH TRX. Calls remain ongoing for test case 3.For test case 2 sector shall take a rest and comeup with all TRXs as in working state.

The status of the LAPD link for the unblockedBCCH TRX Signalling is requested with the LAPDLink Status command from BTS Manager.

The states of the OMUSIG and TRXSIG links arereported correctly in the Link Status window. The TRXSIG link of the unblocked BCCH TRXSignalling is reported to be in 'On' state. The Status bar at the bottom of the Supervisionwindow indicates: "O&M enabled" and "Telecomworking".

Calls are made via free timeslots of the TRXs. All calls are successfulCase Ref. Configuration

Hopping

1 2 Omni, EDGE/GSM,Master TRX is

preferred BCCH TRXNo

2 Multi TRX EDGE/GSM BB

3 4 Omni, EDGE with STIRC enabled No

DN06103498 Issue 2-0


MENU



5.4 RSSI

Purpose: To check that RSSI measured values are not lost when Alarm 7607 iscancelled in MetroSite.

Note 30.

Ensure that number of calls is sufficient to cross the threshold number of samples(required to generate alarm). The test case is done with the value of the thresholdnumber of samples as 750,000. To achieve this threshold at least 1 call needs to beheld on each TRX for 1 hour.

Note 31.

Value of RXDL at BSC is set as 10 using MML command: ZEFM:<bcf no.>:RXDL=10;


Set up a site as per the given configuration in thetest case.

The site is in Supervisory state There are noactive alarms except for ‘7801: MMI connectedto Base Station’.

Site is reset.BTS Manager application is launched andconnected to the BTS locally.

Site comes to Supervisory state.BTS Manager starts successfully.

Calls are made via TRX under test and held. Speech calls are successfulAntenna supervisory timer expires after 1 hour.

RSSI results are checked from the BTS Manager’s‘Site Information’ and ‘RSSI comparison values’menu. Alarms are checked from the BSC and BTSManager.

Check the values in the ‘Reliable ‘ and ‘AlarmValues’ listbox.

RX antenna supervision is performed. Results

can be requested from the BTS Manager. Test TRXs reports RX RSSI value with ‘Difference’,‘Frames’ and ‘Time Stamp’ information. Alarm7607 ‘TRX OPERATION DEGRADED’ (Rxlevels differ too much between main anddiversity antennas) is reported on BSC and atthe BTS Manager for TRX1 and TRX9. Butthere will be no Alarm for TRX5 and the other TRXs in the BCF.

Values are same in both listboxes.

Terminate active voice calls. Calls terminated successfullyAttenuator is removed and Calls are made via TRX under test.

Speech calls are successful

DN06103498 Issue 2-0


MENU




Antenna supervisory timer expires after 1 hour.Results are checked from the BTS Manager’s ‘SiteInformation’ and ‘RSSI comparison values’ menu.Alarms are checked from the BSC and BTSManager.

Check the values in the ‘Reliable ‘ and ‘AlarmValues’ listbox.

RX antenna supervision is performed. Resultscan be requested from the BTS Manager. Test TRXs reports RX RSSI value with ‘Difference’,‘Frames’ and ‘Time Stamp’ information. Alarm7607 ‘TRX OPERATION DEGRADED’ (Rxlevels differ too much between main anddiversity antennas) is cancelled. No alarms arereported on BSC and at the BTS Manager.

‘Alarm Values’ listbox displays old values forfirst hour for which alarm had been raised.’Reliable’ listbox displays latest successfullymeasured values.

Case Ref. BCF Configuration Attenuation/Test TRX

1 4+4+4 MetroSite Chain. 20db (RX Main path of TRX1 & TRX9)

5db (RX Main path of TRX5)

5.5 Alarm correlation for chained MetroSite configuration

Purpose:

To check that different level of alarms reported and cancelled correctly from BTSManager and BSC.

Note 32.

The expected range of TX power levels 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, thenexpected 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 testthen the failure reason is included in the TRX test report. Revert back the PMAX valueto 30 once test case is completed.

Note 33.

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 cancelledwithin 10-seconds.

Note 34.

The Receive Diversity value should be set as RDIV=Y.

DN06103498 Issue 2-0


MENU




BCF is in supervisory state BCF is working with no active alarms reportedat both BSC and BTS Manager except for alarm‘7801: MMI connected to Base Station’.

Generate ‘Antenna Connection faulty’ alarm for TRX1 (Non-BCCH)

TRX test failed.

Alarm ‘7606 TRX FAULTY’ with description‘TRX test result Antenna Connection faulty’ isreported for TRX1.

Remove TRX2 (BCCH) from the cabinet. Alarm ‘7603 BTS FAULTY’ with description‘Master TRX detected that connection to slave TRX is lost’ is reported for Sector1


TRX test failed.

Alarm ‘7606 TRX FAULTY’ with description

‘TRX test result Antenna Connection faulty’ isreported for the TRX3


TRX test failed.

Alarm ‘7606 TRX FAULTY’ with description‘TRX test result Antenna Connection faulty’ isreported for the TRX5.

Remove TRX6 (Non-BCCH) from the cabinet. Alarm ‘7606 TRX FAULTY’ with description‘Master TRX detected that connection to slave TRX is lost’ is reported for TRX6

Remove TRX7 (Non-BCCH) from the cabinet. Alarm ‘7606 TRX FAULTY’ with description‘Master TRX detected that connection to slave TRX is lost’ is reported for TRX7


Remove TRX8 (Non-BCCH) from the cabinetbefore BCCH reconfiguration.

TRX test failed. Alarm ‘7606 TRX FAULTY’ withdescription ‘Antenna Connection faulty’ isreported for the TRX4.

Alarm ‘7603 BTS FAULTY’ with description‘Master TRX detected that connection to slave TRX is lost’ is reported for The Sector2


TRX test failed.

Alarm ‘7606 TRX FAULTY’ with description‘TRX test result Antenna Connection faulty’ isreported for the TRX9.

Remove the RX diversity cable from TRX10.

Run TRX Test on TRX10 from BTS Manager.

TRX test failed with reason ‘RX cabling is faultyor missing’ at the BTS Manager.

Alarm ‘7607 TRX OPERATION DEGRADED:

TRX test result antenna connection faulty’ isalso raised at the BTS Manager and BSC.

Connect the RX diversity cable from TRX10.

Run TRX Test on TRX10 from BTS Manager.

The test is successful and the test results areacceptable.

Alarm ‘7607 TRX OPERATION DEGRADED:

TRX test result antenna connection faulty’ iscancelled.

Remove TRX10 (Non-BCCH) from the cabinet. Alarm ‘7606 TRX FAULTY’ with description‘Master TRX detected that connection to slave

TRX is lost’ is reported for TRX10

DN06103498 Issue 2-0


MENU




Remove TRX11 (BCCH) from the cabinet. Alarm ‘7600 BCF FAULTY’ with description‘Master TRX detected that connection to slave TRX is lost’ is reported for BCF

Lock the TRX6 from the BSC and re-install it inthe cabinet.

Unlock the TRX6 from the BSC.

TRX6 is re-installed successfully.

TRX comes up in working state.

Action taken as defined in the test case. Behaviour is per Expected Result defined in thetest case.

Note: When Alarm ‘7600 BCF Faulty’ iscancelled, BCF will be restarted anddiagnostics is executed again and alarm ‘7601BCF Operation degraded’ is reported as the

restored TRX has no diversity.Run the TRX test on the restored TRX from theBTS Manager.

The test is successful and the test results areacceptable.

When the test is started, the alarm ‘7615 RTS ISIN TEST USE’ for used TS is started.

When the test is done finished, the alarm ‘7615RTS IS IN TEST USE’ for the used TS iscancelled.

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

Make calls via restored TRX All calls are successful

Case Ref. Site Type /Configuration

Action Expected Resu lt

1 NSN MetroSite

2+6+3

None+RFHopping+BB Hopping

Restoreantenna for TRX5 andreset TRX5.

Alarm ‘7600 BCF FAULTY’ iscancelled.

Alarm ‘7603 BTS FAULTY’ forSector2 is cancelled.

Alarm ‘7606 TRX FAULTY’ for TRX5is cancelled.

Alarm ‘7606 TRX FAULTY’ withdescription ‘Master TRX detected thatconnection to slave TRX is lost’ isreported for TRX8.

Alarm ‘7603 BTS FAULTY’ withdescription ‘Master TRX detected thatconnection to slave TRX is lost’ isreported for Sector3.

TRX5 restored.

DN06103498 Issue 2-0


MENU



5.6 Antenna Cable Detection

Purpose:

The purpose of these tests is to verify that faults in the antenna cable connection aredetected correctly and alarms are sent correctly from the BTS to the BSC.

Note 35.

Alarms are checked at the BSC and the BTS Manager after every test step. The stateof the BCF is checked from the BSC with MML command ZEEI.

Note 36.

Neighbours are defined for each BTS.

Note 37.

Attenuator should also be removed from the TRX while carrying out Antenna alarmcases.


Calls are made via all TRXs. All Calls are successfulBreak the TX path of the Slave TCH of firstsector.

The antenna fault is detected and alarm 7606 TRX FAULTY (antenna connection faulty) israised both at BTS manager and BSC. Calls via

the Slave TCH TRX are released. All other callsremain ongoing.Reconnect the TX path of the Slave TCH TRX. The alarm is not cancelled automatically. The TRX is locked and unlocked from the BSC. The TRX returns to working state. The alarm is

cancelled.Calls are made via the Slave TCH TRX. Calls are successfulBreak TX path of BCCH TRX of second sector Calls via the BCCH TRX are released. The

antenna fault is detected and alarm 7606 TRXFAULTY (antenna connection faulty) is raisedboth at BTS manager and BSC. Calls arereleased from the BCCH TRX. The TRX isblocked and BCCH reconfiguration is performed.Calls on TRX to be configured as BCCH in the

sector are handed over before reconfiguration.Reconnect TX path of the former BCCH TRX The alarm is not cancelled automatically. TRX lock/unlock is performed The TRX returns to working state. The alarm is

now cancelledCalls are made via all TRXs. All calls are successful

Case Ref. Configuration BCCH TRX

1 2+2,EDGE, STIRC enabled for both sectors Master

DN06103498 Issue 2-0


MENU




BCF is operational.Master TRX of first Slave cabinet is BCCH TRX(TRX in position 5).

Calls are made via every TRX

Site is in supervisory state with no active alarmsreported at both BSC and BTS manager exceptfor ‘Alarm 7801: MMI connected to Base Station’.

All calls are successful TX path of the BCCH TRX in the first Slavecabinet is broken.

Alarm 7606 TRX Faulty (Antenna ConnectionFaulty) is raised for the TRX with removedantenna. After alarm is sent to the BSC, thenBCCH reconfiguration is performed. Calls viaBCCH TRX are dropped Calls on TRX to beconfigured as BCCH in the sector are handed

over before reconfiguration. Rest of the callsremain ongoing.

Calls are made on the newly configured BCCH TRX of the first slave cabinet.

Calls are successful .

Repeat the input steps 2 and 3 for all the newlyconfigured BCCH TRXs of the first slave cabinet.

Alarm 7606 TRX Faulty (Antenna ConnectionFaulty) is raised for the TRX with removedantenna. After alarm is sent to the BSC, thenBCCH reconfiguration is performed. Calls viaBCCH TRX are dropped Calls on TRX to beconfigured as BCCH in the sector are handedover before reconfiguration. Rest of the callsremain ongoing.

For the last BCCH TRX which is the only working TRX of the first slave cabinet, Alarm 7603 BTSFaulty will get raisedAlarm 7767 BCCH Missing will also get raised forthe sector.

Transmission of the last faulty TRX is checkedusing spectrum analyser.

The TRX is not transmitting.

Reconnect the TX path of all the TRXs of the firstslave cabinet and reset the BTS.

All alarms shall get cancelled. The first SlaveCabinet shall return to the operational state.

ConfigurationCase Ref.

2 4+4+4

DN06103498 Issue 2-0


MENU



5.7 DMR uni ts detection

Purpose:

The purpose of this test case is to verify that the BTS is correctly reporting the alarmsfrom the DMC in case of BTS polling is in use.


Site is made as per the test case configuration.

Add both the DMC on the BSC, withZQWA:BCF=47:DMR=INDEX:Q1PORT:;Check the Q1 management on BTS Manager(Transmission -Q1 Management) and switchedON the "InternalToExternal" relay.BTS polling is in use and we can see both theDMR equipment in ZQWL:BCF=#commandoutput.Make a call on the BTS.

Site is in supervisory state with no active alarmsreported at both BSC and BTS manager exceptfor ‘Alarm 7801: MMI connected to BaseStation’.

Site with DMC setup is working fine.

Call is successful

Physical tributary unit from the DMC isdisconnected

Alarm 8061 is reported on BSC and BTSmanager. No disturbance is observed onongoing call.

The disconnected physical tributary unit isreconnected.

Alarm 8061 is cancelled from both BSC andBTS manager. No disturbance is observed onongoing call.

One of the DMR units in DMC setup is switchedOFF.

Alarm 8081, 8099 are reported with severityCritical and Alarm 8102 is reported with severityMajor on BSC and BTS manager Nodisturbance is observed on ongoing call.

The DMR unit that has been switched OFF isswitched ON.

All the alarms get cancelled both on BTSManager and BSC.On BTS Manager alarm 8081 and 8099 arecancelled with severity Critical and alarm 8102 is

cancelled with severity major. No disturbance isobserved on ongoing call.

Configuration Case Ref .1. Any

DN06103498 Issue 2-0


MENU



6. BTS MANAGER FUNCTIONALITY

6.1 BTS Configurations and Site Information

Purpose:

The purpose of these tests is to verify that the BTS configurations and Site Informationare displayed correctly.


The BCF is operational and calls are made. Calls are successfulBTS Manager is locally connected to the BCF. The Equipment view is activated from the

Supervision menu.

Local connection to BCF is established. Alarm7801 ‘MMI CONNECTED TO BASE STATION:

Local MMI connected’ is started at both the BSCand the BTS Manager. The Supervision window is opened with theEquipment view, which displays the physicalconfiguration of the BTS and correct Unit Type.

The mouse pointer is moved over the cabinet(s),the BCF, TRX(s), TRE and other objects.

The information given in the Status bar at thebottom of the window is updated when the mouseis moved from one object to another.Information is correct.

Select any of the objects (Power supply unit, TRX(s)). Right click on that and select HWversions.Unit Type, Version and Serial Number are

verified.

HW Versions Report opened successfully.Unit Type, Version and Serial Number are showncorrectly.

The Logical Objects view is activated from theSupervision menu.

The logical objects (BCF, Sector, TRX, and TRE)configuration view is displayed in graphicalhierarchical format in the Supervision window.

The mouse pointer is moved over the logicalobjects.

The information given in the Status bar at thebottom of the window is updated when the mouseis moved from one object to another. Informationis correct.

From the logical view, BCF Information is savedinto a file.

The report format is sensible and the informationis as in the dialog box.

The Supervision | Site Information command isselected.

The SW Versions, HW Versions, LAPD status,Alarms, Object Data, Clock Control Settings andAbis State is shown correctly in the SiteInformation dialog box

The Site Information is saved into a file with theSave As command.

The Site Information file contents are correct andthe report format is sensible

Reset the BCF and repeat the above test steps. Operation Successful.

Case Ref. Configuration HW Unit

1 2+2 VTPA+HVTP, HVSx

DN06103498 Issue 2-0


MENU



7. REMOTE BTS MANAGER

7.1 Multiple Remote BTS Manager sessions for di fferent BTSs

Purpose:

The purpose of the test is to verify that several remote BTS manager sessions fordifferent BTSs can exist simultaneously on single PC.


More than seven different BCFs are used onseveral BSCs. The remote BTS Managerconnections are established from a single PC.

Use few BCFs from Same BSC.

All the remote sessions operate simultaneouslyon a single PC. Alarm 7801 ‘MMI CONNECTED TO BASE STATION: Remote MMI connected’ is

started at the BSC for all BCFs and the alarm isalso visible at the separate BTS Managers.

The remote BTS Manager session to BCF1 isdisconnected and then reconnected.

The remote BTS Manager sessions to theremaining BCFs stay operational and BCF1 isreconnected.

The process is repeated for all the Remote BTSsessions.

All sessions remain operational other than thesession disconnected.


1 Any

7.2 Remote BTS link failure - BER Introduced

Purpose:

The purpose of these tests is to ensure that the Remote BTS Manager sessionterminates correctly when some link between the BTS and the BTS manager fails.

Note 38.

For BER greater than 1E-6 and less than 1E-3, the alarm 8102 ‘BIT ERROR RATE(BER) > 1E-6’ is raised. For BER greater than 1E-3 the alarm 8099 ‘BIT ERROR RATE(BER) > 1E-3’ is raised.

Test Tool: Data Channel Simulator


The BCF is operational and in supervisory state. The BER (Bit Error Rate) is set with the DataChannel Simulator to 1E-6. The BER is generated in the uplink direction, inthe downlink direction and simultaneously in bothdirections. Alarms are checked at the BSC andBTS manager.

Site is in working state. There are no activealarms except for ‘7801: MMI connected to BaseStation’. Alarm 8102 ‘BIT ERROR RATE (BER) >1E-6’ will be reported at the BSC and the BTSmanager, when the error is in downlink or bothdirections.In case the error is in uplink direction, Alarm“2923 CRC BIT ERROR RATIO OVER LIMIT” willbe raised on ET in use on BSC. .

DN06103498 Issue 2-0


MENU




The Remote BTS Manager session is started. A TRX test is started from the remote BTS Managermenu command by selecting TESTS/TRX TEST.

The remote BTS Manager gets connected andalarm 7801 ‘MMI CONNECTED TO BASESTATION: Remote MMI connected’ is started atboth the BSC and the BTS Manager.Executed commands are successful.

The test is repeated with BER value 1E-9 and 1E-3

The Remote BTS Manager does not getconnected with BER value 1E-3.


1 Any, Use Combined Signalling

7.3 Dynamic Abis EDAP pools update on Mult iple remote BTS Manager

Purpose:

The purpose of this test is to verify that the dynamic Abis EDAP pools from multipleremote BTS Manager applications can be updated.

Note 39.

The data throughput rates expected in this test specification is based upon simulations.Customers must not consider these figures to be a commitment to actual performancein a live network. If IR port is used for connecting phone to PC, it will be bottleneck forthroughput, so cable connection (Phone-PC) is recommended for better datathroughput.

Note 40.

EGPRS cannot be used without Dynamic A-bis being configured. Unless specificallystated in the test case.

The protocol layer between the MS and the PCU is the RLC/MAC layer. There are twomodes for the RLC protocol:

Acknowledged RLC Mode

Unacknowledged RLC Mode

In Acknowledged RLC Mode, the receiver acknowledges the data sent. If data is notcorrectly received the data is retransmitted. In this mode Incremental Redundancy isautomatically enabled.

In Unacknowledged RLC Mode the data is not acknowledged. Incremental Redundancydoes not take place. The system relies upon error correction using the redundancyincorporated in the coding scheme. Any data blocks that are not successfully errorcorrected remain corrupt.

Note 41.

The Link Adaptation algorithm is also influenced by the amount of space left in theEDAP. If the space in the EDAP runs out, Link Adaptation will restrict the MCS used inthe downlink accordingly. In the uplink the PCU scheduling function will prevent the MSfrom sending data for one block period, until space again becomes available in the

EDAP. The data rate will not be as high as anticipated. For this reason, the EDAP mustbe of a sufficient size for the number of radio timeslots configured as EGPRS.

DN06103498 Issue 2-0


MENU



Note 42.

To enable/disable Link Adaptation use the MML commands:ZEQV:BTS=##:ELA=1; Link Adaptation = on

ZEQV:BTS=##:ELA=0; Link Adaptation = off

To set the initial MCS use the MML command:

ZEQV:BTS=##:MCA=#,MCU=#;

Where:

MCA = initial coding scheme in acknowledged RLC mode.

MCU = initial coding scheme in unacknowledged RLC mode.

Note 43. The behaviour of the Link Adaptation algorithm, and hence the resulting MCS used anddata rate achieved, can be manipulated by an offset applied to the Bit Error Probability(BEP) measurements sent to the PCU. The offsets are applied using the parametersMBP (for 8PSK) and MBG (for GMSK). In order to see the expected data rates it isimportant that these offsets are set to zero.

This is done using the MML command:

ZEQV: BTS=#: MBP=0, MBG=0;

Note 44.

In Unacknowledged RLC Mode Link Adaptation chooses the highest MCS that keepsthe raw block error rate below the limit set by the operator using the BLU parameter.Because there are no retransmissions the user rate for the MCS chosen should remainconstant and close to the expected user rate. The data at the receiving end can beexpected to be corrupted, but no more than the upper limit set by the operator. This limitis expressed as the maximum number of block errors per 1000 allowed. Setting BLU toits lowest value of 10 will cause Link Adaptation to select a more robust MCS soonerwhen radio conditions deteriorate.

Table 3

CodingScheme

Number of SlaveFrames

MCS 1 0MCS 2 1

MCS 3 1

MCS 4 1

MCS 5 1

MCS 6 2

MCS 7 3

MCS 8 4

MCS 9 4

DN06103498 Issue 2-0


MENU




Two different BCFs are used. The Sites are operational.

Sites are in working state. There are no activealarms except for ‘7801: MMI connected toBase Station’.

EGPRS call is made in both BCFs using MCS-9. The Abis is monitored during the calls

Calls are successful. The Master Data Framepoints to the Slave data frames at the EDAP TS.

Remote BTS Manager connections are made toboth BCFs from the same PC.

Both BTS Managers are started successfully.

The Transmission/Traffic Manager command isselected from the BTS Manager for the BCFs. The EDAP pool in both BCFs is increased byadding one TS at the beginning of the EDAPpool at the traffic manager.

The EDAP pool are modified successfully andnew Abis allocation are sent to the transmissioncards.

Lock the BTS.EGPRS is disabled. Using MMLcommand ZESM, the EDAP pool in both BCFsis increased by adding one TS at the beginningof the EDAP pool. EGPRS is enabled. Unlockthe BTS.

The pools are modified at the BSC successfully.

EGPRS calls are made using MCS-9. Calls are successful. The Abis are monitored

during the calls. The Master Data Frame pointsto the Slave data frames at the new EDAP TS.

Choose BCF1 for further operations BCF1is in working state. There are no activealarms except for ‘7801: MMI connected toBase Station’.

Choose an MS so that RLC Mode =Unacknowledged RLC Mode (See Note 44).

Operation successful

Use the MML commandZERM: BTS=##, TRX=##: GTRX=Y or N; To enable EGPRS on the BCCH or non-BCCH TRX as indicated in the table below.Use CDED, CDEF and CMAX to enable 2 radio

timeslots as EGPRS.

Operation successful

DN06103498 Issue 2-0


MENU




Operation successfulSet Link Adaptation =on (see Note 41).Use the MML commandZEQV: BTS=##: BLU=10; To set the max. Limit for block error rate to 10per 1000.

Check that no offsets are applied to the BEPvalues (See Note 43).

Set up equipment to adjust Carrier / Interference(C/I) conditions in the air interface in the directionshown in the table. Initially set C/I >30dB.

Transfer a 500KB file using UDP/IP protocol inthe direction shown in the table below.Use one timeslot for uplink transfer.Use two timeslots for downlink transfer.

On Abis PCU frames are monitored.

Slowly change the C/I from 30dB to 0dB andback to 30dB. Carry out 2 times. Rate of change=1 dB/sec approx.

The coding scheme used steps down through thecoding schemes from the least robust (MCS9) tothe most robust (MCS1) and back again to matchthe changing air interface conditions. MCS 4 maybe skipped as Link Adaptation switches from

8PSK to GMSK and vice versa. The data ratechanges to reflect the changing MCS.

Stop recording. Check the A-bis trace for theMCS used, and the allocation of PCU Slave DataFrames.

Dynamic A-bis allocates PCU SLAVE DATAFRAMES correctly as the MCS changes.

Case Ref. Configuration Type of TRX Direction of Interference

Direction of Data Transfer

1 Multi TRX EDGE Non – BCCH Downlink Downlink

DN06103498 Issue 2-0


MENU



7.4 Alarm Handling: Slave TCH TRX removed

Purpose:

The purpose of these tests is to verify that the Remote BTS Manager can handle thealarms correctly.

Note 45.

TRXs need to be set to PMAX of 0dB in order to generate the ‘Antenna connectionfaulty’ alarm. PMAX value should be turned back to 30db once the completion of testcase.


Calls are made via every TRX. All Calls are successful The BTS Manager is started from a remote PCvia NetAct and BSC using the NSN GCSconnection tool.

Remote connection to BCF is established. Alarm7801 ‘MMI CONNECTED TO BASE STATION:Remote MMI connected’ is started at both theBSC and the Remote BTS Manager.

Generate ‘Antenna Connection faulty’ alarm for TRX1 (BCCH)

Alarm '7606 antenna connection faulty’ will bereported for TRX1.BCCH reconfiguration will take place.

The non-BCCH slave TCH TRX is removed. When the Slave TRX is removed, alarm ‘7606 TRX FAULTY’ (Master TRX detected thatconnection to the Slave is lost) is reported at the

BSC and Remote BTS Manager.Calls via the removed TRX are released. The removed TRX is locked and unlocked fromthe BSC.

The alarm is cancelled from BSC with lock actionand then sent again with unlock action.

The Slave TRX is reinstalled.Calls are made via every TRX.

The Slave TRX is initialised. The TRX returned toworking state and the alarm ‘7606 TRX FAULTY’is cancelled at both the BSC and the RemoteBTS Manager. Calls are successful via every TRX.

Repeat with all non-BCCH slave TRXs Result should be correct

Case Ref. Configuration O&M and TRXSIG BCCH TRX

1 Multi TRX Combined Master

8. INTELLIGENT SHUTDOWN FOR METROSITE

Purpose:

The purpose is to verify that the site can perform the Background SW Download andOMU block/Unblock operation while in Intelligent Shutdown mode are handledcorrectly..

Note 46.

For all Intelligent Shutdown test cases neighbours are defined for BTS under test.Neighbours defined shall not be involved within the testing of the feature other than tohandle the calls once handed over by the BSC unless otherwise stated.

DN06103498 Issue 2-0


MENU



Note 47.

During Intelligent Shutdown, the shutdown TRXs shall get powered OFF. The TRXsshall no longer report to the BTS Manager and therefore shall not be visible on theequipment view of the BTS Manager. The administrative state of the TRXs for theshutdown TRXs shall not be possible to be verified.

The exception to this rule shall be the Master TRX. This shall remain powered even inthe shutdown mode. The Master TRX of the Master Cabinet shall also power OFF theMaster TRX of the Slave cabinets, if all TRXs in the Slave cabinet are in the Shutdownmode. The Master TRX when left powered during shutdown mode shall be visible onthe equipment view and could be verified as shutdown.

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

The TRXs could be verified as being in shutdown or supervisory mode on the BTSManager using the objects/properties command.

Note 48.

For Intelligent shutdown test cases receiver diversity should be disabled.

Note 49.

For all the intelligent shutdown test cases it is assumed that the testing shall becompleted using an external BBU (EAC inputs) unless otherwise stated. The EAC inputshall need to be set as detailed below. The predefined external input for MetroSite forthe Mains fail is EAC 01.

ZEFX:<bcf_id>:INBR=1:ROU=MAINS:POL=<OPEN - active or CLOSED -

inactive>,SEV=AL3;Note 50.

When BTS_CONF_DATA message is received during intelligent shutdown, any unit inthe configuration message that is in shutdown mode are unaffected. It is to be verifiedthat a BTS_CONF_COMPL message is sent for the BCF in which shutdown TRXsreside, even if the actual configuration is skipped for these.

Note 51.

The feature consists of three BTS Battery Backup procedures that may be applied onmains failure, these are:

•

Al l shutdown mode - maintain full service,• BCCH shutdown mode - maintain the BCCH TRXs, or

• None shutdown mode - maintain only the transmission equipment.

Note 52.

It is possible to Activate Intelligent Shutdown with Timer Control with the MMLcommand ‘EFM’:

ZEFM:<bcf_id>:BBU=<BTS battery backup procedure>,NTIM=1,BTIM=3;

Where:

ZEFM:<BCF identification>:BBU<BTS battery backup procedure>,NTIM<TRX

shutdown timer>, BTIM<BCCH TRX shutdown timer> where <TRX shutdown timer>and <BCCH TRX shutdown timer> are given as a decimal number.

DN06103498 Issue 2-0


MENU



NTIM=1 means that after a mains failure, there is full service on the BTS Site for oneminute before the service level is changed. This can be any value from 1 minute to 600

minutes.

BTIM=3 means that the BCCH TRXs will be maintained for three minutes after the non-BCCH TRXs are shut down, that is, until the BTIM timer expires. This can be any valuefrom 1 minute to 600 minutes.

Timer 1 Timer 2 Timer 3 Timer 4 Timer 5TRX type

Power State Power State Power State Power State Power State

TRX 1 –BCCH

ON WO ON WO ON WO ON BL-SHD

OFF BL-PWR

TRX 2 - TCH ON WO ON BL-SHD

OFF BL-PWR

OFF BL-PWR

OFF BL-PWR

TRX 3 - TCH ON WO ON BL-SHD

OFF BL-PWR

OFF BL-PWR

OFF BL-PWR

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

DN06103498 Issue 2-0


MENU



8.1 Background SW Download

Purpose:

To verify that background software download is successful in MetroSite, while site is inBCCH shutdown state.


Configure the site as per test case configuration.

Define the value of NTIM at the BSC and set theshutdown mode as BCCH.

Site is in supervisory state. There are no activealarms except for ‘7801: MMI connected to BaseStation’. The shutdown mode is successfully defined atthe BSC.

MAINS breakdown alarm is generated over thesite using the EAC box and that is configured overthe site using the MML command ZEFM andZEFX.

Alarm ‘7995 - Mains breakdown with batterybackup’ is observed in the BSC and the BTSmanager.

After the expiry of NTIM timer the site enters theBCCH shutdown mode

Make one speech call and hold it throughout thebackground SW download

Speech call is successful

BTS S/W package as defined in the test case isattached to the BCF using ZEWA command. TheSW download progress is seen over the Abisinterface.

Background S/W download over the site startsand completes successfully.

Speech call is successfully terminated. Terminate the speech call.

Activate the downloaded SW from the BSC. The SW is activated successfully. The BCFtakes a reset and comes up in working state fora few seconds. The Mains breakdown alarm isre-reported to the BSC. The BSC starts theNTIM again. After the expiry of NTIM the siteenters the BCCH shutdown mode.

Check the version of active SW at the BTSmanager and the BSC.

The active SW version is the same as that of thebackground downloaded SW.

Cancel the MAINS breakdown alarm. The alarm is cancelled both at the BTS managerand the BSC. The site recovers from shutdownmode and comes up in working state.

Make calls on every TRX of the BCF. The calls are successful.

Case Ref. BTS Configuration BTSType

Init ial BTS SW BTS SW toDownload

1 4 Omni MetroSite CX6 CX7

DN06103498 Issue 2-0


MENU



8.2 OMU Block/Unblock from BSC

Purpose:

To verify that BCCH transmission from Master TRX (defined as preferred BCCH TRX)does not start after OMU block/unblock in NONE shutdown mode.


The site is configured as per the test case. Site is in the supervisory state with no activealarms reported at both BSC and BTS Managerexcept for alarm "7801: MMI connected to BaseStation".Command is successfully executed. The intelligent shutdown with both timers is

activated for the NONE Shutdown mode.ZEFM: <bcf _i d>: BBU=NONE;

ZEFM: <bcf _i d>: NTI M=<NTI M_t i mer >, BTI M=<BTI M_t i mer >;

Make speech calls on all TRXs. All calls are successful The mains breakdown alarm is generated. Alarm 7995:MAINS BREAKDOWN WITH

BATTERY BACK-UP is reported at the BSC andBTS Manager. The NTIM timer is started. The set time for the NTIM timer expires.

The calls are handed over from the non-BCCH

TRXs to the neighbour or to the BCCH TRX of the sector. When the Hand-off timer started bythe BSC expires or all the calls are handed off then the BSC sends theBTS_PWR_SUPPLY_CONTROL (switch off each non BCCH TRX) message to the BTS. The BTIM timer is started.All non-BCCH Slave TRXs are put to BL-PWRstate indicating that these have been shutdown. The Master TRX (BCCH TRX) remainsoperational. The set time for the BTIM timer expires. The calls are handed over from the BCCH TRXs

to the neighbour cells. When the Hand-off timerstarted by the BSC expires or all the calls arehanded off then the BSC sends theBTS_PWR_SUPPLY_CONTROL (switch off BCCH TRX) message to the BTS. The Master TRX remains powered on but is setto BL-PWR state at BSC and LED status of Master TRX is Amber at BTS Manager and BTScabinet.BCCH transmission is stopped.

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

The state of the TRXs is shown as defined in[Note 47]

For test case 1 traffic trace (from Tests Menu) is

monitored from BTS manager for the BCCH TRX.

In the traffic trace the BCCH timeslot of the TRX

is in idle state.

DN06103498 Issue 2-0


MENU




The OMU is blocked from the BSC whilst the siteis in ‘None shutdown mode’ state using command–ZDTC: <OMU>: BL;

The state of the OMU is blocked at the BSC.Alarm 7706 “BTS O&M LINK FAILURE” is activeat BSC.

The OMU unblock command is given from BSC.ZDTC: <OMU>: WO;

Alarm 7706 “BTS O&M LINK FAILURE” iscancelled at BSC and OMU state changed toworking.Master TRX LED remains Amber at BTSManager and BTS cabinet.

Check the BCCH transmission using SpectrumAnalyser. For test case 1 traffic trace (From Testsmenu) is monitored from BTS manager for theBCCH TRX.

BCCH transmission is not started.For test case 1 traffic trace shows that theBCCH timeslot of the TRX is in idle state.

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

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

All Slave TRXs are switched ON. All TRXs areinitialised and come to WO state and BCCHtransmission gets started.

New speech calls are established on all TRXs. All calls are successful

Case Ref . BCF Configuration BCCH TRX

1 4 Omni, GSM/EDGE Master

2 4 Omni, GSM/EDGE Master

9. RECOVERY FOR BSS AND SITE SYNCHRONISATION

Purpose:

The purpose is to check the Recovery handling for BSS and Site Synchronisation.

Note 53.

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

or Base Station.In order for the network to recover automatically from a loss of synchronisation greatercontrol is exercised by the BSC. So in S11 onwards the Base Station is told by the BSCin the BTS_CLOCK_REQ message which synchronisation mode it should be in.

9.1 Sync Recovery - Miss ing GPS Signal

Purpose:

To check that a previously synchronised chain behaves correctly when the LMU’s GPSsignal is lost and then returns. To check that the recovery actions are not triggered if theGPS outage is less time than the LMU timer period. To check that the Base Station

responds correctly to the BSCs control when the recovery actions are triggered by anoutage longer than the LMU timer period.

DN06103498 Issue 2-0


MENU



Note 54.

LMU has an internal timer. If the GPS fix is lost for less than the timer period the LMUcontinues to send its clock signal. The synchronisation chain of BCF continues to besynchronised by the LMU as if nothing had happened.

After the LMU’s timer has expired it sends alarm 1001 ‘clock out disabled’. It is thisalarm, which triggers the recovery procedure when it is received at the BSC.

Note 55.

It will be necessary to perform this test either in a screen room, or by fully cabling theMobile Stations to the Base Stations. This is because the MS must be able to see, andhand over to, a neighbouring cell, and cannot therefore be locked onto the segmentbeing used for test.


All the operations are successful.Create the Sites at the BSC depending upon theconfiguration indicated in the test case and in thediagrams below. Lock all TCH except timeslot 2on each TRX in the Multi-BCF segment.

Also unlock timeslot 7 on TRX4 in each BTS inthe segment. Make this a dedicated GP timeslot.

Ensure there is a neighbouring BTS to which callson the synchronised BCFs may be handed over.

Set the BTS power level of the neighbouring BTSmuch lower than the segment so that MS preferthe segment.

At LMU Manager, Select View→ Advanced.Select Maintenance. Open the ‘Clock Out TimeSettings…’ dialogue box. Set the Time from fixlost to clocks out alarm to 240 sec. Set the Timefrom clocks out alarm to clock disable to 60 sec.

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

When The BCF resets it sends a BTS_OMUSTARTED message with synchronisation mode =Slave, regardless of the setting in HWconfiguration file.

DN06103498 Issue 2-0


MENU




Camp 8 MS on to the segment. Make sure theycan also see the neighbouring BTS. i.e. it will notbe possible to use the MS field test software tolock them to the segment. Make 4 pairs of speechcalls. Speech is maintained. These calls will be left up during the test case.

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

All calls are successful

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

Monitor the BTS Events window in BTS Manager,

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

The LMU sends a ‘GPS fix lost’ alarm 48 on theQ1 bus. The BCF sends this up the Abis as an‘8048 GPS fix lost’ alarm. However, the LMUdoes not send a ‘1001 clock disable’ alarm. TheBCFs continue to be synchronised by the clocksignal from the LMU.

Check the status of the calls and transfers.

Check the sync status at BTS Manager / MMI.

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

All calls remain up. Both GPRS transfers remainongoing.

BCFs still show as being in Slave mode.

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

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

The LMU sends an alarm 48 cancel on the Q1bus. The BCF forwards this as an ‘8048 GPS fixlost’ cancel on the Abis. The BSC does not beginany further recovery actions when it receives thisalarm.All calls/transfers remain up. The BCFs continueto be synchronised by the clock signal from theLMU.

At 4 minutes monitor the Q1 bus. The LMU does not send any alarms. i.e. the LMUtimer was successfully reset.

Case Ref. Configuration Software

1 Figure 2 LMU SW Version: LMUB 1.0 CD3

DN06103498 Issue 2-0


MENU




Create the Sites at the BSC depending upon theconfiguration indicated in the test case and in thediagrams below. Lock all TCH except timeslot 2on each TRX in the Multi-BCF segment.

Also unlock timeslot 7 on TRX4 in each BTS inthe segment. Make this a dedicated GP timeslot.

Ensure there is a neighbouring BTS to which callson the synchronised BCFs may be handed over.Set the BTS power level of the neighbouring BTSmuch lower than the segment so that MS preferthe segment.

At LMU Manager, Select View→ Advanced.Select Maintenance. Open the ‘Clock Out TimeSettings…’ dialogue box. Set the Time from fixlost to clocks out alarm to 240 sec. Set the Timefrom clocks out alarm to clock disable to 60 sec.

All the operations are successful.

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

When The BCF resets it sends a BTS_OMUSTARTED message with synchronisation mode =Slave, regardless of the setting in HWconfiguration file.

Camp 8 MS on to the segment. Make sure theycan also see the neighbouring BTS. i.e. it will notbe possible to use the MS field test software tolock them to the segment. Make 4 pairs of speechcalls. Speech is maintained.

These calls will be left up during the test case.

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


DN06103498 Issue 2-0


MENU




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

Monitor the BTS Events window in BTS Manager,or the Messages and Alarms window in BTS MMI. Disconnect the GPS antenna from the LMU, orblock the antenna’s view of the satellite. At thesame time start a stop-clock to monitor the lengthof time the GPS signal is missing.

The LMU sends a ‘GPS fix lost’ alarm 48 on theQ1 bus. The BCF sends this up the Abis as an‘8048 GPS fix lost’ alarm. However, the LMUdoes not send a ‘1001 clock disable’ alarm. TheBCFs continue to be synchronised by the clocksignal 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 MMLcommand:ZEFL;

All calls remain up.

BCFs still show as being in Slave mode.

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

At 4 minutes on the stop clock monitor the Q1 busand Abis.

The LMU sends alarm ‘1001 clocks out disabled’. The first BCF forwards this alarm up the Abis tothe BSC as: Talk: 7876 LMU. External synchronisation signalsdisabled.

MetroSite: 7602 BCF Notifications. Externalsynchronisation signals disabled. (Alarm detail =28)

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

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

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

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

Clock sync =PCM_ExternalClock output =Enabled. The first BCF comes into working order in Mastermode.

After the first BCF has sent theBTS_CONF_COMPL message, the BSC resetsthe second BCF. The BSC sends aBTS_CLOCK_REQ message on the Abis, with:Clock sync = BTS_ExternalClock output =Disabled. The BCF comes into working order in Slavemode.

Check the MS carrying the GPRS transfers. The MS reselect the BTS in the segment again.

DN06103498 Issue 2-0


MENU




Check the sync status at the BSC for all BCFs,using the MML command:ZEFL;

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

Check for alarm ‘8048 GPS fix lost’ alarm at BSCusing MML command:ZEOL:<first Slave BCF number>;

8048 alarm is still active.

Disconnect the calls now on the neighbour. Re-establish 4 pairs of calls on the segment. Speechis maintained.


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

The LMU cancels alarm 48 on the Q1 bus andthis is forwarded by the BCF as a cancellation of alarm ‘8048 GPS fix lost’ on the Abis.

All calls hand over successfully to theneighbouring BTS. The GPRS transfers reselectthe neighbouring BTS.

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

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

Monitor the MMI and Abis for all of the BCFs. The BSC resets the first BCF in the chain. TheBSC sends a BTS_CLOCK_REQ message onthe Abis, with:Clock sync = BTS_ExternalClock output =Disabled. The first BCF comes into working order in Slavemode synchronised to the restored clock from the

LMU.

After the first BCF has sent theBTS_CONF_COMPL message, the BSC resetsthe second BCF. The BSC sends aBTS_CLOCK_REQ message on the Abis, with:Clock sync = BTS_ExternalClock output =Disabled. The BCF comes into working order in Slavemode.

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 BCFs,using the MML command:ZEFL;

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

Disconnect the calls now on the neighbour. Re-establish 4 pairs of calls on the segment. Speechis maintained.


Case Ref. Configuration Software

LMU SW Version: LMUB 1.0 CD32 Figure 2

DN06103498 Issue 2-0


MENU



9.2 Site Synchronisation: BCF reset - Clock Source – LMU

Purpose:

The purpose is to verify that the Base Station initialises into the correct synchronisationmode.


Synchronization chain is defined at the BSCusing the MML commandZEFM: <s1>: CS=LMU, SENA=T, ADD=<s2>;<s1> = Sl ave 1 BCF numberLock all TCH channels except timeslot 2 oneach TRX in the Multi-BCF segment.

Physically create and commission the Sites.Monitor the BTS Events window in BTSManager, or the Messages and Alarmswindow in BTS MMI.

Operation is successful. The site is in supervisorystate with BTS clock synchronised to the LMU There are no active alarms reported at both BSC andBTS manager except for ‘Alarm 7801: MMI connectedto Base Station’.

PCM .is disconnected.

GPS is disconnected.

OMU will come into BL state. Alarm 7704” PCMFailure “ will get reported both at BTS manager andBSC. Site will remain in BL-RSL state.

GPS disconnection will not have any effect on Sitestate.

PCM is connected. Alarm 7704 : PCM Failure “ will get cleared and OMUwill come to WO state.

The BSC sends each BCF a BTS_RESET REQ withobject identity =BCF. The BCF resets and sends a BTS_OMU STARTEDmessage with synchronization mode =as per testcase.

Each BCF sends BTS_CONF_REQ to the BSC. TheBSC sends a BTS_LMU_FN_OFFSET COMMAND tothe BCF next to the LMU. The BCF returns aBTS_LMU_FN_OFFSET_ANSWER with success-failure = failure . The BSC sends a BTS_CLOCK_REQ to all the BCFswith:

Clock sync =PCM_InternalClock output =disabled

The BSC sends the configuration of the Sites inBTS_CONF_DATA messages. The BCFs come intoworking order. The BCFs send aBTS_CONF_COMPLETE. The BTS Events/MMIwindow shows that the BCFs are in independentmode.

Lock 8 MS to the segment. Make 4 pairs of speech calls. Speech is maintained.


Repeat the reset/call sequence a total of 5

times.

The Site’s behaviour is repeatable.

DN06103498 Issue 2-0


MENU




Case Ref. Configuration LMU SW Sync Mode inBTS_OMU_STARTED

1 LMU+Metro(4 Omni) ,

RF hoppingLMUB 1.0 CD3 Independent


Site is configured as per the test case. Site is in supervisory state with no active alarmsreported at both BSC and BTS manager exceptfor ‘Alarm 7801: MMI connected to BaseStation’. The BTS clock is synchronised to theLMU.

LMU reset is given from the menu of the LMUManager.

The LMU shall get reset.

Alarms are Monitored at the BTS Manager andBSC.

Alarm 8048:Loss of incoming signal shall beraised at the BTS Manager and BSC.

The BTS resets and returns to working statewith independent clock source. The LMU shall returns to operational state. GPSsignal indicates "OK" and then "locked" at LMUManager. LMU alarm 8048 shall get cancelledat BSC and BTS Manager.

BTS shall take the reset and the site returns toworking state with BTS clock synchronised tothe LMU"

Calls are established on the BTS All calls are successful

Test case is repeated ten times for consistency. Identical results are observed.

Case Ref BTS Configuration ClockSource

Q1 Address

2 4 Omni LMUA 5

DN06103498 Issue 2-0


MENU



10. END TO END DOWNLINK ABIS PERFORMANCE MONITOR

10.1 Downlink LAPD Performance Counters Reporting

Purpose:

To check that BCF reports down link performance counter values to BSC inBTS_LAPD_CTR_REP Message for all TRXs which responded toLAPD_STATISTICS_REQ_MSG from BCF/Master TRX

Note 56.

In all test cases it is to be verified that in BTS_LAPD_CTR_REP message, value of LAPD performance counters for OMUSIG always preceded by the TRXSIG counter

values and OMUSIG counter values are always present.

Note 57.

Top of Hour: when BCF comes to supervisory state after BCF Reset, it updates BTSReal Time clock. BCF receives BTS Real Time clock in BTS Conf. Data from BSC. itstarts 10 minute timer to calculate LAPD performance counter reporting time. After each10-minute expiry BCF check the current time with Top of Hour (XX:00). If current time isbetween (XX: 50- XX:00) hours, BCF sends LAPD_STATISTICS_REQ_MSG messageto all detected TRXs. And after 2000ms BCF sends BTS_LAPD_CTR_REP message toBSC on Abis containing value of LAPD performance counters.

Equipment and BTS Set-Up

BTS configuration as defined in test case. BTS Site should be in commissioned andsupervisory state.


Lock/Unlock BCF from BSC using ZEFScommand

BCF Resets and during reset procedure BSCsends real time update to BCF in BTS Conf. Dataon Abis.

BCF initialise the real time clock and send BTS

Conf Complete message to BSC on Abis. Aftersending BTS Conf. Complete message to BSCBCF starts Top of hour timer.

BCF returns to WO-EX state at BSC.At BTS Manager, BCF and all TRXs return tosupervisory state.

Note time of BTS Conf. Complete message fromBCF to BSC on Abis analyser.

If this time is XX: YZ Hrs, thanBTS_LAPD_CTR_REP message is expected atXX: 5Z Hrs on Abis.

DN06103498 Issue 2-0


MENU




Using Data Simulator inject continuous randomerrors into downlink direction of all LAPD linksterminating in BTS Site for 30 minutes.

Select error rate of 1E-05.

On Abis, errors can be seen on all LAPD links indownlink direction.

Start and Cancel of Alarm ‘8102 RECEIVED BITERROR RATIO (BER) >1E-6’ can be observedon BSC.At BTS Manager Start and Cancel of Alarm ‘8102ERROR RATE >1E-6’ is observed.

Using Data Simulator insert delay of 250ms inuplink direction of Abis link for all LAPD links for 5minutes.

On Abis, 2 or more consecutive RR message canbe seen for all LAPD links on uplink and downlinklinks.

Start CX(M)6 BTS SW build backgrounddownload from BSC to BCF.

Background BTS SW download startssuccessfully.

Background BTS SW download completedsuccessfully

Set up MS – MS speech calls on all TRXs andhold calls for minimum 60 seconds.

All Calls are successful

Wait for Top of hour and checkBTS_LAPD_CTR_REP message for LAPDperformance counters on OMUSIG LAPD link

At Top of hour:At D-Bus Trace: BOIA/Master TRX will sendLAPD_STATISTICS_REQ_MSG message to allConnected TRXs. And wait 2 seconds forresponses from all TRXs.

All TRXs will respond to BCF/Master TRX withLAPD performance counters values inLAPD_STATISTICS_REP_MSG.

After 2 second of sendingLAPD_STATISTICS_REQ_MSG, BCF/Master TRX will prepare BTS_LAPD_CTR_REPmessage (from responses of TRXs) and send thisreport to BSC on OMUSIG.

BTS_LAPD_CTR_REP will contain LAPDperformance counter values for all TRXSIG andOMUSIG.

Verify values of LAPD performance countersreported by respective TRXs inLAPD_STATISTICS_REP_MSG to BOIA/Master

TRX with LAPD performance counters valuesreported by BCF/Master TRX to BSC inBTS_LAPD_CTR_REP message.

LAPD performance counters values reported inLAPD_STATISTICS_REP_MSG should matchwith respective LAPD performance counter

values in BTS_LAPD_CTR_REP message.

Verify values to LAPD performance counters inBTS_LAPD_CTR_REP message

Values of LAPD performance counters are with inrespective tolerance range of actual values foreach counter.

Case Ref. BTS Configuration /BTS Type OMU signalling Type

1 4 Omni, MetroSite Combined

DN06103498 Issue 2-0


MENU



11. STIRC

11.1 STIRC handl ing wi th GSM sector

Purpose:

To check that BCCH transmission of the GSM sector stops when STIRC is enabled forthe sector.


Site is configured as per the test case. Site is in supervisory state with no active alarmsreported at both BSC and BTS manager exceptfor ‘Alarm 7801: MMI connected to BaseStation’.

Speech calls are made on all TRXs. Speech calls are successful.STIRC is enabled from BSC using ZEQM:BTS=<BTS no>: STIRC=Y; in test sector.

STIRC is enabled successfully.“BTS_CONF_DATA” is sent to BTS by BSCcontaining STIRC as ON for the sector undertest.Alarms “7606 TRX FAULTY: Non EDGE TRXdevice type used accidentally in Edge CapableMode” for all the TRXs but one and Alarm "7603BTS FAULTY: Non EDGE TRX device typeused accidentally in Edge Capable Mode” arereported for sector under test. Calls in testsector are dropped. Calls in other sector are not

affected.BTS state and alarms are checked at BSC. Sector is in BL-BTS state. Alarms 7606 & 7603can be seen at BSC for the sector.

BCCH transmission of sector under test ischecked using Spectrum Analyser.

BCCH transmission is not seen for sector undertest.

STIRC is disabled from the BSC. STIRC is disabled successfully.“BTS_CONF_DATA” is sent to BTS by BSCcontaining STIRC as OFF for sector under test.Alarms reported previously are cancelled. Sectorcomes to WO state.

BCCH transmission of sector under test ischecked using Spectrum Analyser.

BCCH transmission of test sector can be seenon Spectrum Analyser.

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

Test steps two to eight are repeated for thesecond sector.

Results obtained are same as output two toeight.

Test case is repeated for both the sectors withoutBB hopping.

Identical results are obtained.

Case Ref. Configuration Hopping Mode

1 2+2 GSM (1800) BB, both sectors

DN06103498 Issue 2-0


MENU




Site is configured as per the test case. Site is in supervisory state with no active alarmsreported at both BSC and BTS manager exceptfor ‘Alarm 7801: MMI connected to BaseStation’.

For test case 2 spectrum Analyser is connected to TRX9, 10, 11 & 12 and for test case 3 it isconnected to TRX 5,6,7, & 8

Transmission is observed on the BCCH timeslotfor TRX 9 for test case 2 and for TRX 5 for testcase 3 on spectrum Analyser.

Speech calls are made on all the TRXs of theconcerned BTS.


STIRC is enabled on Sector 3 (GSM Sector) using“ZEQM: BTS=<btsno>: STIRC=Y;” command fromBSC.

"BTS_CONF_DATA is sent to BTS by BSCcontaining STIRC mode as enabled.Alarm 7606 of 'TRX faulty' is reported for TRX 9,10 & 11 and these TRX are in BL-TRX state at

BSC and BTS Manager after reconfiguration.Alarm 7603 of 'BTS faulty' is reported for thirdsector & BTS is in BL-BTS state at BSC andBTS Manager.

Transmission is observed on the SpectrumAnalyser.

It is observed that the BCCH after re-configuration is not transmitting on BCCHchannel, verified on Spectrum Analyser.

Input 1, 2 and 3 are repeated for the first sector BCF and all TRXs are in WO-EX state at BSCand in Supervisory state at BTS Manager.

No active alarms are reported at both BSC andBTS manager except for ‘Alarm 7801: MMI

connected to Base Station’.

Speech calls are made on all the TRXs of theconcerned BTS.

Speech call is successful

Input 1, 2 and 3 are repeated for the secondsector.

Alarm 7606 “Non-EDGE TRX device type usedaccidentally in EDGE capable mode” is reportedon BTS Manager and at BSC for the GSM TRXsand these TRXs goes to BL-TRX state at BSCand BTS Manager after reconfiguration. Alarm7705 LAPD FAILURE is reported at the BSC forthe GSM TRXs. The remaining EDGE TRXs return to the WOstate.

Speech calls are made on all working TRXs of theconcerned BTS.


Case Ref. BCF Configuration BCCH

2 4(EDGE)+4(GSM/EDGE)+4(GSM) TRX9

3 4(EDGE)+4(GSM/EDGE)+4(GSM) TRX5

DN06103498 Issue 2-0


MENU




Site is configured as per the test case. Site is in supervisory state with no activealarms reported at both BSC and BTSmanager except for ‘Alarm 7801: MMIconnected to Base Station’..

STIRC is enabled in the first sector and BCCHtransmission is monitored using a spectrum analyser.

Alarm 7606 "TRX FAULTY: Non EDGE TRX device type used accidentally in EdgeCapable Mode" is reported for TRX 1 bothat BSC and BTS Manager and this TRX isin BL-TRX state at BSC.

Alarm "7603 BTS FAULTY: Non EDGE

TRX device type used accidentally in EdgeCapable Mode" is reported both at BSC andBTS Manager after some time. The BTSand BCCH TRX are in BL-BTS state atBSC.

BCCH transmission from the sector undertest is stopped after some time.

Non BCCH TRX of the first sector is blocked from BTSManager and monitor BCCH transmission using aspectrum analyser.

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

BCCH transmission from the first sector is kept under

observation for next few minutes.

There shall be no transmission from the

sector under test.

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

Make calls on all the sectors. All calls are successful


4 2+2 GSM


Site is configured as per the test case. Site is in supervisory state with no activealarms reported at both BSC and BTSmanager except for ‘Alarm 7801: MMIconnected to Base Station’.

DN06103498 Issue 2-0


MENU




STIRC is enabled in the first sector using MMLcommand ZEQM.

STIRC gets enabled in the sector under test.

Alarm “7606 TRX FAULTY: Non EDGE TRXdevice type used accidentally in EDGECapable Mode.” is raised for the first TRX inthe sector under test both at BTS Manager aswell as at BSC.

After some time alarm “7603 BTS FAULTY:Non EDGE TRX device type used accidentallyin Edge Capable Mode.” is also raised for thesector under test both in BTS Manager as wellas in BSC.

In BSC the sector under test as well as its TRXs goes to blocked state.

In BTS Manager Traffic Trace is opened: using Tests ->TRX Traffic Trace and the TRX number of the BCCH TRX is selected.

The BCCH TRX shows no transmission, whichcan be confirmed by a spectrum analyser.

STIRC is disabled in the first sector using MMLcommand ZEQM.

STIRC gets disabled in the sector under test.

The alarms 7606 and 7603 get cancelled bothat BTS Manager as well as at BSC.

The sector under test and its TRXs come toworking state.

In BTS Manager Traffic Trace is opened: using Tests ->TRX Traffic Trace and the TRX number of the BCCH TRX is selected.

The BCCH TRX shows transmission in TS 0which can be confirmed by a spectrumanalyser.

Establish calls in the first sector. Calls are successfulIn BTS Manager Traffic Trace is opened: using Tests ->TRX Traffic Trace and the TRX number of the TRXs on which calls are ongoing are selected.

The TRX shows transmission in thecorresponding TS where the call is going onwhich can be confirmed by a spectrumanalyser.

BCF ConfigurationCase Ref.

5 2+2 GSM, 1800 band with BB Hopping

11.2 STIRC handl ing wi th EDGE sector

Purpose:

The purpose of this test case is to verify that ongoing calls in a site are not disturbed,when STIRC is enabled after BCCH reconfiguration.


Site is configured as per the test case. Site is in supervisory state with no active alarmsreported at both BSC and BTS manager exceptfor ‘Alarm 7801: MMI connected to Base Station’.

DN06103498 Issue 2-0


MENU




LAPD signalling for the BCCH TRX is blockedfrom the BSC.

Alarm’ 7705: LAPD failure’ is raised for theBCCH TRX. BCCH TRX goes into BL-RSL state.BCCH is reconfigured.

LAPD signalling of the former BCCH TRX isunblocked.

Alarm’ 7705: LAPD failure’ gets cancelled for the TRX and TRX comes to WO state.

Speech calls are established on all the TRXs andremain ongoing for the duration of the test case.

All calls are established successfully

STIRC is enabled for the BTS. STIRC gets enabled successfully. All callsremain ongoing.

STIRC is disabled for the BTS. STIRC gets disabled successfully. All calls

remain ongoing.Ongoing calls are disconnected and new set of calls on all the TRXs.


Alarms are checked both at BSC and BTSManager.

There are no active alarms reported at both BSCand BTS manager except for ‘Alarm 7801: MMIconnected to Base Station’..

ConfigurationCase Ref

6 4 Omni, EDGE


Site is configured as per the test case with RDIVand UL DTX disabled.

The site is in supervisory state with no activealarms reported at both BSC and BTS managerexcept for ‘Alarm 7801: MMI connected to BaseStation’.

LAPD signalling for the BCCH TRX is blockedfrom the BSC.

Alarm’ 7705: LAPD failure’ is raised for theBCCH TRX. The BCCH TRX goes into BL-RSLstate.BCCH is reconfigured.

LAPD signalling of the former BCCH TRX isunblocked.

Alarm’ 7705: LAPD failure’ gets cancelled for the TRX and TRX comes to WO state.

AFS and AHS calls are established on all TRXs inthe BTS and remain ongoing for the duration of the test case.


RDIV and UL DTX are enabled for the BTS. RDIV and UL DTX are enabled in the BTS. The calls remain unaffected.

RDIV and UL DTX is disabled for the BTS. RDIV and UL DTX are disabled in the BTS. The calls remain unaffected.

AMR codecs for both HR and FR calls are

changed for the sector from the BSC.

AMR codecs settings are changed for the BTS

successfully.All calls remain unaffected.

DN06103498 Issue 2-0


MENU




PMAX of the BTS is changed using ZEUGcommand.

The calls remain unaffected.

The value of RXDL is changed for the BCF undertest.

The calls remain unaffected.

All calls are disconnected and new set of calls areestablished on all TRXs.


Alarms are checked at BSC and BTS Manager. There are no active alarms reported at both BSCand BTS manager except for ‘Alarm 7801: MMIconnected to Base Station’.

Case Ref BTS Configuration Hopping

7 8 Omni, EDGE RF


Site is configured as per the test case. The site is in supervisory state with no activealarms reported at both BSC and BTS managerexcept for ‘Alarm 7801: MMI connected to BaseStation’.

The intelligent shutdown with both timers isactivated for the NONE Shutdown mode.

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

Command is successfully executed.

Mains breakdown alarm is generated. Alarm “7995 MAINS BREAKDOWN WITHBATTERY BACK-UP” is reported on BTSManager & BSC. Site enters NONE shutdownstate after expiry of BTIM.

STIRC & RDIV are enabled in all the sectorsusing ZEQM:BTS=<BTS ID>:STIRC=Y,RDIV=Y;

STIRC and RDIV are successfully enabled.“BTS_CONF_DATA” is sent to BTS by BSCcontaining STIRC as ON for the sectors undertest.

BCCH transmission for sectors under test ischecked using Spectrum Analyser.


LAPD status of all the TRXs is checked on BSC. LAPD for all TRXs are in blocked state.Mains breakdown alarm is cancelled. Mains breakdown alarm is cancelled and all

TRXs come into working stateCalls are made on all TRXs of the sectors undertest

Calls are successful on all TRXs.

Test case is repeated by disabling STIRC in eachsector.


Case Ref. BCF Configuration Hopping Preferred BCCH TRX

8. 4+4+4 EDGE RF+NoHopping+RF

One, Five, Nine

DN06103498 Issue 2-0


MENU



BCCH

3 4

1 6

7 8

5

BTS2BTS1

LMU

BCF 1

MASTER

SLAVE

SEGMENT

BTS3

BTS 3 (not in sync chain)

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

ADJACENT BCF

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

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

LMU – MetroSite – MetroSite + Neighbour

Figure 2.

DN06103498 Issue 2-0


MENU



Disclaimer

The information in this document is subject to change without notice and describesonly the product defined in the introduction of this documentation. This documentationis 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 writtenpermission of Nokia Siemens Networks. The documentation has been prepared to beused by professional and properly trained personnel, and the customer assumes fullresponsibility when using it. Nokia Siemens Networks welcomes customer commentsas part of the process of continuous development and improvement of thedocumentation.

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 productsshall be defined conclusively and finally in a separate agreement between NokiaSiemens Networks and the customer. However, Nokia Siemens Networks has madeall reasonable efforts to ensure that the instructions contained in the document areadequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not becovered 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 ANYLOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE,

BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected bycopyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registeredtrademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

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

Copyright ©Nokia Siemens Networks 2009. All rights reserved.

MENU

cxm7 system regression specification

Documents