Test Specification for Features Dn0749988 2-0 En

DN0749988 Issue 2-0 en 18/01/2008

© Nokia Siemens Networks

1 (381)

Nokia Flexi EDGE Base Station

Test Specification for Features BTS SW EP1.1

Test Specification for Features

2 (381) © Nokia Siemens Networks

DN0749988Issue 2-0 en18/01/2008

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

Contents

DN0749988 Issue 2-0 en 18/01/2008


3 (381)

Contents

1 About this document .............................................................................7 1.1 Document structure..................................................................................7 1.2 Common aspects of test execution and configuration..............................7

2 Flexi EDGE BTS Features......................................................................9 2.1 Base Stations ...........................................................................................9 2.1.1 BTS Time Base Reference from PCM .....................................................9 2.2 Base Station Controller ..........................................................................13 2.2.1 Discontinuous Reception (DRX).............................................................13 2.2.2 Ciphering................................................................................................17 2.2.3 Call Release after Loss of TRAU Frame Synchronisation .....................21 2.2.4 Mode Modify Procedure .........................................................................22 2.3 Radio Network Performance ..................................................................26 2.3.1 Synthesised Frequency Hopping ...........................................................26 2.3.2 Antenna Hopping ...................................................................................30 2.3.3 Dynamic Frequency Channel Allocation ................................................35 2.3.4 Half Rate ................................................................................................40 2.3.5 Adaptive Multi Rate Codec.....................................................................42 2.3.6 Active/Idle Channel Interference Estimation ..........................................49 2.3.7 Downlink And Uplink DTX ......................................................................53 2.3.8 Handover and Power Control Algorithms...............................................56 2.3.9 Enhanced Measurement Report ............................................................64 2.3.10 Air Interface Measurement Pre-processing............................................71 2.3.11 Enhanced Automatic Frequency Correction...........................................73 2.3.12 CCCH Improvements .............................................................................76 2.3.13 Support for Different Training Sequence Codes (TSC)..........................80 2.3.14 Intelligent Frequency Hopping (IFH) ......................................................83 2.3.15 FACCH Call Setup .................................................................................85 2.3.16 Base Band Frequency Hopping .............................................................88 2.3.17 Dynamic SDCCH Allocation ...................................................................91 2.3.18 BSS Site Synchronisation Recovery Improvement ................................94 2.4 Data......................................................................................................101 2.4.1 General Packet Radio Service (GPRS)................................................101 2.4.2 Dual Transfer Mode .............................................................................105 2.4.3 14.4 kbit/s GSM Data Services ............................................................107 2.4.4 Dynamic Abis Allocation.......................................................................109 2.4.5 GPRS: Coding Schemes CS-3 and CS-4 ............................................113 2.4.6 EGPRS P-Channel Required (EPCR)..................................................115 2.4.7 Enhanced General Packet Radio Service (MCS 1-9) ..........................117 2.4.8 High Speed Circuit Switched Data (HSCSD) .......................................123 2.5 Macrocellular ........................................................................................126 2.5.1 RX Antenna Diversity ...........................................................................126 2.5.2 Multi BCF Control .................................................................................131 2.5.3 Common BCCH and Dual/Tri-band Operations ...................................135 2.5.4 Mast Head Pre-Amplifier ......................................................................140



DN0749988Issue 2-0 en18/01/2008

2.6 Microcellular ........................................................................................ 146 2.6.1 MS Speed Detection............................................................................ 146 2.7 Operability ........................................................................................... 149 2.7.1 Transmission Control: Alarm Handling via LAPD ................................ 149 2.7.2 Intelligent Shutdown for Flexi EDGE BTS ........................................... 151 2.7.3 Autodetection....................................................................................... 158 2.7.4 External Battery Back Up Unit Support ............................................... 166 2.7.5 BTS External Alarms and Controls...................................................... 168 2.7.6 TRX Test ............................................................................................. 172 2.7.7 BTS Local Blocking ............................................................................. 177 2.7.8 Forced Handover for O&M Reason ..................................................... 188 2.7.9 Abis Loop Test..................................................................................... 189 2.7.10 RX Antenna Supervision by Comparing RSSI..................................... 196 2.7.11 Remote Flexi EDGE BTS Manager ..................................................... 201 2.7.12 Modification of BCF Parameters by Append Commissioning.............. 208 2.7.13 BTS Object Control.............................................................................. 211 2.7.14 BTS Supervision.................................................................................. 220 2.7.15 Temperature Control System .............................................................. 239 2.7.16 Runtime Diagnostics and BTS Alarms ................................................ 242 2.7.17 Real Time Update to the BTS.............................................................. 252 2.7.18 BTS SW Background Downloading..................................................... 253 2.7.19 TX Antenna VSWR Supervision .......................................................... 260 2.8 Transmission ....................................................................................... 267 2.8.1 Transmission Fault Management ........................................................ 267 2.8.2 Abis Loop Protection ........................................................................... 271 2.8.3 Transmission Management ................................................................. 282 2.8.4 Transmission Performance Management............................................ 292 2.8.5 Transmission Support for Abis Signalling............................................ 294 2.8.6 Satellite Abis........................................................................................ 299 2.8.7 Support for Nokia Microwave Radio Links........................................... 304 2.9 Value Added Services ......................................................................... 307 2.9.1 Enhanced Full Rate Codec.................................................................. 307 2.9.2 Short Message Service Cell Broadcast with DRX ............................... 308 2.9.3 Short Message Service (SMS) Point-to-Point ..................................... 310 2.9.4 Short Message Cell Broadcast ............................................................ 317 2.9.5 Remote Interrogation of Serial and Version Numbers......................... 319

3 Flexi EDGE BTS Maintenance .......................................................... 327 3.1 Flexi EDGE BTS Module Replacement............................................... 327 3.1.1 BTS Unit Replacement ........................................................................ 327 3.1.2 Transmission Units Replacement........................................................ 336 3.1.3 Auxiliary Power Supply Unit Replacement .......................................... 340

4 Flexi EDGE BTS Site Installation ..................................................... 343 4.1 Flexi EDGE BTS Site Commissioning ................................................. 343 4.1.1 BTS Site Expansion............................................................................. 343 4.1.2 BTS Site Commissioning..................................................................... 350 4.2 Flexi EDGE BTS Software Deployment .............................................. 367

Contents

DN0749988 Issue 2-0 en 18/01/2008


5 (381)

4.2.1 Software Package Creation and Storage.............................................367 4.2.2 Software Release Upgrade/Fallback....................................................370



DN0749988Issue 2-0 en18/01/2008

About this document

DN0749988 Issue 2-0 en 18/01/2008


7 (381)

1 About this document This document incorporates the functional test phase and defines the test cases for verifying features of the BTS software release EP1.1 for Nokia Flexi EDGE Base Station. The purpose is to verify that the BTS configured with the features works as specified.

1.1 Document structure

This document is sectioned into major testing views: Flexi EDGE BTS Feature, Flexi EDGE BTS Maintenance Action, and Flexi EDGE BTS Site Installation. Within each of these sections, there are high level functional testing descriptions. These areas are then structured in the following way:

• A brief description of the feature or functional area

• A table detailing the test case titles executed and any variations in BTS configuration or parameters. Note that a test case may appear multiple times in the table with different configurations and / or parameters.

• The subsequent subsections contain the test case descriptions and steps.

1.2 Common aspects of test execution and configuration

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

• Any Flexi EDGE BTS configuration, as there is no dependency



DN0749988Issue 2-0 en18/01/2008

• As a precondition the Flexi EDGE BTS site has been successfully commissioned, connected to the BSC and all TRXs are in working state and without any unknown alarms or faults.

• Receive Diversity is enabled in the BSC (RDIV=Y.)

• RF Hopping is enabled for all BTS objects

Standard test equipment • GSM Abis Analyser

BSS Network Element • Nokia BSC S12 with latest CD release

Flexi EDGE BTS Features

DN0749988 Issue 2-0 en 18/01/2008


9 (381)

2 Flexi EDGE BTS Features The section covers the verification of the main features of Flexi EDGE BTS SW release EP1.1.

2.1 Base Stations

2.1.1 BTS Time Base Reference from PCM

Overview The Clock Unit (OCXO) of the Flexi EDGE BTS can be adjusted according to the frequency of the incoming PCM signal. A reference signal, extracted from the PCM is used for adjusting the output of the OCXO to produce 13 MHz for the BTS internal timing. This is not a phase-locked loop but a longer term averaging type of adjustment, the 13 MHz output is adjusted every 20 minutes based on the incoming PCM signal. The requirement for the PCM is ± 0.015 ppm in order to meet GSM requirements 0.05 ppm for clock accuracy at the Air interface. Because the tuning period is so long, a special fast tuning method is available in Flexi EDGE BTS for commissioning purposes.

If BTS detect the significant degradation in PCM clock, greater than 5 Hz against PCM frequency of Abis clock source, an alarm (7601, Major Alarm) is generated. When PCM signal becomes again good, the tuning is resumed after hysteresis timeout (1 minutes) and the alarm is cancelled.

The tuning can be controlled per site with the Flexi EDGE BTS Manager. If tuning is not used, then the master clock output is based solely on the oven oscillator. Also, if the incoming PCM is not accurate enough to tune the OCXO, the tuning is stopped.



DN0749988Issue 2-0 en18/01/2008

Scope of testing The scope of the testing is to verify that when incoming PCM reference is good, the BTS tunes the OCXO to generate an accurate 13 MHz signal (+/-.02ppm). Also in case of Abis degradation, OCXO tuning is stopped and alarm is reported by BTS and cancelled when PCM reference is good again.

Configuration

Item Details

Synchronisation Priority Priority 1 Interface 1

Priority 2 Internal Timing Settings None.

Test cases

Pos Name Comment

1 BTS Time Reference from PCM Any BTS configuration, FIPA, T1 line

2 BTS Time Reference from PCM Any BTS configuration, FIEA

3 BTS Time Reference from PCM Any BTS configuration, FIFA

4 Frequency deviation in the incoming PCM signal

Any BTS configuration, FIPA, E1 line

2.1.1.1 BTS Time Reference from PCM

The purpose of this test is to verify that Flexi EDGE BTS supports adjustment of its OCXO against the reference PCM clock. Adjustment allows OCXO tuning for a maximum of +/-7 DAC Word steps within a measurement period of about 20 minutes in case of phase difference between OCXO and incoming PCM clock.

Test environment Hardware tools

• Frequency counter - The counter should have a stable reference clock source from external 10 MHz Oscillator or GPS receiver

Test case execution Pre-setup:


DN0749988 Issue 2-0 en 18/01/2008


11 (381)

1. During commissioning line interfaces are configured and fast tuning has taken place.

2. Flexi EDGE BTS Manager is connected to the BTS Site via local connection.

3. To measure the "13 MHz Test Output Clock", connect the frequency counter at the SYNC OUT connector (Pin 8 (GND) and 11) of the ESMA.

Step Input Expected output

1 Verify the clock sync state and the oscillator state in the BCF properties view in Flexi EDGE BTS Manager. Also verify the "Clock Control" view at Flexi EDGE BTS Manager. ("Clock Control" View is under Menu item "BTS Control")

Monitor the current and calibrated DAC word in the "Clock Control" view at Flexi EDGE BTS Manager.

The oscillator status is shown as ready and the clock sync state is in independent mode in the BCF properties view as well as the clock control view at Flexi EDGE BTS Manager.

The current and calibrated DAC word should be the same just after the start-up.

2 Monitor the current DAC word for 1 hour in the "Clock Control" view at Flexi EDGE BTS Manager. Allow the DAC word to stabilise.

The current DAC word becomes stable and does not change for 1 hour.

If the current DAC word changes, repeat step 2, until the current DAC word becomes stable.

3 Monitor the current DAC word in the "Clock Control" view at Flexi EDGE BTS Manager and 13 MHz frequency at the frequency counter.

DAC/13MHz does not show any difference from the PCM line.

4 Check the frequency and the swing of it over a period of 6 hours at the frequency counter.

13 MHz clock should remain within the accuracy limit (+/- .02PPM).

5 Now increase the value by 100 steps from the current value with Flexi EDGE BTS Manager.

- Select “BTS Control” ”Clock Control” menu item from main menu at Flexi EDGE BTS Manager

- Enter the desired DAC word

- Press the "Make Current" button

Also monitor the 13 MHz frequency at the frequency counter.

The current DAC word value gets updated in the Flexi EDGE BTS Manager clock control view.

13 MHz clock drifts towards higher value by increasing the DAC word.

6 Monitor the current DAC word in the "Clock Control" view at Flexi EDGE BTS Manager after every 20 minutes.

The current DAC word changes by maximum of 7 steps towards the noted DAC value in step 4 in every 20 minutes, until it reaches a stable value.



DN0749988Issue 2-0 en18/01/2008


Also write down the value of the calibrated DAC word.

Also monitor the 13 MHz frequency at the frequency counter.

The calibrated DAC word is updated every time the current DAC word value changes, so that the difference between them remains less than or equal to 11 steps.

During tuning, the clock should move towards 13 MHz and after the tuning is completed, the 13 MHz again should be stable within the accuracy limit (+/- .02PPM).

7 After the current DAC word reaches the stable value, monitor the current and calibrated DAC word value for 1 hour.

The current and calibrated DAC word values remain stable and do not change.

8 Measure the frequency and the swing of it over a period of 6 hours at the frequency counter.

13 MHz clock should remain within the accuracy limit (+/- .02PPM).

9 Now decrease the value by 100 steps from the current value through Flexi EDGE Manager.

The current DAC word value gets updated in the Flexi EDGE Manager clock control view.

13 MHz clock drifts towards lower value by decreasing the DAC word.

10 Repeat steps 6, 7 and 8. The output is the same as mentioned above.

2.1.1.2 Frequency Deviation in the Incoming PCM Signal

The purpose of this test case is to verify the BTS functionality when there is a significant degradation (more than 5 Hz) in the reference PCM signal.

Test environment Hardware tools:

• Data channel simulator

• External signal generator

• Frequency counter

The counter should have a stable reference clock source from an external 10 MHz oscillator or GPS receiver.


1. The OMUSIG link to the BSC is established.

2. OCXO is available and has warmed up.


DN0749988 Issue 2-0 en 18/01/2008


13 (381)

3. A data channel simulator is used in Abis (between the BSC and BTS).

4. To measure the ‘13 MHz Test Output Clock’, connect the frequency counter at the SYNC OUT connector (Pin 8 (GND) and 11) of the ESMA.


1 Measure and note down the 13 MHz test clock frequency.

2 Create > 5 Hz frequency errors to Abis with Data Channel Simulator.

Check the alarms in the alarm window at Flexi EDGE BTS Manager.

BTS detects at least 5 Hz difference.

7601 Major alarm “BCF operation degraded, difference between PCM and BTS frequency ref” is present.

3 Check oven tuning state at Flexi EDGE BTS Manager (by viewing the BCF properties in the Base Station View).

Oven tuning state is disabled.

4 Check the alarms on the BSC using MML command (ZEOL:<bcf_no>;).

7601 Major alarm “BCF operation degraded, difference between PCM and BTS frequency ref” is present.

5 Measure the frequency and the swing over a period of 1 hour at the frequency counter.

The 13 MHz clock should remain stable and it should show any change from the 13 MHz test clock value read in step 1.

6 Adjust the Abis frequency back to the original with Data Channel Simulator (set signal generator frequency back to used PCM).

Check the alarms in the alarm window at Flexi EDGE BTS Manager after 1 minute.

BTS detects the re-adjusted Abis frequency.

7601 Major alarm “BCF operation degraded, difference between PCM and BTS frequency ref” disappears.

7 Check oven tuning state at Flexi EDGE BTS Manager (by viewing the BCF properties in the Base Station View).

Oven tuning state is enabled again.

8 Check the alarms on BSC using MML command (ZEOL:<bcf_no>;).

7601 Major alarm “BCF operation degraded, difference between PCM and BTS frequency ref” is not present.

2.2 Base Station Controller

2.2.1 Discontinuous Reception (DRX)

Overview



DN0749988Issue 2-0 en18/01/2008

A mobile in idle mode is paged in order to establish a mobile-terminated call or to deliver a mobile-terminated SMS. The mobile thus needs to monitor the downlink paging channels on the CCCH. As there a number of PCH channels, in the simplest scheme, an MS must read all the PCH channels to know whether there is a paging message sent by the BSC for it or not. This involves a lot of power consumption for the mobile. In order to reduce the power consumption, paging groups are defined and a mobile listens to the paging sub-channels corresponding to its paging group. The mobile is then said to work in Discontinuous Reception (DRX) mode. Here, DRX refers to means where the MS listens to the paging channels discontinuously.

The BSC calculates the correct paging group for a paging message according to the IMSI of the subscriber being paged. This group number is added to the paging message sent to the BTS. The BTS then schedules this paging message for transmission over the air interface in the correct paging group as commanded by the BSC. This feature enables mobiles to listen to their own paging group only and thus prolongs battery lifetime considerably.

The GSM specifications allow multiple timeslots of BCCH frequency (TS 0, 2, 4, 6) to carry paging messages. However, Nokia BSS supports only one CCCH timeslot (Timeslot 0).

The BSC sends Paging Command to the BTS. The BTS has the option to pack the paging messages whereby one to four MSs can be paged using a single paging message on the air interface. The Flexi EDGE BTS supports all paging request types 1, 2, and 3. This allows an efficient use of the downlink CCCH as several mobiles can be paged by one message.

Scope of testing Scope of testing is limited to observing the Paging command on test mobiles where there is no mobile terminating call. Additionally, for a mobile terminated call, the Paging Command on the Abis and the corresponding response of the MS is observed.

Configuration

Item Details

Site Configuration 6 + 6

Frequency Band 900 band in one sector, 1800 in another sector

Channel Configuration

Sector 1:

BCCH TRX: MBCCH + SDCCH/8 + 6 TCH/D

Non_BCCH TRXs: 8 TCH/D

Sector 2:

BCCH TRX: MBCCHC + SDCCH/8 + 6 TCH/D


DN0749988 Issue 2-0 en 18/01/2008


15 (381)

Item Details


Settings 1. Number of Access Grant Blocks in a 51-frame multiframe. >>>ZEQJ:BTS=<bts_id>:AG=<BS_AG_BLKS_RES >;

DECIMAL NUMBER 0 ... 7 (IF COMBINED BCCH NOT USED)

1 ... 7 (IF CBCH USED AT SDCCH/8)

0 ... 2 (IF COMBINED BCCH USED)

2. Number of 51-frame multiframes after which the paging cycle repeats itself.

>>>ZEQJ:BTS=<bts_id>:MFR=<BS_PA_MFRMS >;

RANGE: DECIMAL NUMBER 2 ... 9

Additional Information 1. Format of Dummy Paging Message (message sent on PCH when

no valid paging message is available) is as follows: 0x15, PROT_DISC_AND_TRA_ID (0x06),

RR_PAGING_REQ_1(0x21), RR_NORMAL_PAGE_MODE (0x00),

0x01, 0xF0, FILL_BITS, FILL_BITS, FILL_BITS, FILL_BITS, FILL_BITS,

FILL_BITS, FILL_BITS, FILL_BITS, FILL_BITS, FILL_BITS, FILL_BITS,

FILL_BITS, FILL_BITS, FILL_BITS, FILL_BITS, FILL_BITS, FILL_BITS

(Where FILL_BITS = 0x2B)

2. For the details of Paging Group calculation, refer 3GPP TS 45.002.

Test cases

Pos Name Comment

1 Testing DRX Behaviour for Combined/Non-combined BCCH

6+6, BB hopping

2.2.1.1 Testing DRX Behaviour for Combined/Non-combined BCCH

The objective of the test case is to verify the DRX behaviour with both combined and non-combined channel combination.


• Air interface monitor mobile



DN0749988Issue 2-0 en18/01/2008


1. Sector 1 is configured with non-combined BCCH (MBCCH).

2. Sector 2 is configured with combined BCCH (MBCCHC).

3. Set AG and MFR for Sector 1 so that there are a total of 24 paging groups (AG=3, so PCH = 9 – 3 = 6, MFR = 4, Total Paging Groups = 6*4 = 24. >>>ZEQJ:BTS=<bts_id>:AG=<BS_AG_BLKS_RES >;


4. Set AG and MFR for Sector 2 such that there are a total of 6 paging groups (AG=1, so PCH = 3 – 1 = 2, MFR = 3, Total Paging Groups = 2*3 = 6. >>>ZEQJ:BTS=<bts_id>:AG=<BS_AG_BLKS_RES >;


5. Give a site reset to the BTS using Flexi EDGE BTS Manager. All the Logical objects (BCF, BTS, TRX) should come up in supervisory state.

6. Check active alarms at the BSC with MML command ZEOL; No unexpected alarms are present that indicate a hardware or software problem.


1 Switch on the “Air interface monitor mobile” and latch in on sector 1 BCCH frequency. Observe RR messages on the Signalling Information logs.

Also observe the GSM Abis analyser.

On the “Air interface monitor mobile”, dummy-paging messages are seen (see test plan for message details). This message is seen on the PCH that corresponds to the paging group of the IMSI of the monitoring mobile.

On GSM Abis analyser, no paging message is seen (as there is no call related activity).

(Note that depending upon the Monitoring mobile capability, it may be possible that some mobiles show additional paging messages apart from those received on their own paging channel.)

2 Now use another test mobile to call the “Air interface monitor mobile”.

Paging Command is seen on the Abis analyser with the Paging group corresponding to the IMSI of the “Air interface monitor mobile”. The Paging group in the message should correspond to the IMSI of the MS being paged.

The Paging response is seen and the call is connected successfully.


DN0749988 Issue 2-0 en 18/01/2008


17 (381)


3 Repeat steps 1and 2 but on sector 2 BCCH frequency.

Same as in steps 1 and 2. However, as the two sectors have different paging blocks, the paging group of the same mobile will be different in sector 2. For all paging messages, the Paging group in the message should be corresponding to the IMSI of the MS being paged.

4 Repeat the steps above for 5 pairs of calls (1MO+1MT) each, on sectors 1 and 2 with different IMSIs.

There should be different paging groups seen in the Paging group corresponding to the IMSI of the MS being paged.

The paging group should lie within the maximum paging group of each sector.

2.2.2 Ciphering

Overview Ciphering is one of the security procedures defined to protect subscriber identity and data. When Ciphering is active, all information exchanged between the mobile and the network on the dedicated radio channels is encrypted. The key previously set between the network and the MS is used to encipher and to decipher the encrypted information. During the authentication procedure in which the identity provided by the MS is checked to prevent unauthorised use, the ciphering key Kc is set between the network and the MS.

The feature enables the usage of different A5 algorithms (currently A5/1) and gives an alternative of using no ciphering at all (A5/0). The user cannot set the ciphering mode. MSC has although the possibility to indicate to BSS all ciphering algorithms. The selection of the ciphering algorithm used is based on a BSS level system parameter, which determines the allowed algorithms and their fixed preference. The operator is not able to change the reference, which currently is A5/1 first and then A5/0. For the BTS, two different software packages will be available: A5/1,0 packet and A5/0 packet. In the BSC, the ciphering method must specified in the software package in the customer specific data.

Scope of testing Scope of testing is limited to testing ciphered call using A5/1 and testing unciphered call using A5/0. This is done using two packages A5/1 and A5/0.

Note: A5/2 ciphering algorithm support is not supported in Flexi EDGE BTS.

Settings



DN0749988Issue 2-0 en18/01/2008

1. List all software builds available on the BSC. >>>ZEWL;

2. Attach the SW build to the BCF. >>>ZEWA:<bcf_id>:<partition_detail>:<build_name>;

3. Activate the SW build. >>>ZEWV:<bcf_id>:<partition_detail>;

4. Allow A51 Ciphering from the MSC. >>> ZMXN:NAME=NOKIA:::::NOCIPH=N,A51=Y,:CIPH=Y:;

5. Disallow Ciphering from the MSC. >>>ZMXN:NAME=NOKIA:::::NOCIPH=Y,A51=N,:CIPH=N:;

Test cases

Pos Name Comment

1 Testing A5/0 and A5/1 Algorithm with A5/1 BTS Package

--

2 Testing A5/0 Algorithm with A5/0 BTS Package

--

2.2.2.1 Testing A5/0 and A5/1 Algorithm with A5/1 BTS Package

The objective of the test case is to verify that procedures like location update/voice calls can be performed using the A5/1 and A5/0 algorithms with the A5/1 BTS package.


1. Define the A5/1 encryption algorithm at the MSC using the MML command ZMXN. >>> ZMXN:NAME=NOKIA:::::NOCIPH=N,A51=Y,:CIPH=Y:;

2. Attach the software build A5/1 for the BCF at the BSC using the MML command ZEWA and activate it using the MML command ZEWV: >>>ZEWA:<bcf_id>:<partition_detail>:<build_name>;

>>>ZEWV:<bcf_id>:<partition_detail>;

3. Give a site reset to the BTS using Flexi EDGE BTS Manager. All the logical objects (BCF, BTS, and TRX) should come up in supervisory state.


DN0749988 Issue 2-0 en 18/01/2008


19 (381)




1 Power off an MS and switch it on.

Verify Ciphering algorithm in the “Encryption Command” message on the GSM Abis analyser.

In the downlink direction, the Encryption Command indicates ciphering algorithm - GSM A5/1.

In the uplink direction, the Cipher Mode Complete message is seen indicating the successful setting of cipher mode context.

The location update procedure is successful, as the MS has latched on to the BCCH frequency.

2 Initiate an MS-MS call.

Observe the “Encryption Command” message on the GSM Abis analyser.

In the downlink direction, the Encryption Command indicates ciphering algorithm - GSM A5/1.

In the uplink direction, the Cipher Mode Complete message is seen, indicating the successful setting of cipher mode context.

The voice call is established successfully.

The voice quality is good without disturbances or cracking sound.

3 Terminate the call. The voice call is released.

4 Change the setting at the MSC and remove ciphering support.

Now repeat steps 1 to 3.

In both cases above, the procedure is successful.

The encryption command is either not seen, or it is seen with algorithm A5/0 (indicating no ciphering).

2.2.2.2 Testing A5/0 Algorithm with A5/0 BTS Package

The objective of the test case is to verify that procedures like location update/voice calls can be performed using the A5/0 algorithm with the A5/0 BTS package.


1. Remove ciphering support at the MSC using the MML command ZMXN.



DN0749988Issue 2-0 en18/01/2008

>>>ZMXN:NAME=NOKIA:::::NOCIPH=Y,A51=N,:CIPH=N:;

2. Attach the software build A5/0 for the BCF at the BSC using the MML command ZEWA and activate it using the MML command ZEWV. >>>ZEWA:<bcf_id>:<partition_detail>:<build_name>;

>>>ZEWV:<bcf_id>:<partition_detail>;


4. Check the active alarms at the BSC with the MML command ZEOL; No unexpected alarms are present that indicate a hardware or software problem.


1 Power off an MS and switch it on.

Verify the Ciphering algorithm in the “Encryption Command” message on the GSM Abis analyser.

In the downlink direction, the Encryption Command is either absent or, if present, it indicates ciphering algorithm - GSM A5/0.

In the uplink direction, the Cipher Mode Complete message is either absent or, if present, it indicates the successful setting of cipher mode context.

The location update procedure is successful, as the MS has latched on to the BCCH frequency.

2 Initiate an MS-MS call.

Observe the “Encryption Command” message on the GSM Abis analyser.

In the downlink direction, the Encryption Command is either absent or, if present, it indicates ciphering algorithm - GSM A5/0.

In the uplink direction, the Cipher Mode Complete message is either absent or, if present, it indicates the successful setting of cipher mode context.



3 Terminate the call. The voice call is released.

4 With same BTS SW package, change the setting at the MSC so that A5/1 is enabled using the ZMXN command.

The setting is changed.

5 Now, try location update by switching an MS off and on.

The location update procedure will probably succeed (despite ciphering enabled at the MSC and disabled at the BSS).

6 Now initiate an MS-MS call. The voice call will not be established because the BTS does not support A5/1.


DN0749988 Issue 2-0 en 18/01/2008


21 (381)

2.2.3 Call Release after Loss of TRAU Frame Synchronisation

Overview The BTS sends a connection failure message with cause remote transcoder failure to the BSC, if there is a loss of frame synchronisation between the BTS and the transcoder for over one second. The BSC then releases the call. The reason for the loss of synchronisation can be, for example, a failure in transmission.

The BTS repeats the remote transcoder failure in one-second period until the BSC releases the call or the frame synchronisation is obtained again.

Scope of testing This test plan covers the call release of EFR, AMR/FR and AMR/HR calls because of Loss of Frames Sync between the BTS and the transcoder.

Settings • The BSC specific parameter Number of Ignored Transcoder

Failure message is set to 4: >>> ZEEQ: ITCF=4;

Additional information Cross connect to be used to bypass the Traffic channel (only) and loop it back to the original BTS.

Test cases

Pos Name Comment

1 Checking for Call Release after Loss Of TRAU Frame Synchronisation

EFR


AMR/FR


AMR/HR on both sub-channels

2.2.3.1 Checking for Call Release after Loss of TRAU Frame Synchronisation

The objective of the test case is to verify that when there are Loss of TRAU frames in the downlink (BSC/TRAU to BTS), the BTS informs the BSC regarding this fault continuously through the Connection Failure Indication message until the channel is released.

Test case execution



DN0749988Issue 2-0 en18/01/2008

Pre-setup:

1. Traffic channels of the BTS(s) are cross-connected and looped back to Interface 3 of ESMA and the TRX signalling channel is terminated at Interface 1 of ESMA.


1 Initiate an MS-MS call. The voice call is established successfully. The voice quality is good without disturbances or cracking sound.

2 Remove the cable connected to Interface 3 of ESMA.

Α Connection Failure Indication message with the cause 'Remote Transcoder failure' is seen on the Abis analyser, sent by the BTS repeatedly once every second until the BSC initiates channel release procedure.

At least 4 (No. of Ignored message) + 1 Connection Failure Indication message is seen on the Abis traces before the channel is released.

The channel is successfully released at the BTS.

3 Reconnect the cable removed in step 2. -

4 Establish a call on the same channels that was used in step 1.



2.2.4 Mode Modify Procedure

Overview The purpose of the Mode Modify feature is to modify the channel type within the used TCH. The possible changes are:

• Signalling to speech

• Speech to data

• Data to speech

• Data transmission speed

Scope of testing The scope of testing is limited to verifying the change of the data transmission speed triggered from the BSC. The change of signalling to speech feature is tested in FACCH Call setup. The change of speech to data and data to speech is not tested.

Settings


DN0749988 Issue 2-0 en 18/01/2008


23 (381)

1. To enable HSCSD: >>>ZWOC:10,47,FF;

2. To enable 14.4 kbit/s data services at the BSC: >>>ZWOC:10,48,FF;

Test cases

Pos Name Comment

1 Mode Modify Procedure to change Data Transmission Speed for a data call

2+2+2, By Pass

2 Mode Modify Procedure to change Data Transmission Speed of a Multi-slot HSCSD Call

2+2+2, By Pass

2.2.4.1 Mode Modify Procedure to change Data Transmission Speed for a data call

The objective of the test case is to verify that a Mode Modify procedure is initiated to convert a single slot non-transparent CSD call setup at a data rate of 14.4 kbits/s to a 9.6 kbits/s call when interference is introduced on the air interface.

Test environment Software tools:

• HIT


1. Enable Automatic Link Adaptation at the BSC: >>> ZEUG:BTS=1:AENA=Y;


1 Establish a single slot 14.4 kbps CSD call between the mobile and network.

Set AT commands for establishing a CSD call.

Execute an AT command from Dialup Application Command Mode Window at the originating end.

Execute the following AT commands at the originating end.

AT+CBST = 75, 0, 1

AT+CHSN = 2, 0, 0, 12

Execute ATA command at the terminating end.

Verify that a single slot CSD call is set up at a data rate of 14.4 kbps.



DN0749988Issue 2-0 en18/01/2008


2 Initiate data transfer between the mobile and network.

Verify that the data transfer takes place successfully.

Verify that the throughput is as desired.

3 Introduce interference through signal generator in downlink.

Verify codec changes from 14.4 kbps to 9.6 kbps.

Verify at GSM Abis analyser that the BSC sends “Mode Modify” to BTS for each timeslot part of CSD call with "speech/data codec" 9.6 kbps.

Further verify that the BTS sends “Mode Modify ACK” for all the received Mode Modify messages to the BSC.

Verify at Abis that the BSC sends “Channel Mode Modify” to the MS.

Verify that the MS sends "Channel Mode Modify Ack" to the BSC.

4 Decrease interference through the signal generator in downlink.

Verify codec changes from 9.6 kbps to 14.4 kbps.

Verify the change in throughput for the file transfer.

5 Repeat the increase and decrease of interference on the air interface 5 times.

Verify that the CSD call rate changes to 14.4 kbps when interference is decreased and that it falls down to 9.6 kbps when interference is introduced.

Verify the user throughput during the change of data transmission speeds.

2.2.4.2 Mode Modify Procedure to change Data Transmission Speed of a Multi-slot HSCSD Call

The objective of the test case is to verify that a Mode Modify procedure is initiated to convert a multi-slot non-transparent HSCSD call setup at a data rate of 14.4 kbits/s to a 9.6 kbits/s call when interference is introduced on the air interface.


• HIT


DN0749988 Issue 2-0 en 18/01/2008


25 (381)


1. Enable Automatic Link Adaptation at the BSC: >>> ZEUG:BTS=1:AENA=Y;


1 Establish a multi-slot 14.4 kbps (3+1) HSCSD call between the mobile and network.

Set AT commands for establishing a HSCSD call.

Execute an AT command at the originating Dialup Application Command Mode window.

Execute the following commands at the originating end:

AT+CBST = 81, 0, 1

AT+CHSN = 5, 3, 0, 12

Execute ATA at the terminating end of the Dialup Application Command Mode window.

Verify that a multi-slot HSCSD call is set up at a data rate 14.4 kbps. (3+1 call).

Verify that the BSC sends separate Channel Activation for the primary and the secondary channels.

2 Initiate data transfer between the mobile and network.

Verify that the data transfer takes place successfully.


3 Introduce interference through the signal generator in downlink.

Verify codec changes from 14.4 kbps (3+1) to 96 kbps (3+1).

Verify at GSM Abis analyser that the BSC sends “Mode Modify” to the BTS for each activated channel of the HSCSD call with ‘speech/data codec" 9.6 kbps.

Verify that the BTS sends “Mode Modify ACK” for all the received Mode Modify messages to the BSC.

Verify at Abis that the BSC sends “Configuration Change Command” to the MS.

Verify that the MS sends "Configuration Change ACK" to the BSC.

4 Decrease interference through the signal generator in downlink.

Verify codec changes from 9.6 kbps (3+1) to 14.4 kbps (3+1).

Verify the change in throughput for the file transfer.

5 Repeat the increase and decrease of interference on the air interface 5 times.

Verify that the HSCSD call rate changes to 14.4 kbps when interference is decreased



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output and it falls down to 9.6 kbps when interference is introduced.

Verify the user throughput during the change of data transmission speeds.

2.3 Radio Network Performance

2.3.1 Synthesised Frequency Hopping

Overview Synthesised frequency (RF) hopping is available for configurations that have at least two TRXs per sector. RF hopping enables all TRXs to change frequencies in successive frames. Both random and cyclic hopping over MA frequency list can be used.

Note that the BCCH carrier must remain at a fixed frequency and is not part of RF hopping groups.

Scope of testing The scope of the test cases verifies the usage of MA list and MAIO values and the activation and deactivation of the feature.

Configuration

Item Details

Site configuration 2+4+2

Combining 2-way for the second sector, bypass for others

MA list Same MA List of 16 consecutive ARFN's used in all sectors

Hopping Random RF Hopping in all sectors (HSN <>0)

MAIO MAIO step size of 2 used along with different MAIO for each sectors

Channel configuration SDCCH defined on TCH TRX

Test cases

Pos Name Comment

1 Call Establishment with Synthesised E-GSM Band, ARFN=0


DN0749988 Issue 2-0 en 18/01/2008


27 (381)

Pos Name Comment Frequency Hopping included in MA List

2 Call Establishment with Synthesised Frequency Hopping

1800 band


900 Band


800 band

5 Call Establishment with Synthesised Frequency Hopping Single MA List

4+4+4, P-GSM (BCCH), E-GSM band in MA List

6 Synthesised Frequency Hopping Configuration

E-GSM Band

2.3.1.1 Call Establishment with Synthesised Frequency Hopping

The objective of the test case is to verify that with synthesised frequency (RF) hopping configured, calls can be placed on multiple timeslots and multiple TRXs.


• Spectrum analyser


• The TRX test is successful on all the TRXs.


1 Calls are placed on the same timeslots of all TRXs on all BTSs.

Hold the calls for at least 5 minutes. Monitor the voice quality for all calls.

All calls are successful. Calls are stable.

The voice quality for all calls is good.

2 Using Spectrum Analyser, observe the TCH frequencies used and their RX level for a call on a TRX.

All the frequencies defined in the MAL list attached to BTSs are used. The downlink signal levels for all the frequencies are close to each other.

3 Reset one non-BCCH TRX by lock and unlock at the BSC.

Observe the ongoing calls on test mobiles.

Verify the state of the reset TRX at BTS Manager.

The TRX is reset successfully.

Only calls ongoing on the TRX are released. All other calls are still ongoing.

The TRX becomes operational after reset.



DN0749988Issue 2-0 en18/01/2008


4 Release all the calls, one by one.

At the BSC, verify the state of all the timeslots of the BCF.

All the calls are released successfully as seen from test mobiles.

All the timeslots are idle at the BSC.

5 Place new calls so that all the timeslots of a non-BCCH TRX are used.

Monitor the voice quality for 5 minutes.

All calls are successful.

The voice quality for all calls is good. Calls are stable.

6 At Abis analyser, monitor the Rx quality parameters reported in measurement report.

The measurement reports indicate that Rx_qual tends to zero, and the value of uplink FER is 0.

7 Release all the calls, one by one. All the calls are released successfully as seen from the mobiles.

2.3.1.2 Call Establishment with Synthesised Frequency Hopping Single MA List

The objective of the test case is to verify that with synthesised frequency (RF) hopping configured where both EGSM and PGSM frequencies are used in single MA list, calls can be placed on multiple timeslots and multiple TRXs.


• Spectrum Analyser


1. The BCCH is configured on PGSM 900 frequency.

2. In each BTS object, two TRX objects are assigned frequencies of PGSM 900 and two TRX objects are assigned frequencies of EGSM 900.

3. GTRX=N is set for non BCCH TRX objects by MML command ZERM.

4. MA list attached to each BTS object containing 3 frequencies of PGSM 900 and 3 frequencies of EGSM 900.

5. RF hopping is enabled in each sector and all sectors are neighbours to each other.

6. TRX test is successful on all the TRXs.


1. Calls are placed on the same timeslots of all TRXs on all BTSs.

Hold the calls for at least 5 minutes. Monitor the

All calls are successful. Calls are stable.


DN0749988 Issue 2-0 en 18/01/2008


29 (381)

Step Input Expected output voice quality for all calls. The voice quality for all calls is good.

2. Using the Spectrum Analyser, observe the TCH frequencies used and their RX levels for a call on a TRX.

All the frequencies defined in the MA list attached to the BTSs are used. The downlink signal levels for all the frequencies are close to each other. The TRX transmits on both EGSM and PGSM frequencies.

3. Reset one non-BCCH TRX by lock and unlock atthe BSC.

Observe the ongoing calls on test mobiles.

Verify the state of the reset TRX at the BTS Manager.

The TRX is reset successfully.

Only calls ongoing on the TRX are released. All other calls are still ongoing.

The TRX becomes operational after reset.

4. Release all the calls, one by one.

At the BSC, verify the state of all the timeslots of the BCF.

All the calls are released successfully as seen from test mobiles.

All the timeslots are idle at the BSC.

5. Place new calls such that all the timeslots of a non-BCCH TRX are used.



The voice quality for all calls is good. Calls are stable.

6. At Abis analyser, monitor the Rx quality parameters reported in measurement report.

The measurement reports indicate that Rx_qual tends to zero, and the value of uplink FER is 0.

7. Release all the calls, one by one. All the calls are released successfully as seen from the mobiles.

2.3.1.3 Synthesised Frequency Hopping Configuration

The objective of the test case is to verify that synthesised frequency hopping can be applied and used successfully at the BTS.




1. No Hopping mode is configured in the largest sector. All the other BTS sectors are configured with RF hopping.



1 Calls are placed on all the TRXs on all BTSs. All calls are successful.



DN0749988Issue 2-0 en18/01/2008


Voice quality is observed. The voice quality is good.

2 From the BSC, lock the BTS sector without hopping and apply RF hopping. Attach the MA list to the BTS.

Unlock the sector from the BSC. Observe the BTS state at the BSC and Flexi EDGE BTS Manager.

Calls are released from the locked BTS.

All the TRXs in the BTS sector come to operational state after unlock operation.

3 Calls on other BTS sectors are observed. All the calls are ongoing.

4 From the BSC observe the hopping mode for the above BTS.

The hopping mode is shown as RF for the BTS.

5 Place new calls on all the TRXs in BTS just configured with RF Hopping.



All calls are stable. Voice quality is good.

6 Lock the above BTS. Define the hopping mode for the sector as none.

Unlock the BTS.

Verify the BTS state at the BSC.

The calls are released for the BTS.

After unlock, the BTS and all the TRXs in the BTS come to operational state.

7 For the BTS, observe the hopping mode at the BSC.

No hopping mode is shown for the BTS.

8 Place new calls on the BTS sector without hopping.

Voice quality is monitored.


Voice quality is good.

2.3.2 Antenna Hopping

Overview The Antenna Hopping for Flexi EDGE BTS enables the TRXs in an RF hopping/Non hopping BTS to transmit via all TX antennas in the sector. The Antenna Hopping algorithm defines the routing from TRX to TRX within the hopping group and the frequency each TRX is tuned to at any point in time. The algorithm has been optimised for the different frequency hopping parameters and channel types (traffic/signalling).

Antenna Hopping can improve the frequency hopping performance by adding spatial diversity to the frequency diversity of the regular RF hopping configuration.

Scope of testing The scope of testing is testing the following:


DN0749988 Issue 2-0 en 18/01/2008


31 (381)

• CS calls in Antenna hopping sector

• PS calls in Antenna hopping sector

• Internal Site recovery

Test cases

Pos Name Comment

1 CS Call Support in an Antenna Hopping Sector

8+8, 2 way, Antenna hopping + RF Hopping, AMR FR

2 CS Call Support in an Antenna Hopping Sector

3 + 3 + 3 cost optimised, Antenna hopping + RF Hopping, AMR HR

3 PS Data Transfer Support in an Antenna Hopping Sector

3 + 3 + 3 cost optimised, Antenna hopping + RF Hopping

4 Reconfiguration Support in an Antenna hoppping Sector

8+8, 2 way, Antenna hopping + RF Hopping

2.3.2.1 CS Call Support in an Antenna Hopping Sector

The objective of the test case is to verify calls are successfully established in an Antenna Hopping sector.


• Mobile Call Generator for establishing speech calls.


None.


1 Establish speech calls (codec as per test case comment) on the same timeslots of all TRXs in the sector.

Each call should be established for 5 minutes.

Speech calls are successfully established in the sector.

The speech quality for the calls is good.

2 Monitor the call for 5 minutes. Observe the following in Measurement Results (for both TCH and SDCCH) on the GSM Abis Analyser

• RX Qual

The value of uplink and downlink RX Qual (full or sub) is 0.

For traffic channels, the value of uplink and downlink FER is 0.



DN0749988Issue 2-0 en18/01/2008


• FER

3 Observe Traffic Trace at Flexi EDGE BTS Manager for the CS calls established.

The radio timeslots on which a call is established are seen as active on the Traffic Trace screen at Flexi EDGE BTS Manager.

4 Repeat steps 1-3 for different same TS of TRX, including TS 0.

Results are the same as in steps 1-3.

5 Initiate multiple SMSs simultaneously from 6 additional mobile phones. Repeat the sending of SMSs 4 times.

Observe the following in Measurement Results for SDCCH on the GSM Abis Analyser:

RX Qual


2.3.2.2 PS Data Transfer Support in an Antenna Hopping Sector

The objective of the test case is to verify that PS data transfer sessions are successfully established in an Antenna Hopping sector.

Note: File upload of 1 Mb and file download of 5 Mb will be attempted.

Test case execution Pre-Setup:

1. GPRS and EGPRS both are enabled.


1 Use BSC command

>>> ZEQV:BTS=<BTS no>, BFG=1;

so that all GP timeslots are allocated on the BCCH TRX.

Enable GPRS/EGPRS services on Mobile.

Verify that the command is executed successfully.

Verify that MS get attached successfully for GPRS/EGPRS services.

2 Establish multiple PS data transfer sessions on the sector.

Initiate file upload as well as download.

Upload a file by executing following command on ftp prompt: put <filename>

Download a file by executing following command on ftp prompt: get <filename>

Verify that the sessions are established successfully.

Verify that complete file is uploaded/ downloaded correctly.

Verify that desirable throughput is seen on the ftp application.

3 Observe Traffic Trace at Flexi EDGE BTS All Gp timeslots at the BSC are shown as


DN0749988 Issue 2-0 en 18/01/2008


33 (381)

Step Input Expected output Manager for the PS data transfer sessions established.

active at the Traffic Trace screen of the Flexi EDGE BTS Manager.

4 Keep some trace mobiles in idle mode, latched to the BCCH frequency.

Verify that during the PS data transfer sessions, the trace mobiles do not lose service and continue to remain latched to the BCCH frequency.

5 Repeat PS data transfer session establishment for 5 times.

Verify that file upload/download takes place successfully for each session.

6 Set BFG set to 2 so that GP timeslots are allocated on the non-BCCH TRX.


Repeat test step 2 above.

Verify that the output is as expected in test steps 2 above.


Verify that file upload/download takes place successfully.

2.3.2.3 Reconfiguration Support in an Antenna hopping Sector

The objective of the test case is to verify that:

When a logical TRX is disabled (by disconnecting the bus cable of the EXxx TRX module) in an Antenna hopping sector, a complete BTS object will be reconfigured. Corresponding alarm(s) are raised for the faulty logical TRX and cancelled after the fault is cleared. Reconfiguration of one sector of a BTS site in Antenna Hopping mode does not impact operation of the other sectors in the BTS site. All ongoing CS calls on the other TRXs in the same BTS object are handed over if commanded by BSC. After the fault of the TRX is removed, complete BTS object will be again reconfigured. After reconfiguration, the site resumes normal operation, and new calls (CS/PS) can be generated on the reconfigured BTS object including the faulty TRX.


1. Antenna Hopping is enabled from the BSC.

2. BCCH TRX is the first TRX in each sector.

3. There is no alarm active at the BTS site.

4. Configure a third test base station object (referred to as Test BTS object) and all configured sectors are defined as neighbours of each other using the MML command:

>>> ZEAC:BTS=<BTS1 No.>:ABTS=<BTS2 No.>;

5. Enable GPRS and EGPRS on all BTS objects.



DN0749988Issue 2-0 en18/01/2008

Step Input Expected Output

1 Establish CS calls on all the defined sectors, 6 in each sector so that the originating legs of all the calls are on sectors under testing and the terminating leg is on Test BTS Object.

Verify that the calls are successfully established.

2 Generate a disabling alarm for an EXxA TRX module of the sector by removing the bus cable between the EXxA TRX module and the ESEA System Extension module.

Check the alarm status at the active alarms window of Flexi EDGE BTS Manager and at the BSC.

The alarm '7606, TRX Faulty' alarm is started for each TRX of the EXxA TRX module with the alarm text as "TRX unable to carry traffic. EXxA connection is missing or is not operational" and the object state as "disabled".

3 Observe the status of all ongoing calls on the EXxA TRX module on which the fault was introduced.

All ongoing calls on the EXxA TRX module are dropped.

4 Observe the status of all ongoing calls associated with the other TRXs of the sector in which the fault was introduced.

Verify that all ongoing calls on the other TRXs are handed over (if commanded by BSC) to the adjacent sector, if defined.

5 Verify that within 10 seconds that the complete BTS Object on which the fault was introduced is reconfigured.

A new TRX is configured as BCCH if the disabling alarm has been raised on a TRX configured as BCCH.

Verify that the sector is successfully reconfigured and reaches supervisory state.

6 Observe the existing calls on other BTS objects in the BTS site during reconfiguration of the designated BTS object.

Verify that the calls continue on the other sectors without any disruption.

7 Observe the BTS objects and TRX objects antenna hopping property in Flexi EDGE BTS Manager.

BTS objects and TRX Objects with object state as "enabled" show Antenna hopping as "enabled".

8 Generate CS calls on the reconfigured BTS Object.

Initiate PS data transfer on the reconfigured BTS Object.

Verify that the CS calls are successfully established.

PS Data Transfer is successful.

9 Release the CS calls and the PS data transfer session.

Verify that the CS calls and the PS data transfer sessions are successfully released.

10 Check the operational state of Test BTS object and all TRX objects under Test BTS object.

Operational state for Test BTS object and all TRX objects except TRX objects on which alarm was raised in step 2 is "WO"-

11 Lock/Unlock the Test BTS object from the BSC.

Verify the operational state of Test BTS object and TRX objects under it. Use MML command

Test BTS object and all TRX objects under it have same operational state as in step 10.


DN0749988 Issue 2-0 en 18/01/2008


35 (381)

Step Input Expected Output ZEEI

12 Observe the status for all the TRX objects for the Test BTS object in Flexi EDGE BTS Manager.

TRX objects "disabled" in step 2 remains in "disabled" state. And all other TRX objects have object state as "enabled".

13 Fetch the site information report from Flexi EDGE BTS Manager.

TRX Objects with object state as "enabled" show Antenna hopping as "enabled" under TRX properties. (Same as in step 12)

14 Reconnect the bus cable of the EXxA TRX Module.

Verify that after 10 seconds, the complete BTS object is reconfigured with both the TRXs of the new EXxA TRX Module coming into service.

Alarms raised in step 2 are cancelled.


15 Check the alarm status at the alarm window of Flexi EDGE BTS Manager.


There is no active alarm at Flexi EDGE BTS Manager.

There is no active alarm at the BSC.

16 Observe the BTS objects and TRX objects antenna hopping property in Flexi EDGE BTS Manager.

BTS objects and TRX Objects with object state as "enabled" show Antenna hopping as "enabled".

17 Generate 1 MS-MS CS call and 1 PS data transfer session on the reconfigured BTS object.

Verify that the CS call and packet data transfer are successfully established.

2.3.3 Dynamic Frequency Channel Allocation

Overview Dynamic Frequency and Channel Allocation (DFCA) is a powerful software product designed to provide maximum capacity from scarce frequency resources. It is a channel assignment method for dynamically assigning the optimum radio channel for a new circuit-switched call, directed retry, or incoming handover. DFCA is based on real-time knowledge of frequency usage and interference at any given location in the network.

By dynamically allocating frequency hopping parameters (MA, MAIO) for each individual timeslot, DFCA provides more effective frequency reuse than a static frequency plan. This leads to a significant capacity gain with ensured quality. DFCA uses interference estimations derived from mobile station downlink measurement reports and combines them with the timeslot and frequency usage information.



DN0749988Issue 2-0 en18/01/2008

The DFCA algorithm selects a frequency hopping radio channel for a connection, based on the C/I ratio criteria. Both the C/I for the new connection and the interference effect on existing connections are estimated before channel allocation. DFCA channel allocation ensures enough quality in terms of C/I so that each connection will meet its Quality of Service (QoS) requirements.


• CS (GSM FR/HR calls with UL/DL DTX active) calls on DFCA enabled TRX.

• Intra-cell handover for CS (AMR FR/HR and EFR) calls.

• Reconfiguration of Non-DFCA TRX to DFCA and DFCA to Non-DFCA TRX.

• RX test from Flexi EDGE BTS Manager and BSC on DFCA TRX.

Settings MML command for setting up DFCA:

1. Verify that DFCA is activated in BSC with ZWOS command. 00810 DFCA_USAGE ACTIVATE

2. Activate the DFCA hopping for the BTS objects.

3. Change the clock source to LMU.

4. Set TRX to DFCA TRX.

Note: Two TRXs in each sector should be DFCA TRXs.

Test cases

Pos Name Comment

1 CS Call Support in a DFCA enabled Sector AMR FR, 4+4+4, 2 Way, RF Hopping

2 CS Call Support in a DFCA enabled Sector AMR HR, 4+4+4, 2 Way, RF Hopping

3 Reconfiguration Support in DFCA and Non DFCA TRX

4+4+4, 2 Way, DFCA TRX on EXxA module connected to ERxA module, RF Hopping

4 TRX Test Initiated From BSC for DFCA TRX

4+4+4, 2 Way, RF Hopping

5 DFCA Configuration after BCF Reset from BSC

4+4+4, 2 Way, RF Hopping


DN0749988 Issue 2-0 en 18/01/2008


37 (381)

2.3.3.1 CS Call Support in a DFCA enabled Sector

The objective of the test case is to verify calls are successfully established in a DFCA enabled BTS object.


• ·Mobile Call Generator for establishing speech calls.


1 Establish AMR (Codec as per test case comment) speech calls on the same timeslots of all TRXs in the sector.

Each call should be established for a duration of 5 minutes.

AMR calls are successfully established in the sector.


2 Monitor the call for 5 minutes. Observe the following in Measurement Results (for both TCH and SDCCH) on the GSM Abis Analyser

• RX Qual

• FER



3 Observe Traffic Trace at Flexi EDGE BTS Manager for the CS calls established.

The radio timeslots on which call is established are seen as active on the Traffic Trace screen at Flexi EDGE BTS Manager.



2.3.3.2 Reconfiguration Support in DFCA and Non DFCA TRX

The objective of the test case is to verify that any DFCA TRX can be reconfigured to a non-DFCA TRX and a non-DFCA TRX can be reconfigured to a DFCA TRX.


1. Site is in supervisory state with DFCA enabled and working.


1 Fetch and save the site information report from Flexi EDGE BTS Manager.

The site information report is saved successfully and reflects correctly the DFCA feature.

2 Initiate one CS voice call on each TRX of all BTS objects.

All calls are established successfully.

3 Disconnect EXxA module (BCCH and Non-BCCH TRX objects) from the ESMA module by plugging out the BUS cable. Keep it disconnected for at least 30

A '7606, TRX Faulty' alarm is started on both TRX objects of the disconnected EXxA TRX module with the alarm text "ESMA System module has lost connection to EXxx TRX



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output seconds.

Observe the active alarms at the BSC using MML command ZEOL as well as the Flexi EDGE BTS Manager active alarms window.

module" and the object state as "disabled".

4 Check the status of TRX objects of the EXxA module in the BTS object from which EXxA module was disconnected in step 3 on Flexi EDGE BTS Manager.

Both TRXs are in supervisory state.

Any one TRX objects is reconfigured as BCCH TRX.

DFCA mode for reconfigured TRX Object is displayed as Disabled.

DFCA mode for other TRX is still enabled.

DFCA mode for BCCH TRX object disconnected in step 3 is enabled.

5 Observe the CS calls started on all BTS objects in step 2.

CS calls are still going on in all BTS objects except BTS object 1, with no disruption.

Calls ongoing on the disconnected EXxA TRX module are dropped.

Calls ongoing on the reconfigured TRX in step 2 are dropped or handed over if commanded by the BSC.

Calls ongoing on the other TRX of the same EXxA module are not dropped.

6 Initiate a new pair of CS voice calls on reconfigured TRX.

Call is established successfully.

7 Reconnect the EXxA TRX module disconnected in step 3.

A '7606, TRX Faulty' alarm is cancelled on TRX5 and TRX6 with the alarm text "ESMA System module has lost connection to EXxx TRX module" and the object state as "enabled".

8 Check the status of all TRX objects on the Flexi EDGE BTS Manager.

All TRXs are in supervisory state with object state as "enabled".

9 Verify the status of ongoing calls on all other TRX objects.

No call drop is observed.

10 Fetch the site information report from Flexi EDGE BTS Manager. Check TRX properties and TRX_CONF_Data.

The TRX properties for the BCCH TRX and reconfigured TRX in step 3 as seen in the site information report fetched in step 1 are interchanged in the recently fetched site information report.

2.3.3.3 TRX Test Initiated From BSC for DFCA TRX

The objective of the test case is to verify that the TRX Tests can be successfully executed from the BSC on DFCA TRX.


DN0749988 Issue 2-0 en 18/01/2008


39 (381)


1. All TRXs are in supervisory state.

2. The BCCH power level for all sectors is defined to be the maximum value (i.e. 0) using ZEUG MML command.


1 Start the TRX Test from the BSC on any of DFCA TRX through MML Command ZUBS, with testing mode as 'GMSK' and any randomly chosen timeslot.

Observe the execution output of the MML command at the BSC which displays:

‘TRANSCEIVER TEST STARTED

COMMAND EXECUTED’.

2 Invoke the TRX Test Report for DFCA TRX on the BSC using MML Command ZUBP.

Verify that the TRX test is successful its Report is displayed at the BSC with the following contents:

BCF/BTS/TRX/RTSL Number

Test Result: Passed

Transmitted Power Level: >= 47 dBm

BER for main branch::0

Rx Sensitivity for main branch: < -110 (i.e. better than -110)

BER for Diversity Rx branch: 0

Rx Sensitivity for Diversity branch: < -110

3 Repeat steps 1-2 for all time slots of DFCA TRX in step 1.

Verify the results as given in step 1 and 2.

4 Repeat steps 1-3 for all DFCA TRXs in the site. Verify the results as given in steps 1-3.

5 Repeat step 1-2 for all Non-DFCA TRX. Verify that results as given in step 2.

6 Run at least one MS-MS CS call in each sector (not necessarily simultaneously) for a timeslot which was used for the TRX test.

Verify that the call establishment is successful having good voice quality with no perceptible glitches/echo/noises etc.

7 Observe the active alarms on the BSC for all the TRXs/Sectors in the BTS site, using the ZEOL MML command.

There are no active alarms related to TRX Test/Loop Test.

2.3.3.4 DFCA Configuration after BCF Reset from BSC

The objective of the test case is to verify that DFCA configuration is regained after a BCF reset from the BSC.




DN0749988Issue 2-0 en18/01/2008

• Signal generator

Test case execution Configuration:

TSC of BCCH and Non BCCH carrier are set to different values.

Pre-setup

None.


1 Check the TRX properties for all TRXs at Flexi EDGE BTS Manager.

All the TRX objects are in supervisory state.

For DFCA enabled TRX Objects, DFCA Mode is displayed as Enabled and for other TRX Objects. DFCA Mode is displayed as Disabled.

2 Check the clock synch state for BCF at Flexi EDGE BTS Manager.

Clock synch state is Slave (LMU).


Site information report contains information as mentioned in output of step 1 for TRX Object Properties.

4 Reset the BCF using MML command ZEFR The BCF object is reset and comes to supervisory state.

All TRX objects show their operational state as "WO" on the BSC.

5 Check the TRX properties for all TRXs at Flexi EDGE BTS Manager.

All TRXs are in supervisory state.

DFCA mode is displayed as enabled for the same TRX as in step 1.

6 Check the clock synch state for the BCF at Flexi EDGE BTS Manager.

Clock synch state is Slave (LMU).


Site information report contains information as mentioned in output of step 1 for TRX Object Properties.

8 Establish one CS voice call on each TRX object.

All calls are successfully established.

2.3.4 Half Rate

Overview Half Rate is a feature designed to maximise the spectrum efficiency by doubling the amount of radio resources as compared to the use of the Full Rate traffic resources only. Each radio time slot of the BTS TRX can be configured to be a Full Rate, Half Rate, or Dual Rate TCH resource.


DN0749988 Issue 2-0 en 18/01/2008


41 (381)

In the last case, the BSC will be able to allocate an idle radio time slot either for Half Rate or Full Rate coding dynamically on a call basis.

Scope of testing Scope of testing is limited to normal Half-Rate (TCH/HS) calls only. AMR Half-Rate Calls (TCH/AHS) are tested as part of the AMR test plan.

Testing of upper and lower free TCH/F is not within the scope of this test plan. However, the TCH allocation based on the channel combination is covered.

Settings 1. AMR FR and HR should be de-activated:

>>> ZEQY:BTS=<bts_id>:FRC=0, HRC=0::;

Test cases

Pos Name Comment

1 Establishment and Release of Half Rate Calls

--

2.3.4.1 Establishment and Release of Half Rate Calls

The objective of the test case is to verify that Half Rate calls (TCH/HS) are successful on Flexi EDGE BTS. The objective is to also verify that if channel combination is changed to TCH/F, then only full rate calls are established.


1. AMR FR and HR should be de-activated: >>> ZEQY:BTS=<bts_id>:FRC=0, HRC=0::;


1 Initiate an MS-MS call using the test mobile.

Calls are successful.

The “Channel Mode” information element in “Channel Activation” message on the GSM Abis Analyser indicates “Half Rate” (TCH/H) with speech coding algorithm set to "1".


The Flexi EDGE BTS Manager (see Tests Traffic Trace) shows the timeslots allocated for Half Rate calls as Active.

(Note that if the timeslots are allocated on



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output different timeslots/TRX, then it is not necessary that for a pair of half rate calls, only one timeslot is shown active; that is, two timeslots can also be active for a pair of half rate calls.)

2 Do active listening that has periods of speech and silence.

Speech transfer is good with smooth audible transitions between silence and speech periods.

3 Initiate more MS-MS calls. All calls are Half Rate calls (since only TCH/H channels are assigned at the BSC).

Other observations are as in step 1.

4 Terminate all calls. Change the channel configuration whereby all traffic channels are converted from TCH/H to TCH/F for the site using ZERM command.

The channel configuration for all channels at the BSC is changed TCH/F.

5 Initiate new MS-MS calls. Now, all the calls established are TCH/F. The “Channel Mode” information element in “Channel Activation” message on the GSM Abis Analyser indicates “Full Rate” (TCH/F) with speech coding algorithm set to "1".

6 Release all the calls. All the calls are released.

The Flexi EDGE BTS Manager (see Tests Traffic Trace) shows none of the timeslots as active for GSM.

2.3.5 Adaptive Multi Rate Codec

Overview Different speech codecs are used in a network. These speech codecs work with different speech coding algorithms and give different speech coding bit rate and varied efficiency in recovery of speech.

The AMR codecs which are available for use in a network are:

1. Adaptive Multirate Full Rate (AMR/FR)

2. Adaptive Multirate Half Rate (AMR/HR)

Each speech codec is selected on the basis of the radio link condition that is, the C/I ratio or cell load.

If the C/I ratio is low then the speech codec with the higher error correction bits is preferred, to facilitate better recovery of speech.

Scope of testing The scope of testing for AMR codecs includes establishment of AMR/FR and AMR/HR calls, verification of changes in codec rates with


DN0749988 Issue 2-0 en 18/01/2008


43 (381)

introduction of co-channel interference over the air interface and verification of voice quality with changes in codec rates.

Settings 1. All the AMR parameters are the default values for the BTS.

2. DL DTX is disabled. >>> ZEGP:18,0:;

3. At least four frequencies are used in the MA list for each of the sectors.

4. Default parameter settings are used at the BSC for Link Adaptation.

Test cases

Pos Name Comment

1 Fast Link Adaptation for Co-Channel Interference [UL]

AMR/FR calls


AMR/HR calls


AMR/FR calls, UL DTX


AMR/HR calls, UL DTX

5 Fast Link Adaptation for Co-Channel Interference [DL]

AMR/FR calls

6 Fast Link Adaptation for Co-Channel Interference [DL]

AMR/HR calls

2.3.5.1 Fast Link Adaptation for Co-Channel Interference [UL]

This test case verifies the following for an MS-MS AMR Call with Fast Link Adaptation activated:

1. With varying link conditions (co-channel interference) in the uplink, 'Fast Link Adaptation' occurs and corresponding codecs are selected.

2. Call quality performance with 'Fast Link Adaptation'.



• RF Shielding box



DN0749988Issue 2-0 en18/01/2008


1. Test Mobiles with AMR/FR and AMR/HR support are placed in the RF shielding box.

2. Fast Link Adaptation is in use.Fast Link Adaptation is in use at the BSC by default.

>>>" ZEEO:ALL:;" displays parameter 'SAL' set to 'N'.

3. Signal generator is connected to introduce interference in UL.

4. MS Power control is disabled and the MS Power is set at constant value so that the Rx_level received is about -85 dBm.

5. TRAU traces are monitored on the Abis.

6. Enhanced Measurement Reporting is active.

>>>" ZWOS:2,776:;" displays parameter EMR_SUPPORT_IN_BSC set to 'Activated'.

7. Uplink DTX is disabled with the following command unless specified otherwise.

>>>" ZEQM:BTS=<bts id>:DTX=2:;"

Note that when UL DTX is applied, then the values of UL_Rx_qual_sub should be considered instead of the values for UL_Rx_qual_full.The values of UL_Rx_qual_sub should tend to 'zero' instead of UL_Rx_qual_full. Also, there should be no disturbances when there are transitions from DTX applied to DTX not-applied and vice-versa.


1 Initiate a voice call between MS1 and MS2.

Call is successfully established.

The voice quality is good and the speech heard is clear, free of any disturbances.

2 Observe the speech frame format in TRAU Speech Frame sent after connection acknowledgment.

Observe the AMR TRAU frames in the UL and DL directions.

It is observed that under good RF conditions the Codec shifts from the 2nd most robust codec to the least robust codec.

It is observed that the Codec Mode can change every 40 msec.

3 Actively listen at both ends for the call established in step 1.

Observe the Measurement reports on the

It is observed that the voice heard is clear and free of disturbances during the changes of these codecs.


DN0749988 Issue 2-0 en 18/01/2008


45 (381)

Step Input Expected output GSM Abis analyser.

The Enhanced Measurement reports indicate that Rx_qual_full tends to zero, DL FER and UL FER tend to zero.

4 Introduce Co-Channel interference in the Uplink direction so that a certain amount of C/I is created.


Verify that the reported codecs used in the Measurement reports are as per what has changed on the TRAU.

Observe that the codec mode shifts from the least robust codec to the next robust Codec.


Active listening indicates that the voice heard is clear and free of disturbances.

The Enhanced Measurement reports observed show that Rx_qual_full tends to zero, DL FER and UL FER tend to zero.

The codecs reported in the Measurement reports are consistent with the TRAU frames.

5 Increase the Co-Channel interference in the Uplink direction gradually.

It is observed that the codec mode shifts to the most robust codec through all the other Codec modes in between if sufficient C/I is introduced.

Active listening indicates that the voice heard is clear and free of disturbances when the most robust codec is used.



6 Decrease the Co-Channel interference that was introduced in the Uplink direction gradually.

It is observed that the codec mode shifts from the most robust codec to the next robust Codec.



7 Continue to decrease the Co-Channel interference that was introduced in the Uplink direction.

It is observed that under good RF conditions the Codec shifts to the least robust codec through all the codecs in between.

The Enhanced Measurement reports indicate that Rx_qual_full tends to zero, DL



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output FER and UL FER tend to zero.

Active listening indicates that the voice heard is clear and free of disturbances when the least robust codec is used.

8 Repeat steps 5 to 7 for ten times. Observations as in steps 5 to 7.





2.3.5.2 Fast Link Adaptation for Co-Channel Interference [DL]

This test case verifies the following for an MS-MS AMR Call with 'Fast Link Adaptation' activated:

1. With varying link conditions (co-channel interference) in the downlink, 'Fast Link Adaptation' occurs and corresponding codecs are selected.

2. Call quality performance with 'Fast Link Adaptation'.



• RF shielding box


1. Test Mobiles with AMR/FR and AMR/HR support are placed in the RF shielding box.

2. Fast Link Adaptation is in use. Fast Link Adaptation is in use at the BSC by default.

>>>" ZEEO:ALL:;" displays parameter 'SAL' set to 'N'.

3. Signal generator is connected so as to introduce interference in DL.


DN0749988 Issue 2-0 en 18/01/2008


47 (381)

4. MS Power control is disabled and the MS Power is set at constant value so that the Rx_level received is about -85 dBm.

5. TRAU traces are monitored on the Abis.

Enhanced Measurement Reporting is active.

>>>" ZWOS:2,776:;" displays parameter 'EMR_SUPPORT_IN_BSC' set to 'Activated'.


1 Initiate a voice call between MS1 and MS2.

Call is successfully established.


2 Observe the speech frame format in TRAU Speech Frame sent after connection acknowledgment.


It is observed that under good RF conditions the Codec shifts from the 2nd most robust codec to the least robust codec.



Observe the Measurement reports on the GSM Abis analyser.

It is observed that the voice heard is clear and free of disturbances during the changes of these codecs.


4 Introduce Co-Channel interference in the Downlink direction so that a certain amount of C/I is created.


Verify that the reported codecs used in the Measurement reports are consistent with the TRAU frames.

It is observed that the codec mode shifts from the least robust codec to the next robust Codec.



The Enhanced Measurement reports observed show that Rx_qual_full tends to zero, DL FER and UL FER tend to zero.


5 Increase the Co-Channel interference in the Downlink direction gradually.

It is observed that the codec mode shifts to the most robust codec through all the other Codec modes in between if sufficient C/I is introduced.

Active listening indicates that the voice



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output heard is clear and free of disturbances when the most robust codec is used.



6 Decrease the Co-Channel interference that was introduced in the Downlink direction gradually.

It is observed that the codec mode shifts from the most robust codec to the next robust Codec.



7 Continue to decrease the Co-Channel interference that was introduced in the Downlink direction.

It is observed that under good RF conditions the Codec shifts to the least robust codec through all the codecs in between.


Active listening indicates that the voice heard is clear and free of disturbances when the least robust codec is used.

8 Repeat steps 5 to 7 for ten times. Observations as in steps 5 to 7.






DN0749988 Issue 2-0 en 18/01/2008


49 (381)

2.3.6 Active/Idle Channel Interference Estimation

Overview The active-channel interference estimation feature utilises idle TDMA frames on TCH channels and also the silent periods when the MS is using DTX in uplink. The BTS calculates the interference levels and reports them to the BSC in the 'RF_resource_indication' message.

Active Channel Interference Reporting enables the BSC to get information on the interference levels of an active TCH channel. This makes it possible for the BSC to activate the next call in the best TCH channel immediately after the channel has been released.

Note that if uplink DTX is not activated, the active-channel interference cannot be measured for half rate calls.

Idle channel measurement is performed for all inactive channels including the SDCCH and TCH. Idle channel measurement is reported over the multiframe period.

Scope of testing This test plan covers the active channel measurement for EFR, AMR/FR and AMR/HR calls and Idle channels measurement for RF Hopping and BB Hopping sectors.

Configuration

Item Details


Channel Configuration BCCH TRX: MBCCH +SDCCH/8 + 3TCH/F + 3 TCH/D

Non_BCCH TRXs: 4 TCH/F + 4 TCH/D

Settings 1. Set uplink DTX to 'MS may use DTX mode'.

>>>ZEQM:BTS=253:DTX=0;

Additional information GMSK modulated interference to be introduced in one of the carriers in the MA list. Test cases

Pos Name Comment

1 Active Channel interference reporting

6+6, AMR/FR, GSM 900, calls on FR and DR channel



DN0749988Issue 2-0 en18/01/2008

Pos Name Comment

2 Active Channel interference reporting

6+6, AMR/HR on both subchannels, GSM 1800.

3 Idle Channel interference reporting 6+6, BB Hopping Sector

2.3.6.1 Active Channel Interference Reporting

The objective of the test case is to verify that BTS reports correct interference band value for active channels in RF Resource Indication message corresponding to the level of interference present. The RF Resource Indication contains:

1. One entry for timeslots active with Full Rate Call irrespective of DTX applied in the uplink.

2. Three entries per timeslot (each for HR subchannel 0, 1 and Full rate channel as whole) when active with 2 Half rate call (HR0/HR1) if DTX is applied in the uplink.

3. No entry for the timeslot active with 2 Half rate calls (HR0/HR1) when DTX is not applied in the uplink.




1. The signal generator connected to the BTS used to introduce interference. Initially there is no interference introduced.

2. The mobiles used are kept in shielding box.


1 Make calls in a BTS object 2 on BCCH TRX and 2 on non-BCCH TRX (use codec as per the test case comment).

Voice call is established successfully.

Voice quality is good without disturbances or cracking sound.

2 Have continuous speech in the uplink, so that uplink DTX is not applied by the mobile for the entire span of interference reporting period.

Observe the RF resource Indication message in abis traces.

Observe the Measurement reports for a call in the Abis trace.

RF resource Indication has the Interference band value (indicating no interference; Interf Band = 1) for the channels on which Full Rate call (EFR, AMR/FR) is going on, but there is no value for channel on which Half Rate call (AMR/HR) is going on.

It is observed that "DTX Used" field contains '0 DTX was not used' in the measurement report.


DN0749988 Issue 2-0 en 18/01/2008


51 (381)


Check for the Interference level at the BSC with ZERO command.

Interference band seen at the BSC also indicates no interference (I.LEV = 0) for the corresponding channels.

3 Have continuous "no-speech" in the uplink, so that uplink DTX is applied by the mobile for the entire span of interference reporting period and observe the RF resource Indication message in abis traces.

Observe the Measurement report in the Abis trace.


RF resource Indication has the Interference band value (indicating no interference; Interf Band = 1) for all the channels (FR and HR) on which calls are going on.

It is observed that "DTX Used" field contains '1 DTX was used' in the measurement report corresponding to the "no-speech" periods.

Interference band seen at BSC also indicates no interference (I.LEV = 0) for the corresponding channels.

4 Have "speech" and "no-speech" in the uplink at regular periods, so that uplink DTX is applied by the mobile for atleast half the span of interference reporting period and observe the RF resource Indication message in abis traces.



Same output as in step 3.

It is observed that "DTX Used" field contains '0 DTX was not used' or '1 DTX was used' in the measurement report corresponding to "speech" or "no-speech" periods.

Interference band seen at the BSC also indicates no interference (I.LEV = 0) for the corresponding channels.

5 Have alternate "speech" and "no-speech" switching, so that uplink DTX is applied by the mobile for short durations (3 or 4 times) during the entire span of interference reporting period and observe the RF resource Indication message in abis traces.




6 Introduce GMSK Modulated Interference in uplink on all 8 timeslots of the BCCH carrier using Signal generator and repeat steps 2 - 5.

Same outputs as in steps 2-5. But the Interference band value seen in RF resource indication(Interf Band > 1) and at the BSC indicates that there is increase in interference (I.LEV > 0) level for channels in the BCCH TRX and no interference for



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output channels in non-BCCH TRX

Note that in case of BB hopping, there is increase in Interference level for channels in the BCCH and Non-BCCH TRX.

7 Introduce GMSK Modulated Interference in uplink on all 8 timeslots of the non-BCCH carrier (No interference on BCCH carrier) using Signal generator and repeat steps 2-5.

Same outputs as in steps 2-5. But the Interference band value seen in RF resource indication (Interf Band > 1) and at the BSC indicates that there is increase in interference level (I.LEV > 0) for channels in the non-BCCH TRX and no interference for the channels in BCCH TRX.

Note that in case of BB hopping, there is increase in the Interference level for channels in BCCH and Non-BCCH TRX.

2.3.6.2 Idle Channel Interference Reporting

The objective of the test case is to verify that the BTS reports the proper Interference band for all the Idle channels in the RF Resource Indication message.




1. The signal generator connected to the BTS used to introduce interference. Initially there is no interference introduced.


1 Observe the Abis trace for RF Resource Indication message for BCCH and non-BCCH TRX.

Interference band value (indicating no interference; Interf Band = 1) is reported for all the SDCCH subchannels, all the Full Rate channels.

Three Interference band values (indicating no interference; Interf Band = 1) are reported for Dual rate channels: one each for HR Subchannel 0, HR Subchannel 1, and Full rate channel.

2 Introduce GMSK modulated interference in uplink per timeslot basis, one by one on 3 or 4 timeslots of the BCCH carrier using signal generator.

Observe the Abis trace for RF Resource

Interference (band value increase on BCCH TRX, Interf Band > 1) is observed on one timeslot or two adjacent timeslots, relative to how the signal generator and BTS are synched.


DN0749988 Issue 2-0 en 18/01/2008


53 (381)

Step Input Expected output Indication message for BCCH and non-BCCH TRX.


Interference band value on rest of the timeslots is the same as observed in step 1.

Interference band seen at the BSC also indicates there is increase in interference (I.LEV > 0) for the corresponding timeslots.

3 Introduce GMSK modulated interference in uplink per timeslot basis, one by one on 3 or 4 timeslots of a non-BCCH carrier using signal generator.

Observe the Abis trace for RF Resource Indication message for BCCH and non-BCCH TRX.


Same output as in step 2 on non-BCCH TRX.

Note that the interference level reported for a TRX with RF hopping is lesser than that for the BCCH TRX for the same interference level (on the corresponding timeslots).

In case of BB hopping, the interference level reported for all the TRXs (except the timeslot 0 of BCCH TRX) is the same for the same interference level (on the corresponding timeslots).

2.3.7 Downlink And Uplink DTX

Overview Discontinuous transmission (DTX) is a mechanism allowing the radio transmitter to be switched off during speech pauses. This feature reduces the power consumption of the transmitter, which is important for mobile phones, and decreases the overall interference level on the radio channels affecting the capacity of the network. The BSS supports both downlink and uplink discontinuous transmission.

Scope of testing The scope of testing is verifying that DTX is supported by Flexi EDGE BTS with each of the supported speech codecs. DTX will be enabled to be used in both uplink and downlink.

Settings 1. BSC commands to enable uplink DTX: >>> ZEQM:BTS=<bts id>:DTX=<value>:;

where, 0 = MS may use DTX, 1 = MS shall use DTX, 2 = MS shall not use DTX

2. BSC commands to enable downlink DTX:



DN0749988Issue 2-0 en18/01/2008

>>> ZEGP: 18,1:;

Test cases

Pos Name Comment

1 UL/DL DTX for Full Rate Speech EFR, 4+4, RF Hopping

2 UL/DL DTX for Full Rate Speech AMR/FR, 6+6, BB Hopping

3 UL/DL DTX for Half Rate Speech

AMR/HR, 6+6, BB Hopping

4 UL/DL DTX for Half Rate Speech

4+4, 2 Way, AMR HR, RF & Antenna Hopping

2.3.7.1 UL/DL DTX for Full Rate Speech

The objective of the test case is to verify that Flexi EDGE BTS supports uplink and downlink DTX for full rate speech calls.




1. Enable uplink and downlink DTX at the BSC.


1 Establish multiple MS to Network full rate speech calls (codec as in test case comment) on BCCH and non-BCCH carrier.

Verify that the call is successfully established.

2 Observe call behaviour for 5 minute duration with active speech.


3 Observe the following with respect to the Measurement Reports seen at GSM Abis Analyser.

Verify that RxQual (full or sub) values are tending to 0.

Verify that uplink FER and downlink FER values (if reported by MS) are tending to 0

4 Introduce periods of no speech/ silence during the call.

Observe the downlink RF transmission for the BCCH and non-BCCH carrier using Spectrum Analyser.

There is no disturbance in voice during periods of silence.

The continuous downlink RF transmission is seen for the BCCH carrier

Intermittent downlink RF transmission (corresponding to Silence Descriptor frames) is seen for the non-BCCH carrier.

5 Verify that there are no disturbances in voice when there are speech to no speech

No disturbances are heard and voice quality is good.


DN0749988 Issue 2-0 en 18/01/2008


55 (381)

Step Input Expected output transitions and vice-versa.

Observe the donwlink RF transmission for the BCCH and non-BCCH carrier using Spectrum Analyser.

The fields in the Measurement Reports are correct.

The continuous downlink RF transmission is seen for the BCCH carrier.

Downlink RF Transmission switches on and off for the non-BCCH carrier.

6 Repeat test steps 1 to 5 above 5 times. Verify that the behaviour during each call is the same as described above.

2.3.7.2 UL/DL DTX for Half Rate Speech

The objective of the test case is to verify that Flexi EDGE BTS supports uplink and downlink DTX for half rate speech calls.




1. Enable uplink and downLink DTX at the BSC.


1 Establish two half rate speech calls (codec as in test case comment) between MS to Network such that both half rate channels of a single radio timeslot are utilised for establishing the calls.


2 Observe call behaviour for 5 minutes with active speech.


3 Observe the following with respect to the Measurement Reports seen at GSM Abis Analyser.

Verify that RxQual (full or sub) values are tending to 0.

Verify that uplink FER and downlink FER values (if reported by MS) are tending to 0.

4 Introduce periods of no speech/ silence for one of the half rate speech calls.


Verify that there is no disturbance in voice during periods of silence.

The continuous downlink RF transmission is seen for the BCCH carrier

Intermittent downlink RF transmission (corresponding to Silence Descriptor frames) is seen for the non-BCCH carrier.

5 Verify that there are no disturbances in voice No disturbances are heard when there are



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output when there are speech to no speech transitions and vice-versa.


transitions from DTX applied to DTX not applied and vice-versa.

The fields in the Measurement Reports are correct.

The continuous downlink RF transmission is seen for the BCCH carrier.

Downlink RF Transmission switches on and off for the non-BCCH carrier.

6 Repeat test steps 1 to 5 above 5 times each time varying the half rate speech call being observed.

Note: Observe DTX behaviour for one half rate call with transitions from speech to no speech and vice versa, while the other call is ongoing with active speech.

Verify that the behaviour during each call is the same as described above.

2.3.8 Handover and Power Control Algorithms

Overview Handover and Power Control Algorithm is a feature designed to make the mobility of the mobile stations (MS) possible during a call and to maintain good speech/data quality. Furthermore, the battery lifetime of an MS can be optimised.

The BSC supports handovers, which occur between different channels of TRX, between different TRXs of BTS, between different BTSs of BSS, and between different BSSs of NSS(s). The handover can be synchronised or asynchronised, depending upon whether the cells are synchronised or not.

The BSC controls the transmission power of the BTS through the BS Power Control message for BCCH channel and the channels on which calls are going on, the BCCH power level is received initially when the system comes to supervisory, also when user manually changes the Power at BSC. However on active channels on which calls are going on, BSC controls the BTS transmission power depending on the received signal power from the MS.

Scope of testing The scope of testing is to observe the BCCH transmission power of the BTS different hopping (Non, BB and Antenna) sector and transmission power on active channels during calls is the same as commanded by the BSC. To verify for successful handover of calls Intra-cell (because of


DN0749988 Issue 2-0 en 18/01/2008


57 (381)

Interference), Inter-cell both Synchronous and Asynchronous incase of good signal strength of neighbouring cells.

Test cases

Pos Name Comment

1 BCCH Power Control 6+6, Sector1: Non-Hopping & Sector2: BB Hopping

2 BCCH Power Control 4+4, 2 Way, Antenna Hopping

3 Power Control on Active Channels 6(GSM 900)+6(GSM 1800), Sector1: Non-Hopping & Sector2: BB Hopping, EFR

4 Power Control on Active Channels 6(GSM 900)+6(GSM 1800), Sector1 & Sector2: BB Hopping, AMR/HR on Both SubChannels

5 Power Control on Active Channels 4+4, 2 Way, Antenna Hopping, AMR FR

6 Intra Cell Handover 2+2+2, By Pass, EFR

7 Intra Cell Handover - AMR Packing/Unpacking

2+2+2, By Pass

8 Inter Cell Handover - Synchronous 6(GSM 900)+6(GSM 1800), EFR, BB Hopping on both sectors

9 Inter Cell Handover - Synchronous 6(GSM 900)+6(GSM 1800), AMR/FR, BB Hopping on both sectors

10 Inter Cell Handover - Asynchronous Independent BCFs, BCF1: 2+2+2, BCF2: 2+4+2, EFR

11 Inter Cell Handover - Asynchronous Independent BCFs, BCF1: 2+2+2, BCF2: 2+4+2, AMR/FR

12 Inter Cell Handover - Asynchronous Independent BCFs, BCF1: 2+2+2, BCF2: 2+4+2, AMR/HR

2.3.8.1 BCCH Power Control

The objective of the test case is to verify that BCCH transmission power of the BTS do not drift in the power level when observed for long duration, irrespective of the Hopping mode configured.



DN0749988Issue 2-0 en18/01/2008




1. Spectrum Analyser is connected to BTS for Measuring the output signal strength of BTS.

2. The Attenuation Level at BSC is set to 0;(PMAX = 0).

3. For Antenna hopping configurations, transmission from all the Antennas in a sector is combined together to feed in spectrum analyser.


1 Observe the power of BCCH Carrier in all the sectors for 2hrs with Spectrum Analyser.

The BTS transmission power value measured at the Spectrum Analyser corresponds to the Power level commanded by BSC.

Power level measured at the spectrum analyser does not change for 2hrs.

2 Observe the power of Non BCCH carrier in all the sectors for 15 minutes with Spectrum Analyser. (No ongoing calls)

No transmission on the Non BCCH carrier.

3 Increase the Attenuation PMAX to 10 at the BSC.

The BTS transmission power value measured at the Spectrum Analyser falls by 10db compared to the value observed in step 1.

4 Increase the Attenuation PMAX to 20 at the BSC.

The BTS transmission power value measured at the Spectrum Analyser falls by 20db compared to the value observed in step 1.

2.3.8.2 Power Control on Active Channels

The objective of the test case is to verify that BTS successfully changes the transmission power as commanded by the BSC on the active channels in Non-Hopping / BB-Hopping / Antenna Hopping Mode.



• Variable attenuators


DN0749988 Issue 2-0 en 18/01/2008


59 (381)


1. Spectrum Analyser is connected to BTS for measuring the output signal strength of BTS.

2. Variable Attenuator is connected between MS(s) and BTS(s).

3. Attenuation level at the BSC is set to PMAX = 0 and PMIN = 30.

4. For Antenna hopping configurations, transmission from all the Antennas in a sector is combined together to feed in spectrum analyser.


1 Establish 4 calls in each sectors (codec used as per the case comment), 2 on BCCH TRX and 2 on Non BCCH TRX.



2 Observe the power level of the active channels of BCCH and Non BCCH carrier with Spectrum Analyser.

Power level seen at the Spectrum analyser follows the power commanded by the BSC for Non BCCH carrier.

The power level for the BCCH carrier does not vary and corresponds to the BCCH power level.

Note: In case of BB hopping, the BCCH power level (and not the channel specific power level) is used when the RF transmission happens on the BCCH carrier. When the transmission happens on non-BCCH carrier the channel specific power level is used for transmission (even if the call is on BCCH TRX).

3 Introduce attenuation between the Mobile and BTS with variable attenuator.

Increase attenuation once every 2 minutes for 10 minutes. (This triggers the BSC to command Increased transmission power of the BTS)

Observe the power level of the active channels of BCCH and Non BCCH carrier with Spectrum Analyser.

Same output as in step 2

4 Decrease attenuation once every 2 minutes for 10 minutes. (This triggers the BSC to command Decreased transmission power of BTS)

And observe the power level of the active channels of BCCH and Non BCCH carrier with




DN0749988Issue 2-0 en18/01/2008

Step Input Expected output Spectrum Analyser.

2.3.8.3 Intra-Cell Handover

The objective of the test case is to verify that Intra-cell handover happens properly without call getting disconnected. Test environment Hardware tools:


Test case execution The TSC of the BCCH and Non-BCCH carrier are set to different values.

Pre-setup:

1. The signal generator is connected to the BTS for introducing interference.


1 Establish call as per case comment, 2 on BCCH carrier and 2 on Non BCCH carrier in BTS Object 1.



2 Introduce GMSK Modulated Interference in the Uplink through Signal Generator on all the 8 timeslots of the BCCH carrier.

This should trigger Intra-Cell handover procedure.

Actively listen to the speech during the handover.

Successful handover of all the calls to Non-BCCH carrier.

Also voice quality is good without disturbances or cracking sound during the handover.

3 Now introduce GMSK Modulated Interference in the Uplink through Signal Generator on all the 8 timeslots of the Non BCCH carrier on one of the hopping frequencies.

This again should trigger Intra-Cell handover procedure.

Successful handover of all the calls to BCCH carrier.

Voice quality is good without disturbances or cracking sound during the handover.

4 Repeat steps 2 and 3 for 10 times and observe handover of calls back and forth with active listening.

Handover is successful in all cases with good voice quality.


DN0749988 Issue 2-0 en 18/01/2008


61 (381)

2.3.8.4 Intra-Cell Handover - AMR Packing/Unpacking

The objective of the test case is to verify that Intra-cell handover happens for AMR calls with packing/unpacking without call getting disconnected.




Pre-setup:

1. Signal Generator is connected to BTS for introducing Interference.

2. The upper and lower limit for Full rate TCH resource is 60% and 40% respectively by using the below mentioned command.

>>ZEQM:BTS=<bts-id>:FRU=60%,FRL=40%;


1 Establish 10 AMR calls in BTS Object 1.

(No interference is introduced)



Some calls are AMR/FR and some are AMR/HR.

2 Establish 4 more AMR calls in BTS Object 1. Voice call is established successfully.


Some calls (AMR/FR) established in step 1 are packed to AMR/HR channels.

3 Introduce GMSK Modulated Interference in the Uplink through Signal Generator on all the 8 timeslots for non-BCCH TRX on one of the hopping frequencies.

This should trigger unpacking.

Actively listen to the speech during unpacking.

Successful handover/ unpacking of AMR/HR calls (in the non-BCCH TRX) to AMR/FR calls.

Voice quality is good without disturbances or cracking sound during this procedure.

4 Release all the calls. Check for channel status at the BSC with ZERO command.

All calls released and channel in Idle state.

5 Repeat steps 1 to 4 for 5 times. Same output as steps 1 to 4.



DN0749988Issue 2-0 en18/01/2008

2.3.8.5 Inter-Cell Handover – Synchronous

The objective of the test case is to verify that Inter-cell Synchronous handover happens properly without the call getting disconnected.


• Fading simulator

• Variable attenuator


Pre-setup:

1. Two Variable Attenuators used, one connected between MS(s) and BTS 1 (this is set to minimum attenuation initially) and the other between MS(s) and BTS 2 (this is set to maximum attenuation initially).

2. Fading Simulator is used to change the distance of the mobile from the BTS in 5 to 30 km range. It is connected between MS(s) and BTS1 and BTS2.


1 Establish 6 calls on BTS 1 (codec set used as per test case comment) and listen to the voice for 1 minute.



2 Using the fading simulator, continuously change (Increase/decrease) the distance of MS(s) w.r.t BTS(s).

Using Variable attenuator Increase attenuation of MS(s) w.r.t BTS1 and decrease attenuation of MS(s) w.r.t BTS2.

This should trigger Inter-Cell handover procedure.


Successful handover of all the calls from BTS1 to BTS2.


3 Repeat step 2 but this time Increase attenuation of BTS2 and decrease attenuation of BTS1 w.r.t MS(s)

Successful handover of all the calls from BTS2 to BTS1.


4 Repeat steps 2 and 3 for 20 times and observe handover of calls back and forth with



DN0749988 Issue 2-0 en 18/01/2008


63 (381)

Step Input Expected output active listening.

(Each time having a unique distance value between the MS(s) and BTS(s))

2.3.8.6 Inter-Cell Handover – Asynchronous

The objective of the test case is to verify that Inter-cell Asynchronous handover happens properly without the call getting disconnected.





Pre-setup:

1. Two variable attenuators used, one connected between MS(s) and BTS 1/BCF1 (this is set to minimum attenuation initially) and the other between MS(s) and BTS 1/BCF2 (this is set to maximum attenuation initially).

2. Two fading simulators used, one connected between MS(s) and BTS 1/BCF1 and the other between MS(s) and BTS 1/BCF2. Distance at fading simulator to be varied from 5 to 30 km.


1 Establish 6 calls as per case comment on BTS1/BCF1 and listen to the voice on mobiles for 1 minutes.



2 Simulate the MS(s) moving away from BTS1/BCF1 and towards BTS1/BCF2 using the fading simulator. Also simulate continuous decrease in signal strength of BTS1/BCF2 and increase in signal strength of BTS1/BCF2 using variable attenuator.

This should trigger Inter-Cell handover procedure.


Handover of all the calls from BTS1/BCF1 to BTS1/BCF2 happens successfully.

Also, the voice quality is good without disturbances or cracking sound during the handover.

3 Repeat step 2 but this time, simulate MS(s) moving towards BTS1/BCF1 and away from

Handover of all the calls from BTS1/BCF2 to BTS1/BCF1 happens successfully.



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output BTS1/BCF2 with continuous increase of signal strength of BTS1/BCF1 and decrease signal strength of BTS1/BCF2.

Also, the voice quality is good without disturbances or cracking sound during the handover.

4 Repeat steps 2 and 3 for 20 times and observe handover of calls back and forth with active listening. (Each time having a unique distance between MS(s) and BTS(s))


2.3.9 Enhanced Measurement Report

Overview The support for the Enhanced Measurement Report (EMR) feature The Support for Enhanced Measurement Report (EMR) feature provides the Base Station Sub-system (BSS) with enhanced serving and neighbour cell measurements. This is achieved by requesting the Mobile Station (MS) to use the EMR for reporting downlink measurements. The Enhanced Measurement Report also provides the system with information such as Downlink Frame Erasure Rate (DL FER), the usage of Bit Error Probability (BEP) instead of RX Quality during the DTX frames, and the support for reporting WCDMA RAN neighbour cells. In addition, the EMR also provides an extended range for the serving and neighbour cells downlink signal strength and the possibility to report altogether up to 15 GSM and/or WCDMA RAN neighbour cells in one report.

These reports can be used by the network to enhance the generic performance of the existing system, enable GSM/WCDMA interworking, and enhance several existing or new Nokia features, such as Automated planning, Dynamic Frequency Channel Allocation (DFCA) and Intelligent Underlay Overlay (IUO) and Intelligent Frequency Hopping (IFH).

The major difference between the Enhanced Measurement Report (EMR) and the Measurement Report (MR) is that the EMR only reports on the neighbours it is told about. When the EMR reporting is requested, in addition to the neighbour cell BCCH frequencies, the BSC also sends valid Base Transceiver Station Identity Codecs (BSICs) of the neighbouring cells to the MS.

Scope of testing EMR testing is limisted in this plan is limited to Circuit Switched Voice Calls. They are not done for GPRS/EGPRS (where EMR is not applicable) nor done for CSD/HSCSD where they are not supported. The following aspects are covered:


DN0749988 Issue 2-0 en 18/01/2008


65 (381)

• Uplink and Downlink Measurement Parameters Reporting for DL/UL FER, MEAN_BEP and CV_BEP

• EMR reporting with and without averaging

• EMR for AMR and non-AMR calls

• EMR reporting with and without external interference

Configuration BTS band and configuration as defined in the test case.

Settings 1. MML command to activate EMR support in the BSC: >>>ZWOA:2,776:{A,D};

where, A = Activate, D = De activate

2. MML command to set the FER_USAGE parameter ON: >>>ZWOA:2,628,A;

3. Set the RXQ_HAC_USAGE_P parameter ON ZWOC:10,28,FF;

4. MML command to activate DTX mode (in uplink from MS BTS BSC):

>>>ZEQM:BTS <bts_id>:DTX=<value>;

Where; 0 = MS may use DTX, 1 = MS shall use DTX, 2 = MS shall not use DTX

5. MML command to activate DTX mode (In downlink from BSC BTS MS) at the BSC:

>>>ZEGP:18,1;

6. MML command to activate DTX mode (In downlink from BSC BTS MS) at the MSC:

>>>ZEPR:NO=<cell_id>:DTX=OFF:;

Note: From the MSC, a value of 'OFF' will enable DL DTX.

7. MML command to set the averaging period for Measurement Reporting:

>>>ZEQM:BTS=<bts_id>:BMA= <Averaging rate [1-4]>;

8. MML command to deactivate AMR FR and HR: >>> ZEQY:BTS=<bts_id>:FRC=0, HRC=0::;

Additional information For this test plan, the following parameters are important:



DN0749988Issue 2-0 en18/01/2008

• Uplink FER: These indicate the number of bad frames in uplink. Along with the UL and DL Codecs. The number of pairs of (Bad Frames, UL/DL codecs) depends upon extent of averaging. If the measurements are not averaged the FER measurement information is included only once. If averaging is used, the number of bad frames and the codec information are added from each measurement report separately. In case where no downlink measurements have been received from mobile, no FER information elements are added either. In case of CS Data, uplink FER (number of bad frames) is not valid.

• EMR Information: These include the MEAN_BEP and CV_BEP and the number of bad frames received in downlink. If the measurements are not averaged the EMR measurement information is included only once. If averaging is used, the number of bad frames is added from each measurement report separately.

− MEAN_BEP: This is the mean of the Bit Error Probability (BEP) over a radio block. The MEAN_BEP is represented as a numeric value of 0 (worst case) to 31 (best case), wherein each value specifies a range of MEAN_BEP. For details, refer to 3GPP TS 45.008.

− CV_BEP: This is the coefficient of variation of the Bit Error Probability (BEP) over a radio block. The CV_BEP is represented as numeric value of 0 (worst case) to 7 (best case), where each value specifies a range of CV_BEP. For details, refer 3GPP TS 45.008.

Test cases

Pos Name Comment

1 Verification of UL FER under various scenarios

6+6 with RTC, BB Hopping

2 Verification of DL FER under various scenarios

6+6 with RTC, No Hopping

3 Verification of MEAN_BEP and CV_BEP under various scenarios

8-omni, 4 Way, RF Hopping, 900 Band, UL DTX OFF, DL DTX OFF


8-omni, 4 Way, RF Hopping, 900 Band, UL DTX ON, DL DTX OFF


8-omni, 4 Way, RF Hopping, 900 Band, UL DTX OFF, DL DTX ON


8-omni, 4 Way, RF Hopping, 900 Band, UL DTX ON, DL DTX ON


DN0749988 Issue 2-0 en 18/01/2008


67 (381)

2.3.9.1 Verification of UL FER under various scenarios

The objective of the test case is to verify the UL FER reporting by the BTS to the BSC in the following cases:

• In absence and presence of external interference

• In absence and presence of averaging of measurement reports

• For non-AMR and AMR calls

• During speech and silent periods


1. EMR and FER are enabled (See Setting as detailed above).

2. Averaging value (BMA) is set to 1 (No averaging).

3. There is no external interference applied.

4. AMR is disabled (See Setting as detailed above).

5. Enable UL DTX (See Setting as detailed above).


1 Establish a non-AMR FR MS-MS call. Voice call is successfully established. Verify that the speech quality is good

2 For about two minutes, observe the "MEAS RES" message on the GSM Abis analyser.

The UL FER value reported tends towards 0 and does not vary much.

3 Introduce co-channel GMSK interference in ongoing voice call in Uplink direction using signal generator. Now observe the "MEAS RES" message on the GSM Abis analyser.

The UL FER value is higher as compared to step 2.

4 Increase the co-channel GMSK interference further.

The UL FER increases.

5 At sufficiently high levels of interference, press mute button on the MS.

During silence periods when the DTX is applicable, the FER value is not calculated by BTS (reported as 0).

Note: It may be observed that UL FER may be calculated for non-contained units during silence. That is, reports sent during start and end of silence period.

6 Now reduce the co-channel GMSK interference and bring it back to zero levels.

Terminate the MS-MS call.

The UL FER should come back to zero as was seen in step 2.

The call should be released.



DN0749988Issue 2-0 en18/01/2008


7 Repeat the steps 1 to 6 for BMA = 2 by changing the BMA using ZEQM command.

Similar observations as seen in steps 1 to 6 above should be seen. In addition UL FER data should be reported two times, once each for two reporting periods.


Similar observations as seen in step 1 to 6 above should be seen. In addition UL FER data should be reported four times, once each for four reporting periods.

9 Enable AMR call using ZEQY.

Repeat the steps 1 to 8 for an FR AMR MS-MS call.

Similar observations as listed in steps 1 to 8.


Repeat the steps 1 to 8 for an HR AMR MS-MS call.


2.3.9.2 Verification of DL FER under various scenarios

The objective of the test case is to verify the DL FER reporting by BTS to BSC under following cases:









5. Deactivate both UL and DL DTX (See Setting as detailed above).


1 Establish a non-AMR FR MS-MS call. Voice call is successfully established. Verify that the speech quality is good.


The DL FER value reported tends towards 0 and does not vary much.

3 Introduce co-channel GMSK interference in The DL FER value is higher as compared to


DN0749988 Issue 2-0 en 18/01/2008


69 (381)

Step Input Expected output ongoing voice call in Downlink direction using signal generator. Now observe the "MEAS RES" message on the GSM Abis analyser.

step 2.

4 Increase the co-channel GMSK interference further.

The DL FER increases.



The DL FER should come back to zero as was seen in step 2.

Call should be released.


Similar observations as seen in steps 1 to 5 above should be seen. In addition DL FER data should be reported two times, once each for two reporting periods.


Similar observations as seen in step 1 to 5 above should be seen. In addition DL FER data should be reported four times, once each for four reporting periods.


Repeat the steps 1 to 7 for an FR AMR MS-MS call.


9 Repeat the steps 1 to 7 for an HR AMR MS-MS call.


2.3.9.3 Verification of MEAN_BEP and CV_BEP under various scenarios

The objective of the test case is to verify the reporting of MEAN_BEP and CV_BEP by the BTS to the BSC in the following cases:




• With DTX disabled and enabled






5. Activate/Deactivate UL and DL DTX as per test case comment (See Setting as detailed above).



DN0749988Issue 2-0 en18/01/2008


1 Establish a non-AMR FR MS-MS call. Voice call is successfully established. Verify that the speech quality is good.


For the downlink, observe the following in the "Enhanced Measurement Report" sent by MS to the BSC via the BTS:

MEAN BEP is near 31

CV BEP is near 7

RX QUAL FULL/SUB is near 0

RX LEV FULL/SUB is near 63

For the uplink, observe the following in the Uplink measurements sent by the BTS to the BSC:

MEAN BEP is near 31

CV BEP is near 7

RX QUAL FULL/SUB is near 0

RX LEV FULL/SUB is near 63

Note: When DTX is active, the "SUB" values are looked at, while when DTX is OFF, then the "FULL" values are looked at.

3 Introduce co-channel GMSK interference in ongoing voice call in both uplink and downlink direction using signal generator. Now observe the "MEAS RES" message on the GSM Abis analyser.

For both uplink and downlink, the following are observed with increasing interference:

MEAN BEP decreases

CV BEP decreases

RX QUAL FULL/SUB increases

RX LEV FULL/SUB is nearly the same

Note: When DTX is active, the "SUB" values are looked at, while when DTX is OFF, then the "FULL" values are looked at.



The parameter values should come back to values seen in step 2.

Call should be released.


Repeat the steps 1 to 4 for an AMR FR MS-MS call.



Repeat the steps 1 to 4 for an AMR HR MS-MS call.



DN0749988 Issue 2-0 en 18/01/2008


71 (381)

2.3.10 Air Interface Measurement Pre-processing

Overview For an established call, the BTS always sends measurement reports for each TCH channel in the Uplink direction (towards the BSC) at regular intervals, based on which a number of decisions are made at the BSC.

For each channel, the measured parameters, such as Rx_level and Rx_qual, shall be the average of the received signal level measurement samples taken on that channel within the reporting period of length of one or multiple SACCH multiframes (1 to 4) depending on the Averaging parameter set at the BSC.

Scope of testing The scope of testing includes verification of measurement reporting at correct intervals and in sequence for both SDCCH sub-channels and TCH channels.

Settings None.

Test cases

Pos Name Comment

1 Measurement_reporting_Varying_Averaging_period

Non Hopping, TCH configured as TCH/F

2 Measurement_reporting_Varying_Averaging_period

Non Hopping, TCH configured as TCH/H

2.3.10.1 Measurement_reporting_Varying_Averaging_period

The purpose of this test case to verify that the measurement reports are sent in sequence and at the correct interval when calls are established on SDCCH and TCH channels in accordance with the values set for the averaging period.


1. The averaging period parameter BMA is set as '1' and can be verified with the command below.

>>>‘ZEQO:BTS=<bts_id>:MIS:;’


1 Establish an MS to MS call between the MS in sector 1 to MS in sector 2.

Calls are successfully established between the MS.



DN0749988Issue 2-0 en18/01/2008


2 Observe the CHAN. ACT messages on the GSM Abis analyser for assignment of SDCCH sub-channels.

Observe the Measurement reports for SDCCH sub-channels on the GSM Abis Analyser.

The CHAN. ACT message with Channel Mode -"signalling" indicates the “SDCCH sub-channel” which are assigned for the originating and terminating call.

The "Measurement results" for the active SDCCH sub-channel start from Meas. Res. Nr. "0" and continue to increase in steps of '1'.

The "Measurement results" for the SDCCH sub-channel stop when the SDCCH sub-channel has been released.

Measurement result messages are observed in intervals of ~ 0.5 sec for the SDCCH/sub-channel.

3 Observe the CHAN. ACT messages on the GSM Abis analyser for assignment of TCH.

Observe the Measurement reports for the TCH channels on the GSM Abis Analyser.

The CHAN. ACT message with Channel Mode -"speech" indicates which “TCH” are assigned for the originating and terminating call.

The "Measurement results" for the active TCH start from Meas. Res. Nr. "0" and continue to increase in steps of '1'.

After Meas. Res. Nr. "255", the Meas. Res. start again from Meas. Res. Nr. "0".

Measurement result messages are observed in intervals of ~ 0.5 sec for active TCH channels.

4 Disconnect the existing call. Calls are disconnected successfully.

The "Measurement results" for the TCH stop when the TCH channel have been released.

5 Repeat steps 1 to 4 for 5 times. Observations as in steps 1 to 4.

6 Modify the averaging period for sector 1 and sector 2 with the MML command "ZEQM:BTS=<bts id>:BMA=4:;".

Averaging period "BMA" is modified successfully for sector 1 and sector 2.

7 Repeat steps 1 to 4 for 5 times. Calls are successfully established between the MS.

Observations as in steps 1 to 4. However, the interval between the Measurement result messages is observed to be ~ 2 sec.

8 Modify the averaging period for sector 1 and sector 2 with the MML command "ZEQM:BTS=<bts id>:BMA=1:;"

Averaging period "BMA" is modified successfully for sector 1 and sector 2.


DN0749988 Issue 2-0 en 18/01/2008


73 (381)


9 Repeat steps 1 to 4 for 5 times. Calls are successfully established between the MS.

Observations as in steps 1 to 4. The interval between the Measurement result messages is ~ 0.5 sec.

10 Repeat steps 1 to 9 so that observations are verified for HR 0 and HR 1( both sub-channels of TCH).

Note: This step is valid only for TCH/H configuration.

Observations as in steps 1 to 9 for HR 0 and HR 1(both sub-channels of the TCH).

2.3.11 Enhanced Automatic Frequency Correction

Overview Enhanced Automatic Frequency Correction feature (E-AFC) accounts for good RF performance when mobile user is travelling at high speed, which otherwise gets impaired by frequency errors introduce because of Doppler shifts (caused by the mobile user physically moving at high speed).

The Enhanced Automatic Frequency Correction algorithm estimates the frequency errors and attempts to cancel these in the received signal path, by calucating a long-term coarse (average) frequency offset value which gets updated on each new burst received per user. This 'average' value is used to apply a coarse correction to subsequent bursts from the same user therby enabling proper comminication without breakage while the user is moving.

Scope of testing This test plan covers the application of Enhanced Automatic Frequency Correction in case of SMS (SDCCH - signalling channel), AMR/FR and AMR/HR calls.

Test cases

Pos Name Comment

1 Enhanced Automatic Frequency Correction - SDCCH

6+6, BB Hopping

2 Enhanced Automatic Frequency Correction - TCH

6+6, non Hopping, AMR/FR & AMR/HR, GSM 900

3 Enhanced Automatic Frequency Correction 6+6, BB Hopping,



DN0749988Issue 2-0 en18/01/2008

Pos Name Comment - TCH AMR/FR & AMR/HR,

GSM 1800

2.3.11.1 Enhanced Automatic Frequency Correction – SDCCH

The objective of the test case is to verify that Enhanced Automatic Frequency Correction (E-AFC) happens properly for SDCCH channels and the SMS sent on these channels is received without any error.



• Shielding box


1. Four mobiles are used, MS1..4. Two used for Mobile Originating SMS and 2 for Mobile Terminating SMS.

2. Fading simulator is used to change the distance of the mobile from the BTS in 5 to 30 km at the speed of 300 km/h. It is connected between the MS (used for receiving the SMS) and the BTS.

3. MS(s) used for receiving SMS are kept in the shielding box.


1 Using the fading simulator, continuously Increase/decrease the distance at 300 km/h speed of the mobiles (terminating) connected w.r.t BTS. (This step is applicable throughout the testcase)

-

2 Send 10 messages (concatenated SMS of 600 character length each) one after another from MS1 to MS2 and from MS3 to MS4.

All messages are successfully sent/received by the mobiles without any error.

3 Observe the measurement report of the SDCCH channels on the Abis interface.

The measurement reports indicate that rxqual_full tends to zero and UL FER tend to zero for all the channels.

4 Repeat steps 1 to 3 for 5 times. Same output as in steps 1 to 3.


DN0749988 Issue 2-0 en 18/01/2008


75 (381)

2.3.11.2 Enhanced Automatic Frequency Correction – TCH

The objective of the test case is to verify that Enhanced Automatic Frequency Correction (E-AFC) happens properly in case of AMR/FR and AMR/HR calls without call quality degradation.



• Shielding box


1. Four mobiles are used, MS1..4 for making 2 Mobile Originating (MO) + 2 Mobile Terminating (MT) calls

2. Fading Simulator is used to change the distance of the mobile from the BTS in 5 to 30 km at the speed of 300 km/hr range. It is connected between MS (used for terminating the call) and the BTS.

3. MS used for terminating calls are kept in the shielding box.


1 Using the fading simulator, continuously Increase/decrease the distance at 300 km/h speed of the mobiles (terminating) connected w.r.t BTS. (This step is applicable throughout the testcase)

-

2 Establish 4 AMR/FR calls 2 MO and 2 MT.

Actively listen to the speech of all calls for 15 minute.

Observe the Measurement reports on the GSM Abis Analyser for all calls.


Voice quality is good without disturbances or cracking sound on all mobiles.

The Enhanced Measurement reports indicate that rxqual_full tends to zero, DL FER and UL FER tend to zero for all the calls.



4 Establish 4 AMR/HR calls 2 MO and 2 MT.

Actively listen to the speech of all calls for 15 minute.

Observe the Measurement reports on the GSM Abis Analyser for all calls.


Voice quality is good without disturbances or cracking sound on all mobiles.

The Enhanced Measurement reports indicate that rxqual_full tends to zero, DL FER and UL FER tend to zero for all the



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output calls.



6 Repeat steps 1 to 5 for 5 times. Same output as in steps 1 to 5.

2.3.12 CCCH Improvements

Overview The Common Control Channel (CCCH) scheduling algorithm has been improved to allow priority for access grant messages over paging messages when there are no BTS access grant resources available.

The performance of the CCCH can be monitored with counters provided by the BTS. These counters are sent to the BSC in the message 'CCCH_LOAD_IND'. The number of paging messages that had to be deleted because of excessive paging load is calculated and reported. The average and maximum occupation of paging buffers is then reported as percentages.

Scope of testing Testing the exact algorithmic improvements are outside the scope of this test plan. Thus, it is not possible to specify the exact values of CCCH statistics reported by Flexi EDGE BTS. However, what can be tested through external observations is that the downlink load reporting is done as per expected behaviour over the Abis.

Additionally, it is tested that even when there are no AGCH resources assigned, the Immediate Assignment messages can be carried over the Paging Channels.

Configuration

Item Details


Channel Configuration Sector 1:

BCCH TRX: MBCCH + SDCCH/8 + 6 TCH/H


Sector 2:

BCCH TRX: MBCCHC + SDCCH/8 + 6 TCH/H



DN0749988 Issue 2-0 en 18/01/2008


77 (381)

Settings 1. Number of Access Grant Blocks in a 51-frame multiframe. >>>ZEQJ:BTS=<bts_id>:AG=<BS_AG_BLKS_RES >;

DECIMAL NUMBER 0 ... 7 (IF COMBINED BCCH NOT USED)

1 ... 7 (IF CBCH USED AT SDCCH/8)

0 ... 2 (IF COMBINED BCCH USED)

2. Number of 51-frame multiframes after which the Paging cycle repeats itself.

>>>ZEQJ:BTS=<bts_id>:MFR=<BS_PA_MFRMS >; RANGE: DECIMAL NUMBER 2 ... 9

Additional information The main parameters in CCCH Load Indication (downlink) include:

• Paging Load: This indicates the available buffer space.

• Supplementary Load Info: This includes:

− Average Buffer Occupancy Percentage field: This indicates average paging buffer occupancy percentage during the reporting period. The range of this parameter is 0...100% with 1% intervals.

− Maximum Buffer Occupancy Percentage field: This indicates maximum paging buffer occupancy percentage during the CCCH_LOAD_IND reporting period. It is the peak value of all ABO values, which are calculated at the end of each paging multiframe cycle during the concerned CCCH_LOAD_IND reporting period. The range of this parameter is 0...100% with 1% intervals.

− Number of Deleted Paging Commands field: This indicates the number of deleted paging commands during the reporting period. The range of this parameter is 0...65535.

• Radio Interface CCCH Load: This includes:

− Radio Block Occupancy Paging: This indicates the average paging load in Radio interface during the reporting period. The range of this parameter is 0…100% with 1% intervals. The radio block occupancy percentage for paging messages (occupied radio blocks vs. all radio blocks during the reporting period) is calculated and reported in

− Radio Block Occupancy DRX AGCH: This indicates the average DRX AGCH load in Radio interface during the



DN0749988Issue 2-0 en18/01/2008

reporting period. The range of this parameter is 0...100% with 1% intervals. The radio block occupancy percentage for AGCH messages requiring DRX (occupied radio blocks vs. all radio blocks during the reporting period) is calculated and reported in CCCH_LOAD_IND message.

− Radio Block Occupancy non-DRX AGCH field: This indicates the average non-DRX AGCH load in Radio interface during the reporting period. The range of this parameter is 0...100% with 1% intervals. The radio block occupancy percentage for AGCH messages not requiring DRX (occupied radio blocks vs. all radio blocks during the reporting period) is calculated and reported in CCCH_LOAD_IND message.

Test cases

Pos Name Comment

1 Testing CCCH Load Reporting for Combined/Non-combined BCCH

6+6, BB Hopping

2.3.12.1 Testing CCCH Load Reporting for Combined/Non-combined BCCH

The objective of the test case is to verify the load reporting for both combined and non-combined channel combination. It is also confirmed that Flexi EDGE BTS allows Immediate Assignment messages to be carried over AGCH when no AGCH channels are reserved for such messages.


• Air interface monitor mobile


1. Sector 1 is configured with non-combined BCCH (MBCCH).

2. Sector 2 is configured with combined BCCH (MBCCHC).

3. Set AG and MFR for sector 1 such that there are a total of 24 paging groups (AG=3, so PCH = 9 – 3 = 6, MFR = 4, Total Paging Groups = 6*4 = 24.

>>>ZEQJ:BTS=<bts_id>:AG=<BS_AG_BLKS_RES >;


4. Set AG and MFR for sector 2 such that there are a total of 9 paging groups (AG=0, so PCH = 3 = 3, MFR = 3, Total Paging Groups = 3*3 = 9.


DN0749988 Issue 2-0 en 18/01/2008


79 (381)

>>>ZEQJ:BTS=<bts_id>:AG=<BS_AG_BLKS_RES >;


5. GPRS/EGPRS is disabled so that GPRS CCCH statistics are not reported.

>>>ZEQV:BTS=<BTS identification>,GENA=N;

>>>ZEQV:BTS=<BTS identification>:EGENA=N;




1 While both sector are in supervisory and without any ongoing call, observe the CCCH Load Indication for downlink for sector 1 and 2. Observe the following:

• Paging Load

• Supplementary Load Info

- Average Buffer Occupancy

- Maximum Buffer Occupancy

- Num. of Deleted Paging Cmds

• Radio Interf. CCCH Load

- Radio Block Occupancy Paging

- Radio Block Occup DRX AGCH

- Radio Block Occ non-DRX AGCH

All parameters except paging load will be 0 (because there are no ongoing calls). Paging load indicates the available buffer space.

[Note: Exact values for reported variables are beyond the scope of this test case].

2 Make MS-MS calls on sector 2. Calls are possible even when no AGCH blocks are reserved.

3 Calls are loaded in both the sectors. Depending upon the loading and distribution of paging command (in time domain and based on paging groups), the aveage and max buffer space varies.

Make an intuitive assessment of observations for any anomaly. As an example, in light load, the number of deleted paging commands would be 0. When pages exceed the outgoing capacity of the BTS, then the paging messages can be reported as deleted.



DN0749988Issue 2-0 en18/01/2008

2.3.13 Support for Different Training Sequence Codes (TSC)

Overview In the GSM system, the BCC (Base Station Colour Code) is transmitted in the SB (Synchronisation Burst) and is used in the MS (Mobile Station) to discriminate between cells using the same frequencies during the cell selection and camping on process. The BCC is also used to identify the TSC (Training Sequence Code) to be used when reading the BCCH (Broadcast Control Channel).

The TSC for the BCCH TRX object is always the same as the BCC set for that sector.The TSC for the non-BCCH TRX defined in a non-hopping or an RF hopping sector can be the same as that of the BCC ( Base Station Colour Code) or different from that set as the BCC for that sector. Scope of testing The scope of testing includes the following:

• Calls made in RF hopping sectors when the TSC of the BCCH carrier and the non-BCCH carrier are not the same.

• TRX loop tests for BCCH and non-BCCH carriers when TSC of non-BCCH carrier is different from the BCC

Test cases

Pos Name Comment

1 Call Set Up when TSC of non-BCCH carrier is different from BCC

2+4+2

2 TRX Loop Test 2+4+2, TSC of non-BCCH carrier different from BCC

2.3.13.1 Call Set-Up When TSC of Non-BCCH Carrier Is Different From BCC

This test case verifies that the calls are successful on the BCCH carrier and the non-BCCH carrier when the TSC of the non-BCCH carrier is not the same as the TSC of the BCCH carrier in the sector.

TSC Configuration

Sector Configuration

Sector 1 BCCH TRX: 2, Non_BCCH TRX: 3

Sector 2 BCCH TRX: 5, Non_BCCH TRX:1

Sector 3 BCCH TRX: 4, Non_BCCH TRX: 7


DN0749988 Issue 2-0 en 18/01/2008


81 (381)

Pre-setup:

1. The BTS site is in the operational state with no unexpected alarms.

2. Adequate test mobiles attached to the BTS.


1 Initiate an MS-MS calls from MS in sector 1 to MS in sector 2.

Observe the messages on the GSM Abis Analyser.


The CHAN. ACT message with Channel Mode -"speech" indicates which “TCH” are assigned for the call.

The ASSIGNMENT COMMAND message for the above traffic channel indicates the TSC which is used.


Observe the Measurement reports on the GSM Abis Analyser.


The measurement reports sent to the BSC for the active TCH channels indicate good voice quality. (Rx_qual tending to zero).

3 The call established in step 1 is held for about 5 minutes and then disconnected.

Throughout the duration of the call, the voice quality is good without disturbances or cracking sound.

Call is successfully disconnected.

4 Repeat steps 1 to 3 for 10 times so that calls are established on TCH channels of the BCCH carrier and the non-BCCH carrier.

Observations as in steps 1 to 3.

Calls are established successfully on all attempts using TCH channels of the BCCH carrier and the non-BCCH carrier of sector 1 and sector 2.

5 Lock the non-BCCH carrier of sector 1. Modify the TSC of the non-BCCH carrier.[TSC different from BCC].

Unlock the non-BCCH carrier of sector 2.

Non-BCCH TRX of sector 1 comes into supervisory state.

6 Repeat steps 1 to 3 for five times. Observations as in steps 1 to 3.

Calls are established successfully on all attempts using TCH channels of the BCCH carrier and the non-BCCH carrier of sector 1 and sector 2.

7 Reset the BCF from the BSC. The BCF is reset and then comes up in Supervisory state.

8 Repeat steps 1 to 3 for five times so that calls are established on TCH channels of the BCCH carrier and the non-BCCH carrier.


Calls are established successfully on all attempts using TCH channels of the BCCH



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output carrier and the non-BCCH carrier of sector 1 and sector 2.

2.3.13.2 TRX Loop Test

This test case also verifies that if TRX loop test is executed on either the BCCH or the non-BCCH carrier, the test is always successful irrespective of the value of the TSC of the BCCH and non-BCCH carrier.


1. Flexi EDGE BTS Manager is connected to the BTS.

2. Verify that the 'TSC' of the non-BCCH carrier is as per the variation for the test case.

>>>" ZERO:BTS=<bts id>:;"


1 Initiate a DSP-ABIS 1-AIR 3 loop test for any TCH timeslot of the BCCH carrier of sector 1 from the Flexi EDGE BTS Manager "Loop Test" window.

Note that the test is initiated for a duration of at least 60 seconds. The test cannot be initiated for any of the control timeslots.

The test is successfully initiated with the following alarm displayed at the Flexi EDGE BTS Manager Alarm window - "RTSL is in test use" for the timeslot on which the test is initiated.

2 Verify that the test initiated in step 1 is successful using the 'Loop Test' window of the Flexi EDGE BTS Manager.

The 'Ongoing' status for test initiated in step 1 on the 'Loop Test' window of the Flexi EDGE BTS Manager indicates that the loop test has been initiated successfully.

The Test result - "Passed" in the Test Report Parameters after the duration of the test indicates that the test has been completed successfully.

3 Repeat steps 1 and 2 at least 5 times for different timeslots of the BCCH carrier.

The TRX loop test is successful on all the attempts on the BCCH carrier.

4 Initiate a DSP-ABIS 1-AIR 3 loop test for any TCH timeslot of the non-BCCH carrier of sector 1 from the Flexi EDGE BTS Manager "Loop Test" window.

The test is successfully initiated with the following alarm displayed at the Flexi EDGE BTS Manager Alarm window - "RTSL is in test use" for the timeslot on which the test is initiated.

The Test result - "Passed" in the Test Report Parameters after the loop test has


DN0749988 Issue 2-0 en 18/01/2008


83 (381)

Step Input Expected output been executed indicates that the test has been completed successfully.

5 Repeat step 4 for five times on different timeslots of the non-BCCH carrier..

Observations as in step 4.

The TRX loop test is successful on all attempts on the non-BCCH carrier.

6 TRX loop test is carried out in sector 2.

Repeat steps 1 to 5 for sector 2.


The TRX Loop test is successful on all attempts on the BCCH carrier and non-BCCH carrier of sector 2.

2.3.14 Intelligent Frequency Hopping (IFH)

Overview Intelligent frequency hopping is designed to allow the operator to reuse frequencies more intensively, and therefore achieve a higher radio network capacity.

This feature allows the use of separate Mobile Allocation Frequency Lists of RF hopping for regular layer and the super-reuse layer. BB hopping is implemented by treating the regular layer as a normal cell and the super-reuse layer as a new hopping group.

Scope of testing The scope of the test includes verification the successful configuration of the feature and verifying that calls can be made in each layer.

Additional information Using ZERC/ZERM: TRX definition while creation or modification put

FRT(TRX FREQUENCY TYPE) <>0

Test cases

Pos Name Comment

1 Intelligent Frequency Hopping configuration

4+4, RF hopping in all sectors



DN0749988Issue 2-0 en18/01/2008

2.3.14.1 Intelligent Frequency Hopping Configuration

The objective of the test case is to verify that the intelligent frequency hopping can be enabled and disabled successfully.


1. The BTS is configured without intelligent frequency hopping.

2. All the TRXs are operational without any alarm.


4. Intra-cell handovers are enabled.


1 Place calls on all TRXs of second BTS object. All calls are successful.

2 The first BTS sector is locked at the BSC. The TRXs state is observed at Flexi EDGE BTS Manager.

All TRXs in first sector are in locked state. Second sector TRXs are operational.

3 After locking the TRXs, half of the TRXs in the sector are configured as regular layer TRXs.

Note that the BCCH is on regular layer.

Rest are configured as super reuse layer TRXs. TSC value for super reuse layer TRXs should be different from regular layer TRXs.

The same hopping is defined in both layers (as defined in test plan).

BTS is unlocked.

After unlock, the BTS resets and all the TRXs come to operational state.

4 The BTS configuration is observed at the BSC. Observe FRT value.

The TRXs defined with super reuse frequencies are shown in super reuse layer (configured FRT value seen). The TRXs defined with regular layer frequencies are shown in regular layer.

5 Verify the TRX frequencies at the BTS Manager.

At BTS Manager, if BB Hopping is in use, correct frequency is displayed for all TRXs.

If RF hopping is in use, it indicates hopping is in use.

6 Place calls on all TRXs of first BTS object.

Monitor the calls for 5 minutes.

Observe the calls on second sector.

The new calls are placed successfully and are stable.

Calls in 2nd BTS are still ongoing.

7 The first BTS is locked at the BSC. The TRXs state is observed at BTS Manager.

All the calls on 1st BTS are released.

All TRXs in first sector are in locked state


DN0749988 Issue 2-0 en 18/01/2008


85 (381)


8 All the TRXs are locked and then configured as normal TRX (FRT set to 0) at the BSC. The BTS object is unlocked.

After unlock, the BTS object is reset and all the TRXs come to operational state.

9 Place calls on all TRXs of first BTS object.

Monitor the calls for 5 minutes.

Observe the calls on second sector.

The new calls are placed successfully and are stable.

Calls in 2nd BTS are still ongoing.

2.3.15 FACCH Call Setup

Overview When an MS requests a dedicated resource by sending a random access, the BSC tries to allocate an SDCCH for the MS. If there are no SDCCHs available at that moment, the BSC tries to allocate a TCH instead of rejecting the resource request. If there are free TCHs, FACCH Call Set-up is used to assign the MS from the CCCH to the TCH - instead of the SDCCH - with the immediate assignment procedure. The FACCH is used for call set-up signalling instead of the SDCCH. The TCH is used for signalling and thus no assignment procedure is needed in the radio interface. Instead, only the mode modify procedure is required to change the channel mode from signalling to, for example, speech or data.

Scope of testing The scope of testing for FACCH Call Set-up includes the establishment of Emergency calls and Mobile to Mobile calls using FACCH Call Set-Up.

Configuration

Item Details

Hopping Sector 1 - Non Hopping, Sector 2 - RF Hopping, Sector 3 - Non Hopping

Settings 1. Dynamic SDCCH feature should be de-activated. >>>“ZWOC:<>Class=10,<>Number=42,<>Value=0:;”

2. FACCH call setup feature should be activated. >>>“ZWOC:<>Class=10,<>Number=15,<>Value=FF:;”

Test cases



DN0749988Issue 2-0 en18/01/2008

Pos Name Comment

1 Emergency Call Set-Up Through FACCH TCH configured as TCH/F

2 FACCH Call Set Up TCH configured as TCH/D

2.3.15.1 Emergency Call Set-Up through FACCH

This test case verifies that emergency calls can be set up via the feature FACCH Call Set-Up.



2. Settings as mentioned in the test plan, so that FACCH call Set-up is activated.


1 Reserve all the SDCCH resources in all the sectors.

All the SDCCH resources have been reserved.

2 Initiate an emergency call (called number 112) in sector 1 using the test mobiles.

Observe the messages on the GSM Abis analyser.

The ‘Channel Required’ message indicates that the channel request is for an ‘Emergency Call’.

The signalling takes place on TCH and the signalling channel is then modified to a traffic channel through the ‘Mode Modify’ command.

The call is established successfully.

The voice quality is good without disturbances or a cracking sound.

3 Disconnect the call established in step 2. The call is successfully disconnected.

4 Repeat steps 2 and 3 for ten times so that TCH channels of the BCCH carrier and non-BCCH carrier are used.

Observations as in steps 2 and 3.

Emergency calls are established successfully on all the attempts through the FACCH call set-up procedure.

Emergency calls are successful when they are established on TCH channels of the BCCH carrier and the non-BCCH carrier through FACCH Call Set-Up procedure.

5 Repeat steps 2 to 4 in sector 2. Observations as in steps 2 to 4 for sector 2.


DN0749988 Issue 2-0 en 18/01/2008


87 (381)

2.3.15.2 FACCH Call Set-Up

This test case verifies that mobile to mobile calls can be set up via the feature FACCH Call Set-Up.



2. Settings as mentioned in the test plan, so that FACCH call Set-up is activated.




2 Initiate a mobile to mobile call from mobiles in sector 1 to mobiles in sector 2.

Observe the messages on the GSM Abis Analyser for the originating MS.(that is, in sector 1).

Call is established successfully.

For the originating MS, the "CM SERVICE REQUEST" message is observed on the TCH with the Service Type as "Originating Call".

Signalling takes place on TCH and the signalling channel is then modified to a traffic channel through the "Mode Modify" command.

3 Observe the messages on the GSM Abis Analyser for the originating MS. (that is, in sector 2).

For the terminating MS, the "Paging Response" message is observed on the TCH.

Signalling takes place on TCH and the signalling channel is then modified to a traffic channel through the "Mode Modify" command.

4 Disconnect the call established in step 2. Call is successfully disconnected.

5 Repeat steps 2 and 3 for 10 times so that mobile to mobile calls are made on the BCCH and non-BCCH carrier through FACCH call set-up procedure.

Observations as in steps 2 and 3.

Mobile to mobile calls are established successfully on all attempts through the FACCH call set-up procedure on TCH channels of the BCCH and non-BCCH carrier.

6 Repeat steps 2 to 4 in sector 2. Observations as in steps 2 to 4 - for sector 2.



DN0749988Issue 2-0 en18/01/2008

2.3.16 Base Band Frequency Hopping

Overview Baseband switching is used for frequency hopping. Both random and cyclic hopping can be used. Baseband hopping is allowed for all BTS configurations. The number of frequencies used in the frequency hopping sequence is the same as the number of TRXs in the sector.


• CS (AMR calls with UL DTX active) calls in BB hopping sector

• PS calls in BB hopping sector

Configuration

Item Details

Site configuration 12 Omni

Combining Cavity combining

Channel configuration Configuration of sector:

BCCH TRX: MBCCH + SDCCH/8 + 6 TCH/D

3 Non_BCCH TRXs: SDCCH/8 + 7TCH/D

8 Non_BCCH TRXs: 8 TCH/D

Refer to Note below for allocating SDCCH on the non-BCCH TRXes.

Item Details

Site configuration 6 (900) + 6 (1800)

Combining Cavity Combining

Channel configuration Configuration of sector:

BCCH TRX: MBCCH + SDCCH/8 + 6 TCH/F

1 Non_BCCH TRXs: SDCCH/8 + 7TCH/F

4 Non-BCCH TRXs: 8 TCH/F

Refer to Note below for allocating SDCCH on the non-BCCH TRXes.

Note: SDCCH/8 should be allocated on Timeslot 0 of some non-BCCH TRXs. Settings 1. Command to enable BB Hopping at the BSC:


DN0749988 Issue 2-0 en 18/01/2008


89 (381)

>>>ZEQE:BTS=<BTS no>:HOP=BB, HSN1=xx, HSN2=yy;y;

where HSN1 and HSN2 shall be set for random (1-63) hopping.

2. Uplink DTX should be enabled at the BSC: >>>ZEQM:BTS=<BTS no>:DTX=<1 for will use>;

Test cases

Pos Name Comment

1 CS Call Support in a BB Hopping Sector AMR/FR & HR calls, 12 Omni, BB Hopping

2 CS Call Support in a BB Hopping Sector AMR/FR calls, 6+6 , BB Hopping

3 PS Data Transfer Support in a BB Hopping Sector

PS calls, 12 Omni, BB Hopping

4 PS Data Transfer Support in a BB Hopping Sector

PS calls, 6+6, BB Hopping

2.3.16.1 CS Call Support in a BB Hopping Sector

The objective of the test case is to verify calls are successfully established in a Baseband Hopping sector.


• Mobile call generator for establishing speech calls


None


1 Establish AMR FR speech calls on the same timeslots of all TRXs in the sector.

Each call should be established for a duration of 5 minutes.

AMR calls are successfully established in the sector.


2 Monitor the call for 5 minutes. Observe the following in Measurement Results (for both TCH and SDCCH) on the GSM Abis Analyser:

: RX Qual

: FER



3 Observe Traffic Trace at Flexi EDGE BTS The radio timeslots on which call is



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output Manager for the CS calls established. established are seen as active on the Traffic

Trace screen at Flexi EDGE BTS Manager.



5 Initiate multiple SMSes simultaneously from 6 additional mobile phones. Repeat the sending of SMS for 4 times.

Observe the following in Measurement Results for SDCCH on the GSM Abis Analyser

: RX Qual


2.3.16.2 PS Data Transfer Support in a BB Hopping Sector

The objective of the test case is to verify PS data transfer sessions are successfully established in a Baseband Hopping sector.

Note: File upload of 1 Mb and file download of 5 Mb will be attempted.


1. For the 6+6 configuration, GPRS is enabled on one sector and EGPRS is enabled on the other sector.

2. For the 12 Omni configuration, GPRS and EGPRS both are enabled.


1 Use the BSC command


so that all GP timeslots are allocated on the BCCH TRX.

Enable GPRS/EGPRS services on Mobile.

Verify that command is executed successfully.

Verify that MS get attached successfully for GPRS/EGPRS services.

2 Establish multiple PS data transfer sessions on the sector.

Initiate file upload as well as download.

Upload a file by executing following command on ftp prompt: put <filename>

Download a file by executing following

Verify that the sessions are established successfully.

Verify that complete file is uploaded/ downloaded correctly.

Verify that desirable throughput is seen on the ftp application.


DN0749988 Issue 2-0 en 18/01/2008


91 (381)

Step Input Expected output command on ftp prompt: get <filename>

3 Observe Traffic Trace at Flexi EDGE BTS Manager for the PS data transfer sessions established.

All Gp timeslots at the BSC are shown as active at the Traffic Trace screen of the Flexi EDGE BTS Manager.

4 Keep some trace mobiles in idle mode, latched to the BCCH frequency.

Verify that during the PS data transfer sessions, the trace mobiles do not lose service and continue to remain latched to the BCCH frequency.


Verify that file upload/download takes place successfully for each session.

6 Set BFG set to 2 such that GP timeslots are allocated on the non-BCCH TRX.


Repeat test step 2 above.

Verify that the output is as expected in test steps 2 above.


Verify that file upload/download takes place successfully.

2.3.17 Dynamic SDCCH Allocation

Overview Dynamic Stand-alone Dedicated Control Channel (SDCCH) is an application software in the BSC. It enables the configuration of SDCCH resources according to the actual SDCCH traffic situation of a cell. When the BTS temporarily needs larger SDCCH capacity than normally, the BSC configures idle traffic channel (TCH) resources for SDCCH use. When the SDCCH congestion situation is over, the extra SDCCH resources are configured back to the TCH resources.

The minimum static SDCCH capacity is configured at the BTS to handle the normal SDCCH traffic. An extra SDCCH resource is allocated only when the actual SDCCH congestion situation has started after the last free SDCCH is allocated. Consequently, when the dynamic SDCCH radio resource is totally free again, it is immediately configured back for TCH use. Thus, the maximum number of TCHs is always in traffic use depending on the actual need of the SDCCH resources at the time.

Scope of testing Mobile-to-mobile calls and SMS transfer using Dynamic SDCCH will be tested.



DN0749988Issue 2-0 en18/01/2008

Item Details

Site configuration 2 + 4 + 2

Hopping Sectors 1 and 3 - Non Hopping

Sector 2 - RF Hopping

Channel configuration If configuration has 4 or more TRX per sector:

BCCH TRX: MBCCH+ SDCCH/8+6 TCH/D


If configuration has less than 4 TRX per sector:

BCCH TRX: MBCCHC+ 7 TCH/D

Non_BCCH TRXs: 8 TCH/D Settings 1. Dynamic SDCCH feature should be activated.

>>>‘ZWOC:<>Class=10,<>Number=42,<>Value=FF:;’

2. FACCH call setup feature should be deactivated. >>>‘ZWOC:<>Class=10,<>Number=15,<>Value=0:;’

Test cases

Pos Name Comment

1 Call Set-up, SMS using Dynamic SDCCH 2+4+2

2.3.17.1 Call Set-up, SMS using Dynamic SDCCH

This test case verifies the basic functionality of Dynamic SDCCH. With the Dynamic SDCCH feature enabled and all SDCCH blocked, MO and MT calls are established successfully, SMS can be sent and are delivered successfully. Messages are observed on the Abis interface to verify the TCH allocation for signalling.



2. Adequate test mobiles attached to the BTS.





DN0749988 Issue 2-0 en 18/01/2008


93 (381)


2 Initiate a mobile to mobile call in sector 1.


The messages observed on the GSM Abis analyser indicate that “Dynamic SDCCH ” are assigned to normal traffic channels.


The messages observed on the GSM Abis Analyser indicate that the channel used for “Dynamic SDCCH ” are released when the calls are established and the TCH which were assigned "Dynamic SDCCH" can be used again for traffic.

3 Observe the TCH channel status using the

MML command " ZERO".

It is observed that the Channel Status is "ID" and Operational status is "WO" for TCH channels which were assigned "Dynamic SDCCH" in step 2.

4 Disconnect the call established in step 2. Call is successfully disconnected.

5 Repeat steps 2 to 4 for 10 times. Observations as in steps 2 to 4.

Calls are established successfully on all attempts using "Dynamic SDCCH" and TCH channels assigned earlier for "Dynamic SDCCH" can be assigned as traffic channels.

Calls are successful even if "Dynamic SDCCH" are assigned on normal Traffic channels of the non-BCCH carrier.

6 Repeat steps 2 to 5 in sector 2. Observations as in steps 2 to 5 for sector 2.

7 Initiate mobile to mobile calls simultaneously from 10 mobiles in sector 1 to 10 mobiles in sector 2, so that "Dynamic SDCCH" are assigned to more than 1 normal traffic channels in sector 1 and sector 2.

All the MS-MS calls are established successfully.

It is observed on the GSM Abis Analyser that "Dynamic SDCCH" are assigned to more than 1 normal traffic channels in sector 1 and sector 2 when these MS-MS calls are initiated at the same moment.

It is observed that the "Dynamic SDCCH" are released after the successful establishment of the calls, indicating that these TCH can be used for normal traffic if required.

8 Initiate an SMS between mobiles in sector 1.


SMS are delivered successfully.

It is observed that “Dynamic SDCCH ” are assigned to normal traffic channels.



DN0749988Issue 2-0 en18/01/2008


It is observed that the channel used for “Dynamic SDCCH ” are released when the SMS has been delivered and these TCH can be used again for traffic.

9 Initiate SMS simultaneously from 10 mobiles in sector 1 to 10 mobiles in sector 2 so that "Dynamic SDCCH" are assigned to more than 1 normal traffic channels in sector 1 and sector 2.


All the SMS are delivered successfully.

It is observed on the GSM Abis Analyser that "Dynamic SDCCH" are assigned on more than 1 normal traffic channels in sector 1 and sector 2 when these SMS are initiated at the same moment.

It is observed that "Dynamic SDCCH" are released after the successful delivery of the SMS, indicating that the TCH which were assigned "Dynamic SDCCH" can be used for normal traffic if required.

2.3.18 BSS Site Synchronisation Recovery Improvement

Overview When GPS signal to LMU is lost even for 24 hours period, BSS Synchronisation can be maintained by using the Abis as reference frequency. If the GPS signal is regained during the 24-hour period, the BSS Synchronisation will revert to the GPS. During the changeover from Synchronisation to an external LMU, to Synchronisation with Abis clock, the ongoing calls should not be affected.

Scope of testing The scope of the test cases is to test the BTS SW for

1. Improved BSS Synchronisation feature for LMU-Slave BCF1 -Slave BCF2-Slave BCF3

2. Recovery of Slave BCFs after a reset when sites are in Improved BSS Synchronisation mode.

Configuration For all the configurations, the type of BTS is Flexi EDGE unless explicitly mentioned as UltraSite.

Settings 1. Define clock source as LMU-Abis for first BCF >>>ZEFM:<bcf-id>:CS=LAB:;.


DN0749988 Issue 2-0 en 18/01/2008


95 (381)

2. Enable Synchronisation at the first BCF >>>ZEFM:<bcf-id>:SENA=T:;

3. Check clock source and synchronisation mode for all BCF >>>ZEFL:<bcf-id>;

Clock source is shown as "LMU-Abis" for BCF1 at BSC. Synchronisation mode is shown as "LMU Sync" for all other BCFs at BSC.

4. Check BCF Restarted due to loss of LMU Sync’ timeout parameter set to default value at BSC.

>>>ZWOI : 37,44

5. Check LMU Signal Loss (‘GPS Fix Loss to Clocks out alarm’) timer set to default value at LMU.Connect LMU Manager to LMU. Go to Advance settings. Check the value (default value is 120 sec)

Test cases

Pos Name Comment

1 BSS Synchronisation Recovery when LMU GPS Signal Lost and Regained within 24 Hrs

BCF1: 2+2, BCF2: 2+2, BCF3: 2+2, RF hopping

3 BCF Recovery after Reset to Slave BCFs in LMU chain with UltraSite and two Flexi EDGE BTSs

BCF1: 2+2 UltraSite, BCF2: 2+2, BCF3: 2+2, RF hopping

2.3.18.1 BSS Synchronisation Recovery when LMU GPS Signal Lost and Regained within 24 Hrs

The objective of this test case is to verify that in a LMU-Slave BCF1-Slave BCF2-Slave BCF3 configuration when LMU GPS signal is lost and regained within 24 hours, then

• BSS Synchronisation Recovery takes place and the BTS sites are reconfigured to Master-Slave-Slave configuration when GPS signal is lost.

• BSS Synchronisation Recovery takes place and the BTS sites are reconfigured to LMU-Slave BCF1-Slave BCF2 -Slave BCF3 configuration when GPS signal is regained within 24 hours.

• Calls are not dropped during the BSS Synchronisation Recovery process.

• No interference to other calls using another LMU as a synch source.



DN0749988Issue 2-0 en18/01/2008


• LMUB


As per the test case comment (referred to as chain 1). PCM link is connected to interface 1 for all BCFs.

Additionally, any standard configuration in LMU chain (referred to as chain 2) is used to monitor the interference because of possible drift in clock.

Pre-setup:

• All the BCFs are in supervisory state.

• Flexi EDGE BTS Manager is connected to all the Flexi EDGE BTSs.

• All the BTS objects (in chain 1 and 2) are in RF hopping and use same MA List (8-10 frequencies in the MA List) with different MAIO.

• In the Transport Priority list, Sync Input is in highest priority followed by RxClock IF1 for all BCFs and active source is Sync Input.

• LMU is connected to the BCF1 and locked to the GPS signal and GPS fix is OK as seen in LMU Manager.

• Initial value of DAC words on all BCFs is noted.


1 Establish calls on same timeslot of non-BCCH TRXs of all sectors for all the BCFs in both the chains.



2 Using Flexi EDGE BTS Manager, verify in the BCF Properties of all the BCFs of Chain 1, the Clock Source and State of Oven Tuning.

For all the BCFs, the following is seen:

Clock Source : Slave

Oven Tuning : Enabled

3 Disconnect the GPS antenna of the LMU in the chain 1.

Wait for the LMU timeout timer (2 min. by default).

On expiry of the LMU Timeout timer, check for any alarms reported for BCF 1 at the BSC and Flexi EDGE BTS Manager.

The BCF1 sends alarm 8048 “Loss of Incoming Signal” to the BSC and Flexi EDGE BTS Manager.

BCF1 sends alarm 7602 “External Synchronization Signals Disabled” to the BSC and Flexi EDGE BTS Manager.


DN0749988 Issue 2-0 en 18/01/2008


97 (381)


4 Observe the messages exchanges on the GSM Abis Analyser.

Immediately check the Oven Tuning state for BCF2 and BCF3 at the Flexi EDGE BTS Manager.

Clock control messages are exchanged for all BCFs.

For BCF2 and BCF3, the oven tuning state is disabled for a short interval while the clock source for BCF1 changes from LMU to Abis.

5 After the Clock control messages are exchanged, check the Clock Source and State of Oven Tuning for all BCFs at the Flexi EDGE BTS Manager.

For BCF1 the following is seen:

Clock Source : Master


For BCF2 and BCF3 the following is seen



6 Check the status of the ongoing calls during the Sync Recovery.

Ongoing calls are not impacted during Sync Recovery.There should not be any distrubances in the voice. Voice should be clear.

7 At the BSC, check the synchronisation mode using the command ZEFL:<bcf_id>;

The Sync mode is "Abis Sync" for all the BCFs in the chain.

8 At Flexi EDGE BTS Manager of BCF1, BCF2 and BCF3 , go to Transmission Synchronization and check the Active Source in the Transport Priority table.

For BCF1, Active source is "Rx Clock IF1"

For BCF2 and BCF3, Active source is "Sync Input"

9 At Flexi EDGE BTS Manager of all BCFs, go to BTS Control Clock control and monitor the DAC word for every hour.

For BCF1:

Current DAC word will follow the PCM frequency and change a maximum step of +/-7 steps for every 20 minutes.

Calibrated DAC word will be updated with the Current DAC word whenever the difference between them is more than +/-11 steps.

For BCF2 and BCF3:

Current DAC word will change so as to be in Sync with Master BCF with a maximum step of +/-2 steps for every 23 seconds.

Calibrated DAC word will be updated with the Current DAC word whenver the difference between them is more than +/-4 steps.

10 Check the status of test calls manually (with active speech and listening) at hourly intervals

There should not be any distrubances in the voice. Voice should be clear.



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output for the next 23 hours.

Check in the Measurement Report of the Abis Logs of both the chains that there is no interference.

Rx_QUAL and FER should tend to zero.

11 Reconnect the GPS antenna at the LMU after 23 Hours.

After few seconds, the BCF 1 sends the cancel for alarm 8048 “Loss of Incoming Signal” to the BSC and Flexi EDGE BTS Manager.

12 Verify that BCF 1 of chain 1 sends cancel for alarm 7602 to the BSC and Flexi EDGE BTS Manager.

The alarm 7602 is cancelled at the BSC and Flexi EDGE BTS Manager for BCF1.

13 Check the Clock Source and state of Oven Tuning for all BCFs at the Flexi EDGE BTS Manager.

For all BCFs the following is seen:



14 Check that the status of the ongoing calls during the Sync Recovery.

Ongoing calls are not dropped during Sync Recovery. There should not be any distrubances in the voice. Voice should be clear.

15 At the BSC, check the synchronisation mode using the command ZEFL:<bcf_id>;

The Sync mode is "LMU Sync" for all the BCF in the chain.

16 At Flexi EDGE BTS Manager of BCF1,BCF2 and BCF3, go to Transmission Synchronization and check the Active Source in the Transport Priority table.

For all the BCFs, Active source is "Sync Input"

17 At Flexi EDGE BTS Manager of BCF1, BCF2 and BCF3, go to BTS Control Clock control and monitor the DAC word for 3 hours.

For all the BCFs:

Current DAC word will change towards the initial value with a maximum step of +/-2 steps for every 23 seconds.

Calibrated DAC word will be updated with the Current DAC word whenever the difference between them is more than +/-4 steps.

2.3.18.2 BCF Recovery after Reset to Slave BCFs in LMU Chain with UltraSite and two Flexi EDGE BTSs

The objective of this test case is to verify that in a LMU-Slave BCF1 (UltraSite) -Slave BCF 2-Slave BCF 3 Chain configuration when Improved BSS Synchronisation Feature is enabled at the BSC, then

• After a BCF reset of Slave BCF, it comes up again in Slave mode.

Test environment


DN0749988 Issue 2-0 en 18/01/2008


99 (381)

Hardware tools:

• LMUB


The PCM link is connected to Interface 1 for all the BCFs.

Pre-setup:

• All the BCFs are in supervisory state and in Improved BSS Sync mode.

• Flexi EDGE BTS Manager is connected to all the Flexi EDGE BTS and BTS Manager is connected to the UltraSite BTS.

• All the BTS objects in BCFs are in RF hopping and use same MA List (at least 6 frequencies in the MA List) with different MAIO.

• LMU is connected to the UltraSite BTS and locked to GPS signal and GPS fix is OK as seen in LMU Manager.

• In the Transport Priority list, Sync Input is in highest priority followed by RxClock IF1 for all BCFs and active source is Sync Input.


1 Establish calls on same timeslot of non-BCCH TRXs of all sectors for all the BCFs.



2 Reset the BCF1. BCF 1 is reset and calls in BCF1 are released.

3 Check for alarms reported by BCF2 and BCF 3 in Flexi EDGE BTS Manager and at the BSC.

No alarms are reported for other BCFs.

4 Check the status of all the calls. Calls in BCF1 are released.

The calls in BCF2 and BCF3 are not affected.

5 After the BCF1, comes to supervisory state, check the Clock Source and State of Oven Tuning at Flexi EDGE BTS (or UltraSite) Manager.

For all the BCFs, the following is seen:

Clock Source: Slave

Oven Tuning: Enabled

6 At Flexi EDGE BTS (or UltraSite) Manager of all the BCFs, check the Active Source in the Transport Priority table.

For all the BCFs, active source is "Sync Input".

7 Establish new calls on all non-BCCH TRXs on the same timeslot (as in step1) of BCF 1.

New calls are successful, as seen on test mobiles.



DN0749988Issue 2-0 en18/01/2008


Observe the voice quality for all calls for 5 minutes with active speech and listening.

All existing calls are stable.

Voice quality is good with no disturbances for all calls.

8 Release all the ongoing calls. All the ongoing calls are released.

9 At Flexi EDGE BTS Manager of BCF2, go to BTS Control Clock control. Wait for DAC word to stabilise and note the DAC word.

The stable value of DAC word is noted.

10 Establish calls on same timeslot of non-BCCH TRXs of all sectors for all the BCFs.



11 Reset BCF 2 from the BSC.

Check the status of the calls in all BCFs.

BCF 2 is reset and calls in BCF2 are released.

Calls in BCF1 and BCF3 are not affected.

12 Check for alarms reported by the BCFs (other than the one reset in previous step) in alarm history maintained at Flexi EDGE (or UltraSite) BTS Manager and the BSC.

No alarms are reported for other BCFs.

13 After BCF2 comes to supervisory state, check the clock source and state of Oven Tuning in Flexi EDGE BTS Manager.

For BCF2:



14 At Flexi EDGE BTS Manager of BCF1, BCF2 and BCF3, go to Transmission Synchronization and check the Active Source in the Transport Priority table.

For all the BCFs, active source is "Sync Input.

15 Establish new calls on all non-BCCH TRXs on the same timeslot (as in step 1) of BCF 2. Observe the voice quality for 5 minutes with active speech and listening.

All calls are successful, as seen on test mobiles.

All calls are stable. Voice quality is good.

16 At Flexi EDGE BTS Manager of BCF2, go to BTS Control Clock control and monitor the DAC word for 1 hour.

DAC word is stable as seen before reset.


DN0749988 Issue 2-0 en 18/01/2008


101 (381)

2.4 Data

2.4.1 General Packet Radio Service (GPRS)

Overview General Packet Radio Service (GPRS) provides packet data radio access for GSM mobile phones using coding scheme CS1 and CS2.

Scope of testing The following features/functions are tested in this test plan:

• Data transfer with 2 coding schemes: CS1 – CS2 with GPRS capable mobiles

• Continuous timing advance

• Territory upgrade and downgrade

Compatibility testing: Use of PCU1 and PCU2 within the BSC

Settings None. Test cases

Pos Name Comment

1 PS data transfer with GPRS capable MS. PCU1, GSM900 band sector

2 PS data transfer with GPRS capable MS. PCU2, GSM1800 band sector.

3 Territory upgrade and downgrade in GPRS capable segment.

PCU2, GSM900 band sector

4 PS data transfer and CS call on single EDGE-capable TRX.

PCU2, BCCH TRX is the only GTRX, 900 band.

2.4.1.1 PS Data Transfer with GPRS-Capable MS

This test case verifies the selected coding schemes supported in GPRS and the expected data rates for each of these coding schemes.

Test environment Network elements:

• BSC, PCU (as a part of BSC)

• SGSN

• GGSN



DN0749988Issue 2-0 en18/01/2008

• HLR

• VLR (optional)

• FTP Test Servers

Hardware tools:

• Rel 4 mobiles


None.


1 Observe the status of channels at the BSC using the MML command:

‘ZERO: BTS= <bts_num>;’

Status of the timeslots available for PS usage is ‘GP’.

2 Attach 6 MSs. MSs display ‘G’ on the screen. This is a confirmation for the successfully attached MS.

3 After the MSs have been successfully attached, activate the PDP context for MS. This assigns IP address to the GPRS attached MS.

MSs displays (G) on the screen display. This is a confirmation that PDP context for the MSs are created successfully.

4 After the successful establishment of PDP context, open FTP session with FTP server and initiate file download (ftp-get) for 500 KB file for all the mobiles simultaneously.

Observe the data transfer for the selected coding scheme using Abis analyser.

There are no unexpected drops in the throughput figures and the data transfer rate is as expected.

5 After the successful ‘get’ operation, initiate ‘put’ for 500 KB file for all the mobiles simultaneously.



2.4.1.2 Territory upgrade and downgrade in GPRS-capable segment

This test case verifies that PS territory is downgraded for CS calls when CS call is made while all the traffic channels are occupied by PS territory. Also, verify that when PS data transfer is complete, then additional traffic channels (acquired during file transfer) are returned to the BSC.



DN0749988 Issue 2-0 en 18/01/2008


103 (381)


• SGSN

• GGSN

• HLR

• VLR (optional)


Hardware tools:

• Rel 4 test mobiles


The BTS and TRXs should be in supervisory state without any unexpected alarms.

Check that default territory size for PS is 1 %. (CDED = 0 and CDEF = 1)


1 Observe the status of channels at the BSC using the following MML command:

ZERO:BTS=<bts_num>;

The status of timeslots for PS use is ‘GP’. The status of 1 timeslot is shown as 'GP'. The number of timeslots with status as ‘GP’ depends on CDED and CDEF parameters configured for the BTS.

2 Attach 6 MSs and activate the PDP context for the MSs.

The MSs are attached and the display shows (G) on the MSs indicating successfully attached MSs.

3 Initiate file download for MSs (ftp-get) for 1 MB file.

Observe the additional timeslots upgraded for PS usage using the following MML command:

ZERO:BTS=<bts_num>;

Data transfer is successful on all the MSs.

The status of channels added for PS usage shown as 'GP'.

4 Initiate enough CS calls so that PS territory is downgraded for establishing CS calls.

Execute MML command ZERO to check status of channels at the BSC.

The CS calls are successfully established.

PS territory downgrade takes place and the "GP" timeslots on which the CS calls have been initiated have changed their "CH. STATUS" to "FR".

5 Disconnect all the CS calls. CS calls are terminated successfully.

Observed that territory is again upgraded for PS usage for ongoing file transfer.

6 After the file transfer is complete, switch off the mobiles that were in use.

Additional timeslots acquired during data transfer are returned to the BSC and territory is back to 1 timeslot with status as



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output 'GP' (since CDEF = 1).

2.4.1.3 PS data transfer and CS call on single EDGE-capable TRX




• SGSN

• GGSN

• HLR

• VLR (optional)


Hardware tools:



BTS and TRXs should be in supervisory state and no unexpected alarms should be seen on Flexi EDGE BTS/BSC.

Only 1 TRX is configured as GPRS enabled TRX at the BSC in the sector.


1 Observe the status of the channels at the BSC using the MML command:


The status of the timeslots available for PS usage is ‘GP’.

2 Attach 6 MSs. MSs display ‘G’ on the screen display. This is a confirmation for the successfully attached MS.

3 After the MSs have been successfully attached, activate the PDP context for MS. This assigns IP address to the GPRS attached MS.

MSs displays (G) on the screen display. This is a confirmation that PDP contexts for the MSs are created successfully.

4 After the successful establishment of PDP context, open an FTP session with FTP server and initiate file download (ftp-get) for a 500 KB


There are no unexpected drops in the


DN0749988 Issue 2-0 en 18/01/2008


105 (381)

Step Input Expected output file for all the mobiles simultaneously. throughput figures and the data transfer rate

is as expected.

5 Establish a CS call on EDGE TRX of the sector while data transfer is going on.

Call establishment is successful and the quality of voice is good.

The data transfer that was initiated in step-4 continues.

6 After the successful ‘get’ operation, initiate ‘put’ for 500 KB file for all the mobiles simultaneously.



Observe that data transfer is completed successfully.

7 Observe the CS call. The CS call is still going on.

2.4.2 Dual Transfer Mode

Overview Dual transfer mode (DTM) provides simultaneous Circuit Switched (CS) voice and Packet Switched (PS) data services. In the dual transfer mode, the mobile station (MS) is simultaneously in a dedicated and packet transfer mode so that the timeslots allocated in each direction are consecutive and within the same frequency. The CS part consists of a single-slot connection, whereas the PS part can consist of a multi-slot connection. Scope of testing In the context of Flexi EDGE BTS, the BTS is transparent to the DTM procedures. The role is limited to activation of CS calls and carrying the PS calls.

Settings 1. Query/Modification of DTM Mode:

>>>ZEQO:BTS=<bts_id>:GPRS;

>>>ZEQV:BTS=<bts_id>::::DENA=Y;

Test cases

Pos Name Comment

1 Testing CS and PS Call in Dual Transfer Mode

RF Hopping, PCU2



DN0749988Issue 2-0 en18/01/2008

2.4.2.1 Testing CS and PS Call in Dual Transfer Mode

The objective of the test case is to verify that CS and PS calls can be done simultaneously in Dual Transfer Mode.


• BSC, with PCU2 (PCU1 does not support DTM)

• GPRS core network elements, that is SGSN, GGSN

Hardware tools:

• DTM capable mobiles (for example, Nokia 6630 and Nokia N series, that is, N70, N71, N93)

• Laptop/PCs

• Data cables compatible with the mobiles


1. GPRS/EGPRS is enabled. Other GPRS parameters, such as link adaptation are as set for any GPRS transfer (refer to GPRS test plan for details).

2. GPRS parameters are set as follows: >>>ZEQV:BTS=<bts_id>:CDED=1, CDEF=1, CMAX=100;

3. DTM is enabled. Check DTM State and enable it. >>>ZEQO:BTS=<bts_id>:GPRS;

>>>ZEQV:BTS=<bts_id>::::DENA=Y;




1 Using DTM capable MS, initiate CS call. The call is successfully established.

Verify that the speech quality is good by manually speaking and listening on the phones for 1 minute. No glitches, background noise, speech breaks should be observed.


DN0749988 Issue 2-0 en 18/01/2008


107 (381)


2 Using the same DTM capable MS, initiate a PS call by establishing FTP data transfer in uplink direction.

During the data transfer, again note the speech quality for the ongoing CS call by manually speaking and listening on the phones for 1 minute.

Verify that the data transfer takes place successfully (known by the message displayed by the FTP application).

Verify that the speech quality is good even when data transfer is ongoing. No glitches, background noise, speech breaks should be observed during the transfer.

3 During the ongoing CS call and data transfer, check the timeslot status at the BSC.

ZERO:BTS=<bts_id>:TRX=<trx_id>;

For one the GPRS timeslots, the state “DT” is indicated. For full-rate CS timeslot, the state “FR” is indicated.

4 After the data transfer has been completed, open the received files at the destination location.

Check the ongoing CS call.

Now release the CS call normally.

Then establish PS data transfer again in uplink and downlink direction using the same DTM capable MS.

Verify that the files at the receiving ends are uncorrupted.

Also verify that CS call is ongoing normally and speech quality is good as before.

Verify that the data transfer takes place successfully in both the directions (known by the message displayed by the FTP application).

5 Analyse the Abis traces. Write down the RX Qual / BEP measurements (Mean_BEP and CV_BEP), BFI value reported in PCU Data frames/ PCU Master Data frames for PS call.

Also write down the value of Uplink RX Qual / UL Mean BEP / UL CV BEP measurements reported in Measurement Results for CS call.

Verify that the measurements reported are good and remain nearly constant for both PS and CS calls provided stable RF conditions.

2.4.3 14.4 kbit/s GSM Data Services

Overview Transparent and non-transparent circuit switched data services for 14.4 kbps are supported by the Flexi EDGE BTS.



DN0749988Issue 2-0 en18/01/2008

Scope of testing The scope of testing is limited to establishing a non-transparent CSD call with data rate configured as 14.4 kbps.

Test cases

Pos Name Comment

1 14.4 kbit/s GSM Data Call Non-Transparent CSD

2.4.3.1 14.4 kbit/s GSM Data Call

The objective of the test case is to verify that Flexi EDGE BTS supports 14.4 kbps non-transparent and transparent circuit switched data calls.


• Dialup Application


None.


1 Establish a CSD call from the MS to network.

Execute AT command at Transmitting End Cmd mode window of Dialup Application.

Execute command

at + cbst =<speed>,<name>,<ce> for example,

at + cbst = 75, 0, xx for 14.4 kbps, async, non-transparent/transparent CSD call where

xx = 0 for transparent

xx= 1 for non-transparent services.

The Transmitting End (Mobile) responds with a "Connecting" message displayed at the Command Mode window.

2 Observe the Dialup Application window at the terminating end.

Execute command "ata" at the Dialup Application Command Mode window at the Recipient end.

"Ring" message is displayed on the Command Mode window at the terminating end.

The Command is executed and the Recipient Terminal responds with the “Connect<speed>” message indicating the CSD call has been established.


DN0749988 Issue 2-0 en 18/01/2008


109 (381)


Where <speed>= 14400 bits/sec.

3 Initiate transfer of data in terminal mode by typing characters on one terminal of the Dialup Application.

Transfer data in uplink and downlink.

Verify that the typed characters are seen at the other end of the Dialup Application.

Verify that data transfer is successful in both directions.

4 Initiate transfer of data in file transfer mode by uploading a text file from one terminal of the dialup application.

Verify uplink and downlink data transfer of files.

Verify that the file is transferred successfully in both directions.

5 After the transfer of the file is complete, check the file size at both the ends.

The file size is the same at both the ends.


6 Repeat test steps 1 to 6 above 5 times. Verify that file transfer takes place successfully for each instance.


7 Establish a CSD call from MS to network.

Execute AT command at Transmitting End Cmd mode window of Dialup Application.

Execute command

at + cbst =<speed>,<name>,<ce>, for example,

at + cbst = 75, 0, xx for 14.4 kbps, aysnc, non-transparent/transparent CSD call where

xx = 0 for transparent

xx= 1 for non-transparent services.

The Transmitting End (Mobile) responds with a "Connecting" message displayed at the Command Mode window.

2.4.4 Dynamic Abis Allocation

Overview Dynamic Abis allocation is a solution for higher data rates of Enhanced General Packet Radio Service (EGPRS) to ensure cost efficiency and flexible Abis transmission capacity addition.

Scope of testing The scope of testing is limited to creating/modifying an EGPRS Dynamic Abis Pool (EDAP) for TRXs configured over a PCM link. EGPRS calls



DN0749988Issue 2-0 en18/01/2008

will be attempted to verify the utilisation of the EDAP allocated in each sector.

Territory upgrade/downgrade scenarios will be tested as part of the General Packet Radio Service (GPRS) test plan.

Settings 1. Suitable Dynamic Abis Pool Creation: >>> ZESE:ID=<>,SIZE=<>,CRCT=PCM-TSL,BCSU=<>,PCU=<>:;

2. Enable GPRS in the cell. >>> ZEQV:BTS=<BTS identification>:GENA=Y;

3. Enable EGPRS in the cell. >>> ZEQV:BTS=<BTS identification>:EGENA=Y;

4. Attach EDAP to TRX. TRX must be EDGE-capable. >>> ZERM:BTS=<BTS identification>,TRX=<RX identification>:DAP=<dynamic Abis pool

5. Enable Link Adaptation. >>> ZEQV:BTS=<BTS identification>: ELA=<EGPRS link adaptation enabled>;

Test cases

Pos Name Comment

1 EGPRS Data Transfer after EDAP Creation

2+2+2, FIPA in E1 mode

2 EGPRS Data Transfer after EDAP Creation

2+2+2, FIPA in T1 mode

3 EGPRS Data Transfer after EDAP Modification

2+2+2, FIPA in E1 mode

4 EGPRS Data Transfer after EDAP Modification

2+2+2, FIPA in T1 mode

2.4.4.1 EGPRS Data Transfer after EDAP Creation

The objective of the test case is to create an EDAP for TRXs configured on a PCM link and verify the usage of the EDAP in establishing EGPRS calls.


• Laptops required for establishing ftp connections.

Test case execution


DN0749988 Issue 2-0 en 18/01/2008


111 (381)

Pre-setup:

1. EGPRS is enabled in each sector.

2. Default GPRS/EGPRS parameter settings at the BSC.


1 Establish CS calls on all the BTS objects. CS calls are successfully established.

2 Create an EDAP at the Flexi EDGE BTS Manager from the

Transmission -> Traffic Allocations -> Select EDAP screen.

Attach all the TRXs with the EDAP.

EDAP is successfully created at Flexi EDGE BTS Manager and attached to the TRXs.

CS calls on all the BTS objects continue uninterrupted.

3 Create an EDAP at the BSC.

Note: A suggested EDAP allocation is 4 PCM timeslots on the PCM link.

MML command runs successfully. EDAP is successfully created at the BSC.

4 Lock the first BTS object.

Attach the EDAP with each TRX in the BTS object.

Enable EGPRS for this BTS object.

MML command executes successfully. EDAP is attached to all TRXs of the BTS object.

5 Observe the ongoing CS calls on the other unlocked BTS objects while the EDAP is being attached to TRXs in the locked BTS object.

CS calls on the other BTS objects continue uninterrupted.

6 Unlock the BTS object after the EDAP attach is complete.

Establish few CS calls on the unlocked BTS object.

BTS object is unlocked successfully.

CS calls are established successfully.

7 Repeat test steps 4 to 6 for the other BTS objects.

EDAP is successfully attached to all TRXs of the locked BTS object.

CS calls on the unlocked BTS objects continue uninterrupted.

8 Establish multiple ftp connections on each sector such that the entire EDAP is utilised.

Initiate ftp upload and download from the laptops.

Packet data ftp sessions are established successfully.

9 Observe PCU Data Frames on the GSM Abis Analyser.

PCU Data Frames are exchanged on all the PCM timeslots allocated for the EDAP.



DN0749988Issue 2-0 en18/01/2008

2.4.4.2 EGPRS Data Transfer after EDAP Modification

The objective of the test case is to modify the existing EDAP for TRXs on configured on a single PCM link and verify the usage of the modified EDAP in establishing EGPRS calls.

Note: The existing EDAP pool consisting of 4 PCM timeslots. The modified EDAP pool will have 6 PCM timeslots.


• Laptops needed for establishing EGPRS calls.


1. The site is in supervisory state with no major alarms.

2. An EDAP pool with 4 PCM timeslots is created for the site.


1 Establish few CS calls and PS data transfer sessions on all the BTS objects.

CS calls are successfully established.

PS data transfer sessions are successfully established.

2 Modify the EDAP at the Flexi EDGE BTS Manager from the Transmission -> Traffic Allocations -> Select EDAP screen.

EDAP is successfully modified at the Flexi EDGE BTS Manager.

3 Observe the behaviour of the ongoing CS calls and PS data transfer sessions on all the BTS objects while the EDAP is being modified at the Flexi EDGE BTS Manager.

The ongoing CS calls continue uninterrupted.

The ongoing PS data transfer sessions continue uninterrupted.

4 Modify the EDAP at the BSC using the MML command ZESM.

Note: The modified EDAP contains 6 PCM timeslots.

MML command is successful. EDAP is successfully modified at the BSC.

5 Observe the behaviour of the ongoing CS calls and PS data transfer sessions on all the BTS objects while the EDAP is being modified at the BSC.

The ongoing CS calls continue uninterrupted.

The ongoing PS data transfer sessions continue uninterrupted.

6 Establish multiple ftp connections such that the modified EDAP is entirely utilised.

Initiate a ftp upload as well as download from the laptops.

Verify that the ftp sessions are successfully established.

7 Observe PCU Data Frames on the GSM Abis PCU Data Frames are exchanged on all the


DN0749988 Issue 2-0 en 18/01/2008


113 (381)

Step Input Expected output Analyser. PCM timeslots allocated for the modified

EDAP.

2.4.5 GPRS: Coding Schemes CS-3 and CS-4

Overview General Packet Radio Service (GPRS) provides packet data radio access for GSM mobile phones. GPRS makes the radio interface usage more efficient: This feature allows allows higher data rates to be offered by GPRS capable segment when the data transfer is carried through EDGE TRXs. The data transfer in each of the coding scheme needs 1 slave channel besides the master channel and thus EDAP pool needs to be created which is attached to the EDGE TRX.

Scope of testing The following is checked to verify the SW capability of Flexi EDGE BTS to support GPRS services:

• data transfer with two coding schemes: CS3 – CS4 with GPRS capable mobiles.

Settings 1. EDAP of size 4 PCM-TSL is configured and shared between all

sectors

2. Activating CS3 & CS4 Coding Schemes at the BSC

Check that the CS3 & CS4 license is active ZW7I: FEA, FULL: FEA=2;

Activate CS3 & CS4 coding schemes for the BTS ZEQV: BTS=<BTS identification>: CS34=Y;

Test cases

Pos Name Comment

1 PS data transfer and CS call on single EDGE-capable TRX.

2+2+2, GSM 1800, Enable GTRX on BCCH TRX only and initiate all FTP's on single TRX.

2 Link adaptation for GPRS 2+2+2, GSM 1800



DN0749988Issue 2-0 en18/01/2008

2.4.5.1 Link adaptation for GPRS

This test case verifies that in a GPRS-capable segment, the Link Adaptation feature is supported for PS data transfer while CS calls are ongoing.


• BSC, PCU (as a part of the BSC)

• SGSN, GGSN

• HLR, VLR

• FTP test servers

Hardware tools:



ESMA and attached units are in supervisory state without any unexpected alarms.

Test mobiles are attached and PDP context is activated for them.


1 Initiate FTP-put for 500 KB file for 3 test mobiles.

Data transfer is initiated successfully.

2 Establish CS call. CS call is established.

3 Introduce interference using Signal Generator in uplink direction while data transfer is on-going.

(Vary the interference signal level from –100dbm to –35 dbm in steps of 5 dB each after every 10 seconds)

Verify from Abis analyser traces that coding scheme changes.

Data transfer continues.

4 Now start reducing the interference in uplink direction.

(Vary the interference signal level from –35dBm to –100dBm in steps of 5dB each after every 10 seconds)

Verify from Abis Analyser traces that coding scheme changes.


5 Receive (get) a file from the FTP server for 500KB sized file for 3 test mobiles.

FTP-get is initiated successfully.

6 Introduce interference using Signal Generator in downlink direction while data transfer is on-going.



DN0749988 Issue 2-0 en 18/01/2008


115 (381)


(Vary the interference signal level from –100dbm to –35 dbm in steps of 5 dB each after every 10 seconds)


7 Now start reducing the interference in downlink direction.

(Vary the interference signal level from –35 dbm to –100dbm in steps of 5 dB each after every 10 seconds)


2.4.6 EGPRS P-Channel Required (EPCR)

Overview When the MS wants to send data or upper layer signalling messages to the network, it requires the establishment of an uplink TBF from the BSC. With EGPRS terminals, this has typically been done as two phase access on CCCH where the MS first requests an RLC block from the BSC and after it has been assigned, the MS provides information about its EGPRS capabilities. Based on that information, a Packet Data Channel, if available, is assigned for the TBF and the MS is instructed with attributes to be used in uplink transmission by BSC.

By using EGPRS Packet Channel Request on CCCH the uplink TBF establishment can be speeded up substantially since one phase access is also available for an EGPRS MS. The MS provides information about its EGPRS capabilities already while requesting TBF establishment from the BSC. Based on this information the BSC can assign a Packet Data Channel for the TBF right away, if one is available.

Scope of testing Scope of testing is limited to testing the high level procedures like GPRS attach and packet data transfer and the role of EGPRS Packet Channel Request in these procedures when PBCCH is not configured.

Settings 1. Enable GPRS on a cell level >>>ZEQV:BTS=<BTS identification>,GENA=Y,RAC=<routing area code>;

Note: When GPRS is enabled in a cell, it is enabled in all TRXs by default. It can also enabled or disabled on a TRX level. Locking and unlocking the TRX is only necessary if EGPRS or CS3 & CS4 is enabled.

2. Enable EGPRS in the BTS.



DN0749988Issue 2-0 en18/01/2008

>>>ZEQV:BTS=<BTS identification>:EGENA=Y;

3. Disable Link Adaptation >>>ZEQV:BTS=12:ELA=0;

4. Set the initial MCS Coding Scheme (for RLC Ack/UnackMode) >>>ZEQV:BTS=<bts_id>:MCA=<initial MCS for ack mode>;

>>>ZEQV:BTS=<bts_id>:MCU=<initial MCS for unack mode>;

Test cases

Pos Name Comment

1 Testing EGPRS P-Channel Required over CCCH

Any BTS configuration

2.4.6.1 Testing EGPRS P-Channel Required over CCCH

The objective of the test case is to verify that Edge capable MS use EGPRS Packet Channel Required capability over CCCH. For normal GPRS capable MS (without having EGPRS capability), the GPRS data transfer is successful without using EGPRS Packet Channel Required over CCCH.


• Test mobiles (EDGE-capable MS like Nokia 6230i and non-EDGE MS like Nokia 6310)


1. Enable GPRS/EGPRS in the BTS (see test plan for details).


3. Check the active alarms at the BSC with the MML command ZEOL. No unexpected alarms are present that indicate a hardware or software problem.


1 Power off an EDGE-capable MS (such as Nokia 6230i) and switch it on.

The P-CHANNEL REQUIRED message is seen on Abis Analyser with the Information Element EGPRS PCR with appropriate contents.


DN0749988 Issue 2-0 en 18/01/2008


117 (381)


The Routing Area Update procedure is successful, as the MS has latched on to the BCCH frequency.

2 Perform a FTP downlink transfer (get operation) with the MS.

The data transfer operation should be successful.

File received should be the same as the file at the server.

3 Repeat steps 1 and 2 with a non-EDGE MS (such as Nokia 6310).

Steps are the same as above but the EGPRS PCR Information Element is not visible.

2.4.7 Enhanced General Packet Radio Service (MCS 1-9)

Overview Enhanced Data rates for Global Evolution (EDGE) boosts GSM/GPRS network capacity and data rates to meet the demands of wireless multimedia applications and mass-market deployment. The Nokia EDGE solution includes Enhanced GPRS (EGPRS) for packet switched data.

EGPRS in general allows increased data rates by changing the modulation at the air interface from GMSK to 8-PSK. EGPRS also offers the following two software products for optimum data transfer.

• Incremental redundancy: enables the BTS to decode the packets retransmitted by MS with various puncturing schemes, each offering different level of redundancy (protection). This is needed in case network indicates loss for the earlier received packets from MS. In such cases, MS re-transmits the packets with different puncturing schemes and BTS combines each of those re-transmitted packets to decode the error-free packet that was initially transmitted.

• Link adaptation : In case the radio condition deteriorates, link adaptation allows the re-transmissions of packets with lower coding schemes than the commanded coding schemes that suit the present radio conditions thus maintaining the data transfer at acceptable rate. The changed coding scheme must belong to the same family as the earlier one.

Scope of testing The following functions verify the Flexi EDGE BTS to support EGPRS services



DN0749988Issue 2-0 en18/01/2008

• Data transfer with various coding schemes: MCS1 – MCS9 with EDGE capable mobile

• Incremental redundancy

• Link adaptation

Settings 1. Use the BSC MML default values of configuration parameters in

the site for packet data.

2. A single EDAP pool of size 4 PCM - TSL is configured to be shared between the BTS objects

Test cases

Pos Name Comment

1 PS data transfer with EDGE capable mobile in EGPRS segment

4 + 4, 2 Way, PCU2

2 PS data transfer on a single EDGE capable TRX with simultaneous CS calls

4 + 4, 2 Way, PCU2

3 Link adaptation in downlink in EGPRS segment

4 + 4, 2 Way, PCU2

4 Link adapation in uplink in EGPRS segment

4 + 4, 2 Way, PCU2

2.4.7.1 PS data transfer with EDGE-capable mobile in EGPRS segment

This test case verifies the PS data transfer for various coding schemes using EGPRS.



• SGSN, GGSN,HLR

• VLR (optional)


Hardware tools:

• Rel 4 and Rel 99 Mobiles

Test case execution


DN0749988 Issue 2-0 en 18/01/2008


119 (381)

Pre-setup:

The BTS and TRXs should be in supervisory state and no unexpected alarms should be seen on the Flexi EDGE BTS Manager or the BSC.


1 Observe the status of channels at BSC using the following command:



2 Attach 6 EDGE capable MSs (Rel4 and Rel99 mobiles) on different sectors.

MSs displays ‘G’ on the screen display. This is a confirmation for the successfully attached MS's with the network.

3 After the MSs have been successfully attached, activate the PDP context for them. This assigns IP address to the GPRS attached MS.

MSs displays (G) on the screen display. This is a confirmation that PDP context for the MSs have been created successfully.

4 After the successful establishment of PDP context, open FTP session with FTP server and initiate file download (ftp-get) for 5 MB file for 6 MSs simultaneously.

The data transfer for the selected coding scheme is successful .

There are no unexpected drops in the throughput figures and the data transfer rate is nearly constant.

5 After the successful ‘get’ operation, initiate ‘put’ for 5 MB file for 5 MS's simultaneously.

The data transfer for the selected coding scheme is successful.


6 Repeat step-4 and step-5 mentioned above 5 times.

Same as above.

2.4.7.2 PS data transfer on a single EDGE-capable TRX with simultaneous CS calls

This test case verifies that the PS data transfer on a single EDGE-capable TRX is successful when simultaneous CS calls are ongoing on the same TRX.



• SGSN, GGSN,HLR

• VLR (optional)




DN0749988Issue 2-0 en18/01/2008

Hardware tools:

• Rel 4 and Rel 99 Mobiles


The BTS and TRXs should be in supervisory state and no unexpected alarms should be seen on Flexi EDGE BTS manager or the BSC.


1 Observe the status of channels at BSC using the following command:


Status of the timeslots available for PS usage on GPRS enabled TRX is ‘GP’.

2 Attach 6 EDGE capable MSs (Rel4 and Rel 99 mobiles) on a sector with GPRS capable TRX.

MSs display ‘G’ on the screen. This is a confirmation for the successfully attached MSs with the network.

3 After the MSs have been successfully attached, activate the PDP context for them. This assigns IP address to the GPRS attached MS.

MSs display (G) on the screen. This is a confirmation that PDP context for the MSs have been created successfully.

4 After the successful establishment of PDP context, open an FTP session with FTP server and initiate file download (ftp-get) for 5 MB file for 6 MSs simultaneously.

The data transfer is initiated.


5 Establish a MS-MS CS call on EDGE TRX while data transfer is ongoing.

Observe data transfer that was initiated earlier.

CS call establishment is successful and the quality of speech is good and without any clips.

Data transfer continues with decreased throughput.

6 After the successful ‘get’ operation, initiate ‘put’ for 5 MB file for 6 MSs simultaneously.

The data transfer is completed successfully.


7 Observe the CS call. The CS call is ongoing and the speech quality is good.

2.4.7.3 Link adaptation in downlink in EGPRS segment

This test case verifies that the Link Adaptation functionality works correctly in case of varying radio conditions and the link is adapted to different coding schemes thereby providing optimal throughput data rates.

Test environment


DN0749988 Issue 2-0 en 18/01/2008


121 (381)

Network elements:


• SGSN, GGSN,HLR

• VLR (optional)


Hardware tools:




• The BTS and TRXs should be in supervisory state and no unexpected alarms should be seen on the Flexi EDGE BTS Manager or the BSC.

• An EDGE-capable MS is attached and the PDP context is activated.

• The Rx Level at the BTS and the MS is maintained at -70 dBm.


1 Initiate downlink data transfer with a mobile. Initiate ftp-get for 8MB sized file.

The data transfer is initiated successfully.


2 Introduce interference using Signal Generator in downlink direction.

(Vary the interference signal level from -100 dBm to -35dBm in steps of 5 dB each after every 10 seconds)

Observe the change in coding scheme in Abis Analyser traces and/or the test mobile.

Link adaptation successfully takes place and the change in coding scheme is seen.

Data transfer continues with some decreased throughput as the link adapts to bad radio conditions.

3 Now start reducing the interference in downlink direction.

(Vary the interference signal level from -35dBm to -100dBm in steps of 5 dB each after every 10 seconds)


Link adapts to the higher coding scheme as the interference decreases in the downlink.

Data transfer continues with some increased throughput as the link adapts to changing radio conditions.

4 Repeat the steps-2 and step-3 mentioned above 2-3 times while file download is on-going.

Data transfer continues and transfer rate is as expected.



DN0749988Issue 2-0 en18/01/2008

2.4.7.4 Link adaptation in uplink in EGPRS segment

This test case verifies that the Link Adaptation functionality works well in case of varying radio conditions and the link is adapted to different coding schemes thereby providing optimal throughput data rates.



• SGSN, GGSN,HLR

• MSC, VLR (optional elements)


Hardware tools:




• The BTS and TRXs should be in supervisory state without any unexpected alarms on the Flexi EDGE BTS Manager or the BSC.

• Attach the EDGE-capable MS and activate the PDP context of the MS.

• The Rx Level at the BTS and MS is maintained at -70 dBm.


1 Initiate uplink data transfer with a mobile. Initiate ftp-put for 8 MB sized file.

The data transfer is initiated successfully.


2 Introduce interference using Signal Generator in uplink direction.

(Vary the interference signal level from -35dBm to -100dBm in steps of 5 dB each after every 10 seconds).


Link adaptation successfully takes place and change in coding scheme is seen.

Data transfer continues with some decreased throughput as the link adapts to bad radio conditions.

Observe different puncturing schemes on Abis Analyser using which re-transmissions are done.

3 Now start reducing the interference in uplink Link adapts to the higher coding scheme as


DN0749988 Issue 2-0 en 18/01/2008


123 (381)

Step Input Expected output direction.

(Vary the interference signal level from -100dBm to -35dBm in steps of 5 dB each after every 10 seconds)


the interference decreases in the uplink.

Data transfer continues with some increased throughput as the link adapts to changing radio conditions.

4 Repeat the steps-2 and 3 mentioned above 2-3 times while upload is on-going.

Data transfer continues and transfer rate is as expected.

2.4.8 High Speed Circuit Switched Data (HSCSD)

Overview The High Speed Circuit Switched Data feature provides accelerated data rates for end-user applications. The current trend is for increased demand for high data rate applications like the World Wide Web (WWW), file transfer and facsimile.

Scope of testing The scope of testing is limited to testing

• HSCSD for data rates 9.6 kbps and 14.4 kbps. Asymmetric, asynchronous, non-transparent modes will be tested for both supported data rates.

• Resource upgrade/downgrade will be tested.

Change in the data transmission rate for HSCSD calls is covered in the Test Plan for Mode Modify Procedure.

Settings 1. To enable HSCSD

>>>ZWOC:10,47,FF;

2. To enable 14.4 kbit/s data services at the BSC >>>ZWOC:10,48,FF;

Test cases

Pos Name Comment

1 14.4 kbits/s Non-Transparent HSCSD Call 2+2+2

2 9.6 kbits/s Non-Transparent HSCSD Call 2+2+2

3 Resource Downgrade/Upgrade (3+1 to 1+1) of HSCSD Call

2+2+2



DN0749988Issue 2-0 en18/01/2008

2.4.8.1 14.4 kbits/s Non-Transparent HSCSD Call

The objective of the test case is to verify that Flexi EDGE BTS supports asymmetric, non-transparent HSCSD call for data rate 14.4 kbits/s.


None.


1 Set up a asynchronous, non-transparent data call with 28800 bps (14400 2+2) from the Dialup Application using the AT commands:

at+cbst = 80, 0, 1

at+chsn = 4, 2, 0, 8

Verify that the call is successfully established.

2 Initiate file transfer from the Dialup Application in both directions.

After the transfer of the file is complete check the file size at both the ends.

Verify that the file transfer is successfully initiated.

Verify that the file size is same at both the ends.


3 Repeat test steps 1 and 2 5 times. Verify that call is successfully established for each iteration.

Verify that data transfer takes place successfully.


2.4.8.2 9.6 kbits/s Non-Transparent HSCSD Call

The objective of the test case is to verify that Flexi EDGE BTS supports asymmetric, non-transparent HSCSD calls for the data rate 9.6 kbits/s.


• Dialup application


None.


DN0749988 Issue 2-0 en 18/01/2008


125 (381)


1 Set up a asynchronous,non-transparent data

call with 28800 bps (9600 3+1) from the Dialup Application using the AT commands

at+cbst = 80, 0, 1

at+chsn = 4, 3, 0, 4

Verify that the call is successfull established.

2 Initiate file transfer from the Dialup Application in both directions.

After the transfer of the file is complete check the file size at both the ends.

Verify that the file transfer is successfully initiated.

Verify that the file size is same at both the ends.

Verify that the desired throughput is met.

3 Repeat test steps 1 and 2 above 5 times. Verify that each iteration of the HSCSD call is successfully established.

Verify that file transfer is successful.

Verify that throughput is as required.

2.4.8.3 Resource Downgrade/Upgrade (3+1 to 1+1) of HSCSD Call

The objective of the test case is to verify that Flexi EDGE BTS supports the downgrade and upgrade of 14.4 kbps HSCSD calls (3+1 to 1+1) when the load control parameters are set at the BSC.


1. HSCSD enabled at the BSC.

2. Set the Load Control parameters at the BSC using the command ZEQX;


1 Establish a (3+1) 14.4 kbps Non-Transparent HSCSD call using the AT commands at the originating end.

at+cbst = 81, 0, 1

at+chsn = 5, 3, 0, 8

Type command 'ata' at the receiving end.

Verify that the calls get established successfully.

Note: 2 uni-directional secondary channels and 1 bi-directional primary channel are allocated for each leg of the HSCSD call.

2 Initiate data transfer in both directions between the two test mobiles.

Verify that user data is exchanged successfully.

3 Establish few speech calls on the sector such that resource downgrade of the ongoing HSCSD call is triggered by the BSC.

Verify that speech calls are established successfully.



DN0749988Issue 2-0 en18/01/2008


4 Observe resource downgrade at GSM Abis Analyser.

Verify that BSC releases both the secondary channels of one leg of the existing HSCSD call.

Verify that BSC sends 'Configuration Change Command' indicating that only the primary channel is now allocated for the HSCSD call.

Verify that the ongoing HSCSD call thus downgrades to (1+1).

5 Disconnect some of the speech calls setup in step 3 such that resource upgrade of the ongoing HSCSD call is triggered by the BSC.

Verify that speech calls are released successfully and the ongoing HSCSD call upgrades from (1+1) to (3+1).

2.5 Macrocellular

2.5.1 RX Antenna Diversity

Overview Receiver diversity (spatial diversity) can be enabled/disabled for a sector from the BSC. When diversity is enabled, two RF signals are demodulated separately and combined by the post detection weighted summing method.

Scope of testing The scope of the test plan is to test the functionality of combining the RF signals coming from two different paths. Verify the TRX Tests execution and results when diversity is enabled/disabled for the sector.

Settings RX Diversity can be changed for the BTS Object by the MML command >>>ZEQM:BTS=<bts_id>:RDIV=<Y/N>;

Test cases

Pos Name Comment

1 RX Level Measurements when Diversity is enabled at startup

4 + 4, 2-way, RF Hopping


6 + 6, RTC, BB Hopping


DN0749988 Issue 2-0 en 18/01/2008


127 (381)

Pos Name Comment


4 + 4, 2-way, RF + Antenna Hopping

4 RX Level Measurements when Diversity is disabled at startup.


5 RX Level Measurements when Diversity is disabled at startup.

6 + 6, RTC, BB Hopping

6 TRX Test Reports with RX diversity enabled or disabled


TRX Test Reports with RX diversity enabled or disabled

6 + 6, RTC, Non Hopping

2.5.1.1 RX Level Measurements when Diversity is enabled at startup

The purpose of this test case is to verify consistent RX level is reported corresponding to better of the two paths when diversity is operational.




• Variable attenuators are placed on both the antenna ports of ERxx DDU module or ECxx RTC module of Sector1.

• Flexi EDGE BTS Manager is connected to the BTS.

• Site is started up with Diversity enabled for all the sectors in the configuration.

• There are no active alarms reported to BSC.

• Disable uplink DTX for the all the sectors.


1 Place CS calls in Sector1. Check calls are successful.

2 Verify the speech quality. Speech is clear without any disturbance.

3 Observe the Measurement Report using GSM Abis Analyser.

Note the reported uplink RX level in the measurement report.



DN0749988Issue 2-0 en18/01/2008


4 Using the variable attenuator, introduce attenuation to path B and keep path A unattenuated.

Observe the uplink RX level in the measurement report.

The uplink RX level is same as observed in step 3.

5 Repeatedly change attenuation on path B (keeping path A unattenuated) and observe the measurement for 15 minutes.

Consistent uplink RX level is reported which matches the values observed in step 3..

Calls remain established.

6 Repeat steps 4-5 by changing the attenuation on path A and keeping path B unattenuated.

Same as in steps 4-5.

2.5.1.2 RX Level Measurements when Diversity is disabled at startup

The purpose of this test case is to verify that when diversity is disabled, the BTS takes the uplink RF signal from the main RX path only.



Test case execution The RX1 Main port of the EXxx TRX Module is connected to the receive port corresponding to path A of the ERxx DDU module or ECxx RTC module.

The RX2 Main port of the EXxx TRX Module is connected to the receive port corresponding to path B of the ERxx DDU module or ECxx RTC module.

Pre-setup:

• Variable attenuators are placed on both the antenna ports of ERxx DDU module or ECxx RTC module of Sector1.


• Site is started up with Diversity disabled for all the sectors in the configuration.

• There are no active alarms reported to BSC.

• Disable uplink DTX for the all the sectors


1 Place CS calls in sector 1. Check calls are successful.

2 Verify the speech quality. Speech is clear without any disturbance.


DN0749988 Issue 2-0 en 18/01/2008


129 (381)


3 Observe the Measurement Report using GSM Abis Analyser.

Note the reported uplink RX level in the measurement report.

-

4 Using the variable attenuator, introduce attenuation to path A and keep path B unattenuated.

Observe the uplink RX level in the measurement report.

The uplink RX level for first logical TRX object in the EXxx TRX module, dips compared to the one observed in step 3.

The uplink RX level for second logical TRX object in the EXxx TRX module, remains the same as in step 3.

5 Repeatedly change attenuation on path A (keeping path B unattenuated) and observe the measurement for 15 minutes.

The uplink RX level for first logical TRX object changes with the corresponding change in attenuation.

The uplink RX level for second logical TRX object remains the same as in step 3.

6 Repeatedly change attenuation on path B (keeping path A unattenuated) and observe the measurement for 15 minutes.

The uplink RX level for second logical TRX object changes with the corresponding change in attenuation.

The uplink RX level for first logical TRX object remains the same as in step 3.

2.5.1.3 TRX Test Reports with Rx Diversity enabled or disabled

The objective of the test case is to verify BTS reports in the TRX Tests reports

• BER and RX Sensitivity for both branches when the Rx diversity is enabled for the sector

• BER and RX Sensitivity not measured for the diversity branch and measured values for the main branch when diversity is disabled for the sector.


• The attenuation at the BSC is set to default (PMAX=0).

• Rx diversity is enabled in the BSC for sector1 and disabled for sector2.


1 Start the TRX Test Command for the first TRX of sector 1 from the BSC with MML command ‘ZUBS’.

The BSC MML command window displays: ‘TRANSCEIVER TEST STARTED



DN0749988Issue 2-0 en18/01/2008


The test parameters(mandatory) to be specified in the command are:

BTS Num/Name:

TRX Num: '1'

Observe the execution output of the MML command at BSC.


2 Display the TRX Test Report for TRX 1 on the BSC using MML command ‘ZUBP’.

The parameters to be specified in the MML command are:

Test type: Specify ‘TR’ for Transreceiver Test Report

BCF/BTS/TRX Num

TRX Test for TRX 1 is successful and its report is displayed at the BSC with the following contents: BCF/BTS/TRX/RTSL Number

Test Result: Passed

Transmitted Power Level: 47 dBm

BER for main branch:0% (RF BER)

Rx Sensitivity for main branch: < -110 dBm.

BER for Diversity Rx branch: 0% (RF BER)

Rx Sensitivity for Diversity branch: < - 110 dBm

3 Start the TRX Test Command for the first TRX of sector 2 from the BSC with MML command ‘ZUBS’.

The test parameters(mandatory) to be specified in the command are:

BTS Num/Name:

TRX Num: Id of first TRX in sector2.

Observe the execution output of the MML command at the BSC.

The BSC MML command window displays: ‘TRANSCEIVER TEST STARTED


4 Display the TRX Test Report for the first TRX object of sector 2 on the BSC using MML command ‘ZUBP’.

The parameters to be specified in the MML command are:

Test type: Specify ‘TR’ for Transreceiver Test Report

BCF/BTS/TRX Num

TRX Test for first TRX of sector 2 is successful and its report is displayed at the BSC with the following contents: BCF/BTS/TRX/RTSL Number

Test Result: Passed

Transmitted Power Level: 47 dBm

BER for main branch::0% (RF BER)

Rx Sensitivity for main branch: < -110 dBm.

BER for Diversity Rx branch: 4294967295(=Not Measured).

Rx Sensitivity for Diversity branch: 254 (=Cannot be measured).


DN0749988 Issue 2-0 en 18/01/2008


131 (381)

2.5.2 Multi BCF Control

Overview The Multi BCF Control feature allows the BCF level synchronisation of co-located BTS sites. With BCF synchronisation it enables the use of Common BCCH feature to form Segments of BTS objects across BTS sites. Multi BCF site expansion from UltraSite EDGE BTS to Flexi EDGE BTS, or just Flexi EDGE BTS, with up to a maximum of 9 BTS sites in chain.

Scope of testing The scope of the test cases covers the seamless inter and intra cell handovers, placement of call in all the sectors irrespective of BCCH BTS position in chain, successful administrative operations without impact on service of other objects, recovery of master/slave in the configuration and site start-up.

Configuration All the BTSs in the multi BCF configuration are of type Flexi EDGE unless explicitly mentioned as UltraSite.

6 frequencies are defined in the MA list. The same MA list with different MAIO values is configured for all BTS objects.

Settings At BSC Master/slave configuration defined.

Additional Information For Site synchronisation (clock source of the master clock BCF is BCF), the command is: ZEFM:<master_clock_bcf_id>:CS=BCF,ADD=<bcf_id1>&<bcf_id2>:;

To enable the synchronisation of the chain. ZEFM:<master_clock_bcf_id>:SENA=T:;

Test cases

Pos Name Comment

1 Slave BCF Recovery after reset when clock is missing

/ BCF1: 2+2, BCF2: 2+2, BCF3: 2+2, RF hopping

2 Slave clock recovery after Sync Cable re-connection

/ BCF1: 2+2, BCF2: 2+2, BCF3: 2+2, RF hopping

3 BCF Recovery after Master BCF reset / BCF1: 2+2, BCF2: 2+2, BCF3: 2+2, RF hopping

4 BCF Recovery after Master BCF reset / BCF1: 2+2 UltraSite, BCF2: 2+2, BCF3: 2+2, RF hopping



DN0749988Issue 2-0 en18/01/2008

2.5.2.1 Slave BCF Recovery after reset when clock is missing

The objective of the test case is to verify that with Multi BCF configuration slave BCFs can recover from the reset after the clock is made available later.


• Multi BCF is configured such that BCF1 is chain master, BCF 2 & 3 are 1st and 2nd slave in chain.

• TRX test is successful on all the timeslots

• BCF and all the TRXs are operational without any major/minor alarm.

• Adjacent BTS objects are defined as neighbours.


1 Independent calls are placed on all the BCFs using mobiles.

Observe the voice quality.



2 Disconnect the clock chain cable between master and 1st slave BCF.

Observe the ongoing calls.

Within 20 seconds, 7602 alarm 'BSS synchronisation failed' is raised for both slave BCFs.

All calls are ongoing (calls from slave BCFs are handed over, as directed by BSC).

3 Reset the 1st slave in the chain from the BSC.

Alarms are observed at BSC and Flexi EDGE BTS Manager.

After the reset, alarm 7602 is cancelled and 7600 alarm 'BSS synchronisation failed' is raised for 1st slave.

4 Re-connect the clock chain cable between master and 1st slave BCF.

Observe the alarms and BCF state BSC and Flexi EDGE BTS Manager.

Both the slave BCFs reset.

7600 alarm for 1st slave and 7602 alarm for 2nd slave raised above are cancelled.

All the BCFs are in operational state.

5 New calls are placed on both slave BCFs All calls are successful. Voice quality is good.

6 Disconnect the clock chain cable between the 1st and the 2nd slave BCF.

Observe the ongoing calls.

Within 20 seconds, 7602 alarm 'BSS synchronisation failed' is raised for the 2nd slave BCF.

All calls are ongoing (calls from 2nd slave BCF are handed over, as directed by BSC).

7 Reset the 2nd slave BCF from the BSC. After the reset, alarm 7602 is cancelled and 7600 alarm 'BSS synchronisation failed' is


DN0749988 Issue 2-0 en 18/01/2008


133 (381)



Test mobiles are monitored.

raised for 2nd slave BCF.

No alarm is reported for master and 1st slave BCFs.

All calls (on other BCFs) are ongoing.

8 Re-connect the clock chain cable between 1st and 2nd slave BCF.

Observe the alarms and BCF state BSC and Flexi EDGE BTS Manager.

The 2nd slave BCF is reset.

7600 alarm is cancelled.

All the BCFs are in operational state.

9 Place calls on the all the TRXs of all BCFs, on same timeslot and hold for 5 minutes.

Observe the voice quality.

All calls are successful and stable.


2.5.2.2 Slave clock recovery after sync cable re-connection

The objective of the test case is to verify the recovery of the clock after the clock sync cable has been removed and re-connected after that.


• Multi BCF is configured such that BCF1 is chain master, BCF 2 & 3 are 1st and 2nd slave in chain.

• TRX test is successful on all the timeslots

• BCF and all the TRXs are operational without any major/minor alarm.

• Neighbours are defined for all BTSs such that neighbours are available throughout the test.


1 Place independent calls on the all the BCFs. Monitor the calls on mobiles.

All calls are successful. Voice quality is good.

2 Remove the clock sync cable between Master and first slave BCF.

Monitor the calls.

Within 20 seconds, 7602 alarm 'BSS synchronisation failed' is raised for both slave BCFs.

All calls are ongoing (calls from slaves are handed over), as directed by BSC.

3 State of all TRXs is observed at BSC. All the TRXs in master BCF are in operational state.

TRXs in slave BCFs are in BL-BCF state.



DN0749988Issue 2-0 en18/01/2008


4 Using 'ZEFL' command at the BSC, check the synchronisation state of slave BCFs.

Both the slave BCFs are in unsynchronised mode.

5 Connect the clock sync cable between Master and first slave BCF.

All calls are observed.

Both the 7602 alarms are cancelled and the slave BCFs are reset.

The calls on master BCFs remain unaffected.

6 From BSC observe the synchronisation state of both slave BCFs.

Both the slave BCFs are in synchronised mode.

7 Place calls on all the TRXs for all the BCFs, on same timeslot. Monitor the calls for at least 5 minutes.

All calls are successful. Voice quality is good.

All calls are stable.

2.5.2.3 BCF Recovery after Master BCF Reset

The objective of the test case is to verify that with Multi BCF configuration BCFs can recover from a master BCF reset.


1. Multi BCF is configured so that BCF1 is chain master, BCF 2 and 3 are the 1st and 2nd slaves in the chain.


3. BCF and all the TRXs are operational without any major/minor alarms.

4. All the BTS objects of all BCFs that are part of the sync chain have another BTS site defined as neighbour.


1 Independent calls are placed on all the BCFs using test mobiles.


2 Reset the master BCF from BSC.


Continue to observe the state of the BCFs at Flexi EDGE BTS Manager.

In case master BCF is UltraSite, alarm 7602 'BSS synchronisation failed' is raised for all slave BCFs.

In case master BCF is Flexi EDGE no alarm is observed.

After master BCF becomes operational after reset, both slave BCFs are reset by BSC.

3 Observe the calls. All calls from both slave BCFs are handed over, as directed by BSC.


DN0749988 Issue 2-0 en 18/01/2008


135 (381)


All calls from master BCF are released.

4 From Flexi EDGE BTS Manager observe the clock state of all BCFs.

The first BCF in the chain is the master and the remaining BCFs are in slave mode.

5 Place calls on the all the TRXs of all the BCFs on the same timeslot.

Monitor the calls for at least 5 minutes. Observe the voice quality.

All the calls are successful, as seen on test mobiles.

All the calls are stable. The voice quality is good.

2.5.3 Common BCCH and Dual/Tri-band Operations

Overview Dual Band GSM Network Operation provides the means to manage the traffic between the GSM 900 and GSM 1800 and between GSM 1900 and GSM 800 in a single sector (Segment). The BTS objects used in segment may under same BCF object, or different BCF. In case of different BCF then BCF must be in frame number synchronization and can be same or different Nokia BTS generations.

The main advantages of the common BCCH functionality are:

• Use of signalling channels is optimised by sharing them between bands

• Tighter reuse of all carriers in the non-BCCH bands

Scope of testing The scope of the test cases covers the inter and intra band handovers on having common BCCH, successful administrative operations without impact on service of other objects, TRX tests and BCCH reconfiguration. Segment formed on single or across multiple BCF site generations

Test cases

Pos Name Comment

1 Configuration of Common BCCH 6 (900)+6 (1800) RTC, BB hopping, BCCH in 900

2 Configuration of Common BCCH MultiBCF: UltraSite 2+2, Flexi EDGE 2+2, BCCH on UltraSite

3 TRX Test on Common BCCH configuration

4(900)+ 4(1800), RF Hopping, BCCH on 900

4 BCCH reconfiguration and O&M Operation in Common BCCH

4 (800) + 4 (1900), RF Hopping in both, BCCH on 1900



DN0749988Issue 2-0 en18/01/2008

2.5.3.1 Configuration of Common BCCH

The objective of the test case is to verify that common BCCH can be applied and used successfully at the BTS.


• Multiband test mobiles



• All the BTSs have the BCCH TRX configured, that is, the Common BCCH is not in use.


DN0749988 Issue 2-0 en 18/01/2008


137 (381)


1 All the BTS sectors are locked from BSC. All the BTSs are in BL-USR state.

2 Change the BCCH TRX to non BCCH TRX in all BTS objects to be made TCH BTS.

Segment id of all BTSs is made common. All the BTSs are unlocked.

Observe the BTS state at BSC.

After unlock, all the TRXs under the all the BTSs come to operational state.

Only one BCCH TRX is available in common BCCH configuration.

3 Using spectrum analyser, observe the transmission of all carriers in the BCF.

Only BCCH carrier is continuously transmitted.

No transmission is observed on non-BCCH carriers.

4 Using test mobiles, calls are placed on all the TRXs. Monitor the calls for 5 minutes.


5 Release all the calls from mobiles. All calls are successfully released.

6 Upload and save the Site Information Report in xml format from all sites using Flexi EDGE BTS Manager.

Check the contents of saved xml file.

The Site Information Report can be uploaded and saved in xml format.

The configuration and parameters for the TCH only BTS objects are all correct.

7 Lock all the BTSs.

All the BTSs are assigned the original segment id.

Change BTS object's configuration to have BCCH TRX for all BTS objects.

All the BTSs are unlocked.

Observe the BCF state at BSC and Flexi EDGE BTS Manager.

All the TRXs come to operational state after unlock.

Each BTS and all its TRXs are operational.

8 Using test mobiles place calls on all the BTS sectors.


2.5.3.2 TRX Test on Common BCCH Configuration

The objective of the test case is to verify that TRX test can be successfully run from Flexi EDGE BTS Manager and from BSC with Common BCCH configuration.



Test case execution



DN0749988Issue 2-0 en18/01/2008

Pre-setup:

• The BCF and all the TRXs are operational without any major/minor alarm.

• All the sectors are defined in a common segment.

• At the BSC, PMAX is set to 0.

• At the BSC, default TRX test parameters are used.


1 Start TRX test on BCCH TRX from BSC with GMSK modulation using 'ZUBS' command at the BSC.

Observe the test results at the BSC using 'ZUBP' command.

The TRX test is successful.

The test result is 'PASSED'. Different parameters shown in report are verified

Transmitted power level: >=47dBm

Main branch BER : 0

Main branch Rx sensitivity: better than -110dBm

Diversity branch BER : 0

Diversity branch Rx sensitivity: better than -110dBm

2 Start TRX test on TCH TRX in TCH BTS from BSC with 8-PSK modulation using 'ZUBS' command at the BSC.

Monitor the transmitted power transmitted during the test, using spectrum analyser.

Observe the test results at BSC using 'ZUBP' command.

The TRX test is successful.

The transmitted power is equal to BCCH power level.

The test result is 'PASSED'. Different parameters shown in report are verified

Transmitted power level: >=47dBm

Main branch BER : 0

Main branch Rx sensitivity: better than -110dBm

Diversity branch BER : 0

Diversity branch Rx sensitivity: better than -110dBm

3 Start TRX test on TCH TRX in TCH BTS from the Flexi EDGE BTS Manager using 8-PSK modulation.

Monitor the transmitted power using spectrum analyser.

Observe the test results at Flexi EDGE BTS Manager.

The TRX test is successful with following test report parameters.

The transmitted power is equal to BCCH power level

Test Result: PASS

Tx Power: >=47 dBm

Main Rx BER: 0 (RF BER)

Main Rx Sensitivity: better than -110dBm


DN0749988 Issue 2-0 en 18/01/2008


139 (381)


Diversity Rx BER: 0% (RF BER)

Diversity Rx Sensitivity: better than -110dBm.

2.5.3.3 BCCH Reconfiguration and O&M Operation in Common BCCH

The objective of the test case is to verify that the administrative operations on the TCH TRXs on non-BCCH BTS in common BCCH configuration are performed successfully.


• Triband test mobiles


• Common BCCH is configured using all the BTS objects.¨




1 Lock the TCH BTS object.

Unlock the TCH BTS object.

Observe the BTS state at the BSC and Flexi EDGE BTS Manager.

The BTS is successfully locked and all the TRXs are in BL-USR state.

The BTS is reset and comes to operational state after unlock operation.

2 Block the BCCH TRX from the Flexi EDGE BTS Manager.

Observe the BCCH TRX state at the BSC.

The TRX with blocked state at Flexi EDGE BTS Manager is in BL-TRX state at BSC.

Another TRX is configured as BCCH TRX.

3 Place calls on all TRXs using test mobiles on all BTS objects.


4 Unblock the TRX blocked in step 2, from the Flexi EDGE BTS Manager.

Observe the TRX state at the BSC.

The TRX comes to operational state.

5 Block the TCH BTS from the Flexi EDGE BTS Manager.

Observe the BTS state at the BSC and Flexi EDGE BTS Manager.

Observe the mobiles for ongoing calls.

The BTS is successfully blocked. All its TRXs are in BL-BTS state at the BSC.

Calls are not dropped. Calls from the blocked BTS are handed over to operational TRXs as directed by BSC.



DN0749988Issue 2-0 en18/01/2008


Check the RF transmission form TCH BTS. All RF transmission will stop within 60 seconds from block command given.

6 Unblock the blocked BTS from the Flexi EDGE BTS Manager.

Observe the BTS state and alarms.

Observe the mobiles for ongoing calls.

The TRX is unblocked and comes to operational state as seen at BSC and Flexi EDGE BTS Manager.

BTS is in operational state. No alarm is reported.

Calls on BCCH BTS are still ongoing.

2.5.4 Mast Head Pre-Amplifier

Overview A Mast Head Preamplifier (MHA) is used to compensate losses at the BTS receiver antenna cable. Depending on the actual network uplink/downlink balance this feature allows an MS to use lower transmitting power and thus increases the MS battery lifetime or simply increases the size of the cell. The Nokia MHA provides gain in the range up to 12 dB. The BTS provides electrical power for the MHA up to 150 mA at 11.5 V. DC power is provided on the centre pin of the antenna port, positive with respect to ground.

The MHA has a RF bypass relay, which can be used for two purposes. First, for the duration of the antenna VSWR measurement, it is necessary to bypass the MHA for correct result. Secondly, if a malfunction is detected in the MHA, it can be bypassed with this relay.

Scope of testing The scope of the test cases covers the BCF operation with MHA, appropriate alarm reporting, cancellation of alarms connected to DDU and RTC combiners.

Test cases

Pos Name Comment

1 Alarm reporting for MHA with bypass in DDU configuration

4+4

2 Alarm reporting for MHA with bypass in RTC configuration

6+6 RTC

3 Alarm reporting for MHA without bypass in DDU configuration

4+4

4 Alarm reporting for MHA without bypass in 6+6 RTC


DN0749988 Issue 2-0 en 18/01/2008


141 (381)

Pos Name Comment RTC configuration

2.5.4.1 Alarm reporting for MHA with bypass in DDU configuration

The objective of the test case is to verify the successful operation of a BCF when MHA is in use. The alarm reporting and cancellation is also verified.


• The MHAs are configured with bypass capability.



• At the BSC, PMAX is set as 2.

• Rx diversity is enabled.


1 Place calls on all the TRXs of all BTS objects, using mobiles.


2 Simulate low current condition for 1st MHA of 1st BTS object.

Alarms are monitored at the BSC and Flexi EDGE BTS Manager.

Observe the calls.

All TRXs (Note1) connected with this MHA have 7607 alarm ‘Current used by MHA is out of range for ERxx DDU module (antenna A bypassed)’.

Note1: For one of the TRX the alarm is 7604 reported instead of 7607.

No alarm is observed for 2nd BTS.

All calls are ongoing.

3 Remove the fault condition from 1st antenna and observe the setup for 5 minutes.

The alarms raised above are not cancelled during the observation period.

4 Lock/Unlock the 1st BTS.

Alarms are monitored.

Observe the calls.

Alarms 7607/7604 raised in step 1 are cancelled.

Calls from 1st BTS are released. Calls on 2nd BTS are ongoing.

5 Simulate too high current condition for 1st MHA from 2nd BTS.

Alarms are monitored at BSC and Flexi EDGE BTS Manager.

All TRXs (Note1) connected with this MHA have 7607 alarm ‘Current used by MHA is out of range for ERxx DDU module (antenna A bypassed)’.




DN0749988Issue 2-0 en18/01/2008


No alarm is observed for 1st BTS.

6 Monitor the BTS operational state at BSC and Flexi EDGE BTS Manager.

Observe the calls.

All the TRXs are in operational state.

Calls on 2nd BTS are ongoing as seen on test mobiles.

7 Lock and unlock 2nd BTS from BSC.


Observe the calls.

7607 alarms raised in step 5 are cancelled and reappear when the BTS is operational after reset.

Calls are released.

8 Remove the fault condition from the antenna and observe the setup for 5 minutes.


Alarms are not cancelled automatically during the observation period.



All alarms are cancelled. No active alarm is observed.

10 Place calls on all the TRXs using mobiles. Monitor the calls for 5 minutes.


2.5.4.2 Alarm reporting for MHA with bypass in RTC configuration

The objective of the test case is to verify the successful operation of a BCF when MHA is used with bypass capability with RTC combining. The alarm reporting and cancellation is also verified.


• The MHAs are configured with bypass capability.



• At the BSC, PMAX is configured as 2.



1 Place calls on all TRXs using mobiles. All calls are successful.

2 Simulate low current condition for MHA on 1st antenna of ECxA from 1st BTS.

Monitor the alarms at the BSC and Flexi EDGE BTS Manager.

Within 30 seconds, all TRXs (Note1) connected to the antenna have 7607 alarm ‘Current used by MHA is out of range for ECxx RTC module (antenna A bypassed)’.


DN0749988 Issue 2-0 en 18/01/2008


143 (381)



No alarm is observed for the 2nd BTS.

3 Remove the fault condition from 1st antenna and observe the setup for 5 minutes.

Observe the calls.

The alarms raised above are not cancelled during the observation period.

All calls are ongoing.

4 Lock/unlock the 1st BTS.


Observe the calls.

Alarms 7607 and 7604 raised in above step are cancelled.

Calls from 1st BTS are released. Calls on 2nd BTS are ongoing.

5 Simulate too high current condition for MHA on 1st antenna of RTC from 2nd BTS.

Monitor the alarms at the BSC and Flexi EDGE BTS Manager.

Within 30 seconds, all TRXs (Note1) connected to the antenna have 7607 alarm ‘Current used by MHA is out of range for ECxx RTC module (antenna A bypassed)’.


No alarm is observed for 1st BTS.

6 Monitor the BTS operational state at BSC and Flexi EDGE BTS Manager.

Observe the calls.

All TRXs in both the BTSs are in operational state.

Calls on 2nd BTS are ongoing.



Observe the calls.

7607 and 7604 alarms raised in step 5 are cancelled after reset but reappear within 30 seconds.

Calls are released.

8 Remove the fault condition from the antenna and observe the setup for 5 minutes.


Alarms are not cancelled automatically during the observation period.



All alarms are cancelled. No active alarm is observed.

10 Place calls on all TRXs. Monitor the calls for 5 minutes.


2.5.4.3 Alarm reporting for MHA without bypass in DDU configuration

The objective of the test case is to verify the successful operation of a BCF when MHA is used without bypass capability. The alarm reporting and cancellation is also verified.



DN0749988Issue 2-0 en18/01/2008


• The MHAs are configured without bypass capability.






1 Place calls on all the TRXs using mobiles. All calls are successful.

2 Simulate low current condition for MHA on antenna A.

Monitor alarms at BSC and Flexi EDGE BTS Manager.

All TRXs connected with ERxA with this MHA, have 7607 alarm ‘TRX operation degraded: ERxx DDU module has detected that MHA on its antenna A is broken’. For one TRX 7604 alarm is reported.


3 Simulate high current condition for MHA on antenna B.

Monitor alarms at BSC and Flexi EDGE BTS Manager.

Alarm 7607 raised in above step are cancelled. All TRXs connected with ERxA with this MHA have 7606 alarm ‘TRX faulty:ERxx DDU module has detected that MHA on its antenna B is broken’. For one TRX 7603 alarm is reported.


4 Lock and unlock the BTS from the BSC.

Monitor the alarms.

All 7606/7603 alarms are cancelled after reset but reappear within 10 seconds.

5 Remove fault condition from MHA on antennas A and B.

Monitor the alarms for 5 minutes.

The alarms are not cancelled automatically.


Monitor the alarms.

After the BTS reset, all the BTS alarms are cancelled.

7 Place calls on the BTS. Observe the calls on test mobiles.

New calls are successful. No alarm is observed for other BTSs.

All the calls on the second BTS are ongoing.


DN0749988 Issue 2-0 en 18/01/2008


145 (381)

2.5.4.4 Alarm reporting for MHA without bypass in RTC configuration

The objective of the test case is to verify the successful operation of a BCF when MHA without bypass capability is connected with RTC combining. The alarm reporting and cancellation is also verified.


• The MHAs are configured without bypass capability.





Step

Input Expected output

1 Place calls on all the TRXs using mobiles. All calls are successful.

2 Simulate low current condition for MHA on antenna A.

Monitor alarms at the BSC and Flexi EDGE BTS Manager.

All TRXs connected with ECxA have this MHA, have 7607 alarm "TRX operation degraded: ECxx RTC module has detected that MHA on ANT A is broken’. For one TRX 7604 alarm is reported.


3 Simulate high current condition for MHA on antenna B.

Monitor alarms at the BSC and Flexi EDGE BTS Manager.

Alarm 7607 raised in above step are cancelled. All TRXs connected with ECxA with this MHA have 7606 alarm ‘TRX faulty:ECxx RTC module has detected that MHA on ANT B is broken’. For one TRX 7603 alarm is reported.

No alarm is observed for the 2nd BTS.



Alarms 7606 and 7603 are cancelled after reset but reappear within 30 seconds.

5 Remove fault condition from MHA on antenna B.


Alarms are not cancelled automatically.

6 Lock and unlock 1st BTS from the BSC.

Monitor the alarms.

After BTS reset, all 1st BTS alarms are cancelled.

7 Place calls on 1st BTS. Observe the calls on test mobiles.

No alarm is observed for 2nd BTS. New calls are successful.

All calls on 2nd BTS are ongoing.



DN0749988Issue 2-0 en18/01/2008

2.6 Microcellular

2.6.1 MS Speed Detection

Overview MS Speed Detection is used to determine the speed of the mobile during speech calls and reports the value to the BSC via the Measurement Result message. The BSC using an averaging procedure determines if the mobile is moving fast (MS Speed Class 2) or slower (MS Speed Class 1). The moving speed is an input to handover algorithm: fast moving mobiles can be directed to macrocells and the slower mobiles respectively to microcells, thus decreasing the number of handovers in microcells.

Scope of testing The scope of testing is to check for MS speed reporting to BSC by BTS and to check that the relevant MS Speed Class counters are updated.

Test cases

Pos Name Comment

1 MS Speed Detection AMR FR, 800 Band, ULDTX and DLDTX off, No Hopping

2 MS Speed Detection AMR HR, 1900 Band, ULDTX and DLDTX off, No Hopping

3 MS Speed Detection EFR, 1800 Band, ULDTX and DLDTX off, No Hopping

4 MS Speed with Synthesised frequency hopping

-AMR FR, RF Hopping

2.6.1.1 MS Speed Detection

Description The objective of the test case is to verify that BSC counters are updated accordingly when MS speed is varied within the range of that counter without call getting disconnected.




DN0749988 Issue 2-0 en 18/01/2008


147 (381)

Test case execution Pre-setup

The MS Speed Detection Measurement counters are enabled in the BSC.


1 Fetch the counter values for the following BSC counters for the BTS object.

1. SAMPLES IN SPEED CLASS 1 : 058001



4. TOTAL NR OF INDICATIONS : 058006

All the values are fetched successfully.

2 Establish 2 CS speech calls on BTS A (codec set used as per test case comment) and listen to the voice for 1 minute.



3 Using the RF fading simulator, continuously change (Increase / decrease) the simulated mobile speed.

Vary the mobile speed from 0 km/h to 15 km/h and from 15 km/h to 0 km/h. change the speed of mobile in steps of 2km/h, for each value keep mobile stable for 1 minute.

Repeat this for duration so that one complete set of valid BSC counter values are attained with a minimum duration of 1 hour.

Voice quality is good throughout without disturbances or cracking sound.

4 Fetch the counter values for the following BSC counters for the BTS object.




4. TOTAL NR OF INDICATIONS : 058006

Verify that predominantly (target value is >80%) of reported indications are in MS Speed class 1.

(SAMPLES IN SPEED CLASS 1 : 058001 / TOTAL NR OF INDICATIONS : 058006).

5 Repeat steps 3 to 5 for

• Speed varying between 21km/h to 60km/h

• Speed varying between 60km/h to 100km/h

Same results for steps 3 and 4 are observed.

For speed varying between 21km/h to 60km/h and between 60km/h to 100km/h verify that minority (target value is <20%) of reported indications are in MS Speed class 1

(SAMPLES IN SPEED CLASS 1 : 058001 / TOTAL NR OF INDICATIONS : 058006)

6 Release both the calls initiated in step 2. Both calls are successfully released.



DN0749988Issue 2-0 en18/01/2008

2.6.1.2 MS Speed with Synthesised frequency hopping

The objective of the test case is to verify that MS speed is reported as invalid for ongoing calls on non-BCCH TRX in RF hopping sector, but is reported for ongoing calls on BCCH TRX.


• Fading Simulator


None.


1 Establish 2 CS speech calls on BTS A on a non-BCCH TRX (codec set used as per test case comment) and listen to the voice for 1 minute.



2 Using Abis analyser observe indicated MS speed in Supplementary Measurement Information field of MEAS.RES message.

MS speed is reported as invalid.

3 Release calls established in step 1.

Establish 2 CS speech calls on BTS A on BCCH TRX (codec set used as per test case comment) and listen to the voice for 1 minute.



4 Using the fading simulator, continuously change (increase/decrease) the mobile speed

Vary MS speed from 0 km/h to 104 km/h and then from 104 km/h to 0km/h for a period of 10 minutes.

Have "speech" and "no-speech" in the uplink at regular periods, so that uplink DTX is applied by the mobile and removed at varying intervals.

Using Abis analyser, observe the indicated MS speed in Supplementary Measurement Information field of MEAS.RES message.

Also the voice quality is good without disturbances or cracking sound during the handover.

The mobile speed is reported as invalid for MS speed whenever UL DTX is applied, otherwise a value is reported for the simulated speed.


DN0749988 Issue 2-0 en 18/01/2008


149 (381)

2.7 Operability

2.7.1 Transmission Control: Alarm Handling via LAPD

Overview BTS transmission alarms are reported to BSC and Flexi EDGE BTS Manager as 8000 series (8000 to 8999) BTS Alarms.

Scope of testing The scope of testing is to generate transmission alarm and verify the same in the alarm list of BSC and Flexi EDGE BTS Manager.

Configuration

Item Details

Synchronisation priority Priority 1 Interface 1

Priority 2 Internal Timing Test cases

Pos Name Comment

1 Transmission Alarm via LAPD 2+2+2, EIPA E1

2 Ext-Q1 device Alarms via LAPD 2+2+2, FIFA, E1 Line

2.7.1.1 Transmission Alarm via LAPD

This test case verifies that the BTS transmission alarms start/cancel are reported to the BSC on OMUSIG as 8000 series alarms.


Two ET lines are required to perform this test case. While commissioning the BTS transmission, select two interfaces (interface 1 and 2) are in use. Allocate OMUSIG on interface 1 and TRXSIGs and TCHs on interface 2. Other configuration is as per test plan.

Pre-setup:

1. Flexi EDGE BTS Manager is connected to the BTS site via local connection.



DN0749988Issue 2-0 en18/01/2008


1 Establish MS-MS calls Calls are successfully established

2 Remove interface 2 and check the alarms on BSC using MML (ZEOL:<bcf_no>;) command. Also verify the Supplementary information fields.

8050 "LOSS OF INCOMING 2M SIGNAL" is present in the alarm list.

Q1 address of the of transmission equipment is 4080.

The functional entity number is 0.

The supervision block number (Interface ID) is 2.

3 Check the timestamp of the alarm. The timestamp is correct.

4 Observe the call. The call is released.

5 Remove interface 1 and then re-connect interface 1. Check the alarms on BSC using MML (ZEOL:<bcf_no>;) command. Also verify the Supplementary information fields in the alarms.

Fault condition for interface 2 is still active in BSC alarm list and time stamp of the active alarm is not changed.



6 Execute BCF Object Reset from BSC using MML command (ZEFR:<bcf_no>;).

When BCF reaches in WO state, check the alarms on BSC using MML (ZEOL:<bcf_no>;) command. Also verify the Supplementary information fields and timestamps in the alarms.

8050 "LOSS OF INCOMING 2M SIGNAL" is present in the alarm list.

Q1 address of the transmission equipment is 4080.


The supervision block number is 2.

7 Compare the timestamp of the reported alarm. The timestamp is same.

2.7.1.2 Ext-Q1 Device Alarms via LAPD

This test case verifies that the Ext-Q1 devices alarms start/cancel are reported to the BSC on OMUSIG as 8000 series alarms.


• FIU 19E


Two ET lines and FIU 19E are required to perform this test case. While commissioning the FIU 19, cross-connect two interfaces (interface 1 and 2) to the interface 1 and 2 of the Flexbus. Allocate OMUSIG and TRXSIG on interface 1. Other configuration is as per test plan.


DN0749988 Issue 2-0 en 18/01/2008


151 (381)

Pre-setup:


Step Input Expected output 1 Remove interace 2 from FIU 19.

Check the alarms on the BSC using MML command (ZEOL:<bcf_no>;). Also verify the Supplementary information fields.

8048 " LOSS OF INCOMING SIGNAL" is present in the alarm list for the Q1 address of FIU.

The functional entity number is correct.


2 Check the timestamp of the alarm. The timestamp is correct.

3 Execute BCF Object Reset from the BSC using MML command (ZEFR:<bcf_no>;).

When BCF reaches in WO state, check the alarms on BSC using MML (ZEOL:<bcf_no>;) command. Also verify the Supplementary information fields and timestamps in the alarms.

8048 "LOSS OF INCOMING SIGNAL" is present in the alarm list for the Q1 address of FIU.

The functional entity number is correct.


4 Reconnect interface 2 and check the alarms on BSC using MML (ZEOL:<bcf_no>;) command. Also verify the Supplementary information fields.

8048 "LOSS OF INCOMING SIGNAL" is not present in the alarm list for Q1 address of FIU.

2.7.2 Intelligent Shutdown for Flexi EDGE BTS

Overview A Battery Backup System provides protection against a Mains power break. Intelligent Shutdown maintains the BTS site operational for as long as possible by reducing the capacity (units turned off or reduced to low power consuming modes) so that only essential site functions are maintained. The reduction of the site capacity is controlled by the BSC, which commands the individual transceiver units to be shut down or started up. When the Mains power is restored, the BSC commands the BTS to power up all the shut down equipment and return back to full service.

Scope of testing This test plan verifies Intelligent Shutdown for Non-BCCH carriers and BCCH carriers during power failure.



DN0749988Issue 2-0 en18/01/2008

Configuration As per the test case comment.

Additionally, any standard configuration is used as a neighbouring site.

Settings 1. Activate the Battery Backup option at the BSC. (ZWOA:2,843,A; to activate BBU feature)

2. If EAC interface is used, configure the EAC Line for the 'Mains Break Down Alarm' at the BSC using MML command : ZEFX

Test cases

Pos Name Comment

1 Intelligent Shutdown of Non-BCCH TRXs 4+4+4, 2 Way combining, Common BCCH Segment (BTS 1 and 2)

2 Intelligent Shutdown of Non-BCCH TRXs 4+4+4, 2 Way combining, DDU, Antenna Hopping

3 Intelligent Shutdown of Non-BCCH TRXs 4+4, 2 Way combining, Every sector has its own EOCA unit

4 Intelligent Shutdown of all (BCCH & non-BCCH) TRXs

6+6+6 RTC


8+8, 2 Way combining, DDU


6+6+6, 4 Way combining, ESEA, Every sector has its own EOCA unit

2.7.2.1 Intelligent Shutdown of Non-BCCH TRXs

The objective of this test case is to verify that on power failure, non-BCCH carriers are shut down after the first timer expiry at the BSC. Further, it will be verified that:

• Until the second timer expiry at the BSC, the BCCH carriers continue to work as normal.

• The site can be recovered on recovery of mains power.

Test environment


DN0749988 Issue 2-0 en 18/01/2008


153 (381)

Network elements:

• Flexi EDGE BTS with Battery Backup Unit

Hardware tools:


Test case execution The first EXxx TRX modules in every sector control the ERxx DDU module for that corresponding sector.

Pre-setup:

• Flexi EDGE BTS is in supervisory state and Flexi EDGE BTS Manager is connected to it.

• First TRX in every sector is configured BCCH TRX.

• At BSC, Pmax is set to 0.

• Adjacent cells are defined as neighbours.

• Power supply to ESMA System Module is provided via Battery Backup Unit.

• Set the First shutdown timer (NTIM) at the BSC using ZEFM command.

• Spectrum Analyser is connected to monitor the RF transmission of TRXs.


1 Establish calls on all TRX objects. Voice call is established successfully.


2 Switch off the mains power supply to the Battery Backup Unit and observe the Alarms reported at the BSC and Flexi EDGE BTS Manager.

Check the LED Indications of the System Box at the Flexi EDGE BTS Manager.

The mains power supply is switched off and the BTS gets power from the Battery Backup unit.

Alarm 7995 “MAINS breakdown with Battery Backup” is reported to the BSC and Flexi EDGE BTS Manager.

The LED status of ESMA System Box is blinking yellow.

3 After the expiry of NTIM timer, observe the status of the calls in Non-BCCH TRXs.

The calls are handed over successfully to neighbouring cells (if commanded by the BSC).

4 Observe the messages sent by the BSC for TRX shutdown on the GSM Abis analyser.

Power Supply Control message is seen for the Non-BCCH TRX to be shut down.



DN0749988Issue 2-0 en18/01/2008


BTS Ack for this message is also seen.

5 Observe the RF transmission of BCCH/Non BCCH TRX using Spectrum Analyser.

Also observe the power state of EXxx TRX modules.

RF transmission continues for BCCH TRXs.

EXxx TRX Modules having BCCH and Non-BCCH:

RF transmission for Non-BCCH TRXs is stopped.

EXxx TRX Modules having only Non-BCCH:

EXxx TRX modules having only Non-BCCH are shut down.

Note: Same behaviour is observed for common BCCH configuration, for both non BCCH sector and BCCH sector.

6 Check the state of all non-BCCH TRXs at Flexi EDGE BTS Manager.

All non-BCCH TRXs are shown in Shutdown state with IS icon at Flexi EDGE BTS Manager.

Shut down EXxx TRX modules are shown Grey (dumb) with IS icon at Flexi EDGE BTS Manager.

7 Check the LED indications of all the EXxx TRX Modules at the Flexi EDGE BTS Manager.

The LED status of EXxx TRX modules having BCCH and Non-BCCH will be blinking green.

The LED status of EXxx TRX modules having BCCH and Non-BCCH will be grey.

8 Leave the site for 2 hours. After 2 hours, check for any alarms at the BSC and Flexi EDGE BTS Manager.

No new alarms are reported at the BSC and Flexi EDGE BTS Manager.

9 At Flexi EDGE BTS Manager, check the RSSI values for all TRXs.

The RSSI values reported at the Flexi EDGE BTS Manager should be valid.

10 Fetch SIR using Flexi EDGE BTS Manager and verify the properties of depowered EXxx TRX modules.

The following values are observed for depowered EXxx TRX modules.

Product Code "Unknown"

Serial Number "Unknown"

Hardware Version "Unknown"

HardwareStatus"Dumb"

Hardware State "Unknown"

Network Type "Unknown"

LED Colour "Gray"


DN0749988 Issue 2-0 en 18/01/2008


155 (381)


11 Switch ON the mains power supply and observe alarms on Flexi EDGE BTS Manager and at the BSC.

The 7995 alarm, “MAINS breakdown with Battery Backup” is cancelled at Flexi EDGE BTS Manager and at the BSC.

12 Observe the state of the EXxx TRX modules.

Observe the state of all TRX objects at Flexi EDGE BTS Manager.

Observer the LED state of all the EXxx TRX modules.

All the EXxx TRX Modules are powered on.

The Flexi EDGE BTS Manager displays the state of all TRX objects as supervisory.

The LED status should be the same as was in the start up of the test case execution.

13 Establish new CS calls on all the TRX objects. Calls are successfully established.

2.7.2.2 Intelligent Shutdown of all (BCCH and Non-BCCH) TRXs

The objective of this test case is to verify that on power failure, non-BCCH TRXs are shut down after the first timer expiry at the BSC, and BCCH TRX(s) are shut down after second timer expiry at the BSC. Further, it will be verified that:

• Until the second timer expiry at BSC, BCCH TRXs continue to work as normal.

• On the second timer expiry, BCCH TRX(s) are shut down, but transmission (O&M signalling link) continues to work as normal.

• Site can be recovered on recovery of mains power.


• Flexi EDGE BTS with Battery Backup Unit

Hardware tools:



• Flexi EDGE BTS is in supervisory state and Flexi EDGE BTS Manager is connected to it.


• Set the first shutdown timer (NTIM) and second shutdown timer (BTIM) at the BSC using the ZEFX command.

• Defined other BCF object as neighbour.



DN0749988Issue 2-0 en18/01/2008

• Spectrum analyser is connected to monitor the RF transmission of TRXs.


1 Establish calls on all TRXs. Voice call is established successfully.


2 Switch off the mains power supply to the Battery Backup Unit and observe the alarms reported at BSC and Flexi EDGE BTS Manager.

Check the LED Indications of the System Box at the Flexi EDGE BTS Manager.

Mains power supply is switched off and the BTS gets power from Battery Backup unit.

The Alarm 7995 “MAINS breakdown with Battery Backup” is reported to BSC and Flexi EDGE BTS Manager.

The LED Status of ESMA System Module is blinking Yellow.

3 Check that after the expiry of NTIM timer, observe the status of the calls in Non-BCCH TRXs.

In case of BB/Antenna hopping observe status of the calls in BCCH TRX’s also.


In case of BB/Antenna hopping, hopping group is reconfigured and ongoing calls are handed over successfully to neighbouring cells (if commanded by the BSC).

4 Check the state of all non-BCCH TRXs at Flexi EDGE BTS Manager.


Shut down EXxx TRX modules are shown Grey (dumb) with IS icon at Flexi EDGE BTS Manager.

For all ERxA dual duplexer units, which have all TRX objects as non BCCH are in shutdown state and are shown Grey (dumb) at Flexi EDGE BTS Manager.

5 Check that after the expiry of BTIM timer, observe the status of the calls in BCCH TRXs. (If any)


6 On the GSM Abis analyser, observe the messages sent by BSC for TRX shutdown.

Power Supply Control message is seen for the BCCH TRX to be shutdown.

BTS Ack for this message is also seen.

7 Observe the RF transmission of BCCH / Non-BCCH TRX using Spectrum Analyser.

Also observe the power state of EXxx TRX Modules.

RF Transmission for all TRXs is stopped.

All the EXxx TRX modules are shutdown.

8 Verify the state of all TRX objects and EXxx All TRX objects are shown in Shutdown


DN0749988 Issue 2-0 en 18/01/2008


157 (381)

Step Input Expected output TRX modules in Flexi EDGE BTS Manager.

In case of RTC configuration, verify that there is no impact on ECxx Remote Tune Combiner module in Flexi EDGE BTS Manager.

In case of EOCA modules present, verify that there is no impact on central and remote EOCA module in Flexi EDGE BTS Manager.

state with IS icon.

All the EXxx TRX modules are shown as Grey (dumb).

The Operational State of the ECxx Remote Tune Combiner module is Supervisory.

The Hardware status of the central and remote EOCA module is working.

9 Wait for 5 min and check for any alarms at BSC and at Flexi EDGE BTS Manager.

No new alarms are reported at BSC and Flexi EDGE BTS Manager.

10 Fecth SIR using Flexi EDGE BTS Manager and verify the properties of depowered EXxx TRX modules and ERxA dual duplexer modules.

Following values are observed for depowered EXxx TRX modules.

Product Code "Unknown"

Serial Number "Unknown"

Hardware Version "Unknown"

HardwareStatus"Dumb"

Hardware State "Unknown"

Network Type "Unknown"

LED Colour "Gray"

For depowered ERxA dual duplexer modules:

Product_Code "unknown"

Module_Identifier "unknown"

Serial_Number "unknown"

Hardware_Version "unknown"

Hardware_Status "Dumb"

Network_Type "unknown"

Operational_State "unknown"

Active_SW_Version "unknown"

Backup_SW_Version "unknown"

LED_Colour "Gray"

11 Check ECxx Remote Tune Combiner properties from SIR fetched in step 10(If present).

All the properties have correct values as copmared to values displayed on hardware.

HardwareStatus "Working"

OperationalState "Supervisory"

LedColor Stable "Green"



DN0749988Issue 2-0 en18/01/2008


12 Check central and remote EOCA optical converter module properties from SIR fetched in step 10(If present).

All the properties have correct values as compared to values displayed on hardware.

Hardware_Status "Working"

Led_Colour "Stable Green"

13 Switch ON the mains power supply and observe alarms on Flexi EDGE BTS Manager and at BSC.

The 7995 alarm, “MAINS breakdown with Battery Backup” is cancelled at Flexi EDGE BTS Manager and at BSC.

14 Observe the state of the EXxx TRX modules and TRX objects on Flexi EDGE BTS Manager.

Observe the LED state of all the EXxx TRX modules.

All the EXxx TRX Modules are powered on.

Flexi EDGE BTS Manager displays state of all TRX objects as supervisory.

The LED status should be the same as was in the start up of the test case execution.

15 Establish new CS calls on all TRX objects. Calls are successfully established.

2.7.3 Autodetection

Overview The Flexi EDGE BTS detects the presence and capability of active units automatically, including revision and serial numbers (as on unit identity label). If there is a change in a module, change in configuration when extra capacity (more EXxA TRX modules) are added, or a faulty unit is replaced with a new unit, it is automatically detected.

Scope of testing This test plan verifies the

• Auto-detection of BTS internal units (and related RF cabling) at startup

• Auto-detection of the Q1 device.

Testing of the hot insertion of units is covered in the test plan for the BTS site expansion feature.

Test cases

Pos Name Comment

1 Autodetection of BTS Internal units at Site Startup with DDU

8+8+8, 4-way combining

2 Autodetection of BTS Internal units at Site Startup with RTC

6+6+6, cavity combining


DN0749988 Issue 2-0 en 18/01/2008


159 (381)

Pos Name Comment

3 Autodetection of BTS Internal units at Site Startup with DDU

4+4+4, 2 Way, Flexi EDGE BTS Manager EP1 CD1.0

4 Autodetection of BTS Internal units when more than Configured units are Present

2+2+2, spare TRX module in each sector

5 Autodetection of BTS Internal units when more than Configured units are Present

6+6+6, Each sector has ECEA unit and Spare TRX module

6 Autodetection of Q1 Device Any configuration with FIFA

2.7.3.1 Auto-detection of BTS Internal Units at Site Startup with DDU

The objective of this test case is to verify the auto-detection of BTS internal units with ERxx DDU modules at site startup.


• Flexi EDGE BTS Manager is connected to the Flexi EDGE BTS.

• Flexi EDGE BTS is commissioned so that RF Cabling Auto-detection is enabled.

• Flexi EDGE BTS is in supervisory state.

• Default TRX test parameters used and PMAX=0 set at the BSC.


1 Lock the BCF in the BSC using MML command.

Observe the state of the BCF/BTS/TRX objects at the Flexi EDGE BTS Manager.

The BCF is locked at the BSC.

The state of all the objects is locked.

2 Power reset the Flexi EDGE BTS.

When the BCF comes up, check the status of all the Auto Detected Units in the Flexi EDGE BTS Manager.

The BCF will be in Software Loading State.

LED status of ESMA System Module is blinking green.

All the TRX objects will be in TRX Started state.

LED status of all the EXxx TRX Modules will be blinking yellow.

All the ERxx DDU Modules will be in Configuring state.



DN0749988Issue 2-0 en18/01/2008


LED status of all the ERxA DDU Modules will be blinking yellow.

3 Check BTS internal units are displayed and correctly shown connected on ESMA ports as per physical cabling on Flexi EDGE BTS Manager .

ESMA System Module, EXxx TRX modules and ERxx DDU modules are correctly shown connected in Base Station view in Flexi EDGE BTS Manager.

4 Open the Base Station View in Flexi EDGE BTS Manager, click on ESMA and verify the following properties against the label present on the unit.

System Module Properties

• Product Code

• Module identifier

• Serial Number

• Hardware version

ESMA-System Module properties displayed should exactly match the label present on the unit.

5 Open the Base Station View in Flexi EDGE BTS Manager, highlight the connected EXxx TRX modules and verify the following properties against the label present on the unit.

TRX Module Properties

• Product code


• Serial number


• Network type

EXxx TRX Module properties displayed should exactly match the label present on the unit.

6 Open the Base Station View in Flexi EDGE BTS Manager, highlight the connected ERxx DDU modules and verify the following properties against the label present on the unit.

DDU PIU Properties

• Product Code

• Module Identiifer

• Serial Number

• Hardware Version

• Network type

ERxx DDU module properties displayed should exactly match with the label present on the unit.

7 Unlock the BCF in the BSC. The BCF will be in Supervisory State


DN0749988 Issue 2-0 en 18/01/2008


161 (381)


Wait for BCF to come to supervisory state and check the status in Flexi EDGE BTS Manager.

Check for any alarms at Flexi EDGE BTS Manager and at the BSC.

All the TRX objects will be in supervisory state

The ERxx DDU module will be in supervisory state

The LED status of all the units is stable green.

No alarms are present at Flexi EDGE BTS Manager or at the BSC.

8 Check RF cables information on Flexi EDGE BTS Manager.

Flexi EDGE BTS Manager displays the RF cables (both Tx and Rx) as in the actual physical connection.

9 From the BSC, run TRX Test for all the TRX objects and verify the result at the BSC.

The TRX Test is PASSED with BER and FER = 0.

10 Fetch the Site Information Report from Flexi EDGE BTS Manager and verify all the properties of the units and the cabling information.

Site Information Report reflects the correct information (including the related cabling information) for all the connected modules.

2.7.3.2 Autodetection of BTS Internal Units at Site Startup with RTC

The objective of this test case is to verify the autodetection of BTS internal units with cavity combining at site startup.



• Flexi EDGE BTS is commissioned so that RF Cabling Auto-detection is enabled.




1 Lock the BCF in BSC using MML command.

Observe the state of the BCF/BTS/TRX objects at the Flexi EDGE BTS Manager.

BCF is locked at the BSC

The state of all the objects is locked.

2 Power reset the Flexi EDGE BTS.

When the BCF comes up, check the status of all the Auto Detected Units in the Flexi EDGE

The BCF will be in Software Loading state.

LED Status of ESMA System Module is blinking green.



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output BTS Manager.

All the TRX Modules will be in TRX Started state.

LED status of all the EXxx TRX Modules will be blinking yellow.

All the ECxx RTC Modules will be in Configuring state.

LED status of all the ECxx RTC Modules will be blinking yellow.

3 Check that BTS internal units are displayed and correctly shown connected on ESMA System Module / ESEA System Extension Module ports as per the physical cabling on Flexi EDGE BTS Manager .

ESMA System Module, ESEA System Extension Module, ECxx RTC modules and EXxx TRX modules are correctly shown connected in the Base Station view in Flexi EDGE BTS Manager.

4 Open the Base Station View in Flexi EDGE BTS Manager, click on ESMA and verify the following properties against the label present on the unit.

System Module properties

• Product code


• Serial number

ESMA System Module properties displayed should exactly match with the label present on the unit.

5 Open the Base Station View in Flexi EDGE BTS Manager, highlight the ESEA System Extension module and verify the following properties against the label present on the unit.

Extension Module properties

• Product code

• Serial number


ESEA System Extension Module displayed should exactly match the label present on the unit.

6 Open the Base Station View in Flexi EDGE BTS Manager, highlight the connected EXxx TRX modules and verify the following properties against the label present on the unit.

TRX Module properties

• Product code


• Serial number

EXxx TRX Module properties displayed should exactly match with the label present on the unit.


DN0749988 Issue 2-0 en 18/01/2008


163 (381)



• Network type

7 Open the Base Station View in Flexi EDGE BTS Manager, highlight the ECxx Modules and verify the following properties against the label present on the unit.

RTC Module properties

• Product code

• Module identiifer

• Serial number


• Network type

ECxx RTC Module properties displayed should exactly match with the label present on the unit.

8 Unlock the BCF in the BSC.

Wait for the BCF to come to supervisory state and check the status in Flexi EDGE BTS Manager.

Check for any alarms at Flexi EDGE BTS Manager and at the BSC.

The BCF will be in supervisory state.

All the TRX objects will be in supervisory state.

The ECxx RTC module will be in supervisory state.

The LED status of all the units is stable green.

No alarms are present at Flexi EDGE BTS Manager or at the BSC.

9 Check RF cables information on Flexi EDGE BTS Manager.


10 From the BSC, run TRX Test for all the TRX objects and verify the result at the BSC.

The TRX Test is PASSED with BER and FER=0.

11 Fetch the Site Information Report from Flexi EDGE BTS Manager and verify all the properties of the units and cabling Information.

The Site Information Report reflects the correct information (including the related cabling information) for all the connected modules.

2.7.3.3 Autodetection of BTS Internal Units when more than Configured Units are present

The objective of this test case is to verify autodetection of BTS internal modules at site startup, when the number of internal modules present at site is more than the configuration defined at the BSC.

Test case execution



DN0749988Issue 2-0 en18/01/2008

An additional EXxx TRX module (which is not controlling the ERxx DDU module) is present in each of the sectors

Pre-setup:


• Flexi EDGE BTS is successfully commissioned for 2+2+2 configuration with RF cabling auto-detection enabled.


1 Using the Flexi EDGE BTS Manager, give a BCF reset.

The BCF is reset and Flexi EDGE BTS Manager is disconnected.

2 After the BCF comes up, check BTS internal modules displayed at Flexi EDGE BTS Manager, in Base Station view.

ESMA System Module, 6 EXxx TRX modules and 3 ERxx DDU modules are autodetected and shown at Flexi EDGE BTS Manager.

3 Check the status of all the autodetected modules at Flexi EDGE BTS manager.

BCF will be in supervisory state.

LED status of the ESMA System Module is stable green.

All the configured TRX objects will be in supervisory state.

LED status of the EXxx TRX modules with configured TRX objects is stable green.

All the ERxx DDU modules will be in supervisory state and LED status is stable green.

The unconfigured TRX objects will be in Configuring state.

LED status of the EXxx TRX modules with unconfigured TRX objects is blinking yellow.

4 Check for any alarms reported for the unconfigured TRX objects at the BSC and Flexi EDGE BTS manager.

No alarms are reported for the unconfigured TRX objects at BSC and Flexi EDGE BTS Manager.

5 Fetch the Site Information Report from Flexi EDGE BTS Manager and check for all the properties of all the modules.

The Site Information Report reflects the correct information for all the connected modules (both configured and unconfigured).

The RF cabling information reflects the 2+2+2 configuration.

2.7.3.4 Auto-detection of Q1 Device

The objective of this test case is to verify auto-detection of a Q1 Device by the Flexi EDGE BTS.


DN0749988 Issue 2-0 en 18/01/2008


165 (381)


• FIU19




• FIU19 is commissioned at a valid Q1 address (0-3999) and at the Baud rate defined at the BSC.

• FIU19 is not configured at the BSC.


1 Connect the FIU19 to the Q1 port the Flexi EDGE BTS.

Check that FIU19 is detected within 4 hours by the Flexi EDGE BTS, and observe the GSM Abis Analyser for the message BTS_NEW_TRE_INFO

BTS_NEW_TRE_INFO is sent from the Flexi EDGE BTS to the BSC with the following parameters:

New TRE info

- Q1 address : Address of FIU19

- Q1 capability : Q1E

2 Observe the GSM Abis Analyser for updated BTS_TRE_POLL_LIST message from the BSC.

The updated BTS_TRE_POLL_LIST has the Q1 address of FIU19.

TRE object identity : < tre_id>

Q1 address : <Address of FIU19>

Polling : Low

3 In the BSC, check the list of Q1 devices present using the command

ZQWL:BCF=<bcf_number>;

The following details are displayed :

Q1 address : <Address of FIU19>

Equipmnet Type : FIU19

Equipment Generation : Q1E

4 In Flexi EDGE BTS Manager, in the Base Station View, click on the TRE Icon.

In Flexi EDGE BTS Manager, check for any alarms.

Q1 device-FIU19

Q1 Address - Address of FIU19

are displayed in the Flexi EDGE BTS Manager.

No alarms are present.

5 Remove the Q1 cable between the FIU19 and the Flexi EDGE BTS and check for alarms at the Flexi EDGE BTS Manager and the BSC.

Within 30 seconds, the alarm 8202 "Loss of Supervision Connections" is displayed against the Q1 address of FIU19.

After 10 seconds after reporting of the



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output above alarm, the alarm 7601 "All external Q1 devices fail to respond" is generated.

6 Reconnect the Q1 cable between the FIU19 and the Flexi EDGE BTS and check for the alarm cancellation at the Flexi EDGE BTS Manager and the BSC.

Within 30 seconds, the alarm 8202 "Loss of Supervision Connections" is cancelled against the Q1 address of FIU19.

After 10 seconds after the cancellation of the above alarm, the alarm 7601 "All external Q1 devices fail to respond" is cancelled.

2.7.4 External Battery Back Up Unit Support

Overview A Battery Backup Unit (BBU) is added to the BTS Site, so as to provide protection against mains breakdown. The Flexi EDGE BTS supports three different models of BBU, that is, FPMA, MIBBU and Non-Nokia BBU, which in the emergency/odd conditions of no power supply or fault in powering, provides the site with backup power.

When mains breakdown or some other failures results in the BTS Site down, then BTS site works with the help of BBU and generate alarms according to the fault condition. BSC then takes the appropriate actions as per the fault conditions specified by the BTS site so as to maintain the same state of the BTS site, which in turn will not create any major impact on the services provided by that particular BTS site.

Scope of testing This test plan verifies the alarm generation in case of a mains breakdown and the BBU providing power without call disruption.

Settings Configure EAC Alarms lines. >>>ZEFX: <bcf_id>:INBR=<external Input number>: ROU=3:POL=<OPEN - active or CLOSED - inactive>, SEV=AL3;

Test cases

Pos Name Comment

1 External Battery Back Up - Alarms Reporting

--


DN0749988 Issue 2-0 en 18/01/2008


167 (381)

2.7.4.1 External Battery Back Up - Alarms Reporting

The objective of the test case is to verify that the 7995 Mains breakdown alarm is raised when a mains power failure occurs.


• FPMA unit


1. Configure EAC Line 1 at the BSC for Mains Breakdown Alarm.

2. Flexi EDGE BTS Manager is connected to the system.

3. AC power connected to ESMA through FPMA unit.


1 Establish some calls. Voice calls are established successfully.


2 Switch off the Mains power supply for 2 minutes.

Alarm 7995-Mains breakdown with battery back up is reported at the BSC and the BTS Manager.

The BTS continues to get power from the Battery Backup unit.

3 Observe the ongoing calls, do active listening during step 2.


4 Switch on the Mains power supply. Alarm 7995-Mains breakdown with battery back up is cancelled at the BSC and BTS Manager.

5 Observe the ongoing calls, do active listening during step 4.


6 Repeat step 2. Same as in step 2.

7 Give BCF object reset from BTS Manager. The BCF comes back to supervisory after reset.

Alarm 7995-Mains breakdown with battery back up is reported at the BSC and the BTS Manager.



DN0749988Issue 2-0 en18/01/2008

2.7.5 BTS External Alarms and Controls

Overview

External Alarms and Controls (EAC) signals can be defined to the BTS. Alarms caused on the site, such as the intruder alarm, are sent to NetAct through Abis.

There are 24 user-definable inputs and 6 user-definable outputs. On ESMA, there are 18 inputs and 6 outputs; another 6 inputs are available in an optional additional box (EAC extension module). It is possible to label the user-definable external alarms and controls in the RNW database at the BSC.

The EAC settings (name and polarity) are defined at the BSC. The user can define whether an alarm is raised when the External Alarm input is grounded or disconnected from the ground potential. This allows more flexibility for the alarming device.

Scope of testing The scope of testing is limited to test EAC input lines for route “ACT” and “TMS” only. Route “MAINS” will be covered “Intelligent Shutdown for Flexi EDGE BTS”. Also the EAC output line will be tested under this plan.

Configuration

Item Details

Channel configuration BCCH TRX: MBCCHC+ 7 TCH/F

Non_BCCH TRXs: 8 TCH/F

First TRX of each BTS object is BCCH TRX Settings None. Test cases

Pos Name Comment

1 External Input Line Alarm Control - Reporting route is ACT

2+2+2

2 External Output Line Control 2+2+2

3 External Input Line Alarm Control - Reporting route is TMS

2+2+2

2.7.5.1 External Input Line Alarm Control - Reporting Route Is ACT

The purpose of these tests is to check that the user-definable external alarms operate properly, when the reporting route is defined as ‘ACT’.


DN0749988 Issue 2-0 en 18/01/2008


169 (381)


• EAC Test Line Box


1. Flexi EDGE BTS Manager is connected to the BTS site via a local connection.

2. The EAC Test Line Box is connected.


1 Configure EAC input line with Routing as 'ACT' using MML command

(ZEFX:<bcf_no>:INBR=<line_number>:ROU=ACT,POL= <polarity>: SEV="severity", TID=<Text ID>;

Alarm text is defined to all user definable alarms at the BSC (MML command ZEFE). Some EAC inputs are defined to be active while others are defined to be not active with different polarities. Different severities are defined. Alarm lines are set at the BTS Site so that alarm condition is not active.

EAC lines are configured sucessfully as observed on the BSC.

2 All alarm conditions are activated one by one. Alarms and alarm text are checked from the BSC using MML command (ZEOL:<bcf_no;>).

Alarms are also checked in the Flexi EDGE BTS Manager Alarm window.

Alarms (7401–7424) are activated at the BSC and Flexi EDGE BTS Manager according to activity and polarity definitions. All 24 alarms are in active state at the same time.

3 All alarm conditions are cancelled one by one.

Alarms are checked from the BSC and Flexi EDGE BTS Manager.

Alarms are cancelled.

4 Activate some alarm conditions. Activated alarms and alarm texts are checked from the BSC using MML command (ZEOL:<bcf_no;>)


74xx alarms are activated at the BSC and Flexi EDGE BTS Manager according to activity and polarity definitions.

5 Perform a BCF object reset from the BSC using MML command ZEFR:<bcf_no>;

Once the BCF reaches WO state, activated alarms and alarm texts are checked from the BSC using MML command

74xx alarms are activated at the BSC and Flexi EDGE BTS Manager according to activity and polarity definitions.



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output (ZEOL:<bcf_no;>)


2.7.5.2 External Output Line Control

The purpose of these tests is to check that the user-definable external output operates properly.



• Digital oscilloscope





1 An external output is activated with the BSC MML command (ZEFT:<bcf_no>:ON=<output_line>,:). All user-definable outputs are tested.

States of the external output can be changed with the MML command. The states can be both low and high.

2 All 6 outputs are set to low state (OFF). States of the outputs are set according to the BSC definition.

3 Execute BCF reset and verify with the digital oscilloscope.

States of the outputs remain OFFduring and after the BCF reset and there is no transition to ON.

4 All outputs are set to high state (ON). States of the outputs are set according to the BSC definition.

5 Execute a BCF reset. States of the outputs remain ON after the BCF is started up.

6 All outputs are set to various states ("OFF/ON").

States of the outputs are set according to the BSC definition.

7 Set an output line to high state (ON) and others to low state (OFF).


8 Execute a BCF object reset and verify the output line state, which is set to high (ON) with the digital oscilloscope.

State of the output line changes to OFF and after that there is a single transition to high state (ON).


DN0749988 Issue 2-0 en 18/01/2008


171 (381)


9 Perform power OFF/ON on ESMA and verify the output line state, which is set to high (ON) on the digital oscilloscope.

State of the output line changes to OFF and after power-on. there is a single transition to high state (ON).

10 When the BCF is in supervisory state, change the output line states from low to high and vice versa.


2.7.5.3 External Input Line Alarm Control - Reporting Route Is TMS

The purpose of this test case is to verify that the EAC alarms are reported as 8240 alarms (EAC input line number is in SB field of the alarm), when the route to report is configured as ‘TMS’.




1. Flexi EDGE BTS Manager is connected to the BTS site via a local connection.



1 Configure EAC input lines with Routing as 'TMS' using MML command

(ZEFX:<bcf_no>:INBR=<line_number>:ROU=TMS,POL=<polarity>:;

Some EAC inputs are defined to be active while others are defined to be not active with different polarities. Alarm lines are set at the BTS Site so that alarm condition is not active.

EAC lines are configured sucessfully as observed on the BSC.

2 All alarm conditions are activated one by one. Alarms are checked from the BSC using MML command (ZEOL:<bcf_no>;).


Alarms (8240) are activated at the BSC and Flexi EDGE BTS Manager according to activity and polarity definitions. All 24 alarms are in active state at the same time.

3 All alarm conditions are cancelled one by one.

Alarms are checked from the BSC and Flexi EDGE BTS Manager.


4 Configure EAC input lines with Routing as EAC lines are configured sucessfully as



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output 'TMS' using MML command with polarity "OPEN"

(ZEFX:<bcf_no>:INBR=<line_number>:ROU=TMS,POL=<polarity>:;

The polarity of all the input lines on the EAC test line box are "CLOSED".

observed on the BSC.

5 Disconnect the EAC Test Line Box.

Alarms are checked from the BSC using MML command (ZEOL:<bcf_no>;).


Alarms (8240) are activated at the BSC and Flexi EDGE BTS Manager according to activity and polarity definitions. All 24 alarms are in active state at the same time.

6 Re-connect the EAC Test Line Box (the polarity of all the input lines on the EAC test line box is "CLOSED").

Alarms are checked from the BSC using MML command (ZEOL:<bcf_no>;).



2.7.6 TRX Test

Overview The TRX test checks the loop path from digital parts and radio frequency within the EXxA Dual TRX module, RF interconnect cabling and RF parts of combiner ERxA Dual Duplexer module or ECxA Remote Tuning Combiner module and back. The test gives information on radio signal level and quality, and is provided in test result of the test. The TRX test reserves two traffic channels during the test. Flexi EDGE BTS supports TRX test commanded by the BSC and Flexi EDGE BTS Manager.

Scope of testing Testing shall be started with the following variations:

• ERxA DDU modules (and combining types) and ECxA RTC modules configurations

• Initiated from the both BSC and Flexi EDGE BTS Manager

• Both for GMSK and 8PSK modulation

• All GSM bands 800/900/1800/1900/E900

Configuration


DN0749988 Issue 2-0 en 18/01/2008


173 (381)

GSM E900: MA list shall include ARFN 0.

The same MA list to be attached to all BTS objects.

Settings The TRX Test thresholds criteria defined in BSC MML ('ZUCV') shall have values as recommended in BSC Product Documentation (Radio Network Testing description).

BTS Power level (PMAX) shall be at 4dB attenuation.

Test cases

Pos Name Comment

1 TRX Test Initiated From Flexi EDGE BTS Manager In Supervisory state

4+4+4, RF Hopping, 2-way

2 TRX Test Initiated From Flexi EDGE BTS Manager In Supervisory state

6(GSM 900) + 6(GSM 1800), No Hopping, Cavity Combining

3 TRX Test Initiated From BSC 2+2+2, RF Hopping, bypass

4 TRX Test Initiated From BSC 8+8, RF Hopping, 2-way using 2 DDU per sector

5 TRX Test Initiated From BSC 6(GSM 900) + 6(GSM 1800), No Hopping, Cavity Combining

6 TRX Test Initiated From BSC 4(GSM 1800) + 4(GSM 900) + 4(GSM E900), RF Hopping, 2-way

7 TRX Test Initiated From BSC 8-omni, GSM 1800, RF Hopping, 4-way

8 TRX Test Initiated From BSC 12-omni, No hopping, Cavity Combining

9 TRX Test Initiated From BSC 3+3+3 (cost optimised: 5 EXxA), RF hopping, 2-way

10 TRX Test Initiated From Flexi EDGE BTS Manager In Local Mode Of Operation

4+4, 2-way

11 TRX Test Initiated From Flexi EDGE BTS Manager In Local Mode Of Operation

6(GSM 900) + 6(GSM 1800), Cavity Combining



DN0749988Issue 2-0 en18/01/2008

2.7.6.1 TRX Test Initiated From Flexi EDGE BTS Manager in Supervisory state

The objective of this test case is to verify that the TRX test can be successfully executed from Flexi EDGE BTS Manager when the TRX is in SUPERVISORY state.


1. The BCCH power level for all the sectors is defined as the maximum value (that is, 0) using the ZEUG command on the BSC.

2. GPRS and EGPRS are enabled on all the sectors. There are a few RTSLs in each sector that have synchronisation established with the PCU (that is, timeslots with channel status = 'GP)


1 Start 4 pairs of MS-MS CS calls in sector 1. Verify that the CS calls are established successfully.

2 Invoke a TRX Test for TRX-1 of sector 1 from Flexi EDGE BTS Manager by selecting Tests --> TRX test with the following parameters:

Mode='GMSK'

Timeslot: Any randomly chosen timeslot.

TRX test is started on the mentioned TRX and timeslot. Verify the same in the Test result pane which shows "TRX test is Ongoing".

Verify in the Flexi EDGE BTS Manager active alarms window that 7615 alarms are active for the duration of the test, for each of the reserved timeslots with the description 'RTS IS IN TEST USE: Radio TS is in test use'.

3 Observe the voice quality of all the CS calls for the duration of the test.

Verify that there is no perceptible degradation in voice quality, while the test is running.

4 After the test is over, verify that test results on the right hand pane includes following fields:-

Test Result:

Tx Power:

Main Rx BER:

Main Rx Sensitivity:

Diversity Rx BER:

Diversity Rx Sensitivity:

Verify that the TRX test result is "Passed" with the values of different parameters as follows:

Test Report Parameters

Test Result: PASS

Tx Power: >= 47 dBm

Main Rx BER: 0

Main Rx Sensitivity: < -110 dBm

Diversity Rx BER: 0

Diversity Rx Sensitivity: < -110 dBm

5 Repeat steps 1-4 for all TRXs of sector 1. Use test modes GMSK and 8PSK alternately.


6 Repeat steps 1-4 for a timeslot with channel Verify the results as in steps 1-4.


DN0749988 Issue 2-0 en 18/01/2008


175 (381)

Step Input Expected output status = 'GP' that is, it has PCU synchronisation established. After the TRX test is over, verify that the

channel status comes back to 'GP'. Also verify using Abis Analyser logs that PCU synchronisation again gets established for the timeslot.

2.7.6.2 TRX Test Initiated from BSC

The objective of the test case is to verify that the TRX tests can be successfully executed from the BSC.


• The BCCH power level for all the sectors is defined to be the maximum value (that is, 0) using the ZEUG MML command.


1 Start one MS-MS CS call and one packet data transfer in each sector.

Note: A file of size 5MB (approx.) should be used for transfer to ensure that the data transfer continues for the entire duration of the test. If it finishes before the test case is over, it should be started again.

Verify that the CS calls and packet data transfers start successfully.

2 Start the TRX Test TRX 1 from the BSC with MML command ‘ZUBS’, with the testing mode as 'GMSK' and any randomly chosen timeslot.

Observe the execution output of the MML command at the BSC which displays: ‘TRANSCEIVER TEST STARTED


3 Invoke the TRX Test Report for TRX 1 on the BSC using MML command ‘ZUBP’.

Verify that the TRX test is successful and its report is displayed at the BSC with the following contents:

BCF/BTS/TRX/RTSL Number

Test Result: Passed

Transmitted Power Level: >= 47 dBm

BER for main branch::0

Rx Sensitivity for main branch: < -110 (i.e. better than -110)

BER for Diversity Rx branch: 0

Rx Sensitivity for Diversity branch: < -110



DN0749988Issue 2-0 en18/01/2008


4 Observe the CS calls and packet data transfer started in the first step.

Verify that there is no perceptible degradation in voice quality for CS calls and packet data transfers do not show any significant drop in the data transfer rate.

5 Repeat steps 2-4 for all TRXs in the site. Verify the results as given in steps 2-4.

6 Repeat steps 2-4 with test MODE=8PSK in each sector, for the following TRXs one after the other:

BCCH TRX

At least one non-BCCH TRX

Verify the results as given in steps 2-4.

7 Run at least one MS-MS CS call in each sector (not necessarily simultaneously) for a timeslot which was used for the TRX test.

Verify that the call establishment is successful having good voice quality with no perceptible glitches/echo/noises.

8 Observe the active alarms on the BSC for all the TRXs/sectors on the BTS site, using 'ZEOL' MML command.

There are no active alarms related to TRX Test/Loop Test.

2.7.6.3 TRX Test Initiated from Flexi EDGE BTS Manager in Local Mode of Operation

The purpose of the test case is to verify that the TRX test can be successfully executed from Flexi EDGE BTS Manager when the site is running in Local Mode.


Go to Flexi EDGE BTS Manager, BTS_Control -> Disable_Abis. This will disable the Abis interface and trigger a BCF_Reset. After the site comes up again, on the Flexi EDGE BTS Manager, go to BTS_SW -> Use_Current. The BCF will come to supervisory state in Local mode. The TRX objects will come to CONFIGURING state

Abis link is not connected and an alarm indicating the same is reported.


1 Invoke a TRX Test for any TRX of the site from Flexi EDGE BTS Manager by selecting Tests TRX test with the following parameters:

Mode='GMSK'

Timeslot: Any randomly chosen timeslot.

ARFN - Specify any ARFN belonging to the band of the EXxA TRX Module

TRX test is started on the mentioned TRX and timeslot. Verify the same in Test result pane which shows "TRX test is Ongoing".


DN0749988 Issue 2-0 en 18/01/2008


177 (381)


2 After the test, verify that test results on the right-hand pane include the following fields:-

Test Result:

Tx Power:

Main Rx BER:

Main Rx Sensitivity:

Diversity Rx BER:

Diversity Rx Sensitivity:

Verify that the TRX test result is "Passed" with the values of different parameters as follows -

Test Report Parameters

Test Result: PASS

Tx Power: 47 dBm (+/- 1)

Main Rx BER: :: 0

Main Rx Sensitivity: < -110 dBm

Diversity Rx BER: 0

Diversity Rx Sensitivity: < -110 dBm

3 Repeat step 1-2 for two more TRXs of the site, belonging to different bands (if any). Use test mode 8PSK.


2.7.7 BTS Local Blocking

Overview There are mainly three (logical) objects, which are managed by the Flexi EDGE BTS:

• BCF object

• BTS object

• TRX object

The above-mentioned objects can be blocked locally with Flexi EDGE BTS Manager to enable different operations, such as service operations. The BTS informs the BSC of the blocking by sending a minor (7208 ‘Local Block’) alarm. The BSC then clears all the calls from the TRX concerned and takes appropriate measures to restore traffic via other TRXs in the BTS, as it would do in the case of a real equipment failure. When the BCF/BTS/TRX object is unblocked with Flexi EDGE BTS Manager, the BTS site cancels the alarm and recovers the concerned object.

Scope of testing The scope of testing is limited to BCF, BTS and TRX block/unblock, the verification of BTS SW and BTS Manager version compatibility, and recovery after BSC object control.

Settings



DN0749988Issue 2-0 en18/01/2008

None.

Test cases

Pos Name Comment

1 Local BCF Block/Deblock --

2 Local BTS Block/Deblock -

3 Local BTS Block/Deblock BTS SW EP1 CD1.0, Flexi EDGE BTS Manager EP1.1

4 Local TRX Block/Deblock -

5 Local TRX Block/Deblock BTS SW EP1.1, Flexi EDGE BTS Manager EP1 CD1.0

6 BCCH Reconfiguration on Local TRX Block

-

7 Local BCF Block and Lock/Unlock --

2.7.7.1 Local BCF Block/Unblock

This test case verifies that BCF object can be successfully locally blocked and deblocked from the Flexi EDGE BTS Manager. The BSC clears all calls from the TRX(s) concerned and takes appropriate measures to restore traffic at 60th second of the block command. Also, LAPD links of all the TRXs under the BCF are released and BCCH transmission is stopped after 60 secs of the BCF block command.




• Flexi EDGE BTS Manager is connected to the BTS site via a local connection.


1 Establish a Mobile-to-Mobile call. The call is successfully established.

2 Block the BCF object from Flexi EDGE BTS Manager and observe the following within 60 seconds of BCF Block command.

BCF object state at Flexi EDGE BTS Manager (by viewing the BCF properties in the Base

The object state of the BCF at Flexi EDGE BTS Manager is Block Requested…


DN0749988 Issue 2-0 en 18/01/2008


179 (381)

Step Input Expected output Station View)

TRXSIG of all the TRXs (by viewing the TRX Object properties in the Base Station View)


TRXSIG of the TRXs is ON.

7208 alarm “Local Block” on the BCF object is present in the Flexi EDGE BTS Manager alarm window.

3 Check the operational state of the BCF from the BSC (ZEEI:<bcf_no>; )

The operational state of the BCF/BTS/TRX at the BSC is BL-BCF.

4 Observe the following after 60 secs of BCF Block command from Flexi EDGE BTS Manager:

BCF Object state at Flexi EDGE BTS Manager (by viewing the BCF properties in the Base Station View).

Check the TRXSIG of all the TRXs (by viewing the TRX Object properties in the Base Station View).

Check the EXxA LED colour on EXXA Units and at Flexi EDGE BTS Manager.

The object state of the BCF at Flexi EDGE BTS Manager is Blocked.

TRXSIG of the TRXs is OFF.

The EXxA LED colour on EXxA Units and at Flexi EDGE BTS Manager is stable yellow.

5 Observe the call. BSC clears all calls from the TRX(s) concerned and takes appropriate measures to restore traffic at 60th second of the block command.


The following alarms should be present:

7208 Alarm “Local Block” for BCF object

7767 “BCCH MISSING” alarm for the BCCH TRX

7705 “LAPD FAILURE” alarm for all the TRXs

7 BCCH transmission is checked using a spectrum analyser.

The BCCH transmission is stopped in all the sectors under the BCF.

8 Disconnect and reconnect the Bus cables of all the EXxA units and check the alarms in the alarm window of Flexi EDGE BTS Manager.

Check the alarms on the BSC using MML command (ZEOL:<bcf_no>;)

No 7606/7603/7600 alarm appeared.

9 Unblock the BCF object from Flexi EDGE BTS Manager.

Check the alarms in the alarm window of Flexi EDGE BTS Manager.

7208 alarm “Local Block” on BCF has disappeared in the alarm window at Flexi



DN0749988Issue 2-0 en18/01/2008


Check the alarms on the BSC using MML command (ZEOL:<bcf_no>;).

EDGE BTS Manager.

Alarm 7208 “Local Block” is not present on the BSC alarm list.

The BSC commands a BCF reset. The BCF reset is executed.

10 Once the BCF reset is completed, check the operational state of the BCF/TRXs on the BSC ( ZEEI:<bcf_no>;)

The operational state of the BCF and all TRX objects is WO.

2.7.7.2 Local BTS Block/Unblock

This test case verifies that a BTS object (Sector) can be successfully blocked and unblocked from Flexi EDGE BTS Manager. The BSC clears all the calls from the TRX(s) concerned and takes appropriate measures to restore traffic at the 60th second of the block command. Also, the LAPD link of all the TRXs under the BTS object (sector) is released and the BCCH transmission is stopped in the sector after 60 secs of the BTS block command. Locking/unlocking the BTS object when it is in blocked state does not allow the BTS object to come to supervisory state.




• Flexi EDGE BTS Manager is connected to the BTS site via local connection.


1 Establish an MS-to-MS call in all the BTS objects (sectors).

The calls are successfully established in all the sectors.

2 Block the second BTS object (using 2-way combining) from Flexi EDGE BTS Manager and observe the following within 60 seconds of the BTS Block command:

BTS object state at Flexi EDGE BTS Manager (by viewing the BTS properties in the Base Station View)

TRXSIG of all the TRXs under “blocked requested” sector (by viewing the TRX Object properties in the Base Station View)

The object state of the BTS (sector) at Flexi EDGE BTS Manager is Block Requested…



DN0749988 Issue 2-0 en 18/01/2008


181 (381)



7208 alarm “Local Block” on BTS object is present in the Flexi EDGE BTS Manager alarm window.

3 Check the operational state of the BTS object (sector) from the BSC (ZEEI:<bcf_no>; )

The operational state of the BTS object (sector) and all the TRX objects under BTS object (sector) at the BSC is BL-BTS.

4 Observe the following after 60 seconds of the BTS Block command from Flexi EDGE BTS Manager:

BTS Object state at Flexi EDGE BTS Manager (by viewing the BTS object (sector) properties in the Base Station View)

Check the TRXSIG of all the TRXs (by viewing the TRX Object properties in the Base Station View)

Check the EXxA LED colour at EXxA Units and at Flexi EDGE BTS Manager.

The object state of the BTS object (sector) at Flexi EDGE BTS Manager is Blocked.


The LED colour at EXxA units and at Flexi EDGE BTS Manager is stable yellow.

5 Observe the calls in the blocked sector. The BSC clears all the calls from the TRX(s) concerned and takes appropriate measures to restore traffic at the 60th second of the block command.

6 Observe the calls in the unblocked sectors. The calls are not released.

7 Check the alarms on the BSC using the MML command ZEOL:<bcf_no>;

The following alarm should be present:

7208 ‘Local Block’ for the BTS object (Sector)

8 Check the BCCH transmission using a spectrum analyser.

The BCCH transmission is stopped in the blocked BTS object (sector).

9 Disconnect and reconnect the bus cable of the EXxA unit (to which the ERxA unit is connected) and check the alarms in the alarm window at Flexi EDGE BTS Manager.

Check the alarms on the BSC using the MML command ZEOL:<bcf_no>;

No 7606 or 7603 alarm is displayed.

10 Perform a lock/unlock operation on the blocked BTS object.

Use MML command ZEQS.

On locking the BTS Object, the operational state changes to BL-USR at the BSC.

OnuUnlocking BTS object, the operational state is changed back to BL-BTS.

11 BCCH transmission is checked using spectrum analyser.

The BCCH transmission is not started even momentarily for the BTS object that is locked/unlocked.

12 Check the alarms on the BSC using MML The following alarm should be present:



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output command (ZEOL:<bcf_no>;).

7208 Alarm “Local Block” for BTS object (Sector)

13 Unblock the BTS object (sector) from Flexi EDGE BTS Manager.

Check the alarms in the alarm window at Flexi EDGE BTS Manager-


7208 alarm “Local Block” on BTS Object (sector) has disappeared in the alarm window at Flexi EDGE BTS Manager.

Alarm 7208 “Local Block” on BTS object (sector) is not present in the BSC alarm list.

BTS object (sector) reset is executed.

14 Once the BTS object (sector) reset is completed, check the operational state of the BTS/TRXs object on the BSC (ZEEI:<bcf_no>;)

The operational state of the BCF, BTS and all TRX objects is WO.

15 Observe the ongoing calls. Calls are not released.

2.7.7.3 Local TRX Block/Unblock

This test case verifies that TRX objects can be successfully blocked and unblocked from Flexi EDGE BTS Manager. The BSC clears all the calls from the TRXs concerned and takes appropriate measures to restore traffic at the 60th second of the block command. Also, the LAPD links of the blocked TRXs are released after 60 secs of the TRX block command.






1 Establish MS-to-MS calls on all the TRX objects, in every sector.

Calls are successfully established.

2 Block the both non-BCCH TRX objects (in same EXxA Unit) from Flexi EDGE BTS Manager in the second sector and observe the following within 60 secs of TRX Block command:


DN0749988 Issue 2-0 en 18/01/2008


183 (381)


TRX object state at Flexi EDGE BTS Manager (by viewing the TRX properties in the Base Station View) for both the TRX objects.

TRXSIG of the TRX objects (by viewing the TRX Object properties in the Base Station View).


The object state of the TRX objects at Flexi EDGE BTS Manager is Block Requested…

TRXSIG of the TRX objects is ON.

7208 alarm “Local Block” on TRX objects is present in the Flexi EDGE BTS Manager alarm window.

3 Check the operational state of the TRX objects on the BSC (ZEEI:<bcf_no>; )

The operational state of the TRX objects at BSC is BL-TRX.

4 Observe the following after 60 secs of TRX Block command from Flexi EDGE BTS Manager:

TRX Object state at Flexi EDGE BTS Manager (by viewing the TRX object properties in the Base Station View).

Check the TRXSIG of the blocked TRX objects (by viewing the TRX Object properties in the Base Station View).

Check the LED colour on EXxA (where the TRX objects are blocked) and Flexi EDGE BTS Manager.

The object state of the blocked TRX objects at Flexi EDGE BTS Manager is Blocked.


The LED colour on EXxA and Flexi EDGE BTS Manager is stable yellow.

5 Observe the call on blocked TRX objects. The BSC clears all calls from the blocked TRXs and takes appropriate measures to restore traffic at 60th second of the block command.

6 Observe the calls on working TRX objects. Calls are not released.



7208 alarm “Local Block” for the blocked TRX objects

8 Disconnect and reconnect the bus cable of EXxA unit (where the TRX objects are blocked) and check the alarms in the Alarm window at Flexi EDGE BTS Manager.

Check the alarms on the BSC using MML command (ZEOL:<bcf_no>;)

No 7606/7603/7600 alarm is displayed.

9 Perform a Lock/unlock operation on any of the blocked TRX objects.

Use MML command ZEQS.

On locking the TRX object, the operational state changes to BL-USR at the BSC.

On unlocking the TRX object, the operational state is changed back to BL-TRX.



DN0749988Issue 2-0 en18/01/2008




7208 alarm “Local Block” for the blocked TRX objects

11 Unblock the TRX objects from Flexi EDGE BTS Manager.

Check the alarms in the Alarm window at Flexi EDGE BTS Manager.


7208 alarm “Local Block” on TRX objects has disappeared in the alarm window at Flexi EDGE BTS Manager.

Alarm 7208 “Local Block” on TRX objects is not present on the BSC alarm list.

TRX object reset is executed.

Once the TRX objects reset is completed, check the operational state of the TRX objects on the BSC (ZEEI:<bcf_no>;)

The operational state of the TRX objects is WO.

Observe the ongoing calls. Calls are not released.

2.7.7.4 BCCH Reconfiguration on Local TRX Block

This test case verifies that a BCCH TRX object can be successfully blocked from Flexi EDGE BTS Manager. The BSC reconfigures some other working TRX in the sector as BCCH TRX. Also, the LAPD link of the blocked TRX is released and BCCH transmission is stopped on the TRX after 60 secs of the TRX block command. The BSC clears all the calls from the TRXs concerned and takes appropriate measures to restore traffic at the 60th second of the block command.






1 Establish MS-to-MS call in all the BTS objects (sectors).

Calls are successfully established in all the sectors.

2 Block the BCCH TRX in the second BTS


DN0749988 Issue 2-0 en 18/01/2008


185 (381)

Step Input Expected output object from Flexi EDGE BTS Manager and observe the following within 60 seconds of BTS Block command:

TRX object state at Flexi EDGE BTS Manager (by viewing the TRX properties in the Base Station View).

TRXSIG of the TRX object (by viewing the TRX Object properties in the Base Station View).

Check the alarms in the Alarm window at Flexi EDGE BTS Manager.

The object state of the TRX object at Flexi EDGE BTS Manager is Block Requested…

TRXSIG of the TRX is ON.

7208 alarm “Local Block” on TRX object is present in the Flexi EDGE BTS Manager alarm window.

3 Check the operational state of the BTS object (sector) from the BSC (ZEEI:<bcf_no>; )

The operational state of the TRX object is BL-TRX.

4 Observe following after 60 seconds of the TRX Block command from Flexi EDGE BTS Manager:

TRX object state at Flexi EDGE BTS Manager (by viewing the TRX object properties in the Base Station View)

Check the TRXSIG of the TRXs (by viewing the TRX Object properties in the Base Station View):

Check the EXxA LED colour (where the TRX is blocked) at EXxA Unit and at Flexi EDGE BTS Manager.

The object state of the TRX object at Flexi EDGE BTS Manager is Blocked.

TRXSIG of the blocked TRXs is OFF

The LED colour at EXxA unit and at Flexi EDGE BTS Manager is blinking green.

5 Observe the BCCH reconfiguration status on the BSC using (ZEEI:<bcf_no>;).

BCCH reconfiguration happens and another WO TRX becomes BCCH TRX.

6 Observe the calls on the blocked TRX and the reconfigured BCCH TRX.

BSC clears all calls from the TRX(s) concerned and takes appropriate measures to restore traffic at 60th second of the block command.

7 Observe the calls on unblocked TRXs except the reconfigured BCCH TRX.

Calls are not released.


The following alarms should be present:

7208 alarm “Local Block” for blocked TRX object

7705 “LAPD FAILURE” alarm for the blocked TRX object.


The BCCH transmission is stopped on the blocked TRX object.

The BCCH transmission is started on the



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output reconfigured BCCH TRX object.

10 Unblock the TRX object from Flexi EDGE BTS Manager.


Check the alarms on BSC using MML command (ZEOL:<bcf_no>;).

7208 alarm “Local Block” on TRX Object has disappeared in the alarm window at Flexi EDGE BTS Manager.

Alarm 7208 “Local Block” on TRX object is not present on the BSC alarm list.

TRX object reset is executed.

11 Once the TRX object reset is completed, check the operational state of the BTS/TRXs object on the BSC (ZEEI:<bcf_no>;)

The operational state of the BCF, BTS and all TRX objects is WO.

12 Observe the ongoing calls. Calls are not released.

2.7.7.5 Local BCF Block and Lock/Unlock

This test case verifies that BCF object can be successfully locally blocked from Flexi EDGE BTS Manager. The BSC clears all calls from the TRX(s) concerned and takes appropriate measures to restore traffic at 60th second of the block command. Also, LAPD links of all the TRXs under the BCF are released and BCCH transmission is stopped after 60 secs of the BCF block command. Locking/unlocking of BCF object from BSC can be successfully performed on blocked BCF object.




• Flexi EDGE BTS Manager is connected to the BTS Site via local connection.


1 Establish a mobile-to-mobile call. Call is successfully established.

2 Block the BCF object from Flexi EDGE BTS Manager and observe the following within 60 secs of BCF Block command:

The BCF object state at Flexi EDGE BTS Manager (by viewing the BCF properties in the Base Station View)

TRXSIG of all the TRXs (by viewing the TRX

The object state of the BCF at Flexi EDGE BTS Manager is Block Requested…



DN0749988 Issue 2-0 en 18/01/2008


187 (381)

Step Input Expected output Object properties in the Base Station View)


7208 alarm “Local Block” on BCF object is present in the Flexi EDGE BTS Manager alarm window.

3 Check the operational state of the BCF from the BSC (ZEEI:<bcf_no>; )

The operational state of the BCF/BTS/TRX at the BSC is BL-BCF.

4 Observe the following after 60 secs of BCF Block command from Flexi EDGE BTS Manager:

BCF Object state at Flexi EDGE BTS Manager (by viewing the BCF properties in the Base Station View).

Check the TRXSIG of all the TRXs (by viewing the TRX Object properties in the Base Station View).

Check the EXxA LED colour on EXXA Units and at Flexi EDGE BTS Manager.

The object state of the BCF at Flexi EDGE BTS Manager is Blocked.


The EXxA LED colour on EXxA Units and at Flexi EDGE BTS Manager is stable yellow.

5 Observe the call. BSC clears all calls from the TRX(s) concerned and takes appropriate measures to restore traffic at 60th second of the block command.



7208 Alarm “Local Block” for BCF object


The BCCH transmission is stopped in all the sectors under the BCF.

8 Lock the BCF object from the BSC. Use MML command ZEFS

The operational state of the BCF/BTS/TRX at the BSC is BL-USR.

9 Unlock the BCF object from the BSC. Use MML command ZEFS.



7208 alarm “Local Block” on BCF has disappeared in the alarm window at Flexi EDGE BTS Manager.

Alarm 7208 “Local Block” is not present in the BSC alarm list.

BSC commands a BCF reset. The BCF reset is executed.

10 Once the BCF reset is completed, check the operational state of the BCF/TRXs on the BSC (ZEEI:<bcf_no>;)

The operational state of BCF and all TRX objects is WO.



DN0749988Issue 2-0 en18/01/2008

2.7.8 Forced Handover for O&M Reason

Overview The aim in all operating tasks should be to avoid any disturbance to traffic. The forced handover procedure allows the active calls to be handed over to the unlocked TRX or unlocked sector when an O&M operation requires blocking of a TRX with active calls or the sector with active calls respectively.

Forced handover is available with the commands 'Lock BTS' and 'Lock TRX' as an option. The operator is able to determine the maximum time during which handovers are tried.

With the forced handover procedure, all ongoing calls are handed over to other TRXs of the sector (if only one TRX is cleared from the traffic) or to the neighbouring sectors (if the whole sector is locked).

Scope of testing The following variations are covered for verifying the handover triggered by O&M reasons:

• Locking the TRX with active calls so that the calls are handed over to an unlocked TRX of the same sector.

• Locking the sector with active calls so that the calls are handed over to another unlocked sector.

Settings 1. Create sector-1 and sector-3 as neighbours of sector-2 using the

following commands: >>>ZEAC: BTS=<middle_sector_id>::LAC=<lac_of_sector_1>,CI=<cell_id_of_sector_1>:NCC=<ncc_of_sector_1>,

BCC=<bcc_of_sector_1>,FREQ=<bcch_freq_of_sector_1>;

>>>ZEAC: BTS=<middle_sector_id>::LAC=<lac_of_sector_2>,CI=<cell_id_of_sector_2>:NCC=<ncc_of_sector_2>,

BCC=<bcc_of_sector_2>,FREQ=<bcch_freq_of_sector_2>;

2. Create two neighbour sites for handover in different sites using the following command:

>>>ZEAC:SEG<seg_no_1>::ASEG=<seg_no_2>

where seg_no_2 is the segment on which the calls are to be handed over.


DN0749988 Issue 2-0 en 18/01/2008


189 (381)

Test cases

Pos Name Comment

1 Forced handover of CS call to another BTS object

2+4+2, GSM 1800

2.7.8.1 Forced handover of CS call to another BTS object

The purpose of this test case is to test the handover of the active CS call on another sector when the sector on which the call is ongoing is locked by the administrator.


• 6 test mobiles


• The BTS site should be up and should be in supervisory state.

• Another test site (using any of the standard configurations) is available as a neighbour.

• All the sectors (including the sector in the other test site) are defined as neighbours of each other at the BSC.


1 Establish two CS calls on each of the sectors. The CS calls are established successfully.

2 Lock the sectors of the current site in sequence with the forced handover option.

All the calls from the locked sector are handed over to the unlocked sectors.

3 Observe the RF transmission on the locked sectors using the spectrum analyser.

No RF transmission is seen on the TRXs of the locked sector.

2.7.9 Abis Loop Test

Overview The Abis Loop Tests are supported by Flexi EDGE BTS to check the Abis transmission is setup properly and to trace possible transmission problems in the Abis Interface between Flexi EDGE BTS and the BSC. The test can be performed on free static Abis Speech channel for each TRX and Dynamic Abis Pool sub-timeslots.

Scope of testing



DN0749988Issue 2-0 en18/01/2008

The Abis loop test shall be executed for both Fixed Speech channel and Dynamic Abis configuration with zero and non-zero transmission delay path.

Loop test will be executed via each supported interface type - E1/T1/Flexbus and multiple interfaces.

The Abis loop test shall be run for all the TRX in the BTS simultaneously.

Configuration For Abis configuration, refer to the table below.

Item Details

Abis Interface Configuration

For Interface type E1 and T1

The signaling and traffic channels distributed over multiple Interfaces

For Interface type Flexbus

A protected loop configuration is made between multiple sites

Test cases

Pos Name Comment

1 Abis Loop Test For Fixed Abis Configuration

8+8+8, FIEA


4+4+4, FIPA, T1


4+4+4, FIFA

4 Abis Loop Test For Dynamic Abis Configuration

8+8+8, FIEA, Separate 12 Abis TS EDAP per sector

5 Abis Loop Test With Delay in Abis link 4+4+4, FIPA, E1

2.7.9.1 Abis Loop Test for Fixed Abis Configuration The objective of the test case is to verify that the Abis Loop Tests for a fixed Abis configuration can be executed successfully from the BSC. The loop test shall be executed for all the TRXs of the base station and for all the timeslots in each TRX.

Test case execution


DN0749988 Issue 2-0 en 18/01/2008


191 (381)

The test case shall be executed for different types of interfaces as defined in the test case comments.

Pre-setup:

• GPRS and EGPRS are enabled on all the sectors. There are a few RTSLs in each sector that have synchronisation established with the PCU (that is, timeslots with channel status = 'GP').



DN0749988Issue 2-0 en18/01/2008


1 Establish 1 MS-MS CS call, in each sector. Verify that the calls are successfully established.

2 Start Abis loop test command from the BSC for sector 1 with MML command ‘ZUBK’. Specify only default values for the loop test parameters.

Note: Default value for TRX number is 'ALL' TRXs and the default value for timeslot is 'ALL' timeslots.

Observe the output for the MML command on the BSC: 'TRX-(Number)..... TESTING STARTED COMMAND EXECUTED'

This output is seen for all the TRXs in the sector'.

3 Wait until the test period is over and invoke the Abis Loop Test Report for sector-1 through MML command 'ZUBP'.

Abis Loop Test is successful and its report is displayed on the BSC as follows. -

For each idle traffic timeslot on all TRXs, the individual test result status with the FER,BER values shall be displayed.

RESULT: Passed

FER:0

BER:0

Abis TSL

For control channels, the test result shall say:

INCONCLUSIVE IN USE - REASON: TESTING OF CONTROL CHANNEL NOT ALLOWED

For GPRS timeslots (timeslots with channel status = 'GP') and for timeslots being used for CS calls, the test result shall say:

INCONCLUSIVE IN USE, REASON: CIRCUIT NOT FREE

4 For the duration of the test, capture the traffic on the Abis analyser, for timeslots that have synchronisation established with the PCU (timeslots with channel status = 'GP').

Verify using the Abis analyser logs for all such timeslots that the PCU synchronisation is not lost and remains intact for the entire duration of the test.

5 Observe the voice quality of all the CS calls in all sectors, for the duration of the test.

Verify that there is no perceptible degradation in voice quality, while the loop test is running.

6 Verify the status of all TRXs and traffic timeslots in sector 1 using MML command ‘ZERO’.

The MML command execution output for TRX1 displays:

‘Adm’ state as ‘Unlocked’

‘Opr State’ as ‘WO’.

Radio time slot displays


DN0749988 Issue 2-0 en 18/01/2008


193 (381)


‘Adm.State’ as ‘Unlocked’,

’Opr.State’as ‘WO’

‘Ch.Status’ as ‘Idle'.

7 Also observe the state of all timeslots in sector-1 as shown in the "Tests Traffic_Trace" on the Flexi EDGE BTS Manager.

The status of all idle traffic timeslots is shown as "IDLE".

No radio timeslot has the status "Reserved For Testing".

8 Repeat steps 2-7 for Sector 2 and Sector 3 Verify the results as given in steps 2-7 for Sector 2 and Sector 3.

9 Establish 1 pair of CS calls again, in each sector.


2.7.9.2 Abis Loop Test for Dynamic Abis Configuration

The purpose of the test case is to verify that the Abis Loop Tests for EDAP timeslots can be executed successfully from the BSC for dynamic Abis configuration.


• GPRS and EGPRS are enabled in all the sectors. All the TRXs are also GPRS enabled. There are a few RTSLs in each sector that have synchronisation established with the PCU (that is, timeslots with channel status = 'GP')

• All the TRXs are in supervisory state.


1 Establish 1 MS-MS CS call and 1 packet data transfer, in each sector.

Note: A file of size 5MB (approx.) should be used for transfer to ensure that the data transfer continues for the entire duration of the test.

Verify that the CS calls get established and the packet data transfers also start successfully.

2 Start Abis loop test from the BSC on an EDAP timeslot on a TRX in sector 1 through MML command ‘ZUBK’. Specify only default values for the loop test parameters.

Note: Default value for Sub-timeslot is 'ALL'.

Observe the output for the MML command on the BSC:

'TRX-(NUMBER) ..... TESTING STARTED COMMAND EXECUTED'

3 Wait until the test period is over and invoke the Abis Loop Test Report with MML

For each sub-timeslot of the DAP timeslot under test, the indivitual test result status



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output command 'ZUBP'.

with the FER,BER values shall be displayed.

RESULT: Passed

FER:0

BER:0

4 Observe the voice quality of all the CS calls, for the duration of the test.


5 Observe the packet data transfers in each of the 3 sectors.

Verify that the packet data transfer continue without any disturbance or degradation in the throughput.

6 Verify the status of TRX and radio time slots on which the EDAP Loop Test was carried out using MML command ‘ZERO’.

The MML command execution output for TRX on which the loop test was run, displays:

‘ADM.STATE’ as ‘UNLOCKED’

‘OP.STATE’ as ‘WO’.

Radio time slot displays

‘ADM.STATE’ as ‘UNLOCKED’,

’OP.STATE’ as ‘WO’

‘Ch.Status’ as ‘IDLE’.

7 Also observe the state of the RTSL as shown in the "Tests->Traffic_Trace" on the Flexi EDGE BTS Manager.

The status of the RTSL used for running the test is now shown as "IDLE".

No radio timeslot has the status "Reserved For Testing".

2.7.9.3 Abis Loop Test With Delay in Abis link

The objective of the test case is to verify that the Abis Loop Tests for a fixed Abis Configuration can be executed successfully when a delay is introduced in the Abis link.


• Data channel simulator Test case execution Pre-setup:

• GPRS and EGPRS are enabled on all the sectors. There are a few RTSLs in each sector that have synchronisation established with the PCU i.e (that is, timeslots with channel status = 'GP').


DN0749988 Issue 2-0 en 18/01/2008


195 (381)

• A data channel simulator is connected on the Abis link, and a delay of 3-5 miliseconds is introduced on the Abis link in each of the directions.


1 Establish 1 MS-MS CS call, in each sector. Verify that the calls are successfully established.

2 Start Abis loop test command from the BSC on sector 1 with MML command ‘ZUBK’. Specify only default values for the loop test parameters.

Note: Default value for TRX number is 'ALL' TRXs and the default value for timeslot is 'ALL' timeslots.

Observe the output for the MML command on the BSC:

'TRX-(Number)..... TESTING STARTED COMMAND EXECUTED'

This output is seen for all the TRXs in sector 1.

3 Wait until the test period is over and invoke the Abis Loop Test Report for sector-1 in the BTS site through MML command 'ZUBP'.

Abis Loop Test is successful and its report is displayed on the BSC as follows:

For each idle traffic timeslot on all TRXs, the individual test result status with the FER,BER values shall be displayed.

RESULT: Passed

FER:0

BER:0

Abis TSL

For control channels, the test result shall say:

INCONCLUSIVE IN USE - REASON: TESTING OF CONTROL CHANNEL NOT ALLOWED

For GPRS timeslots (i.e. timeslots with channel status = 'GP') and for timeslots being used for CS calls, the test result shall say:

INCONCLUSIVE IN USE, REASON: CIRCUIT NOT FREE

4 For the duration of the test, capture the traffic on the Abis analyser, for timeslots that have synchronization established with the PCU (i.e. timeslots with channel status = 'GP').

Verify using the Abis analyser logs, for all such timeslots, that the PCU synchronisation is not lost and remains intact for the entire duration of the test.

5 Observe the voice quality of all the CS calls, for the duration of the test.


6 Verify the status of all TRXs and traffic timeslots using MML command ‘ZERO’.

The MML command execution output for TRXs in sector 1, displays:



DN0749988Issue 2-0 en18/01/2008


‘Adm’ state as ‘Unlocked’

‘Opr State’ as ‘WO’.

Radio time slots display

‘Adm.State’ as ‘Unlocked’,

’Opr.State’as ‘WO’

‘Ch.Status’ as ‘Idle'.

7 Also observe the state of all timeslots as shown in the "Tests->Traffic_Trace" on the Flexi EDGE BTS Manager.

The status of all idle traffic timeslots is shown as "IDLE". No radio timeslot has the status "Reserved For Testing".

2.7.10 RX Antenna Supervision by Comparing RSSI

Overview This software product provides long terms continuous antenna supervision for the BTS which has receive Main and Diversity antennas. Since the measurement is done on a per TRX level using RSSI samples from both receivers, then any fault in RX paths module or cables from antenna to EXxA TRX module port will detected.

Scope of testing This test plan verifies the:

• Rx Antenna supervision by comparing RSSI with ECxx RTC module.

• Rx Antenna supervision by comparing RSSI with ERxx DDU module.

• Changing of values for number of samples required for RSSI monitoring.

• Fetching of raw RSSI values.

Configuration Configuration from the top level plan as indicated in the test case comment.

Settings 1. The RSSI difference threshold parameter (RXDL) is set to the

default value (10dB)


DN0749988 Issue 2-0 en 18/01/2008


197 (381)

Test cases

Pos Name Comment

1 RX antenna supervision by comparing RSSI

12 omni RTC combining, BB Hopping, Attenuation in Antenna A


6+6, RTC combining, BB Hopping, Attenuation in Antenna B


EP1 site Upgraded to EP1.1, 8-Omni, 4 Way combining, RF Hopping, Attenuation in Antenna A


4+4, By pass, No hopping, Attenuation in Antenna A of First ERxA Dual Duplexer Module,


8+8, 2 Way combining, Antenna Hopping , Attenuation in Antenna Bof first ERxA Dual Duplexer Module

6 Settable Rx Samples for RSSI Measurements

4+4, By pass, No hopping, Attenuation in Antenna A of Second ERxA Dual Duplexer Module

2.7.10.1 RX antenna supervision by comparing RSSI

The objective of this test case is to verify that in configurations having receive-path diversity, if an antenna becomes faulty, then the BTS automatically detects and reports this condition to the BSC. The test case also verifies that:

• Rx Antenna Supervision works correctly under varied traffic conditions

• If the fault is rectified, this is automatically detected and reported by the BTS to the BSC

• The default value for RSSI sample limit is set to 160000.



• RF Shielding Box



DN0749988Issue 2-0 en18/01/2008



• All the time slots in one TRX are reserved for the packet data traffic.

• Intra-cell handover is enabled in the BSC.

• The variable attenuator is connected to the antenna port under test (as in the test case comment) in the ECxx RTC/ERxx DDU module


1 Establish long duration static CS voice calls calls. Number of calls established should be enough to generate valid RSSI samples.

Establish repetitive packet data transfers on multiple time slots in the TRX reserved for packet data traffic.



Packet data transfers are ongoing on multiple time slots in the TRX reserved for packet data.

2 Check for 1 hour for alarms at Flexi EDGE BTS Manager and the BSC, and RSSI values at Flexi EDGE BTS Manager.

No alarms are present at Flexi EDGE BTS Manager or the BSC.

The Newest and Reliable values for each RX port on each TRX are nearly the same value (+/-2).

3 Using the variable attentuator, induce an attenuation of 20dB (higher than the default threshold set at BSC) on the path to the antenna under test.

After 1 hour, use Flexi EDGE BTS Manager to observe the difference between the Main and Diversity signal strengths reported for all the TRXs.

Attenuation of 20dB is introduced on the path of antenna under test.

For some TRXs (Note1), the difference between the reliable RSSI values for the Main and Diversity paths is seen to be greater than the threshold.

For the TRX in which packet data transfer are ongoing, the difference between the reliable RSSI values for the Main and Diversity paths is seen to be greater than the threshold.

4 Observe the alarms at Flexi EDGE BTS Manager and the BSC.

The 7607 alarm "RSSI detected Rx signal difference exceeding threshold" is reported at Flexi EDGE BTS Manager and the BSC for all TRXs which have reliable Main and Diversity path RSSI difference exceeding threshold.

5 After 1 hour check for any alarms at Flexi EDGE BTS Manager and the BSC.

The 7607 alarm "RSSI detected Rx signal difference exceeding threshold" is reported at Flexi EDGE BTS Manager and the BSC for all TRXs which have reliable Main and


DN0749988 Issue 2-0 en 18/01/2008


199 (381)


Upload and save the Site Information Report from Flexi EDGE BTS Manager.

Diversity path RSSI difference exceeding threshold.

The content of the Site Information report shows the same values for Newest / Reliable as seen from Flexi EDGE BTS Manager views.

6 Readjust the variable attenuator to reduce the attenuation to around 5 dB (below the threshold set at the BSC).

After 1 hour, use Flexi EDGE BTS Manager to observe the difference between the Main and Diversity signal strengths reported for all the TRXs.

The attenuation is set to 5dB.

The difference between the Main and Diversity signal strengths reported for all the TRXs is less than the threshold set at the BSC.

7 Observe the alarms at Flexi EDGE BTS Manager and the BSC.

The alarms reported in step 5 are cancelled.

No active alarms are seen.

8 Release all the ongoing calls. All the ongoing calls are released.

9 Using variable attenuator, induce an attenuation of 20dB (higher than the default threshold set at the BSC) on the path to the antenna under test.

Attenuation of 20dB is introduced on the path of antenna under test.

10 For atleast 2 hours, observe the alarms at Flexi EDGE BTS Manager and the BSC when there is no traffic on the site.

Upload and save the Site Information Report from Flexi EDGE BTS Manager.

In this case, no alarms are reported.

From the Site Information Report, the Newest values show that not enough samples are/were available. The Reliable values show the same values and time stamp as seen from step 6.

Sample limit value in commissionig data is default value of 160000

2.7.10.2 Settable Rx Samples for RSSI Measurements

The objective of this test case is to verify that in configurations having receive-path diversity, Rx Antenna Supervision works correctly under varied traffic conditions and different RSSI sample values. Verify that if no value is given for RSSI samples during commissioning default value for RSSI samples is set to 160000 and can be changed.



• RF Shielding Box



DN0749988Issue 2-0 en18/01/2008


Flexi EDGE BTS Manager is connected to the Flexi EDGE BTS.

RSSI sample limit is not specified during commissioning.


1 Fetch the commissioning Report and SIR from Flexi EDGE BTS Manager.

RSSI value should be 160000 in SIR and commissioning report.

2 Set the RSSI sample value to new value of 350,000 using Flexi EDGE BTS Manager.

RSSI sample value is set successfully.

3 Establish long duration static CS speech calls.

Number of calls to be established should be enough to generate RSSI samples greater than RSSI sample limit as specified in test step 2.



4 Fetch RSSI comparison values from Flexi EDGE BTS Manager after 10 minutes.

Raw RSSI values are displayed for all the TRXs.

5 Fetch SIR report by clicking on "Site information Report " in the Supervision Menu at the Flexi EDGE BTS Manager.

Verify that the Raw RSSI sample values are displayed in the RSSI_Measurement_Reports in the SIR.



The Newest and Reliable values for each RX port on each TRX are nearly same value (+/-2).

7 Release all calls established in step 3. All calls are successfully released.

8 Establish long duration static CS speech calls.

A number of calls should be established to generate RSSI samples between default RSSI limit and set RSSI limit in step 2.



9 Fetch RSSI comparison values from Flexi EDGE BTS Manager after 10 minutes.

Raw RSSI values are displayed for all the TRXs.



Only the newest values for each RX port on each TRX are nearly same value (+/-2).

Reliable values remain the same as in step 6.


DN0749988 Issue 2-0 en 18/01/2008


201 (381)

2.7.11 Remote Flexi EDGE BTS Manager

Overview The Base Transceiver Station (BTS) equipment can be controlled locally at the site by the user with the Flexi EDGE BTS Manager. To minimise the need for site visits, it is necessary that the Flexi EDGE BTS Manager functions are also accessible remotely.

The Flexi EDGE BTS Manager feature enables monitoring and testing of the BTS remotely, by connecting to the BTS through NetAct. The remote Flexi EDGE BTS Manager supports all the features available via a local connection (except the initial commissioning procedures necessary to establish the OMUSIG links).

Scope of testing The scope of testing is to perform operations on different BTS SW (EP1.1 and EP1 CD1.0) from remotely connected Flexi EDGE BTS Manager EP1.1.

Settings Test environment for Remote BTS Manager:

• The remote Flexi EDGE BTS Manager application should be run after dialling into a WAS server. The WAS server can be accessed using a Citrix client application.

• The Flexi EDGE BTS Manager application is installed in the WAS server and can be run from the WAS server.

Test cases

Pos Name Comment

1 Successful connection of Flexi EDGE BTS Manager via NetAct and display of BTS views

BTS SW EP1.1

2 Successful fetch of Site Information Report (SIR) from remotely connected Flexi EDGE BTS Manager

BTS SW EP1.1


BTS SW EP1 CD1.0

4 Successful fetch of B2 cross-connection (32k/16k/8k) from remote Flexi EDGE BTS Manager

BTS SW EP1.1

5 Successful execution of TRX test from Flexi EDGE BTS Manager connected remotely

BTS SW EP1.1

6 Successful launch of FlexiHub Manager -



DN0749988Issue 2-0 en18/01/2008

Pos Name Comment from remotely connected Flexi EDGE BTS Manager

2.7.11.1 Successful connection of Flexi EDGE BTS Manager via NetAct and display of BTS views

This test case verifies the following:

• Flexi EDGE BTS Manager displays the option to connect remotely. Upon filling the correct connection parameters, the remote connection is successfully established.

• When the Flexi EDGE BTS Manager remote connection is attempting and Flexi EDGE BTS Manager is disconnected, then Flexi EDGE BTS Manager gets disconnected in between and does not hang the application.


• NetAct Server with Node Server/ WAS server

Software tools:

• NetAct server connection for remote Flexi EDGE BTS Manager connectivity


• The BTS is commissioned and in supervisory state.

• There are no unexpected active alarms for the BTS.

• No Flexi EDGE BTS Manager is connected to the BTS, either locally at LMP or through a remote connection.


1 From Flexi EDGE BTS Manager, open the Connection Menu.

Connection Menu opened. Flexi EDGE BTS Manager displays an option to connect to the BTS remotely or locally.

2 Click "Connect Remotely” to connect remotely to the BTS Site.

“Remote Connection” dialog opens for the user.

3 Specify the following parameters

BSC Username and password.

IP Address of NetAct Server

BSC ID (ID of BSC to which BTS is connected).

Events View shows that the Flexi EDGE BTS Manager is attempting connection with the BTS.

Flexi EDGE BTS Manager goes into "Flexi EDGE BTS Manager Connected Remotely" state as viewed on the status bar.


DN0749988 Issue 2-0 en 18/01/2008


203 (381)


BCF ID

Click the “Connect” button.

The alarm view displays the alarm “7801-MMI CONNECTED TO BASE STATION”

4 Click on the “Alarm History” button on the alarm view.

After some time the Flexi Edge BTS Manager alarm window displays the recent history of alarms.

5 Save Alarm History by clicking the Save button.

“Save alarm” dialog box is displayed. Give the file name and click Save.

Open the xml file and verify all alarm details are same as seen from Flexi EDGE BTS Manager views.

6 Select the menu option "Supervision -> RSSI Comparison values” to navigate to RSSI comparison values screen.

After some time, the screen shows the RSSI comparison values.

7 Select HW modules ESMA and EXxx1. The properties of the HW modules are displayed in properties view.

8 Select logical modules BCF and logical TRX. The properties of the logical modules are displayed in properties view.

9 Disconnect the Remote BTS Manager session.

“7801-MMI CONNECTED TO BASE STATION alarm is cancelled, as seen at BSC using ZEOL MML command.

Remote BTS Manager session is disconnected successfully.

10 Now, repeat steps 2, 3 but soon after clicking on 'Connect' button, click on 'Disconnect' button.

Remote BTS Manager application does not hang and is disconnected successfully.

2.7.11.2 Successful fetch of Site Information Report (SIR) from remotely connected Flexi EDGE BTS Manager

This test case verifies that Flexi EDGE BTS Manager displays an option to obtain the SIR (Site Information Report) from the remotely connected BTS site. The following information will be contained in the site information report:

• The current SCF from the BTS

• The configuration parameters of BTS_CONF_DATA

• The commissioning report from the BTS

• The current Traffic trace information

• The current HW, SW version report of the BTS



DN0749988Issue 2-0 en18/01/2008

• The current logical object properties information of the BTS

• All alarms, including the real and raw alarm history (start, cancel, transient), and the latest alarm diagnostic report

• Transmission configuration settings

• The TRE poll list information received from the BSC.



• LMU

Software tools:




• No Flexi EDGE BTS Manager is connected to the BTS, either locally at LMP or through remote connection.

• The LMU is connected to the BTS site as a Q1 device and the same is configured at the BSC using the ZQWA MML command.






3 Specify the following parameters




BCF ID

Click on “Connect” button

Events View shows that the Flexi EDGE BTS Manager is attempting connection with the BTS.

Flexi EDGE BTS Manager goes into "Flexi EDGE BTS Manager Connected Remotely" state as viewed on the status bar.

4 From Flexi EDGE BTS Manager, click on the option to Fetch SIR using menu option: “Supervision -> Site Information…”

Events Window shows that Flexi EDGE BTS Manager has sent a request to the BTS to fetch the SIR.

5 View the SIR. The SIR is an XML file.


DN0749988 Issue 2-0 en 18/01/2008


205 (381)


It contains all the Information types as specidied in Description of this test case.

The SIR is human readable.

The information contained in the SIR is correct and consistent (for example, SCF is verified by fetching the SCF from the BTS using the "Fetch SCF from BTS" option and then checking for the contents, and the corresponding field in the SIR.

Same with Commissioing Report. BTS_CONF_DATA is verified from the traces on GSM Abis Analyser.

Current Hardware information is verified by verifying from the Hardware itself.

Logical objects are as defined on the BSC.

BTS Site alarms can be verified on the BSC by issuing the ZEOH command.

Transmission Configuration settings can be verified from Transmission view of BTS Manager and TRE poll list can be verified from the GSM Abis Analyser traces of BTS startup.

6 Save the SIR in the form of XML file by clicking Save and specify the path (such as c:/mylogs/SIR.xml)

Verify that Remarks can also be provided optionally while saving the SIR.

Click to save the SIR.

Open the SIR from the saved path.

SIR is saved in the specified path with same name which was specified during its saving.

The SIR is saved as an XML file.

SIR can be launched correctly. Saved SIR file contains all the information in step 5, and is readable.

2.7.11.3 Successful fetch of B2 cross-connection (32k/16k/8k) from remote Flexi EDGE BTS Manager

This test case verifies that B2 cross-connection (32k/16k/8k) can be read and configured from a remotely connected Flexi EDGE BTS Manager.



Software tools:



DN0749988Issue 2-0 en18/01/2008


Configuration

Item Details

Site configuration Configuration 10:

BCF 1: 2 (900) + 2 (900), Flexi EDGE BTS



Note: 2 E1/T1 Links connected to BCF 1 and then cross-connected to BCF 2 and 3.

Pre-setup:

• 2 E1/T1 links connected to the ESMA System Module.

• The BTS sites are commissioned and in supervisory state.


1 Establish a remote Flexi EDGE BTS Manager connection to BCF 1.

The Flexi EDGE BTS Manager connection is established successfully.

2 From Flexi EDGE BTS Manager, go to inactive-bank cross-connection view:

Transmission -> Cross-connection

Flexi EDGE BTS Manager sends the fetch request for the configuration and a popup message is displayed to the user.

After the fetch of information is complete, the cross-connection information is displayed.

Verify that the presented data is correct and accurate.

3 Disconnect Flexi EDGE BTS Manager from BCF 1 and then connect to BCF 2 and repeat step 2.

The connection is disconnected from BCF 1 and then established to BCF 2.

The cross-connection from BCF 2 is correctly fetched and the cross-connect data is correct.

4 Disconnect Flexi EDGE BTS Manager BCF 2 and then connect to BCF 3 and repeat step 2.

The connection is disconnected from BCF 2 and then established to BCF 3.

The cross-connection from BCF 3 is correctly fetched and the cross-connect data is correct.


DN0749988 Issue 2-0 en 18/01/2008


207 (381)

2.7.11.4 Successful execution of TRX test from Flexi EDGE BTS Manager connected remotely

This test case verifies the successful execution of the loop test from the remotely connected Flexi EDGE BTS Manager.






• Flexi EDGE BTS Manager is connected remotely to the BTS.


1 Navigate to Loop test screen using the menu option ‘TRX Test’

The TRX test screen is displayed.

2 Start a TRX test with the following parameters:

TRX object 1

TS 3

GMSK

Verify that alarm 7615 ‘Radio TS is in test use’ is raised for blocking TSs and reported to Flexi EDGE BTS Manager and the BSC. Then cancel when the test execution is completed.

3 Verify the TRX test result. Verify that the TRX test report for TS 3 is 'PASSED' and a loop test report is available at Flexi EDGE BTS Manager.

4 Repeat the TRX test on a different TRX, TS and modulation (GMSK / 8PSK).

Each TRX test request and result is successful, as defined in steps 2 and 3.

2.7.11.5 Successful launch of FlexiHub Manager from remotely connected Flexi EDGE BTS Manager

This test case verifies a successful launch of FlexiHub Manager from the remotely connected Flexi EDGE BTS Manager.





DN0749988Issue 2-0 en18/01/2008






1 Invoke FlexiHub Manager by selecting the ‘Launch FlexiHub Manager’ menu item in the Flexi EDGE BTS Manager ‘Transmission’ menu.

FlexiHub Manager is launched and is ready for user operation.

2.7.12 Modification of BCF Parameters by Append Commissioning

Overview With Append Commissioning, It is possible to modify BTS commissioning parameters from local/remote Flexi EDGE BTS Manager when the BTS is in fully commissioned state. For this SCF file with "append" as attribute is needed to be downloaded to BTS. BTS on receiving SCF file with "append" attribute compares old and new commissioning information. It applies the changes and does not touch the unchanged information.

The effect of taking into use new parameters from a traffic perspective will be localised to only those objects which are changed.

Scope of testing The scope of testing is to verify that the commissioning of a previously commissioned BTS can be done from a remotely connected Flexi EDGE BTS Manager.

Test cases

Pos Name Comment

1 Upload of SCF from remotely connected Flexi EDGE BTS Manager

Use EP1.1 Flexi EDGE BTS Manager.

2 Append commissioning from remotely connected Flexi EDGE BTS Manager

Site commissioned in EP1 time frame, now running on EP1.1 SW release. Use EP.1 Flexi EDGE BTS Manager for remote connectivity.


DN0749988 Issue 2-0 en 18/01/2008


209 (381)

2.7.12.1 Upload Of SCF from remotely connected Flexi EDGE BTS Manager

The test case aims to verify that the SCF can be successfully fetched from the BTS using a remote Flexi EDGE BTS Manager connection.








1 Place a pair of CS calls at the BTS. The call is placed successfully.

2 Using the remote Flexi EDGE BTS Manager, the SCF is fetched from the BTS.

Go to Commissioning Fetch SCF from BTS.

The SCF is received successfully from the BTS.

The SCF is displayed on the Flexi EDGE BTS Manager screen.

3 The SCF is observed on the Flexi EDGE BTS Manager screen.

The contents of the SCF are verified to be the same as the configuration of the BTS.

4 Save the SCF on the local disk from where the remote Flexi EDGE BTS Manager is run.

The SCF is saved to the chosen location.

5 Verify the status of CS call started in step 1. The CS call is still ongoing.

2.7.12.2 Append commissioning from remotely connected Flexi EDGE BTS Manager

The commissioning parameters of an already commissioned BTS can be modified using a SCF in Append mode. This test case aims to verify that the SCF in Append mode can be successfully handled by a BTS in supervisory state by taking the modified parameters into account and leaving the unchanged parameters unaffected.

Change of BCF ID using append commissioning when BCF is changed at BSC does not have any impact on the BTS site is checked here.



DN0749988Issue 2-0 en18/01/2008




• The BTS is initially commissioned and in supervisory state.




1 Lock the current BCF object from the BSC. The BCF is locked successfully. All TRX objects and BTS objects have operational state as"BL-BCF".

2 Change the Abis termination on the BSC. (Same or different BSC). The new BCF should have the same transmission parameters and hardware configuration.

Abis termination is changed successfully.

3 Unlock the new BCF object from the BSC. The site undergoes a reset and the BCF object and all the TRX objects come to supervisory state and have operational state "WO".

4 Check on Flexi EDGE BTS Manager. All TRX objects have operational state "supervisory".

Alarm 7601 with text "Commissioning failed due to BCF ID mismatch between commissioning file and BSC" is reported in the alarm window.

5 Navigate to Commissioning Wizard by using menu option "Commissioning Wizard",

Choose the "Change settings manually" radio button.

The Commissioning Wizard screen is displayed.

6 Click on "Next" button to navigate to "Site Specific Information".

Change the BCF ID to the new BCF ID.

"Site Specific Information" screen is displayed and the BCF ID is changed successfully.

7 Click on "Next" button to navigate to "Hardware Configuration".

Select "Do not change settings" radio button.

"Hardware Configuration" screen is displayed.

The radio button is selected successfully.

8 Click on "Next" button to navigate to "Transmission Parameters". Select "Do not change settings" radio button.

"Transmission Parameters" screen is displayed.


DN0749988 Issue 2-0 en 18/01/2008


211 (381)


The radio button is selected successfully.

9 Click on "SCF Preview" button. The SCF preview is displayed with the changed value for BCF ID.

10 Click on "Send SCF" button, pop-up for BCF reset is observed. Select the reset option.

The site undergoes a reset and comes to supervisory state.

11 Check on Flexi EDGE BTS Manager. All TRXs have operational state "Supervisory".

No unexpected alarms are shown in the alarm window.

2.7.13 BTS Object Control

Overview The BTS and its units can be reset locally or remotely with Flexi EDGE BTS Manager or their administrative states can be changed from the BSC.

Scope of testing The scope of the test plan is to test the reset of the BTS and its Logical Objects (BCF, BTS and TRX) from Flexi EDGE BTS Manager. Then change in administrative state (from locked to unlocked) from the BSC. The reset of the TRX HW Module is tested from Flexi EDGE BTS Manager. Additionally, the recovery of a sector when the EXxx TRX module carrying the BCCH TRX or the EXxx TRX module controlling the DDU is reset.

Test cases

Pos Name Comment

1 BTS Logical Object Reset from Flexi EDGE BTS Manager

2 + 4 + 2, RF Hopping

2 BTS and TRX Object Administrative State Change from BSC

6 + 6, RTC, Non Hopping

3 BTS and TRX Object Administrative State Change from BSC

3 + 3 + 3 cost optimised, RF Hopping

4 BTS Site Reset from Flexi EDGE BTS Manager

6 + 6, Non Hopping

5 BTS Site Reset from Flexi EDGE BTS Manager

8+8+8, 4-Way combining BB Hopping



DN0749988Issue 2-0 en18/01/2008

Pos Name Comment

6 BCF Object reset from Flexi EDGE BTS Manager with bypass traffic unaffected

6 + 6 + 6, RTC, BB Hopping

7 BCF Object Admin State Change from BSC with bypass traffic unaffected

2 BCFs in Abis chain

8 Alarm Reporting after Object Administrative State Change from BSC

2 BCFs in Abis chain

9 BTS Object Behaviour When EXxx TRX Module Controlling ERxx DDU Module is HW Reset

2 + 4 + 2, RF Hopping

10 BTS Object Recovery when EXxx TRX Module carrying BCCH TRX is HW Reset

3 + 3 + 3, Cost optimised, RF Hopping

11 BTS Logical Object Reset from Flexi EDGE BTS Manager

6 + 6, BB hopping

2.7.13.1 BTS Logical Object Reset from Flexi EDGE BTS Manager

The logical objects BTS and TRX can be reset using Flexi EDGE BTS Manager. The purpose of this test case is to reset the logical objects and then check that the logical objects come to working state.



• The target BTS site is in supervisory state.


1 Place calls on all sectors of the BCF. Calls are successfully placed in the TRXs.

2 From the Base Station View of Flexi EDGE BTS Manager, select any TRX object and click on the reset button on the properties pane.

Observe the TRX object state just after this.

Object state changes from enabled to ‘reset requested’.

All other TRXs in BCF remains in working state and calls

3 Observe the TRX object in Flexi EDGE BTS Manager after reset.

Observe the EXxx TRX module LED states.

Operation state changes to supervisory.

The LED state is stable green.

4 Place calls on the TRX object. Calls are placed successfully on the TRX object.

5 Repeat step 2-4 for each and every of the TRXs present in the BCF in random order.

Same observations as step 2-4.

6 From the Base Station View of Flexi EDGE BTS Manager, select BCF Object.

BTS Object Properties shows:


DN0749988 Issue 2-0 en 18/01/2008


213 (381)


From the logical view select any BTS object. Network type

Object State Enabled

Included TRX Objects

7 Click on the reset button and select option without RF cable auto detection.

Observe the BTS object state just after reset.

The sector object state changes to reset requested.

8 Observe all the TRX objects which belong to this BTS object.

All TRX objects are reset and they come back to supervisory state.

9 Observe the BTS object properties after all TRXs are in the supervisory state.

Object state of sector changes to Enabled.

10 Place calls on the TRX objects belonging to this BTS object.

Calls are placed successfully.

11 Repeat steps 6-10 for each of the BTS objects in the BCF object.

Same observations as steps 6-10.

2.7.13.2 BTS and TRX Object Administrative State Change from the BSC

The administrative states for logical objects BTS or TRX can be changed from the BSC (locked). The purpose of this test case is to verify the changed administrative states of the logical objects. Also check the logical objects comes to working state after unlock.



• There are no active alarms reported to the BSC as can be verified from the MML command ZEOL:<bcf_id>;


1 Place calls on the TRXs belonging to the BCF object.

Calls are successfully placed on TRXs belonging to the BCF object.

2 From the BSC, lock any TRX object using MML command ZERS:BTS=<bts_id>,TRX=<trx_id>:L;

Observe the EXxx TRX module LED.

The object state changes from enabled to ‘locked’.

The EXxx TRX module LED state changes from stable green to blinking green.

3 Unlock the TRX object by running MML command ZERS:BTS=<bts_id>,TRX=<trx_id>:U;

Observe the EXxx TRX module LED after

The TRX object gets a logical reset.

The LED state changes from blinking green to stable green.



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output TRX object reset.

4 Observe the TRX object state in Flexi EDGE BTS Manager.

The operation state changes to supervisory.

5 Place calls on the TRX object after reset. Calls are successfully placed on the TRX object.

6 Repeat steps 2-4 for all the TRXs in the BCF object in random order.

Same observation as in steps 2-4.

7 From the BSC, lock any BTS object using MML command ZEQS:BTS=<bts_id>:L;

Check the state of the BCF using MML command ZEEI:BCF=<bcf_id>;

The state of the BTS and all the sectors is displayed as BL-USR.

8 Check the object states of the TRXs from the Flexi EDGE BTS Manager.

Check the LED states of each of the EXxx TRX modules in the sector.

The object states of all the TRX belonging to the BTS object are locked.

The LED states of all the EXxx TRX modules in the sector are stable yellow.

9 Unlock the BTS object by running MML command ZEQS:BTS=<bts_id>:U;

All TRXs belonging to BTS object are reset.

10 Observe the object states for the TRXs belonging to the BTS object from Flexi EDGE BTS Manager after reset.

Object states for each of the TRXs belonging to BTS object changes to enabled.

11 Place calls on the TRX objects belonging to the BTS object after reset.

Calls are successfully placed.

12 Repeat steps 7-11 for all the BTS objects belonging to the BCF object in random order.

Same observation as in steps 7-11.

2.7.13.3 BTS Site Reset from Flexi EDGE BTS Manager

The purpose of this test case is to reset the BCF object and then check that the logical objects (BCF, BTS and TRX) come to working state after the reset.




• All the TRXs are in supervisory state.



DN0749988 Issue 2-0 en 18/01/2008


215 (381)


1 From the Base Station View of Flexi EDGE BTS Manager, select aBCF Object and click the reset button and select the option without RF cable auto-detection.

A popup window at Flexi EDGE BTS Manager shows graceful disconnection from the BTS due to HW Reset from the Flexi EDGE BTS Manager.

2 Check Flexi EDGE BTS Manager. Flexi EDGE BTS Manager attempts to connect to the BTS.

3 Wait until Flexi EDGE BTS Manager connects to the BTS.

The Base Station view of Flexi EDGE BTS Manager shows all the HW devices connected before the site reset.

The BCF object including all the TRXs comes to the supervisory state.

4 Place calls on the TRXs. The calls are successfully placed.

2.7.13.4 BCF Object reset from Flexi EDGE BTS Manager with Bypass Traffic Unaffected

The purpose of this test case is to reset the BCF in an Abis chain and verify the bypass traffic is not affected.


Any 2 standard configurations in the Abis chain per the test case comment.

Pre-setup:

• The BTS sites are in supervisory state.



1 Make calls in BCF-2. The calls are successfully placed.

2 Connect Flexi EDGE BTS Manager to BCF 1. Observe that the BCF is in supervisory state for BCF 1.

3 From the Base Station View of Flexi EDGE BTS Manager, select BCF Object for BCF 1.

Click the reset button and select the option without RF cable auto-detection.

A popup window at Flexi EDGE BTS Manager shows a graceful disconnection from the BTS.

4 Wait for Flexi EDGE BTS Manager to connect to BCF 1 after the reset.

Flexi EDGE BTS Manager connects to the BTS after startup.

The LED of the ESMA System module of BCF-1 shows stable green.



DN0749988Issue 2-0 en18/01/2008


5 Verify that bypass traffic is not affected by checking the ongoing calls on BCF2.

Ongoing calls are unaffected, as verified by listening to speech and by verifying at the BSC using the ZERO MML command.

2.7.13.5 BCF Object Admin State Change from the BSC with Bypass Traffic Unaffected

The purpose of this test case is to change the admin state of the BCF in an Abis chain and verify that the bypass traffic is not affected.


• Flexi EDGE BTS Manager is connected to BCF-1.

• The target BTS sites are in supervisory state.



1 Place calls on BCF 2. The calls are placed successfully.

2 Lock the BCF object corresponding to BCF 1 from the BSC using the MML command ZEFS:<bcf_id>:L;

The administrative state of the the BCF object for BCF1 is shown locked in the BSC.

3 Verify ongoing calls on BCF-2. Ongoing calls on BCF-2 are unaffected when verified manually from listening to the speech.

4 Unlock the BCF object corresponding to BCF 1 from the BSC using the MML command ZEFS:<bcf_id>:U;

Observe the BCF object in Flexi EDGE BTS Manager.

BCF-1 handles the unlock command and the site is reset.

BCF-1 site comes up after the reset.

5 Verify ongoing calls on BCF-2. Ongoing calls on BCF-2 are unaffected.

6 Place new calls on BCF-1. New calls on BCF-1 are placed successfully.

2.7.13.6 Alarm Reporting after Object Administrative State Change from the BSC

The administrative states of any BTS logical objects like BTS or TRX can be changed from the BSC. The purpose of this test case is to verify the any alarms started on the TRX objects are reissued after the reset, when the fault condition has not been rectified.

Test case execution


DN0749988 Issue 2-0 en 18/01/2008


217 (381)

Pre-setup:

The target BTS site is switched off.


1 Trigger fault on any one of the ERxx DDU Tx path by removing the Tx cable between the EXxx TRX module and ERxx DDU module.

2 Start the BTS site.

Check for the object states in the Flexi EDGE BTS Manager.

Check the Alarms window of Flexi EDGE BTS Manager.

BTS site reaches supervisory state.

7606:"TRX Faulty, ERxx DDU module has detected no Tx power at TxA input" started on TRX objects connected to the DDU Tx path.

Note: If the fault is on path B, then TxB would appear in the alarm.

3 Check for active alarms in the BSC using MML command ZEOL:<bcf_id>;

The alarm 7606:"ERxx DDU module has detected no Tx power at TxA input" is seen on TRX objects connected to the DDU Tx path.

4 From the BSC, lock any affected TRX object using MML command ZERS:BTS=<bts_id>,TRX=<trx_id>:L;

Check for the Alarm Cancellation message in the GSM Abis Analyser.

Check for active alarms in the BSC using MML command ZEOL:<bcf_id>;

TRX Object state changes from enabled to ‘locked’.

The alarm on the locked TRX object is cancelled.

No active alarms on the BTS/TRX object.

5 Unlock the TRX object by running MML command ZERS:BTS=<bts_id>,TRX=<trx_id>:U;

Check for the TRX object state in the Flexi EDGE BTS Manager.

The TRX Object comes up after logical reset.



7 From the BSC, lock the affected BTS object using MML command ZEQS:BTS=<bts_id>:L;

Check for cancellation of the Alarm for TRX objects under the BTS object in the Abis Analyser.

Check for active alarms in the BSC using MML command ZEOL:<bcf_id>;

The BTS object state changes from enabled to ‘locked’.

Alarm cancellation for the TRX objects is seen in the GSM Abis Analyser.

No active alarms on the BTS/TRX object.

8 Unlock the BTS object by running MML All TRXs belonging to BTS object are reset.



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output command ZEQS:BTS=<bts_id>:U;

Check for the TRX object states under the BTS object in the Flexi EDGE BTS Manager.



10 Rectify the fault condition on the ERxx DDU Tx path created in step 1.

11 From the BSC, lock affected BTS object using MML command ZEQS:BTS=<bts_id>:L;

Check for cancellation of the alarm for TRX objects under the BTS object in the Abis Analyser.

Unlock the BTS object by running MML command ZEQS:BTS=<bts_id>:U;

Check for the TRX object states under the BTS object in the Flexi EDGE BTS Manager.

BTS Object state changes from enabled to ‘locked’.

Alarm cancellation for the TRX objects are seen in the GSM Abis Analyser.

All TRXs belonging to BTS object comes up after reset.


No active alarms on the TRX/BTS objects.

2.7.13.7 BTS Object Behaviour When EXxx TRX Module Controlling ERxx DDU Module is HW Reset

The EXxx TRX modules can be HW reset using Flexi EDGE BTS Manager. The purpose of this test case is to verify that the sector recovers when the EXxx TRX Module, controlling ERxx DDU module is HW reset.




• Calls are successfully placed in the TRXs.


1 From the Base Station View of Flexi EDGE BTS Manager, select the EXxx TRX module controlling the ERxx DDU module in the BTS object 2.

The HW state should be working.

2 In the Properties pane, click the HW reset The EXxx TRX module is HW reset.


DN0749988 Issue 2-0 en 18/01/2008


219 (381)

Step Input Expected output button.

3 Check for the Alarms window of Flexi EDGE BTS Manager at this point.

7606: ’TRX faulty:ESMA System module has lost connection to EXxx TRX module’ started for two TRX objects in the BTS object 2.

7606: ’TRX faulty: EXxx TRX module has lost connection to ERxx DDU module’ started for one of the TRX objects in the sector 2.

7603: ’BTS faulty: EXxx TRX module has lost connection to ERxx DDU module’ started for this sector.

4 Observe the object properties of the TRX objects of the EXxx TRX module in Flexi EDGE BTS Manager.

Check for the active alarms in the BTS Alarms window.

The TRX objects come up after the reset and the LAPD links are established.

No active alarms on any TRX object of BTS object 2.

5 Observe the EXxx TRX module TRX object properties in Flexi EDGE BTS Manager.

All the TRX objects in sector 2 reach supervisory state.

6 Place calls on the TRX objects. The calls are successfully placed on the TRX objects of sector 2.

2.7.13.8 BTS Object Recovery when EXxx TRX Module Carrying BCCH TRX is HW Reset

The EXxx TRX modules can be HW reset using Flexi EDGE BTS Manager. The purpose of this test case is to verify that the sector recovers when the EXxx TRX Module carrying the BCCH TRX is HW reset.





1 Identify the EXxx TRX module carrying the BCCH carrier for the sector using the MML command ZEEI:BCF=<bcf_id>;

The TRX Identifier of BCCH TRX is noted.

2 From the Base Station View of Flexi EDGE BTS Manager, select EXxx TRX module corresponding to the TRX object identified in step 1.

The HW state should be working.



DN0749988Issue 2-0 en18/01/2008


3 In the Properties pane, click the HW reset button.

The EXxx TRX module is HW reset.

4 Check the Alarms window in Flexi EDGE BTS Manager at this point.

7606: ’TRX Faulty: ESMA System module has lost connection to EXxx TRX module’ started on both TRX objects to Flexi EDGE BTS Manager and the BSC.

5 Check for the TRX object states using ZEEI:BCF=<bcf_id>;

Find out the TRX object which has been configured as the BCCH by the BSC.

The BCCH has been reconfigured to any other working TRX object in this sector.

6 Check the Alarms window.

Observe the properties of the TRX objects of the EXxx TRX module that was HW reset.

Alarms 7606 are cancelled to Flexi EDGE BTS Manager and the BSC.

The TRX objects come up after the reset and the LAPD links are established.

7 Place calls on any TRX objects in the sector. The calls are successfully placed.

2.7.14 BTS Supervision

Overview In the Flexi EDGE Base Station, both software and hardware carry out supervision activities. BTS Supervision is responsible for carrying out the following procedures:

• Runtime management of units/modules

• Periodic polling of BTS internal units/modules

• Periodic polling of BTS external units/modules

• Monitoring of received signal strengths of main and diversity antennas

• Monitoring of Ethernet and Q1 interfaces

Scope of testing Features tested as per this plan:

• Supervision of the following hardware units:

− ESEA System Extension Module

− EXxA TRX Module

− ECxA RTC Module

− ERxA DDU Module.


DN0749988 Issue 2-0 en 18/01/2008


221 (381)

• Supervision of Ethernet Interface

• Supervision of Q1 Bus.

• Detection and supervision of fan units in the EXxA TRX Module and the ESMA System Modules at startup.

Test cases

Pos Name Comment

1 Supervision Of EXxA TRX Module FAN Unit When Fans Are Missing

2+4+2

2 Supervision Of ESMA System Module FAN Unit When Fans Are Missing

Any BTS Configuration

3 Supervision Of EXxA TRX Module With ERxA DDU Module Connected

2+4+2, RF Hopping

4 Supervision Of EXxA TRX Module Without ERxA DDU Module Connected

2+4+2, RF hopping

5 Supervision Of EXxA TRX Module connected to ERxA DDU Module in a 24 TRX BTS Site

8+8+8, 4 way combining, RF Hopping

6 Supervision Of ESMA System Module to Central EOCA Optical Converter module unit interface in a Feederless Site

4+4, 2 Way combining, separate EOCA per Sector

7 Supervision Of Optical Interface used for a Feederless site

4+4, Bypass combining, Separate EOCA per Sector

8 Supervision of Ethernet Interface 2+2+2

9 Supervision Of ERxA DDU Module 2+2+2

10 Supervision of ESEA System Extension Module

6+6, Cavity Combining, BB Hopping

11 Supervision of ECxA RTC Module 6+6, Cavity Combining, BB Hopping

12 Supervision Of Q1 Bus Any BTS Configuration

13 Sector Reconfiguration Support in a Baseband Hopping Sector

6+6,BB Hopping, EXxA TRX Module with BCCH TRX to be removed


6+6,BB Hopping, Non-BCCH EXxA TRX Module to be removed


12-Omni, BB Hopping, EXxA TRX Module with BCCH TRX to be removed



DN0749988Issue 2-0 en18/01/2008

Pos Name Comment


12-Omni, BB Hopping, Non-BCCH EXxA TRX Module to be removed

2.7.14.1 Supervision of EXxA TRX Module FAN Unit When Fans Are Missing

The objective of the test case is to verify the FAN Unit supervision at the time of EXxA TRX Module initialisation. When the EXxA TRX Module is coming up and no Fans are detected, an alarm is raised and reported to the active clients.


EXxA TRX Module 2 and 3 (TRX Objects 3-6) are associated with sector-2.

Pre-setup:

• The BTS is in supervisory state with no unexpected active alarms.

• Flexi EDGE BTS Manager is connected locally to the BTS and it is operational


1 Start 1 MS-MS CS call on TRX object 3 or 4. CS Calls get established and are running successfully.

2 At Flexi EDGE BTS Manager, Go to BTS Control ->Power Control-> Select Power distribution Unit ID for EXxA TRX Module 3, and change it to 'Turn OFF' state.

EXxA module 3 is powered off.

3 Cut off the power supply of the FAN Unit of EXxA TRX Module-3.

Again at the Flexi EDGE BTS Manager, go to BTS Control ->Power Control-> Select Power distribution Unit ID for EXxA TRX Module 3, and change it to 'Turn ON' state.

Verify that EXxA Module 3 comes up and both TRX objects associated with the module reach Supervisory state.

4 Observe the active alarms at the BSC and the Flexi EDGE BTS Manager.

The alarm '7607, TRX Operation Degraded' is started for both TRX5 and TRX6 with the alarm text as "Commissioning file climate control profile mismatch, no fans detected" and the object current state as "enabled".

5 Observe the CS call started on the BTS in step 1.

CS calls are going on with no disruption.

6 Again, at Flexi EDGE BTS Manager, Go to EXxA module 3 is powered off.


DN0749988 Issue 2-0 en 18/01/2008


223 (381)

Step Input Expected output BTS Control ->Power Control-> Select Power distribution Unit ID for EXxA TRX Module 3, and change it to 'Turn OFF' state.

7 Connect the FAN Unit power back to the EXxA TRX Module-3.

At the Flexi EDGE BTS Manager, go to BTS Control Power Control Select Power distribution Unit ID for EXxA TRX Module 3, and change it to 'Turn ON' state.

Verify that EXxA Module 3 comes up and both TRXs 5 and 6 reach supervisory state.

Also verify that there is no FAN related active alarm for TRX5 and TRX6, at the BSC and Flexi EDGE BTS Manager.

8 Observe the CS calls started on the BTS in step 1.

CS calls are going on with no disruption.

2.7.14.2 Supervision of ESMA System Module FAN Unit When Fans Are Missing

The objective of the test case is to verify the Fan Unit supervision at the time of ESMA System Module initialisation. When the ESMA System Module is coming up and no Fans are detected, an alarm is raised and reported to the active clients.





1 Switch OFF the power supply to the BTS site. The complete BTS site is powered off.

2 Cut off the power supply of the FAN Unit of ESMA System Module.

Power on the BTS site.

The site is powered up and the BTS and all TRXs reach supervisory state.

3 Observe the active alarms at the BSC and the Flexi EDGE BTS Manager.

The alarm '7601, BCF Operation Degraded' is started for the BCF with the alarm text as "Commissioning file climate control profile mismatch, no fans detected" and object state as "enabled".

4 Establish 1 pair of CS call any sector of the site.

Verify that the CS call starts successfully.

5 Switch OFF the power supply to the BTS site. The complete BTS site is powered off. The calls also get cleared.

6 Connect the FAN Unit power back to the ESMA System Module.

The site is powered up and the BTS and all TRXs reach Supervisory state.



DN0749988Issue 2-0 en18/01/2008


Power on the BTS site. Also verify that there is no FAN related active alarm for the BCF, at both the BSC and Flexi EDGE BTS Manager.

7 Establish 1 MS-MS CS call on any sector of the site.

Verify that the CS call starts successfully.

2.7.14.3 Supervision of EXxA TRX Module With ERxA DDU Module Connected

The aim of the test case is to verify the behaviour of the system when an EXxA TRX module is disconnected from the ESMA System module in an operational BTS and then reconnected. The EXxA Module under test has an ERxA DDU Module connected.



Pre-setup:


• Flexi EDGE BTS Manager is connected locally to the BTS and it is operational.


1 Start 1 MS-MS CS call on each sector of the BTS site.

CS calls start successfully.

2 Disconnect EXxA module 2 from the ESMA module by plugging out the BUS cable. Keep it disconnected for at least 30 seconds.

Note: EXxA 2 is connected to the ERxA DDU Module.

Observe the active alarms for sector 2 at the BSC using MML command ZEOL as well as the Flexi EDGE BTS Manager active alarms window.

The '7606, TRX Faulty' alarm is started on both TRX3 and TRX4 with alarm text "ESMA System module has lost connection to EXxx TRX module" and object current state "disabled".

A '7606, TRX Faulty' alarm is started on TRX5 with alarm text "EXxx TRX module has lost connection to ERxx DDU module" and object current state "disabled".

A '7603, BTS Faulty' alarm (re-classification of 7606 TRX faulty alarm on TRX6) is started for BTS 2, with the alarm text "EXxx TRX module has lost connection to ERxx


DN0749988 Issue 2-0 en 18/01/2008


225 (381)

Step Input Expected output DDU module" and object current state "disabled".

3 Observe the CS calls started on all sectors in step 1.

CS calls and packet data transfers are still going on in all sectors except sector 2, with no disruption.

Calls in the second sector get dropped.

4 Connect EXxA module 2 back to the ESMA port at which it was previously connected.

Verify that all TRXs in sector 2 come to Supervisory state.

Also verify that no unexpected re-configurations occur.

5 Observe the currently active alarms at the BSC as well as the Flexi EDGE BTS Manager active alarms window.

Verify that there are no active alarms on sector 2 or any TRX of sector 2.

Also, there should be no active alarms on other sectors of the site.

6 Start one MS-MS CS call on sector 2 of the BTS site.


2.7.14.4 Supervision of EXxA TRX Module without ERxA DDU Module Connected

The aim of the test case is to verify the behaviour of the system when an EXxA TRX module is disconnected from the ESMA System module in an operational BTS and reconnected. The EXxA Module under test does not have an ERxA DDU Module connected.


EXxA TRX Module 2 and 3 (TRX objects 3-6) are associated with sector 2.

Pre-setup:




1 Start 1 MS-MS CS call TRX 3 or 4. CS calls start successfully.


Observe the active alarms for sector-2 at the BSC using MML command ZEOL as well as

A '7606, TRX Faulty' alarm is started on TRX5 and TRX6 with the alarm text "ESMA System module has lost connection to EXxx TRX module" and the object state "disabled".



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output the Flexi EDGE BTS Manager active alarms window.

Note: EXxA-3 of sector 2 is not connected to the ERxA DDU Module.

Verify that TRX3 and TRX4 remain in Supervisory state. Also verify that all TRXs in sector 1 and 3 are in Supervisory state and there are no unexpected alarms in those sectors.

3 Observe the CS call started in step 1. CS calls are still going on with no disruption.


Verify that TRX5 and TRX6 come to Supervisory state.




Also there should be no active alarms on other sectors of the site.

6 Observe the CS call started in step 1. CS calls are still going on with no disruption.

2.7.14.5 Supervision of EXxA TRX Module connected to ERxA DDU Module in a 24 TRX BTS Site

The aim of the test case is to verify the behaviour of the system when an EXxA TRX module is disconnected from the ESMA System module in an operational BTS and reconnected. The EXxA Module in the test has an ERxA DDU Module connected.


1. The BTS is in supervisory state with no unexpected active alarms.

2. The Flexi EDGE BTS Manager is connected locally to the BTS and it is operational.

3. ERxA DDU Module in Sector 1 is controlled by Flexi EDGE Dual TRX Module EXxA-3.



The CS calls start successfully.


Observe the active alarms for sector 1 at the BSC using MML command ZEOL as well as the Flexi EDGE BTS Manager active alarms window:

The '7606, TRX Faulty' alarm is started on both TRX5 and TRX6 with alarm text


DN0749988 Issue 2-0 en 18/01/2008


227 (381)

Step Input Expected output "ESMA System module has lost connection to EXxx TRX module" and object current state "disabled".

A '7606, TRX Faulty' alarm is started on all TRX objects except for BCCH TRX for BTS object 1 with alarm text "EXxx TRX module has lost connection to ERxx DDU module" and object current state "disabled".

A '7603, BTS Faulty' alarm (re-classification of 7606 TRX faulty alarm on BCCH TRX) is started for BTS object 1, with the alarm text "EXxx TRX module has lost connection to ERxx DDU module" and object current state "disabled".

3 Observe the CS calls started on all BTS objects in step 1.

CS calls and packet data transfers are still going on in all BTS objects except BTS object 1, with no disruption.

Calls in the BTS object-1 are dropped.


Verify that all TRXs in BTS object 1 come to Supervisory state.




Also there should be no active alarms on other sectors of the site.

6 Start 1 MS-MS CS call in sector-1 of the BTS site.


7 Repeat steps 1 to 6 on each EOCA / sector and removing different BUS cables supporting EXxA modules which do and do not have an ERxx DDU module supported.

Same behaviour as given in steps 1 to 6.

2.7.14.6 Supervision of ESMA System Module to Central EOCA Optical Converter module unit interface in a Feederless Site

The aim of the test case is to verify the behaviour of a Flexi EDGE BTS Site when one of the Ethernet links between ESMA System module and Central EOCA Optical Converter module unit goes faulty. As a result, the EXxA TRX module linked by the faulty Ethernet cable becomes dumb.

The affected EXxA Module under test, has a BCCH TRX object configured, thereby triggerrng BCCH reconfiguration from the BSC.



DN0749988Issue 2-0 en18/01/2008

When the Ethernet link is restored, the affected TRX objects reach 'Supervisory' state.



EOCA Optical Converter module unit 1 supports EXxA TRX modules 1 and 2 while EOCA Optical Converter module unit 2 supports EXxA TRX modules 3 and 4.

EXxA TRX Module 1 is connected to ERxA DDU Module in Sector 1 while BCCH is configured on TRX object 3.

Pre-setup:

1. The BTS is in supervisory state with no unexpected active alarms.

2. The Flexi EDGE BTS Manager is connected locally to the BTS and it is operational.




2 Disconnect the BUS cable between the ESMA System module and Central EOCA Optical Converter module unit 1 from port 2 of the ESMA System module.

Observe the active alarms for sector 1 at the BSC using MML command ZEOL as well as the Flexi EDGE BTS Manager active alarms window.

The '7606, TRX Faulty' alarm is started on both TRX3 and TRX4 with alarm text as "ESMA System module has lost connection to EXxx TRX module" and object current state as "disabled".

3 Observe the CS calls started on all sectors in step 1.

Observe the BCCH reconfiguration.

CS calls are still going on in all sectors except on TRX objects 3 and 4.

BCCH reconfigures to working TRX object 1 or 2 in Sector 1. Ongoing CS calls for the reconfigured TRX are also dropped or handed over if commanded by the BSC.

4 Reconnect the BUS cable between the ESMA System module and Central EOCA Optical Converter module unit 1, which was disconnected in Step 2 above.

Using Flexi EDGE BTS Manager, verify that TRXs 3 and 4 come to supervisory state.

The alarm started in step 2 is cancelled for both TRX3 and TRX4.




DN0749988 Issue 2-0 en 18/01/2008


229 (381)


Also, there should be no active alarms on other sectors of the site.

6 Start 1 MS-MS CS call in sector 1 of the BTS site.


7 Repeat steps 1 to 6 for a BUS cable connected to each of the EOCA units.

Same behaviour as given in steps 1 to 6.

2.7.14.7 Supervision of Optical Interface used for a Feederless site

The purpose of this test case is to verify the Flexi EDGE BTS site behaviour, when the optical link between central EOCA unit and remote EOCA unit is removed. All the ongoing calls on affected TRXs are dropped. Calls going on other sector are not affected. After reconnecting the optical link between central EOCA unit and remote EOCA unit the affected TRX's are recovered successfully.



EOCA unit 1 supports EXxA TRX modules 1 and 2 while EOCA unit 2 supports EXxA TRX modules 3 and 4.

Every EXxA TRX Module in the site supports a ERxA DDU Module.

BCCH is configured on TRX objects 1 and 5.

Pre-setup:

The BTS is in supervisory state with no unexpected active alarms.

The Flexi EDGE BTS Manager is connected locally to the BTS and it is operational.


1 Disconnect the optical link between central and remote EOCA unit 1.

Observe the alarm on BTS manager and BSC. Use MML command ZEOL to check alarms at the BSC.

The following alarms are active for sector 1 at the BSC as well as the Flexi EDGE BTS Manager window :

Three 7606 alarms "TRX unable to carry traffic" details "EXxA connection is lost” are reported and one 7603 Alarm "BTS faulty" is reported.

2 Observe the status of ongoing calls. Sector 1: All ongoing calls are dropped.

Sector 2: No effect on ongoing calls.



DN0749988Issue 2-0 en18/01/2008


3 Reconnect the optical link between central and remote EOCA unit 1.

All TRX of sector 1 are recovered to "WO" working status as verified from the BSC using 'ZEEI' MML command.

All TRXs are in supervisory state as seen from Flexi EDGE BTS Manager.

4 Observe the alarm on Flexi EDGE BTS Manager and BSC. Use MML command ZEOL to check the alarm at the BSC.

All alarms raised in step 1 are cancelled. No other unexpected alarm is observed.

5 CS calls are made on all TRX objects in sector 1.


6 Fetch the site information report from Flexi EDGE BTS Manager and save it in xml format.

Open the site information report and verify that all the module properties EXxA and EOCA (local and remote) are valid which were affected in steps 1 to 3.

2.7.14.8 Supervision of Ethernet Interface The aim of the test case is to verify the behaviour of the system when all the EXxA TRX modules are disconnected from the ESMA System module in an operational BTS, that is, the Ethernet interface is declared faulty.





1 Disconnect all the EXxA TRX Modules from the ESMA System Module, one by one by removing the connecting cable. Keep it disconnected for at least 60 seconds.

Observe the active alarms at the BSC using the MML command ZEOL and in Flexi EDGE BTS Manager Alarm window.

Alarm '7606, TRX Faulty' is started for all the TRXs except one, in each sector, with the alarm text ‘ESMA System module has lost connection to EXxx TRX module’ and the object state is ‘disabled’.

Alarm 7603 is started for all the sectors (the 7606 alarm for the last TRX in each sector gets reclassified to a 7603 alarm) with the following alarm text ‘ESMA System module has lost connection to EXxx TRX module’ and the object state ‘disabled’.

Alarm '7600, BCF Faulty' is started for the BCF with the alarm text ‘ESMA System module has lost connection to all ECxx


DN0749988 Issue 2-0 en 18/01/2008


231 (381)

Step Input Expected output RTCs and EXxx TRXs’ and the object state is ‘disabled’.

2 Reconnect all the the EXxA TRX Modules to the ESMA System module.

The alarm 7600 is cancelled by the BTS and is no more seen as an active alarm in the BSC alarm history.

The alarm is no longer seen in the Flexi EDGE BTS Manager Active Alarms window.

The BSC will request a BCF_reset upon 7600 alarm cancellation. Verify that the BTS site comes to Supervisory state after the BCF Reset and becomes operational. Also verify that after the site comes up, there are no unexpected active alarms at the BSC or Flexi EDGE BTS Manager.

3 Place 1 MS-MS CS call on any one sector of the site.

The CS call starts successfully.

2.7.14.9 Supervision of ERxA DDU Module

The objective of the test case is to verify that when an ERxA DDU Module connected to EXxA TRX Module is disconnected, then the alarm for no antenna connection is reported by the BTS. It also verifies that when the ERxA DDU Module is reconnected to the BTS, the alarm gets cancelled.





1 Start 1 MS-MS CS call each on the first and second sectors (BTS-1 and BTS-2).


2 Disconnect ERxA DDU Module from the EXxA TRX Module, in the first sector.

Keep it disconnected for at least 30 seconds.

CS calls are dropped in the first sector and ERxA DDU Module will not be visible on Flexi EDGE BTS Manager.

CS and are still going on in the second sector with no disruption.

3 Observe the active alarms at the BSC using MML command ZEOL and at the Flexi EDGE

A '7606, TRX Faulty' alarm is started on one TRX of the sector with alarm text "EXxx



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output BTS Manager active alarms window. TRX module has lost connection to ERxx

DDU module" and object current state "disabled".

A '7603, BTS faulty' alarm is started (re-classification of 7606 alarm for the other TRX) with the alarm text "EXxx TRX module has lost connection to ERxx DDU module" and object state "disabled".

4 Observe the CS calls started on the second sector.

CS call is going on in the second sector with no disruption.

5 Connect the ERxA DDU Module back to the EXxA TRX Module in the first sector.

Both TRX1 and TRX2 come to supervisory state.

6 Observe the active alarms at the BSC using MML command ZEOL and also at the Flexi EDGE BTS Manager active alarms window.

No active alarms are seen on sector 1, that is, the alarms 7606 and 7603 have been cancelled.

7 Observe the CS calls started on the second sector.

CS call and packet data transfer is going on in the second sector with no disruption.

8 Start 1 MS-MS CS call in sector-1. CS calls start successfully.

2.7.14.10 Supervision of ESEA System Extension Module

The objective of this test case is to verify the behaviour of the system if the ESEA System Extension Module is disconnected from the ESMA System Module. The test case focus would be on the 7600 alarm and the behaviour when the ESEA is reconnected and the 7600 alarm gets cancelled.





1 Place 1 MS-MS CS call on both sectors of the BTS site.


2 Disconnect the ESEA System Extension Module from the ESMA System Module by removing the bus cable. Keep it disconnected for at least 60 seconds.

Observe the active alarms at the BSC using the MML command ZEOL and in the Flexi

The CS calls started in step 1 get dropped.

For each affected TRX object, alarm '7606, TRX Faulty' is started (1 alarm in each sector re-classified to '7603, BTS Faulty' alarm) with the alarm detail ‘ESMA System module has lost connection to EXxx TRX


DN0749988 Issue 2-0 en 18/01/2008


233 (381)

Step Input Expected output EDGE BTS Manager Alarm window. module’ and the object state as ‘disabled’.

Alarm '7600, BCF Faulty' is started with the the alarm text ‘ESMA System module has lost connection to ESEA System Extension module’ and the object state as ‘disabled’.

3 Observe BTS view at Flexi EDGE BTS Manager.

The ESEA System Extension Module is marked as a dumb module.

The EXxA TRX modules connected to the ESEA module are marked as dumb modules.

Note: Please note that when a module is marked as dumb, the icon corresponding to that module on the Flexi EDGE BTS Manager BTS view is dimmed on the screen.

4 Reconnect the ESEA System Extension Module to the ESMA System module.

Observe the active alarms at the BSC using the MML command ZEOL, and in the Flexi EDGE BTS Manager Alarm window.

Alarm 7600 is cancelled by the BTS and is no more seen as an active alarm in the BSC alarm history.

Also the alarm is no longer seen in the Flexi EDGE BTS Manager Active Alarms window.

The BSC will request a BCF_reset upon 7600 alarm cancellation. Verify that the BTS site comes to Supervisory state after the BCF Reset and becomes operational.

5 Place 1 MS-MS CS call on any one sector of the site.

The CS call and packet data transfer start successfully.

2.7.14.11 Supervision of ECxA RTC Module

The objective of this test case is to verify that if the ECxA RTC Module is disconnected from the ESMA System Module in an operational Flexi EDGE Base Station, alarm 7603 is raised. It is also verified that the alarm gets cancelled when the ECxA RTC module is reconnected.





1 Place 1 MS-MS CS call on both sectors of the The CS calls start successfully.



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output BTS.

2 Disconnect the ECxA RTC Module in the first sector from the ESMA System Module by removing the bus cable.

Observe the active alarms at the BSC using the MML command ZEOL and in the Flexi EDGE BTS Manager Alarm window.

For each of the Non-BCCH TRXs, alarm '7606, TRX Faulty' is started with the alarm text ‘ESMA System module has lost connection to ECxx RTC module’ and the object state as ‘disabled’.

Alarm '7603, BTS Faulty' is started on the BTS (a re-classification of the 7606 alarm on BCCH TRX), with the alarm text ‘ESMA System module has lost connection to ECxx RTC module’ and the object current state ‘disabled’.

3 Observe the calls established in both sectors. The calls in the first sector get dropped.

The calls in the second sector are still going on without any disruption.

4 Reconnect the ECxA RTC Module to the ESMA System module.

Observe the active alarms at the BSC using the MML command ZEOL and in the Flexi EDGE BTS Manager Alarm window.

Verify that alarm 7603 and all the 7606 alarms that were seen in step 2 have been cancelled and no active alarms are visible in the BSC or in the Flexi EDGE BTS Manager active alarms window.

All TRX objects in sector 1 reach supervisory state.

5 Place 1 MS-MS CS call in sector-1. The CS call starts successfully.

6 Observe the calls established in the second sector.

The CS calls are still running without any disruption.

2.7.14.12 Supervision of Q1 Bus

The aim of the test case is to verify the behaviour of the system when all the Q1 devices connected to the system are lost and the Q1 bus is declared faulty.


• FIU19

• LMU

Software tools:

• Hopper Manager


DN0749988 Issue 2-0 en 18/01/2008


235 (381)




• The Q1 monitor tool is connected on the Q1 bus.

• The LMU is commissioned using LMU manager.

• FIU19 is also commissioned.


1 Connect the FIU19 and LMU to the Base station as Q1 devices via the Q1 Bus.

FIU19 and LMU are connected to the site.

2 Configure LMU at the BSC using the MML command ZQWA, with Q1 Address 132.

Make LMU a high priority device using the BSC MML command ZEXA.

Observe the GSM Abis Analyser. The following messages must be seen on the Abis from the BSC to the BTS:

BTS TRE POLL LIST

Q1 baud rate

Q1 int serial speed : 9600

TRE object identity : TRE, nr 1, subnr 15

Q1 address : reserved 4080

Polling : low


Q1 address : 132

Polling : low

BTS TRE POLL LIST

Q1 baud rate



Q1 address : 132

Polling : Highest

A BTS_ACK is sent from the BTS to the BSC for both these messages.

3 Configure FIU19 at the BSC using the MML command ZQWA

Observe the GSM Abis Analyser. The following message must be seen on the Abis from the BSC to the BTS:



DN0749988Issue 2-0 en18/01/2008


BTS TRE POLL LIST

Q1 baud rate



Q1 address : reserved 4080

Polling : low


Q1 address : 132

Polling : low


Q1 address : (As configured at BSC)

Polling : low

A BTS_ACK is sent from the BTS to the BSC for this message.

4 Remove the Q1 cable between the BTS and the LMU device.

Observe the active alarms at the BSC using MML command ZAHO and at the Flexi EDGE BTS Manager active alarms window.

The alarm '8202, Loss of Supervision Connection' is started for TRE-2 within 10 seconds with the alarm text "Loss of Supervision connection" and the object state "enabled".

5 Disconnect the FIU19 from the Q1 bus.

Observe the active alarms at the BSC using MML commands ZAHO and ZEOL and at the Flexi EDGE BTS Manager active alarms window.

The alarm '8202, Loss of Supervision Connection' is started for TRE-4, within 30 seconds of disconnecting FIU19, with the alarm text "Loss of Supervision connection" and the object state "enabled".

A '7601, BCF Operation Degraded' alarm is started for the BCF with the alarm text "All external Q1 devices fail to respond" and object state "enabled".

6 Reconnect the LMU to the Q1 bus.

Observe the active alarms at the BSC using MML commands ZAHO and ZEOL and at the Flexi EDGE BTS Manager active alarms window.

Verify that the 8202 alarm for loss of LMU and the 7601 alarm get cancelled within 10 seconds and are not visible in the list of active alarms at the BSC or in the Flexi EDGE BTS Manager alarms window.

2.7.14.13 Sector Reconfiguration Support in a Baseband Hopping Sector

The objective of the test case is to verify that


DN0749988 Issue 2-0 en 18/01/2008


237 (381)

• When a logical TRX is disabled (by disconnecting the bus cable of the EXxx TRX module) in a BB hopping sector, the complete BTS object will get reconfigured. Corresponding alarm(s) are raised for the faulty logical TRX and cancelled after the fault is cleared.

• Reconfiguration of one sector of a BTS site in BB Hopping mode does not impact operation of the other sectors in the BTS site.

• All ongoing CS calls on the other TRXs in the same BTS object are handed over if commanded by the BSC.

• After the fault of the TRX is removed, the complete BTS object will be reconfigured again.

• After reconfiguration, the site resumes normal operation

• New calls (CS/PS) can be generated on the reconfigured BTS object including the faulty TRX.




1. Baseband Hopping enabled from the BSC.

2. Each BTS object is in supervisory state with non-combined BCCH.

3. The BCCH TRX is the first TRX in each sector.

4. There is no alarm active at the BTS site.

5. Configure a third test base station object (referred to as Test BTS object) and all the configured sectors are defined as neighbours of each other using the MML command: >>> ZEAC:BTS=<BTS1 No.>:ABTS=<BTS2 No.>;

6. Enable GPRS and EGPRS on all the BTS objects.


1 Establish CS calls on all the defined sectors, 6 in each sector, so that the originating leg of all the calls are on sectors under testing and the terminating leg is on Test BTS Object.


2 Generate a disabling alarm for an EXxA TRX module of the sector by removing the bus cable between the EXxA TRX module and the ESEA System Extension module.

Check the alarm status at the active alarms window of Flexi EDGE BTS Manager and at

The '7606, TRX Faulty' alarm is started for each TRX of the EXxA TRX modules with the alarm text "TRX unable to carry traffic. EXxA connection is missing or is not operational" and the object state "disabled".



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output the BSC.

3 Observe the status of all ongoing calls on the EXxA TRX module on which the fault was introduced.

All ongoing calls on the EXxA TRX module are dropped.

4 Observe the status of all ongoing calls associated with the other TRXs of the sector where the fault was introduced.

Verify that the all ongoing calls on the other TRXs are handed over to the adjacent sector, if defined.

5 Verify that within 10 seconds, the complete BTS object on which the fault was introduced is reconfigured.

A new TRX is configured as BCCH if the disabling alarm has been raised on a TRX configured as BCCH.


6 Observe the existing calls on other BTS objects in the BTS site during reconfiguration of the designated BTS object.

Verify that the calls continue on the other sectors without any disruption.

7 Generate CS calls on the reconfigured BTS object.

Initiate PS data transfer on the reconfigured BTS object.

Verify that the CS calls are successfully established.

PS data transfer is successful.

8 Release the CS calls and the PS data transfer session.

Verify that the CS calls and the PS data transfer sessions are successfully released.

9 Reconnect the bus cable of the EXxA TRX module.

Verify that after 10 seconds, the complete BTS object is reconfigured with both the TRXs of the new EXxA TRX module coming into service.


10 Check the alarm status at the alarm window of Flexi EDGE BTS Manager.


There is no active alarm at Flexi EDGE BTS Manager.

There is no active alarm at the BSC.

11 Generate one MS-MS CS call and one PS data transfer session on the reconfigured BTS object.

Verify that the CS call and packet data transfer are successfully established.


DN0749988 Issue 2-0 en 18/01/2008


239 (381)

2.7.15 Temperature Control System

Overview The Temperature Control System monitors and controls the internal temperature of the Flexi EDGE BTS units (ESMA System Module, EXxx TRX Module, ECxx RTC Module). The design constraint for each module is to keep the temperature at target levels and control the acoustic noise generation from fans. The acoustic performance is defined by the Climate Control Profile when site is commissioned.

Scope of testing The testing scope is limited to the monitoring of the module temperatures and fan speeds in a temperature controlled lab environment for the BTS units (ESMA System Box, EXxx TRX modules and ECxx RTC modules), and the modification of Climate control profiles by append commissioning.

This plan does not cover the testing of the BTS under extreme ambient temperature conditions which may be simulated using a temperature chamber.

Test cases

Pos Name Comment

1 Climate Control Monitoring of BTS Units for Long Duration

6 + 6

2 Changing Climate Control Profile (from Default High MTBF to Min Noise ) using Append Commissioning

Any BTS configuration

2.7.15.1 Climate Control Monitoring of BTS Units for Long Duration

The Flexi EDGE Base Station monitors internal temperature of various BTS units (ESMA System Module, EXxx TRX Module and ECxx RTC Module) continuously, with sensors located inside those modules. The BTS controls its temperature with cooling fans to provide as stable operating condition as possible. This test case verifies that the Temperature Control System ensures that stable operating condition is maintained and there is no temperature and/or fan related alarm(s) when the ambient condition and call traffic profile kept constant.


• The BTS site has been commissioned with the default Climate Control Profile MAX_MTBF.



DN0749988Issue 2-0 en18/01/2008

• Ambient Temperature at the BTS site is maintained at around 25 deg C.

• The BTS site is in operational (BCF in supervisory state).

• The Max Power level is set to default value (PMAX1=0).


1 Monitor the temperature and the fan speed for the ESMA System Module.

Note the observed values.

The temperature in the ESMA System Modules is within the limits.

The speed of the fans is stable.

No temperature related alarm is observed.

2 Monitor the temperature and fan speeds for each of the ECxx RTC modules.


The temperature in the ECxx RTC modules is within the limits.

The speed of the fans is stable.

3 Monitor the temperature and fan speeds for the EXxx TRX modules carrying the BCCH TRX.


The temperature of one of the sensors is higher than the other one.

The fan speeds of the EXxx TRX module fans are stable.

4 Monitor the temperature and fan speeds for the EXxx TRX modules carrying any Non BCCH TRX.


The temperature of the sensors in the EXxx TRX Module is within the limits.

The observed sensor reading of the EXxx TRX module carrying Non BCCH TRXs shall be lower than the higher sensor reading noted in step 3.

5 Check for any alarms at Flexi EDGE BTS Manager.

No temperature or fan related alarm is visible.

6 Place few calls on all the TRXs. Calls are successful.

7 Make the observations in step 1-5 at regular intervals for next 10-12 hours.

Check the trend of observed temperature and fan speed values for each of the sensor and fan respectively.

The temperature of a given sensor is stable and does not show significant deviations.

The speed of a given fan is stable and does not show significant deviations.

8 Verify the alarms for the BCF object using MML command ZEOH.

No temperature or fan related alarm shall be visible.

2.7.15.2 Changing Climate Control Profile (from Default High MTBF to Min Noise) Using Append Commissioning

This test case checks for the change in the acoustic noise level when the Climate Control Profile is changed through Append Commissioning.

Test case execution


DN0749988 Issue 2-0 en 18/01/2008


241 (381)

Pre-setup:

• The BTS site has been commissioned with the default Climate Control Profile MAX_MTBF.

• Ambient Temperature at the BTS site is maintained at around 25 degrees C.

• Flexi EDGE BTS Manager is connected at LMP port of the ESMA System Module.

• No alarm is present that indicate a hardware or software problem.

• The site is up with a few ongoing calls for at least 1 hour.


1 Monitor the fan speed for the ESMA System Module.

Note down the acoustic level by manually hearing the noise of the fan assembly.

The fan speed is stable and does not oscillate.

2 Using the Flexi EDGE BTS Manager fetch the commissioning report and check for the Climate Control Profile in the Site Information section.

The Climate Control Profile in the Commissioning Report shows:

Climate Control Profile: MAX MTBF

3 From the Commissioning Wizard of the Flexi EDGE BTS Manager, change the Climate Control Profile from "Max_MTBF" to "Min_Noise" in the Site Specific Information section.

Click on "Send SCF".

Observe the Commissioning process.

The site gets commissioned and the Commissioning Wizard mentions Commissioning Successful.

4 Check the Commissioning Report Executive Summary.

Check the Detailed Commissioning Report.

The Executive Summary of the Commissioning Report shows:

Commissioning phase of SCF : APPEND

Commissioning Result : SUCCESSFUL

Detailed Commissioning Report for the last attempted commissioning shows:

Climate Control Profile: LOW NOISE

5 Monitor the fan speed for the ESMA System Module.

Note down the acoustic level by listening to the noise of the fan assembly.

The fan speed is stable and does not oscillate.

6 Compare the acoustic noise in steps 1 and 5. The acoustic noise generated by the BTS fan modules is perceived to be lower in step 5 than in step 1.



DN0749988Issue 2-0 en18/01/2008

2.7.16 Runtime Diagnostics and BTS Alarms

Overview Flexi EDGE BTS Fault Management deals with detection of fault conditions that might exist or develop in the BTS units. On detection of fault, they are mapped to logical objects (BCF, BTS or TRX) and reported to active clients Flexi EDGE BTS Manager and BSC. The alarms are cancelled after rectification of the problem either automatically or manually.

Scope of testing The scope of the test plan is to test the fault detection and reporting of the BTS units at BTS start-up and when the BTS is operational.

Only a few representative alarms are considered for scope of this testing as reporting of most of the alarms is verified in test plans for other features.

Test cases

Pos Name Comment

1 Alarm Reporting in case of Units connected at Illegal Port

6+6

2 Alarms Reporting for Missing ECxx RTC Module at Startup

12 omni, RF Cabling defined in SCF file

3 Alarm Reporting for Incorrect RF Cabling with ECxx RTC Module

6+6, BB hopping

4 Alarm Reporting for Incorrect RF Cabling with ERxx DDU Module

2+4+2, RF Hopping

5 Alarm Reporting for Missing ERxx DDU Module at Startup

2+4+2

6 Alarms Reporting for Missing Optical Cable between Central and Remote EOCA unit at Startup

2 + 4 + 2 EXxA TRX Module 1, 2, and 3 on EOCA unit 1 EXxA TRX Module 4 on EOCA unit 2

2.7.16.1 Alarm Reporting in case of Units Connected at Illegal Port

The purpose of the test case is to verify that the BTS SW reports alarms when the ESEA System Extension Module and ECxx RTC module(s) are connected at wrong port/positions.

Test case execution


DN0749988 Issue 2-0 en 18/01/2008


243 (381)

Pre-setup:

• Configure the site in the BSC per the configuration used.

• Flexi EDGE BTS Manager is connected at LMP port of ESMA system module.

• ECxx RTC Modules are connected at port 5 and port 6 of the ESMA System Module.

• ESEA System Extension Module is connected at port 1 of ESMA System Module.

• EXxx TRX Modules are connected to ESEA System Extension Module at correct positions (EXxx TRX Module 1... 6 at port no. 1 .. 6 of ESEA System Extension Module in that order)

• The BTS is powered off.


1 Power on the BTS.

Observe the BTS site coming up.

Observe the state of BTS Modules at the Flexi EDGE BTS Manager.

The ESMA System Module is operational.

The ESEA System Extension Module is shown as illegal unit (pale red coloured icon).

The ECxx RTC Module(s) is shown as illegal unit (pale red coloured icon).

2 Observe the LED display of the ECxx RTC Module and the ESEA System Extension Module.

LED display of ECxx RTC Module(s) is flashing red.

LED display of the ESEA System Extension Module is flashing red.

3 Observe the alarm at the Flexi EDGE BTS Manager and the BSC.

A 7600 "BCF Faulty: ESMA System Module has lost connection to all ECxx RTCs and EXxx TRXx" alarm is reported.

A 7602 “BCF notification:ECxx RTC module connected to wrong port” alarm is reported.

A 7602 “BCF notification: ESEA System Extension module connected to wrong port” alarm is reported.

Note: A 7606 “ESMA System module has lost connection to EXxx TRX module” alarm will be observed for some TRX objects before the 7600 BCF level alarm is reported.

4 Power off the BTS.

Make the correct connections.

Connect the ECxx RTC Module at port 1 and port 2 of the ESMA System Module.

-



DN0749988Issue 2-0 en18/01/2008


Connect the ESEA System Extension Module at port 6 of the ESMA System Module.

5 Power on the BTS.

Observe the Base Station view from Flexi EDGE BTS Manager.

The site comes up and all the BTS units are visible in the Base Station view of the BTS Manager.

All the configured TRX objects come to Supervisory state.

6 Observe the alarms at the Flexi EDGE BTS Manager and the BSC.

No unexpected alarms are visible in the alarms window.

2.7.16.2 Alarms Reporting for Missing ECxx RTC Module at Startup

The purpose of the test case is to verify that the BTS SW detects the condition of a missing ECxx RTC module in the sector and raises a sector level alarm. The sector level alarm is cancelled when the fault condition is rectified.


• Configure the site in the BSC as specified by the particular configuration used.

• Flexi EDGE BTS Manager is connected at LMP port of ESMA system module.

• No ECxx RTC module is connected at startup.

• The BTS is powered off.


1 Power on the BTS.

The ESMA system module, EXxx TRX modules is seen in the Base Station View of the Flexi EDGE BTS Manager.

2 Check the Alarm window of Flexi EDGE BTS Manager.

Alarm 7606 "TRX Faulty: TRX unable to carry traffic; ECxA connection is missing or not operational" is reported for all TRXs but one in the sector.

For the last TRX the alarm is reclassified as alarm 7603 "BTS Faulty: BTS is unable to carry traffic; ECxA missing or not operational" alarm is reported.

3 Check the active alarms in the BSC using MML command ZEOL:<bcf_id>;

Alarms mentioned in expected output of step 2 is visible in the BSC.

4 Reconnect the ECxx RTC module(s). The ECxx RTC Module is seen in the Base


DN0749988 Issue 2-0 en 18/01/2008


245 (381)


Observe the ECxx RTC module(s) in the Flexi EDGE BTS Manager.

Check the alarms at the Flexi EDGE BTS Manager.

Station View of the Flexi EDGE BTS Manager.

All the alarms are cancelled.

The sector is reset and after reset no alarm is seen.

5 Check the active alarms in the BSC using MML command ZEOL:<bcf_id>;

No alarm is visible on the TRX or BTS object.

2.7.16.3 Alarm Reporting for Incorrect RF Cabling with ECxx RTC Module

The purpose of the test case is to verify BTS software maps alarms to the correct TRX Objects when cables faults are detected on the BTS units with ECxx RTC module. Alarm handling is verified at startup as well as supervisory state. Alarms are cancelled when the fault condition is rectified.


1. Configure the site in the BSC as specified in configuration.

2. Tx and Rx cabling is missing from a EXxx TRX Module(s) to ECxx RTC Module of BTS object 2.

3. Flexi EDGE BTS Manager is connected at LMP port of ESMA System Module.

4. The site is uncommissioned.

5. The BTS site is powered off.


1 Power on the BTS.

Observe the BTS Site coming up.

Commission the BTS with RF cabling autodetection enabled.

The ESMA System Module, EXxx TRX Modules and the ECxx RTC Module are visible in the Base Station View of the Flexi EDGE BTS Manager.

Site is commissioned successfully.

2 Check the alarms reported to the Flexi EDGE BTS Manager and the BSC.

The Tx and Rx Cabling information on EXxx TRX Module is not detected with ECxx RTC Module.

Alarm 7606 "TRX Faulty : ECxx RTC module has detected no Tx power during RF cable autodetection" is reported to active clients for TRX objects (for which Tx Cable is disconnected or faulty) of the EXxx TRX Module(s).



DN0749988Issue 2-0 en18/01/2008


3 Connect Tx Cable from EXxx TRX Module with a ECxx RTC Module correctly.

Reset BTS object 2 with RF Auto-Detection from Flexi EDGE BTS Manager.

Check the Alarm window of Flexi EDGE BTS Manager.

On reset, BTS object 2, The Tx Cabling information on EXxx TRX module is detected with ECxx RTC module.

Alarm 7606 "TRX Faulty: EXxx TRX module detected no Rx signal during RF cable autodetection" is observed for TRX objects (for which Rx Cable is disconnected or faulty) of EXxx TRX Module(s).

4 Connect Rx Cable from EXxx TRX Module with a ECxx RTC Module correctly.



The Tx and Rx Cabling information on EXxx TRX module(s) is detected with ECxx RTC module.

No active alarm is present.

TRX objects of EXxx TRX module(s) operational state shall be supervisory and object state enabled.

5 Place calls on the TRX(s) of BTS object 2. Calls are successful, and verified by listening to speech and verifying at the BSC end with ZERO MML command.

6 Disconnect Tx Cable from EXxx TRX (Non-BCCH) module(s) with an ECxx RTC Module in BTS object 1.

Reset BTS object 1 from Flexi EDGE BTS Manager with RF cabling autodetection enabled.

Alarm 7606 "TRX Faulty: ECxx RTC module has detected no Tx power during RF cable autodetection" is reported to active clients for TRX objects (for which Tx Cable is disconnected) of EXxx TRX module(s).

7 Observe the CS calls started on the BTS object 2.

CS call is going on in the BTS object 2 with no disruption.

8 Connect the Tx Cable from the EXxx TRX module(s) to an ECxx RTC module.

Reset BTS object 1 from Flexi EDGE BTS Manager with RF cabling autodetection enabled.


Check the status of the TRX Objects from Base station view.

On reset, BTS object 1, Tx Cabling information on EXxx TRX module(s) is detected with ERxx DDU module.

TRX objects of EXxx TRX module(s) are in operational state and object state enabled.

No active alarm is present.

9 Place calls on the TRX(s) of BTS object 1. Calls are successful, as verified by manually listening to speech and by verifying at the BSC end by using ZERO MML command.


DN0749988 Issue 2-0 en 18/01/2008


247 (381)

2.7.16.4 Alarm Reporting for Incorrect RF Cabling with ERxx DDU Module

The purpose of the test case is to verify BTS software maps alarms to the correct TRX Objects when cables faults are detected on the BTS units with ERxx DDU module. Alarm handling is verified at startup as well as supervisory state. Alarms are cancelled when the fault condition is rectified.


1. Configure the site in the BSC as specified in configuration.

2. Tx and Rx cabling is missing from a EXxx TRX module(s) to ERxx DDU module of BTS object 1.

3. Flexi EDGE BTS Manager is connected at LMP port of ESMA System Module.




1 Power on the BTS.


Commission BTS with RF cabling autodetection enabled.

The ESMA System Module, EXxx TRX Modules and the ERxx DDU Module are visible in the Base Station View of the Flexi EDGE BTS Manager.


2 Check the alarm reported to the Flexi EDGE BTS Manager and the BSC.

Alarm 7606 "TRX Faulty: EXxx TRX module detected no connection to ERxx DDU via RF cable autodetection" is reported to active clients for TRX objects (for which Tx cable is disconnected or faulty) of the EXxx TRX Module(s).

3 Connect Tx cable from EXxx TRX module(s) with an ERxx DDU module correctly.



On reset, BTS object 1, Tx Cabling information on EXxx TRX module(s) is detected with ERxx DDU module.

Alarm 7606 "TRX Faulty: EXxx TRX module detected no connection to ERxx DDU via RF cable autodetection" is observed for TRX objects (for which Rx cable is disconnected or faulty) of EXxx TRX module.

4 Connect Rx cable from EXxx TRX module(s) with a ERxx DDU Module correctly.


The Tx and Rx cabling information on EXxx TRX Module(s) is detected with ERxx DDU Module.

No active alarm is seen.

TRX objects of EXxx TRX Module(s) are in



DN0749988Issue 2-0 en18/01/2008



operational state shall be supervisory and object state enabled.

5 Place calls on the TRX(s) on BTS object 1. Calls are successful, as verified by manually listening to speech and by verifying at the BSC end by using ZERO MML command.

6 Disconnect Tx cable from EXxx TRX (Non-BCCH) module(s) with a ERxx DDU module of BTS object 2.

Reset BTS object 2 from Flexi EDGE BTS Manager with RF cabling autodetection.

Alarm 7606 "TRX Faulty: EXxx TRX module detected no connection to ERxx DDU via RF cable autodetection" is reported to active clients for TRX objects (for which Tx cable is disconnected) of the EXxx TRX Module(s).

7 Observe the CS calls started on the BTS object 1.

CS call is going on in the BTS object 1 with no disruption.

8 Connect Tx cable from EXxx TRX Module(s) with an ERxx DDU Module correctly.



On reset, BTS object 2, Tx Cabling information on EXxx TRX Module(s) is detected with ERxx DDU Module.

TRX objects of EXxx TRX Module(s) are in operational state shall be supervisory and object state enabled.


9 Place calls on the TRX(s) of BTS object 2. Calls are successful, as verified by manually listening to speech and by verifying at the BSC end by using ZERO MML command.

2.7.16.5 Alarm Reporting for Missing ERxx DDU Module at Startup

The purpose of the test case is to verify that the BTS software maps alarms to the correct TRX Objects when no ERxx DDU Module is connected on the BTS units. Alarm handling is verified at startup. The alarms are cancelled when the fault condition is rectified.


1. Configure the site in the BSC as specified in the configuration.

2. The ERxx DDU Module is not connected to the EXxx TRX Module for BTS object 1.

3. Flexi EDGE BTS Manager is connected at the LMP port of the ESMA system module.



DN0749988 Issue 2-0 en 18/01/2008


249 (381)



1 Power on the BTS.


Commission BTS with RF cabling autodetection enabled.

The ESMA System Module is visible but no ERxx DDU Module is visible in the Base Station View of the Flexi EDGE BTS Manager.



Check the active alarms in the BSC using MML command ZEOL:<bcf_id>;

Alarm 7606 "TRX Faulty: EXxx TRX module has no combiner ERxx DDU or ECxx RTC module present" is reported for all TRX objects in the sector. The last alarm is reported as a BTS level alarm as below.

Alarm 7603 "TRX Faulty: EXxx TRX module has no combiner ERxx DDU or ECxx RTC module present" is reported to active clients for BTS object.

3 Connect the bus cable of ERxx DDU module with an EXxx TRX module.

HW reset the EXxx TRX module (in BTS object 1) to which ERxx DDU Module is connected from Flexi EDGE BTS Manager.

Check the alarms at Flexi EDGE BTS Manager and the BSC.

Due to HW reset of the EXxx TRX Module, the following alarms will be raised for a short period of time.

Alarm 7606 "TRX Faulty : ESMA System module has lost connection to EXxx TRX module" is reported for all TRX objects in the sector. The last alarm is reported as a BTS level alarm as below.

Alarm 7603 "TRX Faulty : ESMA System module has lost connection to EXxx TRX module" is reported to active clients for BTS object.

Alarms listed above are cancelled when EXxx TRX module comes up again. But the following alarms are raised since cabling information is still not present.

Alarm 7606 "TRX Faulty: EXxx TRX module has no combiner ERxx DDU or ECxx RTC module present" is reported for all TRX objects in the sector. The last alarm is reported as a BTS level alarm as below.

Alarm 7603 "TRX Faulty: EXxx TRX module has no combiner ERxx DDU or ECxx RTC module present" is reported to active clients for BTS object.

The ERxx DDU Module visible in the Base Station View of the Flexi EDGE BTS Manager.

4 Reset BTS object 1 with RF Autodetection The Tx and Rx cabling information on EXxx



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output from Flexi EDGE BTS Manager.


TRX module(s) is detected with ERxx DDU module.

No active alarms are seen.

5 Check the status of the TRX objects from Base station view.

TRX objects in BTS object are in operational state and object state is enabled.

6 Place calls on any of the TRX of the BTS object.

The calls are successful, as verified by manually listening to speech and by verifying at the BSC end by using ZERO MML command.

2.7.16.6 Alarms Reporting for Missing Optical Cable between Central and Remote EOCA unit at Startup

The purpose of the test case is to verify that BTS software maps alarms to the correct TRX Objects when the optical cable between central and remote EOCA Optical Converter module is not connected for one of the sectors. Alarm handling is verified after BTS site startup.


Configure the site in the BSC as specified in configuration.

EXxx TRX Modules are connected to EOCA Optical Converter module units at correct positions (EXxx TRX Module 1,2, and 3 to EOCA Optical Converter module unit no.1 and EXxx TRX Module 4 to EOCA Optical Converter module unit no. 2).

Flexi EDGE BTS Manager is connected at the LMP port of ESMA System Module.

Site is uncommissioned.

BTS site is powered off.

Optical cable between Remote EOCA Optical Converter module unit 2 and central EOCA Optical Converter module unit 2, serving Sector 3 is not connected.


1 Power on the BTS.

Observe the BTS Site coming up.

Commission the BTS with RF cabling autodetection enabled.

The ESMA System Module is visible but EOCA Optical Converter module unit 2 is not visible in the Base Station View of the Flexi EDGE BTS Manager.



DN0749988 Issue 2-0 en 18/01/2008


251 (381)



Check the active alarms in the BSC using MML command ZEOL:<bcf_id>;

Alarm 7606 "TRX Faulty: ESMA System module has lost connection to EXxx TRX module" is reported for all TRX objects except for BCCH TRX object in the sector 3.

Alarm 7603 "TRX Faulty: ESMA System module has lost connection to EXxx TRX module" is reported to active clients for BTS object 3.

3 Connect the optical cable between the Central and Remote EOCA Optical Converter module unit no. 2.

Check the alarm at Flexi EDGE BTS Manager and the BSC.

Check the Base station view at Flexi EDGE BTS Manager.

The alarms listed in step 2 are cancelled when the EXxx TRX module comes up again.

Since the cabling source is RF cables autodetection, the following alarms will be seen for all the TRX objects except BCCH TRX object in the sector :

Alarm - "7606 - EXxx TRX detected no connection to ERxx DDU via RF cable autodetection".

Alarm- "7606 - EXxx TRX detected no connection to ERxx DDU via RF cable autodetection" is reported for the BTS object.

The Central and Remote EOCA Optical Converter module unit no. 2 are visible in the Base Station view of the Flexi EDGE BTS Manager.

4 Reset BTS object 3 with RF-Autodetection from Flexi EDGE BTS Manager.


The Tx and Rx cabling information on EXxx TRX module(s) is detected with ERxx DDU module.


5 Check the status of the TRX objects from Base station view.

TRX objects in BTS object are in operational state and object state enabled.

6 Place calls on any of the TRX of the BTS object. Calls are successful, as verified by manually listening to speech and by verifying at the BSC end by using ZERO MML command.



DN0749988Issue 2-0 en18/01/2008

2.7.17 Real Time Update to the BTS

Overview The BSC sends the current time (date and time) to Nokia Flexi EDGE Base Station during the initialisation procedure and periodically. The BTS initialises its real time clock accordingly. The real time can be used for various purposes, such as in update for internal and external Q1 devices, commissioning reports, and alarms.

Scope of testing The scope of testing is to verify that the BTS is always updated with the real time at the BSC.

Test cases

Pos Name Comment

1 BTS real time adjustment and broadcast to Q1 devices

--

2.7.17.1 BTS Real Time Adjustment and Broadcast to Q1 Devices

This test case verifies that the ‘Real Time’ of the alarm displayed is the time at the BSC when the alarm was raised. Changing the time at the BSC changes the Real Time of the subsequent alarms.


• LMU connected to the BTS site as a Q1 device


• BTS Polling enabled at the BSC for the LMU using the MML command 'ZWQA'.

• The BTS site has a Flexbus interface towards the BSC via a FIU19 device.

Pre-setup:

• The BTS is commissioned and in Supervisory state.



• The LMU is connected to the BTS site as a Q1 device and no unexpected alarms are active for the LMU. Make sure that the GPS signal is connected to the LMU.


DN0749988 Issue 2-0 en 18/01/2008


253 (381)


1 Check the time at the BSC by command ZDCD The current time of the BSC is given in format (YYYY-MM-DAY) (HOUR-MIN-SEC)

2 Using 'Append' commissioning, configure Interface 2 of the FIFA card into use but without connecting any Flexbus link to it.

BTS ALARM start '8066' with alarm text 'AIS 2M' is reported for Interface 2 of the FIFA card.

3 Remove the GPS signal being connected to the LMU.

LMU raises a critical Q1 alarm '8048 - Loss of incoming signal' on TRE2. Verify on BTS Manager that the Q1 alarm time is in line with the real timestamp of the BSC.

BTS ALARM ‘8048’ with alarm text as ‘Loss of incoming signal’ is reported for TRE2 and is sent on the Abis to the BSC. Verify that the Q1 alarm time is in line with the real timestamp of the BSC.

4 Change the time of the BSC by 30 minutes earlier time using the command ZDCS (provide current date in format (YYYY-MM-DAY) and time in format (HOUR-MIN-SEC) )

The time at the BSC is changed. Execute test step 1 to verify the changed time.

5 Reconnect the GPS signal to the LMU. LMU cancels critical Q1 alarm '8048 - Loss of incoming signal' on TRE2. Verify on BTS Manager Alarm history that the Q1 alarm cancel time is in line with the real timestamp of the BSC.

BTS ALARM ‘8048’ with alarm text as ‘Loss of incoming signal’ is cancelled for TRE2 and is sent on the Abis to the BSC. Verify that the Q1 alarm time is in line with the real timestamp of the BSC.

The alarm time is approximately 30 minutes previous to the earlier alarm in step 3.

6 Use 'Append' commissioning to deactivate Interface 2 of the FIFA card.

BTS ALARM cancel '8066' with alarm text as 'AIS 2M' is reported for Interface 2 of FIFA card. The alarm time is approximately 30 minutes previous to the earlier alarm in step 2.

2.7.18 BTS SW Background Downloading

Overview The BTS SW can be updated by downloading BTS SW package from the BSC, or locally with Flexi EDGE BTS Manager. After downloading the SW is completed, resetting the site activates the BTS SW.



DN0749988Issue 2-0 en18/01/2008

Scope of testing The scope of testing is to verify the download of SW to the BTS from the locally connected Flexi EDGE BTS Manager and the BSC.

Settings 1. .Attach package and start downloading of BTS SW from BSC: >>>ZEWA:BCFno:NW/BU/FB:Build ID:;

2. Activating a BTS SW build from BSC: >>>ZEWV:BCFno:NW/BU/FB:;

Test cases

Pos Name Comment

1 Successful background SW download during normal operation from Flexi EDGE BTS Manager

EP1.1 SW upgrade to EP1.1 CD1 SW

2 Successful background SW download during normal operation from the BSC

EP1.1 SW upgrade to EP1.1 CD1 SW, 16k O&M LAPD

3 Successful activation of SW from the BSC when already in flash

16k O&M LAPD

2.7.18.1 Successful Background SW Download during normal operation from Flexi EDGE BTS Manager

This test case verifies that the Flexi EDGE BTS Manager operator is successfully able to do background SW download of BTS SW to a Flexi EDGE Base Station in 'Supervisory' state.



• The version of the MF should not be the same as either the active or standby version of the MF in the BTS.

• Software Package ‘A’ is running and active. Software Package ‘B’ is a standby package.

• The latest software Package ‘C’ is available in the BSC but not yet attached to the BCF. The software upgrade of the BTS site has to be done with this build only.

• Flexi EDGE BTS Manager is connected to the BTS locally at the LMP port.


DN0749988 Issue 2-0 en 18/01/2008


255 (381)

• Generate alarms on TRX objects 1, 2 in sector 1 by stopping the FAN rotation. Alarm 'start' 7607 with alarm text "TRX operation degraded: EXxA Fan is out of order" is sent to the BSC and Flexi EDGE BTS Manager for TRX objects 1 and 2. Note that if sector 1 has only two TRX objects, then one of the alarms will get reclassified to Alarm 7604 "BTS operation degraded: EXxA Fan is out of order".


1 Enable windows firewall from the control panel of your local PC/laptop through which Flexi EDGE BTS Manager is connected.

Firewall is enabled successfully.

2 Place 1 pair of CS call and 1 PS call in each sector.

Calls are made successfully.

3 Navigate to the “Update SW” screen on Flexi EDGE BTS Manager using the menu option “BTS SW SW Update”.

The Update SW dialog is displayed.

4 Click the “Master file” button and select the software package “C”. Click the “Update SW” button.

Download is not started. A pop-up window appears on the screen with message "SW Download Failed due to error in FTP connection".

5 Change the window settings as per the message in the pop-up window.

Windows settings are changed successfully.

6 Navigate to the “Update SW” screen on Flexi EDGE BTS Manager using the menu option “BTS SW SW Update”.

The Download of the SW starts and the download progress of the SW is displayed to the user.

7 After the download is complete, verify the versions of the SW packages in the flash from Flexi EDGE BTS Manager.

(This is done using "SW version Inquiry" functionality through BTS SW Versions menu-item from Main Menu.)

Software packages "A" and "C" are present in the BTS as follows:

Running Package :------------> "A"

Active Package :------------> "C"

Standby Package :------------> "A"

8 Now, attach SW "C" at the BSC using the MML command ZEWA

BTS does not download "C" as it is already present in the 'Active' partition.

This is verified on Abis analyser on OMUSIG by observing messages "BTS_START_DOWNLOAD_REQ" from BSC and a "package exists" message as a response from BTS Site.

9 Observe the PS and CS calls on BTS started in step 1.

CS and PS calls are still going on with no disruption.

10 Reset the BCF by clicking on “BCF Reset” button on the BCF properties view in Flexi EDGE BTS Manager.

The BCF is reset.

BCF comes in supervisory state after reset.



DN0749988Issue 2-0 en18/01/2008


Verify that the site comes in supervisory state.

11 Verify the versions of the SW packages in the flash from Flexi EDGE BTS Manager.


Software packages "A" and "C" are present in BTS as follows:


Active Package :------------> "A"

Standby Package :------------> "C"

12 Verify from the Flexi EDGE BTS Manager that BTS ALARM 7607/7604 is still active for TRX objects 1 and 2.

BTS ALARM is active for TRX objects 1 and 2 with alarm 7607/7604 and alarm text "TRX/BTS operation degraded: EXxA Fan is out of order" as verified from Flexi EDGE BTS Manager and from the BSC using ZEOL MML command.

13 Remove the 'FAN rotation' blocking material from DTRX 1.

BTS ALARM cancel is sent for TRX objects 1 and 2 with alarm 7607/7604 and alarm text "TRX/BTS operation degraded: EXxA Fan is out of order" as verified from Flexi EDGE BTS Manager and the BSC using ZEOL MML command.

14 Activate the newly downloaded software package "C" using MML command ZEWV.

It is observed on the BSC that the command is successfully executed.

Downloaded SW is taken into use after BCF reset but no software download takes place (as SW is already available at BTS).

BTS comes up with the new SW package "C".


Software packages "A" and "C" are present in BTS as

Running Package :------------> "C"

Active Package :----------------> "C"

Standby Package :-------------> "A"


Calls are successfully made.

2.7.18.2 Successful Background SW Download during Normal Operation from the BSC

This test case verifies the successful background software download of Flexi DGE BTS SW from the BSC to a Flexi EDGE BTS Site in 'Supervisory' state.

Test case execution


DN0749988 Issue 2-0 en 18/01/2008


257 (381)

Pre-setup:


• The version of the MF should not be same as either the active or standby version of the MF in the BTS.

• Software package ‘A’ is running and active. Software package ‘B’ is in standby.

• The latest software package ‘C’ is available with BSC. The software upgrade of the BTS site has to be done with this build only.

• Generate alarms on TRX objects 1and 2 in sector 1 by stopping the FAN rotation. Alarm 7607 with alarm text as "TRX operation degraded: EXxA Fan is out of order" for TRX objects 1 and 2. Note that if sector 1 has only two TRX objects, then one of the alarms will get reclassified to alarm 7604 "BTS operation degraded: EXxA Fan is out of order’.




2 Attach the latest software package "C" with the BCF at the BSC using command ZEWA.

Verify that software package "C" is attached with BCF as NEW using MML command ZEWO.

Command executed, observed on the BSC.

The BSC shows that software package "C" is attached with the BCF.

3 Observe the software download over Abis Analyser.

Background software download start is verified on Abis analyser on OMUSIG by observing messages "BTS_START_DOWNLOAD_REQ", “FILE_RECORDS” messages between the BTS and the BSC.

4 After the software download is complete, verify the versions of the SW packages in the flash from BTS Manager.


Software package "A" and "C" are present in BTS as:




Verify at Abis analyser on OMUSIG

"BTS_SW_SAVE_REQ" message is sent by the BSC to BTS which is acknowledged by the BTS. This confirms that download is complete.



DN0749988Issue 2-0 en18/01/2008


5 Observe the PS and CS calls started in step 1 on the BTS.

CS and PS calls are still going on with no disruption.

6 Reset the BCF by clicking the “BCF Reset” button on the BCF properties view in Flexi EDGE BTS Manager.

Verify that the site comes in supervisory state.

The BCF is reset.

BCF comes in supervisory state after reset.

7 Verify the versions of the SW packages in the flash from BTS Manager.


Software package "A" and "C" are present in BTS as

Running Package :-----------> "A"

Active Package :------------> "A"

Standby Package :------------> "C"

8 Verify from the BTS Manager that BTS ALARM 7607/7604 is still active for TRX objects 1 and 2.

BTS ALARM is active for TRX objects 1 and 2 with alarm 7607/7604 and alarm text "TRX/BTS operation degraded: EXxA Fan is out of order" as verified from BTS Manager and the BSC using ZEOL MML command.


BTS ALARM cancel is sent for TRX objects 1 and 2 with alarm 7607/7604 and alarm text as "TRX/BTS operation degraded: EXxA Fan is out of order" as verified from BTS Manager and the BSC using ZEOL MML command.

10 Activate the newly attached software package "C" using MML command ZEWV.


Downloaded SW is taken into use after the BCF reset. No other software download takes place.

BTS comes up with the new SW package "C".


Software packages "A" and "C" are present in BTS as



Standby Package :-------------> "A"


Calls are successfully made.


DN0749988 Issue 2-0 en 18/01/2008


259 (381)

2.7.18.3 Successful Activation of SW from the BSC When Already in Flash

This test case verifies that a Flexi EDGE BTS site does not background download a SW package when the same package already exits in the flash memory of the BTS site.



• Software package ‘A’ is 'running' and 'active' while SW package ‘B’ is in 'standby'.

• The BCF under test has only SW package ‘A’ present in the BSC at, for example, the ‘NW’ partition. Hence, the ‘BU’ and ‘FB’ partitions are free at the BSC for this test BCF.

• Generate alarms on TRX objects 1, 2 in sector 1 by stopping the FAN rotation. Alarm 7607 with alarm text as "TRX operation degraded: EXxA Fan is out of order" for TRX objects 1,2. Note that if sector 1 has only two TRX objects, then one of the alarms will get re-classified to alarm 7604 "BTS operation degraded: EXxA Fan is out of order’.




2 Attach the software package "B" with the BCF at the BSC using command ZEWA.

Verify the software package "B" is attached with the BCF as NEW using MML command ZEWO.


BSC shows that software package "B" is attached with the BCF.

3 Observe the status of software download over Abis Analyser.

Software download does not take place as BCF already has package “B”.

BTS sends "package already exists" in response to BSC's "BTS_START_DOWNLOAD_REQ"



Software package "A" and "B" are present in BTS as


Active Package :------------> "B"


5 Observe the PS and CS calls on BTS. CS and PS calls are still going on with no disruption.

6 Reset the BCF by clicking on “BCF Reset” button on the BCF properties view in Flexi

The BCF is reset.



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output EDGE BTS Manager.


(using "SW version Inquiry" functionality through BTS SW Versions menu-item from Main Menu.)

Software packages "A" and "B" are present in BTS as

Running Package :-----------> "A"

Active Package :-----------> "A"

Standby Package :------------> "B"

8 Verify from the BTS Manager that BTS ALARM 7607/7604 is still active for TRX objects 1 and 2.

BTS ALARM is active for TRX objects 1,2 with alarm 7607/7604 and alarm text "TRX/BTS operation degraded: EXxA Fan is out of order" as verified from BTS Manager and the BSC using ZEOL MML command.


BTS ALARM cancel is sent for TRX objects 1 and 2 with alarm 7607/7604 and alarm text "TRX/BTS operation degraded: EXxA Fan is out of order" as verified from BTS Manager and the BSC using ZEOL MML command.

10 Activate the software package "B" using MML command ZEWV.

Command executed, observed on BSC.

After a BCF reset, the BTS starts and receives a BTS_START_DOWNLOAD_REQ message for Build B.

BTS site responds with 'package exists' but resets itself to swap its active and standby partitions. No other software download takes place.

After the second reset, the BTS starts successfully and reaches 'Supervisory' state with the new SW package "B".


Software packages "A" and "B" are present in the BTS as

Running Package :------> "B"

Active Package :------> "B"

Standby Package :------> "A"

12 Place CS and PS calls in each sector. Calls are successfully made.

2.7.19 TX Antenna VSWR Supervision

Overview


DN0749988 Issue 2-0 en 18/01/2008


261 (381)

The BTS supervises the Voltage Standing Wave Ratio (VSWR) of antennas of RTC/DDU. The VSWR shall be calculated from forward and reflected power measurements of the antenna ports. DDU/RTC continuously monitors the VSWR measurements, validity and input Transmitted power for all antennas.

Antenna Monitoring provides the following functionalities in different scenarios.

When input Transmitted power to an antenna of DDU/RTC is not sufficient following actions are taken according to the scenario present:

If BCCH TRX object is connected to this antenna line, a 7606 "Too low power" alarm is started. It cannot be cancelled automatically.

If only TCH TRX objects are connected to this antenna line, no action is taken.

When VSWR at an antenna of DDU/RTC exceeds the minor or major VSWR thresholds, defined during commissioning, the following actions are taken according to the scenario present:

If VSWR measurement exceeds the minor alarm threshold, then the alarm 7607 "VSWR operation degraded" is started in around 30 seconds.

If the measurement is valid and the VSWR measurement is again below the minor alarm threshold, but minor alarm is active, then alarm 7607 is cancelled.

If VSWR measurement exceeds the major alarm threshold, then alarm 7606 "VSWR broken" is given in around 60 seconds. This alarm cannot be cancelled automatically.

When there is an invalid VSWR at an antenna (Input Transmitted power at an antenna must exceed 25.5 dBm to have a valid VSWR), the following actions are taken according to the scenario present:

If the BCCH TRX object is connected to this antenna line and BCCH power level is 0…2, alarm 7606 "Too low power" is given. It is not automatically cancellable.

If BCCH TRX object or only TCH TRX objects are connected to this antenna line and BCCH power level is 3…15, no action is taken.

Scope of testing • Only BCCH Antenna Monitoring is in the scope of testing. Antenna

Monitoring is not available for only TCH TRX antennas.

• No Transmission Input Handling.

• VSWR Minor threshold crossed Handling.

• VSWR Major threshold crossed Handling.

• Antenna Supervision Alarm Handling during Abis breaks.



DN0749988Issue 2-0 en18/01/2008

• VSWR Alarm Handling interacting with different Object Management Operations.

• VSWR Alarm Handling when Thresholds for Minor and Major are the same.

• BB Hopping configurations are not included as there is no Antenna Boosting and Antenna Monitoring is only for BCCH Antenna.

Settings:

VSWR Thresholds: VSWR Thresholds are defined for each antenna during Commissioning. The ranges of VSWR Thresholds are given below. VSWR Major and Minor Alarms will be generated, if the defined thresholds are exceeded.

VSWR Alarm VSWR Ratio (Default)

Range (VSWR Ratios)

VSWR Minor Alarm 2.1 1.5 - 2.9

VSWR Major Alarm 3.1 2.7 - 3.5

Test cases

Pos Name Comment

1 Low Power Alarm Handling with Abis Breaks.

4+4, 2 Way combining

2 VSWR Alarm reporting when different and when same VSWR Minor/Major Thresholds configured.

4+4, 2-way combining

3 VSWR Alarm Handling with Lock/Unlock and Block/Unblock Operations.

6+6, RTC Combining

4 VSWR Alarm Handling with Lock/Unlock and Block/Unblock Operations.

8-Omni, 4-way combining.

2.7.19.1 Low Power Alarm Handling with Abis Breaks.

The purpose of this test case is to verify that Low Power Alarms are raised only because of no input transmission power at an Antenna when there is some disconnection in the Transmit path. Low Power Alarm should not be raised when transmission stops due to Abis Break.


• Power meter


DN0749988 Issue 2-0 en 18/01/2008


263 (381)


BTS site should be up and should be in supervisory state with PMAX at BSC set to 0.

Flexi EDGE BTS Manager is connected locally to the BTS Site.


1. Observe the Transmitted Power at Antenna Port A for both BCCH Transmission Line using Power meter.

The power at Antenna Port A is above 25.5 dBm.

2. Now disconnect the Tx Cable connected between the BCCH TRX and DDU/RTC connected to Antenna Port A (Main Antenna in case of RTC).

Observe the alarm at the BSC and Flexi EDGE BTS Manager.

The following alarm is raised for all the TRX connected to Antenna port A:

7606, TRX unable to carry traffic; too low input power level at ERxA(ECxA) Ant A path.

3. Reconnect the Tx cable disconnected in step 2.

Observe the alarm at Flexi EDGE BTS Manager and the BSC .

Verify that no 7606 alarm cancellation is reported.

4. Lock/Unlock the BTS object from the BSC.

Observe the alarm at Flexi EDGE BTS Manager and the BSC.

Verify that 7606 alarms are cancelled.

5. Place a call on TRX of the BTS Site, connected to the Antenna Port A and Port B (if used as per configuration).

The call is placed successfully.

6. Break the Abis Link for 95 seconds. A critical alarm 8050, "Loss if Incoming 2M signal " is reported at Flexi EDGE BTS Manager.

Observe that no alarm related to Antenna Monitoring is reported.

7. Reconnect the Abis Link for 65 seconds. The critical alarm 8050, "Loss of Incoming 2M Signal " is cancelled. Cancellation is reported to Flexi EDGE BTS Manager and the BSC.

Observe that there is no unexpected Alarm start/cancellation.

8. Repeat steps 6-7 for 10 times. Similar observations are seen as in respective steps.

9. Repeat steps 2-5. Similar observations are seen as in respective steps.



DN0749988Issue 2-0 en18/01/2008

2.7.19.2 VSWR alarm reporting when different and when the same VSWR Minor/Major Thresholds configured

The purpose of this test case is to verify:

• Generation of VSWR alarms when both the VSWR Major and VSWR Minor thresholds defined are different. 7606 alarm is raised when VSWR minor threshold is crossed and 7606 alarm is raised when Major threshold is crossed.

• Generation of VSWR alarms when both the VSWR Major and Minor thresholds defined are the same. 7606 alarm is reported both at Flexi EDGE BTS Manager and the BSC for exceeding the VSWR threshold.


• VSWR Stub Tuner


Flexi EDGE BTS Manager is connected locally and its operation is normal.

BTS site is in supervisory state.


1 From the BSC, configure TRXs to transmit at power level in 0...2 range.

Correct power level is set.

2 Observe the Operational state of DDU/RTC at Flexi EDGE BTS Manager.

State of DDU/RTC is Supervisory state.

3 Make a CS call so that it is on TRXs transmitting from Antenna A (Main in case of RTC).

Verify that the call is successfully made.

4 Using VSWR stub tuner, degrade the VSWR of Antenna A (Main in case of RTC) so that it just crosses the Minor Alarm Threshold.

Watch Flexi EDGE BTS Manager Alarm window and active alarms on the BSC.

The following alarm is raised for all the TRX connected to Antenna A.

7607, TRX provides reduced traffic services; ERxA/ECxA antenna degraded (VSWR).

5 Observe the status of CS call. Verify that the call is still running successfully.

6 Using VSWR stub tuner, remove the degradation (now there is no VSWR on Antenna A)

Verify that alarms 7607 are cancelled.

7 Using VSWR stub tuner, degrade the VSWR of Antenna A (Main Antenna in case of RTC) so that it crosses the Major Alarm Threshold.

The following alarm is raised for all the TRX connected to Antenna A.

7606, TRX unable to carry traffic;


DN0749988 Issue 2-0 en 18/01/2008


265 (381)


Watch Flexi EDGE BTS Manager Alarm window and active alarms on the BSC.

ERxA/ECxA antenna broken (VSWR).

8 Observe the status of the CS call. Verify that the call is dropped.

9 Using VSWR stub tuner, remove the degradation so that it is above the minor alarm threshold.

No alarm is cancelled on Flexi EDGE BTS Manager or the BSC.

10 Lock/unlock the sector. All TRXs come in supervisory state and VSWR is still above minor alarm threshold, so alarms as in step 4 are raised.

11 Remove all the degradation of VSWR. The alarms 7607, for VSWR minor threshold crossed, are cancelled.

12 On Flexi EDGE BTS Manager, go to the Commissioning Wizard and change the VSWR Limits for the Antenna A as given below:

vswrMinorLimit 2.9

vswrMajorLimit 2.9.

Click the Send SCF button for recommissioning of the site.

The site is successfully commissioned.

13 Make a CS call so that it is on TRXs transmitting from Antenna A (Main in case of RTC)


14 Using the VSWR stub tuner, degrade the VSWR of Antenna A (Main Antenna in case of RTC) so that it crosses the Minor Alarm Threshold (same in this case).

Observe alarms on Flexi EDGE BTS Manager and active alarms at the BSC.

The cfollowing alarm is raised for all the TRX connected to Antenna A.

7606, TRX unable to carry traffic; ERxA/ECxA antenna broken (VSWR).

15 Observe the status of the CS call. Verify that the call is dropped.

16 Reduce the degradation so that there is no VSWR on the antenna.

No alarm is cancelled.

17 Lock and unlock the sector. Alarms 7606 are cancelled and the TRXs come up successfully to supervisory state.

18 Make a CS call so that it is on TRXs transmitting from Antenna A (Main in case of RTC).


2.7.19.3 VSWR alarm handling with Lock/Unlock and Block/Unblock Operations

The purpose of this test case is to verify Antenna Monitoring/VSWR Alarm Handling, for both antennas of Flexi EDGE Dual Duplexer Module, interacting with Object Management Functionalities (Lock/Block of TRX, BTS).



DN0749988Issue 2-0 en18/01/2008


• VSWR stub tuner


Flexi EDGE BTS Manager is connected locally and its operation is normal and there are no active alarms.

BTS site is in supervisory state.


1 Configure TRXs to transmit at power level in a 0...2 range. Set the power level in the range of 27dBm - 50dBm.

Correct power level is set.

2 Observe the operational state of DDU/RTC. State of DDU/RTC is Supervisory.

3 Using the VSWR stub tuner, degrade the VSWR of Antenna A so that it just crosses the Minor Alarm Threshold.

Watch the Flexi EDGE BTS Manager Alarm window and active alarms on the BSC.

The following alarm is raised for all the TRXs connected to Antenna A.

7607, TRX provides reduced traffic services; ERxA antenna degraded (VSWR).

4 Lock a TRX connected to Antenna A and then unlock it.

The alarm for the TRX is cancelled when the TRX is locked and reported again when it is unlocked.

5 Block a Non-BCCH TRX connected to Antenna A from Flexi EDGE BTS Manager, and once it is blocked, unblock it.

The alarm for the TRX is cancelled when the TRX is blocked and reported again when it is unblocked.

6 Lock the sector and then unlock it. The alarms for all the TRX of the sector are cancelled when the sector is locked and are reported again when the sector is unlocked.

7 Block the sector from Flexi EDGE BTS Manager and once it is blocked, unblock it.

Alarm for all the TRX of the sector are cancelled when the sector is blocked and are reported again when the sector is unblocked.

8 Using the VSWR stub tuner, remove all the degradation of VSWR at Antenna A (now no VSWR exists on Antenna A).

VSWR alarm 7607 is generated for the TRX connected to Antenna A is cancelled.

Verify that there is no other unexpected alarm start/cancellation seen.

9 Using the VSWR stub tuner, degrade the VSWR of Antenna A so that it crosses the Major Alarm Threshold.

Observe the Flexi EDGE BTS Manager Alarm window and active alarms on the BSC.

The following alarm is raised for all the TRXs connected to Antenna A:

7606, TRX unable to carry traffic; ERxA antenna broken (VSWR)


DN0749988 Issue 2-0 en 18/01/2008


267 (381)


10 Using the VSWR stub tuner, remove all the degradation of VSWR at Antenna A (now no VSWR exists on Antenna A).


11 Repeat steps 4-5. Similar observations as in respective steps.

12 Lock the sector and then unlock it. Alarms for all the TRXs of the sector are cancelled and the TRXs come up successfully in supervisory state.

13 Using the VSWR stub tuner, degrade the VSWR of Antenna A so that it crosses the Major Alarm Threshold.

Observe the Flexi EDGE BTS Manager Alarm window and active alarms on the BSC.

The following alarm is raised for all the TRX connected to Antenna A:

7606, TRX unable to carry traffic; ERxA antenna broken (VSWR)

14 Using the VSWR stub tuner, remove all the degradation of VSWR at Antenna A (now there is no VSWR on Antenna A).


15 Block the sector from Flexi EDGE BTS Manager and once it is blocked, unblock it.

Alarms for all the TRXs of the sector are cancelled and the TRXs come up successfully in supervisory state.

16 Repeat steps 13-14. Similar observations as in respective steps.

17 Lock the BCF and then unlock it. The alarms for all the TRXs are cancelled and the TRXs come up successfully in supervisory state.

18 If Antenna B has BCCH TRX:

Repeat steps 3-17 for Antenna B.

Same observations as in the respective steps, but for TRXs connected to Antenna B.

2.8 Transmission

2.8.1 Transmission Fault Management

Overview The Flexi EDGE BTS will report to Flexi EDGE BTS Manager (if connected), BSC and NetAct transmission fault alarm (8000 series) for internal and external Q1 devices when Flexi EDGE BTS is configured for BTS polling. Scope of testing



DN0749988Issue 2-0 en18/01/2008

The scope of testing is to sample alarms from different functional areas of the BTS and the Nokia Q1 compatible product connected to the v.11 interface of the Flexi EDGE BTS. Test cases

Pos Name Comment

1 Remote BTS Alarm Handling and Reporting ( BTS Polling )

--

2.8.1.1 Remote BTS Alarm Handling and Reporting (BTS Polling)

The aim of this test case is to verify that remote alarm reporting works for a Flexi EDGE BTS that is configured for BTS polling.

The test will be done by sampling alarms from different functional areas of the BTS.


• FIEA transmission plug in unit

• MetroHub with 2 FXC E1 transmission units installed

Software tools:

• NetAct

Hardware tools:

• PDH analyser for E1 signal


1. The Flexi EDGE BTS is in supervisory state without alarms that affect the performance.

2. 64k OMU and 16k TRXSIG shall be used as granularity for the Abis.

3. To test the far end alarm, an FIEA transmission submodule is required.

4. The FXC E1 units are installed in the MetroHub unit slots 1 and 2, but all transmission interfaces are set to ‘Not in use’.


1 Verify the alarms at the BSC and NetAct before the alarm is triggered.

There is no active Flexi EDGE BTS alarm visible.


DN0749988 Issue 2-0 en 18/01/2008


269 (381)


2 Perform a test call. Test call is successful.

3 - Alarm: 8021 Loop to Interface

Trigger: Set IF2 in USE. Select "Loop to Interface" using the Flexi EDGE BTS Manager Application for IF2.

Check with ZEOL that the alarm is shown as active in the BSC.

Alarm "8050 Loss of incoming 2M Signal" is raised for Interface 2.

Alarm: "8021 Loop to Interface" is raised for interface 2 locally as well as at the BSC and NetAct and the Supplementary Information is correct.

4 - Alarm: 8021 Loop to Interface

Cancel: Wait until timer expires (default 600 seconds) or release IF Loop using the Flexi EGDE BTS Manager Application. Set IF2 out of USE.

Check with ZEOL that the alarm is cancelled in the BSC.

The alarm is cancelled and there is no active Flexi EDGE BTS alarm visible locally or at the BSC or NetAct.

5 Listen to the voice call. Test call is active and has a good voice quality.

6 - Alarm: 8179 Far-end

- Alarm: "8050 Loss of incoming 2M Signal"

Trigger: Set Interfaces 2 and 3 into "use" and only connect the Rx path of IF 2 to the Tx path of IF3.


Alarm "8179 Far-end Alarm" is raised for the Interface 2

Alarm "8050 Loss of incoming 2M Signal"

is raised for Interface 3.

Both alarms are raised locally as well as at the BSC and NetAct.

7 - Alarm: 8179 Far-end

- Alarm: "8050 Loss of incoming 2M Signal"

Cancel: Set IF2 and IF3 out of USE.


Alarms are cancelled and there is no active Flexi EDGE BTS alarm visible locally or at the BSC or NetAct.

8 Listen to the voice call. Test call is active and has a good voice quality.

9 - Alarm: "8066 AIS 2M"

Trigger:

Put IF2 in USE.

Insert AIS into IF2 using E1-capable PDH Analyser.


Alarm: "8066 AIS 2 M" is raised (IF2) locally as well as at the BSC and NetAct.



DN0749988Issue 2-0 en18/01/2008


10 - Alarm: "8066 AIS 2M"

Cancel: Stop sending AIS from the analyser


The alarm is cancelled and there is no active Flexi EDGE BTS alarm visible locally or at the BSC or NetAct.

11 - Alarm: "8179 Far-end alarm"

Trigger: Insert Far-end alarm into IF2 using E1 capable PDH Analyser


Alarm: "8179 Far-end alarm" is raised (IF2) locally as well as at the BSC and NetAct.

12 - Alarm: "8179 Far-end alarm"

Cancel: Stop sending Far End alarm from analyser


Alarm is cancelled and there is no active Flexi EDGE BTS alarm visible locally as well as at the BSC and NetAct.

13 - Alarm: "8099 Error rate > 1 E-3"

Trigger: Insert error rate > 1 E-3 into IF2 using E1 capable PDH Analyser.


Alarm: "8099 Error rate > 1 E-3" is raised (IF2) locally as well as at the BSC and NetAct.

14 - Alarm: "8099 Error rate > 1 E-3"

Cancel: Stop sending BER from analyser.


Alarm is cancelled and there is no active Flexi EDGE BTS alarm visible locally as well as at the BSC and NetAct.

15 - Alarm: "8022 Loop to equipment"

Trigger: IF2 is still getting a valid PDH signal from E1 PDH Analyser. Select "Loop to Equipment" using the Flexi EDGE BTS Manager Application for any unused IF Port.

Alarm "8022 Loop to equipment" is raised locally as well as at the BSC and NetAct.

16 - Alarm: "8022 Loop to equipment"

Cancel: Wait until timer expires (default 600 seconds) or release IF Loop using the Flexi EDGE BTS Manager Application.

Alarm cancels and there is no active Flexi EDGE BTS alarm visible locally as well as at the BSC and NetAct.

17 Listen to the voice call. Test call is active and good voice quality.

18 Take a separate local management connection to the Nokia MetroHub Manager.

Change the Q1 speed to 9600 and Q1 addess to 100.

Make sure the the Q1 switches for the

The basic settings for the MetroHub to be BTS polled via the Q1 ext port are set.


DN0749988 Issue 2-0 en 18/01/2008


271 (381)

Step Input Expected output microprocessor and the Q1 ext ports are closed.

19 Connect the v.11 interface of the Flexi EDGE BTS to the Q1 Ext connector of the MetroHub.

Use the following MML command to check the that the MetroHub gets autodetected by the Flexi EDGE BTS: ZQWL:<BCF No>;

The MetroHub is autodetected by the Flexi EDGE BTS.

It is shown in the BSC as TRE=2 with Q1 speed 9600 and Q1 address 100 under the BCF number of the Flexi EDGE BTS.

20 Generate a fault situation in the MetroHub.

Set E1 interface 1 of the FXC E1 unit to "In use".

Set the E1 interface 2-4 to "Not in use".

Use the MML command ZEOL:<BCF No>; to check the alarm of the BTS.

Open local manager connection to the Flexi EDGE BTS with the Flexi EDGE BTS Manager.

"Loss of incoming 2M signal" alarm is displayed in the BSC for the E1 interface that is in use in the MetroHub.

The same alarm is also displayed in the alarm list of the Flexi EDGE BTS Manager.

21 Cancel the fault in the MetroHub by setting E1 interface 1 of the FXC E1 unit to "Not in use".


"Loss of incoming 2M signal" alarm is cancelled in the BSC for the E1 interface that is in use.

The alarm is also cancelled both in the alarm list of the MetroHub and the Flexi EDGE BTS Manager.

22 Plug out the FXC unit in unit slot 2 of the MetroHub without logically uninstalling it.


"Hardware is missing units" alarm can be seen under the BSC.

The same alarm is also displayed in the alarm list of the Flexi EDGE BTS Manager.

23 Insert the unit again.


"Hardware is missing units" alarm is cleared in BSC as well as locally both in the MetroHub as in the Flexi EDGE BTS alarm view.

24 Listen to the voice call. Test call is active and good voice quality.

2.8.2 Abis Loop Protection

Overview The aim is to verify to create a protected loop topology transmission network with Flexi EDGE BTS sites and Nokia MetroHub sites. Then with end user traffic active, verify that the protection of Abis traffic works reliably during singular breaks of the transmission path within the loop



DN0749988Issue 2-0 en18/01/2008

network.

Scope of testing The aim of this test is to verify that the loop protection works for the Abis and synchronisation.

Singular breaks of the transmission path shall not cause any BTS to fail of supervisory connection nor shall ongoing phone calls be dropped Test cases

Pos Name Comment

1 Loop network support test --

2.8.2.1 Loop Network Support Test

The purpose of the test is to verify the transmission loop protection operations and recovery within a simulated live network for the Flexi EDGE BTS.

• Abis loop protection

− Protected bidirectional (P2) cross-connection

− Redundant Abis trunk for E1 interface

− Equal switching

− Priority switching

− Masked bidirectional (M2) cross-connection used as pilot bit for Protected cross-connections

− Unidirectional fixed data (D1) cross-connection used as pilot bit for Protected cross-connections

• PDH traffic routing

− Traffic by passing using Bidirectional (B2) cross-connections

• Loop synchronisation

− Synchronisation Master Control Bit (MCB/LCB) and Loop Control Bit (LCB) used in time slot 0.

− Synchronisation Master Control Bit (MCB/LCB) and Loop Control Bit (LCB) used in time slot n (n = timeslot 1-31).

• Synchronisation and cross-connection protection status indication in Flexi EDGE BTS Manager.


• MetroHub 1 and 2 with MetroHopper radio pair


DN0749988 Issue 2-0 en 18/01/2008


273 (381)

• Flexi EDGE BTS 1 with FIFA plug-in unit

• Flexi EDGE BTS 2 with FIPA plug-in unit (symmetrical E1)

• UltraSite BTS (can also be MetroHub)

• Flexi EDGE BTS 3 with FIEA plug-in unit (asymmetrical E1)


Configuration as in the diagram.

The node settings make use of all the features listed above

MetroHub1

Flexi EDGE

BTS 1

UltraSite

BTS

FlexiHopper plus

MetroHopper

MetroHub2

Flexi EDGE

BTS 2

Flexi EDGE

BTS 3A

B

C

Primary synchronizationsource for loop slaves

Symmetrical E1

Symmetrical E1

Asymmetrical E1

Asymmetrical E1

BSC

MetroHub1

Flexi EDGE

BTS 1

UltraSite

BTS

FlexiHopper plusFlexiHopper plus

MetroHopperMetroHopper

MetroHub2

Flexi EDGE

BTS 2

Flexi EDGE

BTS 3A

B

C

Primary synchronizationsource for loop slaves

Symmetrical E1

Symmetrical E1

Asymmetrical E1

Asymmetrical E1

BSC

Pre-setup:

1. All the BTSs are in in supervisory state without alarms that affect the performance.



DN0749988Issue 2-0 en18/01/2008

2. Abis and synchronisation is set up with loop protection


1 Start a full rate (FR) phone call between the Flexi EDGE BTSs that are part of the loop network.

The phone calls are on.

2 Cut the signal on the protecting side C of the Loop master.

This makes sure that the payload is used on the protected side.

Check that the 8 listed checkpoints behave as expected and fill the pass/fail results in the Result list.

The checkpoints behave correctly.

Details for received M/L bits:

MetroHub 1:

FB1, Ch1: M/L = 0/1

FB1, Ch3: M/L = 0/1

FXC E1, IF1: M/L = 1/1

FXC E1, IF3: M/L = 1/1

Flexi EDGE BTS 1:

FB1, Ch1: M/L = 0/0

FB2, Ch1: M/L = 0/1

MetroHub 2:

FB1, Ch3: M/L = 0/0

FXC E1/T1, IF3: M/L = 0/1

Flexi EDGE BTS 2:

FIPA, IF2: M/L = 0/0


UltraSite BTS:

FXC E1/T1, IF3: M/L = 0/0

FXC E1, IF3: M/L = 1/1

Flexi EDGE BTS 3:

IF1: M/L = 0/0

IF5: M/L = 1/1

3 Remove the cut and go through the The checkpoints behave correctly.


DN0749988 Issue 2-0 en 18/01/2008


275 (381)

Step Input Expected output checkpoints again and record the results. Details for received M/L bits:

MetroHub 1:

FB1, Ch1: M/L = 0/1

FB1, Ch3: M/L = 0/1

FXC E1, IF1: M/L = 0/0

FXC E1, IF3: M/L = 0/0

Flexi EDGE BTS 1:

FB1, Ch1: M/L = 0/0

FB2, Ch1: M/L = 0/1

MetroHub 2:

FB1, Ch3: M/L = 0/0

FXC E1/T1, IF3: M/L = 0/1

Flexi EDGE BTS 2:



UltraSite BTS:

FXC E1/T1, IF3: M/L = 0/0

FXC E1, IF3: M/L = 0/0

Flexi EDGE BTS 3:

IF1: M/L = 0/0

IF5: M/L = 0/0

4 Cut the signal on the protected side A of the Loop master.

This makes sure that the payload and synchronisation has to switch to use the protecting side.




MetroHub 1:

FB1, Ch1: M/L = 1/1

FB1, Ch3: M/L = 1/1

FXC E1, IF1: M/L = 0/1

FXC E1, IF3: M/L = 0/1



DN0749988Issue 2-0 en18/01/2008


Flexi EDGE BTS 1:

FB1, Ch1: M/L = 1/1

FB2, Ch1: M/L = 0/0

MetroHub 2:

FB1, Ch3: M/L = 1/1

FXC E1/T1, IF3: M/L = 0/0

Flexi EDGE BTS 2:



UltraSite BTS:

FXC E1/T1, IF3: M/L = 0/1

FXC E1, IF3: M/L = 0/0

Flexi EDGE BTS 3:

IF1: M/L = 0/1

IF5: M/L = 0/0

5 Remove the cut and go through the checkpoints again and record the results.



MetroHub 1:

FB1, Ch1: M/L = 0/1

FB1, Ch3: M/L = 0/1

FXC E1, IF1: M/L = 0/0

FXC E1, IF3: M/L = 0/0

Flexi EDGE BTS 1:

FB1, Ch1: M/L = 0/0

FB2, Ch1: M/L = 0/1

MetroHub 2:


DN0749988 Issue 2-0 en 18/01/2008


277 (381)


FB1, Ch3: M/L = 0/0

FXC E1/T1, IF3: M/L = 0/1

Flexi EDGE BTS 2:



UltraSite BTS:

FXC E1/T1, IF3: M/L = 0/0

FXC E1, IF3: M/L = 0/0

Flexi EDGE BTS 3:

IF1: M/L = 0/0

IF5: M/L = 0/0

6 Shut down the UltraSite BTS on the protected side of the slave Flexi EDGE BTS.



MetroHub 1:

FB1, Ch1: M/L = 0/1

FB1, Ch3: M/L = 0/1

FXC E1, IF1: M/L = 0/1

FXC E1, IF3: M/L = 1/1

Flexi EDGE BTS 1:

FB1, Ch1: M/L = 0/0

FB2, Ch1: M/L = 0/1

MetroHub 2:

FB1, Ch3: M/L = 0/0

FXC E1/T1, IF3: M/L = 1/1

Flexi EDGE BTS 2:





DN0749988Issue 2-0 en18/01/2008


Flexi EDGE BTS 3:

IF1: M/L = 1/1

IF5: M/L = 0/0

7 Power up the UltraSite BTS on the protected side of the Flexi EDGE BTSs.

Wait for the node to restart before going through the checkpoints.



MetroHub 1:

FB1, Ch1: M/L = 0/1

FB1, Ch3: M/L = 0/1

FXC E1, IF1: M/L = 0/0

FXC E1, IF3: M/L = 0/0

Flexi EDGE BTS 1:

FB1, Ch1: M/L = 0/0

FB2, Ch1: M/L = 0/1

MetroHub 2:

FB1, Ch3: M/L = 0/0

FXC E1/T1, IF3: M/L = 0/1

Flexi EDGE BTS 2:



UltraSite BTS:

FXC E1/T1, IF3: M/L = 0/0

FXC E1, IF3: M/L = 0/0

Flexi EDGE BTS 3:

IF1: M/L = 0/0

IF5: M/L = 0/0

8 Cut the signal at the B point of the loop network.




DN0749988 Issue 2-0 en 18/01/2008


279 (381)




MetroHub 1:

FB1, Ch1: M/L = 0/1

FB1, Ch3: M/L = 0/1

FXC E1, IF1: M/L = 0/1

FXC E1, IF3: M/L = 0/1

Flexi EDGE BTS 1:

FB1, Ch1: M/L = 0/0

FB2, Ch1: M/L = 1/1

MetroHub 2:

FB1, Ch3: M/L = 0/0

FXC E1/T1, IF3: M/L = 1/1

Flexi EDGE BTS 2:



UltraSite BTS:

FXC E1/T1, IF3: M/L = 1/1

FB1, Ch3: M/L = 0/0

9 Remove the cut and go through the check points again and record the results.



MetroHub 1:

FB1, Ch1: M/L = 0/1

FB1, Ch3: M/L = 0/1

FXC E1, IF1: M/L = 0/0

FXC E1, IF3: M/L = 0/0

Flexi EDGE BTS 1:

FB1, Ch1: M/L = 0/0

FB2, Ch1: M/L = 0/1



DN0749988Issue 2-0 en18/01/2008


MetroHub 2:

FB1, Ch3: M/L = 0/0

FXC E1/T1, IF3: M/L = 0/1

Flexi EDGE BTS 2:



UltraSite BTS:

FXC E1/T1, IF3: M/L = 0/0

FXC E1, IF3: M/L = 0/0

Flexi EDGE BTS 3:

IF1: M/L = 0/0

IF5: M/L = 0/0

10 Cut the signal on the protecting side C of the Loop master.





MetroHub 1:

FB1, Ch1: M/L = 0/1

FB1, Ch3: M/L = 0/1

FXC E1, IF1: M/L = 1/1

FXC E1, IF3: M/L = 1/1

Flexi EDGE BTS 1:

FB1, Ch1: M/L = 0/0

FB2, Ch1: M/L = 0/1

MetroHub 2:

FB1, Ch3: M/L = 0/0

FXC E1/T1, IF3: M/L = 0/1

Flexi EDGE BTS 2:



DN0749988 Issue 2-0 en 18/01/2008


281 (381)



UltraSite BTS:

FXC E1/T1, IF3: M/L = 0/0

FXC E1, IF3: M/L = 1/1

Flexi EDGE BTS 3:

IF1: M/L = 0/0

IF5: M/L = 1/1

11 Remove the cut and go through the checkpoints again and record the results.



MetroHub 1:

FB1, Ch1: M/L = 0/1

FB1, Ch3: M/L = 0/1

FXC E1, IF1: M/L = 0/0

FXC E1, IF3: M/L = 0/0

Flexi EDGE BTS 1:

FB1, Ch1: M/L = 0/0

FB2, Ch1: M/L = 0/1

MetroHub 2:

FB1, Ch3: M/L = 0/0

FXC E1/T1, IF3: M/L = 0/1

Flexi EDGE BTS 2:



UltraSite BTS:

FXC E1/T1, IF3: M/L = 0/0

FXC E1, IF3: M/L = 0/0



DN0749988Issue 2-0 en18/01/2008


Flexi EDGE BTS 3:

IF1: M/L = 0/0

IF5: M/L = 0/0

2.8.3 Transmission Management

Overview The configuration and management of all the transmission interfaces can be carried out by the single Flexi EDGE BTS Manager interface. The fault management and reporting of transmission (8000 series) alarms can be enabled from either BTS site or BSC polling through a service channel.

Scope of testing To verify that all the different management actions can be done remotely and locally via Flexi EDGE BTS Manager, and that a Flexi EDGE BTS can be set to BSC Fault Management polling.

Test cases

Pos Name Comment

1 Remote configuration of cross connections FIEA

2 Remote configuration of cross connections FIPA, T1 mode

3 Remote configuration of cross connections FIFA

4 Remote configuration of loop synchronization bits

FIEA


FIPA, T1 mode


FIFA

7 Remote configuration of Q1 FIEA

8 Remote configuration of Q1 FIPA, T1 mode

9 Remote configuration of Q1 FIFA

10 Remote management of MetroHub connected to Flexi EDGE BTS via v.11 interface

--

11 Save SCF file remotely using Flexi EDGE BTS Manager

FIEA

12 Save SCF file remotely using Flexi EDGE FIPA, T1 mode


DN0749988 Issue 2-0 en 18/01/2008


283 (381)

Pos Name Comment BTS Manager

13 Save SCF file remotely using Flexi EDGE BTS Manager

FIFA

2.8.3.1 Remote Configuration of Cross-connections

The purpose of this test case is to verify that the cross connections can be remotely added, edited, deleted and copied via a remote Flexi EDGE BTS Manager connection. Also exporting and importing of the cross connection bank will be tested. Additionally a mobile to mobile phone call will be established to verify that there is no any harm to the traffic while configuring the cross connections.


Any standard configuration, with transmission card and interface type as specified in the test plan.

Pre-setup:

1. The Flexi EDGE BTS is in supervisory state using Abis on interface 1.

2. Enable all transission interfaces.

3. Establish a mobile to mobile voice calls for duration on this test case.


1 Add from remote Flexi EDGE BTS Manager different types/granularity of cross-connections in the inactive bank for different interfaces.

Bidirectional type (B2):

Of granularity [ 8K,16K,32K and 64K ]

Masked bidirectional type (M2):

Of granularity/Mask:-

8K [ Mask 0 and 1] ,16K [ Mask 01],

32K [ Mask 0101], 64K [ Mask 10101010 ]

Unidirectional Fixed Data type (D1):

Of granularity/pattern:-

The cross-connections can be added to the inactive bank.

The phone call is undisturbed.



DN0749988Issue 2-0 en18/01/2008


8K [ pattern 0 and 1 ], 16k [ pattern 10 ]

32k [ pattern 1010 ],

64k [ patterm 11001100 ]

Protected bidirectional type (P2) :

Create cross connection of 16K and 32K with :-

Interface 4 as Reliable termination point

Interface 5 as Protected termination point

Interface 6 as Protecting termination point

and define Equal condition type:

Condition bit 1:

Interface 3, time slot 6, bit 1

Condition bit 2:


Create cross connection of 64K with interface configuration same as above and define Prioriy condition type:

Condition bit 1:


2 Activate the CC bank. The inactive bank becomes active.

Abis is not disturbed and the phone call is ongoing.

3 Export the active cross connection bank to NOD file.

The exportation can be done.


4 Copy the CC bank to the inactive bank. CC settings are copied to the inactive bank.


5 Delete some CCs. CCs can be deleted.


6 Modify some of the cross-connections like change the granularity, interface, Mask or pattern.

CCs can be modified.


7 Activate the inactive CC bank. The inactive bank becomes active.


DN0749988 Issue 2-0 en 18/01/2008


285 (381)



8 Clear the inactive cross connection bank. The inactive bank becomes empty.


9 Import the cross connection file saved in step to the inactive cross connection bank.

The cross connection file is successfully imported.


2.8.3.2 Remote configuration of loop synchronisation bits

The purpose of this test case is to verify that the MCB/LCB can be remotely added, edited and deleted. A mobile to mobile voice call will be established to verify that there will no any harm to the traffic while configuring the MCB/LCBs.


• NetAct



Pre-setup:

1. The Flexi EDGE BTS is commissioned with plug-in unit FIEA and in supervisory state.

2. Abis is set up in interface 1.

3. Synchronisation is taken from interface 1.

4. Minimum configuration is a 2 Omni setup.

5. Enable all interfaces.

6. Establish a mobile-to-mobile voice call.

7. Take a remote Flexi EDGE BTS Manager connection via NetAct to the Flexi EGDE BTS.



DN0749988Issue 2-0 en18/01/2008


1 From remote Flexi EDGE BTS Manager, enable two other interfaces (such as 2 and 8) in ESMA.

2 Add the MCB/LCB bits in both interfaces, for example:

IF 2: TS 23, bits 3,4

IF 8: TS 23, bits 3,4

The MCB/LCB configuration can be done.


3 Modify the MCB/LCB bits, for example:

IF 2: TS 11, bits 7,8

IF 8: TS 11, bits 7,8

The MCB/LCB configuration can be modified.


4 Delete the MCB/LCB configuration for the interface 8.

The MCB/LCB configuration for interface 8 can be deleted.


5 Take another interface into use.

Add for that interface the MCB/LCB bits, for example:

IF 3: TS 11, bits 7,8

The MCB/LCB configuration can be done.


6 Modify the MCB/LCB bits for IF 2 and 3:

IF 2: TS 30, bits 5,6

IF 3: TS 30, bits 5,6

The MCB/LCB configuration can be modified.


7 Delete both MCB/LCB configurations. The configurations are deleted.


2.8.3.3 Remote Configuration of Q1

The purpose of this test case is to verify that the Q1 service channel (EOC) can be remotely added, edited and deleted and that the BTS can be set to from BTS to BSC polling and finally back to BTS polling. A mobile-to-mobile voice call will be established to verify that there will be no any harm to the traffic while configuring the EOCs.


DN0749988 Issue 2-0 en 18/01/2008


287 (381)



Pre-setup:

1. The Flexi EDGE BTS (Commissioned with FIEA) set to BTS Q1 polling.

2. The Abis is set up in interface 1 and somewhere between timeslot 1-22.

3. Make sure that the whole 2M channel the Abis is part of is cross-connected all the way to the Flexi EDGE BTS.

4. Enable all interfaces.

5. Take a remote Flexi EDGE BTS Manager connection through NetAct to the Flexi EGDE BTS.

6. Establish calls via the BTS site for duration of test case.


1 Use the ZQWG command to change the Q1 address for TRE=1 of the BCF to an address between 1-3999.

Also create a 64k EOC (Q1 service channel) for the Flexi EDGE BTS in timeslot 23 in the same interface where the Abis is.

The polling state is shown as BSC polling and the address is the same as set for TRE=1 of the BCF.

The EOC has been created in the Flexi EDGE BTS.


2 Use the MML session to create a 9600 Baud, 64k bandwidth, timeslot 23, Q1 service channel for BSC polling in the BSC with command:

The BSC polling channel is created.


3 Add the TRE of the BCF as polled equipment to the polling channel using the previously set Q1 address.

Check with MML command ZQWI:<service channel no>:ALL; that the BSC polling channel is correctly set and that the polled equipment is correctly added.

The polling channel and the the added equipment are shown correctly.

The polling channel state is AD and the status of the polled equipment is "NO POLLING, UNINIT".


4 Enable the BSC polling at the BSC by changing the service channel state to AL (ZQWS:<CH>:AL;)

Note that it can take a few minutes before the

The BSC polling starts on the service channel and Flexi EDGE BTS are seen with status "OK" or "Alarm" if there is non-relevant transmission alarm in the Flexi EDGE BTS already from the start (pre-setup).



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output equipment is recognised in the polling channel. The phone call is undisturbed.

5 Edit the EOC with the remote Flexi EDGE BTS Manager connection.

Move it to TS 24, bits 1-4, with 32k bandwidth.

Check with ZQWI command that the polling has been lost for the BTS.

The polling is lost "NO POLLING, UNINIT".


6 Disable the BSC polling at the BSC by changing the service channel state to AD.

The service channel is set to AD and the polling is stopped.


7 Use the MML session to edit the disabled polling channel to 4800 Baud, 32k banddwidth, timeslot 24, sub timeslot 0 with command:

The BSC polling channel is modified.


8 Use the ZQWG command to change the Q1 speed for TRE=1 of the BCF to 4800, and leave the address unchanged.

Use the remote Flexi EDGE BTS Manager connection to check that the polling state is still BSC polling and that the Q1 speed has changed from 4800.

The Q1 speed is changed and the phone call remains undisturbed.

9 Enable the BSC polling at the BSC by changing the service channel state to AL.(ZQWS:<CH>:AL;)

Note that it can take a few minutes before the equipment is recognised in the polling channel.

The BSC polling starts on the service channel and Flexi EDGE BTS are seen with status "OK" or "Alarm" if there is a non-relevant transmission alarm in the Flexi EDGE BTS already from the start (pre-setup).


10 Use the remote Flexi EDGE BTS Manager connection to delete the EOC in the Flexi EDGE BTS.

Check that the equipment drops from polling at the BSC.

The equipment is shown as "NO POLLING, UNINIT" and the phone call is ongoing.


11 Use the MML session to disable the service channel in the BSC and delete it from the BSC.

Use the remote Flexi EDGE BTS Manager connection to check that the polling state is still to BSC polling.

The service channel is deleted, but the Flexi EDGE BTS is still in BSC polling state.


12 Use the ZQWG command to change the Q1 address for TRE=1 of the BCF to 4080 and the speed back to 9600 baud.

The Flexi EDGE BTS is in BTS pollnig state, Q1 speed is 9600 and Q1 address is 4080.


DN0749988 Issue 2-0 en 18/01/2008


289 (381)


Use the remote Flexi EDGE BTS Manager connection to check that the polling state is now to BTS polling and speed and address is shown as set in the BSC.


2.8.3.4 Remote Management of MetroHub Connected to Flexi EDGE BTS via v.11 Interface

The aim of this test case is to verify that a remote Flexi EDGE BTS Manager connection can be taken to a MetroHub connected to the V.11 interface of the ESMA.


• MetroHub

Software tools:

• NetAct



Pre-setup:

1. Connect the MetroHub to V.11 interface of the ESMA.

2. The Flexi EDGE BTS (commissioned with FIPA) shall be in supervisory state.

3. Set interface 1 in USE

Sync priority 1: interface 1

4. Configure the Abis channel according to the BSC.

5. No transport related alarms are active.


1 Assign a unique Q1 address for the MetroHub via local connection.

2 Add the MetroHub as a TRE (equipment under BCF) under the Flexi EDGE BTS

ZQWA:BCF=bcfno:TRE=x:q1add_e

The MetroHub has been added as equipment under the Flexi EDGE BTS.



DN0749988Issue 2-0 en18/01/2008


x = internal index

q1add_e = unique Q1 address selected for the MetroHub

Check with ZQWL:BCF=bcfno; that the MetroHub is shown as a TRE under the Flexi EDGE BTS.

3 Set up the necessary settings in NetAct to to enable a remote connection to the MetroHub.

The settings are created.

4 Take a remote manager connection from NetAct to the MetroHub.

The connection is successul.

5 Generate a fault situation in MetroHub.

Set the E1 interfaces of the FXC E1/T1 card in use.

Configure the four sync sources.


"Loss of incoming 2M signal" alarm can be seen for the E1 interfaces.

Also "Loss of synchronization signal(s)" is active for the MetroHub.

6 Set the E1 interfaces out of use.


"Loss of incoming 2M signal" alarms are cleared in the BSC.

"Loss of synchronization" alarm can be seen under the BSC.

7 Set pritiority 1 as Internal in the MetroHub.


"Frequency error" alarm can be seen under the BSC.

8 Plug out the unit.


"Hardware missing" alarm can be seen under the BSC.

9 Insert the unit.


"Hardware missing" alarm is cleared.

10 Create a cross connection in the MetroHub. Action is possible.

11 Create a MCB/LCB in a interface of the MetroHub.

Action is possible.

12 Create an EOC in a interface of the MetroHub. Action is possible

13 Disconnect the remote connection. Action is possible.


DN0749988 Issue 2-0 en 18/01/2008


291 (381)

2.8.3.5 Save SCF file remotely with Flexi EDGE BTS Manager

The purpose of this test case is to verify that the SCF file can be saved remotely with Flexi EDGE BTS Manager from a commissioned BTS independent of which plug-in unit type is used.


• NetAct



Pre-setup:

1. Abis is set up in interface 1 and is used for Synchronisation source.

2. Enable all interfaces

3. Calls are established and then held for duration of test case.


1 Take a remote Flexi EDGE BTS Manager connection to the BTS.

The remote connection is established.

2 Configure the interface settings remotely.

Set Interface 5 to NOT IN USE.

Set Interfaces 6, 7 and 8 to USE, CRC OFF.

Click the "Send LIF" button.

The extra interface settings have been set.

The call is still ongoing.

3 Add an extra synchronisation priority to the sync list and press "Send Synchronization" button.

The synchronisation settings have been set.


4 Create an EOC to an unused interface. The EOC is set and shown by the Flexi EDGE BTS Manager after 5 seconds.


5 Create a MCB/LCB in an unused interface. Configuration can be done remotely via Flexi EDGE BTS Manager.


6 Save the SCF file remotely with the Flexi EDGE BTS Manager.

The file is saved.


7 Take a local connection with Flexi EDGE BTS The Flexi EDGE BTS is uncommissioned



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output Manager and uncommission the Flexi EDGE BTS .

and the call is dropped.

8 Commission the Flexi EDGE BTS with the SCF file saved in step 6.

The Flexi EDGE BTS comes up in supervisory state.

9 Set up a mobile to mobile call. Connection is established. Good voice quality.

10 Check all extra settings done in steps 2 to 5. The settings are correctly set.

2.8.4 Transmission Performance Management

Overview From all Nokia transmission nodes, including Flexi EDGE BTS transmission object, G.826 counter can be collected and then retrieved to the BSC and NetAct for presentation in Transmission Key Performance Indicator data.

The G.826 counters are also available to be viewed and saved using Flexi EDGE BTS Manager.

Scope of testing The scope of testing is to verify that performance management and RX level measurements in the test network are collected and then stored at BSC in measurement files.

TRE measurement is only 24-hour measurement and all transmission equipment (supporting Nokia Q1E format) is automatically included.

TRE SEL measurement from the BSC can be made with various output intervals (15, 30, 60, 120, 180 min. and 24h), hence you can select desirable equipment and their SBs to the measurement.

Settings No special settings needed. Test cases

Pos Name Comment

1 Performance data (G.826) collection locally and in BSC

--

2.8.4.1 Performance Data (G.826) Collection Locally and in BSC


DN0749988 Issue 2-0 en 18/01/2008


293 (381)

The aim is to check that performance management and RX level measurements in the test network can be verified with Flexi EDGE BTS Manager and BSC measurement files.

TRE measurement is only a 24-hour measurement and all transmission equipment (supporting Q1E) is automatically included. TRE SEL measurement with various output intervals (15, 30, 60, 120, 180min and 24h), hence you can select desirable equipment and their SBs to the measurement.

In this measurement standard G.826 counters and RX min/max will be collected.


• Tool for converting BSC Measurement files



Pre-setup:

• The BSC shows no alarms which could prevent the PM data transfer to the BSC.


1 In the BSC, check if the TRE objects are included to the transmission measurements

ZQUI;

All objects which are measured will be listed.

2 With ZTPI (MML) check if the measurements are running.

Stop measurements with: ZTPE

If there are objects missing in the list they are added with ZQUB

Measurements are stopped.

BTS are added to the object list.

3 The FE and SB numbers can be checked from the MML-session with following command: ZQUS

All FE and SB numbers are shown.

4 Before the measurement data can be checked the transmission measurements must be activated.

Check transmission measurements are already running: ZTPI.

If the measurements are not already running continue given BSC: ZTPS to start collection.

Running measurements are listed.

Measurement data starts to be collected at the interval specified.



DN0749988Issue 2-0 en18/01/2008


5 After the new BSC measurement files are stored to hard disk, retrieve these and convert to a readable format with the conversion tool.

Files are available and can be converted to a readable format.

6 Using Flexi EDGE BTS Manager, open the menu item "Performance Monitoring", and save these to disk.

Window "Performance Report for IF X" opens. The report can be saved to the PC hard disk.

7 Compare the following counters with the converted file of the BSC:

Total Time

Available Time

Error Seconds

Severely Errored Seconds

Background Block Errors

Errored Blocks

Counter values are the same from saved report and converted BSC measurement file.

2.8.5 Transmission Support for Abis Signalling

Overview On the Abis different LAPD signalling capacities (16k, 32k or 64k) can be used for TRX and O&M LAPD links for operational reasons.

The compressed Abis feature allows the LAPD link (TRX or O&M) to be placed on the first time slots of the Abis speech channel allocation. The use of this feature is at expense of available TCH capacity.

Scope of testing The aim of these tests is to verify the functionality of the compressed Abis Solution (OMU SIG on TCH) and (TRX SIG on TCH). The aim is also to verify the proper functioning of all possible signalling capacities in the Abis Interface (16k, 32k and 64k signalling for O&M and TRX Signalling).

Test cases

Pos Name Comment

1 Abis Signalling Capacity (16K/32K/64K) --

2 Compressed Abis Functionality (OMU SIG on TCH)

--

3 Compressed Abis Functionality (TRX SIG on TCH)

--


DN0749988 Issue 2-0 en 18/01/2008


295 (381)

2.8.5.1 Abis Signalling Capacity (16K/32K/64K)

The aim of this test case is to verify the proper function of all possible signalling capacities in the Abis Interface. This test includes 16K, 32K and 64K Signalling for O&M as well as TRX Signalling.


• NetAct


• Any standard configuration

• 16k/32k/64k LAPD signalling for both E1 and T1

Pre-setup:

1. The Flexi EDGE BTS is set to BTS polling and is in supervisory state without alarms that affect the performance.

2. The Abis is set up somewhere between timeslot 1-22.

3. Make sure that the whole 2M channel the Abis is part of is cross-connected all the way to the Flexi EDGE BTS.

E1 test cases:


1 16K E1 test case:

Configure the Abis Allocation locally and remotely (BSC).

Configuration successful.

2 Perform at least one 1-minute FR/HR rate test call for each TRX. Actively listen to the call.

The test calls are successful and the quality is acceptable.

3 32K E1 test case:





5 64K E1 test case:







DN0749988Issue 2-0 en18/01/2008

T1 test cases:


7 16K T1 test case:





9 32K T1 test case:





11 64K T1 test case:





2.8.5.2 Compressed Abis Functionality (OMU SIG on TCH)

The aim of this test case is to verify the functionality of the compressed Abis Solution (OMU SIG on TCH).


• Flexi EDGE BTS with PIU FIEA or FIPA


Any standard configuration, with transmission card and interface type as specified in the test plan

Pre-setup:

None.

Test steps: 16K signalling


1 Configure the O&M SIG to be allocated on TRX1 TCH0/1-2, (16K Signalling).



DN0749988 Issue 2-0 en 18/01/2008


297 (381)


All remaining TCH TSLs should be configured as TCHD.

Configure TRX1 to MBCCHC (CH0=MBCCHC, ZERM)

Set TRX 1 to be the preferred BCCH TRX (Pref=P, ZERM)

2 Check the SW versions using the BTS Manager Application.

Attach and activate a software package which is currently not in the flash (ZEWV).

Monitor SW DL with BCF Phase Monitoring from the BSC (RPHASE Extension )

Check the state of the BTS and the SW version in Flexi EDGE BTS Manager.

SW versions are as expected

Download of SW takes place.

The BCF is in WO state without any active alarms.

The SW version shows the attached package is running.

3 Perform at least 1-minute FR/HR rate test calls on each remaining timeslot of TRX1 and TRX2, and actively listen to the calls.

Test calls on all remaining TSLs are successful and quality is acceptable.

2.8.5.3 Compressed Abis Functionality (TRX SIG on TCH)

The aim of this test case is to verify the functionality of the compressed Abis Solution (TRX SIG on TCH)


• Flexi EDGE BTS with PIU FIEA or FIPA



Pre-setup:

None.



1 Configure TRXSIG1 to be allocated on TRX1 TCH1/1-2, (16K Signalling), and TRXSIG2 to be allocated on TRX2 TCH1/1-2.




DN0749988Issue 2-0 en18/01/2008


Configure MBCCHC to TRX1.

CH0 has to be NOT USED at the BSC for TRX2.

Remaining TS are TCHD.


2 Perform at least 1-minute FR/HR rate calls on each timeslot of TRX1 and TRX2, and actively listen to the calls.


3 Lock the TRXSIG for TRX1 (ZDTC)

Wait until the recovery action is completed.

TRX SIG blocked successfully (BL_US)

During BCCH Reconfiguration TRX2 restarts.

When the recovery is completed, the MBCCHC moved successfully to TRX2. TRX2 is in "WO" state again.

4 Perform at least 1-minute FR/HR rate calls on each remaining timeslot of TRX2, and actively listen to the calls.


5 Unlock TRXSIG for TRX2 (ZDTC)


TRXSIG unblocks successfully, TRXs restart. When the recovery is completed, the MBCCHC moved successfully back to TRX1. Both TRXs are in "WO" state again.


The test calls on all remaining TSLs successful and quality is acceptable.



1 Configure TRXSIG1 to be allocated on TRX1 TCH1/1-4, (32K Signalling) and on TRXSIG2 TCH2/1-4.

Configure MBCCHC to TRX 1.

Set to NOT USED CH1 for TRX1 and CH0 & 1 for TRX2.

Remaining TS are TCHD.



2 Perform at least 1-minute FR/HR rate test calls on each remaining timeslot of TRX1 and



DN0749988 Issue 2-0 en 18/01/2008


299 (381)

Step Input Expected output TRX2, and actively listen to the calls.

3 Lock the TRXSIG for TRX1 (ZDTC).


TRX SIG blocked successfully (BL_US).

During BCCH reconfiguration TRX2 restarts.

When the recovery is completed, the MBCCHC moved successfully to TRX2. TRX2 is in "WO" state again.

4 Perform at least 1-minute FR/HR rate test calls on each remaining timeslot of TRX2, and actively listen to the calls.


5 Unlock TRXSIG for TRX2 (ZDTC).


TRXSIG unblocks successfully, TRXs restart. When the recovery is completed, the MBCCHC moved successfully back to TRX1. Both TRXs are in "WO" state again.



2.8.6 Satellite Abis

Overview Satellite Abis enables the operator to create coverage of the network in areas where the coverage could not be otherwise implemented due to the limitation of transmission media. Satellite circuits are useful when connecting extremely remote locations, but also when no other transmission means exist. The Satellite Abis is an application software intended for connecting the BSC to remote BTSs and enables a transmission path having a delay of about 280 ms in each direction.

Scope of testing The scope of testing includes testing of the following with satellite Abis configuration:

• BTS Time Reference from PCM

• Call release after Loss of TRAU Frame Synchronization

• Dynamic Abis allocation

• Link Adaptation with EGPRS

• Fast Link Adaptation with AMR

• Abis loop tests



DN0749988Issue 2-0 en18/01/2008

• BTS SW background downloading

• Modification of BCF Parameters by Append Commissioning

• Remote Flexi EDGE BTS Manager

Configuration Site configuration 4+4+4 with E1 Abis.

Settings 1. Follow the recommeneded BSC parameter settings and channel

configurations as defined Nokia BSC/TCSM Product Documentation, Activating and Testing BSC4040: Satellite Abis, DN981265

2. All cases use data channel simulator to introduce delay of 280 ms in both direction paths.

Test cases

Pos Name Comment

1 BTS Time Reference from PCM -


EFR


AMR/FR


AMR/HR on both Subchannels.

5 Link adaptation in uplink in EGPRS segment

-

6 Link adaptation in downlink in EGPRS segment

-

7 PS data transfer on a single EDGE capable TRX with simultaneous CS calls

-

8 Fast Link Adaptation for Co-Channel Interference [ UL ]

RF Hopping AMR/FR

9 Fast Link Adaptation for Co-Channel Interference [ DL ]

RF Hopping AMR/HR

10 GPRS data transfer with coding scheme CS3/CS4

GTRX on all TRXs


-

12 Successful background SW download during normal operation from BSC

16k O&M LAPD

13 Successful fetch of B2 cross-connection -


DN0749988 Issue 2-0 en 18/01/2008


301 (381)

Pos Name Comment (32k/16k/8k) from remote Flexi EDGE BTS Manager


-

2.8.6.1 BTS Time Reference from PCM

See section 2.1.1.1.

2.8.6.2 Checking for Call Release after Loss Of TRAU Frame Synchronisation


2.8.6.3 Link adaptation in uplink in EGPRS segment


2.8.6.4 Link adaptation in downlink in EGPRS segment


2.8.6.5 PS data transfer on a single EDGE capable TRX with simultaneous CS calls


2.8.6.6 Fast Link Adaptation for Co-Channel Interference [UL]


2.8.6.7 Fast Link Adaptation for Co-Channel Interference [DL] See section 2.3.5.2.

2.8.6.8 GPRS data transfer with coding scheme CS3/CS4




• SGSN, GGSN, HLR

• MSC, VLR (optional)




DN0749988Issue 2-0 en18/01/2008

Test execution Pre-setup:

BTS and TRXs should be in supervisory state and no unexpected alarms should be seen on Flexi EDGE BTS Manager/BSC.


1. Observe the channel status at the BSC using the following MML command:



2. Attach 6 MSs. MSs display ‘G’ on the screen display. This is a confirmation for the successfully attached MS.

3. After the MSs have been successfully attached, activate the PDP context for MS. This assigns IP address to the GPRS attached MS.

MSs displays (G) on the screen display. This is a confirmation that PDP contexts for the MSs are created successfully.

4. After the successful establishment of PDP context, open an FTP session with FTP server and initiate upload of file (ftp-put) for a 500 KB file for all the 6 mobiles simultaneously.

Observe using Abis Analyser traces that the data transfer happens with coding schemes including CS-3 or CS-4.

There are no unexpected drops in the throughput.

5. After the successful ‘put’ operation, initiate ‘get’ for 500 KB file for all the 6 mobiles simultaneously.


There are no unexpected drops in the throughput.

6. Repeat step 4 and step 5 twice. The same output is observed as above.

2.8.6.9 Abis Loop Test For Fixed Abis Configuration


2.8.6.10 Successful background software download during normal operation from the BSC


2.8.6.11 Successful fetch of B2 cross-connection (32k/16k/8k) from remote Flexi EDGE BTS Manager



DN0749988 Issue 2-0 en 18/01/2008


303 (381)

2.8.6.12 Successful fetch of Site Information Report (SIR) from remotely connected Flexi EDGE BTS Manager

This test case verifies that Flexi EDGE BTS Manager displays an option to obtain the Site Information Report (SIR) from the remotely connected BTS site. The following information will be contained in the site information report:

• The current SCF from the BTS

• The configuration parameters of BTS_CONF_DATA

• The commissioning report from the BTS

• The current Traffic trace information

• The current HW, SW version report of the BTS

• The current logical object properties information of the BTS

• All alarms, including the real and raw alarm history (start, cancel, transient), and the latest alarm diagnostic report

• Transmission configuration settings

• The TRE poll list information received from BSC.

Test environment Network elements


Software tools



No Flexi EDGE BTS Manager is connected locally to the BTS.

LMU is connected to BTS Site as a Q1 device and the same is configured at the BSC using ZQWA MML command.






3 Specify the following parameters:



The Events View shows that the Flexi EDGE BTS Manager is attempting connection with the BTS.

Flexi EDGE BTS Manager goes into "Flexi EDGE BTS Manager Connected Remotely" state as



DN0749988Issue 2-0 en18/01/2008



BCF ID

Click on “Connect” button.

viewed on the status bar.

4 From Flexi EDGE BTS Manager, click on the option to Fetch SIR using menu option “Supervision -> Site Information…”

The Events window shows that Flexi EDGE BTS Manager has sent a request to the BTS to fetch the SIR.

5 The Flexi EDGE BTS Manager is used to view and examine the Site Information Report (SIR).

All the information types as specified in test case introduction are verified.

The on-screen view is in a readable format.

The information contained in the SIR is correct and consistent (for example, SCF is verified by fetching the SCF from the BTS using the "Fetch SCF from BTS" option and then checking for the contents, and the corresponding field in the SIR).

Same with Commissioning Report. BTS_CONF_DATA is verified from the traces on GSM Abis Analyser.

Current hardware information is verified by verifying from the hardware module labels.

Logical objects are as defined on the BSC.

BTS Site alarms can be verified on the BSC.

Transmission configuration settings can be verified from Transmission view of BTS Manager and TRE poll list .

6 Save the SIR in the form of XML file by clicking on the Save option and specify the path (such as c:/mylogs/SIR.xml)

Verify that Remarks can also be provided optionally while saving the SIR.

Click to save the SIR.

Open the SIR from the saved path.

SIR is saved in the specified path with same name which was specified during its saving.

The SIR is saved as an XML file.

SIR can be opened without error in standard XML view applications. The SIR file contains all the information in step 5.

2.8.7 Support for Nokia Microwave Radio Links

Overview With the FIFA transmission plug-in module, it is possible to connect and use Nokia Microwave Radios (Outdoor Units) to carry the Abis over.


DN0749988 Issue 2-0 en 18/01/2008


305 (381)

Scope of testing The scope of testing is to verify that the Outdoor Units can be installed and commissioning Hub Manager connected via Flexi EDGE BTS.

Configuration Any BTS configuration with FIFA transmission module.

Test cases

Pos Name Comment

1 Installation of radio single hop with FIU and Flexihopper

Low / Flexi Hopper Outdoor Units

2.8.7.1 Installation of Radio Single Hop with FIU and Flexihopper

The aim of this test case is to extend an existing network with a radio link. The Flexi EDGE BTS will be installed and commissioned after a Hub via a radio and an indoor unit during normal operation.


• Flexi EDGE BTS with FIFA card

• HUB with Radio Interface unit

• Flexi Hopper radio pair

• Radio Indoor Unit

Software tools:

• Flexi Hub Manager

• Nokia Metro Hub Manager


1. Radio is available with radio software.


1 Verify that the software versions and application versions of the network elements are according the planned configuration.

Versions are according to the planned configuration.

2 Establish a local connection to hub via LMP and identify a free radio interface.

Connect this radio interface to the FlexiHopper.

Hub connected to FlexiHopper.



DN0749988Issue 2-0 en18/01/2008


3 Connect the other FH to the Indoor Unit.

Connect one E1 interface of the indoor unit and to the Flexi EDGE BTS.

FlexiHopper is connected to Indoor Unit.

Indor Unit is connected to Flexi EDGE BTS via FlexiHopper.

4 Enable the selected interfaces on the Hub and Indoor Unit and start the radio commissioning wizard.

Radio commissioning completed.

5 Create and activate the necessary CCs for the Flexi EDGE BTS in the Hub and Indoor unit according to the planned configuration.

CC activation successful.

6 Create Flexi EDGE BTS with all relevant parameters in BSC and attach the latest SW release to the BCF.

BCF successfully created in the BSC.

7 Establish local connection to Flexi EDGE BTS via LMP and check that the BTS has no active alarms.

No active BTS alarms.

8 Enable the E1 interface on the Flexi EDGE BTS and check the alarm status (internal E1).

The interface is enabled.

No active LOS alarm.

9 Start the commissioning wizard on the Flexi EDGE BTS and complete the commissioning with all relevant parameters.

Commissioning completed.

10 Check the status of the OMUSIG of the Flexi EDGE BTS.

Check SW download from BSC (BSC command: ZEWI)

OMUSIG is working.

SW download started.

11 Wait approximately 20 minutes and check the download activity until download has finished.

SW download finished.

12 Check the status of the TRXSIG and TCH. (BSC command: ZEEI)

TRXSIG is working and TCHs are in idle state.

13 Perform a location update with all three mobiles on the Flexi EDGE BTS.

Setup a voice and a data call.

Location Update successful.

Call setup is successful.

14 Release the voice and data calls. Calls are released.


DN0749988 Issue 2-0 en 18/01/2008


307 (381)

2.9 Value Added Services

2.9.1 Enhanced Full Rate Codec

Overview The Enhanced Full Rate (EFR) speech codec uses the full rate channel coding but provides a considerably better performance in all channel conditions.

The BSC forwards the information on the codec type to the Base Transceiver Station (BTS) in the channel activation message. The BTS configures the active timeslot according to this information to support EFR.

Scope of testing This test plan covers successful EFR call establishment (single call) and multiple calls with long duration stability of the call.

Test cases

Pos Name Comment

2 Enhanced full rate call establishment BB Hopping Sector

3 Enhanced full rate call establishment RF Hopping sector

2.9.1.1 Enhanced Full Rate Call Establishment

The objective of the test case is to verify that Enhanced Full Rate call gets established successfully and also observe the stability of the call during long duration with multiple EFR calls.


The sector configuration is as per test case comment.

Pre-setup:

None.


1 Initiate 6 EFR calls including some emergency calls.

Observe the Channel Activation message on the Abis Interface.


Channel Mode IE of the Channel activation message has ‘GSM speech coding algorithm version 2’ value 0x11 for Speech coding algorithm field indicating EFR codec



DN0749988Issue 2-0 en18/01/2008


Listen to voice on all the calls for 1 minute actively.

is used.


2 Have calls active for 2 hrs and listen to the speech at periodic intervals.

Observe the Measurement reports on the GSM Abis analyser for all the calls.


The Enhanced Measurement reports indicate that Rx_qual_full tends to zero, DL FER and UL FER tend to zero for all the calls.

3 Release all the calls and check the status at the BSC.

All calls released successfully and the channels are idle.

4 Establish new calls on the same channels that were used in step 1.

Listen to the voice on all the calls for 1 minute actively.



2.9.2 Short Message Service Cell Broadcast with DRX

Overview Short Message Service Cell Broadcast is a service in which short messages may be broadcast from a PLMN to Mobile Stations (MS). Reception of SMSCB messages by the MS is only possible in idle mode.

The SMS Cell Broadcast service is designed to minimise the battery usage requirements for a MS. A MS can read the schedule message transmitted on the Cell Broadcast channel and decide to receive the entire Broadcast message that is following or go to sleep mode for the schedule period if all the messages are already received by the MS and there is no change in the message content. This is possible only when DRX is enabled.

Scope of testing This test plan contains test cases pertaining to SMS-CB with DRX.

Test cases

Pos Name Comment

1 Short message cell broadcast - DRX ON 2+4+2, Non Hopping, Combined BCCH Sector

2 Short message cell broadcast - DRX ON 2+4+2, Non Hopping,


DN0749988 Issue 2-0 en 18/01/2008


309 (381)

Pos Name Comment Non Combined BCCH Sector

2.9.2.1 Short Message Cell Broadcast - DRX ON

The objective of the test case is to verify that all the cell broadcast messages that are created and activated at the BSC are properly transmitted on the air as per the repetition rate and received by the mobile when DRX is enabled in the cell.


• Air Interface monitoring device


Sector configuration as per test case comment.

Pre-setup:

1. Messages with the below attributes to be created and activated at the BSC with different text.

− Number of pages = 2 pages, repetition rate = 2 seconds.

− Number of pages = 15 pages, repetition rate = 60 seconds.

2. BTS Manager is connected to the system


1 Latch the Air Interface monitoring device and test mobiles to the BCCH frequency and observe the Air Interface monitoring device and test mobile for 3 minutes.

The Air Interface monitoring device and test mobiles successfully latched.

The Air Interface monitoring device receives all the CB messages repeatedly according to the rate continuously along with the 'Schedule message' regarding the scheduling of the CB messages.

The test mobile receives all the CB messages completely.

2 Change the text of one of the message and observe the Air Interface monitoring device and test mobile for 3 minutes.

The Air Interface monitoring device receives all the CB message only the text of one of the message is changed, the messages are received repeatedly as per the rate along with the 'Schedule message'.

The test mobile receives only the CB



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output message that was changed.

3 Break the LAPD link of the BCCH TRX and connect after 1 minute and observe on the Air Interface monitoring device.

LAPD gets established successfully and the carrier reaches supervisory state.

The CB messages and 'Schedule Messages' can be seen being received by the Air Interface device.

4 Give the BTS object a reset (To the BTS object under observation) from BTS Manager.

Observe the Air Interface monitoring device.

The BTS comes back to supervisory state after the reset.

The Air Interface monitoring device receives all the CB messages repeatedly according to the rate with the 'Schedule message'.

2.9.3 Short Message Service (SMS) Point-to-Point

Overview Short message service is a mechanism of delivery of short messages over the mobile networks. It is a store and forward way of transmitting messages to and from mobiles. The message (text only) from the sending mobile is stored in the short message center (SMSC) which then forwards it to the destination mobile.

These characters can be text (alphanumeric) or binary non-text short messages. Since SMS makes use of signalling channels as opposed to dedicated channels, these messages can be sent/received simultaneously with the voice/data/fax service over a GSM network.

Scope of testing

This test plan contains test cases pertaining to:

• Point-to-Point SMS when the mobiles are IDLE.

• Point-to-Point SMS when the mobiles are BUSY.

• Point-to-Point SMS when the mobiles are GPRS-attached.

Test cases

Pos Name Comment

1 Point-to-Point SMS when Mobiles are IDLE 2+2+2, Non Hopping, Combined SDCCH

2 Point-to-Point SMS when Mobiles are IDLE 2+2+2, Non Hopping, Non-combined SDCCH

3 Point-to-Point SMS when Mobiles are 2+2+2, Non Hopping,


DN0749988 Issue 2-0 en 18/01/2008


311 (381)

Pos Name Comment BUSY TCH/D, EFR codec

4 Point-to-Point SMS when Mobiles are BUSY

2+2+2, Non Hopping, TCH/D, AMR/FR codec

5 Point-to-Point SMS when Mobiles are BUSY

2+2+2, Non Hopping, TCH/H, AMR/HR codec

6 Point-to-Point SMS when Mobiles are in GPRS Attach

2+2+2, Non Hopping,

7 Point-to-Point SMS through GPRS network 2+2+2, Non Hopping,

2.9.3.1 Point-to-Point SMS when Mobiles are IDLE

This test case verifies the functionality of Point-to-Point SMS, which is sent on the SDCCH channel when the mobiles are in 'Idle' mode. The various signalling messages exchanged are also observed and verified on the Abis interface.


1. The BTS is in supervisory state with no unexpected alarms.

2. Test mobiles MS 1 and MS 2 are attached to Sector 1 and Sector 2 of the BTS respectively.


1 Initiate an SMS from MS 1 to MS 2. SMS is successfully initiated by MS 1 and received by MS 2.

2 Observe the messages for the SMS transfer on the GSM Abis Analyser for the originating MS (that is, for MS 1).

The “Timeslot/Channel Nr." information elements in “Channel Activation” message indicate the timeslot/sub-channel number on which the SMS is initiated.

[SDCCH/4 OR SDCCH/8 sub-channel]

The "EST IND" message on this SDCCH sub-channel with the 'CM Service Type' set as SMS indicate that the MO-SMS is initiated using SDCCH.

3 Observe the messages for the SMS transfer on the GSM Abis Analyser for the terminating MS (that is, for MS 2).

The “Timeslot/Channel Nr." information elements in “Channel Activation” message indicate the timeslot/sub-channel number on which the SMS is received.




DN0749988Issue 2-0 en18/01/2008


The "EST. REQ" message on this SDCCH sub-channel with the SAPI Indicator set to "3" indicates that MT SMS has been terminated on SDCCH.

4 Verify that the message (SMS) sent from MS 1 and the received message received by MS 2 are the same.

The message (SMS) sent from MS 1 and the message received by MS 2 are the same.

5 Initiate 10 more SMS from MS 1 to MS 2 of varying lengths including a blank SMS and an SMS with length as 160 characters.

All the SMS which are initiated from MS 1 are received successfully by MS 2.

All the SMS received at MS 2 contain exactly the same characters as the SMS initiated by MS 1.

6 Initiate a concatenated SMS (SMS of length exceeding 160 characters and therefore sent as multiple messages) from MS1 to MS2.

Note: The concatenated SMS should have lengths greater than 320 characters)

The concatenated SMS is successfully initiated by MS 1 and received by MS 2.

The messages initiated from MS 1 and received by MS 2 are the same.

7 Initiate 5 more concatenated SMS from MS 1 to MS 2 with varying lengths.

All the concatenated SMS which are initiated from MS 1 are received successfully by MS 2.


2.9.3.2 Point-to-Point SMS when Mobiles are BUSY

This test case verifies the functionality of Point to Point SMS with ongoing call which is sent on the SACCH/TCH. To accomplish this, SMSs are sent from and received by test mobiles for which a call is active, and the messages are observed for the SMS transfer on the Abis to verify that SACCH/TCH is used for the same.


1. The BTS is in supervisory state with no unexpected alarms.

2. Test mobiles MS 1, MS 2 and MS 3 are attached to the BTS.


1 Initiate a mobile to mobile call between MS 1 and MS 2.

Actively listen at both ends of the call MS 1 and MS 2 to verify that the voice quality is


The “Channel Mode/Speech Coding Algorithm” information in “Channel Activation” message indicates the codec


DN0749988 Issue 2-0 en 18/01/2008


313 (381)

Step Input Expected output good. used for the call.

The "Channel Mode/Speech Coding Algorithm" information as "HALF RATE" and "3" indicate that the codec is "AMR/HR".

The "Channel Mode" information as "FULL RATE" with the Speech Coding Algorithm set as"2" and "3" indicate that the codec is "EFR" and "AMR/FR" respectively.


2 While the call is still in progress, initiate an SMS from MS 3 to MS 1.

Observe the traces on the Abis interface using GSM Abis Analyser.

The SMS is successfully initiated by MS 3 and received by MS 1.

The "EST IND" message on SDCCH sub-channel with the "CM Service Type" set as SMS indicate that the MO-SMS is initiated using SDCCH.

The "EST. REQ" message on the TCH channel on which MS 1 is active with the SAPI Indicator set to "3" indicates that MT SMS has been terminated on TCH.


3 While the call is in progress, initiate an SMS from MS1 to MS2.

Observe the traces on the Abis interface using GSM Abis Analyser.

SMS is successfully sent by MS 1 and delivered to MS 2.

The "DATA IND" message on the TCH channel on which MS 1 is active with the CM Service Type information element as "SMS" indicates that MO SMS has been initiated on TCH.

The "EST. REQ" message on the TCH channel on which MS 2 is active with the SAPI Indicator set to "3" indicates that MT SMS has been terminated on TCH.

The message (SMS) sent from MS 1 and the message (SMS) received by MS 2 are the same.

4 While the call is in progress and the SMS is sent or received, verify that there are no unwanted disturbances.

Active listening at MS 1 and MS 2 indicates that there are no unwanted disturbances at MS 1 and MS 2 when the SMSs are sent or received.

5 While the call is in progress, initiate SMS from MS1 to MS2 for varying lengths of the message.

All the SMSs that are initiated from MS 1 are delivered to MS 2.



DN0749988Issue 2-0 en18/01/2008


Initiate SMS for various lengths, 0-160 characters, and at least 10 SMS of varying lengths.

The message (SMS) sent from MS 1 and the message (SMS) received by MS 2 are the same.


Note: The concatenated SMS should have lengths greater than 320 characters)

The concatenated SMS is successfully initiated by MS 1 and received by MS 2.



All the concatenated SMS which are initiated from MS 1 are received successfully by MS 2.


Active listening at MS 1 and MS 2 indicates that there are no unwanted disturbances at MS 1 and MS 2 when the SMSs are sent or received.

2.9.3.3 Point-to-Point SMS when Mobiles are in GPRS Attach

This test case verifies the functionality of Point to Point SMS for GPRS-attached mobiles.


• SGSN


1. The BTS site in operational state with no unexpected alarms.

2. GPRS is enabled at the site.

‘ZEQV:BTS=<bts_id>:GPRS=’Y’,CDED=1,CDEF=1,CMAX=100:;

- Conventional Abis.

3. Test mobiles are attached to the BTS. The ‘G’ symbol is present on the screen of the mobile station.

4. Test mobiles are in 'Ready' state.

5. Default parameters are set at the BSC.



DN0749988 Issue 2-0 en 18/01/2008


315 (381)


1 Initiate an SMS from MS 1 to MS 2. The SMS is successfully initiated by MS 1 and received by MS 2 over the circuit switched network.

2 Observe the messages for the SMS transfer on the GSM Abis Analyser for the originating MS (that is, for MS 1).

The “Timeslot/Channel Nr.” information elements in “Channel Activation” message indicate the timeslot and the sub-channel number on which the SMS is initiated.


The "EST IND" message on this SDCCH sub-channel with the 'CM Service Type' set as SMS indicate that the MO-SMS is initiated using SDCCH.

3 Observe the messages for the SMS transfer on the GSM Abis Analyser for the terminating MS (that is, for MS 2).

The 'CS-PAGING CMD' message is observed on the GSM Abis Analyser.The 'CHAN RQD' message is observed as response to it.

The “Timeslot/Channel Nr.” information elements in “Channel Activation” message indicate the timeslot and sub-channel number on which the SMS is received.


The "EST. REQ" message on this SDCCH sub-channel with the SAPI Indicator set to "3" indicates that MT SMS has been terminated on SDCCH.

4 Verify that the message (SMS) sent from MS 1 and the message received by MS 2 are the same.


5 Initiate 10 more SMS from MS 1 to MS 2 of varying lengths including a blank SMS and an SMS with length of 160 characters.




Note : The concatenated SMS should have lengths greater than 320 characters.








DN0749988Issue 2-0 en18/01/2008

2.9.3.4 Point-to-Point SMS through GPRS network

This test case verifies the functionality of Point to Point SMS for GPRS-attached mobiles through the GPRS network.


• SGSN


1. The BTS site in operational state with no unexpected alarms.

2. GPRS is enabled at the site. ‘ZEQV:BTS=<bts_id>:GPRS=’Y’,CDED=1,CDEF=1,CMAX=100:;

- Conventional Abis.

3. Test mobiles, MS 1 and MS 2 are attached to the GPRS network. The ‘G’ symbol is present on the screen of the Mobile Station.

4. Test mobiles MS 1 and MS 2 are in 'Ready' state.

Note: A prerequisite for this test case is that the network is configured for SMS transfer through the GPRS network and the necessary bearer services are provided to the test mobiles.


1 Initiate an SMS from MS 1 to MS 2.

Monitor the messages on the GSM Abis Analyser and monitor the PCU traces also.

SMS is successfully initiated by MS 1 and received by MS 2.

MS 1 and MS 2 use the packet network for originating and terminating the SMS.

SDCCH channels are not used for the transfer of messages. No "Channel Activation" messages for SDCCH are observed.

SMS is routed through LLC layer on SAPI 7 as observed on the PCU traces.

2 Verify that the message (SMS) sent from MS 1 and the message received by MS 2 are the same.


3 Initiate 10 more SMS from MS 1 to MS 2 of varying lengths, including a blank SMS and an SMS with length of 160 characters.




DN0749988 Issue 2-0 en 18/01/2008


317 (381)


4 Initiate a concatenated mobile to mobile SMS (SMS of length exceeding 160 characters and therefore sent as multiple messages) from MS 1 to MS 2.

Note: The concatenated SMS should have lengths greater than 320 characters.






2.9.4 Short Message Cell Broadcast

Overview Short Message Service Cell Broadcast is a service in which short messages may be broadcast from a PLMN to Mobile Stations (MS). Reception of SMSCB messages by the MS is only possible in idle mode.

The SMS Cell Broadcast service is designed to minimise the battery usage requirements for the MS. The MS can read the first part of a CB message and then decide whether or not to read the rest of the message.

Scope of testing This test plan contains test cases pertaining to SMS-CB without DRX.

Test cases

Pos Name Comment

1 Short message cell broadcast - DRX OFF 2+4+2, Non Hopping, Combined BCCH Sector

2 Short message cell broadcast - DRX OFF 2+4+2, Non Hopping, Non Combined BCCH Sector

2.9.4.1 Short Message Cell Broadcast - DRX OFF

The objective of the test case is to verify that all the cell broadcast messages that are created and activated at the BSC are properly



DN0749988Issue 2-0 en18/01/2008

transmitted on the air as per the repetition rate and received by the mobile when DRX is disabled in the cell.

Hardware tools:

• Air Interface monitoring device


1. Messages with the below attributes should be created and activated at the BSC with different text.

− Number of pages = 2 pages, repetition rate = 2 seconds

− Number of pages = 15 pages, repetition rate = 60 seconds

2. BTS Manager is connected to the system.


1 Latch the Air Interface monitoring device and the test mobiles to the BCCH frequency and observe the Air Interface monitoring device and test mobile for 3 minutes.

The Air Interface monitoring device and test mobiles successfully latched.

The Air Interface monitoring device receives all the CB messages repeatedly according to the rate.

The test mobile receives all the CB messages completely.

2 Change the text of one of the messages and observe the Air Interface monitoring device and test mobile for 3 minutes.

Both devices should receive the message with the changed text. (Note that the Air Interface monitoring device repeatedly receives all the CB messages but the test mobile receives only the changed CB message once.)

3 Break the LAPD link of the BCCH TRX and connect after 1 minute and observe the Air Interface monitoring device.

LAPD gets established successfully and the carrier reaches supervisory.

The CB messages can be seen being received by the Air Interface monitoring device.

4 Give the BTS object a reset (to the BTS object under observation) from BTS Manager.

Observe the Air Interface monitoring device.

The BTS comes back to supervisory after the reset.

The CB messages can be seen being received repeatedly by the Air Interface monitoring device as per the repetition rate.


DN0749988 Issue 2-0 en 18/01/2008


319 (381)

2.9.5 Remote Interrogation of Serial and Version Numbers

Overview The serial numbers and hardware version numbers of BTS units are stored in each unit by the manufacturer and detected automatically by the BTS SW at start-up and/or adding or replacing units. For passive BTS units like EWxA WBC module, cabinet, power supply units, environmental shields and filters the serial number shall be provided by the user during BTS commissioning. The serial numbers and version numbers can be read from the NetAct via the BSC so that the precise type of equipment and configuration is obtained remotely without a site visit.

Scope of testing The testing scope is limited to the verification of serial number and hardware version number of the BTS units remotely through the Nokia NetAct application. Also check for the updates in the NetAct HW Browser when the BTS units like EXxA TRX Modules are replaced when the BTS is operational.

Test cases

Pos Name Comment

1 Remote Interrogation of Serial Number and Version Number with ERxx DDU module in sector

8 Omni, 2-Way, PIU transmission card FIFA

2 Remote interrogation of serial and version number when EXxx TRX module is replaced

8+8+8, 4-Way , PIU transmission card FIFA

3 Remote interrogation of serial and version number when EXxx TRX module is replaced

4+4,2 Way combining, EOCA unit 1 - Sector 1, EOCA unit 2 - Sector 2

4 Remote Interrogation of Serial Number and Version Number with ECxx RTC module in sector

6 + 6, Cavity Combining, PIU transmission card FIPA

5 Remote Interrogation of Serial Number and Version Number After Passive Unit Details are Changed Through Append Commissioning

8 Omni, 2-Way



DN0749988Issue 2-0 en18/01/2008

2.9.5.1 Remote Interrogation of Serial Number and Version Number with ERxx DDU Module in Sector

The objective of this test case is the verification of serial number and hardware versions of the BTS units remotely through the Nokia NetAct Application. Check for the match between versions stored in the units by the manufacturer and the ones reported by the BTS at startup. For passive units like EWxx WBC Modules, check for the match between versions specified by the operator during commissioning and the ones reported by the BTS.


• Nokia NetAct Server


• The BTS is commissioned and the product codes and serial numbers of the EWxx WBC passive units are specified correctly during commissioning.


• The Nokia NetAct application is running.

• Hardware Upload is done from Top Level User Interface (TLUI) for the target BTS.


1 In the Nokia NetAct server from the start page click on ‘Administration’ to find the HW browser application. Double-click the HW browser.

Select ‘BCF’ from the network element type drop-down list and click Search.

Select the target BTS Site from the list of BCFs.

Hardware Browser displays the following HW details for ESMA System Module, ERxx DDU Module, EXxx TRX Module, EWxA WBC Module and PIU Transmission card:

Unit Type

Unit Identifier

Vendor Name

Identification Code

Operational State

Serial Number

Version

2 Check the HW units for the Unit Identifier, Vendor Name, Identification Code, Serial Number and Version.

Compare the serial number of all the HW units between Hardware Browser with actual physical details at the site. They should match.

Verify from the HW browser, EXxx TRX modules have the correct EWxA WBC


DN0749988 Issue 2-0 en 18/01/2008


321 (381)

Step Input Expected output modules associated with them as specified during commissioning.

3 Check the physical connection of EWxx WBC Modules with the EXxx TRX Modules.

Check the association of EWxx WBC Modules with the EXxx TRX Modules in the Hardware Browser.

The physical association will be the same as the one reported in the HW Browser.

2.9.5.2 Remote Interrogation of Serial and Version Number when EXxx TRX Module Is Replaced

The objective of this test case is the verification of serial number and hardware version of the BTS modules remotely through Nokia NetAct application.

Check for the serial number and hardware version is updated in the NetAct HW Browser when the BTS module, such as EXxx TRX Module, is replaced when the site is operational.




• The BTS is commissioned and the product codes and identification for passive units are provided during commissioning.

• The target BCF is in supervisory state as seen in Flexi EDGE BTS Manager.


• Hardware upload is done from Top Level User Interface (TLUI) for the target BTS.




Select the target BTS Site from the list of

Hardware Browser displays the following HW details for ERxx DDU Module, ESMA System Module, EXxx TRX Module, EWxA WBC Module, PIU Transmission card and EOCA Optical converter module Units (if used) :

Unit Type



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output BCFs. Unit Identifier

Vendor Name

Identification Code

Operational State

Serial Number

Version

2 From the Flexi EDGE BTS Manager, block the TRX Objects 3 and 4.

Check the object state of TRX 3 and TRX 4.

In the Flexi EDGE BTS Manager, the object states should be shown as Blocked and the TRX Sig should be OFF.

3 Switch off the power of the EXxx TRX Module from sector 2 using PDU Control from Flexi EDGE BTS Manager.

Replace the EXxx TRX Module in Sector 2 with a different EXxx TRX Module.

Switch on the power of the EXxx TRX Module using PDU Control from Flexi EDGE BTS Manager.

4 Unblock TRX3 and TRX4 from Flexi EDGE BTS Manager.

The TRXs objects TRX3 and TRX4 are reset and come back to working state.

5 Hardware Information upload through Nokia NetAct server is done for the target BTS.

Hardware information upload is successful.

6 Fetch the HW version and serial numbers of the new EXxx TRX Module from Hardware Browser for the target BCF in Nokia NetAct server.

Verify if the HW browser shows updated information on the HW information for the new EXxx TRX Module.

Compare the serial number of the new EXxx TRX Module between Hardware Browser and with actual physical details at site. They should match.

7 Check the physical connection of the EWXx WBC Modules with the EXxx TRX Modules.

Check the association of the EWXx WBC Modules with the EXxx TRX Modules in the Hardware Browser.

The physical association will be the same as the one reported in the HW Browser.

2.9.5.3 Remote Interrogation of Serial Number and Version Number with ECxx RTC Module in Sector

The objective of this test case is the verification of serial number and hardware versions of the BTS units remotely through Nokia NetAct


DN0749988 Issue 2-0 en 18/01/2008


323 (381)

application. Check for the match between versions stored in the units by the manufacturer and the ones reported by BTS at startup. For passive units, such as MHAs connected to ECxx RTC Modules, check for the correct association between the MHA units and the ECxx RTC units to which they are connected.




• The BTS is commissioned and the product codes and serial numbers of the MHAs are specified correctly during commissioning.



• Hardware upload is done from Top Level User Interface (TLUI) for the target BTS.


1 In the Nokia NetAct server, from the start page click ‘Administration’ to find the HW browser application. Double-click the HW browser.

Select ‘BCF’ from the network element type dropdown list and click Search.

Select the target BTS site from the list of BCFs.

Hardware Browser displays the following HW details for ESMA System Module, ESEA System Extension Module, ECxx RTC Module, EXxx TRX Module, MHA and PIU Transmission card:

Unit Type

Unit Identifier

Vendor Name

Identification Code

Operational State

Serial Number

Version

2 Check the HW units for the Unit Type, Unit identifier, Vendor Name, identification Code, Serial number and Version.

Compare for all the HW units between Hardware Browser with actual physical details at site. These should match.

Check for the correct association between the BTS units like ECxx RTC Modules and the MHAs connected to them.

Verify from the HW browser that ECxx RTC modules have the correct MHAs associated with them as specified during



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output commissioning.

2.9.5.4 Remote Interrogation of Serial Number and Version Number after Passive Unit Details are Changed Through Append Commissioning

The objective of this test case is to verify that the passive unit details of a WBC are correctly reported in the NetAct Hardware browser when they are changed through Append Commissioning for a BTS site in ‘Supervisory’ state.


The cabling has been done correctly as mentioned in the test case comment.

Pre-setup:

• The BTS site is in 'Supervisory' state without any unexpected alarms

• Flexi EDGE BTS Manager is connected to the BTS site.




Select the target BTS Site from the list of BCFs.

Hardware browser displays the following HW details for ESMA System Module, ERxx DDU Module, EXxx TRX Module, EWxA WBC Module and PIU Transmission card:

Unit Type

Unit Identifier

Vendor Name

Identification Code

Operational State

Serial Number

Version

2 Write down the Unit Identifier of all the EWXx WBC Modules.

3 Fetch the SCF from BTS Manager. SCF is successfully displayed to the user.

The SCF is saved on the PC.

4 Block one sector from the Flexi EDGE BTS Manager.

Switch off the power of the EXxx TRX Module using PDU control in Flexi EDGE BTS


DN0749988 Issue 2-0 en 18/01/2008


325 (381)

Step Input Expected output Manager.

5 Remove the WBC being connected to TRX object and replace it with a new EWxx WBC Module of the same band.

Switch on the power of the EXxx TRX Module using PDU control in Flexi EDGE BTS Manager.

6 Unblock the sector from the Flexi EDGE BTS Manager.

The TRXs in the EXxx TRX modules comes to supervisory state after reset.

7 Using the Flexi EDGE BTS Manager Commissioning Wizard commission the site using the SCF file saved in step 3.

Update the serial number and product code of the new WBC being connected to TRX.

Click 'Send SCF' .

View the SCF details as shown in BTS Manager and verify that Commissioning mode is shown as 'APPEND'.

8 Wait for the completion of the commissioning process.

Check the commissioning report.

The Commissioning Wizard shows that commissioning is successful.

The commissioning report executive summary shows:

Commissioning Result: SUCCESSFUL

9 Upload the current BTS unit details from the NetAct HW Browser application.

Check for the EWxx WBC Modules' details.

The Unit Identifier for the changed EWXx WBC Module matches with the one specified during the last commissioning process.

For the remaining EWxx WBC Modules, the Unit Identifiers are the same as the ones noted in step 2.



DN0749988Issue 2-0 en18/01/2008

Flexi EDGE BTS Maintenance

DN0749988 Issue 2-0 en 18/01/2008


327 (381)

3 Flexi EDGE BTS Maintenance The section covers the verification of the maintenance actions of the BTS site when using Flexi EDGE BTS SW release EP1.1.

3.1 Flexi EDGE BTS Module Replacement

3.1.1 BTS Unit Replacement

Overview In the field, due to various reasons, at one time or other, BTS units need to be replaced. The following different types of units are used in a BTS:

• ECxA RTC Module

• EXxA TRX Module

• ERxA DDU Module

• ESEA System Extension Module

• FSEA Flexi Alarm Extension Module

Scope of testing The scope of this test plan is to verify the procedures for BTS module replacement in a working BTS site.

Configuration As per the test case comment. If nothing is given in the case comment, use any BTS configuration.

Settings Configuring EAC lines (Line 19 to line 24) at the BSC, which will automatically use FSEA module at the BTS.



DN0749988Issue 2-0 en18/01/2008

Test cases

Pos Name Comment

1 Replacement of EXxA TRX module controlling ERxA DDU module

2+4+2, use BTS Manager block/unblock

2 Replacement of ECxA RTC module 6+6 BB Hopping, use BTS Manager block/unblock

3 Replacement of ERxA DDU module 2+4+2, use BTS Manager block/unblock

4 Replacement of EXxA TRX Module (used with ECxA RTC Module)

6+6 BB Hopping, use BSC lock/unlock

5 Replacement of ESEA System Extension Module

6+6, use BSC lock/unlock

6 Replacement of EXxA TRX module not controlling ERxA DDU module

2+4+2, use BSC lock/unlock

7 Replacement of FSEA Alarm Extension Module

--

3.1.1.1 Replacement of EXxA TRX Module Controlling ERxA DDU Module

Objective is to verify that EXxA TRX module, controlling ERxA DDU module can be replaced without disturbing the operation of other sectors of the BTS.


• The BTS site is commissioned and in supervisory state with no unexpected alarms.

• Flexi EDGE BTS Manager is locally connected to the BTS site


1 Make a call on BTS sector 1 and 3. Successful calls are made.

2 Go to Flexi EDGE BTS Manager and verify the HW versions of all the HW units connected to the BTS. Verify also the Ethernet cabling of all the HW units connected to the BTS.

Product code, module ID, version and serial number as well as cabling information are correctly shown at Flexi EDGE BTS Manager.

3 Block the BTS object 2 from Flexi EDGE BTS Manager.

BTS object 2 is successfully blocked as seen at the Flexi EDGE BTS Manager.

4 At Flexi EDGE BTS Manager,

Go to BTS Control Power Control Select


DN0749988 Issue 2-0 en 18/01/2008


329 (381)

Step Input Expected output Power distribution Unit ID for EXxA TRX Module, which is controlling ERxA DDU Module of BTS scetor 2, and change it to 'Turn OFF' state.

Observe the EXxA TRX Module and ERxA DDU Module at Flexi EDGE BTS Manager.

The colour of EXxA and ERxA DDU modules turns gray.

5 Replace EXxA TRX Module with the different EXxA TRX Module.

At BTS Manager, go to BTS Control Power Control Select Power distribution Unit ID for the TRX module, which is controlling ERxA DDU Module, and change it to 'Turn ON' state.

The newly replaced EXxA TRX Module and ERxA DDU Module are autodetected and reach configuring state.

6 Go to Flexi EDGE BTS Manager and verify the HW versions of all the HW units connected to the BTS. Verify the Ethernet cabling of all the HW units connected to the BTS.


7 Unblock the BTS object 2 from Flexi EDGE BTS Manager.

BTS object 2 is successfully unblocked and reached in supervisory state.

8 Attempt a call for BTS object 2. Calls are placed succesfully.

9 Observe the calls made on other sectors. Calls are ongoing without any disruption.

3.1.1.2 Replacement of ECxA RTC Module

The objective is to verify that the ECxA RTC Module can be replaced without impacting operations in other sectors of the BTS.

Test case execution ECxA RTC Modules 1 and 2 are associated with BTS objects 1 and 2 respectively.

Pre-setup:

• Flexi EDGE BTS Manager is connected locally.

• The BTS site is in operational state with no active alarms pending.


1 Initiate calls in all BTS object 2. Calls are successful.





DN0749988Issue 2-0 en18/01/2008



Observe the calls in other sector.

BTS objects are successfully blocked.

Calls in other sector are ongoing.

4 At Flexi EDGE BTS Manager, go to BTS Control Power Control Select Power distribution Unit ID for RTC module 1, and change it to 'Turn OFF' state.

Observe the RTC module at BTS Manager.

The colour of ECxA RTC Module 1 turns gray.

5 Replace ECxA RTC Module by a different RTC module in the BTS object 1.

At BTS Manager, go to BTS Control Power Control Select Power distribution Unit ID for RTC module 1, and change it to 'Turn ON' state.

ECxA RTC module 1 is autodetected and comes to configuring state.


Product code, module ID, version and serial number as well as cabling Information are correctly shown at Flexi EDGE BTS Manager.


The newly replaced RTC Module reaches supervisory state.

BTS object 1 and associated TRXs reach supervisory state.

8 Observe the calls in the other sector. Calls are still going on, without any disruption.

9 Make calls in BTS object 1. Calls are placed succesfully.

3.1.1.3 Replacement of ERxA DDU Module

The objective is to verify that the ERxA DDU module connected with the EXxA TRX module, can be replaced without disturbing the operation of other sectors of the BTS.



• Flexi EDGE BTS Manager is locally connected to the BTS site.


DN0749988 Issue 2-0 en 18/01/2008


331 (381)


1 Make a call on BTS sectors 1 and 3. Successful calls are made.




BTS object 2 is successfully blocked.

4 At BTS Manager, go to BTS Control Power Control Select Power distribution Unit ID for the TRX module, which is controlling ERxA DDU Module of sector 2, and change it to 'Turn OFF' state.

Observe the EXxA TRX Module and ERxA DDU Module at Flexi EDGE BTS Manager.

The colour of EXxA TRX Module and ERxA DDU Modules turns gray.

5 Replace the ERxA DDU Module with the different ERxA DDU Module.

At BTS Manager, go to BTS Control Power Control Select Power distribution Unit ID for the TRX module which is not controlling the ERxA DDU Module, and change it to 'Turn ON' state.

The newly replaced ERxA DDU Module and the TRX Module are autodetected.

6 Go to Flexi EDGE BTS Manager and verify the HW versions of all the HW units connected to the BTS.

Also verify the cabling of all the HW units connected to the BTS.

The product code, module ID, version, serial number and cabling information are correctly shown at Flexi EDGE BTS Manager.


BTS object 2 is successfully unblocked and reaches supervisory state.

8 Attempt a call for BTS object 2. Calls are placed successfully.

9 Observe the calls made on other sectors. Calls are ongoing without any disruption.

3.1.1.4 Replacement of EXxA TRX Module (used with ECxA RTC Module)

The objective is to verify that the EXxA TRX Module connected with the RTC (ECxA) module can be replaced without disturbing the operation of other parts of the BTS.

Test case execution



DN0749988Issue 2-0 en18/01/2008

ECxA RTC Modules 1 and 2 are associated with BTS objects 1 and 2 respectively.

Pre-setup:

• Flexi BTS EDGE BTS Manager is connected locally.

• The BTS site is in operational state with no active alarm pending.


1 Initiate calls in BTS object 2. Calls are successfully made.



3 Lock the BTS object 1 from the BSC. The BTS object is successfully locked.

4 At BTS Manager, go to BTS Control Power Control Select Power distribution Unit ID for the TRX module in the BTS object 1, and change it to 'Turn OFF' state.

Observe EXxA TRX Modules at Flexi EDGE BTS Manager.

The colour of EXxA TRX Modules turns gray.

5 Replace TRX module (powered off in step 4) by a different TRX module.

At BTS Manager, go to BTS Control - Power Control Select Power distribution Unit ID for TRX module and change it to 'Turn ON' state.

The newly replaced EXxA TRX Module is autodetected and reaches configuring state.


Verify the cabling of all the HW units connected to the BTS.

Product code, module ID, version and serial number and cabling information is correctly shown at Flexi EDGE BTS Manager.

7 Unlock the BTS object 1 from the BSC. BTS object is successfully unlocked and reached in supervisory state.

8 Attempt calls for BTS object 1. Calls are placed succesfully.

9 Observe the calls in other sector. Calls are still going on without any disruption.

3.1.1.5 Replacement of ESEA System Extension Module


DN0749988 Issue 2-0 en 18/01/2008


333 (381)

The objective of this case is to verify that the ESEA System Extension Module can be replaced. The replacement process impacts the operation of the BTS site.


• Flexi BTS EDGE BTS Manager is connected locally.

• The BTS site is in operational state with no active alarm pending.



Verify the Ethernet cabling of all the HW units connected to the BTS.

Product code, module ID, version and serial number as well as cabling information is correctly shown at Flexi EDGE BTS Manager.

2 Lock the BCF object from the BSC. BCF objects are successfully locked.

3 Switch off the power to ESEA System Extension Module.

Observe the state in the Flexi EDGE BTS Manager.

The ESEA System Extension Module and the TRX modules connected to ESEA System Extension Module turn gray.

4 Replace the ESEA module with a different module. Switch on the power to ESEA module.

The ESEA module and the connected EXxA TRX modules are autodetected.

TRXs are in Configuring state.



Product code, module ID, version, serial number and cabling information are correctly shown at Flexi BTS EDGE BTS Manager.

6 Unlock the BCF object from the BSC. The site is reset and then reaches supervisory state.

7 Repeat step 4. Same as in step 4.

8 Make calls in all sectors. Calls are placed successfully.

3.1.1.6 Replacement of EXxA TRX Module Not Controlling ERxA DDU Module

The objective of this test case is to verify that the EXxA TRX module (which is not controlling the ERxA DDU module) can be replaced without disturbing operations of other unrelated BTS objects.

Test case execution TRX module 2 is controlling the ERxA DDU module.



DN0749988Issue 2-0 en18/01/2008

Pre-setup:


• Flexi BTS EDGE Manager is locally connected to the BTS site.

• TRX object 3 is BCCH TRX. TRX objects 3, 4, 5, and 6 are associated with BTS object 2.

• Neighbours are defined for all the BTS objects and forced handover is enabled.


1 Make calls in all BTS sectors. Successful calls are made.



Product code, module ID, version and serial number and cabling information is correctly shown at Flexi BTS EDGE Manager.

3 Lock the TRX objects 5 and 6, (TRX module 3, which is not controlling ERxA DDU Module) from the BSC of sector 2.

TRX objects 5 and 6 are successfully locked.

4 At BTS Manager, go to BTS Control Power Control Select Power distribution Unit ID for the TRX module 3, which is not controlling ERxA DDU Module, and change it to 'Turn Off'' state.

The colour of EXxA TRX Module turns gray.

5 Replace EXxA TRX Module with a different EXxA TRX Module.

At BTS Manager, go to BTS Control Power Control Select Power distribution Unit ID for the TRX module, which is not controlling ERxA DDU Module, and change it to 'Turn On' state.

The EXxA TRX Module is autodetected and reaches configuring state.



Product code, module ID, version and serial number and cabling information are correctly shown at Flexi EDGE BTS Manager.

7 Unlock the TRX objects 5 and 6 from the BSC.

TRX objects 5 and 6 are successfully unlocked and reach supervisory state.

8 Observe the calls made in step 1. Calls are still on going without any disruption.

9 Attempt calls for TRX objects 5 and 6. Calls are placed successfully.


DN0749988 Issue 2-0 en 18/01/2008


335 (381)

3.1.1.7 Replacement of FSEA Alarm Extension Module

The objective of this test case is to verify that the EAC extension HW module can be replaced. This entire process does not have any impact on other operations of the BTS site.



• The BTS site is in operational state with no active alarms pending.

• The FSEA module is connected and commissioned.

• Line no. 19 to 24 is configured at the BSC using the ZEFX command, with reporting Route as ACT, Polarity as open for active alarm and Severity as AL1 (Lowest priority alarm).


1 Make calls in all the BTS sectors. Successful calls are made.

2 Go to Flexi EDGE BTS Manager Test EAC Input and verify that lines 19 to 24 are configured with the defined polarity.

Configuration of lines 19-24 is correctly shown at Flexi EDGE BTS Manager.

3 Go to Flexi EDGE BTS Manager HW Module View and verify the product code, serial number, and description of the FSEA module in the passive unit view.

Product code and serial number is correctly shown at Flexi EDGE BTS Manager.

4 EAC input line 19 is made open at the FSEA module.


Alarm 7419 ’External alarm 19’ is active and reported.

5 Disconnect the FSEA module, connected to the EAC port, present at the ESMA HW module.

Observe the alarm at the BSC and BTS Manager.

Cancellation of alarm 7419 ’External alarm 19’ is reported.

6 Continue to observe the alarms at Flexi EDGE BTS Manager as well as on the BSC (MML command: ZEOL)

Within 20 seconds of disconnection of the FSEA module, alarm 7601 ‘ESMA System module has lost connection to FSEx External Alarm (EAC) module’ is reported.

7 Replace the FSEA module with a different FSEA Module.

Provide the product code and serial number information of the FSEA module with append commissioning of the BTS.

Observe the alarm reported at Flexi EDGE

The FSEA module is successfully replaced.

Within 20 seconds of the replacement of the FSEA module, cancellation of alarm 7601 is observed.



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output BTS Manager.

8 EAC input line 19 is made open at the FSEA module.


Alarm 7419 ’External alarm 19’ is active and reported.

9 Go to Flexi EDGE BTS Manager HW Module View and verify the product code, serial number, and description of the FSEA module in the passive unit view.

Product code and serial number are correctly shown at Flexi EDGE BTS Manager.

10 Go to Flexi EDGE BTS Manager Test EAC Input and verify that lines 19 to 24 are configured with the defined polarity.

Configuration of lines 19-24 is correctly shown at Flexi EDGE BTS Manager.

11 Observe the calls made. The calls are still going on without any disruption.

3.1.2 Transmission Units Replacement

Overview In the field, due to various reasons, at one time or other, BTS units need to be replaced. The transmission unit is an important unit, the replacement of which may cause distruption of services to the BTS concerned and to other BTSs in the transmission chain.

Different types of transmission units are used in a BTS. For the Abis interface E1, T1 and Nokia Flexi transmission equipment is commonly used.

Scope of testing The scope of the test cases covered under this release test plan is to test the Flexi EDGE BTS SW for recovery from transmission unit replacement. The observations to be made during the testing will include the recovery of BTS operations after the replacement of various available transmission units with or without in transmission. Information available through the Abis analyser, BSC, Flexi EDGE BTS Manager and MS will be used to provide the verdict of testing.

Test cases

Pos Name Comment

1 BCF Recovery after Transmission Unit Replacement

4+4+4, E1 FIPA

2 BCF Recovery after Transmission Unit 4+4+4, T1 FIPA


DN0749988 Issue 2-0 en 18/01/2008


337 (381)

Pos Name Comment Replacement

3 BCF Recovery after Transmission Unit Replacement

BCF1: 4+4, BCF2: 4+4, FIEA with Abis chaining

4 BCF Recovery after FIFA Unit replacement BCF1: 4+4, BCF2: 4+4, FIFA with Abis chaining

3.1.2.1 BCF Recovery after Transmission Unit Replacement

The objective of the test case is to verify the BCF recovery after the transmission unit has been replaced.


• Flexi EDGE BTS

• BSC S12

• In case of Abis chain configuration, the transmission capacity for the second BCF is routed through the first BCF.

Pre-setup:

• The TRX test is successful on all the TSs


• The serial number of the spare unit is noted down.

• The spare transmission unit was earlier configured with different transmission configuration.


1 From Flexi EDGE BTS Manager, enable a transmission interface that is not in use.

Observe the alarms at Flexi EDGE BTS Manager and the BSC.

With E1 interface, alarm 8050 'Loss of incoming 2M signal' (with T1 interface, alarm 8056 'Loss of incoming 1.5M signal') is raised for TRE1 for that interface at BTS Manager and the BSC.

2 Lock the BCF (first BCF in case of transmission chain) from the BSC.

The BCCH transmission is stopped. This is verified from the signal level at mobiles.

3 Switch OFF the ESMA power supply. Replace the existing transmission unit (from the first BCF in case of transmission chain) with the spare unit.

Switch ON the system module power supply. Unlock the BCF from the BSC.

After the startup procedure, the BCF comes to operational state.

The alarm raised in step 1 is present. No other alarms are observed.



DN0749988Issue 2-0 en18/01/2008


4 From Flexi EDGE BTS Manager verify that all the timeslot configurations at transmission unit. Observe cross-connection information.

All the transmission configuration parameters are available. The cross-connect configuration is unchanged.

5 Verify the operational state of all the BTSs at the BSC.

All BTSs are in operational state.

6 From the BTS Manager, verify the serial number of the replaced unit.

The BTS Manager shows the correct serial number for the replaced unit.

7 Remove the usage of the transmission interface that was enabled in step 1. Verify the alarms at BTS Manager and the BSC.

The 8050 alarm is cancelled both at Flexi EDGE BTS Manager and the BSC.

8 Place calls on each BTS object at least once. All the calls are successful.

3.1.2.2 BCF Recovery after FIFA Unit Replacement

The objective of the test case is to verify the BCF recovery after the FIFA transmission unit has been replaced.




• Flexi EDGE BTS

• BSC S12

• The transmission capacity for the second BCF is routed through the first BCF.

Pre-setup:

• The TRX test is successful on all the TSs


• The serial number of spare unit is written down.

• The spare transmission unit was earlier configured with different transmission configuration.


1 From Flexi EDGE BTS Manager, enable a transmission interface that is not in use.

Observe the alarms at Flexi EDGE BTS

Alarm 8066 'AIS 2M' is raised for TRE object 1 for that interface at BTS Manager and the BSC.


DN0749988 Issue 2-0 en 18/01/2008


339 (381)

Step Input Expected output Manager and the BSC.

2 From Flexi EDGE BTS Manager observe transmission configuration available at the transmission unit. Observe cross-connection information also.

Write down this information.

The transmission configuration parameters are available.

3 Lock the BCF (first BCF in case of transmission chain) from the BSC.


4 Switch OFF the power supply of the ESMA System Module in the BCF locked in step 2. Replace the existing FIFA transmission unit from the corresponding ESMA System Module, with the spare unit.

Switch ON the power supply of the ESMA System Module.

All the units are auto-detected and the BCF comes to configuring state after the BCF has been switched ON.

5 Using FlexiHub Manager, commission the FIFA with the correct RF parameters. Unlock the BCF from the BSC.

Observe the alarms at Flexi EDGE BTS Manager and the BSC.

After BCF unlock, the BCF comes to operational state.

The alarm raised in step 1 is present. No other alarm is observed.

6 From Flexi EDGE BTS Manager, observe the transmission configuration available at the transmission unit. Observe cross-connect information as well.

All the transmission configuration parameters are the same as noted down in step 2.

7 Verify the operational state of all the BTSs at the BSC.

All the BTSs are in operational state.

8 From Flexi EDGE BTS Manager, verify the serial number of the replaced unit.


9 Disable the transmission interface that was enabled in step 1. Verify the alarms at BTS Manager and the BSC.

The 8066 alarms are cancelled both at Flexi EDGE BTS Manager and the BSC.

10 Place calls on each TRX object at least once. All the calls are successful. The voice quality is good without any disturbance for all the calls.

3.1.2.3 BCF Recovery after FIEA (E1) Unit replaced with FIFA Unit

The objective of the test case is to verify the BCF recovery after the FIEA (E1) transmission unit is replaced with FIFA transmission unit.




DN0749988Issue 2-0 en18/01/2008

• One E1 transmission line is terminated on the BTS site.

• FIEA E1 is used as transmission unit for BTS site.

Pre-setup:

TRX test is successful on all the TSs

BCF and all the TRXs are operational without any major/minor alarm.

The serial number of spare unit is noted down.


1 From Flexi EDGE BTS Manager, observe transmission configuration available at transmision unit.

Also note down this information.

The transmission configuration parameters are available.

2 From Flexi EDGE BTS Manager, perform undo commissioning for the BTS site.

BTS Site ungergoes a reset and comes to uncommsssioning state. All hardware units are attached, autodetected and displayed correctly on Flexi EDGE BTS Manager.

3 Switch OFF the power supply of the ESMA System Module. Replace the existing FIEA transmission unit from the corresponding ESMA System Module, with the spare FIFA transmission unit.

Switch ON the power supply of the ESMA System Module.

All the units attached are autodetected and BCF comes to uncommisioned state after ESMA power supply is switched ON.

No unexpected alarm is reported on Flexi EDGE BTS Manager.

4 Using Flexi Hub Manager, commission the FIFA with correct RF parameters.

The card is commissioned successfully.

5 Commission the BTS site. Use transmission configuration information saved in step 1.

BTS Site is successfully commissioned and comes to supervisory state.

6 Verify the operational state of all the BTSs at BSC for BTS site.

All BTSs are in operational state.

7 From the Flexi EDGE BTS Manager, verify the serial number of the replaced unit.


8 Calls are placed on each TRX object at least once. All calls are successful. Voice quality is good without any disturbance for all calls.

3.1.3 Auxiliary Power Supply Unit Replacement

Overview In the field, due to various reasons, at one time or other, BTS units need to be replaced. The Auxilliary Power supply unit is an important unit, the


DN0749988 Issue 2-0 en 18/01/2008


341 (381)

replacement of which may cause disruption of services to the BTS concerned and to other BTSs in the transmission chain.

Scope of testing The scope of the test cases is the physical replacement of the Auxilliary Power supply Unit, then the update of the product code and serial number details with the Flexi EDGE BTS Manager to the BTS Site.

Test cases

Pos Name Comment

1 BCF Recovery after Auxiliary Power Supply Unit replacement

FPMA replacement

3.1.3.1 BCF Recovery after Auxiliary Power Supply Unit replacement

The objective of the test case is to verify the BCF recovery after the Auxiliary Power Supply unit has been replaced.




• The serial number of spare unit is noted down.


1 Lock the BCF from the BSC.

Switch OFF the mains power supply to the BTS.


2 Replace the existing power supply unit with the spare unit.

Switch ON the mains power supply. Unlock the BCF from the BSC.

Verify the operational state of all the BTSs at the BSC.

After reset all the TRXs come to operational state.

3 Observe BTS Manager and the BSC for alarms.

No alarm is observed for any object on the BCF.

4 Using BTS Manager, update the unit serial number and save it.

Fetch the site information and verify the serial

The serial number in the site information file is the same as that of the unit.



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output number for the power supply unit.

5 From the BTS Manager, verify the serial number of the replaced unit.


6 Place calls on each BTS object at least once. All the calls are successful.

Flexi EDGE BTS Site Installation

DN0749988 Issue 2-0 en 18/01/2008


343 (381)

4 Flexi EDGE BTS Site Installation The section covers the verification of commissioning of a Flexi EDGE BTS using SW release EP1.1, and the deployment of EP1.1 SW release from the BSC and NetAct.

4.1 Flexi EDGE BTS Site Commissioning

4.1.1 BTS Site Expansion

Overview To cater to the increase in traffic, the capacity of a BTS Site has to be increased. Capacity can be increased by adding additional EXxA TRX Modules to the sectors or adding EXxA TRX Modules in a cost-optimised solution and splitting additional capacity across two sectors. When adding capacity this can be to existing antenna or by adding additional combining units and antennas. Scope of testing The scope of testing covers the following

• Increasing the number of carriers in a sector

− Adding capacity to existing combiners

− Increasing size over 12 TRX thus taking ESEA into use

− Adding combining and antenna units to sector

Test cases

Pos Name Comment

1 Adding TRXs to Existing Sectors (with wide-band combining)

2+4+2 upgrade to 3+4+3

2 Adding TRXs to Existing Sectors (with 4+4 (BB Hopping)



DN0749988Issue 2-0 en18/01/2008

Pos Name Comment cavity combining) upgrade to 6+4

3 BTS Site Expansion from 4+4+4 Two Way Combining to 6+6+6 Two Way Combining

-

4.1.1.1 Adding TRXs to Existing Sectors (with Wide-Band Combining)

The objective of this test case is to verify that the capacity of an already operational site can be enhanced by adding new carriers to existing sectors having ERxx DDU modules. Also, it is verified that ongoing calls on existing carriers are not impacted.


Start with 2+4+2 to be expanded to 3+4+3 configuration.

For Feederless Site configuration, every sector should have a separate Opto unit.

Pre-setup:


• Site is commissioned with Site Commissioning File for 2+4+2.

• BCF is in Supervisory state with 2+4+2 configuration defined at the BSC.

• At the BSC, TRXs 1 and 2 are defined for Sector 1, TRXs 5, 6, 7, and 8 are defined for Sector 2 and TRXs 9 and10 are defined for Sector 3.



1 Establish calls on all TRX objects. Voice call is established successfully.


2 Using the Flexi EDGE BTS Manager, Go to BTS Control Power Control menu and ensure that the Power distribution unit for ports where new EXxx TRX modules are to be connected are turned off.

The state of Power distribution unit for ports where new EXxx TRX modules are to be connected is Off.

3 Add one new EXxx TRX modules to BTS site by connecting the bus cable and power cable correctly.

Perform RF cablings for the newly added EXxx TRX module using two new EWxx WBC

The newly connected EXxx module is autodetected as seen at the Flexi EDGE BTS Manager.


DN0749988 Issue 2-0 en 18/01/2008


345 (381)

Step Input Expected output modules such that each EXxx TRX modules serve the Sectors to be expanded.

At Flexi EDGE BTS Manager, go to BTS Control Power Control Select Power distribution Unit ID for concerned EXxx TRX modules and change it to 'Turn ON' state.

4 Open the Base Station View in Flexi EDGE BTS Manager, highlight the newly connected EXxx TRX module and verify the following properties against the label on the module.


Product code

Module identifier

Serial number

Hardware version

Network type

EXxx TRX Module properties displayed should exactly match with the label present on that module.

5 Using Change Settings in Commissioning Wizard,

- Enter the relevant Information (serial number) for the newly added passive units (EWxx WBC module).

- Allocate Traffic Time Slots for the newly added TRXs.

Append Commissioning is successful and Traffic is allocated for the newly added TRXs.

6 Check the operational state of all the TRXs at the Flexi EDGE BTS Manager.

The TRX objects in the newly added EXxx TRX Module are in configuring state.

The TRXs objects in the existing EXxx TRX modules continue to be in Supervisory state.

7 Check the status of the ongoing calls. All the calls are made in step 1 are still ongoing.

8 At the BSC, create TRX objects: TRX 3 in sector 1 and TRX 4 in sector 3 and unlock them.

Check at the Flexi EDGE BTS Manager the Operational State of all the existing TRXs.

The newly created TRX objects reach supervisory state without any unexpected alarm being reported for the BTS site.

Flexi EDGE BTS Manager continues to show Operational state as Supervisory for all the existing TRXs.

9 Check RF cable information for the newly added EXxx TRX module on Flexi EDGE BTS Manager.


10 From the BSC, run TRX tests for all the newly added TRXs and check the result at the BSC.

All the TRX tests are passed with BER and FER = 0.



DN0749988Issue 2-0 en18/01/2008


11 Flexi EDGE BTS Manager, retrieve the Site Information Report and check the information of the newly added module.

Site Information Report reflects the relevant information for the newly added module.

12 Establish one or more calls on the newly added TRXs.

Calls can be successfully established on the newly added TRXs.

4.1.1.2 Adding TRXs to Existing Sectors (with Cavity Combining)

The objective of this test case is to verify that the capacity of an already operational site can be enhanced by adding new carriers to existing sectors having ECxx RTC modules. Also, it is verified that ongoing calls on existing carriers are not impacted.


4+4, RTC combining configuration (to be expanded to 6+4 configuration).

Pre-setup:

• Flexi EDGE BTS Manager is connected to the Flexi EDGE BTS

• The site is commissioned with a site commissioning file for 6+6 (RTC) combining configuration and commissioning is successful

• The BCF is in supervisory state with 4+4, RTC combining configuration

• At the BSC, TRXs 1, 2, 3, and 4 are defined for Sector 1 and TRXs 7, 8, 9, 10 are defined for Sector 2

• Default TRX test parameters used and PMAX=0 set at the BSC


1 Establish calls on all TRX objects. The voice calls are established successfully.


2 Using the Flexi EDGE BTS Manager, go to BTS Control Power Control menu and ensure that the Power distribution unit for the port where the new EXxx TRX module is to be connected is turned off.

The state of Power distribution unit for the port where the new EXxx TRX module is to be connected is off.

3 Add a new EXxx TRX module to the BTS site by connecting the bus cable and power cable correctly. Make the necessary RF cablings

The newly connected EXxx TRX module is autodetected as seen at the Flexi EDGE BTS Manager.


DN0749988 Issue 2-0 en 18/01/2008


347 (381)

Step Input Expected output between the new EXxx TRX module and the ECxx RTC module in sector 1.

At Flexi EDGE BTS Manager, go to BTS Control Power Control Select Power distribution Unit ID for the concerned EXxx TRX modules and change it to 'Turn ON' state.



• Product code


• Serial number


• Network type

EXxx TRX Module properties displayed should exactly match the label on the module.

5 Using Change Settings in Commissioning Wizard, allocate Traffic Time Slots for the newly added TRXs

Append Commissioning is successful and traffic is allocated for the newly added TRXs.

6 Check the Operational State of all the TRXs at the Flexi EDGE BTS Manager.

The TRX objects in the newly added EXxx TRX module are in configuring state.


7 Check the status of the ongoing calls. All the calls are made in step 1 are still ongoing.

8 At the BSC,

1. Lock the sector 1 with forced handover.

2. Create TRX objects: TRX 5 and TRX 6 in sector 1

3. Unlock the TRX objects and unlock sector 1


Calls are handed over as commanded by BSC.

The newly created TRX objects reach supervisory state without any unexpected alarm being reported for BTS Site.


9 Check RF cables information for the newly added EXxx TRX modules on Flexi EDGE

Flexi EDGE BTS Manager displays the RF cables (both Tx and Rx) as in the actual



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output BTS Manager. physical connection.

10 From the BSC, run TRX tests for all the newly added TRXs and check the result at the BSC.

All the TRX tests are Passed with BER and FER = 0.

11 Flexi EDGE BTS Manager, retrieve the Site Information Report and check the information of the newly added modules.

The Site Information Report reflects the relevant information for the newly added modules.

12 Establish one or more calls on the newly added TRXs.

Calls can be successfully established on the newly added TRXs.

4.1.1.3 BTS Site Expansion from 4+4+4 Two Way Combining to 6+6+6 Two Way Combining

The objective of this test case is to verify that capacity of an already operational site can be enhanced by adding new carriers and ERxx DDU modules so that no change in cabling takes place for existing sectors. Also it is verified that on addition of ESEA System Extension Module, there is no impact on the current BTS site.


• 4+4+4 configuration (to be downgraded to 2+4+2 configuration).

Pre-setup:


• The site is commissioned with a site commissioning file for 4+4+4.

• The BCF is in supervisory state with 4+4+4 configuration defined at the BSC.

• At the BSC, TRXs 1, 2, 3, and 4 are defined for sector 1, TRXs 5, 6, 7, and 8 are defined for sector 2 and TRXs 9, 10, 11, and 12 are defined for sector 3.



• Set the First shutdown timer (NTIM) at BSC using ZEFM command


1 Power off the BTS site. BTS site is powered off.

2 Disconnect all the EXxA TRX Modules from ESMA System Module snd connect them to the ESEA System Extension Module. Also

All the units are connected correctly.


DN0749988 Issue 2-0 en 18/01/2008


349 (381)

Step Input Expected output connect the EXxA TRX Module modules 7, 9 and 11 to the ESEA System Extension Module.

One new EXxA TRX Module and ERxA module is added to each existing BTS object.

Also do the RF cabling for the newly connected EXxA TRX Modules.

Connect the ESEA System Extension Module to ESMA System Module.

3 Power on the BTS site.

Check Flexi EDGE BTS Manager for all units connected.

The BCF comes to supervisory state, with all configured TRXs' operational state as supervisory.

The ESEA System Extension Module is autodetected and correctly displayed in Flexi EDGE BTS Manager.

No unexpected alarm is observed in the Alarm window of Flexi EDGE BTS Manager.

All unconfigured EXxA TRX Modules are autodetected and are in configuring state in Flexi EDGE BTS Manager.



Product code

Module identifier

Serial number

Hardware version

Netwrk type

EXxx TRX Module properties displayed should exactly match the label on that module.

5 Using Change Settings in Commissioning Wizard,

- Enter the relevant Information (serial number) for the newly added passive units (EWxx WBC module).

- Update the RF cabling information

- Allocate Traffic Time Slots for the newly added TRXs on interface 2

Append Commissioning is successful and traffic is allocated for the newly added TRXs.

6 Check the Operational State of all the TRXs at the Flexi EDGE BTS Manager.

The TRX objects in the newly added EXxx TRX module are in configuring state.



DN0749988Issue 2-0 en18/01/2008



7 At the BSC, create TRX objects: TRX 13 and 14 in sector 1, TRX 17 and 18 in sector 2, and TRX 21 and 22 in sector 3. Unlock them.


The newly created TRX objects reach supervisory state without any unexpected alarm being reported for BTS Site.


8 Check RF cable information for the newly added EXxx TRX module on Flexi EDGE BTS Manager.

Flexi EDGE BTS Manager displays the RF cables (both Tx and Rx) as per the actual physical connection.

9 From the BSC, run TRX tests for all TRXs and check the result at the BSC.

All the TRX tests are passed with BER and FER = 0.

10 Flexi EDGE BTS Manager, retrieve the Site Information Report and check the information of all the modules.

Site Information Report reflects the relevant information for the all the modules.

11 Reset the BCF site from the BSC using MML command ZEFR.

The BCF object comes to supervisory state, with no unexpected alarm in Flexi EDGE BTS Manager alarm window.

12 Switch off the mains power supply to the battery backup unit, and check the status of EXxA TRX Modules and ERxA Dual Duplexer Modules in Flexi EDGE BTS Manager


All BCCH TRX are in supervisory state.

The EXxx TRX modules that were shut down are shown grey (dumb) with the IS icon at Flexi EDGE BTS Manager.

All ERxA Dual Duplexer modules, which have all TRX objects as non BCCH, are in shutdown state and are shown grey (dumb) at Flexi EDGE BTS Manager.

4.1.2 BTS Site Commissioning

Overview Commissioning a BTS involves tasks to enable the BTS to connect to the network. These tasks include the configuration of the transmission equipment and also some operational tests. The procedure involves providing general information about the BTS site, defining the hardware


DN0749988 Issue 2-0 en 18/01/2008


351 (381)

configuration of the BTS and the cabling information. Another important parameter defined is the traffic allocations for the BTS.

It is possible to commission the site using a Site Commissioning File (SCF). The Flexi EDGE BTS Manager Commissioning Wizard is used to commission the BTS. It is also possible to modify the commissioning of an already commissioned BTS. In this case, the SCF is used in Append mode.

The result of the commissioning is provided in the commissioning report, and included in the Site Information File.

Scope of testing The scope of testing covers success and failure scenarios, commonly expected during Commissioning of a Flexi EDGE BTS Site using BTS modules directly from the factory. The testing shall cover different BTS configurations, RF cabling, sector configurations, transmission interface for both success and failure scenarios.

Configuration All harware units should be on default factory settings.

Settings The BTS Object parameters are set to default at the BSC like PMAX = 0, Threshold Tx power = 47dbm for TRX test parameters.

GENA and EGENA parameters should be enabled at the BSC and relevant EDAP timeslots should be configured at the BSC and BTS Site. Specific details are given in the Pre-setup of each test case.

Test cases

Pos Name Comment

1 Successful Commissioning of a new BTS site

2 + 4 + 2


6 + 6 + 6, Cavity combining, MHA, BB Hopping


8 Omni, 4-way


12 Omni, with MHA, BB Hopping


3+3+3, cost optimised


4(GSM 1800) + 4(PGSM 900) + 4(EGSM 900), common BCCH for PGSM and EGSM



DN0749988Issue 2-0 en18/01/2008

Pos Name Comment sectors


2 + 2+ 2,


8 + 8, 2-Way Combining RF cables defined in SCF


4+4+4+4+4+4, 2 way combining


8+8, Antenna Hopping + RF Hopping


4+4+4, ESEA, Every sector has its own EOCA unit

12 BTS Site Commissioning with incorrect Connections of EXxx TRX Module Bus and Power cables

2 + 2 + 2

13 BTS Site Commissioning with incorrect Connections of EXxx TRX Module Bus and Power cables

6 + 6, BB Hopping,

14 BTS Site Commissioning with mismatch between RF Cabling in SCF and Physical Cabling

12 Omni, BB Hopping

15 BTS Site Commissioning with mismatch between RF Cabling in SCF and Physical Cabling

3+3+3, cost optimised

16 BTS Site Commissioning with Incorrect TCH Timeslot Information

2 + 2 + 2

17 BTS Site Commissioning with incorrect TRXSIG timeslot information

2 + 4 + 2

18 BTS Site Commissioning without Abis Link Connectivity

2+2+2+2+2+2

19 Successful Append Commissioning for an Operational BTS site

2 + 4 + 2, RF cabling defined in SCF

4.1.2.1 Successful Commissioning of a New BTS Site

The objective of this test case is to verify that a BTS site can be successfully commissioned and brought into ‘Supervisory’ state without any unexpected alarms when commissioned through a customised SCF template file, as specified in the test case comment.

Test case execution


DN0749988 Issue 2-0 en 18/01/2008


353 (381)

Configuration:

The cabling should be done correctly as per the site configuration mentioned in the test case comment.

For Feederless site configurations, every sector must be installed with a separate EOCA unit.

Pre-setup:

• The BCF is in uncommissioned state.


• Abis link is connected to the BTS site.

• The BTS site is created at the BSC with the frequency band and hopping parameters as specified. The administrative state of each object as 'Unlocked'.

• GENA, EGENA is enabled in all the sectors of the BTS site using the MML command ’ZEQV’ with CDED, CDEF and CMAX as 10.

• For every sector, 4 EDAP Abis timeslots are reserved for a TRX object on which the PS data transfer will be tested. For example, if the BTS site has 2 sectors, then 8 Abis timeslots should be reserved for EDAP on the Abis link.

• A barcode reader is installed on the Flexi EDGE BTS Manager PC for providing passive unit information like serial number and product code.


1 In the Flexi EDGE BTS Manager, go to the Commissioning Wizard.

Select "Commission from EasyWizard Template File".

Browse for the hardware template file that matches the hardware configuration used.

Browse for the transmission template file that matches the hardware configuration used.

Click Next.

The hardware template file name shall be shown in the file name for hardware template.

The transmission template file name shall be shown in the file name for transmission template.

Note: Choosing the right template file for the BTS type (outdoor or indoor) will help to fill in the details of passive units such as environmental shields and filters.

2 Provide the site specific information including the correct BCF Id.

Click "Next".

BCF Id is saved in the Commissioning Wizard.

3 Provide other details like Antenna details, The antenna details and MHA type (if given)



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output MHA type (Optional).

Click Next.

Note: Such information as serial number and product type for passive units is entered using the Barcode reader.

are saved in the Commissioning Wizard.

4 Choose the used Battery Backup Unit type (Optional) and provide hardware details.

Click "Next".

Note: Such information as serial number and product type for passive units is entered using the Barcode reader.

The Battery Backup Unit details (if given) are stored in the Commissioning Wizard.

5 Fill in Unit name, Serial number, Product type and description of other Optional passive units like EWxA WBC units, EAC (FSEA), Filters, cabinets, Power supply unit, shields etc.

Click "Next".

Note: Information like Serial number, Product type for Passive units are entered using the Barcode reader.

The SCF preview shows the content of the SCF file as provided in the previous steps.

6 Click "Send SCF".

Observe the Commissioning process.

Wait until the commissioning process completes in the Commissioning Wizard.

Observe the sequence of steps in the Commissioning process.

"Commissioning State" becomes green.

"BCF Waiting for LAPD" becomes green.

"BCF SW Downloading" becomes green.

"BCF Configuring" becomes green.

"Test Started" becomes green.

"Abis loop Test" becomes green.

"TRX Test" becomes green.

"Tests Completed" becomes green.

"Commissioning report" becomes highlighted.

Result is displayed as "Commissioning Successful".

7 Wait for the commissioning report to be received.

Save the commissioning report on the PC running Flexi EDGE BTS Manager.

Open it using a text editor.

The latest commissioning report executive summary shows:

Commissioning phase of SCF: FULL

Commissioning result: SUCCESSFUL


DN0749988 Issue 2-0 en 18/01/2008


355 (381)


Check the content of the commissioning report.

Note: In case BB hopping is enabled at BSC, then an additional note will be given as 'Commissioning test timer expired'.

Detailed Commissioning report has Sector Configuration as per the configuration at the BSC.

Usability Status of All 24 TRXs

Correct BTS HW Versions

Correct BTS SW Versions

Abis Test Results status 'PASS' for all the configured TRXs in the BCF.

TRX Test Results 'PASS' for all the configured TRXs in the BCF.

No unexpected alarm in BTS Alarms Test.

External TREs in Q1 port as configured in the BSC.

Cabling Details as per cabling physically at site.

Antenna Info as provided in SCF, if MHA is used.

LIF Settings as provided in SCF

Synchronisation as provided in SCF

Abis Termination as provided in SCF

Cross Connection as provided in SCF

8 Exit the Commissioning Wizard clicking the Finish button.

Check for the Operation states of the BCF and TRXs in the Flexi EDGE BTS Manager.

BCF and all TRXs reach supervisory state.

Fetch the SCF and verify that the RF cabling information displayed in SCF is the same as the physical connection at the site.

9 From Flexi EDGE BTS Manager, choose a TRX module randomly from the configuration and highlight it by clicking on the 'Highlight' button on the HW Module property window.

Check that the correct unit responds.

Repeat the highlighting command above for following modules:

For RTC configuration, highlight the ESEA System Extension module and a random RTC

HW Module LED is highlighted (Cycling of stable colours: Red - Yellow - Green - Red...) for the selected period.

After LED highlighting stops, verify that the HW module LED colour is the same as it was before this step.



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output module.

For DDU configuration, highlight any random DDU module.

Note: Default LED highlighting period is 5 seconds.

10 Upload the SIR, save as XML on a local PC.

Check the contents of the SIR for correctness.

The configuration details of the BTS site as provided at the BSC matches the information presented in the SIR.

Passive unit information (as entered in steps 3, 4, and 5) is correctly included in the SIR report.

The template specified under commissioning data is same as used for commissioning.

11 CS calls are placed and held for a minimum of 30 seconds via each TRX object in the BCF.

Calls can be established via each TRX and audio and measurement quality is good.

12 PS file transfer is made successfully via each BTS objects in the BCF.

File transfer is successfully made.

4.1.2.2 BTS Site Commissioning with Incorrect Connections of EXxx TRX Module Bus and Power Cables

The objective of this test case is to verify that a BTS site can be brought to 'Supervisory' state. The site is initially commissioned with incorrect connections of EXxx TRX modules to the ESMA System Module or ESEA System Extension Module. The BTS site will report a BCF-level alarm after commissioning and it will be cancelled after correcting the connections followed by a BCF reset.



Pre-setup:



• Bus cables and power cables are connected in the wrong order for EXxx TRX Modules 1 and 2 (the position of the power cables is swapped between power port 1 and 2 for the EXxx TRX Modules).

• The BTS site is created at the BSC with the administrative state of each object as 'Unlocked'.


DN0749988 Issue 2-0 en 18/01/2008


357 (381)


• For every sector, 4 EDAP Abis timeslots are reserved for a TRX object on which PS data transfer will be tested. For example, if the BTS site has 2 sectors then 8 Abis timeslots should be reserved for EDAP on the Abis link.



Select "Commission from Easy Wizard Template File".

Select the appropriate SCF template files and commission the BTS.

The BTS gets commissioned.

The commissioning report mentions

Commissioning Result: PARTIALLY FAILED

Power Cable Test failure for EXxx TRX Modules.

The BCF comes to the Supervisory state.

2 Check the alarm window of the Flexi EDGE BTS Manager.

Alarm 7601 "BCF operation degraded, Module power cable connections are incorrectly configured" is active.

3 Reset the BCF from Flexi EDGE BTS Manager.

The BCF site is successfully reset as seen from BTS Manager.

4 Verify the state of BCF and TRX objects from Flexi EDGE BTS Manager.

The BCF and TRX objects reach 'Supervisory' state.

Alarm 7601 "BCF operation degraded, Module power cable connections are incorrectly configured" is reported again.

5 Power off the EXxx TRX modules 1 and 2 from Flexi EDGE BTS Manager.

Reconnect the power cables in the correct order.

Power on the EXxx TRX modules 1 and 2 from Flexi EDGE BTS Manager.

Alarm 7601 "BCF operation degraded, Module power cable connections are incorrectly configured" is raised again.

6 Reset the BCF from Flexi EDGE BTS Manager.

The BCF and TRX objects reach 'Supervisory' state.

There is no active alarm 7601 "BCF operation degraded, Module power cable connections are incorrectly configured" present.



DN0749988Issue 2-0 en18/01/2008

4.1.2.3 BTS Site Commissioning with Mismatch between RF Cabling In the SCF and Physical Cabling

The objective of this test case is to verify that a BTS site reaches 'Supervisory' state. The site is initially commissioned with a mismatch between the RF cabling defined in the SCF file and the actual cabling done physically at the site.

Commmissioning will be 'Partially Failed' in this case since the TRX test will not 'Pass' due to the RF cabling mismatch.


All cables are connected as per site configuration mentioned in the test case comment, except the following:

• For one TRX object, the TX cable to ERxx DDU module is not connected.

• For one other TRX object, the RX cable from ERxx DDU module to RX port of EXxx TRX module is not connected.

Pre-setup:





• For every sector, 4 EDAP Abis timeslots are reserved for a TRX object on which PS data transfer will be tested. For example, if the BTS site has 2 sectors then 8 Abis timeslots should be reserved for EDAP on the Abis link.




Select the appropriate SCF template files and commission the BTS.

Wait for the commissioning process to complete.

The Commissioning Wizard displays:

Commissioning has partially failed due to the following: One or more commissioning tests failed.

2 Save the Commissioning report and check it in a text editor.

The latest Commissioning report executive summary shows:

Commissioning phase of SCF : FULL


DN0749988 Issue 2-0 en 18/01/2008


359 (381)


Commissioning result : PARTIALLY FAILED

Detailed Commissioning report has the TRX test results as given below for TRX objects having RF cabling mismatch.

TRX Test Results

================

<TRX_ID> Test Results FAIL

Measured Values

TX Power : <Invalid value will be reported>

Main Rx Result : RX Sens. : cannot be measured 255 (FFh)

Main Rx BER : < Invalid value will be reported>

Diversity Rx Result : RX Sens. : cannot be measured 255 (FFh)

Diversity Rx BER : < Invalid value will be reported>

3 Reconnect the RF cables in the correct order.

4 Reset the BTS objects having the TRXs with faulty cabling.

All TRXs under the BTS object are reset and they come to the supervisory state.

5 From the BSC, run TRX Test for the TRX object discussed in step 2.

TRX Test should pass.

4.1.2.4 BTS Site Commissioning with Incorrect TCH Timeslot Information

The objective of this test case is to verify that a BTS site can be successfully brought into ‘Supervisory’ state with no unexpected alarms. The BTS site is to be initially commissioned by providing Incorrect TCH timeslot information for a TRX object at the BSC, not matching with the Traffic timeslot allocation at the Flexi EDGE BTS Manager.

During such a BTS site commissioning, the commissioning will be "Partially Failed" since Abis loop tests will "Fail" on all the timeslots of the TRX object with incorrect TCH timeslot configuration. When the timeslot mismatch is corrected for the TRX object, calls can be successfully placed on the TRX object.




DN0749988Issue 2-0 en18/01/2008

The cabling has been done correctly as per site configuration mentioned in the test case comment.

Pre-setup:



• A TRX object is created at the BSC with TCH timeslot different from the one provided in the Transmission Template File.



• For every sector, 4 EDAP Abis Timeslots are reserved for a TRX object on which PS data transfer will be tested. For example, if the BTS site has 2 sectors then 8 Abis timeslots should be reserved for EDAP on the Abis link.




Select the appropriate hardware and transmission template files and commission the BTS.

Send the SCF to the BTS.

Wait for the Commissioning process to complete.

The Commissioning Wizard mentions

Commissioning has partially failed due to the following: One or more commissioning tests failed.

2 Save the commissioning report in the PC running the Flexi EDGE BTS Manager.

Exit the Commissioning Wizard.

Check for the BCF and TRX Object states in the Flexi EDGE BTS Manager.

BCF and TRX objects reach ‘Supervisory’ state as viewed from BTS Manager.

3 Check the commissioning report opening it in a text editor.



Commissioning result : PARTIALLY FAILED

Detailed Commissioning report has

Abis Test Results status 'FAIL' for all the


DN0749988 Issue 2-0 en 18/01/2008


361 (381)

Step Input Expected output timeslots of TRX object (which has incorrect TCH timeslot allocation).

Abis Test Results status 'PASS' for the remaining TRX objects in the BCF.

4 Lock the TRX object, delete it in the BSC.

Create the TRX object with the correct TCH timeslot as compared to the Traffic timeslot allocation at the BTS Manager.

Unlock the TRX object.

TRX object is reset and comes to the supervisory state.

5 Run Abis Loop test from BSC for TRX object created newly in step 4.

ABIS Loop Test result indicates "Pass".

6 Place CS calls on all the TRX objects. Calls are successfully placed.

4.1.2.5 BTS Site Commissioning with Incorrect TRXSIG Timeslot Information

The objective of this test case is to verify that a BTS site can be successfully brought into ‘Supervisory’ state with no unexpected alarms. BTS site is initially commissioned by providing Incorrect Abis timeslot for TRXSIG Link of a TRX object. The TRX Object with incorrect TRXSIG Abis timeslot will remain in "Wait for LAPD" state. When the timeslot mismatch is corrected at the BSC, the TRX object should reach "Supervisory" state.



Pre-setup:




• For one TRX object the TRX signalling link created at the BSC with a timeslot not matching the one mentioned in the SCF transmission template.


• For every sector, 4 EDAP Abis timeslots are reserved for a TRX object on which PS data transfer will be tested. For example, if the



DN0749988Issue 2-0 en18/01/2008

BTS site has 2 sectors, then 8 Abis timeslots should be reserved for EDAP on the Abis link.


1 From Flexi EDGE BTS Manager, go to the Commissioning Wizard.

Select ‘Commission from EasyWizard Template File’.

Select the appropriate hardware and transmission template files and commission the BTS.

The Commissioning Wizard reports commissioning as successful.

2 Verify the BCF and TRX objects from Flexi EDGE BTS Manager.

Verify the state of the TRX objects from the BSC.

The BCF reaches ‘Supervisory’ state as viewed from BTS Manager.

The TRX object with the mismatch in the TRX signalling link timeslot is in ‘Wait for LAPD’ state.

The operational state of the TRX object at the BSC will be shown as BL-SYS.

3 Check the commissioning report. The commissioning report executive summary states:


4 Delete the TRX signalling link at the BSC and create a TRX signalling link matching the timeslots mentioned in the transmission template file.

Unlock the TRX object.

The TRX object that was stuck in 'Wait for LAPD' now undergoes a reset and reaches the 'Supervisory' state.

5 Place CS calls on all the TRX objects. The calls are successfully placed.

4.1.2.6 BTS Site Commissioning without Abis Link Connectivity

The objective of this test case is to verify that a BTS site can be successfully brought into ‘Supervisory’ state with no unexpected alarms, after commissioning has been initially done without Abis link connectivity. Once Abis link connectivity is established, the BTS site should progress from ‘Wait for LAPD’ state towards ‘Supervisory’ state after performing commissioning tests like Abis loop tests and TRX tests.




DN0749988 Issue 2-0 en 18/01/2008


363 (381)

Pre-setup:

• The BCF is in uncommissioned state without any unexpected alarms.

• Flexi EDGE BTS Manager is connected at the LMP port of ESMA System Module.


• The Abis Link is disconnected.


• For every sector, 4 EDAP Abis timeslots are reserved for a TRX object on which PS data transfer will be tested. For example, if the BTS site has 2 sectors, then 8 Abis timeslots should be reserved for EDAP on the Abis link.


1 Open the Commissioning Wizard in Flexi EDGE BTS Manager and commission the BTS with the SCF template files matching the configuration.

SCF is sent to the BTS.

2 Check the commissioning progress in the Commissioning Wizard.

Commissioning State becomes green.

BCF Waiting for LAPD becomes highlighted

BCF SW Downloading is skipped

BCF Configuring is skipped

Test Started is skipped

Abis loop Test is skipped

TRX Test is skipped

Tests Completed is skipped

Commissioning report is highlighted.

Result is displayed as "Commissioning has failed due to Wrong OMUSIG provided. See commisioning report for details".

3 Save the commissioning report on the PC running Flexi EDGE BTS Manager.

Open it using a text editor.

Check the content of the commissioning report.

The latest commissioning report executive summary shows:


Commissioning result : FAILED

Wrong Omusig.

Detailed Commissioning report has

Blank Sector Configuration



DN0749988Issue 2-0 en18/01/2008


Blank Usability Status in TRX



Blank Abis Test Results

Blank TRX Test Results

Blank BTS Alarms Test.

Blank External TREs in Q1 port

Blank Cabling Details

Antenna Info as provided in SCF




Cross Connection as provided in SCF

4 Check for the status of the BCF in Flexi EDGE BTS Manager base station view by selecting the BCF object.

Check the Alarms window.

BCF operational state is 'Waiting for LAPD Establishment.'

Alarm 8050 “Loss of Incoming 2M signal” is reported at Flexi EDGE BTS Manager.

5 Connect the Abis link after 15 minutes and check for OMUSIG link establishment in BCF properties.


O&M link is established.

BTS_CONF_DATA and BTS_COMMISS_TEST_REQ is sent to the BTS by the BSC.

The BCF operational state is supervisory.

6 Check the operational status of BTS, TRX objects at the BSC by MML command

ZEEI:BCF=<bcf_id>;

The BCF, BTS and TRX objects have operational state “WO”.

7 Fetch the commissioning report from BTS by selecting Commissioning Report Fetch from BTS in Flexi EDGE BTS Manager and save it on PC.

Open the report in text editor.



Commissioning result : SUCCESS

The Detailed Commissioning report has Sector Configuration as per the configuration at the BSC.

Usability Status of all TRXs



Abis Test Results status 'PASS' for all the


DN0749988 Issue 2-0 en 18/01/2008


365 (381)

Step Input Expected output configured TRXs in the BCF.

TRX Test Results 'PASS' for all the configured TRXs in the BCF.

No unexpected alarm in BTS Alarms Test.

External TREs in Q1 port as configured in the BSC.

Cabling Details as specified in the SCF.

Antenna Info as provided in SCF




Cross Connection as provided in SCF.

4.1.2.7 Successful Append Commissioning for an Operational BTS Site

The objective of this test case is to verify that some of the BTS Site commissioning parameters like Passive unit details, EDAP information can be changed using Append Commissioning for a BTS Site in ‘Supervisory’ state. The new Passive unit information should be readable after fetching the SCF file from Flexi EDGE BTS Manager. The new EDAP information can be checked from the Transmission view of the Flexi EDGE BTS Manager.



Pre-setup:

• The BTS site is in 'Supervisory' state without any unexpected alarms


• EDAP is configured on any 4 Abis timeslots for the BCCH TRX object in Sector 2.

• At least one CS call is ongoing in all the TRX objects of the BTS site. Repetitive PS transfer is ongoing in the BCCH TRX object of Sector 2.

• Adjacent cell parameters are defined between Sector 1 and 2, for handover purpose.



DN0749988Issue 2-0 en18/01/2008

• TRX objects 1, 3, 7 are BCCH TRX objects.


1 Fetch the SCF from Flexi EDGE BTS Manager.

SCF is successfully displayed to the user.

The SCF is saved on a PC.

2 At the BSC, lock TRX objects 5 and 6 with Forced Handover.

CS calls on TRX objects 5, 6 are successfully handed over to Sector 1, as commanded by the BSC.

3 Remove the EWxx WBC module being connected to TRX objects 5 and 6.

Replace it with a new EWxx WBC hardware of the same band.

Edit the saved SCF with the serial number and product code of the new WBC being connected to TRX object. 5 and 6.

4 Use 'ZESM' MML command to expand the EDAP capacity of the site from 4 Abis timeslots to 6 Abis timeslots.

Edit the saved SCF and add EDAP information on 2 additional Abis timeslots for TRX object 3.

5 Open the Commissioning Wizard and browse the SCF and click the 'Next' button.

Click 'Send SCF' to download the SCF from the PC to the BTS site.

View the SCF details as shown in BTS Manager and verify that Commissioning mode is shown as 'APPEND'.

After sending the SCF, the BTS site is commissioned with the new details of WBC and expanded EDAP. This can be verified by fetching the SCF using BTS Manager.

The new SCF shows the modified serial number and product code for the WBC being connected to TRX object 5 and 6.

Modified information of EDAP for TRX object 3 can be verified by seeing the Transmission view of the BTS Manager.

6 Check the commissioning report. The commissioning report executive summary mentions

Commissioning phase of SCF: APPEND


7 Place new CS voice calls on the TRX objects 5, 6.

Observe the status of other ongoing calls.

Calls are successfully placed on TRX objects 5, 6.

Ongoing CS calls and PS transfers in other TRX objects are still successfully active as verified by manually listening to speech and


DN0749988 Issue 2-0 en 18/01/2008


367 (381)

Step Input Expected output by checking at the BSC using MML command "ZERO".

4.2 Flexi EDGE BTS Software Deployment

4.2.1 Software Package Creation and Storage

Overview Flexi EDGE BTS software package can be upgraded in the field either from the BSC, NetAct or Flexi EDGE BTS Manager. For distribution of the BTS software, NetAct and the BSC must be able to take the package from media drive and create internally the BCF software build, which is then later attached and downloaded to the Flexi EDGE BTS sites.

Scope of testing The scope of the test cases is to test that in both compatible release of NetAct and BSC to Flexi EDGE BTS EP1.1 can read the software package versions and can create a BCF software build.

Software packages The following software package names are used in all of the test cases, attached to this test plan.

• Software Package "A": all BTS Units. (Example: EP1.1)

• Software Package "B": all Application Files CD release. (Example: EP1.1 CD1.0)

• Software Package "C": all Application Files next EP release. (Example: EP2 )

• Software Package "D": changes over EP1.1 CD 2.0 in some Application Files (AF) but no change in Transmission Software component. (Example: EP1.1 CD2.1)

• Software Package "E": changes over EP1.1 CD 2.0 in some Application Files including Transmission software component (Example: EP1.1 CD3.0).

• Software Package "F": changes over EP1.1 CD 1.0 in software for Application Files including update to ERxA DDU module software. (Example: EP1.1 CD1.1)



DN0749988Issue 2-0 en18/01/2008

Test cases

Pos Name Comment

1 EP Software package creation at the BSC --

2 EP Software placement at NetAct server A5/0 package

3 EP Software placement at NetAct server A5/1 package

4.2.1.1 EP Software Package Creation at the BSC

This test case verifies that different BCF software packages can be transferred to the BSC disk, in different packs. Then the BCF software build can be created for further use.


• BSC O&M link is up

• Both of the BSC disks are in the normal working state (WO-BU) (MML command: ZISI )

• Subdirectory pack_<XX> is empty, checked by MML command: ZIWX


1 Copy/place the new BTS software build files of software package "A" to the first unused build subdirectory of disk (BCF_PACK>pack_<XX>)

The software package files are transferred to pack_<XX> where XX is a given subdirectory number.

2 Software package "A" is created using MML command: ZEWC with the parameters:

- Build ID as EP__<c> where b and c are given name per the release and the ciphering mode used respectively

- MF file name as BTS_<W><X><Y><Z>. <baseline number>

- SDIR as pack_<x>

[Note: Refer to the test plan for naming convention of these fields]

Command executed succesfully, without any error message.

3 Using MML command ZEWL, verify that software package ID, software build type, Rel Version, MF name and subdir are correctly shown.

All the fields are shown correctly

Software build ID: EP__<c>

Software build type: E

MF name:BTS_<W><X><Y><Z>. <baseline number>

Subdirectory :pack_<x>


DN0749988 Issue 2-0 en 18/01/2008


369 (381)


Release Version:

<V>.<W><X>-<Y><Z>

[Note: Refer to the test plan for naming convention of these fields]

4 Repeat the test steps 1 and 3 for Software packages B, C, D, E, F.

Observation is same as in test step 1 to 3.

4.2.1.2 EP Software Placement at NetAct Server

The test case verifies that different BTS software packages can be loaded to the NetAct Server.


• NetAct Server


1 FTP all the files of the new software package ‘A’ to the directory in the Tier3 server of NetAct.

/var/opt/nokiaoss/shared/admin/swmgmt/swtemp

The new files are available at the mentioned location in the NetAct server.

2 Using NetAct menu import new software package.

(BSC Utils Software Configuration Mgmt NE Software Configuration Mgmt SW

Archive Tab Import New SW Package)

The 'Import Software' window is displayed.

3 All the files (Software Package ‘A’) that are to be imported are selected from the location /var/opt/nokiaoss/shared/admin/swmgmt/swtemp.

Provide the package name, as EP__<c> where b and c are given name per the release and the ciphering mode used respectively.

The BTS SW package imported successfully at the NetAct Server with the package ID: EP__<c>

4 Repeat the test steps 1 and 2 for software packages ‘B’,’C’,’D’.

Same observations as in test steps 1 to 3.



DN0749988Issue 2-0 en18/01/2008

4.2.2 Software Release Upgrade/Fallback

Overview The Flexi EDGE BTS software package can be upgraded in the field either from the BSC, NetAct or Flexi EDGE BTS Manager. During BTS software package download to the BTS, the normal BTS operation is not affected. Only at the time of activation of the upgraded software package, the BTS site requires a reset. The previous running software package can be taken into use in the following BSC or NetAct control without a need to download the package again.

Scope of testing The scope of the test cases is to verify the following operations:

• Update to EP1.1 when a previous BTS SW release is running

• Fallback to original EP BTS SW release from EP1.1

• Operation to be verified from Flexi EDGE BTS Manager, BSC and NetAct

• Operation when upgrading and activating BTS SW for BTS sites in a transmission chain configuration.

Configuration Any BTS configuration with 16k O&M LAPD link

To verify that the field update of future EP BTS SW packages can be loaded and activated the special version of EP1.1 SW will be used to mimic these packages.

Test cases

Pos Name Comment

1 EP Software Upgrade from Flexi EDGE BTS Manager

Running (EP1.1), Download (EP2), Flexi EDGE BTS Manager for EP1 CD1.0.

2 EP Software Upgrade from Flexi EDGE BTS Manager

Running (EP1.1), Download (EP2), Flexi EDGE BTS Manager for EP1.1.

3 EP Software Upgrade/Fallback at Startup from BSC

Running (EP1 CD1.0), download (EP1.1), 4+4, 2-Way combining, ERxA DDU module in first sector of Vendor A and ERxA DDU module in sector 2 of Vendor B

4 EP Software (No change in Transmission Running (EP1.1),


DN0749988 Issue 2-0 en 18/01/2008


371 (381)

Pos Name Comment Software) Upgrade/Fallback from BSC Download (EP1.1

CD1.0), Cross connects between 2 BCFs

5 EP Software (change in few Application Files including Transmission software) Upgrade/Fallback from BSC

Running (EP1.1), Download (EP2), Cross connects between 2 BCFs

6 EP Software Upgrade/Fallback using NetAct server

Running (EP1 CD1.0), Download (EP1.1),3 BCFs, Cross connects between BCF1 & BCF2

4.2.2.1 EP Software Upgrade from Flexi EDGE BTS Manager

A BTS software package can be downloaded in the background from a locally connected Flexi EDGE BTS Manager. After the activation of the BTS SW at the BSC, the software package is taken into use by the BTS.



• BTS site is in operational (Supervisory) state with no active alarm pending.

• Software Package "B" is running and active with BCF at the BSC.

• Latest software Package "C" is available with the BSC. The software upgrade of BTS site must be done with this package only.

• At the BTS site, Running and Active Partition consists of Software Package "B".


1 Place CS calls and dynamic PS traffic (make new connections randomly) in each sector for BTS site.

Calls are made successfully. Note the throughput as desired in PS traffic.

2 Verify the versions of the SW packages in the flash from Flexi EDGE BTS Manager (using "SW version Inquiry" functionality through BTS SW Versions menu - Flexi EDGE BTS Manager from Main Menu.)

Software packages "A" and "B" are present in the BTS as

Running Package :------------> "B"

Active Package :--------------> "B"

Standby Package: ---------- "A"

3 Download BTS software package "C" , using "Update SW" functionality through BTS SW Versions menu - Flexi EDGE BTS Manager from Main Menu. Select Master file from the

"Package down load in progress" Bar at Flexi EDGE BTS Manager shows download of different files to BTS.



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output browse through option.

Observe the LED status of ESMA module.

Continue to monitor the SW download over BTS Manager.

The ESMA module LED is blinking green.

After successful download of all files to BTS flash writing starts with progress Bar "Package flashing progress".


(using "SW version Inquiry" functionality through BTS SW Versions menu - Flexi EDGE BTS Manager from Main Menu.)

Observe the LED status of ESMA module.

Software packages "B" and "C" are present in BTS as

Running Package :------------> "B"

Active Package :--------------> "C"


The ESMA module LED is stable green.

5 Observe CS calls on the BTS. CS calls are still going on with no disruption.

6 Observe the dynamic PS traffic, placed in all the sectors of BTS site. Observe the throughput.

No unexpected drop is observed in the throughput. New connections are taking place successfully.

7 Attach the latest software package "C" with BCF at the BSC using command

ZEWA

Verify the software package "C" is attached with the BCF using MML command

ZEWO


The BSC shows that software package "C" is attached with the BCF.


Verify on the BSC that the software is not being downloaded by using MML command ZEWI;

Observe the LED status of ESMA System Module.

No application files download takes place.

Activity – None

ESMA System Module LED is stable green.

9 Leave the site after software download for 2 hrs. Then activate the software package "C" attached at the BSC, using MML command ZEWV

Observe the messages at Abis Analyser.

Observe the ongoing CS and PS calls.

Before the command is given during the 2 hrs all BTS operations are working normally. When the command is executed, observed on the BSC.

Downloaded SW is taken into use after reset of the ESMA module. BTS comes up with the SW package "C".No other software downloading takes place.

Calls are released during the BCF reset of ESMA module.


Software packages "B" and "C" are present in BTS as


DN0749988 Issue 2-0 en 18/01/2008


373 (381)





11 Place CS and PS calls in each sector. Calls are successfully made.

4.2.2.2 EP Software Upgrade/Fallback at Startup from BSC

A BTS software package can be activated to the BTS site at the BSC and, if required, directly downloaded to the BTS site at BCF startup. After completion of download, the software package is taken into use by the BTS.The fallback software package in the ESMA System Module can be activated at the BSC and used without additional SW package downloads.


1. Flexi EDGE BTS Manager is connected locally.

2. BCF consists of software package "A".

3. BTS site is switched off.

4. EP software package "B" is available at the BSC.


1 Attach and activate the latest software package "B" with the BCF at the BSC.

Command Executed, observed on BSC, with SW download denied. Reason of denial is "O&M link state".

2 Switch on power to the BTS site.

Observe the software download over Abis Analyser.

The site powers on and establishes O&M LAPD link.

Software download of software package "B" starts.

3 Verify on the BSC that the software is downloading by using MML command ZEWI;


Continue to monitor the SW download over Abis Analyser.

Activity – ATTACHMENT

Phase - DOWNLOADING

ESMA System Module LED is blinking green.

After completion of the SW download, the BCF takes a reset, and then comes to supervisory state.

4 Verify the versions of the software packages from BTS Manager.

(using "SW version Inquiry" functionality through BTS SW Versions menu-item from Main Menu.)

Software packages "A" and "B" are shown as

Running Package :------------ "B"



DN0749988Issue 2-0 en18/01/2008



Active Package :-------------- "B"

Standby Package :------------ "A"


5 Place calls and data transfers sessions in each sector.

Calls and data transfer are made successfully.

6 Activate the software package "A" for the BCF using MML command ZEWV


Observe the ongoing CS calls and PS data transfer sessions in step 7.

Software Package "A" is taken into use by the BCF after the BCF reset. The BTS comes up with the previous SW package "A".

No AF files downloading take place.

All CS calls and PS data transfer sessions are dropped as a result of BCF reset.

7 Verify the versions of the SW packages for the BCF from BTS Manager.

Software packages "A" and "B" are shown as


Active Package :--------------> "A"


8 Make CS calls and dynamic PS data transfer sessions in each sector for BCF.


Data transfer throughput is as desired.

4.2.2.3 EP Software (No Change in Transmission Software) Upgrade/Fallback from the BSC

When two BTS sites are connected through cross-connection, the BTS software package (with changes in BTS Application Files but no change in AFs of Transmission Software component) can be downloaded to first BTS site, in the background. After activation of the SW at the BSC, the software package is taken into use by the first BTS site in the Abis chain without impact to the second BTS. The fallback software package in the ESMA System Module can be activated at the BSC and used without additional SW package downloads.


2 BTS sites (BCF1 and BCF2) connected through cross-connections. The cross-connections are defined at BCF1.

Pre-setup:

• BTS Manager is connected locally.

• Both BTS sites are in operational (Supervisory) state with no active alarm pending.


DN0749988 Issue 2-0 en 18/01/2008


375 (381)

• Software package ‘B’ is running and active with BCF1 at the BSC.

• The latest software package ‘D’ is available with the BSC. The software upgradation of BCF1 has to be done with this build only.

• At BCF1, the Running and Active Partition consists of software package ‘B’.


1 Make CS calls and dynamic PS data transfer sessions (make new connections randomly) in each sector for BCF1 and BCF2.


Data transfer throughput is as desired. Note the throughput.

2 Attach the latest software package "D" with the BCF on BTS 1 at the BSC using command ZEWA.

Verify that software package "D" is attached with the BCF using MML command ZEWO.


The BSC shows that software package "D" is attached with the BCF.


Software download is going on.

4 Verify on the BSC that the software is downloading by using MML Command ZEWI;




Phase - DOWNLOADING

ESMA System Module LED is blinking green.

On completion of the SW download, BTS_SW_SAVE_REQ is send from the BSC to the BTS and BTS_ACK will be sent from the BTS to the BSC.

5 Observe the CS calls on BCF1 and BCF2. CS calls are still going on with no disruption.

6 Observe the PS data transfer, placed in all the sectors of BCF1 and BCF2. Observe the throughput.

No unexpected drop is observed in the throughput. Dynamic PS data transfer sessions are successful.

7 Verify the versions of the SW packages for BCF1 from BTS Manager. (using "SW version Inquiry" functionality through BTS SW Versions from the Main Menu.)


Software packages "B" and "D" are present in BCF1 as


Active Package :-------------- "D"

Standby Package :------------ "B"

The ESMA System Module LED is stable green.

8 Activate the software package "D" at the BSC for BCF1, using MML command ZEWV.


Command executed at BCF1, observed on the BSC.

Downloaded SW is taken into use after BCF reset. The BTS comes up with the new SW package "D".



DN0749988Issue 2-0 en18/01/2008


No application files downloading take place.

9 Observe the CS calls and dynamic PS traffic data transfer sessions for BCF2 in step 1.Observe the throughput.

Observe calls placed on BCF 1 in step 1.

For BCF2, the CS calls and PS data transfer sessions are going with no disruption. No unexpected drop is observed in the throughput. New connections are taking place successfully.

All calls are dropped on BCF 1.

10 Verify the versions of the SW packages for BCF1 from BTS Manager.

Software packages "B" and "D" are present in the BTS as

Running Package :------------ "D"

Active Package :-------------- "D"


11 Place CS calls and dynamic PS traffic in each sector of BCF 1.

Calls are made successfully and continued on BCF 1.

12 Activate the software package "B" at the BSC for BCF1, using MML command ZEWV.


Command executed at BCF1, observed on the BSC.

After BCF reset, BTS comes up with the SW package "B". No application files downloading takes place.

13 Verify the versions of the SW packages for BCF1 from BTS Manager.

Software package "B" and "D" are present in the BTS as



Standby Package :------------ "D"

14 Repeat steps 9 and 11 to verify CS calls and PS transfers.

The same as in steps 9 and 11.

4.2.2.4 EP Software (Change in a few Application Files including Transmission Software) Upgrade/Fallback from the BSC

When two BTS sites are connected through cross-connect (Abis chain), the BTS software package (with some BTS and transmission AF updated) can be downloaded to the first BTS site, in the background. After activation of the BTS SW at the BSC, the software package is taken into use by the BTS site with a short break to cross connect traffic for the later BTS sites.


DN0749988 Issue 2-0 en 18/01/2008


377 (381)

The fallback software package in the ESMA System Module can be activated at the BSC and used without additional SW package downloads.


2 BTS sites (BCF1 and BCF2) connected through cross-connections. The cross-connections are defined with BCF1.

Pre-setup:

• BTS Manager is connected locally.

• Both BTS sites are in operational (Supervisory) state with no active alarm pending.

• Software package ‘B’ is running and active with BCF1 at the BSC.

• The latest software package ‘E’ is available with the BSC. The software upgradation of BCF site has to be done with this build only.

• At BCF1, the running and active partition consists of software package ‘B’.


1 Make CS calls and dynamic PS data transfer sessions (make new connections randomly) in each sector for BCF1 and BCF2.


Data transfer throughput is as desired. Note the throughput.

2 Attach the latest software package "E" with the BCF on BCF 1 at the BSC using command ZEWA

Verify that the software package "E" is attached with the BCF as NEW using MML command ZEWO


The BSC shows that software package "E" is attached with the BCF.



4 Verify on the BSC that the software is downloading by using MML command ZEWI;

Observe the LED status of the ESMA System Module.



Phase - DOWNLOADING

The ESMA System Module LED is blinking green.

On completion of the SW download, BTS_SW_SAVE_REQ is send from the BSC to the BTS and BTS_ACK will be send from the BTS to the BSC.

5 Observe the CS calls on BCF1 and BCF2. CS calls are still going on with no disruption.



DN0749988Issue 2-0 en18/01/2008


6 Observe the PS data transfer, placed in all the sectors of BCF1 and BCF2. Observe the throughput.

No unexpected drop is observed in the throughput. Dynamic PS data transfer sessions are successful.

7 Verify the versions of the SW packages in BCF1 from BTS Manager (using "SW version Inquiry" functionality through BTS SW Versions from the Main Menu.)


Software packages "B" and "E" are present in the BTS as


Active Package :-------------- "E"



8 Activate the software package "E" attached at the BSC on BCF 1, using MML command ZEWV

Observe the CS calls and PS data transfer sessions in BCF1 and BCF 2.

Command executed, observed on the BSC. Software package " E" is taken into use after the BCF reset. No AF file download takes place.

All CS calls and PS data transfer sessions are released as a result of the BCF1 reset.

9 Observe the status of O&M and TRX LAPD for BCF2 at Flexi EDGE BTS Manager and at Abis Analyser.

BCF2 LAPDs recover within 120 seconds after SW package was activated for BCF1.

10 Make CS calls and dynamic PS data transfer sessions in each sector for BCF1 and BCF2.

CS calls are made successfully.


11 Verify the versions of the SW packages in BCF1 from BTS Manager.

Software packages "B" and "E" are present in BTS as

Running Package :------------ "E"

Active Package :-------------- "E"


12 Activate the software package "B" attached at the BSC on BCF1, using MML command ZEWV

Observe the CS calls and PS data transfer sessions in BCF1 and BCF 2.

Command executed at BCF1 is observed on the BSC.

All CS calls and PS data transfer sessions are dropped as a result of BCF1 reset.

13 Repeat the test step 9. Same as in test step 9.

14 Verify the versions of the SW packages in BCF1 from BTS Manager.

Software packages "B" and "E" are present in the BTS as



Standby Package :------------ "E"


DN0749988 Issue 2-0 en 18/01/2008


379 (381)

4.2.2.5 EP Software Upgrade/Fallback using NetAct Server

BTS Software Package can be downloaded to the BSC and package created, then background downloaded to BTS site from NetAct Server. After activation of the SW, using NetAct Server, the software package is taken into use by the BTS.


Two BTS sites (BCF1 and BCF2) connected through cross-connections. The cross-connection configuration is defined with BCF1. An additional independent BTS site (BCF3) is used.

Pre-setup:


• The NetAct server is connected to the BSC under which BCFs 1, 2, and 3 are defined.

• All BCFs are in operational (Supervisory) state with no active alarm pending.

• Software package ‘B’ is running and active at all the BCFs. Software package ‘A’ is also attached with all the BCFs.

• Software package ‘C’ is not available at the BSC, but is in the NetAct server.


1 Make CS calls and dynamic PS data transfer sessions (Make new connections randomly) in each sector for BCF1, BCF2 and BCF3.



2 Verify that the software package "C" is not available with the BSC using MML command ZEWL.

Software package "C" is not available at the BSC.

3 Go to NetAct Software Manager application Software Archive BS Software Software package "C" is selected.

Go to Managed Objects BSC ID BCF IDs (BCF1 and BCF 3) Download Tasks Scheduling and select "Immediately" and check/click the Active Software option .

Observe the task status.

The task status changes from Waiting to Ongoing.

4 Observe the LED status of ESMA System Module for BCF1 and BCF3.

LED colour is blinking green.

5 After five minutes, go to NetAct Software Manager application Software Archieve BS Software Software Package "C" is



DN0749988Issue 2-0 en18/01/2008

Step Input Expected output selected.

Go to Managed Objects BSC ID BCF IDs (BCF 2) Download Tasks Scheduling and select "Immediately" and check the Active Software option .

Observe the Task Status.

Task status is moved to Ongoing from Waiting .

6 Observe the LED status of ESMA System Module for BCF2.

LED colour is blinking green.

7 Observe the software download for BCF1, BCF2, and BCF3 over Abis Analyser.


8 Continue to observe the task status at NetAct.

Observe the status of calls.

Task status changes to completed.

Activation of the software package leads to BCF reset.

No AF files downloading takes place.

Calls are dropped during BCF reset.

9 Observe the software downloading for BCF2 over Abis Analyser.

Software download process is aborted.

Error message is shown at NetAct server.

10 Observe status of BCF 1 and BCF 3. BCF 1 and BCF 3 comes up with the new SW package "C".

11 At NetAct, select the software package from NW and then activate it for BCF 2.

(NE Software Management Managed Objects Select BCF 2 View Software packages Tasks).

Observe the software downloading for BCF 2 over Abis Analyser.

Software downloading is restarted.

12 Continue to observe the task status at NetAct for BCF2.

Task status changes to completed.

Activation of the software package will lead to BCF reset.

No AF files downloading take place.

13 Observe status of BCF 2. BCF 2 comes up with the new SW package "C".

14 Verify that the software package "C" is now available with the BSC using MML command ZEWL.

Software package "C" is available with information: BUILD-ID, TYPE, REL VER, MF NAME, SUBDIR.

15 Verify that the software package "C" is attached with all three BCFs using MML command ZEWO.

BSC shows that the new software package "C" is attached and activated with all the BCFs.


DN0749988 Issue 2-0 en 18/01/2008


381 (381)


16 Verify that no error message is displayed at NetAct workstation for any of the three sites.

No error message is displayed at NetAct workstation.

17 Verify the versions of the SW packages in BCF1, BCF2 and BCF3 from BTS Manager (using "SW version Inquiry" functionality through BTS SW Versions from the Main Menu.)

Software packages "B" and "C" are shown as




18 Make CS calls and dynamic PS data transfer sessions in each sector for BCF1, BCF2, and BCF3.



19 At NetAct, select the software package "B" from BU and then activate it for all three BCFs.

(NE Software Management Managed Objects Select concerned BCFs View Software packages Tasks).

Observe the calls.

Activation of the software package will lead to BCF reset. All the BCFs comes up with the new SW package "B".

BCF2 comes to supervisory state without any delay.

No other software downloading takes place (No new AF files are downloaded).

Calls are dropped during BCF reset.

20 Verify the versions of the SW packages for all BCF sites from BTS Manager.

Software packages "B" and "C" are present in all the BCF sites as



Standby Package :------------ "C"

21 Make CS calls and dynamic PS data transfer sessions in each sector for BCF1 and BCF2.

Documents

Test Specification for Features Dn0749988 2-0 En