cx(m)7 common telecom regression test specification

© Nokia Siemens Networks Company Confidential 1 (406)

UltraSite and MetroSite EDGE BTS SW CX(M)7 – Common Telecom Regression Test Specification

Release Delivery: CX(M)7 Product Family: GSM/EDGE Base Stations Product: UltraSite EDGE Base Station and MetroSite EDGE Base Station Release: CX(M)7

DN0694168 Issue 2-0


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

3.1 Hardware Requirements .......................................................................................................................................... 9 3.2 Software Requirement ........................................................................................................................................... 11 3.3 Specialist Test Equipment Requirements .............................................................................................................. 11

4. SPEECH CALL SETUP .............................................................................................................................. 13 4.1 Speech and Emergency call Setup via SDCCH..................................................................................................... 13 4.2 UL FER reporting ................................................................................................................................................... 16 4.3 Dynamic SDCCH Reservation ............................................................................................................................... 17 4.4 Rx Diversity testing during speech call................................................................................................................... 19 4.5 Speech Call and Emergency Call Setup via FACCH ............................................................................................. 20 4.6 Support for Different Ciphering Algorithms............................................................................................................. 22

5. Single Timeslot Data Call Setup ................................................................................................................. 24 5.1 Non-Transparent Data via SDCCH ........................................................................................................................ 24 5.2 Non-Transparent Data via FACCH......................................................................................................................... 26 5.3 Transparent Data via SDCCH................................................................................................................................ 26 5.4 Transparent Data via FACCH ................................................................................................................................ 27 5.5 Group 3 Fax via SDCCH........................................................................................................................................ 28

6. Multislot Data Call Setup............................................................................................................................. 29 6.1 Non-Transparent Data via SDCCH ........................................................................................................................ 29

7. Short Message Service............................................................................................................................... 30 7.1 Originating & Terminating SMS on SDCCH ........................................................................................................... 30 7.2 Terminating SMS in Dedicated Mode..................................................................................................................... 31

8. GPRS Operation in BTS ............................................................................................................................. 32 8.1 GPRS synchronisation in BTS ............................................................................................................................... 33 8.2 Paging Modes ........................................................................................................................................................ 40 8.3 Data transfer .......................................................................................................................................................... 41 8.4 GPRS Data Transfer with changing Time Advance Value. .................................................................................... 44 8.5 Data Transfer with Radio Link Failure .................................................................................................................... 45 8.6 SMS via packet data .............................................................................................................................................. 46 8.7 Cell Reselection and Timing Advance.................................................................................................................... 48 8.8 RF Performance & Power Control.......................................................................................................................... 49

9. Adaptive Multi Rate Codec ......................................................................................................................... 51 9.1 AMR Call Setup via SDCCH and Link Adaptation (LA) .......................................................................................... 52 9.2 AMR call Setup with mobiles moving ..................................................................................................................... 54 9.3 Packing/Unpacking of AMR calls with Fast LA/Slow LA......................................................................................... 55 9.4 Slow link adaptation with uplink DTX ON. .............................................................................................................. 57 9.5 Intercell Handover from AMR cell to Non-AMR cell................................................................................................ 58

10. BTS Idle Mode Functions............................................................................................................................ 59 10.1 SMS Cell Broadcast ............................................................................................................................................... 59 10.2 RACH and PRACH Success Rate under C/I Conditions........................................................................................ 60

11. SACCH messages ...................................................................................................................................... 62 11.1 SACCH messages during Speech call................................................................................................................... 62

12. Dedicated Mode Functions ......................................................................................................................... 63 12.1 SDCCH Handovers ................................................................................................................................................ 63 12.2 Intra Cell Handover ................................................................................................................................................ 64 12.3 Inter cell Asynchronous Handover ......................................................................................................................... 66 12.4 Inter Cell Synchronous Handover .......................................................................................................................... 68 12.5 Intra-Cell Handovers within a Multi-BCF Segment ................................................................................................. 69 12.6 Inter-Cell Handovers between Multi-BCF Segments.............................................................................................. 71 12.7 Automatic Link Adaptation ..................................................................................................................................... 83 12.8 Multislot Upgrade / Downgrade.............................................................................................................................. 84 12.9 DTX Applied to Speech & Data calls...................................................................................................................... 84 12.10 Measurement Pre-processing ................................................................................................................................ 87 12.11 Mobile Speed Handling .......................................................................................................................................... 88 12.12 Interference with HR channel when high traffic ...................................................................................................... 89 12.13 BTS Power Control ................................................................................................................................................ 90

13. Recovery from Fault Conditions.................................................................................................................. 91

DN0694168 Issue 2-0


13.1 TRAU Frame Breaks.............................................................................................................................................. 91 14. Separate RLT Parameter for AMR and EFR .............................................................................................. 92

14.1 Radio link timeout with speech call ........................................................................................................................ 94 14.2 Radio link timeout on TCH for EFR/FR with change of ARLT ................................................................................ 95 14.3 Radio link timeout on TCH for AMR with change of RLT ....................................................................................... 97 14.4 Radio link timeout on TCH for AMR with different values of ARLT......................................................................... 98 14.5 Radio link timeout on TCH for AMR with change of ARLT ..................................................................................... 99 14.6 Radio link timeout on TCH for AMR and GP recovery ......................................................................................... 100 14.7 Radio link timeout with Handover......................................................................................................................... 101 14.8 Object control and Radio link timeout................................................................................................................... 103 14.9 AMR packing/unpacking and Radio link timeout .................................................................................................. 105 14.10 Multiple speech calls and Radio link timeout........................................................................................................ 106 14.11 Multiple speech calls with change in RLT/ARLT .................................................................................................. 107 14.12 Multiple Breaks at Air interface............................................................................................................................. 108 14.13 T200 Expiry .......................................................................................................................................................... 109

15. Dynamic A-bis Allocation .......................................................................................................................... 110 15.1 Downlink Resource Allocation Loading ................................................................................................................ 110 15.2 Uplink Resource Allocation Loading..................................................................................................................... 111 15.3 Maximum Dynamic Pool Size............................................................................................................................... 112 15.4 Dynamic Abis loop test......................................................................................................................................... 113

16. Enhanced Data Rates for Global Evolution, EDGE.................................................................................. 114 16.1 EGPRS MCS 1-9 & Incremental Redundancy ..................................................................................................... 115 16.2 Link Adaptation in Unack Mode (Changing Air Interface Conditions)................................................................... 119 16.3 Link Adaptation in Ack Mode (Changing Air Interface Conditions) ....................................................................... 120 16.4 GPRS Data transfer when EGPRS is enabled..................................................................................................... 122 16.5 GPRS & EGPRS TBFs on One Timeslot ............................................................................................................. 124 16.6 GPRS Link Adaptation ......................................................................................................................................... 125 16.7 EGPRS/GPRS Territory Upgrade/Downgrade ..................................................................................................... 127 16.8 Multiple TBFs on One Timeslot at Different Distances......................................................................................... 129 16.9 Cell Reselection & Timing Advance with EGPRS ................................................................................................ 130 16.10 EGPRS Reliability at Various MS Speeds............................................................................................................ 131 16.11 EGPRS Reliability at Various Distances .............................................................................................................. 132 16.12 RF Performance & Power Control........................................................................................................................ 133 16.13 Break (Air Interface and A-bis) in EGPRS............................................................................................................ 134 16.14 GPRS transfer when EGENA is OFF................................................................................................................... 136 16.15 EDAP mismatch between BSC and the BTS Manager ........................................................................................ 136

17. EGPRS Channel Requirement on CCCH................................................................................................. 137 17.1 EPCR Capability Reporting.................................................................................................................................. 137 17.2 PRACH Types on CCCH and PCCCH................................................................................................................. 138

18. Enhanced Measurement Reports (EMR).................................................................................................. 140 18.1 (E)MR sending in response to Measurement Information Message..................................................................... 142 18.2 Invalid_BSIC_Reporting Response...................................................................................................................... 146 18.3 SCALE_ORD Response ...................................................................................................................................... 148 18.4 Reporting Priority of Neighbouring Cells .............................................................................................................. 149 18.5 Uplink RX Quality Measurement .......................................................................................................................... 150 18.6 Downlink Frame Erasure Rate (FER) Measurement............................................................................................ 153 18.7 Averaging of Enhanced Measurement Report (EMR) .......................................................................................... 155 18.8 Reporting of correct TA value under high interference and load conditions ......................................................... 157 18.9 Bad UL SACCH Frames ...................................................................................................................................... 158

19. Ecell .......................................................................................................................................................... 159 19.1 ECell ERACH Success Rate................................................................................................................................ 160 19.2 ECell Emergency Call .......................................................................................................................................... 161 19.3 ECell Signalling .................................................................................................................................................... 162 19.4 ECell Voice Calls.................................................................................................................................................. 163 19.5 ECell Ghost RACH/ERACH ................................................................................................................................. 165 19.6 ECell Handovers .................................................................................................................................................. 165 19.7 ECell HO during data call ..................................................................................................................................... 167 19.8 ECell EMR ........................................................................................................................................................... 168 19.9 ECell simultaneous GPRS and EGPRS transfer.................................................................................................. 169 19.10 ECell Circuit Switched Dataf ................................................................................................................................ 170

20. DFCA ........................................................................................................................................................ 171 20.1 Speech Call Set-up via FACCH with DFCA ......................................................................................................... 171

DN0694168 Issue 2-0


20.2 AMR with DFCA................................................................................................................................................... 172 20.3 Synchronous & Asynchronous Handover with DFCA........................................................................................... 174 20.4 EGPRS with DFCA .............................................................................................................................................. 175 20.5 Antenna Hopping & DFCA antenna Sharing ........................................................................................................ 175

21. IMSI Based Handover............................................................................................................................... 176 21.1 IBHO Feature Activation, GSM to GSM ............................................................................................................... 176 21.2 GSM to GSM IBHO, call setup 2 MS with different PLMN, EMR/MR and multi-band .......................................... 177

22. CS3 & 4..................................................................................................................................................... 178 22.1 Paging Mode........................................................................................................................................................ 178 22.2 Data transfer ........................................................................................................................................................ 178 22.3 CS3 and CS4 GPRS Data transfer ...................................................................................................................... 180 22.4 CS4 with speech call............................................................................................................................................ 181 22.5 GPRS and EGPRS TBF’s on one time slot .......................................................................................................... 182 22.6 CS3 & CS4 Data transfer with IDD/4UD & IDD BBH configuration ...................................................................... 184 22.7 Link Adaptation: GPRS Link adaptation ............................................................................................................... 185 22.8 Link Adaptation: GPRS and EGPRS Link adaptation........................................................................................... 187 22.9 Data Transfer with A-bis Failure........................................................................................................................... 188 22.10 Data Transfer with Air Interface Failure................................................................................................................ 188 22.11 Cell Reselection & Timing Advance with GPRS CS3&4 ...................................................................................... 189 22.12 GPRS Territory Upgrade/Downgrade................................................................................................................... 191 22.13 GPRS CS3&4 Reliability at Various Distances..................................................................................................... 193 22.14 Mobile speed handling ......................................................................................................................................... 194 22.15 Dynamic Abis Allocation....................................................................................................................................... 194 22.16 TRX Loop Test ..................................................................................................................................................... 196 22.17 Abis loop test........................................................................................................................................................ 198 22.18 Intelligent Shutdown............................................................................................................................................. 198 22.19 Load and stability testing...................................................................................................................................... 199

23. Ghost RACH and PRACH Tests............................................................................................................... 200 23.1 Ghost RACH and PRACH Absolute Test ............................................................................................................. 200 23.2 Ghost RACH and PRACH Relative Test .............................................................................................................. 208

24. Modification of Timer values from BSC .................................................................................................... 214 24.1 Modification of LAPDm Timer value from BSC..................................................................................................... 214 24.2 Modified LAPDm T200 with Multi BCF ................................................................................................................. 214 24.3 Verification of SDCCH T200 timer value .............................................................................................................. 217 24.4 Verification of FACCH T200 timer value .............................................................................................................. 219

25. DRTRAU ................................................................................................................................................... 221 25.1 Support of DR TRAU framing in Synchronous and Asynchronous Handovers .................................................... 222 25.2 Supported AMR codecs in DR TRAU................................................................................................................... 226 25.3 Unsuccessful Handovers ..................................................................................................................................... 228 25.4 Support of Normal Handover ............................................................................................................................... 230 25.5 Packing and Unpacking of AMR calls with DR TRAU .......................................................................................... 231 25.6 Intra Cell Handovers with Speech Break less than 100 ms.................................................................................. 233 25.7 Synchronous & Asynchronous Inter Cell DR TRAU Handovers........................................................................... 238 25.8 Intra-Cell Handovers within an UltraSite Multi-BCF segment and Intra-Cell Handovers within a Chained MetroSite segment ........................................................................................................................................................... 241 25.9 Inter-Cell DR TRAU Handovers between UltraSite Multi-BCF Segments and Inter-Cell handovers between Chained MetroSite segments............................................................................................................................. 243 25.10 IntraCell DR TRAU Handover during MS in motion.............................................................................................. 245 25.11 Synchronous Inter Cell DR TRAU Handover during MS in motion....................................................................... 249 25.12 DR TRAU Handover during Intelligent Shutdown................................................................................................. 250 25.13 DR TRAU HO and Cell Reselection between E- and N-Areas of the same BTS ................................................. 253 25.14 DR TRAU Handover with DFCA........................................................................................................................... 254 25.15 DR TRAU Handover with Packet Data calls ongoing ........................................................................................... 255 25.16 DR TRAU Handover under Bad RF conditions .................................................................................................... 256 25.17 Continuous Synchronous Inter Cell DR TRAU Handovers................................................................................... 257 25.18 Synchronous Inter Cell DR TRAU Handover with FACCH Repetition.................................................................. 258 25.19 Asynchronous Inter Cell DR TRAU Handover during MS in motion ..................................................................... 261 25.20 DR TRAU with ICE+ Configuration ...................................................................................................................... 262 25.21 Continuous Asynchronous Inter Cell DR TRAU Handovers................................................................................. 263 25.22 Asynchronous Inter Cell DR TRAU Handover with FACCH Repetition ................................................................ 263

26. EGPRS in Extended TRXs ....................................................................................................................... 270 26.1 GPRS Data transfer with changing timing advance in E-Cell ............................................................................... 275

DN0694168 Issue 2-0


26.2 EGPRS MCS1 to MCS9 and IR in E-Area ........................................................................................................... 276 26.3 EGPRS Link Adaptation and IR in E-Area ........................................................................................................... 277 Purpose:........................................................................................................................................................................... 277 26.4 Cell Reselection with GPRS/EGPRS in E-Cell..................................................................................................... 278 26.5 GPRS/EGPRS Reliability at Various MS Speeds in E-Area................................................................................. 280 26.6 EGPRS power control in E-Area .......................................................................................................................... 281 26.7 Break in Abis interface during GPRS/EGPRS data transfer in E-Area................................................................. 282 26.8 GPRS Link adaptation in E-Area.......................................................................................................................... 282 26.9 Multiple Dynamic A-bis Allocation for E-TRXs ..................................................................................................... 284 26.10 EGPRS Modulation coding schemes and IR in E-Area........................................................................................ 284 26.11 EGPRS Link Adaptation in Unack Mode in E-Area .............................................................................................. 285 26.12 EGPRS data transfer with changing timing advance in E-Cell ............................................................................. 287 26.13 Simultaneous packet data transfer in both areas of E-Cell .................................................................................. 288 26.14 EGPRS/GPRS data transfer in E-Area with BER in Abis ..................................................................................... 289 26.15 EGPRS/GPRS Data Transfer after E-Cell Recovery from Power Breakdown ..................................................... 290 26.16 GPRS/EGPRS data transfer Stability in E-TRX of E-Cell..................................................................................... 290 26.17 GPRS/EGPRS data transfer with STIRC in E-Area ............................................................................................. 291 26.18 GPRS /EGPRS in E-Cell segment with Site Synch Improvement ........................................................................ 292 26.19 GPRS/EGPRS data transfer reliability during Intelligent shutdown modes .......................................................... 293 26.20 Abis loop test from BSC for EGPRS enabled E-TRX........................................................................................... 295 26.21 GPRS/EGPRS Data transfer with Fast Tune Synchronisation enabled ............................................................... 295

27. STIRC ....................................................................................................................................................... 296 27.1 STIRC enabled sector and EGPRS Link Adaptation............................................................................................ 296 27.2 EMR measurement reporting and comparison testing of STIRC and IRC ........................................................... 298 27.3 Enable and Disable STIRC in the first sector whilst Packet Data calls and speech calls ongoing in the second sector. .................................................................................................................................................................. 301 27.4 Enable and Disable STIRC in the first sector whilst AFS, AHS and CS Data calls ongoing in the second sector. 302 27.5 Speech Emergency call Setup via SDCCH.......................................................................................................... 303

28. AMR signalling Improvements .................................................................................................................. 304 28.1 Capability Notification - Lock/Unlock from BSC.................................................................................................... 307 28.2 Capability Notification - Block/Unblock from BTS Manager.................................................................................. 309 28.3 Capability Notification - TRX Replacement and Power Reset.............................................................................. 310 28.4 Capability Notification - Capability Notification after Sector Reconfiguration with BB Hopping ............................ 311 28.5 Feature Control - SACCH Repetition ................................................................................................................... 312 28.6 Feature Control - Downlink FACCH Repetition with Asynchronous Handover..................................................... 314 28.7 Feature Control - Downlink FACCH Repetition with Synchronous Handover ...................................................... 317 28.8 Downlink Message Transmission on SACCH ...................................................................................................... 318 28.9 UL DTX estimation and estimation validity........................................................................................................... 321 28.10 ASI Statistics - ASI Statistics for DL SACCH Repetition ...................................................................................... 323 28.11 ASI Statistics - ASI Statistics for UL SACCH Repetition ...................................................................................... 324 28.12 ASI Statistics - ASI Statistics for DL FACCH Repetition....................................................................................... 325 28.13 Non-Repetition of FACCH and SAACH - No Downlink FACCH Repetition with AMR disabled ........................... 329 28.14 ASI with DFCA - SACCH Repetition with DFCA .................................................................................................. 331 28.15 ASI with DFCA - Downlink FACCH Repetition with DFCA ................................................................................... 332 28.16 ASI with DFCA - Uplink DTX estimation and estimation validity with DFCA ........................................................ 334 28.17 ASI with IDD/4UD - SACCH Repetition with IDD/4UD ......................................................................................... 335 28.18 ASI with IDD/4UD - Downlink FACCH Repetition with IDD/4UD.......................................................................... 337 28.19 ASI with IDD/4UD - UL DTX estimation and estimation validity with IDD/4UD..................................................... 339 28.20 ASI with E-Cell - SACCH Repetition with E-Cell .................................................................................................. 340 28.21 ASI with E-Cell - Downlink FACCH Repetition with E-Cell ................................................................................... 342 28.22 ASI with E-Cell - UL DTX estimation and estimation validity with E-Cell.............................................................. 344 28.23 ASI with Early Classmark Sending - SACCH Repetition with ESI Disabled ......................................................... 345 28.24 ASI with Early Classmark Sending - Downlink FACCH Repetition with ESI Disabled.......................................... 347 28.25 ASI with DR TRAU Handover - SACCH Repetition after DRTRAU handover...................................................... 349 28.26 ASI with DR TRAU Handover - Downlink FACCH Repetition during Inter Cell DRTRAU handover .................... 353 28.27 ASI with Separate UL/DL AMR thresholds - Downlink FACCH Repetition with Separate UL/DL AMR thresholds......................................................................................................................................................................... 356 28.28 ASI with STRIC - SACCH Repetition with STIRC ................................................................................................ 357 28.29 ASI with STRIC - Downlink FACCH Repetition with STIRC ................................................................................. 359 28.30 ASI with STRIC - UL DTX estimation and estimation validity with STIRC............................................................ 362 28.31 ASI with Different Hopping Modes - SACCH Repetition with Different Hopping modes....................................... 364

DN0694168 Issue 2-0


28.32 ASI with Different Hopping Modes - Downlink FACCH Repetition with Different Hopping modes ....................... 365 28.33 ASI with Different Hopping Modes - Uplink DTX Estimation and Estimation Validity with Different Hopping modes ................................................................................................................................................................ 367 28.34 ASI with BSS and Site Synchronization - SACCH Repetition with BSS and Site Synchronization ...................... 369 28.35 ASI with BSS and Site Synchronization - Downlink FACCH Repetition with BSS and Site Synchronization................................................................................................................................................................ 371 28.36 ASI with RLT - ARLT with SACCH Repetition...................................................................................................... 373 28.37 Power Control with SACCH Repetition - Power Control with SACCH Repetition................................................. 374 28.38 SACCH Repetition with MS Speed and Distance................................................................................................. 376 28.39 UL DTX Estimation Accuracy............................................................................................................................... 379 28.40 Downlink FER Reporting without SACCH Repetition ........................................................................................... 380 28.41 Downlink FER Reporting with UL SACCH Repetition .......................................................................................... 381 28.42 ASI with IUO - SACCH Repetition with IUO ......................................................................................................... 383 28.43 ASI with IUO - Downlink FACCH Repetition with IUO.......................................................................................... 384 28.44 ASI with IUO - Uplink DTX Estimation and Estimation Validity with IUO.............................................................. 386 28.45 Scheduling of MI Messages on Air Interface........................................................................................................ 388 28.46 ASI with EGPRS - SACCH Repetition with EGPRS............................................................................................. 390 28.47 ASI with EGPRS - Downlink FACCH Repetition with EGPRS ............................................................................. 392 28.48 Downlink FACCH Power Increment ..................................................................................................................... 393

29. Common MAL for both PGSM and EGSM frequencies............................................................................ 396 30. Directed Retry ........................................................................................................................................... 397 31. Intracell SDCCH Handover with SMS....................................................................................................... 399 32. Network Controlled Cell Re-selection ....................................................................................................... 400 33. STIRC ....................................................................................................................................................... 401

33.1 Enable/Disable STIRC from BSC......................................................................................................................... 401 33.2 STIRC enabled sectors and IDD/4UD.................................................................................................................. 402 33.3 STIRC enabled sector and Intelligent Shutdown.................................................................................................. 403 33.4 STIRC enabled sector and hopping modes ......................................................................................................... 405

Contact:

Contact your local Nokia Siemens Networks support

Summary of changes:

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

DN0694168 Issue 2-0


1. PURPOSE

This document incorporates regression test phase and defines the test cases for verifying the telecom features of BTS SW CX (M) 7 using BSC SW S14 This document is meant both for UltraSite and MetroSite base stations.

Some testcases have been executed on S13 BSC SW for compatibility purpose.

In general, the features and test cases described herein are intended for Nokia Siemens Networks GSM 800, 900, 1800 and 1900 environments. However, due to specific GSM environment, or customer’s configurations, or requirements or peculiarities, some features and test cases might not apply to all environments. Those test cases not valid for all bands are marked as to which band they apply.

2. DOCUMENT STRUCTURE

This document is sectioned into major testing view: UltraSite EDGE BTS Regression.

Within these sections there are high level testing descriptions. These areas are then structured in the following way:

• Common aspects of test execution and configurations for all the features or functional areas.

The following sections detail the individual test cases:

• The scope of the test case.

• Specific aspects of testing the case (if required).

• A table containing the test case steps and expected outputs. Following the test steps the table contains the channel and hardware configurations to be applied to the test case.

Repeated for each test case.

3. COMMON ASPECTS OF TEST EXECUTION AND CONFIGURATION

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

Note 1. BSC parameters are set to their default values until otherwise stated.

Note 2. Test cases have to be performed on both UltraSite and MetroSite base stations unless specifically mentioned.

ECell is to be tested for UltraSite only.

“Modification of LAPDm timer value” is to be tested for UltraSite only.

DN0694168 Issue 2-0


Note 3. Minimum TCH calls repetitions for a test case is determined by the following criteria:

A TCH activated on each TRX in the cell at least once A TCH activated on each BCCH TRX timeslot A TCH activated on each timeslot of non-BCCH TRX in each hopping group (calls can be distributed among the TRXs to cover each hopping group)

Note 4. Antenna Hopping (AH) and RF+ Antenna Hopping (RAH) is used only when test case is executed on UltraSite.

Note 5. Enable CS3&4, only when specified. CS3&4 can be enabled from BSC using command:

EQV: BTS=<x>: CS34=Y;

DAP is mandatory to attach with GPRS enable TRXs when CS3&4 is enabled.

Note 6. Use GPRS capable MS only for GPRS data transfer, when EGENA=Y.

Note 7. With 16 Kbps TRX signalling link only 12 SDCCH channels/TRX are possible.

Note 8. Wherever the configuration is mentioned as “Any” or “Multi TRX”, use 4 OMNI configuration.

Note 9. A5/3 BTS SW packet of CX(M)7, when used with BSC S14, supports A5/3, A5/1 and A5/0 ciphering types. BTS SW downgrades its ciphering scheme in accordance with the ciphering type commanded by MSC.

DN0694168 Issue 2-0


3.1 Hardware Requirements

Base stations UltraSite base stations with the following transceiver units are required to perform the test cases in this document:

TSGB 900 EDGE

TSDB 1800 EDGE

TSTB 800 EDGE

TSPB 1900 EDGE

TSGA 900 GSM

TSDA 1800 GSM

TSPA 1900 GSM

The BB2A, BB2E and BB2F base band cards will be required for any UltraSite configuration. For GSM TRX configuration we can use any of these base band cards while for EDGE and Mixed configuration we need to use BB2E or BB2F base band cards.

MetroSite base stations with the following transceiver units are required to perform the tests in this document:

CTGA 900 EDGE

CTDA 1800 EDGE

WTFA 800 EDGE

WTPA 1900 EDGE

HVTG/VTGA 900 GSM

HVTD/VTDA 1800 GSM

HVTP/VTPA 1900 GSM

DN0694168 Issue 2-0


UltraSite BTS Configuration Definitions The following BTS Configuration definitions are used in this document.

• GSM Configuration: BB2A with one or two TSxA

• EDGE Configuration: BB2E/BB2F with one or two TSxB

• Mixed Configurations: Mixed-1: “BB2A with one or two TSxA” and “BB2E/BB2F with one or two

TSxA”

Mixed-2: BB2E with one TSxA and one TSxB

Mixed-3: “BB2A with one or two TSxA” and “BB2E with one or two TSxB“

Mixed-4: “BB2A with one or two TSxA” and “BB2F with one or two TSxB “

Mixed-5: BB2F with one TSxA and one TSxB

• Hybrid Configuration: BB2E/BB2F with one or two TSxA

Other Network Elements

BSC

Core Network with GPRS and EDGE capabilities

In addition to the BTS under test, the network elements listed in [Table 2] are required.

GSM mobile handsets supporting the features are defined in [Table 1].

Table 1 GSM Mobile Handsets (RSC & Non RSC)

Feature Specific options Speech channels FR, HR, EFR, AMR Single data channels 9600, 14400 Non-Transparent Multislot data channels 9600 or 14400 Non-Transparent using 1+1, 2+2 or 3+1

timeslots GPRS Class B & Class C EGPRS Class B & Class C General SMS Mobile Originating (MO) & Mobile Terminating (MT) Enhanced Measurement Reports

EMR Capable

DN0694168 Issue 2-0


3.2 Software Requirement

BTS SW CX7 and Site Wizard 7 releases are required for the testing. SW versions of the other network elements are detailed in [Table 2]. The latest Change Deliveries (CD) should be installed into the network elements and recorded in the test log.

Table 2 SW Versions of Other Network Elements

Network Element SW Version BSC S14, S13 MSC/HLR M14.2 LMU 4.4 LMUB 4.1 SGSN SG7.0 Transmission (FXC E1, FXC E1/T1, FXC RRI)

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

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

PC Applications - Internet browser

- FTP, UDP software

- Terminal Emulator

3.3 Specialist Test Equipment Requirements

The following test equipment is required in some test cases:

- Traffic Generator, preferably Load Tester

- IR/LA Rig

- Assortment of combiners

- Attenuators

- Terminators

- 8 PSK & GMSK capable signal generator

- Spectrum analyser

- GSM Analyser for the A-bis, Gb and A interfaces

- Air Interface Monitoring devices and software

- Frequency Counter

- 8PSK & GMSK capable Fading Simulator

DN0694168 Issue 2-0


- Abis Breaker

- Location Management Unit

- CMU

- RF TA rig

DN0694168 Issue 2-0


4. SPEECH CALL SETUP

4.1 Speech and Emergency call Setup via SDCCH

Purpose:

The purpose of these tests is to verify that speech and emergency calls can be activated from SDCCH channels.

Note 10. EFR, FR & AFS are supported on TCHF and EFR, FR, HR, AFS & AHS are supported on TCHD and all paging groups available in configuration are used.

Note 11. EFR call is possible in 900/1800/1900 band sites. All test cases for emergency call will activate FR/EFR/AFS TCH and normal call should be activated on TCH specified by test case.

Note 12. Different IMSI are used during a test case to verify all paging groups possible in configuration.

AG Blocks can be set by MML command ZEQJ:BTS=xx:AG=yy;

Note 13. For test cases involving more than one speech Codec (i.e. FR and AMR) two types of MS must be used and while making calls using minimum repetition criteria, each speech Codec specified in test case must be used at least once.

Note 14. For the TCHD configuration, each tested timeslot is reused in sequence of FR, HR#0, FR, HR#1 and then FR again.

Note 15. Dynamic power control is enabled at the BSC by defining different values of PMAX and PMIN in the power parameters of the BTS.

Input Expected Output Configure the site as per test case configuration For test case no. 2, 4 & 7, enable dynamic DL power control at the BSC for the test BTS(s).

Site is in supervisory state. There are no active alarms except for ‘7801: MMI connected to Base Station’ Dynamic power control is defined for the test BTS(s).

DN0694168 Issue 2-0


Calls are made from MS to MS on the test BTS using minimum call repetition criteria. Each call must be held for at least 60 seconds. For test case 6 & 10, use SDCCH of non -DFCA non-BCCH TRX for call initiation. For testcase 6A: 8 hrs stability with AMR full rate codec set to disabled. Only AHS calls are to be made with full loading on all TRXs.

All calls are successful and held until user terminates the calls. . The received audio quality is good and without distortion of the original speech, and there are no additional disturbing sounds heard at the receiving end during speech or silence periods.

The A-bis TRX signalling links are followed during the test.

In A-bis Measurement Result values for RX Qual in both UL/Dl and UL FER and DL FER( In case of EMR calls) are predominantly 0. A-bis RF RES IND message for a reserved TCH timeslot includes the active interference measurement. In CCCH LOAD IND message (uplink), BTS reports non-zero values for RACH access count.

For test case 2, 4 and 7 BS power control and measurement result messages are followed for both BCCH TRX and for non- BCCH TRXs(during active call).

For test case 2 : The power control level reported in measurement result for both BCCH TRX and non- BCCH TRXs (during call) is the power commanded by BSC in the BS Power Control message immediately prior to the measurement result. For test case 4 and 7: The power control level reported in measurement result for the time slot of the BCCH TRX is the PMAX value set at BSC. For non- BCCH TRXs (during call), the power control level reported in measurement is the power commanded by BSC in the BS Power Control message immediately prior to the measurement result.

Calls are made to the emergency service number (112) where specified. A timeslot on each TRX in the configuration is used at least once. Each call must be held for at least 30 seconds.

All emergency calls are successful . Calls are held until user terminates the calls.


A-bis Channel Required message contains ‘Emergency Call’ for field Request reference.

Case Ref.

Channel configuration

Codec BTS Configuration/Site type

AG blocks in BCCH

Hopping Mode

Emergency Call

1. Combined BCCH + TCHF

EFR/FR/AFS

Any EDGE/MetroSite

0 Non-hopping

Yes4

2. Non-combined BCCH + TCHF

EFR/FR/AFS

6 Omni Mixed 5 /UltraSite

1 BB-hopping

Yes 2


AFS Any EDGE/UltraSite

3 RAH-hopping

Yes5

DN0694168 Issue 2-0


4. Non-combined BCCH + TCHD

HR/FR/AHS

Any, EDGE/UltraSite

0 RF-hopping

No1

5. Non-combined BCCH + TCHD, 2 Channels Configured as TCHH

HR /EFR/AHS

Any, EDGE/MetroSite

1 BB-hopping

Yes 2

6. (Combined BCCH +7*TCHF) (SDCCH+7*TCHD)

HR /FR/EFR

4 Omni EDGE, 2 N TRX &2 DFCA TRX/MetroSite

1 RF-hopping for Non DFCA TRXs

Yes 2


HR/FR/AHS

Any GSM/UltraSite 0 RF-hopping

No

1A Combined BCCH + TCHF

FR 1 TRX GSM with modified BB2A card

1 Non-hopping

No7

1B Combined BCCH + TCHF

FR 1 TRX 1 Non-hopping

No

1C Combined BCCH + TCHF

FR 4 OMNI EDGE HW 1 BB No9

2A Combined BCCH + TCHF4

EFR 2 TRX EDGE HW 0 BB-hopping

Yes9

3A Non-combined BCCH + TCHF1

HR/FR/AFS (for AFS call use only 5.15 kbps in the codec set)

4 – 12 TRXs EDGE

1 BB-hopping

Yes 2,8

6A Non-combined BCCH + TCHD

AHS 2TRX 0 RF-hopping

No6

Case Ref.


Codec BTS Configuration/Site type

Hopping Emergency Call

8 Combined BCCH+TCHF

FR/AFS Common BCCH (2+2 configuration) 3/MetroSite

RF-Hopping (BTS1), BB-Hopping (BTS2)

Yes 5

9 Combined BCCH+TCHD

HR/FR (2+2), EDGE/UltraSite

BB-hopping Yes

10 (Combined BCCH +7*TCHD)(SDCCH+7*TCHF)

HR/FR/EFR

4 Omni with 2 DFCA TRXs/UltraSite

RF-hopping on non DFCA TRXs

Yes

1 61 ARFN used in MA List. 2 MS does not have valid SIM card so only emergency call are possible. 3 Call is made both in BCCH and non BCCH BTS of common BCCH segment. 4 EDAP is configured for all TRX. 5 Use BSC S13 SW. 6 Use BSC S13 CD3.0 SW. 7 Monitor the STR messages with the help of UC-DSP traces. Verify that no STR-0x0E is present in UC-DSP traces. 8 Ensure that voice quality is good. Also listen to speech and verify that there is no distortion. 9 Make sure that TSL 0 of non BCCH TRX doesn't Hop when it is idle.

DN0694168 Issue 2-0


4.2 UL FER reporting

Purpose: The purpose of these tests is to verify that UL FER with value 0 is reported at Rx_Qual_full (0 to 3) and that no FER with value 24 is reported at Rx qualities (0 to 3).

Input Expected Output Configure the site as per test case configuration.

Site is in supervisory state with no unexpected alarm.

Make AFS & AHS speech calls in pairs. Call answering time should be more than 10 sec

Calls are successful. For MTC calls, all Measurement Results between Alert & Connect messages report Uplink FER value as 0. After CONNECT, the UL FER value is observed to be 0

Make EFR & GSM FR speech calls in pairs. Call answering time should be more than 10 sec

Calls are successful. For MTC calls, all Measurement Results between Alert & Connect messages report Uplink FER value as 0. After CONNECT, the UL FER value is observed to be 0.

Repeat Step2 and Step3 with different mobile models

Result is consistent for all mobile models.

Case Ref. BCF Configuration

Band Channel Configuration

1 4 Omni EDGE 1800 TCHD 2 4 Omni EDGE 1800 TCHD Input Expected Output

Configure the site as per test case configuration. Set UL DTX off

Site is in supervisory state with no unexpected alarm.

Make AFS & AHS speech calls in pairs Call answering time should be more than 10 sec

Calls are successful f. or MTC calls, all Measurement Results between Alert & Connect messages report Uplink FER value as 0. After CONNECT, the UL FER value is observed to be 0.

Make EFR & GSM FR speech calls in pairs. Call answering time should be more than 10 sec

Calls are successful . for MTC calls, all Measurement Results between Alert & Connect messages report Uplink FER value as 0. After CONNECT, the UL FER value is observed to be 0.

Repeat Step2 and Step3 with different mobile models

Result is consistent for all mobile models.


Band Channel Configuration

3 4 Omni EDGE 900 TCHD

DN0694168 Issue 2-0


Input Expected Output Configure the site as described in the test case.

The site is in supervisory state. No unexpected alarm is observed on the BTS Manager and the BSC.

Set the AMR (AFS/ AHS) MTC mobile (NOKIA 6220/6230) with ringtone “Nokia Tune” and profile other than “silent”.

Make AFS and AHS calls. Adjust the UL Interference level with signal generator such that Rx Quality range is 0 and 1 only.

Between ALERTING and CONNECT messages for AMR MTC mobile, there should be no multiframe with 24 FER till CONNECT message received if rx_qual_full is 0. FER value should be 0 for the SACCH multiframe with rx_qual_full 0 and 1.

Increase the UL Interference with signal generator so that Rx Qual is 2 or 3

FER value should be predominantly 0 for SACCH multiframes with rx_qual_full 2 and 3. There could be the cases where very few blocks fails BER Threshold or 1 to 3 blocks fails CRC checking at BTS or combination of both but percentage of non zero FER should be very less.

Increase the UL Interference with signal generator so that Rx Qual is above 3.

FER value should be 24 for most of the SACCH multiframes for rx_qual_full 4 to 7.

Case Ref. Configuration 4 4 OMNI EDGE, UL DTX on1 1Use 7270 and 6220 MS, use 7270 for MT call.

4.3 Dynamic SDCCH Reservation

Purpose:

The purpose of these test cases is to verify that dynamic SDCCH channels can be reserved and released successfully from any TS configured as either TCHF or TCHD and that TS can be reused as TCH after dynamic activation.

Note 16. Ensure FACCH_CALL_SET_UP is not active on concerned BSC.

Note 17. For the TCHD configuration HR and FR call is established.

Input Expected Output Configure the site as per test case configuration

Site is in supervisory state. There are no active alarms except for ‘7801: MMI connected to Base Station’

Dynamic SDCCH feature is activated at BSC.

Dynamic SDCCH feature is successfully activated at the BSC.

DN0694168 Issue 2-0


Input Expected Output SDCCH reservations are made by IMSI Attach and / or sending and receiving of SMS at the same time. .(SDCCH reservation can be made using GLINK script.) The number of mobiles used for test must be at least the same as the number of static SDCCH channels plus 8 additional mobiles.

A TCH is assigned to SDCCH/8 when static SDCCH is all reserved. All location updates and SMS sending / receiving are successful.

When the case is complete, a speech call is established on the same TCH as used for dynamic SDCCH. In case of TCHD HR & FR call is established.

Call is successful. The timeslot can be re-used as TCH after all dynamic SDCCH/8 have all been released.


When a TCH is dynamically made SDCCH/8, the A-bis RF RES IND message includes interference values for all un-reserved sub timeslots. After all dynamic SDCCH have been released from TS, the RF RES IND reports the values for the original TS configuration again. In CCCH LOAD IND message (uplink), BTS should report non-zero values for RACH access count.

Case Ref.

Channel Configuration BTS Configuration/Site Type

Hopping Mode

AG blocks in BCCH

1 MBCCB + 7*TCHF 4 Omni EDGE/UltraSite

RAH-Hopping 1

2 MBCCB + 7*TCHF1 4 Omni EDGE/UltraSite, 2 N-TRXs, 2 DFCA TRXs

Non- Hopping 1

3 (MBCCH + SDCCH + 6*TCHD)(SDCCH + 7*TCHF)

4 Omni GSM/EDGE/MetroSite

BB-Hopping 3

4 (MBCCH + SDCCH + 6*TCHD)(SDCCH + 7*TCHF)

4 TRX Sector (2 BB2F with 2 TSxA and 2 TSxB)/UltraSite

BB-Hopping 3

5 (MBCCH + SDCCH + 6*TCHD)(SDCCH + 7*TCHF) 1

4 Omni EDGE/MetroSite, 2 N-TRXs, 2 DFCA TRXs

Non- Hopping 3

1 For test case 2 & 5 call is established on non-DFCA non-BCCH TRX.

DN0694168 Issue 2-0


4.4 Rx Diversity testing during speech call

Purpose:

The purpose of these test cases is to check that Rx diversity feature works properly during speech calls.

Input Expected Output Create the site as per the test case configuration.

Site is in supervisory sate with no active alarms reported at both BSC and BTS Manager except for alarm “7801: MMI CONNECTED TO BASE STATION: Local MMI Connected”.

RX Diversity feature is set ON for the BTS. RX Diversity feature is successfully set ON for the BTS from BSC.

MS to MS call is established on all TRXs of the test BTS. Calls must be held for the entire test duration.

Calls are successfully established and on going. Received audio quality is good with no distortion of the original speech. No additional disturbing sounds are heard at the receiving end during speech or silence periods.

A-bis TRX signalling links are followed during the test.

A-bis Measurement Result message values for RX Qual in both UL/DL and UL FER are predominantly zero.

Block the specified Rx path of the TRX on which call is active so that it can receive Rx signal through only one Rx path. Use terminator for blocking the signal.

Call is undisturbed. Received audio quality is good with no distortion of the original speech. No additional disturbing sounds are heard at the receiving end during speech or silence periods.

A-bis TRX signalling links are followed during the test.

A-bis Measurement Result message values for RX Qual in both UL/DL and UL FER are predominantly zero.

Case Ref.

BTS Configuration Rx Path blocked

1 4 Omni DIV 2 4 Omni EDGE DIV 3 4 Omni Main 4 2 Omni Main

DN0694168 Issue 2-0


4.5 Speech Call and Emergency Call Setup via FACCH

Purpose:

The purpose of these test cases is to verify that a TCH channel can be first used for signalling (speech call & emergency call establishment) and then be modified to a speech channel.

Note 18. For test cases involving more than one speech Codec (i.e. FR and AMR) two types of MS must be used and while making calls using minimum repetition criteria, each speech Codec specified in test case must be used at least once.

Note 19. For the TCHD configuration, each tested timeslot is reused in sequence of FR, HR#0, FR, HR#1 and then FR again.

Note 20. Terminating HR FACCH call is not possible.

Note 21. Dynamic SDCCH feature is deactivated on concerned BSC.


Input Expected Output Create the site as per the test case configuration. For test case no. 1 enable dynamic DL power control at the BSC for the test BTS(s).

Site is in supervisory state with no active alarms reported at both BSC and BTS Manager except for alarm “7801: MMI CONNECTED TO BASE STATION: Local MMI Connected”. Dynamic power control is defined for the test BTS(s).

FACCH_CALL_SET_UP is activated on BSC. Static SDCCH channels are reserved in sector.

FACCH_CALL_SET_UP is successfully activated on BSC. SDCCH channels are successfully reserved in the sector.

Calls are made from MS to MS on the test BTS using minimum call repetition criteria. Each call must be held for at least 60 seconds.

All calls are established via FACCH on TCH TS. After signalling is complete the TS is changed to appropriate Codec via Mode Modify message and calls are held until terminated. The received audio quality is good and without distortion.

DN0694168 Issue 2-0


Input Expected Output The A-bis TRX signalling links are followed during the test.

A-bis RF RES IND message for a reserved TCH timeslot shall include the active interference measurement when defined as signalling and speech activation.

For test case 1 BS power control and measurement result messages are followed for both BCCH TRX and for non- BCCH TRXs(during active call).

The power control level reported in measurement result for the time slot of the BCCH TRX is the PMAX value set at BSC. For non- BCCH TRXs(during call), the power control level reported in measurement is the power commanded by BSC in the BS Power Control message immediately prior to the measurement result.


All emergency calls are successful. Calls are held until user terminates the calls.

Case Ref.


Codec BTS Configuration/Site Type

Hopping Mode

Emergency Call

1. Combined BCCH+TCHF

FR/AFS 4 Omni EDGE Non-hopping

Yes

2. Combined BCCH + TCHD1

HR/FR/AHS 4 Omni Mixed BB-hopping

Yes

3. Non-combined BCCH + TCHD2,3

HR/EFR/AHS (4+4) EDGE BB-hopping

Yes

4. Non-combined BCCH + TCHD2

HR/EFR/AHS 4 Omni EDGE BB-hopping

Yes


FR/EFR/AFS 2+2 Omni EDGE/MetroSite

RF-hopping

Yes


HR/EFR/AHS Any GSM BB-hopping

Yes

7. Non-combined BCCH + TCHF3

FR/EFR/AFS Any RF-hopping

Yes

8 Non Combined BCCH + TCHF4

EFR/AFS 4 OMNI EDGE BB-hopping

No

1 MS does not have valid SIM card 2 EDAP is configured for all TRX 3 Use BSC S13 SW 4 Make sure that TSL 0 of non BCCH TRX doesn't Hop when it is idle

DN0694168 Issue 2-0


4.6 Support for Different Ciphering Algorithms

Purpose The purpose of these tests is to verify that different ciphering algorithms are supported.

Note 23. MSs which support A5/1 are used (the A5/1 MS supports A5/0 and A5/1 ciphering modes).

Input Expected Output Site is created with the BTS configuration as specified in the test case.

Site is successfully created as per the configuration.

SW package is attached and activated as per the test case. Commission the site.

Software is successfully activated and after commissioning site comes up with supervisory state no active alarms reported at both BSC and BTS Manager except for alarm “7801: MMI CONNECTED TO BASE STATION: Local MMI Connected”.

Location update is performed. If the BTS SW Package supports the ciphering algorithm requested by the NW then, location update is successful. If the BTS SW Package does not support the ciphering algorithm requested by the NW then, location update is not done and error report is seen at the A-bis.

Monitor A-bis interface through GPA for location update.

If A5/0 ciphering algorithm is in use then, “Encr. Info” field in “ENCR. CMD” will contain “no encryption required” and “Ciphering Mode Setting” in CIPHERING MODE COMMAND” message should have A5/0 ciphering type. If A5/1 ciphering algorithm is in use then, “Encr. Info” field in “ENCR. CMD” message and “Ciphering Mode Setting” in "CIPHERING MODE COMMAND” message will contain ciphering type (A5/1)

Attempt a call in the sector. For case 8 calls are attempted on all the TRXs of the sector.

If the BTS SW Package supports the ciphering algorithm requested by the NW then the call/calls is/are successful. If the BTS SW Package does not support the ciphering algorithm requested by the NW then, call/calls will not mature and error report can be seen at the A-bis.

DN0694168 Issue 2-0


Input Expected Output Monitor A-bis interface through GPA for MO and MT call/calls. Verify “ENCR. CMD” (Encryption command) message.


Verify “CHAN. ACT.” (Channel Activation) message for TCH.

If A5/1 ciphering algorithm is in use then, “Encr. Info” field in “CHAN. ACT.” message for TCH will contain ciphering type (A5/1) If A5/0 ciphering algorithm is in use then, “Encr. Info” field will be missing in “CHAN. ACT.” message

Verify “ASSIGNMENT COMMAND” message.

If A5/1 ciphering algorithm is in use then, “Cipher Mode Setting” in "ASSIGNMENT COMMAND” message will contain ciphering type (A5/1). If A5/0 ciphering algorithm is in use then, Cipher Mode Setting” will be missing "ASSIGNMENT COMMAND” message

For case 3 & 4 perform the following steps. SMS (up to 160 characters) is sent.

If the BTS SW Package supports the ciphering algorithm requested by the NW then SMS is sent and received successfully. If the BTS SW Package does not support the ciphering algorithm requested by the NW then, SMS is sent successfully and error report is seen at the A-bis.

Monitor A-bis Interface for SMS through GPA.


Case Ref.

BTS Configuration/Site Type

SW Packages Used in BTS

IMSI Ciphering Level at MSC

Location update

Call set-up

1. Any A5/0 A5/0 Accepted Accepted 2. 2 omni IDD, BB

hopping A5/3 A5/1 Accepted Accepted

3. 4 Omni EDGE with BB2E card1

A5/0 A5/3 Not accepted

Not accepted

DN0694168 Issue 2-0


Input Expected Output 4. 4 Omni

GSM/MetroSite A5/3 A5/0 Accepted Accepted

5. Any2 A5/3 A5/0 Accepted Accepted 6. Any/UltraSite2 A5/3 A5/1 Accepted Accepted

7. 4 Omni Hybrid, GSM TRXs with BB2E card1

A5/3 A5/1 Accepted Accepted

8. 4 Omni GSM/EDGE A5/0 A5/1 Not accepted

Not accepted

9. Any EDGE A5/0 A5/1 Not accepted

Not accepted

1Use Release 6 MS 2Use BSC S13 SW

5. SINGLE TIMESLOT DATA CALL SETUP

Purpose: The purpose of these cases is to verify that single timeslot data channels can be activated, different user data rates are supported, and that 7 & 8 bit data can be transferred at the expected data rate.

Note 24. Each test case is made using a mixture of originating / terminating sources (MS – MS, MS – PSTN & PSTN –MS). Calls are established using minimum call repetition criteria.

Note 25. Data packet of 7-bit ASCII type is transferred via raw ASCII protocol and 8-bit data file by Z-modem protocol.

Note 26. Received contents of the file are compared with the sent one for the correctness.

5.1 Non-Transparent Data via SDCCH

Purpose: The purpose of these cases is to verify that single timeslot non-Transparent data channels can be activated from SDCCH channels, different user data rates are supported, and that 7 & 8 bit data can be transferred at the expected data rate.


DN0694168 Issue 2-0


Test Tools Required: PSTN Setup

Equipment and BTS Set-Up As per test case configuration.

Input Expected Output Setup a CS data call as per the test case. For test case 1 & 8, enable dynamic DL power control at the BSC for the test BTS(s).

Data call is established successfully and held until user terminates the call. Dynamic power control is defined for the test BTS(s).

A data packet of at least 200kb is transferred from A to B and then again from B to A.

Data is successfully sent and received in both directions and the user data rate is achieved on transfers. In lab conditions there are no bit errors on user data.


In A-bis Measurement Result message, values for RX Qual in both UL/DL are predominantly zero. A-bis RF RES IND message for a reserved TCH timeslot will include the active interference measurement when defined as non-transparent data activation.

For test case 1 & 8 BS power control and measurement result messages are followed for both BCCH TRX and for non- BCCH TRXs (during active call).

The power control level reported in measurement result for both BCCH TRX and non- BCCH TRXs (during call) is the power commanded by BSC in the BS Power Control message immediately prior to the measurement result.

Case Ref.

Channel Configuration

BTS Configuration

User Rate

User Data Hopping Mode

1. TCHF 1 Any EDGE 9600 7 bit ASCII BB-Hopping

2. TCHF1 Any EDGE 14400

8 bit data file RAH-Hopping

3. TCHF1 Any 4800 8 bit data file RF-Hopping

4. TCHD Any EDGE 9600 8 bit data file BB-Hopping

5. TCHD Any3 9600 8 bit data file BB-Hopping

6. TCHF Use configuration as in Figure 3

14400

7 bit ASCII Use as specified in figure

7. TCHF2 Use configuration as in Figure 1

14400


8. TCHF1 Any GSM 9600 7 bit ASCII BB-hopping 1 No needs to make PSTN-MS Calls 2 Data transfer is done both in master and slave BTS of multi BCF segment. BCCH is on Talk Family BTS. 3 Use BSC Software S13

DN0694168 Issue 2-0


5.2 Non-Transparent Data via FACCH

Purpose:

The purpose of these test cases is to verify that a TCH channel can be first used for signalling (call establishment) and then be modified to a data channel.


Input Expected Output Dynamic SDCCH feature is deactivated and FACCH_CALL_SET_UP is activated on BSC. Static SDCCH channels are reserved in sector

FACCH_CALL_SET_UP is successfully activated on BSC. SDCCH channels are successfully reserved in the sector.

Setup a data call as per the test case. Call is established via FACCH on TCH TS. After signalling is completed, the TS is automatically changed to appropriate codec via Mode Modify message and held until user terminates the call.

A data packet of at least 500 kB is transferred from A to B and then again from B to A.

Data is successfully sent and received in both directions and the user data rate is achieved on transfers in lab conditions. There are no bit errors on user data.

The A-bis TRX signalling links are followed during the test

In A-bis Measurement Result message, values for RX Qual in both UL/DL are predominantly zero. A-bis RF RES IND message for a reserved TCH timeslot will include the active interference measurement when defined as non-transparent data activation.

Case Ref.


BTS Configuration

User Rate User Data

Hopping Mode

1. TCHF Any EDGE 9600 7 bit ASCII

BB-Hopping

2. TCHD 1 Any EDGE 14400 7 bit ASCII

Non-Hopping

3. TCHD Any, EDGE 14400 8 bit data file

RAH-Hopping

1 EDAP is configured for all TRX

5.3 Transparent Data via SDCCH

Purpose:

The purpose of these test cases is to verify that single timeslot transparent data channels can be activated from SDCCH channels, different user data rates are supported and 7 & 8 bit data can be transferred at the expected data rate.

DN0694168 Issue 2-0




Input Expected Output Setup a data call as per the test case. For test case 3 setup a call on the BCCH TRX. For test case 3, enable dynamic DL power control at the BSC for the test BTS(s).

All calls are established and held until user terminates the call. Dynamic power control is defined for the test BTS(s).

A data packet of at least 500 kB is transferred from A to B and then from B to A.

Data is successfully sent and received in both directions and the user data rate is achieved on transfers. There are no bit errors on user data.


In A-bis Measurement Result message, values for RX Qual in both UL/DL are predominantly zero.

For test case 3, BS power control and measurement result messages are followed for both BCCH TRX and for non- BCCH TRXs (during active call).

The power control level reported in measurement result for both BCCH TRX and non- BCCH TRXs (during call) is the power commanded by BSC in the BS Power Control message immediately prior to the measurement result.

Case Ref.


BTS Configuration/ Site Type

User Rate User Data Hopping Mode

1. TCHF1 Any EDGE 14400 8 bit data file

Non- Hopping

2. TCHD Any 9600 7 bit ASCII Non- Hopping

3 TCHF1 Any EDGE 4800 7 bit ASCII RAH-Hopping

4. TCHD Any EDGE 9600 7 bit ASCII NAH- Hopping

1No need to make PSTN-MS Calls.

5.4 Transparent Data via FACCH

Purpose: The purpose of these test cases is to verify that a TCH channel is first used for signalling (call establishment) and then be modified to a data channel.


DN0694168 Issue 2-0


Input Expected Output Dynamic SDCCH feature is deactivated and FACCH_CALL_SET_UP is activated on BSC. Static SDCCH channels are reserved in sector.

Dynamic SDCCH feature is successfully deactivated. FACCH_CALL_SET_UP is successfully activated on BSC. Static SDCCH channels are successfully reserved in sector.

Setup a data call as per the test case. Call is established via FACCH on TCH TS. After signalling is completed, the TS is automatically changed to appropriate Codec via Mode Modify message and held until user terminates the call.

A data packet of at least 200kb is transferred from A to B and then again from B to A.

Data is successfully sent and received in both directions and the user data rate is achieved on transfers in lab conditions. There are no bit errors on user data.


In A-bis Measurement Result message, values for RX Qual in both UL/DL are predominantly zero.

Case Ref.


BTS Configuration

User Rate


1. TCHF Any EDGE 9600 8 bit data file RAH-Hopping 2. TCHD Any 14400 7 bit ASCII BB-Hopping

3. TCHD1 Any EDGE 14400 8 bit data file RAH-Hopping 1 Call should be made on BCCH and Non BCCH TRX

5.5 Group 3 Fax via SDCCH

Purpose:

The purpose of these test cases is to verify that single timeslot transparent data channels for Group3 fax can be activated from SDCCH channels, different user data rates are supported, on air data rate can be changed due to fax protocol speed reductions and that multi page images can be transferred.

Note 29. The maximum receive rate is set as defined for the terminating sources

Test Tools Required: FAX Setup, PSTN Setup

Input Expected Output Calls are established using minimum call repetition criteria.

All calls are established successfully. Where the originating user rate is greater than terminating max RX rate, fax protocol negotiates the speed down. This can be seen in the Mode Modify message of the A-bis trace.

DN0694168 Issue 2-0


Input Expected Output When call is established, a multi page test fax image is transmitted.

The received image is compared to the original for correctness.

Case Ref.


BTS Configuration

Originating user rate

Terminating Max RX rate

Hopping Mode

1. TCHF Any EDGE 9600 2400 RAH-Hopping

2. TCHF Any 9600 4800 BB-Hopping

6. MULTISLOT DATA CALL SETUP

6.1 Non-Transparent Data via SDCCH

Purpose:

The purpose of these test cases is to verify that Multislot Non-Transparent data channels at 9600 & 14400 rates can be activated from SDCCH channels, different user data rates are supported, and 7 & 8 bit data can be transferred at the expected data rate.


Input Expected Output The site is configured as per the BTS configuration defined.

The site comes up to “WO” state with no active alarms except “7801: MMI CONNECTED TO BASE STATION: Local MMI Connected”.

Each test case is performed using a mixture of originating / terminating sources (MS – PSTN, MS – MS, PSTN-MS). Calls are established using minimum call repetition criteria. For test cases 2 & 3: Make data call on BCCH & Non BCCH TRX respectively. At BSC, PMAX and PMIN should have different values.

All calls are established and held until user terminates the call. For test cases 2 & 3: Data call is established on BCCH & Non BCCH TRX respectively.

When data call is established, a data packet of at least 200kb is transferred from originating to terminating MS and vice-versa. (A file of 1Mb is transferred at least once during in each case) Data packet type is specified in each case and transferred using 7-bit ASCII via Raw ASCII protocol and 8-bit data file by Z-modem protocol.

Data can be sent and received in both directions with reliable user data rate. In addition there should be no bit errors on user data.

DN0694168 Issue 2-0


Input Expected Output The A-bis TRX signalling links are followed during the test. For test case 2 & 3 also observe the ‘power level’ value in ‘BS POWER CNTL’ parameter and the DL power reported in the MEASUREMENT RESULT

A-bis Measurement Result message values for RX Qual in both uplink and downlink and uplink FER, in laboratory conditions is predominantly 0. For test cases 2 & 3, ‘Power level’ value in ‘BS POWER CNTL’ and the average DL power reported in the MEASUREMENT RESULT should be same. For Multislot call, measurement reports shall be sent for all the time slots used in uplink data transfer. A-bis RF RES IND message for a reserved TCH timeslot shall include the active interference measurement when defined as non-transparent data activation

Case Ref.


Configuration used

TS used / User rate


1. TCHD 4 TRX Sector (2 BB2F with 2 TSxA and 2 TSxB)

2 TS / 9600 7 bit ASCII BB-hopping

2. TCHF Any configuration EDGE HW

2 TS / 14400

8 bit data file

RAH-hopping

3 TCHF Any configuration GSMHW

2 TS / 14400

8 bit data file

RF-hopping

4 TCHF Any configuration GSM HW

2 TS/9600 8 bit data file

RF-hopping

5 TCHF Any configuration EDGE HW

3+1 TS / 9600

7 bit ASCII RF-hopping

6 TCHF1 Common BCCH 2+2 configuration EDGE HW

3+1 TS / 14400

8 bit data file

RAH-hopping (BTS1), non-hopping (BTS2)

7 TCHF2 Use configuration as in Figure 3

3+1 TS / 14400


8 TCHF2 Use configuration as in Figure 1

3+1 TS / 14400


1 Data Transfer is done both in BCCH and non BCCH BTS of common BCCH segment. BTS SW Packet type is A5/0 2 Data transfer is done both in master and slave BTS of multi BCF segment. BCCH is on Talk Family BTS

7. SHORT MESSAGE SERVICE

7.1 Originating & Terminating SMS on SDCCH

Purpose:

The purpose of this test case is to verify that SMS of various lengths can be originated and terminated using SDCCH channels.

Test Tools Required: Fading Simulator.

DN0694168 Issue 2-0


Input Expected Output Create a site with the configuration as mentioned in the test case

Site is in Supervisory state.

Send a SMS from one MS to another MS both MS should be idle mode.

SMS is sent successfully and accurately received.

One message of zero length, one with few characters and one with 160 characters sent one by one

All SMS messages are sent and accurately received via SDCCH.

Monitor the A-bis trace. Check the CP_DATA (SMS).

SMS-SUBMIT and SMS-DELIVER messages are sent correctly.

Case Ref Configuration Used /Site Type

Hopping Mode

1. 4 TRX Sector /Metrosite BB Hopping

7.2 Terminating SMS in Dedicated Mode

Purpose:

The purpose of these test cases is to verify that SMS messages can be terminated using SACCH channels associated with different TCH configurations.

Input Expected Output Create a site with the Configuration as mentioned in the test case

Site is in Supervisory state.

Make the calls as mentioned in the test case. Calls are successful

Send a SMS from an MS in idle mode to a second MS that is in dedicated mode as defined in the test case. The length of the message is defined in the test case.

SMS is sent successfully and accurately received.

Monitor the A-bis trace. Check the CP_DATA (SMS).

SMS-SUBMIT and SMS-DELIVER messages are sent correctly. Messages are delivered via SACCH channels. SMS is sent using SAPI 3.

DN0694168 Issue 2-0


Input Expected Output During the reception of the SMS in speech call, the audio path shall be monitored.

For speech calls the received audio quality is good and without distortion of the original speech during reception of SMS, and there are no additional disturbing sounds heard at the receiving end.

For data calls check the received data at the receiving end.

For data calls the data sent during the SMS receiving are accurate and without errors to user data. (In the case of transparent data there will be a period of corrupted data during the SMS receiving due to frame stealing)

Case Ref.

Call type Configuration Message Length (characters)

Hopping

1. AMR/EFR Common BCCH 2+2 configuration(EDGE) with DFCA, Call is in non-BCCH BTS and MO mobile moving away from BTS at 200 km/hr

50 RF

2. AMR/EFR Common BCCH 2+2 configuration(EDGE) Call is in non-BCCH BTS

50 RAH-hopping

3. HR#0 and HR#1

Any with EDGE Hardware1

100 BB-hopping

4. HR#0 and HR#1

Any2 100 BB-hopping

5. Single TS 9600 NT

Any 50 NONE

6. Multislot 3+1, 14400

Use Any EDGE HW, Non combined BCCH and configure SDCCH on TS7 of BCCH TRX

160 RAH-hopping

7. Any Use EDGE Hardware, and MO mobile moving towards BTS at 200 km/hr

Variable length messages like 0,few and maximum(160)

RAH-hopping

1 Use BTS SW packet type A5/0.Ciphering type at n/w side is A5/0. 2 Use S13 BSC

8. GPRS OPERATION IN BTS

Different states of GPRS MS Idle State: The subscriber is not reachable by the GPRS network. The MS is capable of receiving only Point to Multipoint Multicast (PTM-M) data. The network elements hold no valid context for the subscriber and the subscriber is not attached to the mobility management. To change state to the ready state, the MS must perform a GPRS Attach procedure.

DN0694168 Issue 2-0


Standby State: The subscriber is attached to the mobility management and the location of MS is known on a routing area level. The MS is capable of receiving Point to Multipoint (PTM) data and pages for Point-to-Point (PTP) data. The network holds a valid mobility management context for the subscriber. If the STANDBY timer expires, the MS move to IDLE state and the mobility management context is removed. If the MS sends data, the MS moves to the READY state. The MS can use the Discontinuous Reception (DRX) to save the battery.

Ready State: The subscriber is attached to the mobility management and the location of MS is known on a cell level. The MS is capable of receiving PTM and PTP data. The SGSN can send data to the MS without paging at any time and the MS can send data to the SGSN at any time. The network holds a valid mobility management context for the subscriber. If the READY timer expires, the MS moves to STANDBY state. If the subscriber performs a GPRS Detach procedure, the MS moves to IDLE state and the mobility management context is removed. MS in READY state does not necessarily have radio resources reserved. The MS can use the DRX to save the battery.

Note 30. The GPRS feature is set active for the tested BTS with default GPRS capacity, if not otherwise stated. Also set UL DTX ON if not stated otherwise.

8.1 GPRS synchronisation in BTS

Purpose:

The purpose of these test cases is to verify that all GPRS configured timeslots can be activated and synchronised, and that System Information 13 is scheduled on BCCH.

Test Tools Required: Abis Breaker, Air interface monitoring tool.



GPRS is activated for BTS such that GPRS Channels are allocated primarily from BCCH TRX with the MML Command: ZEQV:BTS=<BTSID>:BFG=1,GENA=Y,CDED=0,CDEF=100,CMAX=100, RAC=<RA_Number>;

GPRS is activated for sector. When GPRS enabled, System Info 13 is scheduled on BCCH transmission.

GPRS is activated for Non- BCCH TRXs such that each of the TRX (Non-DFCA) has at least one Gp configured to it.

GPRS is activated to all Non-BCCH TRXs.

DN0694168 Issue 2-0


Input Expected Output A GPRS Attach and PDP context activation and then packet data transfer is done for BCCH and non-BCCH (Non-DFCA) TRX.

GPRS packet data is sent successfully on BCCH and non-BCCH TRX

Monitor PCU Data Frames for each GPRS Timeslot on Abis Interface through GPA

In PCU Data Frames the values for Coding scheme and Rx level are verified to be reliable. After successful transfer of packets, all timeslots reserved for GPRS send idle PCU Data Frames,

The Air interface is monitored for the scheduling of system information.

All system information sent by BSC is correctly scheduled and broadcast on the BCCH.

Case Ref. BTS Configuration 1. 3 DFCA and 3 Non-DFCA TRX,

Hopping : RF Hopping for Non- DFCA TRXs Hardware Type: EDGE



GPRS is activated for the sector with the MML Command ZEQV:BTS=<BTS ID>,GENA=Y,RAC=<RA_Number.>;

GPRS is activated in the sector

Sector reset is given by BSC( Lock and Unlock of Sector) with MML Command: Lock sector: ZEQS:BTS=<BTS ID>, L; Unlock sector ZEQS:BTS=<BTS ID>, U;

Sector is locked successfully. After Unlock the sector comes up to working state. GPRS synchronisation procedure takes place correctly.

A GPRS Attach is performed and packet data is transferred.

GPRS packet data sent successfully.


In PCU Data Frames the values for Coding scheme and Rx level are verified to be reliable. After successful transfer of packets, all timeslots reserved for GPRS send idle PCU Data Frames,



Case Ref BTS Configuration/ Site Type 2 Any configuration

Hopping: RF Hardware Type: GSM

DN0694168 Issue 2-0




GPRS is activated for BTS such that GPRS Channels are allocated primarily from BCCH TRX with the MML Command: ZEQV:BTS=<BTSID>:BFG=1,GENA=Y,RAC=<RA_Number>;

BCCH TRX has Gp configured to it.

Block LAPD Link of the BCCH TRX with MML Command: ZDTC:<D-Channel Link name>:BL:;

The LAPD link is blocked successfully. Alarm "7705 LAPD FAILURE" is activated at the BSC. The TRX is blocked at the BSC. BCCH reconfiguration takes place. GPRS Synchronisation operates correctly and Gp configures to the new BCCH TRX.

A GPRS Attach is performed and packet data is transferred from the new BCCH TRX



In PCU Data Frames the values for Coding scheme and Rx level are verified to be reliable. After successful transfer of packet all timeslots reserved for GPRS usage achieve synchronisation and send idle PCU Data Frames.



The case is repeated at least once to verify consistency.

Consistent results are observed each time.

Case Ref BTS Configuration 3 Any configuration

Hopping: RAH- Hardware Type: EDGE

4 Any configuration Hopping: RF- Hardware Type: EDGE



DN0694168 Issue 2-0


Input Expected Output GPRS is activated for the sector with the MML Command ZEQV:BTS=<BTS ID>,GENA=Y,RAC=<RA_Number.>;

GPRS is activated in the sector

A GPRS Attach is performed and packet data is transferred.



In PCU Data Frames the values for Coding scheme and Rx level are verified to be reliable.



In between the Data transfer switch off the cabinet for 2 minutes and then switch it on

After the cabinet is switched on the site returns to working state. GPRS Synchronisation procedure takes place correctly

A GPRS Attach is performed and packet data is transferred

GPRS packet data sent successfully





Case Ref BTS Configuration 5 Any configuration

Hopping: RF Hardware Type: EDGE

DN0694168 Issue 2-0




GPRS is activated for Non-BCCH BTS with the MML Command: ZEQV:BTS=<BTS ID>:GENA=Y,RAC=<RA Number.>;

GPRS is activated for Non- BCCH BTS.

A GPRS Attach performed and packet data transferred.

GPRS packet data can be sent successfully

BCCH BTS is reset by BSC (Lock and Unlock of BTS) with MML Command. Lock BTS: ZEQS:BTS=<BTS ID>, L; Unlock BTS ZEQS:BTS=<BTS ID>, U;

BTS is locked successfully. After Unlock the BTS comes up to working state. GPRS Synchronisation procedure takes place correctly

A GPRS Attach performed and packet data transferred.



In PCU Data Frames the values for Coding scheme and Rx level are verified to be reliable. After successful transfer of packet all timeslots reserved for GPRS usage achieve synchronisation and send idle PCU Data Frames,



The case is repeated by giving resets from BTS manager.

After Reset the results are similar to the reset given by BSC.

Case Ref BTS Configuration 6. Common BCCH 2+2 configuration, GP on non-BCCH BTS BCCH BTS-RF

Hopping, Non-BCCH BTS- BB Hopping Input Expected Output

The site is configured as per the BTS configuration defined.


GPRS is activated for both Non-BCCH and BCCH BTS with the MML Command: ZEQV:BTS=<BTS ID>:GENA=Y,RAC=<BSC No.>;

GPRS is activated for Non- BCCH BTS and BCCH BTS.

DN0694168 Issue 2-0


Input Expected Output A GPRS Attach performed and packet data is transferred on both BTSs.


BCCH and Non-BCCH BTS is reset (after the first BTS comes operational) by BSC (Lock and Unlock of BTS) with MML Command. Lock BTS: ZEQS:BTS=<BTS ID>, L; Unlock BTS ZEQS:BTS=<BTS ID>, U;

The site returns to working state. GPRS synchronisation procedure operates correctly each time


GPRS packet data can be sent successfully.





The case is repeated by giving resets from BTS manager.

After Reset the results are similar to the reset given by BSC.

Case Ref BTS Configuration 7. Common BCCH 2+2(Mixed5) configuration

BCCH BTS-RF Hopping, Non-BCCH BTS- BB Hopping



GPRS is activated for BTS such that GPRS Channels are allocated primarily from BCCH TRX with the MML Command: ZEQV:BTS=<BTS ID>:BFG=1,GENA=Y,RAC=<BSC No.>;

BCCH TRX has Gp configured to it.

BCCH reconfiguration is made to occur by breaking PCM1 (ABIS BREAK), which includes GPRS, enabled TRX.

BCCH reconfiguration occurs and the GPRS synchronisation procedure operates correctly.

Data transfer is done when GP timeslot moves to new TRX.


DN0694168 Issue 2-0


Input Expected Output Monitor PCU Data Frames for each GPRS Timeslot on Abis Interface through GPA




To verify consistency repeat the test case for five times.

Consistent results verified.

Case Ref BTS Configuration 8. 4 omni, 2 PCM are used, OMU (64 kbps) and

at least one Non – BCCH TRX on PCM2 and BCCH on PCM1

9. 12 omni, 2 PCM are used, OMU (64 kbps) and at least one Non – BCCH TRX on PCM2 and BCCH on PCM1



GPRS is activated for BTS such that GPRS Channels are allocated on Non-BCCH TRX(Gp no Preference) with the MML Command: ZEQV:BTS=<BTS ID>:GENA=Y,RAC=<RA_Number.>;

GPRS is activated.

Configure Intelligent Shutdown in BCCH shutdown mode with MML command: ZEFM:<bcf>:BBU=BCCH, NTIM=1,BTIM=3;

BCCH shutdown mode is set at BSC.

The mains breakdown alarm is generated Alarm ‘7995:MAINS BREAKDOWN WITH BATTERY BACK-UP’ is reported at the BSC and BTS Manager. The BSC starts the NTIM timer.

After the expiry of NTIM all Non BCCH TRXs are in BL-PWR state and Gp timeslot moves to BCCH TRX. In case of RAH hopping after expiry of NTIM timer site will take a reset.

A GPRS Attach performed and packet data transferred during BCCH shutdown mode

GPRS packet data can be sent successfully during BCCH shutdown mode

DN0694168 Issue 2-0


Input Expected Output Monitor PCU Data Frames for each GPRS Timeslot on Abis Interface through GPA




The mains breakdown alarm is cancelled by MML Command:

The site comes back to operational state. Gp is again configured to a Non-BCCH TRX.







Case Ref BTS Configuration 10. Any configuration

Hopping: RAH Hardware type: EDGE

8.2 Paging Modes

Purpose:

The purpose of the test case is to verify that all GPRS mobile in the Standby state can be paged via CCCH, and that a GPRS mobile in Ready state can be paged for circuit switched connection via SGSN.



GPRS is activated for the sector with the MML Command ZEQV:BTS=<BTS ID>,GENA=Y,RAC=<RA_Number.>; GPRS mobile is in the Ready state

GPRS is activated in the sector. Gp gets configured to the Timeslots

DN0694168 Issue 2-0


Set Network Mode=1 Network Mode is set to mode 1 ,this allows CCCH to be used for GPRS as well as CS paging.

(a) MS is in Packet Idle mode. (No Data transfer is being done) A terminating speech call is made to the mobile. The Gb interface and TRX signalling links at A-bis interface are monitored.

Paging command message is seen for the test mobile in Gb interface traces. At A-bis interface ‘CS-PAGING COMMAND’ is seen. The speech call is established as normal.

(b) MS is in Packet transfer mode. (Data transfer is being done) A terminating speech call is made to the mobile. The Gb interface and TRX signalling links at A-bis interface are monitored.

The speech call is established as normal. After speech call is terminated, the data transfer resumes and transfer is successful. Paging command message is seen for the test mobile in Gb interface traces. At A-bis interface ‘Packet Paging Command’ is seen.

The test is repeated with mobiles having different IMSI.

The output is verified to remain the same.

Case Ref. Configuration Used

Hopping Mode

1. 2+2 Common BCCH

BTS1-RF, BTS 2-BB

8.3 Data transfer

Purpose:

The purpose of these test cases is to verify that GPRS capable mobiles can do attach/detach successfully, PDP context can be established and data can be transferred using coding scheme 1 and 2, reliably in both uplink & downlink on PDTCH, and that a given TS can be used alternatively for circuit switched and packet data.

Test Tools Required: Fading Simulator

Input Expected Output The site is configured as per the BTS configuration defined For test case 5 & 6 : PMAX and PMIN should have different values.


GPRS is activated for BTS using default GPRS capacity with the MML Command: ZEQV:BTS=<BTS ID>,GENA=Y,RAC=<RA Number.>;

GPRS is activated for the BTS

DN0694168 Issue 2-0


Input Expected Output A Circuit switched speech call is established (make sure that Gp time-slot is being used for CS call) and checked in the timeslot to be tested. Abis is monitored during the testing For test case 5 & 6 : Observe the ‘power level’ value in ‘BS POWER CNTL’ parameter and the average DL power reported in the MEASUREMENT RESULT

The circuit switched call is successful For test case 5 & 6 : The circuit switched call is successful.. ‘Power level’ value in ‘BS POWER CNTL’ and the average DL power reported in the MEASUREMENT RESULT should be same.

The call is released. After releasing the call the timeslot regains synchronisation.

Packet data transfer is started using UDP/IP in tested timeslot with coding scheme and direction as defined in the case

GPRS packet data is sent successfully on the tested Timeslot.

Monitor PCU Data Frames for tested GPRS Timeslot on Abis Interface through GPA and verify the user data rate (Repeat the transfer for at least 3 times to get a reliable figure on throughput.)

In PCU Data Frames the values for Coding scheme and Rx level are verified to be reliable The data is transferred with BER of 0%. The expected data rates for the coding scheme are achieved. (CS-1 approx. 9kbit/s per timeslot used and CS-2 is approx. 13.4kbit/s per timeslot)

When the data transfer is complete a circuit switched speech call is again established and verified in the same tested timeslot.

The circuit switch call is successful.. After releasing the call the timeslot regains synchronisation.

Case Ref.

Configuration Used

BCCH Config/ TCH config/ CS Call type

GPRS Enabled TRX (Data Transfer TRX)

Coding Scheme / number of timeslots available

Data transfer direction

Hopping

1. 3 DFCA And 3 Non-DFCA EDGE TRX

MBCCH/TCHF / FR1

All Non-DFCA TRXs(Data Transfer one by one)

CS-1 / 1 TS

Downlink 1Mb file & uplink 500kb file

RF hopping for Non-DFCA TRXs

2. Any Config MBCCH/TCHD / FR

Non-BCCH TRX

CS-1 / 2 TS

Downlink 1Mb file and uplink 500 kb file

None

3. 3 DFCA And 3 Non-DFCA EDGE TRX

MBCCHC/TCHD / FR2

All Non-DFCA TRXs( One by One)

CS-2 / 3 TS

Downlink 1Mb file

RF hopping for Non-DFCA TRXs

4. 4 OMNI GSM/EDGE

MBCCHC/TCHD/ FR

BCCH TRX

CS-2 / 1 TS

Downlink 1Mb file

BB hopping

DN0694168 Issue 2-0


Input Expected Output 5. Any Config with

EDGE HW MBCCH /TCHF / FR

BCCH TRX

CS-2 / 2 TS


RAH-hopping

6. Any Config with GSM HW

MBCCH /TCHF / FR

BCCH TRX and Non-BCCH TRX.

CS-2 / 2 TS


None

7. Any Config MBCCH/TCHF / FR1

Non-BCCH TRX

CS-2 / 2 TS

Five separate uplink and downlink data transfers of 1 MB each are made during the same session.

RF-hopping


MBCCH/TCHF / FR

Non-BCCH TRX

CS-2 / 2 TS


RF-hopping


MBCCH/TCHF / FR2

Non-BCCH TRX

CS-2 / 2 TS


RF-hopping

1 EDAP is configured for all Non DFCA TRXs and for DFCA TRXs set GTRX=N. 2 BSC S13 PCU1

DN0694168 Issue 2-0


8.4 GPRS Data Transfer with changing Time Advance Value.

Purpose:

The purpose of these test cases is to verify that GPRS capable mobiles can do attach/detach successfully, with varying TA.




GPRS is activated for BTS using default GPRS capacity with the MML Command: ZEQV:BTS=<BTSID>,GENA=Y,RAC=<BSC No.>;

GPRS is activated for the BTS

Packet data transfer is started using UDP/IP in tested timeslot with coding scheme and direction as defined in the case. The user data rate is monitored.

GPRS packet data is sent successfully on the tested TimeSlot.

As the transfer of one file completes, promptly begin the transfer of a new file. Repeat this process until the MS reaches a distance of 0 Km (If MS is moving towards the BTS) / 35 Km (if MS is moving away from BTS).Monitor the value of TA on Abis PCU Frames.

Correct TA value is shown in PCU RANDOM ACCESS FRAME and IMMEDIATE ASSIGNMENT COMMAND

Monitor PCU Data Frames for tested GPRS Timeslot on Abis Interface through GPA and verify the user data rate.

In PCU Data Frames the values for Coding scheme and Rx level are verified to be reliable The data is transferred with BER of 0%. The expected data rates for the coding scheme are achieved. (CS-1 approx. 9kbit/s per timeslot used and CS-2 is approx. 13.4kbit/s per timeslot).

Case Ref.

Config Used

BCCH Config/ TCH config

GPRS enabled TRX

Coding Scheme / number of timeslots available

Start Dist./ Speed

Direction Data transfer direction

1. Any Config with EDGE HW BB Hopping

MBCCHC/TCHF

BCCH TRX

CS-1 / 1 TS 35 Km/ 200 km/hr

Towards BTS

Downlink 1Mb file

2. Any Config BB Hopping

MBCCHC/TCHF 1

BCCH TRX

CS-1 / 1 TS 35 Km/ 200 km/hr

Towards BTS

Downlink 1Mb file

DN0694168 Issue 2-0


Input Expected Output 3. Any

Config MBCCH + SDCCH /TCHD 2

Non-BCCH TRX

CS-1 / 2 TS 0 km/ 150 km/hr

Away from BTS

Uplink 500kb file

4. Any Config

MBCCH + SDCCH / TCHD

BCCH TRX CS-2 / 1 TS 0 Km / 100km/hr

Away from BTS

Downlink 1Mb file

5. Any Config

MBCCHC/TCHF

Non-BCCH TRX

CS-2 / 2 TS 35 Km/ 200 km/hr

Towards BTS

Downlink 1Mb file and uplink 500 Kb file

6. Any Config

MBCCHC/TCHF3

Non-BCCH TRX

CS-2 / 2 TS 35 Km/ 200 km/hr

Towards BTS

Downlink 1Mb file and uplink 500 Kb file

1 BSC- S13 PCU 2 2 BSC- S14 PCU 1 3 BSC- S14 PCU 2 8.5 Data Transfer with Radio Link Failure

Purpose:

The purpose of these test cases is to verify that radio link failures are handled correctly during packet data transfer.

Note 31. Very occasionally the A-bis may be broken while the BSC is polling the BTS. This will cause the LAPD to drop and the air interface to be disabled. It may take over 30 sec to recover the site once the A-bis is reconnected. During this time the TCP/IP connection will probably be dropped. It may also be necessary to re-activate the PDP Context.

Test Tools Required: ABIS Breaker



DN0694168 Issue 2-0


Input Expected Output GPRS is activated for BTS with the MML Command: ZEQV:BTS=<BTS ID>,GENA=Y,RAC=<RA_Number.>;

GPRS is activated for the BTS.

All BCCH TRX timeslots are configured to be GPRS enabled. Keep GTRX enabled for BCCH TRX and disabled for rest TRXs with MML command: ZERM:BTS=<BTS ID>,TRX=<TRX NO>:GTRX=Y,; for BCCH ZERM:BTS=<BTS ID>,TRX=<TRX NO>:GTRX=N,; for Non-BCCH TRXs

BCCH TRX Timeslots show Gp configured.

Start packet data transfer (e.g. FTP) as defined in test case. and introduce Abis break for the time mentioned in Test case

The data transfer is interrupted when there are breaks in air or A-bis interface. Resources are released correctly and PCU SYNCHRONISATION Frames are sent after restoration in A-bis'. After the break the data transfer is restarted by the TCP protocol requesting retransmission of data.

Each case is repeated 5 times to verify consistency

Consistent results verified.

Case Ref. Configuration Used


Break in interface

1. Any Config Downlink transfer Air interface broken (attenuated for less than 5 s)

2. Any Config Downlink transfer 1 A-bis link is broken for 1 second and then restored

3. 2 DFCA and 2 Non-DFCA EDGE TRX

Downlink transfer 1

(Gp configured to both Non-DFCA TRXs)

A-bis link is broken for 1 second and then restored

4. Any Config Uplink transfer Air interface broken (attenuated for less than 5 s)

5. Any Config Uplink transfer A-bis link is broken for 1 second and then restored

1EDAP is configured for all TRX

8.6 SMS via packet data

Purpose:

The purpose of these test cases is to verify that with mobile in ready state SMS messages can be sent and received via packet data.



DN0694168 Issue 2-0


GPRS is activated for BTS using default GPRS capacity with the MML Command: ZEQV:BTS=<BTS ID>,GENA=Y,RAC=<RA_Number.>; GPRS mobile is in the Ready state

GPRS is activated for the BTS Gp gets configured to the Timeslots

Different lengths of SMS messages are sent from GPRS mobile to normal mobile and vice versa (a setting needs to be made in the mobile for receiving SMS in Ready state).

The SMS messages to and from the GPRS mobile are routed via the GPRS network, rather than through the MSC to the SMSC.

At A-bis link both GSM A-bis signalling and PCU frames are monitored with GPA

SMS does not get routed on SDCCH channel but through LLC layer on SAPI 7. Message “LLC UI format (8)” has “SAPI:7”

Case Ref.

Configuration Used

Hopping Mode GPRS enabled TRX

1. 3DFCA and 3 Non-DFCA EDGE TRX

RF on Non-DFCA TRXs

All Non-DFCA TRXs

2. Any Config BB-hopping BCCH TRX only



GPRS is activated for BTS using default GPRS capacity with the MML Command: ZEQV:BTS=<BTS ID>,GENA=Y,RAC=<RA_Number.>; GPRS mobile is in the Ready state

GPRS is activated for the BTS Gp gets configured to the Timeslots

Start packet data transfer (in downlink direction) with a GPRS capable mobile

GPRS packet data is sent successfully

When data transfer is ongoing, send an MT-SMS to this mobile from another MS (a setting needs to be made in the mobile for receiving SMS in Ready state)

SMS is received successfully. The SMS messages to the GPRS mobile are routed via the GPRS network, (not through MSC).

Monitor Abis through GPA to verify that SMS has not been via GPRS Network.

SMS does not get routed on SDCCH channel but through LLC layer on SAPI 7.On Abis Message “LLC UI format (8)” has “SAPI:7” After reception of SMS Data transfer should continue.

Case Ref.

Configuration Used

Hopping Mode GPRS enabled TRX

3. Any Config RAH-hopping Non-BCCH TRX only

DN0694168 Issue 2-0


8.7 Cell Reselection and Timing Advance

Purpose:

The purpose of these test cases is to verify that during data transfer mobile can make cell reselection with various timing advance values.

Test Tools Required: Fading Simulator,



Define the Source and Target cells as neighbours to each other The MS is in cabled environment with variable attenuator connected between BTS and MS.

The Test BTS Sites (Source and Target) have been defined as neighbours to each other.

GPRS is activated for with the MML Command: ZEQV:BTS=<BTS ID>,GENA=Y,RAC=<RA_Number.>;

GPRS is activated for the BTS.

A packet data uplink and downlink transfer is source cell as defined in the test case. The Variable attenuator is adjusted such that cell reselection takes place to the target cell during data transfer.

The transfer can be established in the source cell. Data transmission continues after cell reselection and received data is accurate. The user data rate does not degrade after reselection procedure.

The A-bis TRX links and PCU RANDOM ACCESS FRAME frames are monitored on source and target cells. The reselection between cells is made at least 10 times for each test case.

Actual TA value can be seen in the IMMEDIATE ASSIGNMENT message & PCU RANDOM ACCESS FRAME (UL).

Case Ref.

Source-Configuration Used

Target Configuration Used

Source: Band / Hopping / distance / speed/ coding scheme

Target: Band / Hopping / distance / speed / coding scheme

1. Any Config with EDGE HW

Any Config with EDGE HW

900/ BB-hopping / 10- /20Kmph/CS-11

1800/ RAH-hopping / 20- /20Kmph - / CS-1

2. Any Config Any Config 900 / BB-hopping / - / CS-1

1800 / RF-hopping / - /- / CS-1

3. 2 DFCA TRX and 2 Non-DFCA EDGE TRX

Any Config 900 / No hopping / - / CS-2

1800 / BB-hopping / - / -/ CS-2

DN0694168 Issue 2-0


Input Expected Output 4. Any Config Any Config 900 / NAH-hopping /

- / CS-2 1800 / BB-hopping / - / -/ CS-2

5. Any Config Any Config - / Non-hopping / 5km / CS-2 2

- / Non-hopping / 2km / -/ CS-2

6. Any Config Any Config 800/ Non-hopping / 5km / CS-1

1900 / RAH-hopping / 2km / -/ CS-2

1 Data Transfer at least on BCCH TRX 2 Source and target cell have different RA values.

8.8 RF Performance & Power Control

Purpose: To check that EGPRS power level is equal to BCCH power level and speech power level varies on signal strength.

Test Tools Required: Spectrum Analyser



EGPRS is activated for BTS with the MML Command: ZEQV:BTS=<BTS ID>,GENA=Y,RAC=<RA_Number.> ,EGENA=Y; Set BTS to use MCS as specified Disable link adaptation: ZEQV:BTS=##:ELA=0; Set initial coding scheme: ZEQV:BTS=##:MCA=#,MCU=#;

EGPRS is activated for the BTS

Set up speech call and EGRPS data transfer in the specified direction and Timeslots

All calls are established and held until user terminates the call. Data transfer begins. speech calls remain unaffected by EGPRS



Using spectrum analyser monitor power level of EGPRS & speech call timeslots

EGPRS power level is equal to BCCH (i.e. PMAX parameter). Speech call power level is dependent on signal strength. In case speech call is on BCCH TRX, no change in the power of the speech call.

Attenuate UL & DL of speech call. Monitor A-bis EGPRS power level remains equal to BCCH. Speech call power level increases with attenuation. Power control message is seen on A-bis

DN0694168 Issue 2-0


Input Expected Output Terminate the calls Calls get terminated successfully

Case Ref

Config Used

EGPRS enabled TRX

MCS Speech Call Time Slot on Non-BCCH TRX

Speech Call Time Slot on BCCH TRX

EGPRS Data Time Slot on Non-BCCH TRX


1 Any Config

Non-BCCH TRXs

9 0 & 6 None 7 Uplink

2 Any Config

Non-BCCH TRXs

9 0 & 6 None 7 Downlink

3 2 Omni Non-BCCH TRXs

2 any 5 5 & 7 Uplink

4 2 Omni EDGE HW

BCCH and Non-BCCH TRXs ( Make one PS on BCCH TRX also)

2 any 7 7 Downlink

DN0694168 Issue 2-0


9. ADAPTIVE MULTI RATE CODEC

Purpose: The purpose of these test cases is to ensure the functionality of the Adaptive Multi Rate (AMR) Codec feature.

Note 32. Nokia Siemens Networks UltraSite and Nokia Siemens Networks MetroSite EDGE BTSs support FR modes of 12.2, 10.2, 7.95, 7.4, 6.7, 5.9, 5.15 and 4.75 and HR modes of 7.4, 6.7, 5.9, 5.15, and 4.75.

The AMR set includes AMR Codecs, their threshold and hysteresis values and Initial Codec mode used to start the speech coding at call Setup and after handover.

Note 33. Basic AMR set for FR channel on BSC:

Codec Mode

Threshold (C/I)

Hysteresis (C/I)

Lower threshold

(C/I)

Upper threshold

(C/I)

BER (%)

FER (%)

12.2 11 1 11 - 2.97 0.08 7.4 7 1 7 12 6.72 0.15 5.9 4 1 4 8 10.83 0.98 4.75 - 5

Note 34. Basic AMR set for HR channel on BSC:

Codec Mode

Threshold (C/I)

Hysteresis (C/I)

Lower threshold

(C/I)

Upper threshold

(C/I)

BER (%)

FER (%)

7.4 14 1 14 - 0.62 5.9 11 1 11 15 1.08 4.75 - 12

Lower threshold in the tables above means towards more robust Codec (more correction, lower bit rate) and upper threshold means less robust Codec (less correction, higher bit rate).

Note 35. Slow LA can be changed at the BSC using MML command ZEEM. If Fast LA is in use, the Codec mode change is allowed in every second TCH frame (~ 40 ms). With Slow LA, Codec mode changes are allowed on SACCH frame interval (480 ms). (CMI and CMR values are seen on Abis).

Note 36. Channel allocation depends on the parameter Initial AMR Channel Rate. If Any Rate is chosen, the channel rate matches according to the currently used information for channel allocation. If AMR FR is chosen, full rate channel is allocated (if available) despite what information is currently being used. Any Rate is the default rate.

Parameter is valid in call Setup (except FACCH call Setup) and handovers

DN0694168 Issue 2-0


Note 37. Initial Codec mode is used to start the speech coding at call Setup and after handover. If the Initial Codec mode is not defined, it is governed by the following rule:

1 Codec mode, it is the Initial Codec mode

2-3 Codec modes, the Initial Codec mode is the most robust mode of the set with lowest bit rate.

4 Codec modes, the Initial Codec mode is the second most robust mode of the set with second lowest bit rate.

Note 38. Cases are shared between 16 Kbit/s, 32 Kbit/s & 64 Kbit/s TRX signalling links.

Note 39. Default AMR Codec Sets (ACS) is used unless otherwise stated.

Note 40. Default Codecs are:

FR modes - 12.2, 7.4, 5.9, and 4.75

HR modes - 7.4, 5.9, and 4.75.

Note 41. In order to change the value of HRI from 0 to 1, the values for HRT3 > HRT 2 > HRT 1 and HRH 3 >= HRH 2 >= HRH 1

Note 42. BTS commands the MS to apply a particular speech Codec mode in the uplink. The MS can only request BTS to apply a particular speech Codec mode in the downlink because the BTS has an option to override the MS’s request.

9.1 AMR Call Setup via SDCCH and Link Adaptation (LA)

Purpose:

The purpose of these test cases is to verify that correct channel and Codec modes are selected when an AMR call is established via SDCCH, and AMR is capable of adapting its operation according to the prevailing channel conditions and to ensure that AMR Codec mode can be changed correctly during the active call.

Test Tools Required: Variable Attenuator, Signal Generator, and Spectrum Analyser

Input Expected Output Make set up as per the Site configuration. For Case ref no. 1: Set different AMR threshold values for uplink & downlink i.e. FRTD1, FRTD2 & FRTD3 values should be different from FRTU1, FRTU2 & FRTU3

Set up is configured. For Case ref no. 1: Different uplink & downlink AMR threshold values are set.

DN0694168 Issue 2-0


Input Expected Output values respectively.

A call is made via every TS of TRXs. Each call must be held for at least 30 seconds. For Case ref no. 4: Calls should be made such that TSLs 6, 7 of both GSM & EDGE TRXs are occupied. Calls should be made on all TRXs.

Calls are initiated according to parameters defined for the BTS. The quality of the call is good. No disturbing sounds are heard during the speech or silent periods. For case ref no. 4: The quality of the call is good. No disturbing sounds are heard during the speech or silent periods.

The A-bis is monitored during the test A-bis CHANNEL ACTIVATION message includes the used AMR speech Codec and the set of Codec modes. A-bis MEASUREMENT RESULT: When DTX is not used,. the value of RX Qual Full should be monitored and its value varies between 0-7 according the interference. When DTX is used the value of RX Qual Sub should be monitored and its value varies between 0-7 according the interference. MS speed value shall be reported when frequency hopping and uplink DTX are not active; otherwise the value shall be 'Not Valid'. When DTX is ON, invalid FER will be displayed.

During the AMR call, C/I conditions are changed step by step to manipulating the air interface so that the Codec mode is changed. Can be done by generating a constant interference signal using signal generator and then applying variable attenuation. The quality of call is checked during the link adaptation.

When the downlink is degraded, MS requests BTS to apply a new Codec (CMR is seen in the A-bis). When the uplink is degraded, BSC commands MS to apply a new Codec. When the uplink/downlink is attenuated, the Codec mode is changed towards the most robust Codec mode (more correction, lower bit rate). No disturbing sounds are heard when Codec mode change occurs.

The attenuation is decreased step by step When uplink/downlink attenuation is decreased, the Codec mode is changed towards the least robust Codec mode (less Correction, higher bit rate). If Fast LA is in use, the Codec mode change is allowed in every second TCH frame (~ 40 ms). With Slow LA, Codec mode changes are allowed on SACCH frame interval (480 ms). (CMI and CMR values are seen on A-bis)

DN0694168 Issue 2-0


Input Expected Output Case Ref.

Channel Config / Speech Codec

Codec Mode in ACS

Initial Codec Mode

Initial AMR Channel Rate

Hopping Mode

DTX LA

1. TCHD / AFS

12.2, 7.95, 6.7, 4.75

Not defined

FR RAH-hopping

Only Uplink DTX ON

Fast

2. TCHD / AFS

12.2, 7.95, 6.7, 4.75

Not defined

FR Non-hopping

Only Uplink DTX ON

Fast

3. TCHD / AFS

10.2, 7.4, 5.9, 4.75

The most robust mode

Any Rate RF-Hopping

Both Uplink & Downlink DTX ON

Fast

4. TCHD / AFS

10.2, 7.4, 5.9, 4.75

The most robust mode

Any Rate RF-Hopping

Both Uplink & Downlink DTX ON

Fast

5. TCHD / AHS

7.4, 6.7, 5.9

Not defined

Any Rate NAH-hopping

Off Slow

6. TCHD / AHS

7.4, 6.7, 5.9

Not defined

Any Rate RF-hopping

Off Slow

7. TCHD / AHS

7.4, 6.7, 5.9

Not defined

Any Rate BB-hopping

Uplink DTX on

Slow

8. TCHD / AHS

7.4, 6.7, 5.9

Not defined

Any Rate BB-hopping

Both Uplink & Downlink DTX on

Slow

9. TCHD/AHS

7.4, 6.7, 5.9

Not defined

Any Rate Non-hopping

Only Uplink DTX ON

Fast

10. TCHD / AFS1

12.2, 7.95, 6.7, 4.75

Not defined

FR RAH-hopping

Only Uplink DTX ON

Fast

11. TCHD / AHS2

7.4, 6.7, 5.9

Not defined

Any Rate BB-hopping

Uplink DTX on

Slow

1Ensure that voice quality is good. Also listen to speech and verify that there is no distortion 2Make sure that voice quality is good and no additional click sounds are there (except comfort noise)

9.2 AMR call Setup with mobiles moving

Purpose:

The purpose of these test cases is to verify that correct channel and Codec modes are selected when mobile is moving during AMR call and voice quality is good.

Test Tools Required: Fading Simulator, Spectrum Analyser

DN0694168 Issue 2-0


Input Expected Output A multi TRX EDGE sector is used as defined in the channel configuration and hopping mode on a mobile travelling at speeds of 25km/h, 300km/h and 330km/h in each case.

Site is configured as defined.

An AMR call is made, and each held for at least 5 minutes with the MS moving from the BTS starting with 0km and then coming back towards the BTS when distance is 10km. For Case ref no 2: Lock all the timeslots except one on one TRX and make two AHS Call

The call can be established on SDCCH and held until terminated. The received audio quality is good and without distortion. For case ref no. 2: Two AHS calls are successfully made through one unlocked TS of that TRX.

The A-bis Measurement reports are monitored during each case.

Measurement Result message values for RX Qual in both uplink and downlink, and the UL FER shall in laboratory conditions are predominantly of value 0. The A-bis Measurement Result message shows the correct MS speed value when frequency hopping is not active. In cases where the speed cannot be detected the value is reported as 'Not Valid'. The A-bis also indicated the AMR speech Codec in use correctly. The maximum reliable speed detection is approximately 60 km/h (36 miles/h) in GSM 900 and 35 km/h (21 miles/h) in GSM 1800 & GSM 1900.

Case Ref.

Channel Configuration / Speech Codec

No. Of Codec Mode in ACS

Initial Codec Mode

Hopping Mode

LA

1. TCHD / AFS 4 Not Defined No-hopping Slow

2. TCHH / AHS 3 Highest Robust mode

RAH -hopping

Slow

3. TCHD / AHS 2 Highest Robust mode

BB -hopping Fast

4. TCHD / AFS 1 Not Defined BB -hopping Fast

9.3 Packing/Unpacking of AMR calls with Fast LA/Slow LA

Purpose:

The purpose of these test cases is to verify that packing of FR AMR calls to HR AMR calls due to cell load and unpacking of HR AMR calls to FR AMR calls due to call quality works properly.

Note 43. Packing and unpacking the FR and HR calls are performed via intra cell handovers.

DN0694168 Issue 2-0


Note 44. BTS parameters ‘Lower limit for FR TCH resources’ and ‘Upper limit for FR TCH resources’ are set at the BSC with the MML command ZEQM.

Input Expected Output FR AMR calls are made on the BTS (non-hopping) until the number of free full rate resources reduces below the lower limit value.

FR AMR calls are packed to HR AMR calls until the free FR resource increases above the upper limit value. The packing takes place only when the quality of FR AMR calls is above the parameter ‘intra HO threshold Rx Qual for AMR FR’ and the least robust Codec mode is in use.

A conversation is held. During the handovers, both directions of the call are observed for unexpected audio disturbances.

The quality of call is good and there is no additional audio signals noticed (e.g. clicks).

Case Ref BTS Configuration/ TCH Type

LA Type

UL DTX

DL DTX

Hopping Mode

1. Multi sector configuration with TCHD

Fast LA ON OFF Non-hopping

2 Multi sector configuration with TCHD

Fast LA ON OFF Non-hopping

3. Multi sector configuration with TCHD

Fast LA OFF ON Non-hopping

Input Expected Output HR AMR calls are made. Vary the C/I so that the quality of the HR AMR call degrades under the BTS parameter ‘intra HO threshold Rx Qual for AMR HR’.

HR AMR calls are unpacked to FR AMR calls.


The quality of the call is good and there is no additional audio signals noticed (e.g. clicks).


LA Type

UL DTX DL DTX

Hopping Mode

3. Multi TRX/ TCHD Fast ON ON BB-hopping 4 Multi TRX/ TCHD Fast ON ON BB-hopping

DN0694168 Issue 2-0


Input Expected Output FR AMR calls are made via the BTS until the number of free full rate resources reduces below the lower limit value.

FR AMR calls are packed to HR AMR calls until the free FR resource increases above the upper limit value. The packing takes place only when the quality of FR AMR calls is above the parameter ‘intra HO threshold Rx Qual for AMR FR’ and the least robust Codec mode is in use.




LA Type

UL DTX

DL DTX

Hopping Mode

5. Multi Sector /TCHD Slow ON RAH Hopping 6. Multi Sector /TCHD Slow ON ON RF Hopping 7 Multi Sector /TCHD Slow ON ON BB Hopping

9.4 Slow link adaptation with uplink DTX ON.

Purpose: To verify that the codec value does not change more than once within a SACCH frame with slow link adaption.

Note 45. Test cases in this section should be done with following settings:

• Number of codecs in ACS – Any 3 half rate codec modes.

• Initial Codec Mode - Not defined.

• Initial AMR Channel Rate - Any

• DTX - Uplink DTX On

• Link Adaptation – Slow

DN0694168 Issue 2-0


Input Expected Output Setup the BCF as given in configuration Site is in supervisory state.

There are no active alarms except Alarm:7801"MMI CONNECTED TO BASE STATION: Local MMI Connected”"

AHS calls are made via every TRXs. Calls are initiated according to parameters defined to the BTS. The quality of the call is good. No disturbing sounds are heard during the speech or silent periods.[Note 45]

C/I conditions are changed step by step in uplink direction using Signal generator to manipulate the air interface so that the Codec mode is changed. The quality of call is checked during the link adaptation.

When C/I value is decreased the Codec mode is changed gradually towards the most robust Codec mode. When C/I value is increased the Codec mode is changed gradually towards the least robust Codec mode.[Note 35] No disturbing sounds are heard when Codec mode change occurs.

Case Ref. Configuration Hopping Mode 1 2 OMNI TSxB with BB2F [Note 45] BB-hopping

2 2 OMNI TSxA+TSxB with BB2E. 4 half-rate codec modes are defined, Uplink DTX ON and Enable Slow link adaptation.

No

3 2 OMNI EDGE MetroSite with Uplink DTX OFF [Note 45]

No

4 2 OMNI EDGE MetroSite with Uplink DTX ON [Note 45]

No

9.5 Intercell Handover from AMR cell to Non-AMR cell

Purpose:

The purpose of these test cases is to verify that Intercell Handover from AMR cell to Non-AMR cell works properly.

Test Tools Required: Fading Simulator,

Input Expected Output 2 sectors of different BCFs are made neighbours. Sector 1 of BCF1: FRC=12.2,10.2 kbps Sector 2 of BCF2: Non-AMR (FRC&HRC=0) Test case without distance and speed parameters can be executed with zero values. For test case 2 dynamic power control is enabled at the BSC by defining different values of PMAX and PMIN in the power parameters of the BTS

Test set up is configured. Dynamic power control is defined for the test BTS(s).

An AMR call is established and handovers after Handovers are successful; speech quality is

DN0694168 Issue 2-0


Input Expected Output every 30 seconds are performed between the sectors. Perform at least 20 handovers. For case ref no. 2: Handovers should be performed from TSL 4 (other than TSL7 in source cell) to TSL 7 (target cell), use BCCH TRXs of source and Target cell for handover. At BSC, PMAX and PMIN should have different values. Observe the ‘power level’ value in ‘BS POWER CNTL’ parameter and the DL power reported in the MEASUREMENT RESULT

good there is no click sound heard during the handover. The handover from non-AMR cell to AMR cell will result in an AMR call. For case ref no. 2: Handovers are successful; speech quality is good there is no click sound heard during the handover. The handover from non-AMR cell to AMR cell will result in an AMR call. ‘Power level’ value in ‘BS POWER CNTL’ and the DL power reported in the MEASUREMENT RESULT should be same.

A-bis TRXSIG traces are analysed for quality parameter reported in measurement reports.

Reported quality should be of ‘0’ level in lab condition, there shouldn’t be instances of ‘5-6’ quality level in measurement reports.

Case Ref. Source Cell Hopping/distance/speed

Target Cell Hopping / distance/speed

1. BB-Hopping /- /- Non-Hopping /- /-

2. RAH-Hopping /10Km /40Kmph BB- Hopping /5Km /40Kmph

3. RAH-Hopping /10Km /40Kmph Non-Hopping /5Km /40Kmph

4. RAH-Hopping /10Km /40Kmph1 Non-Hopping /5Km /40Kmph 1DL DTX = ON

10. BTS IDLE MODE FUNCTIONS

10.1 SMS Cell Broadcast

Purpose: The purpose of these test cases is to check that SMS cell broadcast messages of various lengths are sent on SDCCH channels successfully.

Note 46. SMS_CBC_USD_IN_BSC feature is set to OFF at the BSC.

Note 47. SMS_CB_DRX_USD_IN_BSC feature is set to OFF at the BSC. Input Expected Output

Configure site as defined in test case. Site comes to supervisory state.

DN0694168 Issue 2-0


Input Expected Output Enable Cell Broadcast in sector using MML command ZEQM:<bts_id>:CB=Y:

Cell Broadcast is enabled in sector.

Create messages with different repetition rates using MML command ZECA:<msg_id>:<msg_code>:4:1,ENG:<repetition rate>;

Messages with different repetition rates are created in the BSC.

Activate these messages at the BSC using MML command ZECS:<message_index>:<bts_id>;

Messages are activated at the BSC.

Observe messages on TRXSIG. ‘SMS BROADCAST REQUEST’ messages are sent at regular intervals on the Abis to BTS.

Introduce disturbance / reset at least 10 times as defined in table.

Message are sent after regular interval and restart after every disturbance/ reset

Case Ref.

Channel configuration Hopping Mode Disturbance / Reset Type

1. MBCCB RAH-hopping BCF reset from BTS Manager

2. MBCCB RF-hopping BTS reset from BSC

3. MBCCHC + SDCCB BB-hopping BCCH Reconfiguration 4. MBCCB RAH-hopping BTS reset from BSC 5. MBCCB No-hopping BCF reset from BTS Manager 6 MBCCHC + SDCCB BB-hopping BCCH Reconfiguration

10.2 RACH and PRACH Success Rate under C/I Conditions

Purpose:

The purpose of this test case is to check that the base station can consistently detect RACH and PRACH bursts from MS in the presence of interference.

Note 48. Use appropriate MS for the different type of RACH: • GPRS PRACH – GPRS capable

• RACH – Circuit Switched capable only

• EGPRS PRACH – EGPRS capable.

Note 49. Limit the MS power for accessing common control and packet control channels using MML command: ZEQG:BTS=<bts id>:TXP1=#,TXP2=#, GTXP1=#,GTXP2=#;

Note 50. Limit the MS power using the MML command: ZEQM:BTS=<bts id>: PMAX1=#,PMAX2=#,PMIN=#;

DN0694168 Issue 2-0


Note 51.

Adjust the power control quality and signal strength parameters using MML commands: ZEUQ:BTS=<bts id>:UUR=#,LUR=#;

ZEUS:BTS=<bts id>:UUR=#,LUR=#;

Note 52. Use the following method to generate RACHs:

• RACH – Use a Load Generator/MAD server to send CHAN REQ for location update.

• PRACH – Send pings in UL direction from MS to IP server. • PRACH – Send pings in DL direction from IP server to MS.

Note 53. Failure rate is calculated as a percentage of the total number of (P)RACH messages: Failure rate = [(location update attempts or Ping attempts) - (P)RACH Messages on Abis]/ (location update attempts or Ping attempts)*100.

Failure rate should be less than 15%

Note 54. EGPRS cannot be used without Dynamic Abis being configured.

Test Tools Required: Signal Generator, Spectrum Analyser, Load Generator

Input Expected Output Configure site of any configuration. Site comes to supervisory state.

Enable EGPRS in the sector. EGPRS is enabled in the sector.

Introduce uplink interference such that C/I = 8 dB.

Interference is introduced and C/I is set.

Use script to send a ping/ location update every 6 seconds. Monitor Abis interface.

Expected message is seen on Abis every 6 seconds.

Run the script for 1 hour. Expected message is seen continuously throughout 1 hour.

Count the number of (P) RACH attempts that did not result in a valid message on the Abis and calculate the failure rate.

Failure rate is within limit.

DN0694168 Issue 2-0


Case Ref.

BCCH Type

Send Method

RACH type Expected Message

A-bis Channel

1. MBCCH UL ping EGPRS P-CHANNEL REQUIRED

TRXSIG of BCCH TRX

2. MBCCHC UL ping EGPRS P-CHANNEL REQUIRED

TRX SIG of BCCH TRX

3 MBCCHC Load Generator

RACH CHANNEL REQUIRED

TRX SIG of BCCH TRX

4 MBCCH BB-Hopping

UL ping PRACH P-CHANNEL REQUIRED

TRX SIG of BCCH TRX

11. SACCH MESSAGES

11.1 SACCH messages during Speech call

Purpose:

The purpose of these test cases is to check that the SACCH messages are exchanged correctly between the MS and the BTS during Speech call.

Test Tools Required: Air interface monitoring Tool

Input Expected Output Configure site as defined in test case. Site is in supervisory state.

Connect the air interface analyser and latch its MS onto the BTS under test

The MS gets latched on successfully.

Make a call to another MS from the air interface analyser phone and keep the call held for about 60 seconds.

The call is successful.

Observe the messages on air Interface analyser. Once the call has been established SI messages for SI5 and SI6 are seen being scheduled alternately every SACCH period on the air interface in the DL direction. In uplink direction Measurement reports are sent in every SACCH period.

Disconnect the call. Define more than 18 neighbours of the same band for the Sector under test. The neighbours need not be in working state.

The call is disconnected. The neighbours can be defined successfully.



DN0694168 Issue 2-0


Input Expected Output Observe the messages on air Interface analyser. Once the call has been established SI messages

for SI5, SI 5bis and SI6 are seen being scheduled on the air interface in the DL direction. The sequence of repetition is SI5, SI6, SI 5bis, SI6 each one 480ms after the other In uplink direction Measurement reports are sent in every SACCH period i.e. 480ms.

Disconnect the call. Delete all the neighbours. Define a neighbour of different band for this BTS

The call is disconnected. The neighbours are successfully deleted. The different band neighbour can be successfully defined.



Observe the messages on air Interface analyser. Once the call has been established SI messages for SI5, SI5bis, SI5ter and SI 6 are seen being scheduled on the air interface in the DL direction. The sequence of repetition is SI5, SI6, SI5, SI6, SI5bis(ter), SI6 each one 480ms after the other In uplink direction Measurement reports are sent in every SACCH period i.e. 480ms.

Disconnect the call. The call is disconnected.

Case Ref.

BTS configuration Call Type

1. 4 TRX Omni/EGSM DFCA enabled sector

AFS/EFR Call is established on BCCH and Non-BCCH Non-DFCA TRX.

2. 4 TRX Omni/EGSM AHS/HR Do this with Rel-6 MSs

3. 4 TRX Omni/EGSM AFS/EFR Do this with Rel-6 MSs

4. 4 TRX Omni/EGSM AHS/HR

12. DEDICATED MODE FUNCTIONS

12.1 SDCCH Handovers

Purpose:

The purpose of these test cases is to verify that SDCCH handovers can be performed successfully.

Input Expected Output Enable SDCCH handover at the BSC SDCCH handover is enabled at the BSC. A call is established in the source cell. A handover is made during SDCCH signalling.

SDCCH Handovers are performed successfully.

DN0694168 Issue 2-0



Configuration Hopping Mode

1. MBCCHC + SDCCH + TCHx RAH-Hopping

2. (MBCCHC + TCHx) (SDCCH + TCHx) 1

BB-hopping

3. (MBCCHC + SDCCH + TCHx) (SDCCH + TCHx)2

RF-hopping

1Call uses SDCCH in second TRX 2Call uses SDCCH defined separately in first TRX

Input Expected Output Enable SDCCH handover at the BSC SDCCH handover is enabled at the BSC. Set Handover parameters LMRG, PMRG & QMRG value 24 each for source and target BTS.

Handover parameters are set for source and target BTS.

A call is established in the source cell. A handover is made during SDCCH signalling.

SDCCH Handovers are performed successfully on target BTS.

Case Ref.

Source cell Configuration

Target cell configuration

Hopping Mode

4. (MBCCHC + TCHx)

(MBCCH + TCHx) (SDCCH + TCHx )

RAH-Hopping

12.2 Intra Cell Handover

Purpose:

The purpose of these test cases is to verify that intra cell handovers can be performed, and that during the handover procedure there is no perceived effect to the end user.

Input Expected Output Use a multi TRX sector. A call is established in the cell as specified in test case. Intra cell handover is triggered in cell at least 50 times during the same call. Additional for Case ref no. 2: Source TRX should be EDGE and target TRX should be GSM.

Handovers can be performed from one timeslot to another in the same cell. If there are assignment failures then the call is not released and failure is recovered by GSM signalling. (There should not be more than 2 assignment failures seen) Additional for case ref no. 2: Handovers are performed correctly.

A conversation is held, during the handovers; both directions of the calls are observed for unexpected audio disturbances. Each case is repeated at least 10 times

The perceived speech is unaffected by the handover procedure and there are no additional audio signals noticed.

DN0694168 Issue 2-0


Case Ref.

Call type / Codec or user rate

Hopping Mode

1. Speech / EFR and AMR BB-hopping

2. Speech / AHS, HR#0 & HR#1

BB-hopping

3. Speech / EFR, AMR 1 Non-hopping

4. Speech / EFR, AMR 3 Non-hopping

5. Common BCCH 2+2/FR, AFS1, 2, 4

RAH-hopping

Input Expected Output Use a multi TRX sector as per the case ref. A call is established in the cell as specified in test case. Intra cell handover between N-TRXs and DFCA TRXs are triggered in cell at least 50 times during the same call.

Handovers are performed from N-TRXs to DFCA TRXs and vice-versa in the same cell. If there are assignment failures then the call is not released and failure is recovered by GSM signalling. (There should not be more than 3 assignment failures seen)

A conversation is held during the handovers; both directions of the calls are observed for unexpected audio disturbances. Call quality parameters are checked before & after handover. Case is repeated at least 3 times.

The perceived speech is unaffected by the handover procedure and there are no additional audio signals noticed. RX Qual in both uplink and downlink, and the UL FER shall be’0’ in laboratory conditions before & after handovers.

Case Ref.


Hopping Mode

6. Speech / EFR RF-hopping

Input Expected Output Use a multi TRX sector. A call is established in the cell as specified in test case. Intra cell handover is triggered in cell at least 50 times during the same call.

Handovers can be performed from one timeslot to another in the same cell. If there are assignment failures then the call is not released and failure is recovered by GSM signalling. (There should not be more than 2 assignment failures seen)

Data call: During the handover procedures a 200 Kb data file is transferred in alternative directions. The transferred data is compared with the original. Each case is repeated at least 10 times.

Data can be sent and received in both directions with the user data rate is achieved on transfers.

Case Ref.


Hopping Mode

7. Single TS Data, NT / 9600

BB-hopping

8. Multislot (2+1), NT 144001 RAH-hopping 1TSC is different to BCC for non-BCCH TRX. 2EDAP is configured for all TRX. 3Execute this test case with BSC S13. 4Execute this test case with STIRC enable.

DN0694168 Issue 2-0


12.3 Inter cell Asynchronous Handover

Purpose:

The purpose of these cases is to verify that inter cell asynchronous handovers can be performed that during the handover procedure there is no perceived effect to the end user, and that neighbour cells can be reported to mobile using adjacent cells or BA lists.


Input Expected Output For each target / source cells there shall be at least 6 valid neighbours available. Cases with out specific Band, distance or speed are made with zero values of distance and speed and with any band. For case ref no 3 Use A5/1 ciphering for source cell and A5/2 ciphering (BTS SW packet CX(M)6 & BSC S13) for target cell.

Site is configured with specifications as defined.

A speech call is established in the source cell as defined in test case and terminated in a separate test cell with same call type Codec or user rate. Inter cell handover are triggered to target cell at least 50 times during the same call. Additional for case ref no 4: Call should be made on BCCH TRX at least.

Handovers can be performed from target to source cell and back. If there are assignment failures, then the call is not released and failure is recovered by GSM signalling. Additional for case ref no 4: Call is successful on BCCH TRX.

On Abis TRXSIG is monitored On A-bis, Handover Detected message has correct value for timing advance and MS speed does not affect call establishment. (Total number of assignment failure or handover failure should not be more than 2.)

A conversation is held; during the handovers both directions of the calls are observed for unexpected audio disturbances.

The perceived speech is unaffected by the handover procedure and there are no additional audio signals noticed. (E.g. clicks). In HR calls there may be a period of silence during handover due to frame stealing.

DN0694168 Issue 2-0




Neighbour Definition

Source: HW type / Band / Hopping / distance / speed

Target: HW type / Band / Hopping / distance / speed

1. Speech / FR, EFR, AMR

BA list EDGE / 900 / BB-Hopping / 5Km / 50 Km/h

EDGE / 1800 / RF- Hopping / 7 Km / 60 Km/h

2. Speech / EFR, AMR1, 2

Adjacent EDGE / 1900 / Non-hopping / - / -

EDGE / 800 / RF- Hopping / - / -

3. Speech / EFR, AMR

Adjacent EDGE / 1900 / Non-hopping / - / -

EDGE / 800 / BB- Hopping / - / -

4. Speech / HR#0 & HR#1, AMR1

BA list GSM / - /- / No-hopping / - / -

EDGE / - / RAH-hopping / - / -

Input Expected Output A data call is established in the source cell as defined in test case and terminated in a separate test cell with same call type Codec or user rate. Inter cell handover are triggered to target cell at least 50 times during the same call. On Abis TRXSIG is monitored

Handovers can be performed from target to source cell and back. If there are assignment failures, then the call is not released and failure is recovered by GSM signalling. On A-bis, Handover Detected message has correct value for timing advance and MS speed does not affect call establishment. (Total number of assignment failure or handover failure should not be more than 2).

During the handover procedures a 200Kb data file is transferred in alternative directions. The transferred data is compared with the original.

Data can be sent and received in both directions with the user data rate is achieved on transfers and no bit errors. In the case of Transparent data there will be a period of corrupted data during the handover (due to frame stealing for FACCH)

DN0694168 Issue 2-0


Case Ref.


Neighbour Definition

Source: HW type / Band / Hopping / distance / speed

Target: HW type / Band / Hopping / distance / speed

5 Single TS Data NT / 14400

Adjacent EDGE / - / RF-hopping / - / 250km/h

EDGE / - / BB-hopping / - / 250km/h

6 Multislot (3+1) NT / 14400

BA list EDGE / 800/ BB-hopping / 10Km / 80 km/h

EDGE / 1900/ RAH-hopping / 10Km / 100 km/h

1Non-BCCH TRX of the source and target cell should have TSC value different from BCC 2Execute this test case with BSC S13.

12.4 Inter Cell Synchronous Handover

Purpose:

The purpose of these test cases is to verify that inter cell synchronous handovers can be performed (with same channel configuration), that the BTS can correctly use the timing advance of the target cell, and that during the handover procedure there is no perceived effect to the end user.


Input Expected Output For each target / source cells there shall be at least 6 valid neighbours available. Cases with out specific Band, distance or speed are made with zero values of distance and speed and with any band.

Site is configured with specifications as defined

A speech call is established in the source cell as defined in test case and terminated in a separate test cell with identical call type / Codec or user rate. Inter cell handover are triggered to target cell at least 50 times during the same call.

Handovers can be performed from target to source cell and back. If there are assignment failures then the call is not released and failure is recovered by GSM signalling (total number of assignment failure or handover failure should not be more than 2).

A conversation is held; during the handovers both directions of the calls are observed for unexpected audio disturbances.

The perceived speech is unaffected by the handover procedure and there are no additional audio signals noticed (e.g. clicks). In HR calls there may be a period of silence during handover due to frame stealing.

DN0694168 Issue 2-0



HW type / Call type Distance / Speed

Source cell: Codec / Band

Target Cell: Codec / band

1. EDGE / Speech 5km / 150km/h

AFS / 900 AHS / 1800

Input Expected Output For each target / source cells there shall be at least 6 valid neighbours available. Cases with out specific Band, distance or speed are made with zero values of distance and speed and with any band.

A data call is established in the source cell as defined in test case and terminated in a separate test cell with identical call type / Codec or user rate. Inter cell handover are triggered to target cell at least 50 times during the same call.

Handovers can be performed from target to source cell and back. If there are assignment failures then the call is not released and failure is recovered by GSM signalling (total number of assignment failure or handover failure should not be more than 2).

During the handover procedures a 200Kb data file is transferred in alternative directions. The transferred data is compared with the original.

Data can be sent and received in both directions with the user data rate is achieved on transfers and no bit errors

Case Ref.

HW type / Call type Source Cell: Codec / Band

Target Cell: Codec / Band

2. EDGE / Single TS Data, NT

9600 / 900 9600 / EGSM 900 (excluding ARFN 0)

3. EDGE / Multi TS Data (3+1), NT

14400 / Any band Same as source

1Non-BCCH TRXs of the source and target cell should have TSC value different from BCC

12.5 Intra-Cell Handovers within a Multi-BCF Segment

Purpose:

The purpose of these test cases is to check that circuit switched calls handover within the same segment: within the same BTS, from BTS to BTS, and from one BCF to another BCF when the synchronisation is either site or BSS synchronisation.

Test Tools Required: Variable attenuator

DN0694168 Issue 2-0


Input Expected Output Create the sites at the BSC as shown in the table and the diagrams below. Make the traffic channels full rate channels (TCHF). Make the default software package DF7.0 on Talk base stations. For case ref no 4: Use GSM configuration in source cell and EDGE configuration in target cell.

Site is configured and in supervisory state.

Define the synchronization chain in the BSC using the MML command: ZEFM:<mm>:CS=BCF,SENA=T,ADD=<s1>; <mm> = Master BCF number <s1> = Slave BCF number For BSS Sync, since LMU is master, so the above command will be modified as ZEFM:<mm>:CS=LMU,SENA=T,ADD=<s1>; <mm> = Master BCF number <s1> = Slave BCF number Physically create and commission the sites.

Synchronisation chain is defined.

Enable intra-cell handovers using the MML command: ZEHG:SEG=<seg num>:EIC=Y,EIH=Y; Set the interval between handovers to 15 seconds using the MML command: ZEHG:SEG=<seg num>:MIH=15,MIU=15; Set the interference threshold very low so that even a small interference signal triggers intra-cell handovers: ZEHI:SEG=<seg num>:IDR=-110,IUR=-110; Set the quality threshold very low so that even a small quality variance triggers intra-cell handovers: ZEHQ:SEG=<seg num>:QUR=1,QDR=1; Ensure there is a very low level of interference on each frequency used by Segment 1 by using another base station set to adjacent channels, transmitting at minimum power with sufficient attenuation.

Intracell handovers are defined. Interference and quality thresholds are defined.

Lock a pair of MS to Segment 1. Establish a speech call between them.

The call sets up successfully.

Monitor the MS displays for the ARFN used. Every 15 seconds the MS handover to a new ARFN within the same Segment. All ARFN within the segment are used.

DN0694168 Issue 2-0


Input Expected Output Monitor the A-bis for ASSIGNMENT COMMANDs and ASSIGNMENT COMPLETE messages. Pay particular attention to handovers from ARFN in the MetroSite to ARFN in the Talk base station and visa-versa.

The ASSIGNMENT COMMANDS can be seen on the A-bis. For each ASSIGNMENT COMMAND there is a corresponding ASSIGNMENT COMPLETE indicating that all the intra-cell handovers are successful (including those between BCFs).

Speak in both directions while intra-cell handovers are taking place.

The speech can be heard clearly in both directions. There are no noticeable clicks, silent periods or other disturbances as the handovers occur.

Disconnect the call. Call is disconnected. Repeat the test on Segments 2 and 3. Segments 2 and 3 behave in the same way as

described for Segment 1. Case Ref.

Call type / Config.

BTS 1

BTS 2

BTS 3 BTS 4

BTS 5

BTS 6

Synchronisation

1. AFS / Figure 1

TRXD (1800)

TRXD TRXD CTGA (PGSM900)

CTGA (EGSM 900)

CTGA Site Sync

2. AMR / Figure 2

TSTB (800)

TSTB TSTB TSPB (1900)

TSPB TSPB Site Sync

3. AMR / Figure 3

TRXD (1800)

TRXD TRXD TSGB (PGSM900)

TSGB (EGSM900)

TSGB

Site Sync

4. AMR / Figure 3

TRXE (1900)

TRXE TRXE TSTB (800)

TSTB TSTB

Site Sync

5. AMR / Figure 5

TSGA (900)

TSGA TSGA TSDB (1800)

TSDB TSDB BSS Sync with SSI

6. AMR / Figure 6

TRXE (1900)


TSTB TSTB BSS Sync

12.6 Inter-Cell Handovers between Multi-BCF Segments

Purpose:

To check that circuit switched calls successfully perform synchronous handovers from one segment to another within the same synchronised chain. To check that circuit switched calls successfully perform non-synchronous handovers to and from cells outside the synchronised chain. To check that calls do not drop when the handovers fail.

Test Tools Required: Variable Attenuator

Successful Handovers

Input Expected Output Create the sites at the BSC as shown in the table and the diagrams below.

Site is configured.

DN0694168 Issue 2-0


Make the traffic channels full rate channels (TCHF). Make the default software package DF7.0 on talk base stations. Define the synchronization chain in the BSC using the MML command: ZEFM:<mm>:CS=BCF,SENA=T,ADD=<s1>; <mm> = Master BCF number <s1> = Slave BCF number For BSS Sync, since LMU is master, so the above command will be modified as ZEFM:<mm>:CS=LMU,SENA=T,ADD=<s1>; <mm> = Master BCF number <s1> = Slave BCF number Physically create and commission the sites.

Site is in supervisory state with no active alarms except “7801: Local MMI connected to the base station”.

Disable intra-cell handovers using the MML command: ZEHG:SEG=<seg num>:EIC=N,EIH=N; Set the interval between handovers to 3 seconds using the MML command: ZEHG:SEG=<seg num>:MIH=3,MIU=3; Set the RX signal level threshold so that a moderate drop in signal level triggers handovers: ZEHS:SEG=<seg num>:LDR=-80,LUR=-80;

Intra cell handovers are disabled. Interval between handovers is set to 3 seconds

Create the Segments as neighbours in a ring as shown in Figure 7 using MML command: ZEAC:SEG=<seg num>:INDEX=<adjacent cell index>:ASEG=<adjacent seg number>:SYNC=Y; Create the one additional BTS as a neighbour as shown in Figure 7 using MML command: ZEAC:BTS=<bts num>:INDEX=<adjacent cell index>:ABTS=<adjacent bts number>; Cable each segment to an MS via variable attenuators. Lock all radio timeslots in BTS 3 and 5 (except the BCCH timeslot). Camp one MS to one of the Segments in the ring. Do not lock the MS using the field test software because it will not be able to see the neighbour.

Make a call from the MS to a PSTN (land-line) telephone.

The call sets up successfully.

DN0694168 Issue 2-0


Monitor the A-bis for HANDOVER COMMANDS and HANDOVER COMPLETE messages. Monitor the MS display for the ARFN being used. Slowly increase the attenuation from the serving cell until a handover is triggered. Return the attenuation to its original value after the handover has occurred.

A HANDOVER COMMAND is seen on the A-bis from the BSC to MS via the source cell. The ARFN shown on the MS changes to the destination cell and a HANDOVER COMPLETE message is sent from the MS via the destination cell to the BSC.

Repeat the process on each cell to hand the call around the ring twice. [Figure 7]

All handovers complete successfully.

Speak in both directions whilst handovers are taking place.

The speech can be heard clearly in both directions. There are no noticeable clicks, silent periods or other disturbances as the handovers occur.

Disconnect the call. Case Ref.

Call type / Config.

BTS 1

BTS 2 BTS 3

BTS 4

BTS 5

BTS 6

Synchronisa-tion

1. - / Figure 1 TRXE (1900)

TRXE TRXE WTFA (800)

WTFA WTFA Site Sync

2. AMR / Figure 2

TSTB (800)

TSTB TSTB TSPB (1900)

TSPB TSPB Site Sync

3. AMR / Figure 4

TRXD (1800)


CTGA (EGSM 900)

CTGA BSS Sync

4. AMR / Figure 5

TSGA (900)

TSGA TSGA TSDB (1800)

TSDB TSDB BSS Sync with SSI

5. AMR / Figure 6

TRXE (1900)


TSTB TSTB BSS Sync

6. AMR / Figure 1

TRXD (1800)


CTGA (EGSM 900)

CTGA Site Sync

Unsuccessful Handovers

Input Expected Output Continuing from the test case above, increase the attenuation in SEGment 3 to the mobile so that the RX level seen by the BTS is approx. –110dBm. It may be necessary to introduce duplexers so that the attenuation is applied in the uplink direction only, so that the MS can still see the target cell.

Begin a call from the MS to a landline telephone in a different part of the ring and hand the call round to SEGment 2.

DN0694168 Issue 2-0


Monitor the A-bis for HANDOVER COMMANDS and HANDOVER FAILURE and RF CHANNEL RELEASE messages. Monitor the MS display for the ARFN being used. Listen to the speech in both directions. Slowly increase the attenuation from the serving cell until a handover is triggered.

The BSC sends a HANDOVER COMMAND to the MS via the source cell. The MS retunes to the new ARFN, but the target cell cannot hear the MS. There is a brief “dead period” in the speech. The MS returns to the source cell and sends a HANDOVER FAILURE message to the BSC. The target cell sends an RF CHANNEL RELEASE message to the BSC. The call does not drop.

Repeat the handover failure process between each of the cells in the ring in turn.

The behaviour described above is repeated.

Disconnect the call. Case Ref.

Config. BTS 1 BTS 2

BTS 3

BTS 4 BTS 5

BTS 6 Synchronisation

7. AMR / Figure 1

TRXD (1800)

TRXD

TRXD CTGA (PGSM 900)

CTGA (PGSM 900)

CTGA Site Sync

8. AMR / Figure 2

TSGA (900)

TSGA

TSGA TSDB (1800)

TSDB TSDB Site Sync

9. AMR / Figure 6

TRXD (1800)

TRXD

TRXD TSGB (PGSM 900)

TSGB (EGSM900)

TSGB

BSS Sync

Purpose: To check that uplink time alignment, after intra BSC handovers of HR calls, on Non EDGE hardware, does not last for a long time

Input Expected Output

Configure the Site as defined in the test case. Set NECI as 1. Make each sector a neighbour of the other.

The site is in supervisory state with no unexpected alarms both at BSC and BTS Manager.

Set up a HR AMR call on one of the sectors. The HR AMR call is successful

Cause the call to be handed over to the other sector as a HR call and observes the TRAU frames for this call on the target sector.

After the handover is complete, the number of TRAU bits reported in the uplink may vary in this manner – 160, 160,159. This pattern if present is repeated for no more than 3 to 4 times. Also no UFEs are seen in the downlink TRAU frames.

Repeat the above two steps for all the AMR HR codecs.

In each case, after the handover is complete, the number of TRAU bits reported in the uplink may vary in this manner – 160, 160,159. This pattern if present is repeated for no more than 3 to 4 times. Also no UFEs are seen in the downlink TRAU frames.

Set up a HR non AMR call on one of the sectors.

The HR non-AMR call is successful

DN0694168 Issue 2-0


Input Expected Output Cause the call to be handed over to the other sector as a HR call and observe the TRAU frames for this call on the target sector.

After the handover is complete, the number of TRAU bits reported in the uplink may vary in this manner – 160, 160,158. This pattern if present is repeated for no more than 3 to 4.


TCH Configuration

Hopping

10 2+2 GSM TCHD RF 11 2+2 GSM TCHH BB

DN0694168 Issue 2-0


Figure 1

BTS1

BTS2

2

3 4 2

3 4

1

BTS4 BB hop

BTS3

BCF 1 BCF 2

SLAVE MetroSite

EDGE

SEGMENT 2

5 6

1

SEGMENT 1

SEGMENT 3

B

TRX colour indicates the SEGment it belongs to.

Talk – Chained MetroSite Multi-BCF

6

7 8

5

B10

11 12

9

B

B = BCCH

BTS5 RF hop

BTS6 No hop

DN0694168 Issue 2-0


Figure 2

SEGMENT 2

SEGMENT 1

SEGMENT 3

1

2

3

4

5

6

BTS1

BTS2

BTS3

MASTER UltraSite

GSM

1

2

3

4

5

6 BTS6 AH hop

SLAVE UltraSite EDGE

BTS5 BB hop

BTS4 RF hop

BCF 1 BCF 2


UltraSite - UltraSite Multi-BCF

B = BCCH

B

B

B

DN0694168 Issue 2-0


Figure 3

BTS1

BTS2

2

3 4

BTS3

BCF 1

MASTER Talk GSM

SEGMENT 2

5 6

1 SEGMENT 1

SEGMENT 3

1

2

3

4

5

6 BTS6 AH hop


BTS5 RF hop

BTS4 BB hop

BCF 2

B

B

B


Talk - UltraSite Multi-BCF

B = BCCH

DN0694168 Issue 2-0


Figure 4

BTS1

BTS

2

3 4 2

3 4

1

BTS4 RF hop

BTS3

BCF 1 BCF 2

SLAVE Talk GSM

SLAVE MetroSite

EDGE

SEGMENT 2

5 6

1

SEGMENT 1

SEGMENT 3

B


LMU Talk Chained MetroSite Multi-BCF

6

7 8

5

B10

11 12

9

B

B = BCCH

BTS5 No hop

BTS6 BB hop

LMU MASTER

DN0694168 Issue 2-0


Figure 5

SEGMENT 2

SEGMENT 1

SEGMENT 3

1

2

3

4

5

6

BTS1

BTS2

BTS3

SLAVE UltraSite

GSM

1

2

3

4

5

6 BTS6 BB hop


BTS5 RF hop

BTS4 AH hop

BCF 1 BCF 2


LMU UltraSite - UltraSite Multi-BCF

B = BCCH

B

B

B

DN0694168 Issue 2-0


Figure 6

BTS1

BTS2

2

3 4

BTS3

BCF 1

SLAVE Talk GSM

SEGMENT 2

5 6

1 SEGMENT 1

SEGMENT 3

1

2

3

4

5

6 BTS6 RF hop


BTS5 BB hop

BTS4 No hop

BCF 2

B

B

B


LMU Talk - UltraSite Multi-BCF

B = BCCH

DN0694168 Issue 2-0


Figure 7

BTS3

BTS1

BTS6

BTS5

BTS2

BTS4

TS locked

TS locked

BTS7

SEGMENT 1

SEGMENT 2

SEGMENT 3

Extra BTS, separate from synchronised chain. Neighbour of SEG 1.

Neighbour of BTS 7

Neighbour of SEG 2

Neighbour of SEG 3

Ring of Adjacent Cells / Segments

DN0694168 Issue 2-0


12.7 Automatic Link Adaptation

Purpose:

The purpose of these test cases is to verify that during a single timeslot or Multislot call the rate of each channel can be modified as commanded from BSC and there are no errors on user data during adaptation.

Test Tools Required: Signal generator

Input Expected Output Use a multi TRX configuration. For case ref no. 2: Make calls on BCCH & Non-BCCH TRX both.

Data Call is established between MS and PSTN in source cell as specified in test case (calls are not established MS to MS as user data rate will be capped at the lowest Link rate).

The call can be established in source cell as specified in test case

A data file is transferred first from A to B and then B to A for each test case. At the receiving end of the data packet the transfer data rate is monitored.

The achieved CS data transfer rate of user data reflects the channel type used at the time of the CS data transfer

By using BSC parameters and degrading the air interface conditions, the link adaptation takes place to the target data rate. The air interface conditions are changed to return to the source cell user rate. Use command ZEUG to enable ALA This change between data rates is made at least 10 times during the file transfer. The test case is repeated for 3 different TS.

When link adaptation occurs there are no errors in the received data and the achieved user data rate changes to the new rate. For Single-slot data connection, a CHANNEL MODE MODIFY msg and for Multislot connection, a CONFIGURATION CHANGE COMMAND msg is seen on the A-bis indicating the new data rate. The same timeslot(s) are used through the Automatic Link adaptation procedure.

Case Ref.

Source Cell Call type / data rate Target Call type / data rate

Hopping

1. Single TS, NT 14400 Single TS, NT 9600 RAH-hopping

2. Single TS, NT 14400 Single TS, NT 9600 Non-hopping

3 Multislot (2+2), NT 14400 Multislot (2+2), NT 9600

BB-hopping

DN0694168 Issue 2-0


12.8 Multislot Upgrade / Downgrade

Purpose:

The purpose of these test cases is to verify that during a single timeslot or Multislot call the rate of each channel can be modified as commanded from BSC and there are no errors on user data during upgrade/downgrade.

Input Expected Output Use a multi TRX configuration.

Data Call is established between MS and PSTN in source cell as specified in test case.

The call can be established in source cell as specified in test case

A data file is transferred first from A to B and then B to A for each test case. At the receiving end of the data packet the transfer data rate is monitored.

The achieved CS data transfer rate of user data reflects the channel type used at the time of the CS data transfer.

By using BSC parameters and controlling the traffic loading on the TRX resource upgrading / downgrading take place. Use command ZEQX to modify parameters HCL/HCU for upgrade/downgrade. Resource upgrade and downgrade is done at least 10 times during file transfer.

When resource upgrade (from source to target call) / downgrade (from target to source) occurs there are no errors in the received data.

Case Ref.

Source Cell Call type / data rate

Target Call type / data rate

Table 6. Single-slot (1+1) / NT 9600 Multislot (2+2) / NT 9600

2 Multislot (2+2) / NT 14400 Multislot (3+1) / NT 14400

12.9 DTX Applied to Speech & Data calls

Purpose:

The purpose of these test cases is to verify that DTX (UL & DL) can be applied to speech & data calls, that the A-bis messages Measurement Reports and RF RES IND indicate the appropriate values during DTX usage, and there is no audio disturbances heard or loss of speech or data loss during DTX operation transition.

Test Tools Required: FAX Setup

Input Expected Output Test cases are performed with the B-subscriber on a different cell as A-subscriber, but same Codec or a PSTN connection.

DN0694168 Issue 2-0


Input Expected Output A voice call is made between A and B, the A-subscriber is made to perform asynchronous inter cell handovers every 15 seconds. The test case last for at least 10 minutes. For case ref. no 4: Make call on BCCH TRX. At BSC, PMAX and PMIN should have different values. Observe the ‘power level’ value in ‘BS POWER CNTL’ parameter and the average DL power reported in the MEASUREMENT RESULT For case ref. no 5: Make calls on Non- BCCH TRXs. At BSC, PMAX and PMIN should have different values. Observe the ‘power level’ value in ‘BS POWER CNTL’ parameter and the average DL power reported in the MEASUREMENT RESULT

The call can be established and held for the duration of the test case. Asynchronous inter cell handovers are successful. For case ref. no 4: Call is successful in BCCH TRX. ‘Power level’ value in ‘BS POWER CNTL’ and the average DL power reported in the MEASUREMENT RESULT should be same. For case ref. no 5: Call is successful on Non-BCCH TRX. ‘Power level’ value in ‘BS POWER CNTL’ and the average DL power reported in the MEASUREMENT RESULT should be same.

For testcase 3: Apply continuous music as input to Ms which is used for MO call. The A and B subscribers cycle between conversation & periods of silence. The received audio is monitored for speech intelligibility, comfort noise when DTX is applied, missing speech at start of conversation following DTX usage & any disturbing audio disturbances.

During the test there are no audio disturbances heard at either A or B subscriber during transition periods of DTX usage or during handover.

A-bis Measurement Result message values when DTX is not used for RX Qual Full & Sub in both uplink and downlink shall in laboratory conditions is predominantly of value 0. When DTX is applied then values of RX Qual Full should be 7 & RX Lev Full tends to be -110dB, The RX qual Sub shall in laboratory conditions be predominantly of value 0. MS Speed value shall be reported when frequency hopping and Uplink DTX are not active; otherwise the value shall be 'Not Valid'. A-bis RF RES IND message shall include the interference measurement for a reserved TCH (FR /EFR) timeslot. In HR speech channel the interference estimation can be done only of those burst where MS hasn’t send anything i.e. MS is in DTX state

The A-bis TRX signalling link is followed during the test.

When Downlink DTX applied, the BTS shall only stop RF transmission on a non-BCCH timeslot.

DN0694168 Issue 2-0



Codec Type DTX Music feature3 / DTX Mode

Hopping Mode B subscriber

1. FR, AFS,AHS OFF / UL & DL

BB-hopping MS

2. EFR, AFS,AHS OFF / UL RF-hopping MS

3. AFS, AHS ON / UL & DL

RAH-hopping PSTN

4. AFS, AHS - / UL & DL RAH-hopping MS

5. AFS, AHS - / UL & DL No-hopping MS

1A AFS,AHS,EFR2 -/ UL BB-hopping MS

Input Expected Output A data call is made between A and B, the A-subscriber is made to perform asynchronous inter cell handovers every 15 seconds. Data file to be transferred at least 5 times for each test case.

The call can be established and held for the duration of the test case.

A 50kb data file is repeatedly sent from A to B and then B to A during the test case. For Group 3 fax call, a multi page document is sent and received.

The data is received accurately. DTX can be seen to be used during periods when no data was sent / received. DTX cannot be applied to a transparent data / fax call even when set active in the MS & BTS. The DTX flag in the Measurement Report not used and RF transmission is made in all GSM frames. A-bis Measurement Result message values when DTX is not used for RX Qual Full & Sub in both uplink and downlink shall in laboratory conditions is predominantly of value 0. When DTX is applied then values of RX Qual Full should be 7 & RX Lev Full tends to be -110dB, The RX qual Sub shall in laboratory conditions be predominantly of value 0. MS Speed value shall be reported when frequency hopping and Uplink DTX are not active; otherwise the value shall be 'Not Valid'. A-bis RF RES IND message shall include the interference measurement for a reserved TCH (FR /EFR) timeslot.

The A-bis TRX signalling link is followed during the test.

When Downlink DTX applied, the BTS shall only stop RF transmission on a non-BCCH timeslot.

DN0694168 Issue 2-0



Codec/Data Type

DTX Mode Hopping Mode B subscriber

6. Single, NT 9600

UL & DL NAH-hopping MS

7. Multislot (2+2), NT 9600

UL BB-hopping MS

8. Multislot (2+2), NT 9600 1

UL BB-hopping MS

1Execute this test case with BSC S13. 2Use 7270 , E70 MS and 6220 MS (MS can be used for subscriber A or B.Different MSs have to be used for different codecs) 3“DTX music” is a feature at BSC so should be enabled at BSC end.

12.10 Measurement Pre-processing

Purpose:

The purpose of these test cases is to verify that BTS can pre-process the measurement reports as defined by BSC parameter, and that the numbering sequence of the A-bis Measurement Reports are always consecutive.

Note 55.

For each measurement period, UL_FER is reported, when pre-processing is used. I.e. if pre-processing =3 then there will be 3 values of UL_FER.

Input Expected Output Each test case is repeated with the BSC parameter BMA set to 1, 2, 3 & 4.

A call is established and the A-bis Measurement Report numbers are observed. Calls are held until the Measurement report values recycle back to 0. The UL FER values are also monitored.

The measurement report numbers are always consecutively reported (i.e. 0, 1, 2, 3…254, 255, 0…) and the interval of sending on the A-bis is 480mS * BMA value. The UL FER values are not averaged for each measurement period. For AMR calls first and last Codecs used, seen correctly.

Case Ref.

Call type

1. FR

2. HR#0 & HR#1

3. AMR (AFS with 4 Codecs)

4. Multislot data (2+2), NT 14400

DN0694168 Issue 2-0


12.11 Mobile Speed Handling

Purpose:

The purpose of these test cases is to verify that the Mobile Speed Detection works correctly.


Note 56. Mobile Speed Detection can only be seen on A-bis Trace when uplink DTX and hopping is not in use.

Input Expected Output A multi TRX sector is used with channel configuration and hopping mode, specified as per test case.

The call can be established on SDCCH and held until terminated.

Mobile travelling at speeds of 5km/h, 30km/h, 80km/h and 200km/h in each test case.

A call is made as mentioned in the test case and each call held for at least 5 minutes with the MS moving to / from the BTS starting with TA values of 0 & 15km.

For speech calls received audio quality is good and without distortion. In case of data calls, data can be sent and received in both directions with the user data rate is achieved on transfers.

On A-bis TRX signalling are monitored during each test case. Note: For test case 1& 3, Setup a call while MS is travelling at 330Km/h. Only EDGE h/w to be used for these test cases.

The A-bis Measurement Result message shows the correct MS speed value when frequency hopping is not active. In cases where the speed cannot be detected the value is reported as 'Not Valid'. The maximum reliable speed detection is approximately 60 km/h (36 miles/h) in GSM 900 and 35 km/h (21 miles/h) in GSM 1800 & GSM 1900.

Case Ref.

Channel Configuration / Speech Codec Hopping Mode

1. MBCCH+SDCCH+TCHF/EFR & AMR Non-Hopping

2. MBCCH+TCHF/ Single-slot data, NT 9600 RAH-Hopping

3. MBCCH+TCHF/ Multislot data (2+2), NT 14400 BB-hopping

DN0694168 Issue 2-0


12.12 Interference with HR channel when high traffic

Purpose: The purpose of the test cases is to verify that interference values are reported correctly for half rate/full rate traffic channels.

Note 57. A signal generator is needed to introduce interference in the uplink frequency.

Note 58. Uplink DTX is switched off/on using ZEQM:<bts no>: DTX=1(ON) or 2 (OFF)

Note 59. Ensure that no ‘real’ interference is present on the frequency used.

Note 60. Configure TS0 as MBCCH, TS1 as SDCCH, TS2-7 as TCHD

Input Output

Configure the BCF as given in the table. The base station is in Supervisory with no active alarms

High traffic is generated through short duration calls for 2 Hours using a MCG or 10-12 phones. All these calls are HR. For testcase3: Make only one pair of call

Calls are successful. Call is successful.

Monitor the interference (I LEV) on the Traffic channels using MML command ZERO Monitor the RF Resource Ind messages on the Nethawk Alternatively interference can be checked by using the BSC Radio Measurement Monitoring Service Terminal command

No interference is present in the uplink path. In RF Resource Ind message no Interference is reported.

A signal generator is used to introduce interference in the uplink frequency path. Monitor the interference level as in step above.

Interference value greater than ‘0’ is reported on the MML (ZERO Command) and in the RF Resource Ind message, depending on the level of the interference introduced.

Case Ref. BCF Configuration Uplink DTX 1 1 Omni EDGE OFF 2 1 TRX EDGE OFF 3 2 OMNI EDGE with BB Hopping OFF

Note 61.

Configure TS0 as MBCCHC TS1 as SDCCB, TS2-7 as TCHH for TRX1

DN0694168 Issue 2-0


TS0-7 as TCHH for TRX2 for test cases 4 and 5.

Configure TS0 as MBCCHC TS1 as SDCCB, TS2-7 as TCHD for TRX1

TS0-7 as TCHD for TRX2 for test case 6.

Input to Verify the Correction Expected Output

Configure the BCF as given in the table. The base station is in Supervisory with no active alarms

High traffic is generated through short duration calls for 1 Hour using a MCG or 14-16 phones and 10 continuous calls during the whole test.

Calls are successful.

Monitor the interference (I LEV) on the Traffic channels using MML command ZERO Monitor the RF Resource Ind messages on the Nethawk Alternatively interference can be checked by using the BSC Radio Measurement Monitoring Service Terminal command

No interference is present in the uplink path. In ‘RF Resource Ind’ message no Interference is reported.

A signal generator is used to introduce interference in the uplink frequency path. Monitor the interference level as in step above.

Interference value greater than ‘0’ is reported on the MML (ZERO Command) and in the RF Resource Ind message, depending on the level of the interference introduced.

Stop the interference in the uplink frequency path. Monitor the interference level as in step above.

No Interference is reported on the MML (ZERO Command) and in the RF Resource Ind message, depending on the level of the interference introduced.

Case Ref. BCF Configuration Uplink DTX Call Type 3 2 Omni GSM OFF AHS 4 2 Omni GSM OFF AHS 5 2 Omni Hybrid ON AFS, FR EFR, HR,

AHS 6 2 Omni EDGE ON AFS, FR EFR, HR,

AHS 7 2 Omni Hybrid with BB Hopping ON AFS, FR EFR, HR,

AHS 12.13 BTS Power Control

Purpose:

The purpose of these cases is to verify that BTS power control commands from the BSC is used on BCCH and non-BCCH TRX configurations.

Test Tools Required: Data cart, Spectrum Analyzer

DN0694168 Issue 2-0



BTS Power control settings in BSC are that BCCH power level is set to maximum, and the whole of the dynamic power control range is available. A timeslot is used as defined in the channel type, hopping mode and TRX type.

BTS Power control settings are set.

The BTS to MS RF path is not attenuated; forcing the BSC to decreases BS power over the dynamic control range

The call can be established and held until terminated. For speech the audio quality is good and without distortion, and for multislot calls the data is received accurately.

.The BTS to MS RF path is then attenuated so the BSC increases the BS power over the dynamic control range. Use spectrum analyser to measure BCCH output power.

The BCCH transmitted RF power will be BSC PMAX value for all timeslots.

If baseband hopping is being used in the BTS, the BSC sends the BS POWER CNTL commands also to the BCCH transceiver.

The A-bis BS POWER CNTL & Measurement Report messages and RF power level of TX Transmission of BTS are monitored during the whole test case.

For non-BCCH channel activation the BS RF Power reflect the last BS POWER CNTL from the BSC. The BTS reports in the Measurement report the last used BS Power level.

Case Ref. Channel type Hopping Mode / TRX Type 1. FR or EFR Non-hopping / BCCH & non-BCCH TRX

2. FR or EFR BB-hopping / BCCH TRX

3. FR or EFR BB-hopping / Non-BCCH TRX

4. FR or EFR RAH-hopping /Non-BCCH TRX

5. HR#0 & HR#11 RF-hopping / non-BCCH TRX 1Two HR calls are established in on same timeslot. The call using HR#0 RF path is attenuated so the BS Power control algorithm keeps RF transmission at maximum.

13. RECOVERY FROM FAULT CONDITIONS

13.1 TRAU Frame Breaks

Purpose:

The purpose of these cases is to verify that TRX can detect the TRAU frame synchronisation loss and can report it to BSC with A-bis message 'Error Ind'. Also check that on removal of fault, speech calls are possible.

DN0694168 Issue 2-0


Input Expected Output The BSC parameter 'number of ignored transcoder failures' (ITCF) is set value 0. To modify ITCF use MML Command: ZEEQ:ITCF=0;

A call is established. Then on the A-bis interface the TRAU frame link of active call is broken as defined in the test case. A-bis TRX link is monitored. A Talk Family BTS can be used to break the TRAU frames.

When the TRX detects frame synchronisation lost, the A-bis message 'Connection Fail' with reasons 'Remote Transcoder Failure' is sent to BSC. The call is released by BSC after receiving this message.

A call is re-established on the same timeslot after the link has been restored.

The call can be re-established on the previously failed timeslot

Case Ref.

Call Type A-bis TRAU frame link broken

1. FR Both directions

2. HR#0 & HR#1 Downlink direction only

3. Single-slot data, NT 9600 Uplink direction only

4. Multislot data (3+1), NT 14400 Both used TS in both directions

5. AMR (AFS, with four Codecs) Both directions

6 AHS/GSM with BB2A having SDIBA ASIC

Both directions

14. SEPARATE RLT PARAMETER FOR AMR AND EFR

BTS and MS use the Radio Link Timeout –value received in SI6 –message to supervise the radio link. The value sets the limit for the amount of unsuccessfully decoded SACCH frames. Once the limit is reached the channel is released.

Separate radio link timeout parameters for AMR and EFR –feature enables the BSS to use a different RLT value for AMR calls. RLT for AMR calls can be set to a higher value than the RLT for other connections. The feature name also refers to EFR – however, BSC implementation will not support setting a separate RLT for EFR calls. BTS implementation must not take into account the connection type. It shall always assume that BSC is sending a connection specific RLT if connection specific SI6 is received. So, in BSC there will be a separate parameter (ARLT) where user can set RLT value to be used with AMR calls. For all other channels BSC will use the existing RLT parameter value.

DN0694168 Issue 2-0


Note 62. Both EDGE and GSM TRXs will support this feature.

Note 63. Radio link timeout value can be checked using EQO:BTS=bts_no:RAD; command for non-AMR calls.

Note 64. For AMR calls a new parameter ARLT (AMR radio link timeout is added in BSC 11.5). It can be viewed using following command

Note 65. ZEQO: BTS=bts_no: AMR;

To modify the value of ARLT use following command

ZEQY: BTS= bts_no: ARLT=xx;

Range of RLT and ARLT is from 4 to 64.

Note 66. Radio Link timeout is simply the incapacity to decode the SACCH RLT/ARLT times on Layer 1. This definition applies to both uplink and downlink. For SACCH messages that cannot be read, the channel decoder sets the BFI flag to 1. When a radio link failure on Layer 1 is detected on a dedicated channel (TCH and SDCCH), the BTS sends a CONN_FAIL message with cause 1 = radio link failure to the BSC.

Note 67. During call establishment Radio Link Timeout value is received in SI6 message in CHANNEL ACTIVATION message to supervise the radio link as defined in BSC.

Note 68. If SI6 is not received in CHANNEL ACTIVATION then TRX specific RLT value is used as a default value received during TRX initialisation.

Note 69. The term “High Interference” used in Test cases means that MS/BTS is not able to decode the SACCH messages in DL/UL direction e.g. Interference greater than Signal level.

Note 70. For IBHO MSC version M12 is required.

Note 71. All AMR test cases to be done with fast LA enabled unless otherwise stated. Fast LA can be changed at the BSC using MML command ZEEM.

Note 72. Default AMR Codec Sets (ACS) as defined in BSC is used unless otherwise stated.

DN0694168 Issue 2-0


Default Codecs are:

FR Codec modes - 12.2, 7.4, 5.9, and 4.75

HR Codec modes - 7.4, 5.9, and 4.75. 14.1 Radio link timeout with speech call

Purpose: The purpose of this test is to verify that Radio link timeout occurs as defined by ARLT/RLT parameter in BSC with speech call(s) during active phase.

Test Tools Required: Signal Generator, Spectrum Analyser, Screened Box and Fading Simulator

Input Expected Output Set RLT=20 and ARLT=24 at BSC [Note 63and Note 64]. Use MML command ZEHG to disable intracell HO by setting EIC=N, and EIH=N

RLT and ARLT parameters are set successfully.

Speech calls are made from MS to MS as defined in the test case. Monitor the TRX signalling links during call establishment.

All calls are established successfully. During call establishment Radio Link Timeout value received in SI6 message to supervise the radio link is equal to RLT (for EFR call)/ARLT (for AMR call) value defined in BSC. The received audio shall be good and without distortion of the original speech, and there shall be no additional disturbing sounds heard at the receiving end during speech or silence periods.

Introduce high interference [Note 69] in UL direction on active calls. The A-bis TRX signalling links are recorded during the test

It is observed that as soon as BTS is not able to decode number of SACCH messages as defined by RLT (for EFR/FR/HR call) or ARLT (for AFS/AHS call) parameter on BSC, the BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC. It can be verified from the A-bis traces that radio link timeout occur after (480*RLT) ms for non-AMR call and (480*ARLT) ms for AMR call once High interference [Note 69] is introduced. Calls are released.

DN0694168 Issue 2-0


Input Expected Output Speech calls are made again from MS to MS. High interference [Note 69] is introduced in DL direction.

Call establishment is successful. MS starts sending Measurement Report (with RX QUAL=7) till Radio link timeout occurs. Number of Measurement Reports (with RX QUAL=7) send by Mobile will be equal to RLT (for EFR/FR/HR call) or ARLT (for AFS/AHS call). After radio link timeout MS stops sending Measurement Report i.e. SACCH messages.

The A-bis TRX signalling links are recorded during the test

It is observed that as soon as BTS is not able to decode number of SACCH messages as defined by RLT (for EFR/FR/HR call) or ARLT (for AFS/AHS call) parameter on BSC, the BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC. Calls are released.

Case Ref.

Configuration Channel configuration

Call Type Hopping

1. 2 Omni1 MBCCHC + TCHD

AHS RAH

2. 2 Omni1 MBCCHC + TCHF

EFR and AFS on same TRX (BCCH TRX)

BB

3. 4 Omni, Ecell Config [Note 115]

MBCCHC + TCHF

FR and AFS on same TRX (E-cell TRX)

None

4. 2 Omni1 MBCCHC + TCHF

AFS RF

1Use EDGE HW

14.2 Radio link timeout on TCH for EFR/FR with change of ARLT

Purpose:

The purpose of this test is to verify that Radio link timeout occurs as defined by RLT parameter in BSC with EFR/FR call during active phase and change of ARLT does not impact it.

Test Tools Required: Signal generator, Spectrum Analyser, Screened Box


Set RLT=16 and ARLT=16 at BSC [Note 63] and [Note 64].


DN0694168 Issue 2-0


Input Expected Output Establish MS to MS speech call as defined in the test case and monitor the TRX signalling links.

Call is established successfully. During call establishment Radio Link Timeout value received in SI6 message to supervise the radio link is equal to RLT value defined in BSC. The received audio shall be good and without distortion of the original speech, and there shall be no additional disturbing sounds heard at the receiving end during speech or silence periods.

Introduce high interference [Note 69] in UL direction on active calls such that Radio link timeout occurs for (E)FR call. The A-bis TRX signalling links are recorded during the test

It is observed that as soon as BTS is not able to decode number of SACCH messages as defined by RLT parameter on BSC, the BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC. It can be verified from the A-bis traces that radio link timeout occur after (480*RLT) ms for (E)FR call once High interference [Note 69] is introduced. Call is released.

Set ARLT=32 at BSC. ARLT parameter set successfully.

Establish MS to MS speech call as defined in the test case. Monitor the TRX signalling links during call establishment.

Call is established successfully. Change in ARLT does not have any impact on (E)FR call. During call establishment Radio Link Timeout value received in SI6 message to supervise the radio link is equal to RLT value defined in BSC.

Introduce high interference [Note 69] in UL direction on active calls such that Radio link timeout occurs for (E)FR call. The A-bis TRX signalling links are recorded during the test

It is observed that as soon as BTS is not able to decode number of SACCH messages as defined by RLT parameter on BSC, the BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC. It can be verified from the A-bis traces that radio link timeout occur after (480*RLT) ms for (E)FR call once High interference [Note 69] is introduced. Call is released.

Case Ref.

Configuration


DTX used Call type

1. Any MBCCHC + TCHF

UL and DL both (Calls are on BCCH TRX)

EFR


No (Calls are on Non BCCH TRX) FR

DN0694168 Issue 2-0


14.3 Radio link timeout on TCH for AMR with change of RLT

Purpose:

The purpose of this test is to verify that Radio link timeout occurs as defined by ARLT parameter in BSC with AMR call during active phase and change of RLT does not impact it.



Set RLT=16 and ARLT=16 at BSC [Note 63] and [Note 64]. Use any configuration. Define Codec mode in ACS as given in test case using MML command ZEQY.


Establish MS to MS AMR speech call as defined in the test case and monitor the TRX signalling links.

Call is established successfully. During call establishment Radio Link Timeout value received in SI6 message to supervise the radio link is equal to ARLT value defined in BSC. The received audio shall be good and without distortion of the original speech, and there shall be no additional disturbing sounds heard at the receiving end during speech or silence periods.

Introduce high interference [Note 69] in direction specified in the test case on active calls such that Radio link timeout occurs for AMR call. The A-bis TRX signalling links are recorded during the test. TRAU frames are also monitored during the call.

With interference applied Codec mode is changed towards the most robust Codec mode. Codecs observed are same as defined in the test case. It is observed that as soon as BTS is not able to decode number of SACCH messages as defined by ARLT parameter on BSC, the BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC. It can be verified from the A-bis traces that radio link timeout occur after (480*ARLT) ms for AMR call once High interference [Note 69] is introduced. Call is released.

Set RLT=32 at BSC. Establish MS to MS AMR speech call as defined in the test case.

Change in RLT does not have any impact on AMR call. During call establishment Radio Link Timeout value received in SI6 message to supervise the radio link is equal to ARLT value defined in BSC.

DN0694168 Issue 2-0


Input Expected Output Introduce high interference [Note 69] in direction specified in the test case on active calls such that Radio link timeout occurs for AMR call. The A-bis TRX signalling links are recorded during the test. TRAU frames are also monitored during the call.

With interference applied Codec mode is changed towards the most robust Codec mode. Codecs observed are same as defined in the test case. It is observed that as soon as BTS is not able to decode number of SACCH messages as defined by ARLT parameter on BSC, the BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC. It can be verified from the A-bis traces that radio link timeout occur after (480*ARLT) ms for AMR call once High interference [Note 69] is introduced. Call is released.

Case Ref.

Codec Mode in ACS


DTX used Interference Call Type

1. 10.2, 7.4, 5.9, 4.75

MBCCHC+ TCHF


In UL AFS

2. 7.4, 6.7, 5.9 MBCCHC+ TCHD

No (Calls are on Non BCCH TRX)

In UL AHS

14.4 Radio link timeout on TCH for AMR with different values of ARLT

Purpose:

The purpose of this test is to verify that Radio link timeout occurs as defined by ARLT parameter in BSC with AMR call during active phase.


Input Expected Output Set ARLT as given in the test case at BSC [Note 63] and [Note 64].

ARLT parameter set successfully.

DN0694168 Issue 2-0


Input Expected Output Establish MS to MS AMR speech call and monitor the TRX signalling links.


Introduce high interference [Note 69] in UL direction on active calls such that Radio link timeout occurs for AMR call. The A-bis TRX signalling links are recorded during the test

It is observed that as soon as BTS is not able to decode number of SACCH messages as defined by ARLT parameter on BSC, the BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC. It can be verified from the A-bis traces that radio link timeout occur after (480*RLT) ms for EFR call and (480*ARLT) ms for AMR call. Call is released.

Case Ref.


DTX used ARLT

1. 2 Omni2 MBCCHC + TCHF UL and DL both (Calls are on BCCH TRX)

4

2. 2 Omni2 MBCCHC + TCHF No (Calls are on Non BCCH TRX)

32

3. 2 Omni3 MBCCHC + TCHF UL and DL both (Calls are on BCCH TRX)

64

4. 2 Omni1,3 MBCCHC + TCHF UL and DL both (Calls are on BCCH TRX)

Invalid value

1If invalid values of ARLT parameter is defined i.e. < 4 or > 64 using MML command ZEQY then for value less than 4 error “VALUE TOO LOW” and for value > 64 errors “ VALUE TOO HIGH” will be observed on MML. For this test case further test steps as given above will not be valid. 2Use EDGE HW 3Use GSM HW

14.5 Radio link timeout on TCH for AMR with change of ARLT

Purpose:

The purpose of this test is to check the impact of change in ARLT value on already established AMR call.


DN0694168 Issue 2-0


Input Expected Output Set RLT=20 and ARLT=24 at BSC [Note 63] and [Note 64].


Establish MS to MS AMR speech call as specified in the test case. Set ARLT=32 at BSC. Another pair of AMR speech call is made from MS to MS as specified in the test case.

Call is established successfully. During call establishment Radio Link Timeout value received in SI6 message to supervise the radio link is equal to ARLT value defined in BSC. During call establishment Radio Link Timeout value received in SI6 message to supervise the radio link is equal to new ARLT value defined in BSC. New ARLT value has no impact on the call made at the start of test case. All calls are established successfully. The received audio shall be good and without distortion of the original speech, and there shall be no additional disturbing sounds heard at the receiving end during speech or silence periods.

Introduce high interference [Note 69] in UL direction on active calls such that Radio link timeout occurs for AMR calls. The A-bis TRX signalling links are recorded during the test

It is observed that as soon as BTS is not able to decode number of SACCH messages as received from BSC with respective calls, the BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC. It is clear from the A-bis trace that call made at the start of test case is released first as its ARLT value is lower than ARLT value of new call. Calls are released.

Case Ref.

Configuration/Site type


DTX used Call Type



AFS

2. Any (EDGE) MBCCHC + TCHD

No (Calls are on Non BCCH TRX) AHS

14.6 Radio link timeout on TCH for AMR and GP recovery

Purpose:

The purpose of this test is to check the impact of radio link timeout on GP timeslot.


DN0694168 Issue 2-0


Input Expected Output Set ARLT=24 at BSC [Note 63] and [Note 64]. Define CDED=0, CDEF=100, CMAX=100 using MML command ZEQV and activate EGPRS in cell.

ARLT parameter set successfully. All TCH timeslots change to GP timeslot except one.

Establish MS to MS AMR speech call. Monitor the TRX signalling links during call establishment.


Introduce high interference [Note 69] in UL direction on active calls such that Radio link timeout occurs for AMR calls. The Abis TRX signalling links are recorded during the test

It is observed that as soon as BTS is not able to decode number of SACCH messages as received from BSC with respective calls, the BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC. Call is released.

Monitor the GP timeslot on the Abis. GP timeslot resynchronises and PCU Master data frames are seen on the timeslot on which radio link timeout occurred earlier.

Transfer 1 MB file in DL direction using the GP timeslots used earlier for AMR call.

Data transfer is successful.

Case Ref. Configuration Channel configuration 1. 4 Omni MBCCHC+ TCHF 2. Standard Ecell. (Calls and data

transfer are on BCCH TRX) [Note 115]

MBCCHC+ TCHF

3. One Omni MBCCHC+ TCHF

14.7 Radio link timeout with Handover

Purpose: The purpose of this test is to verify that Radio link timeout occurs as defined by ARLT/RLT parameter in BSC with AMR/EFR call(s) after Handover has been performed successfully.

Note 73.

DN0694168 Issue 2-0


ACH-> with this parameter you define the preference between the currently used Multirate configuration and the one defined for the target BTS during internal and external handovers. Use MML command ZEEM to modify the ACH command. ACH=2 means that the Multirate configuration of the target BTS is preferred in further channel allocations.


Input Expected Output Set RLT=20 and ARLT=24 for Source Cell and RLT=16 and ARLT=28 for Target Cell at BSC [Note 63and Note 64]. Check that ACH=2 are defined at BSC. See Note 73.

RLT and ARLT parameters are set successfully for both Target and Source Cell.

Speech calls are made from MS to MS in source cell as defined in the test case. Monitor the TRX signalling links during call establishment.


Level of Source cell is degraded using variable attenuator in DL direction so that Handover is triggered.

Handover to Target cell is successful. MS receives new Radio Link Timeout value as defined for Target cell.

Introduce high interference [Note 69] in UL direction on active calls in target cell. The A-bis TRX signalling links are recorded during the test

It is observed that as soon as BTS is not able to decode number of SACCH messages as defined by RLT (for EFR call) or ARLT (for AMR call) parameter on BSC for target BTS, the BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC. Calls are released.

Speech calls are made again from MS to MS as defined in the test case.

Calls are established successfully.

Level of Source cell is degraded using variable attenuator in DL direction so that Handover is triggered.

Handover to Target cell is successful. MS receives new Radio Link Timeout value as defined for Target cell.

DN0694168 Issue 2-0


Input Expected Output Introduce high interference [Note 69] in DL direction on active calls. The A-bis TRX signalling links are recorded during the test

MS starts sending Measurement Report (with RX QUAL=7) till Radio link timeout occurs. Number of Measurement Reports (with RX QUAL=7) send by Mobile will be equal to RLT (for EFR/FR/HR call) or ARLT (for AFS/AHS call). After radio link timeout MS stops sending Measurement Report i.e. SACCH messages. It is observed that as soon as BTS is not able to decode number of SACCH messages as defined by RLT (for EFR/FR/HR call) or ARLT (for AFS/AHS call) parameter on BSC, the BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC. Calls are released.

Case Ref.

Configuration

Source cell call type

Target Cell call type

DTX used Handover Type

1. Any AFS EFR Both UL & DL

Synchronous

2. Any3 EFR AFS UL only Synchronous

3. Multi BCF configuration

AHS (Master BCF)

AHS (Slave BCF)

DL only Synchronous

4. 4+4+4 Simultaneous AFS and EFR

AFS and EFR1 Both UL & DL

Asynchronous

5. Any2 AFS (GSM cell) AFS (GSM cell)

Both UL & DL

Asynchronous

6. Any3 AFS AFS Both UL & DL

Asynchronous

1InterBSC Handover is performed. 2IMSI Based Handover is performed. 3Use EDGE HW 14.8 Object control and Radio link timeout

Purpose:

The purpose of this test is to verify that Radio link timeout occurs as defined by ARLT/RLT parameter in BSC with AMR/EFR call(s) after object is locked/unlocked/blocked/unblocked.


Input Expected Output Set RLT=20 and ARLT=24 at BSC [Note 63 and Note 64].


DN0694168 Issue 2-0


Input Expected Output Speech calls are made from MS to MS as defined in the test case. Monitor the TRX signalling links during call establishment.


Introduce high interference [Note 69] in UL direction on active calls, The A-bis TRX signalling links are recorded during the test

It is observed that as soon as BTS is not able to decode number of SACCH messages as defined by RLT (for EFR call) or ARLT (for AMR call) parameter on BSC, the BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC. Calls are released.

Action is performed on object specified in the test case. Define RLT=16, ARLT=20 Action is undone.

Object comes in WO state.

Calls are made from MS to MS as defined in the test case on the object the action is performed.



It is observed that as soon as BTS is not able to decode number of SACCH messages as defined by RLT (for EFR call) or ARLT (for AMR call) parameter on BSC, the BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC. Calls are released.

DN0694168 Issue 2-0




Call Type Object Type

Action

1. 6 Omni with IDD/4UD1

MBCCHC + TCHF

AFS & EFR both

BCF Lock

2. Any2 MBCCHC + TCHD

AHS & EFR both

TRX Lock

3. Any2 MBCCHC + TCHF

AFS (with EMR on)

BTS Lock

1Do not change RLT and ARLT values for this test case. 2Use EDGE HW

14.9 AMR packing/unpacking and Radio link timeout

Purpose:

The purpose of this test is to verify that Radio link timeout occurs as defined by ARLT parameter in BSC with AMR call once AMR unpacking has been performed and Unpacking has no impact on RLT.

Note 74. Packing of FR AMR calls to HR AMR calls due to cell load

Note 75. Spontaneous packing of FR AMR calls to HR AMR calls is triggered when the cell load is high enough; the number of free full rate resources reduces below the value of the parameter Lower limit for FR TCH resources. Spontaneous packing is triggered by any new channel allocation.

Note 76. Unpacking of HR AMR calls to FR AMR calls due to call quality

Note 77. Spontaneous unpacking of HR AMR calls to FR AMR calls is triggered when the quality of a HR AMR call degrades below the intraHOthresholdRxqual For AMRHR. Cell load does not have an effect.


Input Expected Output Set ARLT=24 at BSC [Note 63and Note 64]. Use default AMR parameters as defined in the BSC.

ARLT parameter set successfully.

DN0694168 Issue 2-0


Input Expected Output Establish MS to MS AHS speech call. Monitor the TRX signalling links during call establishment.


Introduce interference [Note 69] in UL direction on active calls and increase it slowly so that the quality of the HR AMR call degrades under the BTS parameter ‘intra HO threshold Rx Qual for AMR HR’ (see Note 74). The A-bis TRX signalling links are recorded during the test

HR AMR call is unpacked to FR AMR call. It is observed that as soon as BTS is not able to decode number of SACCH messages as defined by RLT (for EFR call) or ARLT (for AMR call) parameter on BSC, the BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC. It is clear that AMR Unpacking has no impact on ARLT functionality. Call is released.

Case Ref. Configuration Channel configuration 1. (4+4) common BCCH (GSM+EDGE) MBCCHC+ TCHD

Calls are non BCCH BTS. 2. (2+2) common BCCH1 MBCCH+SDCCH +TCHD 3. (2+2) common BCCH2 MBCCH+SDCCH +TCHD

1Use BSC S13 2Use EDGE HW

14.10 Multiple speech calls and Radio link timeout

Purpose:

The purpose of this test is to verify that Radio link timeout occurs as defined by ARLT/RLT parameter in BSC with AMR/EFR call(s) only for interfered call.


Input Expected Output Set ARLT=24 at BSC [Note 64]. Use default AMR parameters as defined in the BSC. All TCH timeslots of Non BCCH TRXs are locked.

ARLT parameter set successfully. TCHs are locked successfully.

DN0694168 Issue 2-0


Input Expected Output Make 2 pairs of EFR to EFR speech call and 2 pairs of AMR to AMR speech call. Monitor the TRX signalling links during call establishment.


Introduce high interference [Note 69] in DL direction on active calls on one pair each of AMR and EFR (i.e. one pair of AMR to AMR and one pair of EFR to EFR). The A-bis TRX signalling links are recorded during the test

It is observed that as soon as BTS is not able to decode number of SACCH messages as defined by RLT (for EFR call) or ARLT (for AMR call) parameter on BSC, the BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC. Calls with no interference remain active and their quality remains good. Interfered Calls are released from BSC.

Case Ref. Configuration Channel configuration 1. 6+6 with RTC MBCCHC+TCHF

14.11 Multiple speech calls with change in RLT/ARLT

Purpose:

The purpose of this test is to check the impact of change in RLT and ARLT value on already established EFR and AMR calls.


Input Expected Output Set RLT=16 and ARLT=24 at BSC [Note 63and Note 64].


DN0694168 Issue 2-0


Input Expected Output Make an EFR to EFR speech call and an AMR to AMR speech call. Monitor the TRX signalling links during call establishment. Change RLT=24 and ARLT=32 Make another EFR to EFR speech call and another AMR to AMR speech call.

All calls are established successfully. During call establishment Radio Link Timeout value received in SI6 message to supervise the radio link is equal to RLT (for EFR call)/ARLT (for AMR call) value defined in BSC. New calls established successfully and receive new RLT/ARLT values. The received audio shall be good and without distortion of the original speech, and there shall be no additional disturbing sounds heard at the receiving end during speech or silence periods.

Introduce high interference [Note 69] in UL direction on active calls such that Radio link timeout occurs for calls. The A-bis TRX signalling links are recorded during the test

It is observed that as soon as BTS is not able to decode number of SACCH messages as received from BSC for respective calls, the BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC. It is clear from the A-bis trace that calls made at the start of test case are released first as there (A)RLT value are lower than (A)RLT value of new calls. Calls are released.

Case Ref.


DTX used

1. 2+2+2 MBCCHC + TCHF


14.12 Multiple Breaks at Air interface

Purpose:

The purpose of this test is to check that counter for SACCH frame is working correctly with multiple breaks at air interface with active AMR call.




DN0694168 Issue 2-0


Input Expected Output Establish MS to MS AMR speech call. Monitor the TRX signalling links during call establishment.

Call establishes successfully. During AMR call establishment Radio Link Timeout value received in SI6 message to supervise the radio link is equal to ARLT value defined in BSC. The received audio shall be good and without distortion of the original speech, and there shall be no additional disturbing sounds heard at the receiving end during speech or silence periods.

Introduce interference [Note 69] in UL direction on active calls and increase it slowly such that Radio link quality becomes bad and SACCH messages are not correctly decoded at the receiving side.

It is observed that as soon as BTS is not able to decode SACCH messages receiving side start decrementing the counter.1

Once receiving side starts counter1, remove the interference before its value decreased to 0. Call remains active. Wait for 30 sec.

Call remains active, quality becomes good and there shall be no additional disturbing sounds heard at the receiving end during speech or silence periods Counter is incremented to MAX value (ARLT).1

Repeat above 2 steps at least 5 times. Call remains active.

Wait for 5 minutes. Introduce high interference [Note 69] in UL direction on active calls such that Radio link timeout occurs for calls. The A-bis TRX signalling links are recorded during the test

Call is active and received audio shall be good and without distortion of the original speech. It is observed that as soon as BTS is not able to decode number of SACCH messages as received from BSC for respective calls, the BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC. Call is released.

Case Ref.


DTX used



1This counter cannot be observed on Abis interface, its value will be equal to ARLT for AMR call, so it is indirectly being tested here. If counter will not be incremented to its MAX value (=ARLT for AMR call) once interference is removed then in few iterations (interference on and off) radio link timeout will occur as soon as Interference is introduced.

14.13 T200 Expiry

Purpose: The purpose of this test is to check that due to radio link failure at air interface timer T200 expires correctly with different values of ARLT.


DN0694168 Issue 2-0




Establish MS to MS AMR speech call. Monitor the TRX signalling links during call establishment.

Call establishes successfully. During AMR call establishment Radio Link Timeout value received in SI6 message to supervise the radio link is equal to ARLT value defined in BSC. The received audio shall be good and without distortion of the original speech, and there shall be no additional disturbing sounds heard at the receiving end during speech or silence periods.


It is observed that as soon as BTS is not able to decode number of SACCH messages as received from BSC for respective calls, the BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC. BSC sends CHANNEL RELEASE (RR message) to BTS.

Timer T200 expires N200+1 times at layer 2 on the BTS.

BTS sends ERROR IND to BSC with cause “timer T200 expired (N200 + 1) times”. BSC sends RF CHANNEL REL to BTS. Call is released.

Case Ref. Configuration/Site type Channel configuration 1. 4+4+4/Ultra Site & Metro Site MBCCHC+TCHF

15. DYNAMIC A-BIS ALLOCATION

15.1 Downlink Resource Allocation Loading

Purpose:

The purpose of these test cases is to check that EGPRS DL resource allocation functions correctly when EDAP resources are lacking.


DN0694168 Issue 2-0


Input Expected Output Use site with only 2 PCM timeslots allocated to EDAP Any transmission unit may be used. LA is set as specified (ZEQV:BTS=##:ELA=#;) Ensure there are at least 6 radio timeslots available for (E) GPRS. Set initial coding scheme to MCS-9: (ZEQV:BTS=##:MCA=9,MCU=9;)

Site is configured as defined.

Setup EGPRS data transfer in downlink direction (on 2 radio timeslots). Monitor PCU frames on A-bis Setup total 3 EGPRS data transfer.

Data transfer begins. A-bis shows MCS-9 in use. Transfer maintains an end-user data rate of at least 48Kbps per timeslot. All data transfers are setup. Lower MCS's are used instead of the specified MCS-9 due to the lack of EDAP TS's. Therefore data rates are reduced. When LA is OFF, coding scheme will remain same but throughput is decreased.

Terminate all calls All the calls are successfully terminated

Case Ref.

LA Mode

Configuration Hopping GP Timeslot Location

1. ON EDGE HW NAH-hopping BCCH TRX1

2 OFF Mixed-2 RF-hopping Non-BCCH TRX

3. OFF Any RF-hopping Non-BCCH TRX

1Use E-Cell configuration and transfer data in E-area

15.2 Uplink Resource Allocation Loading

Purpose:

The purpose of these test cases is to check that EGPRS UL resource allocation functions correctly when EDAP resources are lacking.

DN0694168 Issue 2-0


Input Expected Output Use any configuration. Use site with only 1 TS allocated to EDAP. MS priority is set to be the same for all MS’s used. Any transmission unit may be used. LA is set as specified. (ZEQV:BTS=##:ELA=#;) Ensure there are at least 5 radio timeslots available for (E) GPRS. Set initial coding scheme to MCS-9: (ZEQV:BTS=##:MCA=9,MCU=9;)

Site is configured as given and is in working state.

Setup EGPRS data transfer using TCP/IP in uplink direction (one timeslot). Monitor PCU frames at A-bis. Setup total 5 EGPRS data transfer.

Data transfer begins. A-bis shows MCS-9 in use. Transfer maintains an end-user data rate of at least 48Kbps. All data transfers are setup. MCS-9 is predominantly used for all transfers. The data rates are reduced to due to uplink scheduling. Each transfer achieves at least 9Kbps user rate.

Terminate all packet calls All calls are successfully terminated

Case Ref.

LA Mode

Configuration Hopping GP Timeslot Location

1. ON Any No-hopping Non-BCCH TRX

2 OFF Any BB-hopping BCCH TRX

3. OFF Any RAH-hopping Non-BCCH TRX

15.3 Maximum Dynamic Pool Size

Purpose:

The purpose of these test cases is to check that maximum sized EDAP functions correctly.

Input Expected Output Configure a 3 TRX Omni BTS. BTS is configured

Configure Dynamic A-bis No error messages are seen at the BSC or at the BTS Manager when configuring the EDAP.

DN0694168 Issue 2-0


Use the MML command ZEQV to set the following: CDED=10,CDEF=100,CMAX=100 Enable EGPRS & GPRS. Set GPRS coding scheme as CS2 and EGPRS coding scheme as MCS-9. Set Link Adaptation = ON. (ZEQV:BTS=##:ELA=2;)

(E)GPRS settings are enabled.

Begin TCP/IP data transfers in the direction shown in the table. Begin simultaneously, all the numbers of EGPRS and GPRS transfer shown in the table.

All data transfers start successfully. EGPRS TBFs use MCS9; GPRS TBFs use CS2, nearly all of the time. Lower coding schemes may be seen, but only occasionally.

Monitor the A-bis for PCU MASTER DATA FRAMES and PCU SLAVE DATA FRAMES. Set Link Adaptation = OFF. Set initial coding scheme = MCS-9 Use enough EGPRS transfers in the direction shown to use all the EDAP sub TSs simultaneously. Monitor the A-bis.

The Master Data Frame for each TBF points to the correct Slave Frames. All sub TSs in the EDAP are allocated at some point during the transfer of data (although not necessarily simultaneously). 4 sub TSs are allocated to each MCS9. 1 sub TS is allocated to each CS2. All transfers proceed successfully. At some point in the transfer all the sub TS are used simultaneously.

Case Ref.

Direction Configuration GPRS transfers

EGPRS transfers

1. Uplink (1 RTSL)

Any 4 11

2 Downlink (2 RTSL)

Any 4 5

3. Uplink (1 RTSL)

Any 0 12

15.4 Dynamic Abis loop test

Purpose: To verify that dynamic Abis loop tests are successful on all RTSLs.

Input Expected Output Configure the site as stated in the test case with Attach DAP to all TRXs and enable EGENA at the site.

The site is in supervisory state.

Initiate a Dynamic Abis TRX loop test on RTSL 6 of the BCCH TRX using MML command MML Commands: ZUBK: TEST:BTS=<Bts id>,TRX=<Trx No>:<RTSL>:SEL=1:ATSL=<DAP TSL on Abis>:;

Command is executed successfully.

DN0694168 Issue 2-0


Input Expected Output Print and analyse the Abis loop test report at the BSC. ZUBP:AL:BTS=<Bts id>;

Report states that the loop test has passed.

Delete the test report at BSC. ZUBD:AL:BTS=<Bts id>;

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

Make a pair of calls. All calls are successful

Perform Dynamic Abis TRX loop tests on all the other RTSLs in the BTS.

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

Make calls on all the time slots as stated in the test case.

All calls are successful

Case Ref BTS Configuration Channel Configuration

Hopping Call Type

1 4 Omni EDGE MBCCHC + SDCCB on CH3 + TCHH

RF HR and AHS

2 4 Omni EDGE MBCCH + SDCCH + TCHD

RF AFS and AHS

16. ENHANCED DATA RATES FOR GLOBAL EVOLUTION, EDGE

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

Note 79. EGPRS cannot be used without Dynamic A-bis being configured.

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

Acknowledged RLC Mode

Unacknowledged RLC Mode

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

In Unacknowledged RLC Mode the data is not acknowledged. Incremental Redundancy does not take place. The system relies upon error correction using the redundancy incorporated in the coding scheme. Any data blocks that are not successfully error corrected remain corrupt.

DN0694168 Issue 2-0


Note 80. The Link Adaptation algorithm is also influenced by the amount of space left in the EDAP. If the space in the EDAP runs out, Link Adaptation will restrict the MCS used in the downlink accordingly. In the uplink the PCU scheduling function will prevent the MS from sending data for one block period, until space again becomes available in the EDAP. The data rate will not be as high as anticipated. For this reason, the EDAP must be of a sufficient size for the number of radio timeslots configured as EGPRS.

Note 81. To enable/disable Link Adaptation use the MML commands:

ZEQV:BTS=##:ELA=1; Link Adaptation = ON

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

To set the initial MCS use the MML command: ZEQV:BTS=##:MCA=#,MCU=#;

Where:

MCA = initial coding scheme in acknowledged RLC mode.

MCU = initial coding scheme in unacknowledged RLC mode.

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

This is done using the MML command: ZEQV: BTS=#: MBP=0, MBG=0;

16.1 EGPRS MCS 1-9 & Incremental Redundancy

Purpose:

The purpose of these test cases is to check that all EGPRS coding schemes are supported, Incremental Redundancy is supported in uplink & downlink and on all EGPRS coding schemes. Also verify that 8PSK modulation has no adverse effect upon the interference indications.

Test Tools Required: Signal Generator, Spectrum Analyser

Note 83. Timeslot 7 must always be left unlocked for synchronisation purposes. (E) GPRS transfers are loaded from timeslot 7 forward. In order to test other timeslots it is

DN0694168 Issue 2-0


necessary to first occupy timeslot 7 with another transfer, then begin the transfer under test. Lock up all timeslots except timeslot 7 and the timeslot under test. To test timeslot 6 in the downlink, it is acceptable to have a downlink transfer on two timeslots, one of which is timeslot 6.

Note 84. When more than 1 Multislots EGPRS class 2 mobiles are used and if there are only contiguous GP TSs available, then MS shall get 2+1 TS for data transfer and UL TS will be shared by the phones. This may result to a lower rate of data transfer in UL direction

Note 85. A data block is first protected with the P1 of a certain MCS. If the decoding fails, the received P1 is stored in the receiver's memory for future use and data block is re-transmitted using the P2 and subsequently with P3 of the same MCS.

Incremental Redundancy scheme

Preconditions:

1. Dynamic A-bis is enabled

2. Set BTS to use specified MCS (Disable link adaptation)

DN0694168 Issue 2-0


ZEQV: BTS=##: ELA=0;

3. Set initial coding scheme

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

4. Lock up timeslots to force transfer on timeslot Under test as shown in the table

5. Establish extra transfer on timeslot 7 if necessary. (See Note 338.) 6. For test case 3 & 4, PMAX and PMIN should have different values.

Input Expected Output Monitor A-bis for PCU frames. PCU MASTER DATA FRAME shows data

is sent using correct MCS. No retransmissions are seen.

Change C/I gradually to value as specified in test case. Monitor A-bis for PCU frames Data transfer is repeated 3/4 times and average data rate is calculated

Retransmissions (P1, P2, and P3) are observed on MCS 4 to 9. RF RESOURCE INDICATION messages show expected level of interference in UL (as specified by the boundary limits ZEQK) Data rate is equal to or better than expected.

For test case 3 & 4: Using spectrum analyser monitor power level of EGPRS TS.

For test case 3 & 4: EGPRS power level is equal to BCCH (i.e. PMAX parameter).

DN0694168 Issue 2-0



Configration MCS

UL/DL

File Size

TS Data Rate @ C/I=30dB

Data Rate @ C/I

1. Any3 1 UL

1MB 0 8.5 Kbps 8.5 Kbps 5 dB

2. Any EDGE with BB Hopping

2 DL

500 Kb 1 10.7 Kbps

10.7 Kbps

5 dB

3. Any EDGE with BB Hopping, Data transfer on BCCH TRX

3 UL

500 Kb 2 14.3 Kbps

14.2 Kbps

5 dB

4. Any EDGE with BB Hopping, Data transfer on BCCH TRX

3 UL

500 Kb 2 14.3 Kbps

14.2 Kbps

5 dB

5. Any EDGE 4 DL

500 Kb 3 16.6 Kbps

9.1 Kbps 5 dB

6. 3 N TRX+3 DFCA TRXs , RF Hopping

4 DL

500 Kb 3 16.6 Kbps

9.1 Kbps 5 dB

7. Any EDGE with RAH Hopping

5 UL

500 Kb 4 21.7 Kbps

10.2 Kbps

5 dB

8. Any EDGE2 5 UL

500 Kb 4 21.7 Kbps

10.2 Kbps

5 dB

9. Any 6 DL

1MB 5 27.6 Kbps

11.0 Kbps

5 dB

10. 2N TRX+2 DFCA TRX, (EDGE) data is transferred on both non DFCA TRxs one by one

7 UL

500 Kb 6 43.4 Kbps

23.0 Kbps

10 dB

11. Any 7 UL

500 Kb 6 43.4 Kbps

23.0 Kbps

10 dB

12. Any2 8 DL

1MB 1 50.3 Kbps

26.0 Kbps

10 dB

13 Any1,4 9 DL

1MB 3 54.7 Kbps

28.1 Kbps

10 dB

14 3+3 IDD configuration with RF hopping in both sectors5

4 DL

500 Kb 3 16.6 Kbps

9.1 Kbps 5 dB

1Use common BCCH 2+2 configuration. Data Transfer is done both in BCCH and non BCCH BTS of common BCCH segment. 2Enable extended UL TBF feature at BSC & use extended UL TBF capable phones. 3On BSC S13 with PCU1 4On BSC S13 5Put one ARFN common in both MA list, make CS calls as well in tsl that is being used for EGPRS (non BCCH TRXs of both sectors)

DN0694168 Issue 2-0


16.2 Link Adaptation in Unack Mode (Changing Air Interface Conditions)

Purpose:

When in Unacknowledged RLC Mode, to check that Link Adaptation occurs dynamically as prevailing radio conditions change.


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

Table 6.

Coding Scheme

Number of Slave Frames

MCS 1 0 MCS 2 1 MCS 3 1 MCS 4 1 MCS 5 1 MCS 6 2 MCS 7 3 MCS 8 4 MCS 9 4

Preconditions:

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

2. Use a 2 TRX sector

TRX 2, TS0 = BCCH

3. Use the MML command

ZERM:BTS=##, TRX=##:GTRX= N; for GSM TRXs in the sector.

Use CDED, CDEF and CMAX to enable 2 radio timeslots as EGPRS.

4. Set Link Adaptation = ON (see Note 80).


ZEQV: BTS=##: BLU=10;

DN0694168 Issue 2-0


To set the max. Limit for block error rate to 10 per 1000.

Check that no offsets are applied to the BEP values (See Note 82).

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

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

Transfer started successfully.

On Abis PCU frames are monitored. Slowly change the C/I from 30dB to 0dB and back to 30dB. Carry out 2 times. Rate of change = 1 dB/sec approx.

The coding scheme used steps down through the coding schemes from the least robust (MCS9) to the most robust (MCS1) and back again to match the changing air interface conditions. MCS 4 may be skipped as Link Adaptation switches from 8PSK to GMSK and vice versa. The data rate changes to reflect the changing MCS.

Check the A-bis trace for the MCS used, and the allocation of PCU Slave Data Frames.

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

Case Ref.

Configuration Type of TRX Direction

1. Any BCCH Uplink

2. Any Non – BCCH Downlink

16.3 Link Adaptation in Ack Mode (Changing Air Interface Conditions)

Purpose:

To check that retransmissions are made using MCS within the same family as the initial transmission. To check that retransmissions in a different MCS can be successfully combined (Incremental Redundancy). When in Acknowledged RLC Mode, to check that Link Adaptation occurs dynamically as the prevailing air interface conditions change. Also check that Dynamic A-bis can adjust dynamically in-step with the changes in MCS.


DN0694168 Issue 2-0


Table 6.

Initial transmission, prior

to transition

MCS transition Subsequent transmission, after transition

Air Interface conditions deteriorating MCS 9 MCS 9 → 8 MCS 6 MCS 8 MCS 8 → 7 MCS 6 padded MCS 7 MCS 7 → 6 MCS 5 MCS 6 MCS 6 → 5 MCS 6 MCS 5 MCS 5 → 4 MCS 5 MCS 4 MCS 4 → 3 MCS 4 MCS 3 MCS 3 → 2 MCS 3 MCS 2 MCS 2 → 1 MCS 2

Air Interface conditions improving MCS 1 MCS 1 → 2 MCS 1 MCS 2 MCS 2 → 3 MCS 2 MCS 3 MCS 3 → 4 MCS 3 MCS 4 MCS 4 → 5 MCS 4 MCS 5 MCS 5 → 6 MCS 5 MCS 6 MCS 6 → 7 MCS 6 MCS 7 MCS 7 → 8 MCS 7 MCS 8 MCS 8 → 9 MCS 8

Preconditions

1. Use a 2 TRX sector with two dynamic A-bis connections

TRX 2, TS0 = BCCH


ZERM:BTS=##, TRX=##:GTRX= N; for GSM TRXs in the sector.

3. Use CDED, CDEF and CMAX to enable 2 radio timeslots as EGPRS

4. Set Link Adaptation = ON (see Note 80)

Use the MML command

ZEQV:BTS=##:BLA=100;

To set the maximum limit for block error rate to 100%.

Check that no offsets are applied to the BEP values (see Note 82).

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

DN0694168 Issue 2-0


Input Expected Output Transfer a 500KB file using FTP in the direction shown in the table below. Use one timeslot for uplink transfer on TRX using A-bis. Use two timeslots for downlink transfer on TRX using the other A-bis.


Record an A-bis trace for PCU frames Slowly change the C/I from 30dB to 0dB and back to 30dB. Carry out 2 times. Rate of change = 1 dB/sec approx. Stop recording.

The coding scheme used for initial transmissions steps down through the coding schemes from the least robust (MCS9) to the most robust (MCS1) and back again to match the changing air interface conditions. MCS 4 may be skipped as Link Adaptation switches from 8PSK to GMSK and vice versa.

In the A-bis trace track the MCS used for the initial transmissions of RLC data blocks. Track the retransmission of RLC data blocks either side of each MCS transition.

Retransmissions of the same RLC data block occur in the coding scheme shown in Table 6

Check the A-bis trace for the allocation of PCU Slave Data Frames.

Dynamic A-bis allocates PCU SLAVE DATA FRAMES correctly as the MCS changes see Table 6

Compare the received file with the sent file. The file received is identical to the file sent.

Case Ref.

Type of TRX

Configuration Direction 2-way RX Diversity

1. BCCH Any Uplink On

2. BCCH Any Uplink Off

3. Non–BCCH

Any/ UltraSite Downlink On

4. Non–BCCH

3 NTRX+3 DFCA TRXs Use EDGE HW1

Downlink On

1Data transfer on Non BCCH TRX

16.4 GPRS Data transfer when EGPRS is enabled

Purpose:

The purpose of these test cases is to check that data can be transferred using coding scheme 1 and 2 when EGPRS is enabled that data can be transferred reliably in both uplink & downlink on PDTCH.

Preconditions:

1. EGPRS is enabled.

DN0694168 Issue 2-0


Input Expected Output Using a non-EDGE GPRS MS, Perform Attach and then activate a PDP Context.

Attach and activation of PDP context is successful.

Transfer a file of specified size and in the direction shown in the table below.

The data is transferred with BER of 0%. The expected data rates for the coding scheme are achieved. (CS-1 approx. 9kbit/s per timeslot used and CS-2 is approx. 13.4kbit/s per timeslot).

Monitor the A-bis for PCU frames, user data rate is also monitored At least 3 times transfer should be made to get a reliable figure on throughput

In the PCU data frame the values for Coding scheme & RX level are verified to be reliable.

Case Ref.

BCCH Configuration/ TCH configuration / CS Call type

Configuration Coding Scheme

No of Time Slots


1 MBCCH/TCHF / FR

Any EDGE with BB Hopping

CS-1 1 TS on non-BCCH TRX

Downlink 1Mb file

2 MBCCHC/TCHD / FR

use mixed configuration 1 GSM(BCCH TRX)+3 EDGE

CS-2 1 TS on BCCH TRX

Downlink 1Mb file + uplink 100kb file

3 MBCCHC/TCHD / FR

2 N TRX+2 DFCA TRXs. Use EDGE HW

CS-2 1 TS on BCCH TRX


4 MBCCHC/TCHD / FR

Any EDGE1 CS-2 1 TS on BCCH TRX


1Data transfer on BCCH and NON-BCCH

DN0694168 Issue 2-0


16.5 GPRS & EGPRS TBFs on One Timeslot

Purpose:

The purpose of these test cases is to check that both GPRS and EGPRS TBFs can exist on the same radio timeslot.

Note 87.

The PCU sends a PACKET UPLINK (or DOWNLINK) ASSIGNMENT for each MS. These messages assign a different TFI to each MS. The uplink assignment also assigns a USF to each MS. The USF in the header of the downlink RLC Data Blocks indicate which TBF may transmit in the uplink

The PCU restricts the MCS used for a downlink EGPRS TBF to a GMSK coding scheme when an uplink GPRS TBF shares the same radio timeslot. It does this so that the uplink GPRS MS can read the USF information in the downlink TBF’s header.

Note 88. The priority of the subscriber affects the number of blocks scheduled to the MS when it shares a timeslot and therefore the throughput it achieves. It is handled differently in M10 and M11.

M10: The priority is determined by the precedence class in the subscriber parameters set at the HLR. It can be changed by establishing an MML session with the HLR and using the ZMNM command.

M11: The priority is determined by the Traffic Handling Priority in the QoS Profile attached to the subscriber parameters in the HLR.

The priority agreed by the Network for an MS can be seen in the ACTIVATE PDP CONTEXT ACCEPT message on the A-bis, and the DL-UNIDATA frames on The Gb interface.

Preconditions:

1. Chose three MS so that the RLC Mode = Acknowledged. The MS must have the same priority set at the HLR (See Note 88)

MS1 = EGPRS

MS2 = EGPRS

MS3 = GPRS

DN0694168 Issue 2-0


2. Enable EGPRS on only EDGE TRX (for GSM TRXs set GTRX=N). Lock all traffic timeslot so that only one (E) GPRS timeslot remains available for use.

3. Set Link Adaptation = on for both GPRS and EGPRS, to do this for GPRS: Use the MML command ZEQV to set the following parameters to the values shown:

DLA = 5%, ULA = 5%

DLB = 10%, ULB = 10%, DLBH = 10%, ULBH = 10%

COD = 0, CODH = 0 (GPRS link adaptation used).

4. Start monitoring the A-bis for PCU frames and record a trace

Input Expected Output Perform (E) GPRS attach and activate PDP context for each MS (i.e. MS1, MS2 and MS3).

All the MS attach successfully. All MS activate a PDP Context successfully.

Begin UDP data transfer of 2MB files in the direction shown for each MS: MS1 = uplink MS2 = downlink Begin UDP data transfer of a 2MB file with MS3 = uplink.

Both MS begin transfer successfully using predominantly MCS-9. The TBFs for all three MS are successfully shared on the one timeslot. The coding scheme used for the downlink transfer (MS2) will alternate between GMSK and 8PSK.

Case Ref.

Configuration Hopping mode

1. 2 sectors each with 2 TRX (BB2F with TSxA+TSxB) 1 No-Hopping

2. Multi TRX RF Hopping 1BSC S14 PCU2

16.6 GPRS Link Adaptation

Purpose:

To check that GPRS link adaptation selects the coding scheme (CS1, CS2) appropriate for the air interface conditions. To check that Dynamic A-bis allocates a slave subTS when CS2 is selected by GPRS link adaptation.


DN0694168 Issue 2-0


Note 89. In the uplink direction, the coding scheme used can be found in the uplink MCS indicator in the PCU Master Data Frame. In the downlink direction, the coding scheme to be used can be found in the downlink idle/header type.

Preconditions

1. Use the MML command ZEQV to set the following parameters to the values shown:

DLA = 5%, ULA = 5%

DLB = 10%, ULB = 10%, DLBH = 10%, ULBH = 10%

COD = 0, CODH = 0 (GPRS link adaptation used).

2. EGPRS must be enabled at the test BTS

3. Establish a Carrier / Interference (C/I) ratio > 30dB in the air interface, in the direction shown in the table

4. Use a non-EDGE GPRS MS, and RLC Mode = Acknowledged

Input Expected Output Attach the MS to the sector and activate a PDP Context.

MS attach successfully. MS activate a PDP Context successfully

Transfer a 500K file in the direction shown in the table below. Monitor the A-bis for the coding scheme used.

The PCU MASTER DATA FRAME indicates that CS2 is used. Dynamic A-bis allocates one slave TS.

Deteriorate the radio conditions gradually to C/I = 0dB.

The PCU MASTER DATA FRAME indicates that CS1 is used. No slave frames are allocated in Dynamic A-bis.

Improve the radio conditions gradually to C/I > 30dB.

The PCU MASTER DATA FRAME indicates that CS2 is used again. Dynamic A-bis allocates one slave frame.

Repeat the C/I cycle a further 2 times. The coding scheme switches as expected.

DN0694168 Issue 2-0


Case Ref.

Configuration Hopping Mode Direction

1. Any EDGE RAH hopping Uplink

2. Any No – hopping Downlink

3. 3NTRX+3DFCA TRX use EDGE HW2 RF Hopping Downlink

4. Any BB - Hopping Downlink

5. Any EDGE1 RAH hopping Downlink

6. 2 N TRX+2 DFCA TRXs. Use EDGE HW1 No-hopping Downlink 1Test cases to be done with GPRS enabled only, i.e. EGPRS should be disabled. Slave channels are not used with EGENA=N 2Make one GPRS and one EGPRS data transfer

16.7 EGPRS/GPRS Territory Upgrade/Downgrade

Purpose:

To check that EGPRS/GPRS territory upgrade/downgrade works properly and that one RTSL can support more than one TBF.

Note 90.

When more than 1 Multislots EGPRS class 2 mobiles are used and if there are only contiguous GP TSs available, then MS shall get 2+1 TS for data transfer and UL TS will be shared by the phones. This may result to a lower rate of data transfer in UL direction.

Note 91.

• CSU and CSD parameters at the BSC (command: ZEEM) may need changing in order to cause GPRS upgrade/downgrade.

Preconditions:

1. Using MML command ZEQV set the values of CDED and CDEF such that one dedicated TS and one default TS is configured.

2. For testcase 6 all sites are defined as neighbours to each other.

Note 92. Perform actions specific for testcase 6 on any of one Ultra site and actions are repeated on the same site

Leave all other sites idle for the whole duration of the testcase; make sure that no synch frame should come for (E) GPRS territory TSLs of any site.

DN0694168 Issue 2-0


Input Expected Output Set up CS speech calls until only one timeslot remains idle

All calls are successful and one timeslot is idle.

Set up two data transfers as specified in Test case

Both data transfers begin (two TBF's on one timeslot).

Terminate CS speech calls one by one, until EGPRS territory upgrade is performed.

Existing data calls no longer share one RTSL

Set up CS speech calls one by one, until EGPRS territory downgrade is performed.

Data calls return to sharing one timeslot.

For testcase 6: Testcase is run for 12 hrs duration and in between of data transfer after the end of first hour lock sector by MML command: ZEQS:BTS=<bts no>:L:FHO,<time>; Unlock the sector ZEQS:BTS=<bts no>:U; Repeat steps 1 to 4.

BTS is locked successfully all calls are handed over to neighbours. Sector comes up working with no unexpected alarms. Gp territory regains its synchronisation. (E)GPRS territory upgrade downgrade is successful.

For testcase6: Repeat step 5 at the end of 2nd, 3rd and 11th hour.

Output is consistent.

Terminate all calls. Calls are terminated successfully.

Case Ref.

Data Transfer Type

Transfer 1 Direction


Configuration

1. EGPRS Uplink Uplink 2+2 BB-hopping 2. EGPRS Uplink Downlink 4 Omni EDGE, RAH

hopping 3. EGPRS Downlink Downlink 4 Omni RF Hopping 4. One GPRS

and one EGPRS

Downlink Downlink 3NTRX+2DFCA TRX Use EDGE HW

5. EGPRS Downlink Uplink 4 Omni EDGE, RAH hopping

6 One GPRS (CS4) one EGPRS (MCS9)

Downlink Uplink Multiple Ultra and Metro sites with EGENA enabled1

1Use S13 CD3.0 SW

DN0694168 Issue 2-0


16.8 Multiple TBFs on One Timeslot at Different Distances

Purpose:

The purpose of these cases is to check that the MS at different distances from the base station can share the same radio timeslot.


Preconditions:

1. Choose two EGPRS MS so that the RLC Mode = Acknowledged. The MS must have the same Precedence Class set at the HLR

2. Enable EGPRS on only one TRX. Lock all traffic timeslot so that only one (E) GPRS timeslot remains available for use

3. Set Link Adaptation = ON.

4. Use a fading simulator to simulate delay and attenuation but not fading, for one of the MS. Simulate the distance shown in the table

Input Expected Output Perform EGPRS attach and activate PDP context for the MS.

All the MS attach successfully. All MS activate a PDP Context successfully.

Begin FTP data transfer of 300KB files in the direction shown in the table for both MS. Monitor the A-bis for PCU frames and record a trace.

The PCU sends a PACKET UPLINK (or DOWNLINK) ASSIGNMENT for each MS. These messages assign a different TFI to each MS. Each MS successfully establishes a TBF on the same radio timeslot.

Monitor the end-user data rate for each TBF.

The end-user rate is shared equally between each TBF and is no less than 24 Kb/s for each TBF. MCS 9 is used for both TBFs.

Compare the files received with the files sent.

The files are received error free.

Case Ref.

Direction Distance Configuration Hopping mode

1. Uplink 5 Km 2 sectors each with 2 TRX (BB2F with TSxA+TSxB)

None

2. Uplink 5 Km Any None

DN0694168 Issue 2-0


16.9 Cell Reselection & Timing Advance with EGPRS

Purpose:

The purpose of these test cases is to check that cell reselection functions correctly with EGPRS data transfer and timing advance. Also check that combined IMSI/GPRS attach can be performed with timing advance.


Preconditions:

1. Use any configuration for BTS1 & BTS2 without PBCCH

2. Link adaptation is enabled (ZEQV: BTS=##: ELA=1;)

3. Timing advance is applied to BTS1 only

4. BA list is created containing BTS1 & BTS2 BCCH frequencies

Input Expected Output Turn on EGPRS mobile and attach to the specified BTS

Mobile performs combined IMSI/GPRS attach

Setup EGPRS data transfer in specified direction. MCS used uses at least one slave frame from EDAP

The transfer can be established on the source cell.

Use an adjustable attenuator to cause cell reselection during the data transfer.

Data transfer continues after cell reselection onto target cell.

The A-bis TRX links and PCU MASTER DATA frames are monitored on source and target cells. A-bis traces are recorded.

In the Packet Channel Request message, access delay represents the actual TA value. Post analysis of A-bis trace shows MCS used slave frame in both source and target cells

The reselection between cells is made at least 10 times for each test case.

DN0694168 Issue 2-0



Direction Hopping Mode (BTS1 / BTS2)

RA/LA Source Cell

Timing Advance

Configura-tion

1. Uplink RAH-hopping / Non-Hopping

RA & LA are same for both BTS

BTS1 0 Km Any

2. Downlink RF-hopping / No-hopping

RA is different for both BTS

BTS1 10 Km Any

3. Downlink BB-hopping / RF-hopping

LA is different for both BTS

BTS2 30 Km Any

4. Uplink RAH-hopping / Non-Hopping

RA & LA are same for both BTS

BTS2 10 Km Any

16.10 EGPRS Reliability at Various MS Speeds

Purpose:

To check that data transfer does not fail when the MS speed increases.


Note 93.

8-PSK modulations are more susceptible to MS speed than GMSK. Link Adaptation and Incremental Redundancy should cope with this without data transfer failing completely.

Preconditions:

1. Choose an EGPRS MS so that RLC Mode = Acknowledged RLC Mode.

2. Set Link Adaptation = ON

3. To set the maximum limit for block error rate to 50%.

Use the MML command ZEQV: BTS=##: BLA=50;

4. Check that no offsets are applied to the BEP values (See Note 82).

Input Expected Output Transfer a 1 MB file using the UDP/IP protocol in the direction shown below.


Slowly increase the MS speed from stationary to 200Km/h and back to stationary. Perform 3 times. Monitor the A-bis for BEP values and MCS used.

As MS speed increases the reported BEP increases. Link Adaptation responds accordingly and Incremental Redundancy recovers blocks successfully.

DN0694168 Issue 2-0


Case Ref.

Direction Configuration Hopping Mode

1 Uplink 2 sectors each with 2 TRX (BB2F with TSxA+TSxB)

None

2 Uplink Any None

3 Downlink Multi TRX RF Hopping

16.11 EGPRS Reliability at Various Distances

Purpose:

To check that data transfer does not fail when the MS distance varies over the full range (0 to 35Km).


Preconditions:

1. Use base station configuration as defined in test case with PBCCH

2. Choose an EGPRS MS so that RLC Mode = Acknowledged RLC Mode.

3. Set Link Adaptation = On

4. To set the maximum limit for block error rate to 90% (this is the default value)

Use the MML command ZEQV: BTS=##: BLA=90;

5. Check that no offsets are applied to the BEP values (see Note 82).

6. Start Monitoring the A-bis interface for TRX signalling and PCU frames

Input Expected Output Attach the MS to the sector. Attach is successful.

Promptly begin the transfer of a 2 MB file using the FTP in the direction shown below. Initiate the transfer from the terminal equipment at the MS end. Use the number of timeslots shown in the table.

An EGPRS PACKET CHANNEL REQUEST is seen on the A-bis which reports the timing advance corresponding to the distance of the MS. Data transfer begins and continues successfully.

As the transfer of one file completes, promptly begin the transfer of a new 2 MB file. Repeat this process until the MS reaches a distance of 0Km (if MS is moving towards BTS) and the final file completes its transfer.

Each new file transfer begins successfully. The correct timing advance is shown in the RANDOM ACCESS FRAME. The numbers of files shown in the table are required to fill the time that it takes for the MS to reach the base station.

DN0694168 Issue 2-0


Compare the files received with the files sent. Repeat the data transfer at least 4 times.

The received files are identical to the sent files.

Case Ref.

Direction No. Timeslots

Start Dist

Travel Configuration

1. Uplink 1 35Km Towards BTS with speed 120Km/hr

2 sectors each with 2 TRX (BB2F with TSxA+TSxB

2 Uplink 1 35Km Towards BTS with speed 120Km/hr

Any

16.12 RF Performance & Power Control

Purpose:

To check that EGPRS power level is equal to BCCH and speech burst power level varies with signal strength.

Test Tools Required: Spectrum Analyser Preconditions:

1. Use a Base Station with at least one 2 TRX sector with BCCH on TRX 1.

2. Dynamic A-bis is enabled.

3. Set BTS to use specified MCS(Disable link adaptation:ZEQV: BTS=##: ELA=0;

4. Set initial coding scheme: ZEQV: BTS=##: MCA=#, MCU=#;)

Input Expected Output Setup EGRPS data transfer on TRX 1 of Sector 1 using the time slot as specified in test case.

Data transfer begins.

Setup CS speech call on TRX 2 of Sector 1 using time slot as specified in test case. Setup another speech call on TRX1 on any time slot.

All calls are successful and unaffected by EGPRS.

Using spectrum analyser monitor power level of EGPRS & CS speech call timeslots

EGPRS power level is equal to BCCH (i.e. PMAX parameter). Speech call power level is dependent on signal strength

Attenuate UL & DL of CS speech call. Monitor A-bis.

EGPRS power level remains equal to BCCH. Speech call power level increases with attenuation. Power control message is seen on A-bis

Terminate both calls Calls terminated successfully.

DN0694168 Issue 2-0


Case Ref.

MCS CS speech Call Time Slot

EGPRS Data Time Slot

Download Direction

Configuration

1. 9 7(BCCH and Non-BCCH TRX)

7(BCCH and Non-BCCH TRX

Downlink Any EDGE

2. 2 5 51 Uplink Any 1One additional Data transfer must be done on TS7

16.13 Break (Air Interface and A-bis) in EGPRS

Purpose:

To check that EGPRS data transmission is able to recover after a short break in the Air interface / A-bis interface.

Test Tools Required: Signal Generator, Spectrum Analyser Air Interface Break Preconditions:

1. Disable link adaptation

(ZEQV: BTS=##: ELA=0;)

2. Set C/I = 15dB

Input Expected Output Setup EGPRS data transfer using MCS-9 in the downlink direction using TCP/IP. Monitor A-bis interface

Data transfer begins

Break air interface (UL/DL) for a period of 7 sec (based on counter N3101 and timer T3169 values).

TBF is released When air interface is re-established the TCP protocol will request data retransmission, a new TBF is established (P-CHANNEL REQUIRED message is seen on the A-bis) and data transfer continues

Terminate data transfer Repeat above steps 5 times

Data transfer terminated successfully.

DN0694168 Issue 2-0


Case Ref.

Configuration

1. Any Configuration (EDGE TRX Only)

Preconditions:

1. Disable link adaptation (ZEQV: BTS=##: ELA=0;)

2. Set C/I = 15dB

Input Expected Output Setup EGPRS data transfer using MCS-9 in the downlink direction using TCP/IP. Monitor A-bis interface


Break air interface (UL/DL) for a period of 55 sec (based on counter N3101 and timer T3169 values). Repeat 5 times

TBF is released In case of UDP data transfer new TBF will not be established

Case Ref.

Configuration



A-bis break

Input Expected Output Setup EGPRS data transfer using TCP/IP and using MCS-9 in direction specified in test case.


For a period of 10 seconds the whole A-bis is disrupted with random short (<0.5 s) breaks The link is then left connected until the link recovers. Terminate data transfer Repeat test 5 times.

After the link recovers, PCU frame resynchronises. Data continues to transfer. Very occasionally the A-bis may be broken while the BSC is polling the BTS. This will cause the LAPD to drop and the air interface to be disabled. It may take over 30 sec to recover the site once the A-bis is reconnected. During this time the TCP/IP connection will probably be dropped. It may also be necessary to re-activate the PDP Context.

DN0694168 Issue 2-0


Case Ref.

Configuration Direction

4. Any Uplink

16.14 GPRS transfer when EGENA is OFF

Purpose:

To check that GPRS attach is possible after EGENA is disabled from the BSC


Create the site as per the test case with GPRS and EGPRS enabled in the BTS.

Site is in supervisory state with no active alarms except “7801: Local MMI connected to the base station”.

Disable EGENA and DAP using following MML commands: ZEQS:BTS=<BTS ID>:L; ZEQV:BTS=<BTS ID>:EGENA=N; ZERS:BTS=<BTS ID>,TRX=<TRX ID>:L; ZERM:BTS=<BTS ID>,TRX=1:DAP=N; ZERS:BTS=<BTS ID>,TRX=<TRX ID>:U; ZEQS:BTS=<BTS ID>:U;

Sector resets and reaches supervisory state.

Switch ON test mobile Mobile latches on to the BCCH frequency and GPRS attach is performed successfully.

Check the alarms on the BSC No unexpected alarms appear. A Packet data transfer is started. Packet data transfer is successful. Monitor the A-bis and also the user data rate. In the PCU data frame the values for Coding

scheme & RX level are verified to be reliable The expected data rates for the coding scheme are achieved. (CS-1 approx. 9kbit/s per timeslot used and CS-2 is approx. 13.4kbit/s per timeslot).

Case Ref. Configuration 1 4 OMNI EDGE1 2 1 OMNI EDGE

1Data transfer on BCCH TRX and Non-BCCH TRX one by one

16.15 EDAP mismatch between BSC and the BTS Manager

Purpose: To check that EDAP mismatch between BSC and BTS Manager does not affect the (E)GPRS functionality.

Note 94. While defining the EDAP timeslots, the starting timeslots must be kept the same at both BSC & the BTS Manager.

DN0694168 Issue 2-0


Input Expected Output Create the site in the BSC as given in the configuration.

Site is created.

Enable GPRS & EGPRS using the MML command ZEQV.

GPRS/EGPRS are enabled successfully.

Define the number of EDAP TSs in the BSC as given.

EDAP timeslots are defined.

Commission the site wherein define the number of EDAP TSs in the Traffic Manager as given.

Site is commissioned successfully and is in supervisory state with no active alarms except “7801: Local MMI connected to the base station”.

Start an EGPRS Packet data transfer. EGPRS Packet data transfer is successful. Start a GPRS Packet data transfer with GPRS only capable phone.

GPRS Packet data transfer is successful.

Monitor the Abis and also the user data rate. In the PCU data frame the values for Coding scheme & RX level are verified to be reliable. The expected data rates for the coding scheme are achieved.

Number of EDAP TS Case Ref. Configuration BSC Traffic Manager

1 1 OMNI EDGE 3 4

17. EGPRS CHANNEL REQUIREMENT ON CCCH

17.1 EPCR Capability Reporting

Purpose:

The purpose of these cases is to check that the base station reports its ability to receive EGPRS Packet Channel Requests (EPCR) correctly to the BSC. Also check that the BSC informs the cell’s EPCR capability correctly to the MS.

Note 95.

When a base station resets it can report its EPCR capability in the BTS_OMU_STARTED message. The information element can be found as follows:

BTS_OMU_STARTED -> TRX HW Capability -> EPCR Capability

The EPCR is reported for each TRX present.,EDGE TRX should report as supporting EPCR on CCCH. GSM TRX should report as not supporting EPCR.

Note 96. The BSC informs the MS for the cell’s capability in the SYSTEM INFORMATION 13 message. The information element can be found as follows:

SYSTEM INFORMATION (1/13) -> GPRS Cell Options -> EGPRS PACKET CHANNEL REQUEST.

DN0694168 Issue 2-0


Input Expected Output Create and commission the site as per the configuration mentioned in the table. EGPRS is enabled and at least one EDGE TRX has GP timeslot configured on it.

Site is in supervisory state.

Reset the BCF from BSC. BCF resets successfully. Monitor the A-bis for BTS_OMU_STARTED message. Monitor the signalling links on the Abis for SYSTEM INFORMATION 13 messages. Monitor the air interface for the transmitted SI13 by the base station.

The TRX’s in the sectors indicated in the table below report the expected EPCR Capability in the BTS_OMU_STARTED message. The BSC sends the instruction as mentioned in the table below in the SI13 message to the BCCH TRX’s. The BCCH TRX’s transmit the instruction as mentioned in the table below on the air interface to the MS.

Case Ref.

Config Sector TRX Type

Channel Reported EPCR Capability

EPCR instruction to mobile

1 GSM BCCH CCCH Do not use EPCR

2 EDGE BCCH CCCH Use EPCR

1. 4+4+4

3 EDGE BCCH CCCH Use EPCR

1 EDGE BCCH CCCH Use EPCR 2. 2+2

2 GSM BCCH CCCH Do not use EPCR

17.2 PRACH Types on CCCH and PCCCH

Purpose:

To check that EGPRS Packet Channel Request types initiated by EGPRS capable MS are received by the base station and passed on to the PCU correctly. Also check that this occurs correctly from MS at different distances and under different fading conditions.


Note 97. For the configured BCCH channel the EGPRS Packet Channel Request appears on A-bis as a P-Channel required message containing an EGPRS PCR information element.

DN0694168 Issue 2-0


Note 98. The Access Burst Type parameter sent in the GPRS options in System Information 1 & 13 messages must be = 1 (11 bit access type). Currently, this is fixed at 1 in the BSC.

Input Expected Output Configure the site and the signalling channels as defined in the test case. Enable EGPRS and configure at least one GP timeslot in the sector. Enable 2-way diversity using MML command: ZEQM: BTS=<bts num>: RDIV=Y; Use an EGPRS MS with uplink capability shown in the table. Use an MS, which will use the RLC Mode shown in test case (See Note 79).

Site is in supervisory state. Gp is configured to a timeslot in the sector

Apply the distance and fading profile as shown in the table. When fading is used, allow the signal to pass to the RX port shown in the table. Block the other port using terminators.

Attach an EGPRS MS to the sector and activate a PDP Context. Monitor the signalling links on the Abis.

A P-CHANNEL REQUIRED message is seen on the A-bis containing an EGPRS PCR information element. The Uplink TRS Indicator corresponds to the type of MS used (TRS1=8PSK, TRS2=GMSK). The access burst type = Signalling or One Phase Access

Send one "ping" message to the IP server. A P-CHANNEL REQUIRED message is seen on A-bis containing an EGPRS PCR information element. The Uplink TRS Indicator corresponds to the type of MS used (TRS1=8PSK, TRS2=GMSK). The access burst type = Short Access Request or One Phase Access

DN0694168 Issue 2-0


Input Expected Output Transfer a 1Mb file in the uplink direction. During the transfer trigger a cell reselection. Observe the RACH message on the new cell, as the transfer is re-established.

Transfer starts successfully. A P-CHANNEL REQUIRED message is seen on the A-bis containing an EGPRS PCR information element. The Uplink TRS Indicator corresponds to the type of MS used (TRS1=8PSK, TRS2=GMSK). The access burst type = One Phase Access

While the MS is still in Ready mode (i.e. before the Ready timer has expired), send a "ping" message from the ftp server to the IP address assigned to the MS.

A PACKET CONTROL ACKNOWLEDGEMENT message is seen on the A-bis in a PCU RANDOM ACCESS FRAME on the PDCH assigned to the downlink TBF.

Case Ref.

BCCH timeslot

MS uplink capability

RLC Mode

Configuration

Dis-tance (Km)

Fading Profile

RX port

1. Ts0 = MBCCH Ts1 = SDCCH

8PSK Ack Any 0 HT100 Main

2. Ts0 = MBCCHC

8PSK Ack Any 0 HT100 Main

18. ENHANCED MEASUREMENT REPORTS (EMR)

Note 99. The FIFILE parameter EMR_SUPPORT_IN _BSC is enabled and activated at the BSC to allow Enhanced Measurement Reporting.

Note 100. The INVALID_BSIC_REPORTING parameter is set to 0 (cells that are not neighbours but have correct NCC are not reported) unless otherwise stated.

Note 101. The following setup is used for the EMR test cases unless otherwise stated.

A 2+1+1 site is in use. Each BTS has the same NCC but a different BCC. The calls are made on BTS 1 (having 2 TRX) and the other sectors are the neighbours.

BTS power levels are set as follows: This is to cause the MS to camp onto BTS 1.

BTS 1, PMAX = 16

DN0694168 Issue 2-0


BTS 2, PMAX = 30

BTS 3, PMAX = 30

The test is performed either in a screened room, or a cabled environment, so that the MS can only see the three BTS.

A MS that supports Enhanced Measurement Reporting is selected. The MS is switched on and it is verified In the Field Test software that BTS TEST = OFF, so that the MS can see the neighbouring cells. The MS is therefore not locked to the BTS.

Note 102. The SACCH FILLING contains the MEASUREMENT INFORMATION message. The following parameters are present:

Report Type

Reporting Rate

Invalid BSIC Reporting

BSIC description

Real Time Difference description (RTD)

Report Priority description

Measurement Parameters description

3G Neighbour Cell description

3G Measurement Parameters description

The 3G related parameters in EMR message would be present only when 3G neighbours are defined and RTD parameter will be present only when LMU is configured to be used for Position Based Service (PBS).

Note 103. The MEASUREMENT INFORMATION message is sent to the TRX when it resets in the SACCH FILLING message on the BTSM layer. In the CHANNEL ACTIVATION message the TRX is told which System Information messages (including the Measurement Information message) must be transmitted on the SACCH.

Note 104. Enhanced Measurement Reports are not supported on the SDCCH (i.e. during call Setup). Once a call has been established on a TCH the mobile at first sends ordinary Measurement Reports. The base station is required to send higher priority System Information messages on the SACCH before it sends the Measurement Information message. Only after the MS receives the Measurement Information message on the SACCH can it begin to send Enhanced Measurement Reports.

DN0694168 Issue 2-0


18.1 (E)MR sending in response to Measurement Information Message

Purpose:

The purpose is to verify that the Enhanced Measurement Reports or Measurement Reports messages are being correctly sent when requested by the Measurement Information message.


Input Expected Output The BCF is setup as per the configuration Note 101. The hopping mode given in the configuration against the test case is only for BTS1.

The BCF is setup successfully with hopping enabled in the first sector.

The serving cell has IDLE and MEAS BA lists attached as defined in the test cases.

The IDLE and MEAS BA lists are successfully attached.

Reset the BTS. The BCF is reset successfully. Monitor the Abis for SACCH FILLING messages within the SI BEGIN and SI END messages.

The SACCH FILLING contains the MEASUREMENT INFORMATION message. The parameters present are as shown in [Note 102] The Invalid BSIC Reporting is set to 0 and the Report type is shown as listed below. NO IDLE and MEAS BA Lists attached: The report type is set to 0 (This means The MS shall use the Enhanced Measurement Report message for reporting if at least one BSIC is allocated to each BA (list) frequency. Otherwise, the Measurement Report message shall be used.) IDLE and MEAS BA Lists attached: The report type is set to 1 (This means The MS shall use the Measurement Report message for reporting.)

Make a speech call to a PSTN number or an MS locked to a completely separate BTS.

The Speech call is successful. The value of UL and Downlink quality reported in Measurement Result and Measurement Report is predominantly ‘0’.

Monitor the TRXSIG for BTS 1 on the Abis for MEASUREMENT RESULTS / MEASUREMENT REPORT messages.

NO IDLE and MEAS BA Lists attached: Enhanced Measurement Reports (Layer 3) are sent up the Abis (taking into account Note 104). IDLE and MEAS BA Lists attached: Measurement Reports (Layer 3) are sent up the Abis.

Terminate the call. The call is terminated.

Case Ref. IDLE and MEAS BA Lists attached

Hopping Configuration

1. No RAH-hopping As per Note 101

2. No BB-hopping As per Note 101]

DN0694168 Issue 2-0


Input Expected Output The BCF is setup as per the configuration Note 101. The hopping mode given in the configuration against the test case is only for BTS1.

The BCF is setup successfully with hopping enabled in the first sector.

The serving cell has IDLE and MEAS BA lists attached as defined in the test cases.

The IDLE and MEAS BA lists are successfully attached if mentioned in the test case.

Setup a fading simulator for simulating a varying TA corresponding to 0km from the BTS to 10km from the BTS and back with a speed of 200km/hr.

The parameters are set successfully and simulation is started on the Fading simulator.

Connect an MS to the output of Fading simulator and place it in a screen box. Latch On the MS to the BTS.

The MS is latched on to the BTS successfully.


The Speech call is successful.

Monitor the TRXSIGs for the messages on the ABIS.

Enhanced Measurement Reports (Layer 3) are sent up the Abis (taking into account Note 104).

Monitor the value of TA and speed displayed in the EMR.

The speed and TA value is correctly displayed in EMR report.

Case Ref. IDLE and MEAS BA Lists attached

Hopping Site Type

3. No BB-hopping As per Note 101

Purpose:

To check that the base station forwards the Measurement Information message correctly to the MS. The test does this by changing parameters at the BSC, which are included in the Measurement Information message and checking for the response from the MS.

To check that the base station correctly includes the (layer 3) Enhanced Measurement Report information element in the Measurement Results message.

Note 105. The purpose of Measured BA list which is used to switch EMRs on and off, is outlined in feature BSS11085.This mentions the interaction with the use of Enhanced Measurement Reports. The REPORT TYPE information element in the Measurement Information message is affected depending upon whether IDLE BA is attached and MEAS BA is enabled or not.

Note 106. Two other information elements within the Measurement Information message are toggled during this test. These are INVALID_BSIC_REPORTING and SCALE_ORD.

INVALID_BSIC_REPORTING allows or prohibits the MS from reporting neighbouring cells which are not valid (i.e. have not been defined as adjacent, or included on the BA list), but have the same Network Colour Code (NCC) as the serving cell.

DN0694168 Issue 2-0


SCALE_ORD enables the MS to report RX levels between –37dBm and –47dBm. It does this by offsetting the reported RX level by 10dB (described as “scaled by 10dB). When the measurements are “scaled”, an RX level of

63 means –37dBm

0 means –100 dBm.

Note 107. MEASUREMENT INFORMATION message (with Report Type equal to 1) could be sent by the BSC if the ISHO feature is activated at the BSC even when the BA list is attached to the sector as an IDLE BA list and MEAS BA LIST is enabled.

Equipment and BTS Set-Up For MetroSite, one sector with at least 2 TRX in any base station configuration may be used. For MetroSite use a sector with the EDGE/non-EDGE capability specified in the test case.

For UltraSite use a 2TRX sector with the following combinations:

Config BB2 TRX 1 TRX 2

non – EDGE BB2A TSxA TSxA

EDGE BB2F TSxB TSxB

mixed BB2F TSxA TSxB

The sector being used for this test must have 2 neighbours, which are transmitting, so that the MS can report the RX level for each. Only one of the neighbours is defined as an adjacent cell to the sector being used for this test. The other neighbour available is not defined as an adjacent cell but has the same NCC value as the sector being used for the test. This neighbour needs to be defined with a different BCC to the sector being used for the test.

In order for the MS to see the neighbours it will not be possible to lock the MS to the serving cell using the field test software. For this reason it may be necessary to perform the test in a screened room, or using a cabled RF environment.

Use a mobile station which supports Enhanced Measurement Reports (e.g. Jessie).


Create a BA list, which includes the neighbours of the sector plus 2 or 3 other frequencies. Use MML command: ZEBC:<id>,<band>:<f1>&<f2>&<fn>;

The BA list is successfully created at the BSC.

Lock the sector at the BSC. The sector is locked successfully. Lock TCH timeslots to force calls onto the BCCH / non-BCCH TRX indicated in the test case table. Also set the hopping mode as indicated.

The timeslots are locked successfully. The hopping mode is set.

DN0694168 Issue 2-0


Input Expected Output Attach the BA list to the sector as an IDLE BA list. Also enable MEAS BA LIST. Use MML command:ZEQB:BTS=<bts num>:MEAS=Y,IDLE=<id>, ACT=IDLE;

The BA list is attached to the sector as IDLE BA list. MEAS BA list is enabled for the sector.

Whilst monitoring the A-bis for SACCH FILLING messages within the SI BEGIN or SI END messages, unlock the sector.

The BSC does not send any MEASUREMENT INFORMATION messages (thus indicating that the MS shall use Measurement Reports) [Note 107].

Make a speech call (of the type shown in the test case table below) to a PSTN number or an MS locked to a completely separate BTS. Monitor the TRXSIG of the sector on the A-bis for MEASUREMENT RESULTS / MEASUREMENT REPORT messages.

The BTSM layer MEAS. RES. Message contains the MEASUREMENT REPORT message. The message contains the RX measurements for the current cell and RX level measurements for the frequencies in the BA list.

End the call. The call is ended successfully. Lock the sector. The sector is locked successfully. Detach the IDLE BA and the MEAS BA lists using MML command: ZEQB:BTS=<bts num>:MEAS=N,IDLE=0, ACT=ADJ;

The IDLE and MEAS BA lists are detached.

Set INVALID_BSIC_REPORTING to 0 (cells that are not adjacent but have correct NCC are not reported). Use the MML command: ZEHN:BTS=<bts num>::IBR=0;

The Invalid_BSIC_Reporting is set to 0.

Set SCALE_ORD to 0 (not scaled) using MML command: ZEQM:BTS=<bts num>:SCO=0;

Scale_ORD for the sector is set to 0.

Whilst monitoring the A-bis for SACCH FILLING messages within the SI BEGIN or SI END messages, unlock the sector.

The SACCH FILLING contains the MEASUREMENT INFORMATION message. The REPORT TYPE = 0, INVALID_BSIC_REPORTING = 0, SCALE_ORD = 00.

Make a speech call to a PSTN number or an MS locked to a completely separate BTS. Monitor the TRXSIG of the sector on the A-bis for MEASUREMENT RESULTS / MEASUREMENT REPORT messages.

The BTSM layer MEAS. RES. message contains the ENHANCED MEASUREMENT REPORT message. The message contains the RX measurements for the current cell and RX level measurements for the one adjacent cell. The REPEATED_INVALID_BSIC_INFORMATION section is not present. The parameter SCALE = 0 (not scaled)

End the call. The call is ended successfully. Lock the sector The sector is locked successfully. Set INVALID_BSIC_REPORTING to 1 (cells that are not adjacent but have correct NCC are reported). Use the MML command: ZEHN:BTS=<bts num>::IBR=1;

The Invalid_BSIC_Reporting is set to 1.

Set SCALE_ORD to 1 (scaled by 10dB) using MML command: ZEQM:BTS=<bts num>:SCO=1;

Scale_ORD for the sector is set to 1.

DN0694168 Issue 2-0


Input Expected Output Whilst monitoring the A-bis for SACCH FILLING messages within the SI BEGIN or SI END messages, unlock the sector.

The SACCH FILLING contains the MEASUREMENT INFORMATION message. The REPORT TYPE = 0, INVALID_BSIC_REPORTING = 1, SCALE_ORD = 01.

Make a speech call to a PSTN number or an MS locked to a completely separate BTS. Monitor the TRXSIG of the sector on the A-bis for MEASUREMENT RESULTS / MEASUREMENT REPORT messages.

The BTSM layer MEAS. RES. message contains the ENHANCED MEASUREMENT REPORT message. The message contains the RX measurements for the current cell and RX level measurements for the one adjacent cell. The REPEATED_INVALID_BSIC_INFORMATION section is present. It reports the RX level of the cell which was not defined as adjacent. The parameter SCALE = 1 (scaled by 10dB)

End the call. The call is ended successfully. Case Ref. Config BCCH / non-BCCH Hopping Call Type

9 2+2 common BCCH, EDGE

non-BCCH non – hopping EFR

10 Mixed non-BCCH RF-Hopping AHS

18.2 Invalid_BSIC_Reporting Response

Purpose:

The purpose of these cases is to verify that the Measurement Information messages have been correctly sent by checking that the resulting Enhanced Measurement Reports from the MS correctly reflect the format specified by the Measurement Information messages.

To check that the reporting of neighbours with same NCC but different BCC is possible by setting Invalid_BSIC_Reporting to 1 and reporting of such neighbours is switched off by setting Invalid_BSIC_Reporting to 0.

Input Expected Output The configuration is setup as defined in Note 101. The hopping mode is only for BTS1.

The configuration is defined successfully.

Lock up traffic channels to force calls to be made on the TRX shown in the table of test cases below.

The traffic channels are locked up such that the channel allocated for the call is on the TRX mentioned in the test case.

Create a invalid neighbour BTS3 by ZEAC command using a BTS which is defined at different BSC (put all its parameter correctly e.g. freq, MCC, MNC, LAC except BCC)

The neighbour is defined successfully.

DN0694168 Issue 2-0


Input Expected Output Set INVALID_BSIC REPORTING to 0 (cells that are not neighbours but have correct NCC are not reported). Use ZEHN command for this purpose.

INVALID_BSIC REPORTING is set as off for the sector under test.

Reset the BTS. Monitor the Abis for SACCH FILLING messages within the SI BEGIN or SI END messages. Check both the BCCH and non-BCCH TRX.

The SACCH FILLING contains the MEASUREMENT INFORMATION message. The parameters present are as shown in Note 102. The Report type and the Invalid BSIC Reporting are both set to 0.

Make a call as specified in test case to a PSTN number or an MS locked to a completely separate BTS.



Enhanced Measurement Reports (Layer 3) are sent up the Abis (taking Note 104 into account). They only contain RX level information for BTS 2 (in the REPORTING_QUANTITY bit map). They do not contain RX level information for BTS 3 (no REPEATED_INVALID_BSIC_INFORMATION present).

Terminate the call. The call is terminated successfully. Set INVALID_BSIC_REPORTING to 1 (cells that are not neighbours, but have the correct NCC are reported). Use ZEHN command for this purpose. Monitor the Abis for SACCH FILLING messages.

The Invalid_BSIC_reporting is set to 1 for the sector under test. A SACCH FILLING containing a MEASUREMENT INFORMATION message is sent down the Abis. This time the Invalid BSIC Reporting parameter is set to 1.




Enhanced Measurement Reports (Layer 3) are sent up the Abis. This time, they also contain RX level information for BTS 3 (REPEATED_INVALID_BSIC_INFORMATION is present).

Terminate the call. The call is successfully terminated.

Case Ref. TCH Configuration

Call Type TRX Site Type Hopping

1. TCHF EFR Non-BCCH As per [Note 101]

BB-hopping

2. TCHF AFS BCCH As per [Note 101]

Non-hopping

3. TCHH AHS Non-BCCH As per [Note 101]

RAH-hopping

4. TCHD 2+2 TS, 9600 NT, Data call

BCCH As per [Note 101]

RF-hopping

DN0694168 Issue 2-0


18.3 SCALE_ORD Response

Purpose:

The purpose is to verify that the MS is implementing the SCALE value set by the user in the EMR message.

Input Expected Output The configuration is setup as defined in Note 101. The site is defined successfully and the BCF is in

supervisory state. Lock up traffic channels to force calls to be made on the TRX shown in the table of test cases below.

The channels are locked successfully.

The SCALE_ORD (ZEQM) parameter is set to that specified in the test case. This parameter defines an offset that shall be added to the reported downlink signal level before using it for handover and power control decisions and in the updating of statistics.

The SCALE_ORD parameter is set as per the test case

Reset the BTS. The BTS is reset successfully. Monitor the Abis for SACCH FILLING messages within the SI BEGIN or SI END messages. Check both the BCCH and non-BCCH TRX.

The SACCH FILLING contains the MEASUREMENT INFORMATION message. The parameters present are as shown in Note 102. The Report type and the Invalid BSIC Reporting are both set to 0. The Measurement Parameters description shows the correct SCALE_ORD value.


The call is successful


Enhanced Measurement Reports (Layer 3) are sent up the Abis (taking into account Note 104). The SCALE information represents the SCALE_ORD value set.

Terminate the call. Call terminated successfully.

Case Ref. TRX Configuration

Call Type TRX Site Type SCALE value

1. TCHF EFR BCCH As per [Note 101]

0 (NO)

2. TCHF AFS Non-BCCH As per [Note 101]

1 (scaled by 10dB)

3. TCHF FR Non-BCCH As per [Note 101]

1 (scaled by 10dB)

DN0694168 Issue 2-0


18.4 Reporting Priority of Neighbouring Cells

Purpose:

The purpose is to verify that the EMR reports the correct amount of Neighbours as well as reporting WCDMA neighbours.

Note 108. The test is performed either in a screened room, or a cabled environment.

Note 109. BTS power levels are set so that the MS shall lock onto the serving BTS.

Input Expected Output The BCF containing the serving cell is synchronised using the LMU. This shall force the measurement Information message to be transmitted in 2 instances. The sector in use that has six neighbours Setup, which consist of the same band to that of the serving cell. A further 15 GSM neighbours are Setup, which consist of a different band to that of the serving cell.

The Site is defined and synchronized using an LMU. The BCF is in supervisory state. The neighbours are configured as per the test case.

A MS that supports Enhanced Measurement Reporting is selected. The MS is switched on and it is verified In the Field Test software that BTS TEST = OFF, so that the MS can see the neighbouring cells.

The MS locks onto BTS 1 and starts to report the DL power level of neighbouring cells.

The Measurement Parameters are Setup as defined in the Test cases.

The parameters are set up successfully.

Reset the BTS. The BTS reset is successful. Monitor the Abis for SACCH FILLING messages within the SI BEGIN or SI END messages.

The SACCH FILLING contains the MEASUREMENT INFORMATION message. The parameters present are as shown in Note 102.




Enhanced Measurement Reports (Layer 3) are sent up the Abis (taking into account Note 104). The number of neighbours being reported and the priority in which these are reported are as requested in the measurement information message.

End the call. The Call is terminated successfully.

DN0694168 Issue 2-0


REPORTING Parameter type Priority values Case Ref. SERVING_ BAND

MULTIBAND

FDD_ MULTIRAT

INVALID_ BSIC

Site Type Call Type

1. 3 0 01 0 As per [Note 101]

EFR

2. 0 3 0 0 As per [Note 101]

AFS

3. 0 0 3 0 As per [Note 101]

AHS

18.5 Uplink RX Quality Measurement

Purpose:

The purpose is to verify that the quality of the uplink radio signal is accurately reflected in the measurements reported by the base station to the BSC.

Test Tools Required: Variable Attenuator, Signal Generator, Spectrum Analyser

Note 110. The RX level, RX quality, Mean BEP, CV BEP and UL FER are part of Meas Results message and not part of the Enhanced Measurement Report Layer 3 message.

The Mean BEP, CV BEP and UL FER are coded in Suppl Info field in the Measurement Result in the BTSM layer.

When DTX is on the RxQual Full will always be reported as 7 and may be ignored. The RxQual Sub should reflect the true radio conditions

.

Note 111. The test case should be carried out in a cabled environment only. Ensure that there is no direct path from the MS to the base station through the air. The mobile must be in a screened box. All cable connections must be correctly tightened.

Input Expected Output Define a BCF as per the test case. Use any configuration that allows 2-way diversity. For the BB hopping cases use a sector with 2 TRX. Set uplink DTX and hopping mode as shown in the table. The hopping mode is for BTS1.

The site is defined successfully and the BCF comes up in supervisory state. The DTX and hopping mode is set as per the test case.

Set 2-way diversity on. The main and diverse receiver paths must each be tested separately.

The RF path is setup so as to test the main and diversity paths separately.

DN0694168 Issue 2-0


Input Expected Output Fix the transmit power of the MS to near its minimum using the following MML command: ZEQM:BTS=##:PMAX1=7,PMAX2=6,PMIN=7; This stops the carrier power from varying during the test, and minimises the chances of a leakage signal via the air reaching the base station.

The MS power is set to minimum so as to prevent any leakage signal from reaching the BTS.

Make a speech call of the call type shown in the table to a PSTN number or an MS locked to a completely separate BTS.

The speech call is successful

Monitor the TRXSIG for BTS 1 on the A-bis for MEASUREMENT RESULTS messages. Adjust the variable attenuator so that the signal level seen at the base station is reported as –84 to –85dBm.

The variable attenuator is adjusted to get the required UL level at the BSC.

With the interferer switched off, measure the power of the uplink bursts. Calculate the input power at the receiver taking into account the coupler, any attenuators and any duplexers in the path.

The input power to the receiver is between –83 and –88 dBm.

Disconnect the call. The call is terminated. Setup the signal generator to provide a continuous interferer, with digital modulation = GSM standard. Set the reference level to 10dB below the uplink carrier power measured above (i.e. C/I = 10dB). Switch off the interferer.

The signal generator is connected and the interference level is set to get the required C/I.

Make a speech call to a PSTN number or an MS locked to a completely separate BTS. Check that the carrier power is the same as previously measured. Switch on the interferer (make any slight adjustments to the level if carrier power has changed).

The speech call is successful. The carrier power is adjusted if required, so that the carrier power is the same as measured earlier.

Monitor the A-bis for MEASUREMENT RESULT messages. Record a trace for 1 minute at C/I = 10dB. Reduce the C/I in 1dB steps from 10 to 0dB, recording a 1 minute trace for each.

The trace is recorded successfully.

Disconnect the call, and switch off the interferer. The call is terminated successfully and the interferer is switched off.

Analyse the traces for UL mean BEP, UL FER and… DTX off - RxQual Full DTX on - RxQual Sub UL mean BEP remains zero for NT Data Call.

The UL mean BEP, UL FER and RxQual are within the limits shown below.

DN0694168 Issue 2-0



Call Type Hopping Mode UL DTX activation

Configuration Limits

1. EFR NAH-hopping (for EDGE sector)

ON 2(EDGE)+2(GSM)

See Table 5 and Table 6

2. AFS BB-hopping ON As per Note 101


3. AHS Non-hopping OFF As per Note 101


4. 2+2 TS NT 9600 Data call

RAH-hopping OFF As per Note 101


5. FR RF-hopping OFF As per Note 101


6. AHS Non-hopping ON As per Note 101


7. AFS BB-hopping ON As per Note 101


Table 5 RxQual and UL BEP

Rx Qual level reported UL mean BEP level reported C/I dB

Max Min Max Min

10 0 0 31 31

9 0 0 31 31

8 0 0 31 25

7 1 0 31 19

6 3 0 24 15

5 4 1 19 11

4 5 3 14 8

3 6 4 11 5

2 6 5 8 4

1 7 6 6 3

0 7 6 4 1

DN0694168 Issue 2-0


Table 6 UL FER

UL FER reported C/I dB

Max Min

10 0 0

9 0 0

8 0 0

7 0 0

6 0 0

5 0 0

4 0 0

3 3 0

2 11 0

1 17 0

0 20 1

18.6 Downlink Frame Erasure Rate (FER) Measurement

Purpose:

The purpose is to verify that the Downlink Frame Erasure Rate (FER) is calculated and reported correctly when DL DTX is off and is not being calculated/ reported when DL/UL DTX is on.


Input Expected Output The BCF is defined as per the test case. The BCF is defined successfully and comes in

supervisory state. A MS that supports Enhanced Measurement Reporting is selected. The attenuation at the TX path is adjusted until the BTS power level seen by the MS is -50dBm.

The power level seen by the MS is -50dBm.

DN0694168 Issue 2-0


Input Expected Output Make a speech call to a PSTN number or an MS locked to a completely separate BTS. The call is held for 30 minutes.


Monitor the TRXSIG for BTS 1 on the Abis for MEASUREMENT RESULTS / MEASUREMENT REPORT messages. The RX level, RX quality, Mean BEP, CV BEP. The ‘Supplementary Information Field’ within the Enhanced Measurement Report is also decoded and the FER is calculated to verify that it is being reported correctly.

Enhanced Measurement Reports (Layer 3) are sent up the Abis (taking into account Note 104). The RX level, RX quality, Mean BEP, CV BEP and FER accurately reflect actual input signals. The DL FER is showing zero interference when DL DTX-OFF. When the UL/DL DTX is ON and there is speech in the DL / UL, DTX is shown as ‘off’ and the DL / UL FER is sent. When there is silence, DTX is shown as ‘on’ and the DL and UL FER is not sent.

Terminate the call. The call is successfully terminated

The signal generator is switched on and the level is adjusted to produce enough interference i.e. C/I is set to 5dB.

The C/I is set to 5dB.

Make a speech call to a PSTN number or an MS locked to a completely separate BTS. The call is held for 30 minutes.


Monitor the TRXSIG for BTS 1 on the Abis for MEASUREMENT RESULTS / MEASUREMENT REPORT messages. The RX level, RX quality, Mean BEP, CV BEP. The ‘Supplementary Information Field’ within the Enhanced Measurement Report is also decoded and the FER is calculated to verify that it is being reported correctly.

Enhanced Measurement Reports (Layer 3) are sent up the Abis. The RX level, RX quality, Mean BEP, CV BEP and UL FER accurately reflect actual input signals. When DL DTX-OFF, then the DL FER reflects the interference being introduced. When UL/DL DTX-ON, then DL or UL FER is not sent depending on the DTX on

End the call. Call is terminated successfully

Case Ref. Call Type DTX MODE Configuration

1. . EFR UL DTX-OFF, DL DTX-OFF

As per Note 101e

2. . EFR UL DTX-ON, DL DTX-ON

As per Note 101

3. . EFR UL DTX-ON, DL DTX-OFF

As per Note 101

4. . AFS/Fast LA UL DTX-OFF, DL DTX-ON

As per Note 101

5. . AHS/Slow LA UL DTX-ON, DL DTX-ON

As per Note 101

6. . EFR UL DTX-ON, DL DTX-ON

3(EDGE) +2(GSM). DFCA enabled in EDGE sector. Testing to be done on DFCA sector.

DN0694168 Issue 2-0


Input Expected Output 7. AFS1 UL DTX-ON, DL

DTX-OFF Hybrid configuration use N95 MS

1Ensure that voice quality is good. Also listen to speech and verify that there is no distortion.

Purpose: To check that the RXQUAL and FER values are reported properly after EMR activation.

Input Expected Output Configure the site as defined in the test case. The site is in supervisory state with no unexpected

alarms. Deactivate EMR support in BSC by MML command ZWOA

EMR support in BSC is deactivated successfully.

Make a number of calls in the site and keep the calls ongoing.

All calls are successful

Monitor the RXQUAL and FER values reported in Abis traces.

The reported RXQUAL and FER values are predominantly zero.

Now activate EMR support in BSC by MML command ZWOA

EMR support in BSC is activated successfully.

Monitor the RXQUAL and FER values reported in Abis traces.

There should be no change in the reported RXQUAL and FER values after the activation of EMR support in BSC.

Case Ref. BCF Configuration Type of calls 8 2+2 EDGE AFS + AHS 9 4 Omni EDGE AFS + AHS

18.7 Averaging of Enhanced Measurement Report (EMR)

Purpose:

The purpose is to verify that the EMR is reporting correctly when averaging is active.


Note 112. A single averaging period is 480ms. The maximum value for this parameter is 4, which means that four reports are averaged into one report and there is 1920ms interval between the measurement reports.

Input Expected Output The configuration is setup as defined in Note 101. The hopping mode is for BTS1.

The configuration is defined successfully and hopping mode set for BTS1.

DN0694168 Issue 2-0


Input Expected Output The signal path stated in the test case is attenuated using a variable attenuator. The attenuation is varied so that different signal levels are being received during the averaging period.

The signal level can be successfully varied using the variable attenuator.

Make call to a PSTN number or an MS locked to a completely separate BTS as specified in test case. The call is held for 10 minutes.

Enhanced Measurement Reports (Layer 3) are sent up the Abis (taking into account Note 104) with the intervals specified by the averaging period.

Monitor the TRXSIG for BTS 1 on the Abis for MEASUREMENT RESULTS / MEASUREMENT REPORT messages. The RX level, RX quality, Mean BEP, CV BEP and UL FER are checked for accuracy.

All the fields in the EMR are being reported correctly and the fields for RX level, RX Quality, Mean BEP, CV BEP are being averaged. The supplementary information contains more information the longer the averaging period as it is representing the measurement reports over the averaging period and not the single measurement report.

Terminate the call. The call is terminated successfully.

Case Ref.

Call Type

Hopping Mode

Cell(s) attenuated

Path attenuated

Averaging Period

Configuration

1. EFR NAH-hopping

Serving UL 2 As per Note 101

2. EFR BB-hopping

Serving DL 3 As per Note 101

3. AFS RF-hopping

Neighbour DL 4 As per Note 101

4. AHS RAH-hopping1

Serving DL 2 As per Note 101

5. 2+2 9600 NT

Non-hopping


6. 3+1 14400 NT

RAH-hopping


7. EFR NAH-hopping/ DFCA

Serving UL 2 2(EDGE) +3(GSM), DFCA enabled in GSM sector. Test to be done on DFCA sector

8. EFR BB-hopping


9. EFR BB-hopping

Serving DL 3 As per Note 101,EDGE HW2

1Use BSC SW S13 2UL DTX=ON, Use N95 and 6200 MS

DN0694168 Issue 2-0


18.8 Reporting of correct TA value under high interference and load conditions

Purpose: To check that the TA value is correctly reported under high interference and load conditions.

Note 113.

The test cases must be performed with Rx diversity enabled at the BSC unless otherwise stated.

Equipment and BTS Set-Up Fading Simulator, signal generator

The BCF is in commissioned state.

Input Expected Output The site is up and working as per the configuration defined in the test case.

The Site is in supervisory state with no active alarms except “7801: MMI CONNECTED TO BASE STATION: Local MMI Connected”.

Set up the fading simulator to simulate the TA according to the distance and speed mentioned in the test case.

The fading simulator is setup successfully.

Start the simulation of the TA via the fading simulator.

The TA simulation is started from the fading simulator.

Make 10 calls covering each call type namely (AFS, AHS, EFR, FR, HR).

The calls are successful.

Generate interference using a signal generator and vary the interference such that C/I varies between 27db and 5 db throughout the test case.

The interference is generated using a signal generator and C/I varied through the test case.

Capture the TRX signalling link traces for each TRX via the Abis trace analyser.

The quality of the call will vary as interference is varied.

Observe the Abis Traces for the reported TA values.

The TA should be reported correctly for every call.

This test case is run for 1hr. Record the ABIS trace over this period.

The ABIS trace is recorded successfully.

During the test case periodically observe the TA values reported.

The TA values are correctly reported throughout the test case.

Case Ref. Configuration Speed/distance 1 Any configuration using GSM hardware 60km/hr, 0-30Kms and back

DN0694168 Issue 2-0


18.9 Bad UL SACCH Frames

Purpose:

The purpose is to verify that the Enhanced Measurement Report message is discarded and nothing is done for it if the received SACCH block is bad but however the BTS uplink Measurements are handled normally.

Note 114. The test cases must be performed with RLT and ARLT set to 64 at the BSC.

Test Tools Required: Variable Attenuator, Spectrum Analyser, and Signal Generator

Input Expected Output Make a site with configuration and hopping as described in test case.

The site is successfully defined and hopping enabled. The site is in supervisory state.

A MS that supports Enhanced Measurement Reporting is selected. The MS is switched on and it is verified in the Field Test software that BTS TEST = On, so that the MS cannot hand over to any neighbouring cells.

The MS locks onto the BTS.


The speech call is successful


Enhanced Measurement Reports (Layer 3) are sent up the Abis (taking into account Note 104).

Interference is added in the uplink until Enhanced measurement reports cannot be decoded. Important: Interference should be with in RLT/ARLT time limits

The Enhanced measurement reports cannot be decoded and therefore are no longer reported. The UL measurement message results are still being reported.

Interference is reduced in the uplink until Enhanced measurement reports can be decoded.

The Enhanced measurement reports can be decoded and therefore are reported. The UL measurement message results are still being reported.

End the Call. Call is terminated successfully.

DN0694168 Issue 2-0



Configuration Call Type Hopping Mode

1. 2N- TRX+2DFCA TRX with EDGE HW

EFR, Call is on Non-BCCH Non-DFCA TRX

No-hopping

2. 2+2 AFS Non-hopping 3. 2+2 AHS RAH-hopping 4. 2+2 EFR BB-hopping 5. 5

OMNI,[3(GSM) N-TRXs+2(EDGE) DFCA TRXs]

EFR RF-hopping

19. ECELL

Note 115.

The standard ECell configuration is defined as 2 N-TRX + 2 E-TRX, combiner less, in a BTS. All TRXs are EDGE capable. MHAs may be used, in which case all TRXs should have one.

Note 116. RF TA rig is a set up of equipments (fading simulator and signal generator) that allow signal delay on the air interface so that distance can be simulated.

Note 117. ECell configuration test cases are to be executed on UltraSite only. Tests will be performed with BB2F unless otherwise stated.

Note 118. The TA value for the E-Area can be calculated by subtracting the Extension Radius from the distance between BTS and MS. Then dividing the result by 0.553 and rounding up to nearest integer and the TA value for the N-Area can be calculated by dividing the distance between MS and BTS by 0.553.

Note 119. Expected throughput for (HS) CSD:

Data Rate

bps Minimum transfer time for 1MB (seconds)

Maximum transfer time for 1MB (seconds)

2400 3495 4194 4800 1748 2098 9600 874 1049 14400 583 700 19200 437 524

DN0694168 Issue 2-0


28800 291 349 38400 218 262 43200 194 233 57600 146 175

Note 120. GPRS and EGPRS throughput should lie between 85% and 100% of the maximum

theoretical value. Convert from Kbyte/s to Kbit/s by multiplying by 8.47.

CS or MCS Max theoretical Data Rate (Kbit/s)

85% of theoretical max (Kbit/s)

CS1 8 6.8 CS2 12 10.2

MCS1 8.8 7.48 MCS2 11.2 9.52 MCS3 14.8 12.58 MCS4 17.6 14.96 MCS5 22.4 19.04 MCS6 29.6 25.16 MCS7 44.8 38.08 MCS8 54.4 46.24 MCS9 59.2 50.32

The above throughput values are based on 1 GP RTSL.

19.1 ECell ERACH Success Rate

Purpose:

To check that the ERACH success rate is consistently detected across the range of the E-Area with maximum Extended Radius.

Equipment and BTS Set-Up

Test equipment: RF TA rig, attenuators, combiners, traffic generator with at least 16 MS

Input Expected Output Set up a site as per the test case. Set the radius extension to 35 km. for ECell BTS

Site is in supervisory state. Extended radius is set to 35 km.

Set up the RF TA rig so that the distance varies throughout the range of the extended radius.

RF TA rig is working.

Connect 15 of the phones to the RF TA rig and perform a location update by resetting them. Keep the last phone in the N-Area

The RF TA rig should be configured so that the MSs start off in the N-Area. NetMonitor screen 01.01 displays the TA value. These should correspond to all phones being located in the N-Area, at 35 km, TA is 63.

Monitor OMUSIG and TRXSIGs on the A-bis trace, start traffic generator and make calls.

Call success rate is greater than 99%.

DN0694168 Issue 2-0


Input Expected Output Over a period of at least 8 h, change the distance between MSs and the BTS. The following distances are to be tested: 30, 35, 40, 45, 50, 55, 60, 65, 70, 75 (km).

When distance is 35, the phones should be handed over to E-Area. Call success rate within E-Area is greater than 99%. When distance is above 70 km, phones will be out of range and calls should fail (In a lab environment, this may not be the case and the calls may succeed even outside the E-Area at 75 km.).

Stop A-bis monitoring and analyse the trace. A-bis trace is analysed to see the success rate of ERACH.

Check active alarms and alarm history. No active alarms are present at both BSC and BTS Manager except for alarm “7801: Local MMI connected to the base station”.

Case Ref. Configuration 1. Standard ECell configuration, 2. 6 TRX (3N-TRX + 3E-TRX) configuration with RTC.

19.2 ECell Emergency Call

Purpose:

To check that Emergency Calls can be made from E-Area of an extended cell.

Note 121.

Emergency call services should already be set up in the Core Network.

Equipment and BTS Set-Up MS: phone with FR, EFR, HR, AMR FR&HR, SMS MO&MT capabilities

Test equipment: RF TA rig, attenuators, combiners.

Input Expected Output Set up a site as per test case. Set the radius extension to 19 km. for ECell BTS


Set up the RF TA rig and simulate the distance of 30 km for ECell BTS

RF TA rig is working and distance of 30 km is simulated

Connect the MS to the RF TA rig and perform a location update by resetting it.

On NetMonitor screen 01.01, check that the correct TA value is displayed for the MS. At a distance of 30 km, TA is 21. A value between 19 and 23 is acceptable.


Trace the TRXSIGs on the A-bis interface and attempt an emergency call.

Call is successful.

Analyse the A-bis trace. In CHAN RQD and IMMEDIATE ASSIGNMENT messages, Est. cause of the call is indicated as an Emergency Call.

DN0694168 Issue 2-0


Input Expected Output Check active alarms and alarm history. No active alarms are present at both BSC and BTS

Manager except for alarm “7801: Local MMI connected to the base station”.

Case Ref. Configuration 1. Standard ECell configuration,.

19.3 ECell Signalling

Purpose:

To check that the ECell feature works with different signalling configurations Equipment and BTS Set-Up MS: 2 phones with FR, EFR, HR, AMR FR&HR, SMS MO&MT capabilities

Test equipment: RF TA rig, attenuators, combiners

Input Expected Output Create a site as per test case. Set the radius extension to 24 km for ECell BTS.

Site is in Supervisory state. Extended radius is set to 24 km

Deactivate Dynamic SDCCH feature and activate FACCH call setup at the BSC. FACCH call setup: ZWOC:10,15,<FF=on>; ZEEM:EEF=Y,EPF=Y,EOF=Y,ERF=Y; Dynamic SDCCH: ZWOC:10,42,<0=off>;

Dynamic SDCCH is deactivated and Call setup via FACCH is activated Note that this affects all base stations controlled by the BSC.



Connect at least one of the MSs to the RF TA rig so that it is in the E-Area. Perform location updates by resetting the phones.

On NetMonitor screen 01.01, check that the correct TA value is displayed for both MSs. A distance of 45 km corresponds to TA=38. Values between 36 and 40 are acceptable.

Make a phone call to make sure that everything is set up correctly.

Call is successful. The allocated SDCCH is displayed on the MS display shortly during call setup: screen 01.01, second row, left most value shows the RTSL, bottom row, right most value shows used channel. Check also in the BSC: ZERO:BTS=<nr>; The last column indicates the status of each RTSL. It should correspond to the allocated SDCCH seen on the MS display. This will be difficult to see, due to the short duration of the dynamically configured SDCCH.

DN0694168 Issue 2-0


Input Expected Output Check active alarms and alarm history. Monitor the TRXSIGs on the A-bis interface.

No active alarms are present at both BSC and BTS Manager except for alarm “7801: Local MMI connected to the base station”.

Reserve all pre-configured SDCCH in E-Area. All pre configure SDCCH in E-Area are reserved. Make a phone call and monitor the mobile display.

Call is successful. During FACCH call setup, the following sequence is seen on the MS display, screen 01.01: AGCH, FA, TFR The RTSL for FA is the same as for TFR.

Monitor A-bis. In CHAN. ACT. Message the call is established via FACCH on TCH TS. After signalling is complete the TS is changed to appropriate codec via Mode Modify message. Calls are held until terminated and voice quality is also good without distortion.

Repeat the previous step until all TCH RTSLs on the available E-TRXs have been used at least once.

Same result as for step above.

Free the reserved SDCCH channels. Channels are successfully released. Make one last phone call. Call is successful. .

The pre-configured SDCCH channels are used. See MS display, screen 01.01. The allocated SDCCH is displayed.


Case Ref. Configuration 1. Standard ECell configuration, with separate BCCH/SDCCH

19.4 ECell Voice Calls

Purpose:

To check that voice calls work in a cell configured with E-Cell.

Note 122.

The IR/LA rig is a set up of equipment that allows introduction of interference on the air interface so that bad conditions on the RF path can be simulated.

Note 123. Table of the expected Rx Quality in UL and DL for different values of C/I. The RX Quality is independent of used speech codec. The values below have been achieved through simulation of a static channel, no fading, zero speed of MS, single Rx antenna, 1900 band. Simulation only for UL. Theoretically DL should be the same. There may be some variations when testing in lab in both UL and DL. It is quite possible that at C/I=5 calls will fail. This is acceptable.

DN0694168 Issue 2-0


C/I value UL Rx Quality DL Rx Quality 30 0 0 25 0 0 20 0 0 15 0 0 10 0 0 5 3 3

Equipment and BTS Set-Up MS: 2 phones with FR, EFR, HR, AMR FR&HR capabilities

Test equipment: RF TA rig, attenuators, combiners, IR/LA rig Input Expected Output

Set up a site as per test case. Set the radius extension to 31 km for ECell BTS.




Connect one of the phones to the rig, so that it is in the E-Area and make a location update by resetting it. Leave the second phone in the N-Area.

On NetMonitor screen 01.01, check that the correct TA value is displayed for both MSs. For a distance of 59 km, TA=50. Values between 48 and 52 are acceptable.

Set up the IR/LA rig so that interference can be introduced. Set initial C/I to 30. Note that the rig can only be set up for either uplink or downlink. Both directions must be tested.

IR/LA rig is working.


Monitor the TRXSIGs on the A-bis interface. Make phone calls as specified in the test case and speak in both directions.

Calls are successful. There are no disturbing clicks and noises.

Check active alarms and alarm history. Stop monitoring the A-bis.

No active alarms are reported during the test execution at both BSC and BTS Manager except for alarm “7801: Local MMI connected to the base station”.

Analyse the A-bis trace UL and DL Rx Quality is mainly 0 but no worse than 3. UL FER is mainly 0.

Repeat the above steps with interference, C/I = 25, 20, 15, 10, 5. Monitor test execution as in the first run.

Call is successful. UL and DL Rx Quality decreases, along with decreasing C/I. See table in the Note 123

Case Ref.

Heading Configuration Call type

1. Separate BCCH/SDCCH in N-Area, with and without interference

6 TRX Ecell configuration with RTC (3N-TRX+3E-TRX).

FR/EFR/HR/AHS/AFS

2. Combined BCCH/SDCCH in N-Area, with and without interference

6 TRX Ecell configuration with RTC (3N-TRX+3E-TRX) with BB2E.

FR/EFR/HR/AHS/AFS

DN0694168 Issue 2-0


19.5 ECell Ghost RACH/ERACH

Purpose:

To check that the number of ghost RACH/ERACH is below the specified limit.

Equipment and BTS Set-Up Test equipment: RF TA rig, attenuators, combiners, IR/LA rig


Set up a site as per test case Set the radius extension to 26 km for ECell BTS.


Lock the BTS and maximise the number of paging blocks in the multiframe and reduce the number of multiframes before paging group is repeated with the command:

ZEQJ:BTS=<nr>:AG=1,MFR=2; Unlock the BTS.

Site comes up to WO state. BTS CCH parameters are changed.

Terminate all antennas with 50 Ohm, 50 W terminating loads. Close the door on the cabinet.

All antennas are terminated correctly.

Check active alarms and alarm history No active alarms are reported at both BSC and BTS Manager except for alarm “7801: Local MMI connected to the base station”.

Monitor the TRXSIGs for the TRX carrying BCCH and ERACH on the A-bis interface. Let it run for at least 24 h, but preferably for 72 h. Stop monitoring. Check active alarms and alarm history for the duration of the test.

No active alarms are reported during the test execution at both BSC and BTS Manager except for alarm “7801: Local MMI connected to the base station”.

Analyse the A-bis trace. Look for CHAN REQs on the RACH and ERACH channels. In a 24 h period, there should be no more than 10 ghost RACH and 10 ghost ERACH CHAN REQs.

Case Ref.

Configuration

1. 6Omni IDD E-cell configuration with RTC (3N-TRX+3E-TRX).

19.6 ECell Handovers

Purpose: The purpose of these cases is to check that handovers work in a cell configured with ECell

Equipment and BTS Set-up

Test equipment: RF TA rig, attenuators, combiners, traffic generator

DN0694168 Issue 2-0


Input Expected Output Set up a site as per the test case Set the radius extension to 30 km for ECell BTS.


Set up the RF TA rig to the max distance of 50 km and min distance of 20 km so that the HO type under test can be simulated.

RF TA rig is in working state and maximum and minimum distance are simulated

Configure the traffic generator and connect it to the RF TA rig. TA value is calculated using [Note 118]

Net Monitor screen 01-01 displays the TA value. The TA value displayed on the phone is same as calculated for the specific distance (TA value 2 less or 2 more than calculated is acceptable).

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

Monitor the TRXSIGs on the A-bis interface and start the traffic generator for 2 hrs. All calls are held.

Calls are successful . HOs are successful, no handover failures messages are sent on the A-bis.

Stop the traffic generator and the A-bis monitoring.

All calls end normally.

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

Analyse A-bis trace HO procedure takes place correctly each time and as per test case. UL and DL Rx Quality, both are 0. UL FER is 0.

Case Ref. Configuration Handover 1. Standard ECell configuration. Between E- and N-Areas of the same BTS

Input Expected Output Set up a site as per the test case Set the radius extension to 25 km.


Set up the RF TA rig so that the maximum distance of 45 km and minimum distance of 15 km can be simulated.

RF TA rig is working and maximum and minimum distance are simulated

Connect the required number of phones to the RF TA rig and perform location updates by resetting them.

Net Monitor screen 01-01 displays the TA value. The TA value displayed on the phone is same as calculated for the specific distance (TA value 2 less or 2 more than calculated is acceptable).


Monitor the TRXSIGs on the A-bis interface and make a phone call long enough for at least one HO to take place.

Calls are successful . HOs are successful, no handover failures messages are sent on the A-bis.

Stop monitoring. Check active alarms and alarm history.

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

Analyse A-bis trace HO procedure takes place correctly. UL and DL Rx Quality, both are 0. UL FER is 0.

Case Ref. Configuration Handover

DN0694168 Issue 2-0


Input Expected Output 2. Standard ECell configuration. BSC

S13. HOs between E- and N-Areas of the same BTS for MS at high speed(> 60 km/hr)

3. 6 Omni Ecell configuration with RTC (3N-TRX+3E-TRX).

HOs between E- and N-Areas of the same BTS for MS at high speed(> 60 km/hr)

19.7 ECell HO during data call

Purpose: To check that CS data calls are handed over correctly in an ECell


Test equipment: RF TA rig, (HS)CSD rig, attenuators, combiners

Input Expected Output Set up a site as per test case Set the radius extension to 29 km for ECell BTS.


Set up the RF TA rig and simulate the distance of 40 km for ECell BTS.

RF TA rig is working and distance of 40 km is simulated.

Set up the (HS)CSD rig. Connect one of the data phones to the RF TA rig, so that it is in the E-Area and perform a location update by resetting it. Leave the second phone in the N-Area.

On NetMonitor screen 01.01, Correct TA value is displayed for all MSs. At a distance of 40 km, TA=20. Values between 18 and 22 are acceptable.


Monitor the TRXSIGs on the A-bis interface and make a circuit switched data call as per test case. Transfer 1MB file in both directions. During transmission, move the phone in the E-Area closer so that the call is handed over to the N-Area. Then move it away, so that a second HO takes place and the phone is back in the E-Area.

File transfer is successful, HOs are successful, check the speed and RTSLs used from the NetMonitor display. The sent and the received file should be identical. The data throughput is as expected, see Note 119

Stop monitoring and check active alarms and alarm history.

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

Analyse the A-bis trace. Used speed and RTSLs are the same as displayed on the phones. Check also that there are no corrections or CRC during the transfers. HO commands can be seen.

Case Ref. Heading Configuration

DN0694168 Issue 2-0


Input Expected Output 1. HO between E-Area and N-Area

of same cell during 14.4 k non-transparent CSD call

Standard ECell configuration.

2. HO between E-Area and N-Area of same cell during 3+1 non-transparent HSCSD call

6 TRX Ecell configuration with RTC (3N-TRX+3E-TRX).

19.8 ECell EMR

Purpose: To check that Enhanced Measurement Reports are received from the E-Area of an ECell

Equipment and BTS Set-Up Test equipment: RF TA rig, attenuators, combiners

MS: 2 phones with FR, EFR, HR, SMS MO&MT and EMR capabilities

Input Expected Output Set up the sites as per the test case. Set the radius extension to 25 km for ECell BTS.


Configure the adjacent cells: Neighbour 1 is the second sector in the ECell cabinet and has a valid BSIC. Neighbour 2 must be a site controlled by another BSC, whose BSIC has the same NCC part, but a different BCC part.

Neighbours are created and can be listed with ZEAO:BTS=<ecell>;

Turn off DL DTX using: ZEPR:NO=<bts ci nr>:DTX=ON; .(Note that this is on by default at the BSC and affects all BTSs. It can be switched off at the MSC for individual BTSs) Disable averaging using: ZEQM:BTS=<nr>:BMA=1; Enable reporting of invalid BSICs ZEHN:BTS=<nr>::IBR=1;

DL DTX is successfully switched off. Averaging of the SACCH multiframes is disabled successfully. Reporting on cells with invalid BSIC and allowed NCC part of BSIC is successfully enabled.

Latch the MSs to the BCCH frequency of the BTS under test. Then turn off BTS Test and reset the phones.

NetMonitor screen 01.03 displays the BCCH frequency and the frequencies of the two neighbouring cells.


RF TA rig is working and distance of 30 km is simulated.

Connect one of the phones to the RF TA rig, so that it is in the E-Area and perform a location update by resetting it. Leave the other phone in the N-Area.

On NetMonitor screen 01.01, Correct TA value is displayed for the MSs. For a distance of 30 km, TA=10. Values between 8 and 12 are acceptable. On screen 01.03 check that the neighbours can be seen.

DN0694168 Issue 2-0


Input Expected Output Check active alarms. There are no active alarms reported at both BSC

and BTS Manager except for alarm "7801: Local MMI connected to Base Station".

Monitor the OMUSIG and TRXSIGs on the A-bis interface and reset the site.

Site comes up to WO state after reset. During site reset, the SACCH FILLING message (within the SI BEGIN and SI END messages) contains the MEASUREMENT INFORMATION element containing the parameter Report_Type, which says that EMR will be used if supported by the MS.

Establish FR/EFR and HR calls between the two areas and speak in both directions. The calls should last for period so that several EMRs are received for each call. Monitor A-bis.

Calls are successful. There are no disturbing clicks and noises. During calls: Enhanced Measurement Reports are reported from BTS to BSC after a call has been established. EMR parameters have correct values as follows: BSIC Seen: 01 Reporting Quantity: <ecell bts nr> Reporting Quantity: <neighbour 1 bts nr>

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

Case Ref. Configuration

1 Cabinet 1: 1 standard ECell configuration, 1 normal sector. Cabinet 2: any configuration

19.9 ECell simultaneous GPRS and EGPRS transfer

Purpose: To check that an ECell can handle a simultaneous GPRS and EGPRS file transfer in N-Area.

Note 124. Packet switched services should be configured so that only 1 TSL is used for the GPRS transfer and 1 TSL is used for the EGPRS transfer.


MS: 2 phones with GPRS and EGPRS capabilities

Test equipment: GPRS/EGPRS laptops, attenuators, terminators; , RF TA rig, GPA

DN0694168 Issue 2-0


Input Expected Output Set up a site and activate GPRS and EGPRS as per test case. Set the radius extension to 10 km.

Site is in Supervisory state. Extended radius is set to 10 km The Gp RTSL has been configured to an N-TRX.

Set up laptops and phones for file transfer. Transfer

GPRS/EGPRS setups work.

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

Monitor OMUSIG, TRXSIG and Gp RTSLs for PCU Data Frame on the A-bis interface and transfer a 1 M file in both directions. Note the throughput for the data transfer. Use e. g. a picture file, so it is easy to confirm that transfer is successful.

File transfers are successful. Throughput is as specified for the CS/MCS used. See Note 120

Stop A-bis trace and analyse Correct CS/MCS is used. Rx Quality should be mostly 0 and no worse than 3.

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

Case Ref. Heading Configuration 1 Simultaneous GPRS(CS2) and

EGPRS(MCS9) file transfers in N-Area

Standard ECell configuration.

19.10 ECell Circuit Switched Dataf

Purpose: To check that CSD and HSCSD work in the E-Area of a cell configured with ECell.

Note 125. The Customer configuration for the Trial is defined as 1 N-TRX + 1 E-TRX, combiner less, in a BTS. All TRXs are EDGE capable. MHAs may be used, in which case all TRXs should be equipped with an MHA.

Equipment and BTS Set-Up MS: 2 phones with FR, EFR, HR, AMR FR&HR, SMS MO&MT capabilities

Test equipment: RF TA rig, attenuators, combiners, (HS)CSD laptops, screened room (optional).

Input Expected Output Set up the sites as per test case. Set the radius extension to 29 km.


Set up the RF TA rig and simulate the distance of 40 km for ECell BTS.

RF TA rig is working and the distance of 40 km is simulated.

DN0694168 Issue 2-0


Input Expected Output Set up one (HS)CSD laptop in the E-Area and the other in the N-Area. Connect a phone to each laptop. Perform a location update on the E-Area phone by resetting it.

On NetMonitor screen 01.01, The correct TA value is displayed for all MSs. At a distance of 40 km, TA=20. Values between 18 and 22 are acceptable.


Monitor the TRXSIGs on the A-bis interface and make a circuit switched data call as per test case. Transfer 1M file in both directions.

File transfer is successful, check the speed and RTSLs used from the NetMonitor display. The sent and the received file are identical.

Stop monitoring and check active alarms and alarm history.

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

Analyse the A-bis trace. Used speed and RTSLs are the same as displayed on the phones. Check also that there are no corrections or CRC during the transfers. The required throughput is listed in the Note 119.

Case Ref. Configuration Description 1. Customer ECell configuration, 9.6k CSD non-transparent file transfer in E-Area.

Transfer of 1M file between MS in E-Area and MS in N-Area. Both directions. Time: 17 min +/- 20%. Both ERACH and non-ERACH E-TRXs will be tested

20. DFCA

20.1 Speech Call Set-up via FACCH with DFCA

Purpose: The purpose of the following test case is to ensure that a TCH channel can be first used for signalling (call establishment) & modified to a speech channel on a non DFCA TRX

DN0694168 Issue 2-0


Input Expected Output A DFCA Configuration is used DFCA is configured. Deactivate Dynamic SDCCH feature in BSC and Reserve static SDCCH channels in the DFCA segment.

Dynamic SDCCH feature is deactivated and static SDCCH are reserved in DFCA segment.

Make a CS voice call from MS to MS. Monitor the A-bis Test case is repeated at least 5 times for the consistency of the result.

Call is established via FACCH on non DCFA TRX TS. After signalling is complete the TS is changed to appropriate codec via Mode Modify message and calls are held until terminated. The received audio quality is good and without distortion.

Case Ref. Codec 1 FR

20.2 AMR with DFCA

Purpose: To ensure that AMR call setup, fast link adaptation & slow link adaptation operate correctly with DFCA active.


A DFCA Configuration is used that includes GSM (non EDGE) and EDGE DFCA TRX

DFCA is configured.

ACS and Initial Codec are default values in the BSC. Enable DTX.

DTX is enabled.

A call is made via every TRX. Each call must be held for at least 30 seconds.

Calls are initiated according to parameters defined to the BTS. The quality of the call is good. No disturbing sounds are heard during the speech or silent periods.

DN0694168 Issue 2-0



The A-bis is monitored during the test A-bis CHANNEL ACTIVATION message includes the used AMR speech codec and the set of codec modes. Abis MEASUREMENT RESULT message show values when DTX is not used. RX Qual Full & Sub in both uplink and downlink vary between 0-7 according the interference. When DTX is applied, values of RX Lev Full & RX Qual Full are –110 dB & 7 respectively. The RX qual Sub is 0 in laboratory conditions. Interference applied is also represented by the FER measurements

During the AMR call, C/I conditions are changed step by step by manipulating air interface so that the codec mode is changed.(can be done by attenuation and generating an interference signal from signal generator) The quality of call is checked during the link adaptation.

When the downlink is degraded, MS requests BTS to apply a new codec (CMR is seen in the Abis). When the uplink is degraded, BSC commands MS to apply a new codec. When the uplink/downlink is attenuated, the codec mode is changed towards the most robust codec mode (more correction, lower bit rate). No disturbing sounds are heard when codec mode change occurs.

The attenuation is decreased step by step When uplink/downlink attenuation is decreased, the codec mode is changed towards the least robust codec mode (less correction, higher bit rate). If Fast LA is in use, the codec mode change is allowed in every second TCH frame (~ 40 ms). With Slow LA, codec mode changes are allowed on SACCH frame interval (480 ms). (CMI and CMR values are seen on Abis)

For testcase 3 & 5: Reset the LMU Repeat steps 2 to 6

Site takes reset and recovers its synchronisation with LMU Link Adaptation occurs smoothly

Case Ref. Link Adaptation 1 Fast 2 Slow 3 Fast 4 Fast1 5 Fast2

1Use BSC S13 CD3.0 SW, use regular TRXs for call initiation

2LMU address=9

DN0694168 Issue 2-0


20.3 Synchronous & Asynchronous Handover with DFCA

Purpose: The purpose of the following test cases is to verify that Synchronous and Asynchronous handovers operate correctly with DFCA

Note 126. Test cases 3 and 4 shall be performed causing handovers between a DFCA BTS and a normal (non-DFCA) BTS

Input Expected Output Use any Multi-TRX configuration with type of TRX as specified in test case. Neighbour definition is by adjacency and BA list for all cases

Site is up with given configuration.

A call is established in the source cell and terminated in a separate test cell with same call type Codec or user rate. Inter cell handover are triggered to target cell at least 20 times during the same call.

Handovers can be performed from target to source cell and back. If there are assignment failures, then the call is not released and failure is recovered by GSM signalling.

Speech call: A conversation is held. During the handovers speech quality at both ends of the calls are observed for unexpected audio disturbances.

The perceived speech is unaffected by the handover procedure and there are no additional audio signals noticed. (E.g. clicks). In HR calls there may be a period of silence during handover due to frame stealing.

Data call: Data call is single TS. During the handover procedures a 200Kb data file is transferred in alternative directions. The transferred data is compared with the original file.

Data call is set up on the DFCA TRX. Data can be sent and received in both directions with the user data rate as defined in test case. Data is transferred with zero error.

Case Ref. Call type / Codec or user rate Handover Type

TRX

1. AMR / FR Synchronous EDGE 2 NT data / 14400 Asynchronous EDGE 3 AMR / FR Synchronous EDGE 4 Speech / FR Asynchronous EDGE

DN0694168 Issue 2-0


20.4 EGPRS with DFCA

Purpose: The purpose of the following test cases is to ensure that the BTS will select non DFCA TRX to process packet switched data

Input Expected Output Use any Multi-TRX configuration with type of TRX as specified in test case. All non DFCA TRX timeslots are configured to be GPRS enabled using default GPRS capacity and for DFCA TRXs are set GTRX=N


Set EGPRS as specified EGPRS is set as specified Packet data transfer is started using the coding scheme and direction as defined in the test case. The user data rate is monitored.

The expected data rates for the coding scheme are achieved. In the PCU data frame the values for Coding scheme & RX level are verified to be reliable.

When the data transfer is complete a CS speech call is made on the same TS

The circuit switch call is successful. After releasing the call the timeslot regains synchronisation.

Case Ref. Coding Scheme

Direction EGPRS Data Rate/TS

Configuration

1. CS-1 Uplink Disabled 9Kbit/s GSM/S13 BSC 2. MCS-9 Downlink Enabled 48Kbit/s EDGE

20.5 Antenna Hopping & DFCA antenna Sharing

Purpose:

To ensure that the BTS will support separate sectors sharing the same set of antennas (using wideband combiners), with Antenna Hopping in the first sector and DFCA in the second sector.

Note 127. The sectors (created at the BSC) and the wideband combining for this case is configured as follows:

Note 128. TRX 1 Sector 1 Antenna Hopping } Wideband combined, to Antenna 1 TRX 2 Sector 2 DFCA } TRX 3 Sector 1 Antenna Hopping } Wideband Combined, to Antenna 2 TRX 4 Sector 2 DFCA }

DN0694168 Issue 2-0


Input Expected Output A 2+2 configuration is used: Site is configured and working. Setup a CS voice call on sector 1. Use a spectrum analyser to verify that the call is antenna hopping (Appendix A)

The spectrum analyser shows antenna hopping is working correctly

Setup a CS voice call on sector 2 Call is successful Case Ref. .Configuration 1 UltraSite with EDGE HW , Sector 1: [non DFCA (Antenna hopping)

Sector 2: [1 x BCCH + 1 x DFCA TRX]

21. IMSI BASED HANDOVER

21.1 IBHO Feature Activation, GSM to GSM

Purpose: To verify that when IMSI based handover is enabled for the BTS, the feature information is sent in the SI_BEGIN message, and that the site performs basic functions normally with both old and new SW versions.

Input Expected Output Lock the BTS. BTS is locked successfully. Set IBHO_GSM_ENABLED for the BTS at BSC.

(ZEQM:BTS=##:::::IGE=Y;)

Unlock the BTS and monitor the TRX signalling at A-bis.

In case of CX(M)7.0 SW, SI_BEGIN is sent to the BTS, containing the IBHO feature information which indicates that IBHO feature is enabled and the sector is unlocked successfully.

Check the state of the BTS and alarms at BSC and the MMI.

All units are in working state. There are no active alarms except “7801: Local MMI connected to the base station”.

Establish calls on all TRXs. Calls are successful on all TRXs Case Ref. Configuration SW 1. Any CX(M)7.0 2. Multi TRX CX(M)7.0

DN0694168 Issue 2-0


21.2 GSM to GSM IBHO, call setup 2 MS with different PLMN, EMR/MR and multi-band

Purpose: To check that SI messages are sent separately for each call and handover takes place to the PLMN listed in the ANE.

Input Expected Output Use 2 MS with different PLMN values. Establish a speech call with the first MS Monitor Abis for messages sent to BTS, and measurement reports from MS.

Call is established successfully. CHANNEL ACTIVATION message for the TCH is sent on the Abis to the BTS, with SI5 and SI6 messages (and SI5bis or SI5ter, depending on the bands being tested) containing neighbour cell information from the AN associated with the PLMN of the phone.

Monitor the neighbour ARFN measured by the MS and the information sent by the BSC to the BTS at Abis.

The neighbour ARFN being measured by the MS should correspond with the values sent in the SI messages (for EMR measurements only, this is not true for the period before EMR reports start when standard MR are used)

Establish a speech call with the second MS.

Monitor Abis for messages sent to BTS, and measurement reports from MS.

Call is established successfully. CHANNEL ACTIVATION message for the TCH is sent on the Abis to the BTS, with SI5 and SI6 messages (and SI5bis or SI5ter, depending on the bands being tested) containing neighbour cell information from the AN associated with the PLMN of the phone.

Monitor the neighbour ARFN measured by the MS and the information sent by the BSC to the BTS at Abis.

The neighbour ARFN being measured by the MS should correspond with the values sent in the SI messages

Trigger handovers for both the MSs. Handovers can be performed successfully, at least 2 times, from target to source cell and back for both MS.

Case Ref. MR/EMR Source: Band/Target: Band

Configuration

1. MR 900/9001 Any Configuration 2. MR 900/1800 Any Configuration 3. EMR 1800/18002 Any Configuration 4. MR 900/900 Any Configuration

1 Source cell: Ciphering - A5/1, packet type - A5/3, HW Type: EDGE & Target cell Ciphering - A5/0, packet type - A5/3(Ciphering Disabled at MSC), HW Type: EDGE 2 Source cell packet type - A5/3 HW type – EDGE & Target cell packet type - A5/0 HW type - EDGE.

DN0694168 Issue 2-0


22. CS3 & 4

22.1 Paging Mode

Purpose:

The purpose of these cases is to verify that during GPRS data transfer using CS3 and CS4 coding scheme, mobile can be paged for MT voice call successfully. Also verify that data transfer resumes once call ends.

Input Expected Output Use configuration as defined in the case. Dynamic A-bis is enabled.

Packet data transfer is started using TCP/IP in tested timeslot with coding scheme specified in the case in both UL and DL directions.

The data is being transferred with BER of 0%.

A terminating speech call is made to the mobile. The Gb interface and TRX signalling links at A-bis interface are monitored.

Paging command message is seen for the test mobile in Gb interface traces. At A-bis interface ‘Packet Paging Command’ is seen. The speech call is established as normal.

Speech call is terminated. MS is in Packet transfer mode and data transfer resumes. Data transfer is successful.

Case Ref.

BTS Channel Configuration

Hopping mode

Coding Scheme

1 Multi TRX EDGE MBCCHC + TCHD AH Hopping CS4

22.2 Data transfer

Purpose:

The purpose of these cases is to verify that data can be transferred reliably using coding scheme 3 in downlink direction on PDTCH with BER of 0%, and that the expected data rates for the coding scheme-3 is achieved and the given TS can be used alternatively for circuit switched and packet data.

Test Tools Required: None

DN0694168 Issue 2-0


Input Expected Output Use configuration as defined in the case. Dynamic A-bis is enabled. GPRS coding schemes as given in table are enabled for both sectors. Circuit switched speech calls are established in both sectors and checked in the GP timeslot to be tested. The call is released.

The circuit switched calls are successful. After releasing the call the timeslot regains GPRS synchronisation.

Packet data transfers in given directions are started on the tested timeslot using transfer protocol type as defined for the test. The user data rate, Coding Scheme used and RX level is monitored. Monitor the A-bis for BEP values

The data is transferred with BER of 0%. The expected data rates shown below for the coding scheme are achieved. In the PCU MASTER DATA FRAME the values for Coding scheme & RX level are verified to be reliable. BEP values (CV_BEP & MEAN_BEP) are verified to be reliable.

When the data transfer is complete circuit switched speech calls are again established and verified on the same tested timeslot.

The circuit switch calls are successful. After releasing the call the timeslot regains GPRS synchronisation.

Case Ref.

BCCH Configuration/ TCH Configuration/ CS Call type/Hopping type

Transport Type/ File size

GPRS Enabled TRX/ Number of timeslots available

Expected Data Rate

Direction and coding scheme

1 MPBCCH+SDCCH/TCHFs/TFR 2+2 EDGE/RF in both sectors

TCP/IP/ 5MB

Non BCCH/3 TS CS3-46.8 kbps/CS4-64.2 kbps

CS 3 in DL(first sector) and CS4 in UL (second sector)

2 MBCCH + SDCCH/TCHDs/AHS 2+2 EDGE/RAH Hopping in both sectors

UDP / 1MB BCCH/2 TS CS4-42.8 kbps/CS3-31.2 kbps

CS4 in DL(first sector) CS3 in UL (second sector)

3 MPBCCH+SDCCH /TCHFs/EFR/2+2 EDGE /BB hopping in both sectors

UDP/ 500KB


CS4 in UL(first sector) CS3 in DL (second sector)

4 MPBCCH+SDCCH/ TCHFs/AFS/RF/2+2 EDGE hopping in both sectors

UDP/ 500KB


CS4 in DL(first sector) CS3 in UL (second sector)

DN0694168 Issue 2-0


Input Expected Output 5 MBCCHC

/TCHFs/EFR/2 OMNI RF hopping

TCP/IP /1MB

BCCH/1 TS 21.4 kbps CS4 in UL

22.3 CS3 and CS4 GPRS Data transfer

Purpose:

The purpose of these cases is to verify that data can be transferred using coding scheme 3 and 4, that data can be transferred reliably in both uplink & downlink on PDTCH, and that a given TS can be used alternatively for circuit switched and packet data.


Input Expected Output Use configuration as defined in the case. Dynamic A-bis is enabled. Set BTS to use specified coding scheme as defined in the case.

A Circuit switched speech call is established and checked in the GP timeslot to be tested. The call is released.

The circuit switched call is successful. After releasing the call the timeslot regains synchronisation.

Packet data transfer is started using TCP/IP in tested timeslot with coding scheme as defined in the case in both UL and DL directions. The user data rate is monitored. Date Transfer should be made 3 times to get a reliable throughput File Size: 1 Mb in DL, 100 Kb in UL

The data is transferred with BER of 0%. The expected data rates for the coding scheme are achieved. (CS3 approx. 15.6kbit/s per timeslot used and CS4 is approx. 21.4kbit/s per timeslot). In the PCU Master data frame the values for Coding scheme & RX level are verified to be reliable.

When the data transfer is complete, a circuit switched speech call is again established and verified in the same tested timeslot.


Object administration is performed from BSC as defined in the case.

The GP timeslot regains synchronisation after object administration commands are run successfully.

Packet data transfer is again started using TCP/IP in tested timeslot with coding scheme and direction as defined in the case.

The data transfer is successful.

Case Ref.

BTS/Channel Configuration

GP TRX Coding Scheme /TS

Hopping Object Administration Command

1 6+6, EDGE HW, BB2E, RTxx MBCCHC + MPBCCH + TCHF

Non BCCH CS3/(3+1) BB- Hopping

BTS Lock/Unlock

DN0694168 Issue 2-0


Input Expected Output 2 4+4+4,

GSM/EDGE HW, BB2A/BB2E, DVxx / MBCCHC + TCHF

BCCH CS4/(2+2) RF- Hopping

BCF Lock/Unlock

3 6+6 EDGE HW, BB2E, RTxx / MBCCHC + MPBCCH + TCHF

Non BCCH CS4 BB BTS Lock/Unlock

4 2+2, GSM/EDGE / MBCCHC + TCHF

BCCH CS3 Non-Hopping

BCF Lock/Unlock

5 2+2, EDGE / MBCCHC + TCHF

NonBCCH CS4/(2+2) Non-Hopping

BCF Lock/Unlock

22.4 CS4 with speech call

Purpose:

The purpose of this test case is to verify that successful Speech call can be made simultaneously with GPRS Data call on same TRX. Also verify that GP timeslot transmits at BCCH Power level.


Input Expected Output Use configuration as defined in the case. Dynamic A-bis is enabled. Enable GPRS Link adaptation.

Packet data transfer is started with TCP/IP or UDP/IP in tested timeslot with coding scheme CS4 in DL direction.

The data is being transferred with BER of 0%.

Pair of speech calls is made on same TRX, which has GP timeslot configured.

Speech calls are successful Data transfer is not affected and is successful.

Measure power level of BCCH TRX and GP timeslot using spectrum analyzer.

GP timeslot transmits at BCCH Power level.

Case Ref.

BTS Channel Configuration Hopping mode Direction /Transport Protocol of Application

DN0694168 Issue 2-0


Input Expected Output 1 4 OMNI DFCA

configuration (2TRX +2 DFCA TRX,)EDGE HW

MBCCHC + MPBCCH+TCHF, GP is on Non BCCH TRX

RF Hopping TCP/IP

22.5 GPRS and EGPRS TBF’s on one time slot

Purpose:

The purpose of these tests is to check that GPRS and EGPRS TBFs can exist on the same radio timeslot. To check that the correct CS & MCS is used when this happens.

Note 129. The PCU sends a PACKET UPLINK (or DOWNLINK) ASSIGNMENT for each MS. These messages assign a different TFI to each MS. The uplink assignment also assigns a USF to each MS. The USF in the header of the downlink RLC Data Blocks indicate which TBF may transmit in the uplink

The PCU restricts the MCS used for a downlink EGPRS TBF to a GMSK coding scheme when an uplink GPRS TBF shares the same radio timeslot. It does this so that the uplink GPRS MS can read the USF information in the downlink TBF’s header.

Test Tools Required: Signal Generator, spectrum Analyser

DN0694168 Issue 2-0


Input Expected Output This test case must be performed with SGSN ciphering off or on, as shown in the table. Choose three MS so that the RLC Mode = Acknowledged. The MS must have the same priority set at the HLR. MS1 = EGPRS MS2 = EGPRS MS3 = GPRS Use any base station configuration. EDAP Pool with 3 TS is configured and attached to the GPRS Enabled TRX. EGPRS on only one TRX is enabled. Lock all traffic timeslot so that only one (E) GPRS timeslot remains available for use. Set Link Adaptation = on for both GPRS and EGPRS. (To do this for GPRS: Use the MML command ZEQV to set the following parameters to the values shown: DLA = 5%, ULA = 5% DLB = 10%, ULB = 10%, DLBH = 10%, ULBH = 10% COD = 0, CODH = 0 (GPRS link adaptation used). ELA=1(EGPRS link adaptation used).) Set up Carrier / Interference (C/I) conditions in the air interface for all MS. Set C/I > 27 dB.

DN0694168 Issue 2-0


Input Expected Output (E) GPRS attach each MS in turn to the sector. Activate a PDP Context for each MS in turn. Monitor the A-bis and record a trace Begin UDP data transfer of 2MB files in the direction shown for each MS: MS1 = uplink MS2 = downlink Begin UDP data transfer of a 2MB file with MS3 = uplink.

All the MS attach successfully. All MS activate a PDP Context successfully. Both MS begin transfer successfully using predominantly MCS-9. The TBFs for all three MS are successfully shared on the one timeslot. The coding scheme used for the downlink transfer (MS2) will alternate between GMSK and 8PSK. In the uplink the following coding schemes are predominantly used: MS1 = MCS9 MS3 = CS4

Case. Ref

BCCH/TCH Configuration SGSN Ciphering

(E) GPRS Enabled TRX

1 MBCCH+SDCCH/TCHDs ON Non BCCH

22.6 CS3 & CS4 Data transfer with IDD/4UD & IDD BBH configuration

Purpose:

The purpose of these tests is to check that GPRS data transfer can be performed correctly when IDD/4UD & IDD BBH Configuration is in use.

Note 130. The 4-way diversity parameter is set from BTS Manager during commissioning and diversity is ON at BSC. There are no parameters or definitions at the BSC, only IDD main TRXs and normal non-IDD TRXs are defined to the BSC. When defining TRXs to the BSC, the IDD configuration at the BTS site has to be known by the operator in order to define correct TRXs to BSC.


DN0694168 Issue 2-0


Input Expected Output Use configuration as defined in the case. At least 12 timeslots are configured to be GPRS enabled. EDAP Pool with 4 TS is configured and attached to the GPRS Enabled TRXs. Set the Coding Scheme as shown in the table below. A circuit switched speech call is established (Any call type can be used i.e. EFR) and checked on all the GPRS timeslot. The calls are then released.

The circuit switched call is successful. After releasing the call, the timeslot regains synchronisation.

8 different Packet data transfer is started using 8 different MS in both uplink & downlink direction using Coding scheme as defined in the test. At least 1 Mb file is transferred for reliable results. The user data rate is monitored on each MS. Both TX and RX paths are checked from IDD main and auxiliary TRXs with a spectrum analyser.

The data is transferred with BER of 0%. The expected data rates for the coding schemes are achieved for each transfer. (CS3 approx. 15.6kbit/s per timeslot used and CS4 is approx. 21.4kbit/s per timeslot). In the PCU MASTER DATA FRAME the values for Coding scheme & RX level are verified to be reliable. The spectrum analyser indicates that mobile uses TX path from both main and auxiliary TRX. For RX paths (4-way diversity), that any path single or combination of RX paths can be used.

When the data transfer is complete a circuit switched speech call is again established and verified in the same tested timeslot.


Case Ref.

HW Configuration Hopping Mode Coding Scheme in use

1 2+2, IDD with 4UD Not used CS3 2 4 Omni with IDD only / BB2F BB Hopping CS4

22.7 Link Adaptation: GPRS Link adaptation

Purpose:

To check that GPRS link adaptation selects the coding scheme (CS1, CS2, CS3, CS4) appropriate for the air interface conditions. To check that Dynamic A-bis allocates a slave sub TS when CS4, CS3, CS2 is selected by GPRS link adaptation.

Test Tools Required: Spectrum Analyser, Signal generator

DN0694168 Issue 2-0


Input Expected Output Dynamic A-bis is enabled. Set Link Adaptation = on for both GPRS and EGPRS. (To do this for GPRS: Use the MML command ZEQV to set the following parameters to the values shown: DCSA=7,UCSA=7, ELA=1(EGPRS link adaptation used)). Use any EDGE sector with 3 or more TRX. EGPRS must be enabled in the Sector. Establish a Carrier / Interference (C/I) ratio > 27dB in the air interface, in the direction shown in the table. Use a GPRS MS and set RLC Mode = Acknowledged for this MS.

Attach the MS to the sector and activate a PDP Context. Transfer a 500K file in the direction shown in the table below. Monitor the A-bis for the coding scheme used. Deteriorate the radio conditions to C/I = 0dB. Improve the radio conditions to C/I > 27dB. Repeat the C/I cycle a further 2 times.

MS attach and PDP Context activation is successful. The PCU MASTER DATA FRAME indicates that CS4 is used. Dynamic A-bis allocates one slave frame. As the radio conditions deteriorate the CS being used should change from CS4 to CS3 to CS2 and finally to CS1 (For CS2 & 3 one slave frame will be allocated). No slave frames are allocated when CS1 is in use. The PCU MASTER DATA FRAME indicates that CS4 is used again. Dynamic A-bis allocates one slave frame. The coding scheme switches as expected.

When the data transfer is complete a circuit switched speech call is established and verified in the same tested timeslot.



Case. Ref

Direction Hopping Mode/configuration

1 Downlink Not used/Any 2 Downlink Not used/DFCA

3 Uplink BB Hopping 4 Uplink BB Hopping/2 TRX EDGE HW with MBCCHC +

TCHF, GP is on BCCH TRX 5 Downlink No Hopping/4 OMNI DFCA (2 N-TRX+2 DFCA

TRXs)with MBCCHC+TCHF, GP is on Non BCCH TRX of Non BCCH TRX

DN0694168 Issue 2-0


22.8 Link Adaptation: GPRS and EGPRS Link adaptation

Purpose:

The purpose of these cases is to verify that Link Adaptation occurs dynamically as prevailing radio conditions change i.e. Change in C/I for both GPRS and EGPRS Data calls simultaneously.

Test Tools Required: Spectrum Analyser, Signal generator

Input Expected Output Use configuration as defined in the case. Dynamic A-bis is enabled. GPRS and EGPRS link adaptation is enabled. Establish a Carrier / Interference (C/I) ratio > 27dB in the air interface, in the direction shown in the table. Use an EDGE and non-EDGE GPRS MS, and RLC Mode = Acknowledged. Attach the MS to the sector and activate a PDP Context.

Site is configured and in working state.

Transfer a 1 Mb file in the direction shown in the table below simultaneously with both GPRS and EGPRS mobiles. Monitor the A-bis for the coding scheme used.

The PCU MASTER DATA FRAME indicates that CS4 is used for GPRS MS and MCS9 for EGPRS MS. Dynamic A-bis allocates one slave frame for CS4 and 4 slave frames for MCS9.

Deteriorate the radio conditions to C/I = 0dB. Improve the radio conditions to C/I > 27dB. Repeat the C/I cycle a further 2 times.

As the radio conditions deteriorate the CS being used should change from CS4 to CS3 to CS2 and finally to CS1 for the worst radio conditions for GPRS MS and MCS9 to the MCS1 for EGPRS MS as shown in the Table 19. The PCU MASTER DATA FRAME indicates that coding scheme being used. No slave frames are allocated for CS1. As the radio conditions improve the CS being used should change from CS1 to CS2 to CS3 and finally back to CS4 for the best radio conditions for GPRS MS and MCS1 to the MCS9. The coding scheme switches as expected.


Case Ref.

BTS Channel Configuration Hopping mode

Direction

1 Multi TRX EDGE HW

MBCCHC + MPBCCH+TCHD, GP is on Non BCCH TRX

RF Hopping DL

DN0694168 Issue 2-0


22.9 Data Transfer with A-bis Failure

Purpose:

The purpose of these cases is to verify that multiple short duration A-bis link failures are handled correctly during CS3 & CS4 data transfer.

Test Tools Required: Abis Breaker

Input Expected Output Use Any configuration. Dynamic A-bis is enabled. Set the Coding Scheme as shown in the table. All BCCH TRX timeslots are configured to be GPRS enabled, using default GPRS capacity on BCCH TRX.

Site is up and working with required configuration.

Setup GPRS data transfer using TCP/IP protocol in specified direction. At least a file size of 5 MB is transferred for reliable results.

The data transfer is started.

For a period of 10 seconds the whole A-bis is disrupted with random short (<0.5 s) breaks The link is then left connected until the link recovers. Repeat the above at least 3 – 5 times during the transfer Terminate data transfer

The data transfer is interrupted when there are breaks in A-bis interface. After the link recovers, PCU frame resynchronises. Data continues to transfer. Data Transfer is interrupted but resumes when the link is connected again. Data transfer is completed successfully. (Very occasionally the A-bis may be broken while the BSC is polling the BTS. This will cause the LAPD to drop and the air interface to be disabled. It may take over 30 sec to recover the site once the A-bis is reconnected. During this time the TCP/IP connection will probably be dropped. It may also be necessary to re-activate the PDP Context)

Case Ref.

Direction Coding Scheme in use

1 Uplink & Downlink simultaneously CS3 2 Uplink & Downlink simultaneously CS4

22.10 Data Transfer with Air Interface Failure

Purpose:

DN0694168 Issue 2-0


The purpose of these cases is to verify that multiple short duration Air Interface failures are handled correctly during CS3 & CS4 packet data transfer.


Input Expected Output Use Any configuration. Dynamic A-bis is enabled. Set the Coding Scheme as shown in the table.

Site is configured and in working condition.

Setup GPRS data transfer using TCP/IP protocol in specified direction. At least a file size of 5 MB is transferred for reliable results. Monitor A-bis interface

The data transfer is started. In the PCU MASTER DATA FRAME the values for Coding scheme & RX level are verified to be reliable.

Break air interface (UL/DL) for a period of 7 sec (based on counter N3101 and timer T3169 values). Repeat this above at least 2 – 3 times during data transfer

TBF will release and when re-established the TCP protocol will request data retransmission, a new TBF is established P-CHANNEL REQUIRED or PACKET CHANNEL REQUEST message is seen on the A-bis) and data transfer continues.

For Case Ref. 1, UDP/IP protocol type shall be used for transferring data.

Resources are released, a new TBF is not established.

Case Ref.

Direction Coding Scheme in use

1 Uplink & Downlink simultaneously CS3 2 Uplink & Downlink simultaneously CS4

22.11 Cell Reselection & Timing Advance with GPRS CS3&4

Purpose:

Check cell reselection functions correctly with GPRS CS3&4 data transfer and timing advance. Check that combined IMSI/GPRS attach can be performed with timing advance. Check cell reselection can be performed from one routing area & location area to another.

Test Tools Required: Fading Simulator, Spectrum Analyser, and Signal Generator

DN0694168 Issue 2-0


Input Expected Output Use any configuration for BTS1 & as mentioned in the table below. Set the Coding Scheme as shown specified. Dynamic A-bis is enabled. Hopping mode is set as specified. Timing advance is applied to BTS 1 only. BA list is created containing BTS1 & BTS2 BCCH frequencies. The 2 BTS’s have a different Routing Area (RA) or Location Area (LA) when specified.

Turn on GPRS mobile and attach to the specified BTS. Set up GPRS data transfer in specified direction-using data file big enough for 10 cell reselections

Mobile performs combined IMSI/GPRS attach. The transfer can be established on the source cell. MS uses one slave frame from EDAP Pool during data transfer.

Use an adjustable attenuator to cause cell reselection during the data transfer. The A-bis TRX links and PCU MASTER DATA FRAMEs are monitored on source and target cells. A-bis traces are recorded. The reselection between cells is made at least 10 times for each case.

The Reported TA value is correct in both Source cell and Target cell. Post analysis of Abis trace shows coding scheme used in both source and target cells as specified. The TA value can be observed from the PCU Random Access Frame and Immediate Assignment command The user data rate does not degrade after reselection procedure.

For case ref 4, an interference is to be applied in target cell

DN0694168 Issue 2-0


1Use ARFCN 0 in the source cell.

22.12 GPRS Territory Upgrade/Downgrade

Purpose: To check that GPRS territory upgrade/downgrade is operational with GPRS To Check that one RTSL can support more than one TBF

Note 131. CSU and CSD parameters at the BSC (command: ZEEM) may need changing in order to cause GPRS upgrade/downgrade

The parameter free TSL for CS downgrade (CSD) defines a margin of radio time slots that the BSC tries to preserve idle for circuit switched traffic by downgrading the GPRS territory when necessary.

Free TSL for CS upgrade (CSU) defines the number of radio time slots that has to remain idle in the circuit switched territory after the planned GPRS territory upgrade has been performed.

Case Ref.

Direction Hopping Mode (BTS1 / BTS2)

Attach To

Timing Advance

Coding Scheme(source/target)

1 Uplink Non-Hop /Non-Hop/Any

BTS1 20 Km for BTS1

CS3/CS3

2 Downlink BB Hop / RF Hop/any(LA is different for source and target)

BTS2 30 Km for BTS2

CS4/CS4

3 Uplink NonHopping/RF hopping/MultiTRX EDGE with MBCCHC + TCHF

BTS1 0 km CS3/CS3&4 with Link adaptation

4 Downlink AH hopping/Non Hopping/MultiTRX EDGE with MBCCHC + MPBCCH (RA is different for source and target)+ TCHF

BTS2 15 km for BTS1 and 10 km for BTS2

CS4/CS3&4with Link adaptation is enabled, CS3 is selected due to interference

5 Downlink 2 TRX EDGE HW with MBCCHC +MPBCCH+ TCHF, EDAP is in USE (For both source and target) Source and target should have different RA)

BTS1 15 km for BTS1 (use ARFN=0 in BTS1)

CS4/ CS3&4with Link adaptation is enabled, CS3 is selected due to interference

DN0694168 Issue 2-0



Input Expected Output Any configuration is used. Lock RTSL of all the TRX but except for one TRX having GP timeslots (which is under test). GPRS Coding Scheme as mentioned in the test is configured for the BTS under test.

Site is up with given configuration. GPRS coding scheme is set.

Set up CS speech calls until only one timeslot (GP TS) remains idle (Any call type can be used i.e. EFR, FR, AFS, AHS). GPRS Attach the two MS to the Sector and PDP Context is created. Set up two GPRS TCP/IP data transfers. (File Size 1Mb). For test case 3 Enable EGPRS and establish data transfers with EGPRS capable MSs.

GPRS Attach & PDP Context is successful. Both data transfers begin successfully (two TBF's on one timeslot).

Terminate CS speech calls one by one, until (E) GPRS territory upgrade is performed. Set up CS speech calls one by one, until GPRS territory downgrade is performed.

Existing GPRS data calls no longer share one RTSL GPRS data calls return to sharing one timeslot. Data transfers are successful.

Compare the received file with the sent file. Repeat testcase 3 for CS4 coding scheme.

The file received is identical to the file sent.

Case Ref.



GPRS Enabled TRX Coding Scheme in use

1 Uplink Uplink BCCHe CS3 2 Downlink Downlink BCCH/ 2+2+2 CS4 3 Downlink Downlink BCCH/Multi TRX

EDGE HW with channel configuration MBCCHC + MPBCCH+TCHF (RAH hopping)

CS3

4 Downlink Downlink Non BCCH/4 TRX GSM/EDGE HW with MBCCHC + TCHF/No Hopping

CS3

DN0694168 Issue 2-0


22.13 GPRS CS3&4 Reliability at Various Distances

Purpose: To check that data transfer does not fail when the MS distance varies over the full range (0 to 35 Km). To check that random access bursts are successfully received over the full range of timing advance values.

Test Tools Required: Fading Simulator, Signal Generator and Spectrum Analyser

Input Expected Output Use any configuration. Dynamic A-bis is enabled. Choose a GPRS MS such that RLC Mode should be Acknowledged RLC Mode. Set the Coding Scheme as shown in the table. Use the MML command ZEQV: BTS=##: BLA=90; To set the max. Limit for block error rate to 90% (this is the default value). Establish C/I conditions in the air interface so that C/I > 27dB.


Promptly begin the transfer of a 5 MB file using the transfer protocol and direction as mentioned for the test. Use number of timeslots as shown in the table. During the data transfer, start varying the distance from 0-35km or 35-0 km depending upon the case requirement. Monitor the A-bis interface. As the transfer of one file completes, promptly begin the transfer of a new 5 MB file. Repeat this process until the MS reaches a distance of 0Km (if MS is moving towards BTS) or 35 Km (if MS is moving away from BTS). (Re-start sending the files till the test case is complete)

Data transfer begins successfully and continues without breaks. Timing Advance value is verified from the Abis Traces and should be corresponding to the distance of the MS. In the PCU MASTER DATA FRAME the values for Coding scheme & RX level are verified to be reliable. Each new file transfer begins successfully. The correct timing advance is shown at the A-bis.

The user data rate is monitored The expected data rates at the end of the transfer for the coding schemes are achieved for each transfer. (CS3 approx. 15.6kbit/s per timeslot used and CS4 is approx. 21.4kbit/s per timeslot).

Compare the files received with the files sent and data rate.

The received files are identical to the sent files.

Case Ref.

Direction No. of Timeslots

Start Dist

Travel Coding Scheme in use

1 Downlink 1 0Km Away from BTS

CS4

DN0694168 Issue 2-0


22.14 Mobile speed handling

Purpose:

The purpose of these cases is to verify that GPRS data transfer with CS3 & CS4 does not fail when the MS speed increases up to 200Km/h and TA is changed.

Test Tools Required: fading simulator, spectrum analyser

Input Expected Output Use configuration as defined in the case. Dynamic A-bis is enabled. GPRS link adaptation is disabled.

Packet data transfer is started with coding scheme and direction as specified in the case with GPRS mobile travelling at speeds of 5km/h, 30km/h, 80km/h and 200km/h in each case. GPRS data call is held for at least 5 minutes with the MS moving to / from the BTS starting with TA values of 0 & 35km. Monitor the A-bis for BEP values and coding schemes used. File Size: 1 Mb in DL, 100 Kb in UL (Re-start sending the files till the test case is complete)

In the PCU Master data frame the values for Coding scheme, BER & RX level are verified to be reliable. As MS speed increases the reported BEP increases. Data transfer is successful.

Compare the received file(s) with the sent file(s).

The file(s) received is identical to the file(s) sent.

Case Ref.

BTS Channel Configuration Coding Scheme

Hopping mode

Direction

1 Multi TRX EDGE HW

MBCCHC + TCHF CS3 BB Hopping

DL

2 Multi TRX, EDGE HW

MBCCHC + MPBCCH+TCHF

CS4 Non Hopping

DL

22.15 Dynamic Abis Allocation

Purpose:

The purpose of these cases is to verify that (E)GPRS DL resource allocation functions correctly when EDAP resources are lacking.


DN0694168 Issue 2-0


Input Expected Output Use configuration as defined in the case. Configure EDAP as mentioned in the test case below. Use CDED, CDEF and CMAX to enable radio timeslots as GP TS as specified in the test case. (E)GPRS link adaptation is enabled.


Set up (E)GPRS data transfer(s) in downlink direction (on 2 radio timeslots) as specified in test case. Monitor A-bis Continue to set up additional (E)GPRS data transfers as specified in the test case.

Data transfer begins. A-bis shows CS4 in use for GPRS data transfer and MCS 9 for EGPRS data transfer. All data transfers are set up. Lower (M)CS's are used instead of the CS4 and MCS-9 due to the lack of EDAP TS's. Therefore data rates are reduced.

Case Ref.


Data transfer

Additional data transfer

No. of A bis TS in EDAP

No. of GP RTSL

1 Multi TRX EDGE HW

MBCCHC + TCHF

GPRS only

Three GPRS –

1 8

Purpose:

The purpose of these cases is to verify that (E)GPRS UL resource allocation functions correctly when EDAP resources are lacking.


Input Expected Output Use configuration as defined in the case. Configure 1 A-bis timeslots to the EDAP in case of GPRS and 2 A-bis timeslots in case of GPRS+EGPRS data transfer. Use CDED, CDEF and CMAX to enable radio timeslots as GP TS as specified in the test case. (E)GPRS link adaptation is enabled.


Set up (E)GPRS data transfer(s) in uplink direction (on one radio timeslot) as specified in test case. Monitor A-bis Continue to set up additional (E)GPRS data transfers as specified in the test case.

Data transfer begins. A-bis shows CS4 in use for GPRS data transfer and MCS 9 for EGPRS data transfer. All data transfers are set up. A-bis shows CS4 in use for GPRS data transfer and MCS 9 for EGPRS data transfer. The data rates are reduced to due to uplink scheduling

DN0694168 Issue 2-0




Data transfer

Additional data transfer

No. of GP RTSL

2 2 TRX EDGE HW

MBCCHC +TCHF GPRS and EGPRS

GPRS-7, EGPRS - 2

11

22.16 TRX Loop Test

Purpose: To check that following TRX loop test runs with modulation scheme CS3/CS4:

ABIS1/AIR1, ABIS3/AIR1, ABIS1/AIR3, ABIS1/AIR4, ABIS3/AIR4

Note 132. Acceptable test results are: BER<0.1%, FER<0.1%

Test Tools Required: Spectrum Analyser, CMU

Input Expected Output Use Any Multi TRX configuration. BTS is in Supervisory State with all the TRXs up and working. An MS-MS call is made using the TRX to be tested (Any call type can be used i.e. EFR, FR, AFS, AHS). Select from the TRX Loop Test Option from the BTS Manager, loop test type & coding scheme as defined in the test. Loop Test is started for the TS (Non control channel/traffic TS).

The loop test result indicates success. The test results are acceptable. TS carrying control channels and traffic are not tested. The calls are not affected. For Testcase6: The O&M SW returns an error message that the test is not supported with this modulation scheme (e.g. ABIS 2 \ AIR 1).

Start a data transfer on BCCH TRX. Set PMAX=25 and PMIN=30 and observe the transmitted power.

Data transfer is started successfully. Transmitted power is in accordance with the parameters PMAX and PMIN.

DN0694168 Issue 2-0


The test is repeated for every TSs in the BTS in both BCCH and non-BCCH TRXs except those on which Calls are established. The colour of unit LED’s is verified at the BTS and the BTS manager equipment view.

The test is started for idle channels. TS carrying control channels and traffic are not tested. The calls are not affected. The colour of TSxx and BB2x units LED’s at the BTS and BTS manager are red during the test and return back to original colour when test finishes. The test results are acceptable. For AIR4 Loop Test CMD device is used as the results of the loop test are not displayed on the BTS Manager For Testcase6: The O&M SW returns an error message that the test is not supported with this modulation scheme (e.g. ABIS 2 \ AIR 1).

Case Ref.

Channel Configuration Coding Scheme Selected

Loop test

1 Any EDGE configuration with MBCCH+SDCCH/TCHFs

CS3 ABIS1/AIR1

2 MBCCH+SDCCH/TCHDs CS3 ABIS3/AIR1 3 Any CS4 ABIS1/AIR3 4 Any CS4 ABIS3/AIR4 5 Any CS4 ABIS1/AIR4 6 Multi TRX EDGE HW with

MBCCHC + MPBCCH+TCHF CS3 & CS4 ABIS2/AIR1

7 2 omni EDGE HW with MBCCHC + TCHF

CS3 & CS4 ABIS 1 \ AIR 1 ABIS 3 \ AIR 1 ABIS 1 \ AIR 3 ABIS 1 \ AIR 4

ABIS 3 \ AIR 4 (for last two test cases CMU is to be used)

8 Multi TRX EDGE HW/ MBCCHC + TCHF

CS3 & CS4 ABIS 1 \ AIR 1 ABIS 3 \ AIR 1 ABIS 1 \ AIR 3 ABIS 1 \ AIR 4

ABIS 3 \ AIR 4 (for last two test cases CMU is to be used)

DN0694168 Issue 2-0


22.17 Abis loop test

Purpose:

The purpose of this case is to prove that Abis loop test can be executed successfully on the EDGE TRX having GPRS data transfer with CS3/CS4 coding schemes.

Test Tools Required: None.

Input Expected Output Use configuration as defined in the case Dynamic A-bis is enabled.

Site is up and working with DAP enabled.

Packet data transfer is started using TCP/IP in GP radio timeslot with coding scheme CS3 in DL direction


An Abis loop test is started from the BSC using MML command ZUBK for all TSLs

The test is started.

The loop test results are checked with the MML command ZUBP for all TSLs.

The test status indicates success. The test results are acceptable. TS carrying control channels and GPRS traffic are not tested. The calls are not affected. Test does not affect GPRS transfer and data transfer is successful.

Case Ref.

BTS Channel Configuration Coding scheme

1 Multi TRX with EDGE HW MBCCHC + TCHF CS3 & CS4

22.18 Intelligent Shutdown

Purpose:

To verify that PCU synchronises and Data transfer using coding schemes CS4 is successful after site recovers from NONE shutdown mode.


Input Expected Output Use configuration as defined in the case. Dynamic A-bis is enabled. Use NONE shutdown mode.

Packet data transfer is started using TCP/IP in GP radio timeslot with coding scheme CS4 in DL direction.


DN0694168 Issue 2-0


Input Expected Output The mains breakdown alarm is generated. The BSC starts the NTIM Timer. The set time for the NTIM timer expires.

Alarm ‘7995:MAINS BREAKDOWN WITH BATTERY BACK-UP’ is reported at the BSC and BTS Manager.

Site enters in BCCH shutdown mode. , BSC reconfigures GP Time Slot(s) on BCCH TRX. PCU FRAME SYNCHRONISATION Messages will be seen for new GP Time Slot(s) and GPRS data transfer will continue after PCU Frame Synchronisation is done

The BSC starts the BTIM Timer. The set time for the BTIM timer expires.

Site enters in None shutdown mode and all TRXs go in BL-PWR state.

GPRS data call is dropped.

The mains breakdown alarm is cancelled The ‘7995:MAINS BREAKDOWN WITH BATTERY BACK-UP’ is cancelled at the BSC and BTS Manager. The BSC sends BTS_PWR_SUPPLY_CONTROL (switch on each TRX) message to the BCF for each BTS. Site recovers successfully and PCU synchronises.

Packet data transfer is started using TCP/IP in GP radio timeslot with coding scheme CS4 in DL direction.

Data transfer successful.

Case Ref.


1 Multi TRX EDGE HW MBCCHC+ TCHF, GP is on non BCCH TRX 2 Multi TRX, EDGE HW MBCCHC+MPBCCH + TCHF, GP is on non

BCCH TRX

22.19 Load and stability testing

Purpose:

The purpose of these tests is to check the stability of the BTS SW when the TRX is in heavy GPRS/EGPRS static load with some static speech calls with CS3 & CS4 enabled in sector.

Test Tools Required: MAD server

Input Expected Output Use configuration as defined in the case. Dynamic A-bis is enabled. CS3&CS4 enabled in sector.


Memory block reservations are checked before and after the test by using BB2x trace.

There are as many BB2 memory blocks reserved as there were before the test.

DN0694168 Issue 2-0


Input Expected Output Set up GPRS, EGPRS and Speech calls as mentioned below respectively to fill all the timeslots of the TRXs. GPRS, EGPRS and Speech calls are on for the entire test duration. 1 MB file is used for data transfer in DL direction, repeatedly sent during the period of testing on all GPRS/EGPRS calls.

All GPRS, EGPRS and Speech calls remain on during the whole period of testing. All Data transfers are successful.

Case Ref.


Test case duration

Link Adaptation

Call types

1 2+2, EDGE HW

MBCCHC+MPBCCH + TCHF

4 hrs ON First sector: 4 HR calls, 4 EFR calls, 2 GPRS data calls [2 RTSL], 2 EGPRS Data calls [2RTSL] Second sector: 4 HR calls, 4EFR calls, 2 GPRS data calls [2 RTSL], 4 GPRS Data calls [1RTSL]

23. GHOST RACH AND PRACH TESTS

23.1 Ghost RACH and PRACH Absolute Test

Purpose: To check that the rate at which the basestation generates ghost (P)RACH messages is below an acceptable level.

Note 133. During the lifetime of a software release a small sub-set of the tests below should be periodically performed to monitor the number of ghosts that are being generated. This is because improvements in the receiver performance during the release will affect the ghost performance as well. Towards the end of release testing, once the final fine tuning of the EQDSP has been carried out, a comprehensive set of tests must be performed.

Note 134. The process of detecting RACHs and PRACH burst is the same for non-combined and combined BCCH configurations. Because there are more TDMA frames within the multiframe available to listen for RACHs in the non-combined BCCH the number of ghost generated will always be greater. In other words, an acceptable result for MBCCH will inevitably mean an acceptable result for MBCCHC. For this reason MBCCHC is not tested on its own.

Note 135. Because the antennas in this test are terminated with loads in this test, the basestation should not detect any real (P)RACHs. Only internally generated noise

DN0694168 Issue 2-0


that is detected as having a valid training sequence should result in a low level of ghost (P)RACHs.

Note 136. Because the generation of ghost (P)RACHs is essentially a random process, and because the number of ghosts expected is a very small proportion of all frames that the receiver listens for, it is important to monitor a sufficient number of BCCH channels for a long enough period in order to obtain a meaningful result.


Create the configuration indicated in the table and shown in the diagrams below. Ensure all RF cables have the correct torque. Configure the BCCH as indicated in the table and the remaining timeslots as shown in [Table 7]. Set the ARFN as shown in [Table 8], [Table 9], [Table 10] or [Table 11] depending on the configuration indicated.

Set Cell Bar = Y using MML command: ZEQF:BTS=<bts number>:BAR=Y;

Site is created with the configuration indicated in table.

Create an EDAP and enable GPRS and EGPRS. Set diversity as shown in the table using MML command: ZEQM:BTS=<bts number>:RDIV=<Y or N>; Commission the site and bring it into working order.

Site is up and working.

Maximise the number of paging blocks in the multiframe, and reduce number of multiframes before paging group is repeated using the MML command: ZEQJ:BTS=<bts number>:AG=1,MFR=2; Use a script to generate paging on each paging block on the CCCH.

Paging load is generated on each paging block

50 ohm, 50W terminating loads must be put on each antenna. Firmly close the door of the cabinet.

Each antenna is properly terminated.

DN0694168 Issue 2-0


Set up an A-bis monitor to trace the channels indicated in [Table 12]. Record traces every 24 hours for a total of 72 hours. Analyse the traces and count the messages indicated in [Table 12] for each type of BCCH. Calculate the number of ghosts per BCCH channel per 24 hour period in the following way: total num messages in elapsed time for all BCCH channels of same type Ghosts = ------------------------------------ Num 24hr periods x num BCCH channels

The number of Ghosts/BCCH/24 hours is below the acceptance limit indicated in the table.

Case Ref. Config Band BCCH type RDIV Acceptance Limit Ghosts per channel per 24 hours

1 Figure 8 800 MBCCH only Y 50 2 Figure 8 1800 MBCCH only N 20 3 Figure 9 900 MBCCH only Y 50 4 Figure

10 1900 MBCCH only Y 50

5 Figure 11

800 MBCCH only N 20

6 Figure 11

900 MBCCH only Y 50

7 Figure 11

1800 MBCCH only Y 50

8 Figure 11

1900 MBCCH only N 20

Table 7 Timeslot Configuration for Each BCCH Type

MBCCH only 0 MBCCH 1 SDCCH 2 TCHF 3 TCHF 4 TCHF 5 Gp 6 Gp 7 Gp

Table 8 ARFN to Set for DVxx Config Sector 800 900 1800 1900

1 128 1 512 512

2 153 25 587 572

3 177 50 662 632

4 202 75 737 692

DN0694168 Issue 2-0


5 226 100 812 752

6 251 124 885 810

Table 9 ARFN to Set for RTC Config

Sector 800 900 1800 1900

. 1 128 1 512 512

. 2 251 124 885 810

Table 10 ARFN to Set for 4UD Config

Sector TRX 800 900 1800 1900

1 153 25 587 572 . 1 3 177 50 662 632 5 202 75 737 692 . 2 7 226 100 812 752

Table 11 ARFN to Set for MetroSite

Sector 800 900 1800 1900

. 1 153 25 587 572

. 2 177 50 662 632

. 3 202 75 737 692

. 4 226 100 812 752

1.

Table 12 Messages and Channels to Monitor on A-bis

BCCH

Channels Messages

MBCCH TRXSIG A-bis TS for each BCCH TRX Stack = GSM A-bis

CHANNEL REQ P-CHANNEL REQ EGPRS PACKET CHANNEL REQUEST

MBCCHC TRXSIG A-bis TS for each BCCH TRX Stack = GSM A-bis


DN0694168 Issue 2-0


Figure 8

50 ohm, 30Watt load fitted to each antenna

Door Closed

1+1+1+1+1+1 Bypass configuration, but cabled in pairs for 2 way diversity. All TRX in the same band.

UltraSite with DVxx

DN0694168 Issue 2-0


Figure 9


1+1 RTC configuration, cabled for 2 way diversity. All TRX in the same band. Put 50 ohm terminators on unused RF ports.

UltraSite with RTC

Door Closed

DN0694168 Issue 2-0


Figure 10


Door Closed

2 + 2 4UD Bypass configuration. All TRX in the same band.

UltraSite with 4UD

DN0694168 Issue 2-0


Figure 11


1+1+1+1 configuration, but cabled for 2 way diversity. All TRX in the same band.

MetroSite Config for Absolute Ghost Test

DN0694168 Issue 2-0


23.2 Ghost RACH and PRACH Relative Test

Purpose: To check that the rate at which the basestation generates ghost (P)RACHs has not significantly increased compared to the previous software release.

Note 137. Because the generation of ghost (P)RACHs is essentially a random process, and because the number of ghosts expected is a very small proportion of all frames that the receiver listens for, it is important to monitor a sufficient number of BCCH channels for a long enough period in order to obtain a meaningful result.

Note 138. In these tests two identical basestation configurations run different software packages. Because the antennas are shared in these tests the basestations should be listening to the same noise. By swapping the software packages half way through the test, the affects of hardware differences should be removed.

Input Expected Output Create the configurations indicated in the table and shown in the diagrams below. Choose either 1800 or 1900 band. Configure the BCCH as indicated in the table and the remaining timeslots as shown in [Table 13] Set the on both BCF to the ARFN as shown in [Table 14] Set Cell Bar = Y using MML command: ZEQF:BTS=<bts number>:BAR=Y;

Site is created with the configuration indicated in table.

DN0694168 Issue 2-0


Create an EDAP and enable GPRS and EGPRS. Enable diversity using MML command: ZEQM:BTS=<bts number>:RDIV=Y; Set the BTS power to minimum using MML command: ZEUG:BTS=<bts num>:PMAX1=30,PMAX=30, PMIN=30; Make the default package on the first BCF the most recent released version of the software under test. Make the default package on the 2nd BCF the latest pre-release of the release under test. Ensure that the hardware for each basestation is as identical as possible (units, cable lengths and types, splitter types, attenuator types etc.). Ensure all RF cables are correctly torqued. Commission the sites and bring them into working order

Site is up and working.

Switch off all mobile stations within 20 metres of the basestations. Set up an A-bis monitor to trace the channels indicated in [Table 15]. Record traces for 24 hours. Swap the software packages over so that the previous release is on the 2nd BCF and the new release is on the 1st BCF. Record traces for a further 24 hours. Analyse the traces separately for first 24 hours and next 24 hours , count the number of messages indicated in [Table 15].Do NOT count those (P)RACHs that lead to successful channel activations (i.e. real Location Updates etc.) Calculate the number of ghosts per BCCH channel per 24 hour period in the following way: total num messages in elapsed time for all BCCH channels of same type Ghosts = ------------------------------------ Num 24hr periods x num BCCH channels Compare the results for the two software packages

The Ghosts/BCCH/24hr must not have increased by more than 10%.i.e. New SW ≤ 1.1 x Previous released package

DN0694168 Issue 2-0


Case Ref. Config BCCH Type 1 Figure 12Figure

12 MBCCH only

2 Figure 12Figure 12

MBCCHC

3 Figure 13Error! Reference source not found.

MBCCH only

4 Figure 13 MBCCHC

DN0694168 Issue 2-0


Table 13 Timeslot Configuration for Each BCCH Type

MBCCH only MBCCHC 0 MBCCH MBCCHC 1 SDCCH SDCCH 2 TCHF TCHF 3 TCHF TCHF 4 TCHF TCHF 5 Gp Gp 6 Gp Gp 7 Gp Gp

Table 14 ARFN to Set

Sector 1. 1800 1. 1900

. 1 2. 512 2. 512

. 2 3. 636 3. 611

. 3 4. 760 4. 710

. 4 5. 885 5. 810

DN0694168 Issue 2-0


Table 15 Messages and Channels to Monitor on A-bis

BCCH

Channels Messages

MBCCH TRXSIG A-bis TS for each BCCH TRX Stack = GSM A-bis


MBCCHC TRXSIG A-bis TS for each BCCH TRX Stack = GSM A-bis


Figure 12

1+1+1+1 Bypass configuration, but cabled in pairs for 2 way diversity. All TRX in the same band. Previous release software.

1+1+1+1 Bypass configuration, but cabled in pairs for 2 way diversity. All TRX in the same band. New software under test.

50 ohm, 30dB attenuators

Splitter/combiners

BCF 1 BCF 2

UltraSite Config for Relative Ghost Test

DN0694168 Issue 2-0


Figure 13

1+1+1+1 configuration, but cabled for 2 way diversity. All TRX in the same band.

MetroSite Config for Relative Ghost Test

BCF 1 BCF 2

50 ohm, 30dB attenuators

Previous software release New software release

DN0694168 Issue 2-0


24. MODIFICATION OF TIMER VALUES FROM BSC

24.1 Modification of LAPDm Timer value from BSC

Purpose: To check that LAPDm timer value can be modified from the BSC

Note 139.

For detailed understanding of LAPDm T200 refer 3GPP TS 44.006

Input Expected Output Define a BTS site as mentioned in the test case. The site is defined successfully and it is in

Supervisory state Modify the T200F and T200S values from the BSC as defined in the test case

Values can be modified from the BSC.

Monitor the ABIS traces. From the Abis traces it can be verified that BTS_CONF_DATA is sent with new ‘IE’ BTS_LAPD_T200_VALUES containing the modified values. BTS_ACK should be sent to the BSC

Lock the BCF from the BSC and Unlock it after 2 minutes.

In the BTS_CONF_DATA message, the BTS_LAPD_T200_VALUES shows the changed values.

Case Ref. Configuration T200F and T200S values 1 2+2+2, DVxx, RAH Both ‘0’ 2 6 Omni, RTC, BB Hopping ‘200’ and ‘220’ 3 2+2, IDD with 4UD ‘400’ and ‘500’

24.2 Modified LAPDm T200 with Multi BCF

Purpose: To check that the Multi-BCF sites come into working order regardless of the LAPDm timer values for different BCFs

Note 140.


DN0694168 Issue 2-0


Input Expected Output The site is configured as shown in the diagram below Create the synchronisation chain at the BSC using the MML command: ZEFM: <mm>: CS=BCF, SENA=T, ADD=<s1>; <mm> = master BCF number <s1> = slave BCF number Physically create and commission the sites.

The site comes up in WO state

Set T200F and T200S=0 for Master BCF on the BSC. Set T200F and T200S=1260 for Slave BCF on the BSC. Power off the BCFs

Modification at the BSC is successful. The BTS Manager gets disconnected. BCCH missing and PCM failure alarm is raised on the BSC.

Power on the Master BCF. The Master BCF comes into working order without raising any synchronisation alarms. The BTS Events window shows that the BCF is in Master mode. From the Abis traces it can be verified that BTS_CONF_DATA is sent with ‘IE’ BTS_LAPD_T200_VALUES containing the T200 values as defined for the Master BCF BTS_ACK should be sent to the BSC

Power on the Slave BCF. The slave BCF comes into working order without raising any synchronisation alarms. The BTS Events window shows that the BCF is in slave mode. From the Abis traces it can be verified that BTS_CONF_DATA is sent with ‘IE’ BTS_LAPD_T200_VALUES containing the T200 values as defined for the Slave BCF BTS_ACK should be sent to the BSC

Calls are established in all the BTSs Calls are successful Case Ref. Configuration 1 BTS1&3 (EDGE) RF Hopping, BTS2&4 (GSM)

DN0694168 Issue 2-0


UltraSite-UltraSite

BTS 3 Hop = RF MA = same as BTS 1HSN1 = same as BTS 1 BTS 4 Non-hopping

SEGMENT

BTS1

BTS2

BTS3

BTS4

BCF

BCCH

MASTER SLAVE BCF 2

BTS 1 Hop = RF MA = xx (5 ARFN) HSN1 = yy BTS 2 Non-hopping

1

22

33

44

DN0694168 Issue 2-0


24.3 Verification of SDCCH T200 timer value

Purpose:

The purpose is to verify that SDCCH T200 timer expires as defined at the BSC irrespective of the SAPI

Note 141.


Note 142. TEMS set-up to be used for Air Interface monitoring

Note 143. One may find some delay in the retransmissions (e.g. T200S is set as 400 mS and retransmissions are occurring at 470 mS) due to the long block occurrence of SDCCH. UC needs to wait that the next SDCCH block occurs and only then the UC can send the DL SDCCH message again.

Note 144. ERROR_ IND message may not be seen in the Abis as other BSC timers may get expired before the time period of the product of [ T200*(N200+1) ]. For e.g. Timer T3107 supervises the Assignment procedures and it max value is 7sec.

Equipment and BTS Set-Up As per the test case

DN0694168 Issue 2-0


Input Expected Output Define SDCCH T200 = 400 FACCH call set-up is disabled in the BSC Define RLT=64 and ARLT=64 Disable SDCCH handover for the BTS Dynamic SDCCH feature is disabled from the BSC

The parameters are successfully defined at the BSC.

MS A tries to call MS B latched on a different BTS. During the signalling phase of the call setup introduce very high interference in the UL direction

Call is not successful. Verify from the TEMS set-up that the retransmission of the layer2 frames occurs after every 400 ms (T200) It is observed that as soon as the BTS is not able to decode the UL messages BTS sends ERROR_ IND message with cause 1 = T200 expired with N200+1 times.

Change SDCCH T200 to 600 MS A tries to call MS B. During the signalling phase of the call setup introduce very high interference in the UL direction

Call is not successful. Verify from the TEMS set-up that the retransmission of the layer2 frames occurs after every 600 ms (T200) It is observed that as soon as the BTS is not able to decode the UL messages BTS sends ERROR_ IND message with cause 1 = T200 expired with N200+1 times. It is clear from the Abis trace that ERROR_IND message is delayed by almost [200*(N200+1)] ms in the second scenario.

Case Ref. Configuration 1 Any

DN0694168 Issue 2-0


Input Expected Output Define SDCCH T200 = 400 Disable SDCCH handover for the BTS Dynamic SDCCH feature is disabled from the BSC

The parameters are successfully defined at the BSC.

MS A tries send an SMS to MS B latched on a different BTS. During the signalling phase introduce very high interference in the UL direction

SMS sending failed is displayed on MS A Verify from the TEMS set-up that the retransmission of the layer2 frames occurs after every 400 ms (T200) It is observed that as soon as the BTS is not able to decode the UL messages BTS sends ERROR_ IND message with cause 1 = T200 expired with N200+1 times.

Change SDCCH T200 to 600 MS A tries send a SMS to MS B During the signalling phase introduce very high interference in the UL direction

SMS sending failed is displayed on MS A Verify from the TEMS set-up that the retransmission of the layer2 frames occurs after every T200ms It is observed that as soon as the BTS is not able to decode the UL messages BTS sends ERROR_ IND message with cause 1 = T200 expired with N200+1 times. It is clear from the Abis trace that ERROR_IND message is delayed by almost [200*(N200+1)] ms in the second scenario.

Case Ref. Configuration 2 Any

24.4 Verification of FACCH T200 timer value

Purpose:

The purpose is to verify that FACCH T200 timer expires as defined at the BSC.

Note 145.


Note 146. TEMS set-up to be used for Air Interface monitoring

Note 147. First retransmission may take more time than the defined value of T200F due to intracell handover when MS try to access the new traffic channel.

DN0694168 Issue 2-0


Note 148. ERROR_ IND message may not be seen in the Abis as other BSC timers may get expired before the time period of the product of [T200*(N200+1)]. For e.g. Timer T3107 supervises the Assignment procedures and it max value is 7sec.

Input Expected Output Define FACCH T200 = 400 Define RLT=64 and ARLT=64 Enable Intra cell handover for the BTS

The parameters are successfully set at the BSC.

MS A calls to MS B latched on a different BTS. Introduce very high interference in the UL direction to initiate Intra Cell handover.

Call is successful. BSC sends ASSIGNMENT COMMAND to the MS as seen on the Abis trace as well as on the layer3 window of the TEMS ASSIGNMENT COMPLETE message sent on the UL cannot be decoded Verify from the TEMS set-up that the retransmission of the layer2 frames occurs after every 400 ms (T200) It is observed that as soon as the BTS is not able to decode the UL messages BTS sends ERROR_ IND message with cause 1 = T200 expired with N200+1 times. RF Channel gets released.

Change FACCH T200 to 600 MS A calls to MS B latched on a different BTS. Introduce very high interference in the UL direction to initiate Intra Cell handover.

Call is successful. BSC sends ASSIGNMENT COMMAND to the MS as seen on the Abis trace as well as on the layer3 window of the TEMS ASSIGNMENT COMPLETE message sent on the UL cannot be decoded Verify from the TEMS set-up that the retransmission of the layer2 frames occurs after every 600 ms (T200) It is observed that as soon as the BTS is not able to decode the UL messages BTS sends ERROR_ IND message with cause 1 = T200 expired with N200+1 times. RF Channel gets released. It is clear from the Abis trace that ERROR_IND message is delayed by almost [200*(N200+1)] ms in the second scenario.

Case Ref. Configuration 3 One Omni

DN0694168 Issue 2-0


25. DRTRAU

General Notes for testing DR TRAU Note 149.

ICM of target BTS must be a part of ACS of source side.

Note 150. Codec mode of ICM of target BTS must be either of 4.75, 5.15, 5.90 or 6.70.

Note 151. Use a different ICM for each sector.

Note 152. Define the ACS such that all the codecs available in FR and HR codec set are used in the different test cases.

Note 153. Intercell Handovers (both synchronous and Asynchronous) can be triggered in two ways

1) By varying the signal level through variable attenuators manually.

2) By changing any one among the two sets of BTS level parameters mentioned below:

• ZEHB:BTS=XX:QDRF=<X>,QURF=<X>,QDRH=<X>,QURH=<X>,IHRF=<X>, IHRH=<X>;

• ZEAM:BTS=XX::ABTS=YY::LMRG=-24,PMRG=-24,QMRG=-24;

Note 154. Intracell handovers can be triggered by the following MML command in a sector or in a segment.

ZEHG:BTS=XX:EIC=Y,EIH=Y;

Make HO more likely. ZEHB:BTS=<XX>:IHRF=<0>,IHRH=< 0>;

Note 155. All test cases need to be performed on EDGE Hardware unless otherwise stated in the test case.

Note 156. All test cases need to be performed on BSC version S14 unless otherwise stated.

DN0694168 Issue 2-0


Note 157. Cases can be performed with any GSM band (GSM 800, GSM 900, EGSM 900, GSM 1800 or GSM 1900) unless specified.

Note 158. DR TRAU feature (Feature Code: 582) should be ‘ON’ in the BSC unless otherwise stated.

Note 159. All test cases must be performed with RDIV enabled at the BSC unless otherwise stated.

Note 160. All test cases are performed with BTS Manager connected, unless otherwise stated.

Note 161. Cases without any specified channel configuration are to be performed with combined or non-combined BCCH.

Note 162. The sites under test will be configured as per configuration table. The calls are terminated on a separate BTS which is not under test.

Note 163. For Synchronous Handover test cases BTS 1 and BTS 2 are in the same BCF, whereas for Asynchronous Handover cases BTS 1 and BTS 2 refer to two different BCF’s.

25.1 Support of DR TRAU framing in Synchronous and Asynchronous Handovers

Purpose: To check that DR TRAU framing is supported in both uplink and downlink during synchronous handovers between HR and FR channels, in an AMR call and there is no perceived effect to the end user during the handover procedure.

Hardware Tools Required

• Variable attenuators

• Abis monitoring tool

DN0694168 Issue 2-0


Input Expected Output Configure the site as defined in the test case. Define each of the two sectors as a neighbour of the other.


In the first sector, configure all the traffic channels to be of type TCHH and in the second sector, configure all the traffic channels to be of type TCHF.

The first sector consists of half rate traffic channels only and the second sector consists of full rate traffic channels only.

Lock all traffic channels in both the sectors. In the source BTS unlock the 7th timeslot of the BCCH TRX and in the target BTS unlock the 7th timeslot of a non-BCCH TRX.

Only one traffic channel remains unlocked in each sector.

Set up an AMR call in the first sector to an MS locked to a completely separate BTS and create continuous sound at both mobile stations. Monitor the Abis.

An AMR call is established in the first sector.

DN0694168 Issue 2-0


Trigger a to and fro handover between the two sectors and monitor the Abis [Note 153]

For HR to FR Handover: The source BTS receives a Mode Modify message from BSC containing ICM of target BTS, with 8 Kbit/s TRAU bit disabled and the FICM bit enabled. The source BTS sends CMR and CMC command to TC and MS respectively to step the codec to ICM of target BTS. The TC starts to encode with the ICM of target BTS and this is reflected in the CMI message sent by TC. The BTS now sends an ACK in response to the Mode Modify received earlier At the target BTS a Channel Activation message for FR is received with 8 Kbit/s TRAU & FICM bits enabled. An ACK is sent to the BSC. Target BTS starts receiving 8 Kbit/s TRAU frames on 16 Kbit/s sub-channel and synchronizes to it. A Handover command is sent to MS MS tunes to the new channel and starts receiving valid speech frames immediately. In the uplink, BTS sends 8 Kbit/s TRAU frames on 16 Kbit/s sub-channel. As soon as BSC receives handover complete message, a Mode Modify is message sent to target BTS with 8 Kbit/s TRAU & FICM bits disabled. A CMR is sent to TC using 16 Kbit/s TRAU frame indicating the ICM. TC sends CMI on 16 Kbit/s TRAU frame. Mode Modify ACK is sent now. CMC and CMR commands are sent to MS and TC respectively to start using any codec from ACS of the serving BTS. The MS and TC start to encode with codecs from ACS of serving BTS and this is reflected in the CMI message sent both by TC and MS. Channel is released for source BTS. The handover is successfully completed.

DN0694168 Issue 2-0


For FR to HR Handover: The source BTS receives a Mode Modify message from BSC containing ICM of target BTS, with 8 Kbit/s TRAU & FICM bits enabled. The source BTS, sends a CMR to TC to step the codec to ICM of target BTS and CMC to MS to change the codec mode to the first codec mode which is compatible with the 8Kbit/s DR TRAU format and which is a part of the ACS of source BTS. As soon as a CMI of 8Kbit/s compatible mode is received by the source BTS from MS, it sends a CMR to transcoder in the 8Kbit/s frame format on the 16Kbit/s Abis sub channel indicating ICM of target BTS. Upon receiving this message, TC sends a CMI in the 8Kbit/s frame format on the 16Kbit/s Abis sub channel indicating ICM of target BTS. Now the source BTS sends an ACK in response to the Mode Modify message. The BSC activates a HR channel at the target BTS. On receiving Channel Activation ACK message, the BSC duplicates TRAU data received from the A-ter interface both towards the source and target BTS. A Handover command is sent to MS MS tunes to the new channel and starts receiving valid speech frames immediately. MS sends Handover Complete message to the BSC. Channel is released for source BTS. The handover is successfully completed.

Handovers are triggered to target cell at least 50 times during the same call. [Note 153]

Handovers take place continuously between the two sectors and neither clipping sound nor any other disturbing noise is heard during this period.

Case Ref. Configuration Handover Type Hopping

1 2 (Mixed 5) + 2 (Mixed 2) Synchronous BB + No hopping

2 2+2 EDGE Synchronous BB + RF

3 BCF 1: 4Omni (E)

BCF 2: 4Omni (E)

Asynchronous BB + RF

4 BCF 1: 4Omni (BB2E)

BCF 2: 4Omni (BB2F)

Asynchronous BB+BB1

1Ensure that voice quality is good. Also listen to speech and verify that there is no distortion

DN0694168 Issue 2-0


25.2 Supported AMR codecs in DR TRAU

Purpose: To check that AMR codecs 4.75, 5.90 and 6.70 are supported by DR TRAU feature and link adaptation takes place on active calls according to prevailing channel conditions.




• Signal generator

• Spectrum analyzer

Input Expected Output Configure a 2 sector EDGE site with parameters as defined in the test case. Define each of the two sectors as a neighbour of the other.


In BTS1, configure all the traffic channels to be of type TCHH and in BTS2, configure all the traffic channels to be of type TCHF.


Lock all traffic channels in both the sectors. In the first sector unlock the 7th timeslot of the BCCH TRX and in the second sector unlock the 7th timeslot of any non-BCCH TRX.

One traffic channel in source and target BTS is in ‘WO’ condition.

Set up an AMR call in BTS1 to an MS locked to a completely separate BTS and create continuous sound at both mobile stations. Monitor the Abis.

A half rate call is set up in the first sector.

Set QMRG=24 using MML command ZEAM:BTS=<xx>:ABTS=<xx>:QMRG=24; Introduce interference in the uplink gradually.

The codec modes are seen to change from the least to the most robust mode in the uplink.

Introduce interference in the downlink gradually. The codec modes are seen to change from the least to the most robust mode in the downlink.

Remove interference from both uplink and downlink and set QMRG value to default i.e. 0 using MML command “ZEAM”.

Codec modes return to state, they were in, before the interference was introduced.

DN0694168 Issue 2-0


Trigger a handover from BTS1 to BTS2 [Note 153]

BTS1 receives a Mode Modify message from BSC with the FICM-bit enabled and 8 Kbit/s bit disabled. The MS and TC start to encode with the ICM of BTS2. BTS1 now sends an ACK in response to the Mode Modify received earlier. At BTS2 Channel Activation message for FR channel is received with 8 Kbit/s TRAU & FICM bits enabled. An ACK is sent to the BSC. BSC sends a handover command to BTS1. MS tunes to the new channel on BTS2 and starts receiving valid speech frames immediately. As soon as BSC receives handover complete message, a Mode Modify is sent to BTS2 with 8 Kbit/s TRAU & FICM bits disabled. BTS2 sends a CMR to TC, using 16 Kbit/s TRAU frame, indicating the ICM. TC sends CMI on 16 Kbit/s TRAU frame. Now, BTS2 sends a Mode Modify ACK. CMC and CMR commands are sent to MS and TC respectively to start using any codec from ACS of BTS2. The MS and TC start to encode with codecs from ACS of BTS2 and this is reflected in the CMI message sent both by TC and MS. Channel is released for BTS1. The handover is successfully completed.






DN0694168 Issue 2-0



BTS2 receives a Mode Modify message with the 8Kbit/s TRAU & FICM bits enabled. The MS starts using an 8Kbit/s compatible codec mode. The TC starts using the ICM of BTS1, at 8Kbit/s frame format on the 16Kbit/s Abis sub channel. Now BTS2 sends an ACK in response to the Mode Modify message. BSC sends a handover command to BTS1. Handover is successful.






Case Ref. ICM1 ACS1 ICM2 ACS2

1 4.75 4.75, 5.15, 5.90, 6.70 4.75 4.75, 7.4, 10.2, 12.2

2 5.90 4.75, 5.15, 5.90, 6.70 5.90 4.75, 5.90, 7.40, 12.2

3 6.70 4.75, 5.15, 5.90, 6.70 6.70 4.75, 5.90, 6.70, 12.2

4 5.15 4.75, 5.15, 5.90, 6.70 5.15

5.15, 7.95, 10.2, 12.2

25.3 Unsuccessful Handovers

Purpose: To check that during DRTRAU handover failure of an AMR call between HR and FR channels, the call is not released and is sustained by GSM signalling.


• Variable attenuators,

• Abis monitoring tool.

Input Expected Output Configure the site as described in the test case. Define each of the two sectors as a neighbour of the other.


DN0694168 Issue 2-0


Block the BTS2 main and diversity receive paths, and terminate them using an RF terminator so that the air uplink interface will not work.

The second sector will not receive any signal from the MS via air uplink interface.



Lock all traffic channels except one in both sectors.

The first sector can only support two half rate calls. The second sector can only support a single full rate call.

Set up an AMR call in BTS1 to an MS locked to a completely separate BTS. Monitor the Abis.

A half rate call is set up in the first sector.


BTS1 receives a Mode Modify message containing ICM of BTS2, with FICM-bit enabled and 8 Kbit/s TRAU bit disabled. BTS1 sends CMR and CMC commands to TC and MS respectively to step the codec to ICM of target BTS. The MS and TC start to encode with the ICM of BTS2 and this is reflected in the CMI message sent both by TC and MS. The BTS now sends an ACK in response to the Mode Modify received earlier. At BTS2 Channel Activation message for an FR channel is received with 8Kbit/s & FICM bits enabled. BSC sends a handover command to BTS1. Since MS is not able to access target channel in BTS2, it returns to BTS1 and sends a Handover Failure indication to the BSC. The BSC sends a Mode Modify message with FICM bit disabled to BTS1. This is immediately acknowledged. The call continues in the first sector.

Terminate the call. The call is terminated Unblock the BTS2 main and diversity receive paths.

The second sector will now start receiving signals via air uplink interface.

Block the BTS1 main and diversity receive paths, and terminate them using an RF terminator so that the air uplink interface will not work.

The first sector will not receive any signal via air uplink interface.


A full rate call is set up in the second sector.

DN0694168 Issue 2-0



BTS2 receives a Mode Modify message containing ICM of BTS1, with 8Kbit/s & FICM bits enabled. The source BTS, sends a CMR to TC to step the codec to ICM of target BTS and CMC to MS to change the codec to an 8Kbit/s compatible codec mode. As soon as a CMI of 8Kbit/s compatible mode is received by the source BTS from MS, it sends a CMR to transcoder in the 8Kbit/s frame format on the 16Kbit/s Abis sub channel indicating ICM of target BTS. Now BTS2 sends an ACK in response to the Mode Modify message. The BSC now activates an HR channel at BTS1. As soon as the BSC receives Channel Activation ACK message it sends a handover Command to BTS2. Since the MS is not able to access target channel in BTS1, it returns to BTS2 and sends a Handover Failure indication to the BSC. The BSC sends a Mode Modify message with 8Kbits/s and FICM bits disabled, to BTS2. A CMR is sent to the transcoder to start using the ACS of BTS2 using 16Kbits/s frame format. The TC acknowledges this with a CMI using the 16Kbits/s frame format. An ACK is sent in response to the Mode Modify message by BTS2. The call continues in the second sector.


1 2+2 EDGE 25.4 Support of Normal Handover

Purpose: To check that normal handover is performed between HR and FR channels in an AMR call, when ICM of target BTS is not part of the ACS of the source BTS.

DN0694168 Issue 2-0





Input Expected Output Configure the site as described in the test case. Define each of the two BTSs as a neighbour of the other. Make sure that the ACSs of both BTSs do not have any common codecs.




Lock all traffic channels in both the sectors except one in each.

One traffic channel in source and target BTS is in ‘WO’ condition.


A half rate call is set up in BTS1.


A channel activation message is sent to BTS2 to activate a FR channel. As soon as an ACK is sent for this message, BSC sends a handover command to BTS1. Mode Modify messages are sent to either BTS during the handover process. The call is successfully handed over to BTS2.

The call is sustained and a handover is triggered to BTS1 [Note 153]

A channel activation message is sent to BTS1 to activate a HR channel. As soon as an ACK is sent for this message, BSC sends a handover command to BTS2. No Mode Modify messages are sent to either BTS during the handover process. The call is successfully handed over to BTS1.

Case Ref. Configuration Handover Mode

1 2+2 EDGE Synchronous

2 4 Omni EDGE Asynchronous

25.5 Packing and Unpacking of AMR calls with DR TRAU

Purpose: To ensure that packing of FR AMR calls to HR AMR calls due to cell load and unpacking of HR AMR calls to FR AMR calls due to call quality works properly and DR TRAU handovers are carried out during this process.

DN0694168 Issue 2-0


Note 164.

• Packing and unpacking the FR and HR calls are performed via intra cell handovers.

• BTS parameters ‘Lower limit for FR TCH resources’ and ‘Upper limit for FR TCH resources’ are set at the BSC with the MML command ZEQM.

• The test cases in this section are to be performed on BSC version S13.


• Signal Generators



Configure a site as described in the test case. The site is in supervisory state.

Lock all timeslots except one in each TRX. Only one timeslot per TRX is available to support calls

Set FRU = 60 and FRL = 40 using ZEQM command at the BSC.

The FRU and FRL are set accordingly.

A call is made on this BTS. An FR AMR call is established.

More such FR AMR calls are made on the BTS until the number of free full rate resources fall below the lower limit value for FR calls, defined at the BSC.

FR AMR calls are packed to HR AMR calls until the free FR resource increases above the upper limit value. DR TRAU Handover takes place during the packing process The packing takes place only when the quality of FR AMR calls is above the parameter ‘intra HO threshold Rx Qual for AMR FR’ and the least robust Codec mode is in use.



Disconnect all calls except one HR call pair. There is only one pair HR AMR calls active in the BTS.

Vary the C/I so that the quality of the HR AMR call degrades under the BTS parameter ‘intra HO threshold Rx Qual for AMR HR’. Monitor the Abis

The HR calls are unpacked into FR calls. DR TRAU Handover takes place during the unpacking process


No audio clips or disturbances are observed during handover.

Case Ref. Configuration Hop LA UL DTX

DL DTX

DN0694168 Issue 2-0



1 UltraSite/

4 Omni EDGE, TCHD AHOP Fast On On

2 4 Omni EDGE, TCHD, Use BSC S13 BB Slow On On

3 4 Omni EDGE, TCHD RF Slow Off On 4 4 Omni EDGE, IDD/4UD,TCHD RF Slow On On 25.6 Intra Cell Handovers with Speech Break less than 100 ms

Purpose: To ensure that during Intra Cell handovers between speech channels of the same rate, the maximum speech break during handover is not more than 100 milliseconds and there is no perceived effect to the end user during the handover procedure. Hardware Tools Required

• Abis monitoring tool Input Expected Output Configure site as defined in the test case. Site is in supervisory state. Lock all traffic channels in the sector. Unlock the 7th timeslot of the BCCH TRX and the 7 timeslot of any other non-BCCH TRX.

All TCHs are locked accept two.

Set handover parameters such that handovers occur repeatedly [Note 154]

Handover parameters are set accordingly.

Set up an AMR call in the BTS to an MS locked to a completely separate BTS and create continuous sound at both mobile stations. Monitor the Abis. Make sure that the codec in use when a call is established and the ICM of the BTS are not same.

An AMR call is established. As the call gets continuously handed over from TCH to another TCH the following messages are seen on the GSM Protocol Analyser.

DN0694168 Issue 2-0


The BTS receives a Mode Modify message from BSC, with the FICM-bit enabled. The BTS, sends a CMR to TC to step the codec to ICM of target BTS The TC sends a CMI indicating ICM of target BTS. Upon receiving this message the BTS sends an ACK to the Mode Modify message. It is to be noted that UL codec mode must not change as quickly as DL codec mode and it must follow the LA principle. A Channel Activation message is now received with FICM bit enabled. A Channel Activation ACK is sent to the BSC. As soon as the BSC receives Channel Activation ACK message, the BSC duplicates TRAU data received from the A-ter interface both towards the source and target channels. An assignment command is sent to the BTS to start using the newly activated channel. As soon as the call is handed over to the newly activated channel, an Assignment Complete message is sent to the BSC. Mode Modify is received with FICM bit disabled. BTS sends a Mode Modify ACK. Handover is successfully completed and the idle time between source and target channel speech frames is no longer than 100 ms and quality of speech call is also good. No clipping sound or other disturbing noise is heard during the handover process.

Unlock all TCHs. All TCHs are unlocked. Set up a pair of AMR calls in the same BTS and observe the call quality over 50 handovers. [Note 154]

As the calls get continuously handed over to different TCHs in the same BTS, no clipping sound or other disturbing noise is heard

Repeat the above steps by making sure that the codec in use during the call and the ICM are same

All signalling will be same as above except that no CMR command will be sent to TC by BTS.

Case Ref. Configuration TCH UL DTX DL DTX LA

1 4 Omni EDGE TCHF On Off Fast

2 4 Omni EDGE TCHF On Off Fast

3 4 Omni EDGE TCHH Off Off Slow

DN0694168 Issue 2-0


Purpose: To check that Abis signalling scenarios are supported during intracell handovers between HR and FR channels in an AMR call with the maximum speech break during handover being not more than 100 milliseconds and there is no perceived effect to the end user during the handover procedure. Equipment and BTS Set-Up Sites – As per configuration, a separate UltraSite/MetroSite for call termination.

Abis monitoring tool

Input Expected Output Configure site as defined in the test case. Configure approximately half the TCHs as of type TCHF and the rest as of type TCHH in each TRX. Lock all the TCHs in the BTS. Unlock one TCHH and one TCHF time slot in one of the TRXs. Set handover parameters such that handovers occur repeatedly [Note 154].


Set up an AMR call in the BTS to an MS locked to a completely separate BTS and create continuous sound at both mobile stations. Monitor the Abis. Make sure that the codec in use when a call is established and the ICM of the BTS are not same.

An AMR call is established. As the call gets continuously handed over from Full Rate TCH to Half Rate TCH and vice versa, the following messages are seen on the GSM Protocol Analyser.

DN0694168 Issue 2-0


Input Expected Output In case of HR to FR handover:

BTS receives a Mode Modify message with FICM-bit enabled and 8 Kbit/s TRAU bit disabled. The BTS sends CMR command to TRAU to step the codec to ICM and CMC command to MS to change the codec to ICM. The MS and transcoder start to encode with the ICM and this is reflected in the CMI message sent both by TC and MS. The BTS now sends an ACK in response to the Mode Modify received earlier. A Channel Activation message for FR channel is now received with 8 Kbit/s TRAU & FICM bits enabled. A Channel Activation ACK is sent to the BSC. Target channel receives 8 Kbit/s TRAU frame on 16 Kbit/s sub-channel and synchronizes to it. An assignment command is sent to the BTS to start using the FR channel. As soon as the call is handed over to the FR channel, an Assignment Complete message is sent to the BSC. As soon as BSC receives assignment complete message, a Mode Modify message is sent to the BTS with 8 Kbit/s TRAU & FICM bits disabled. BTS sends a CMR to TC using 16 Kbit/s TRAU frame indicating the ICM. TC sends CMI on 16 Kbit/s TRAU frame indicating ICM is in use. Now, the BTS sends a Mode Modify ACK. CMC and CMR commands are sent to MS and TC respectively to start using any codec from ACS of the BTS. The MS and TC start to encode with codecs from ACS of the BTS and this is reflected in the CMI message sent both by TC and MS. The HR Channel is now released. Handover is successfully completed and the idle time between source and target channel speech frames is no longer than 100 ms and quality of speech call is also good.

DN0694168 Issue 2-0


Input Expected Output In case of FR to HR handover:

The BSC sends a Mode Modify message to the BTS in which the FICM and 8Kbits/s TRAU bit is set. The BTS sends CMR command to TRAU to step the codec to ICM and CMC command to MS to change the codec to an 8Kbits/s compatible codec mode. As soon as a CMI of 8Kbits/s compatible mode is received by the BTS, it sends a CMR to transcoder in the 8Kbits/s frame format on the 16Kbits/s Abis sub channel indicating ICM of BTS. Upon receiving this message, the TC steps down to the 8Kbits/s frame format. The TC sends a CMI indicating that the ICM of the BTS is being used. Upon receiving this message, the source BTS sends an ACK to the Mode Modify message. A Channel Activation message for HR channel is now received with 8 Kbit/s TRAU bit disabled and FICM bit enabled. A Channel Activation ACK is sent to the BSC. As soon as the BSC receives Channel Activation ACK message, the BSC duplicates TRAU data received from the A-ter interface both towards the source and target channels. An assignment command is sent to the BTS to start using the HR channel. MS tunes to the new channel and starts receiving valid speech frames immediately. No BFIs are seen. The handover is successfully completed. The idle time between source and target channel speech frames is no longer than 100ms and quality of speech call is also good.

Lock all the TCHs in the BTS. Unlock one TCHH and one TCHF time slot in two different TRXs.

Only one FR and two HR calls can be supported.

Set up an AMR call in the BTS to an MS locked to a completely separate BTS and create continuous sound at both mobile stations. Monitor the Abis.

An AMR call is established. As the call gets continuously handed over from Full Rate TCH to Half Rate TCH and vice versa, the messages as described above are seen on the GSM Protocol Analyser.

DN0694168 Issue 2-0


Input Expected Output Unlock all TCHs. Set up a pair of AMR calls in the same BTS and observe the call quality over 50 handovers.

As the calls get continuously handed over to different TCHs in the same BTS, no clipping sound or other disturbing noise is heard.

Repeat the above steps by making sure that the codec in use during the call and the ICM are same

All signalling will be same as above except that no CMR command will be sent to TC by BTS and voice quality is good without any distortion.

Case Ref. Configuration Hopping 4 4 Omni EDGE None

25.7 Synchronous & Asynchronous Inter Cell DR TRAU Handovers

Purpose: To ensure that Synchronous Inter Cell DR TRAU handovers are successful.

Note 165.

• For ensuring FR calls in a TRX with channel type TCHD, at the BSC set the parameters FRL to 100and FRU to 0.

• For ensuring HR calls in a cell, set both FRL and FRU to 100.



• Abis monitoring tool Input Expected Output Configure the site(s) as defined in the test case.


Define each of the sectors to be a neighbour of the other.

Neighbours are defined accordingly.

Disable Intra Cell handovers using the MML command: ZEHG:SEG=<seg num>:EIC=N,EIH=N;

Intra cell Handover is disabled.

In the first sector, set threshold parameters so as to support HR calls and in the second sector, set parameters to support FR calls

The threshold parameters are successfully set.

Set up an AMR call in the first sector to an MS locked to a completely separate BTS and create continuous sound at both mobile stations.

An AMR HR call is established in the first sector.

Trigger a to and fro handover between the two sectors and monitor the Abis [Note 153]

Inter Cell DR TRAU handovers take place between the two sectors.

DN0694168 Issue 2-0


For FR – HR handovers observe the Abis for the following messages.


DN0694168 Issue 2-0


For HR – FR handovers observe the abis for the following messages.


Handovers are triggered to target cell at least 50 times during the same call [Note 153]


In the first sector, set threshold parameters so as to support FR calls and in the second sector, set parameters to support maximum HR calls Set up an AMR call in the first sector to an MS locked to a completely separate BTS and create continuous sound at both mobile stations.

An AMR FR call is established in the first sector.

Now, repeat steps 7 and 8. Identical outputs are observed.

DN0694168 Issue 2-0


Case ref. Configuration

Handover Type

Hop UL DTX

DL DTX

LA

1 6 +6 EDGE, TCHD

Synchronous

RAH + BB Off On Fast

2 4+4 EDGE, TCHD

Synchronous

BB + RF On Off Slow

3 BCF1: 6 Omni EDGE with RTC, TCHD

BCF2: 4 Omni IDD/4UD,TCHD

Asynchronous

BB + RF Off On Fast

25.8 Intra-Cell Handovers within an UltraSite Multi-BCF segment and Intra-Cell Handovers within a Chained MetroSite segment

Purpose: To ensure that DR TRAU handover are successful within the same segment: within the same BTS, from BTS to BTS.

In case of an UltraSite to ensure that DR TRAU handover are successful from one BCF to another BCF when the synchronisation is either Site or BSS synchronisation. Hardware Tools Required

• Signal Generators

• Signal Analyzers


Input Expected Output Create the sites at the BSC as shown in the table and the diagrams below.

Sites are created and in supervisory state with the mentioned TCH configuration.

DN0694168 Issue 2-0


Input Expected Output For UltraSite Define the synchronization chain in the BSC using the MML command: ZEFM:<mm>:CS=BCF,SENA=T,ADD=<s1>; <mm> = Master BCF number <s1> = Slave BCF number For BSS Sync, since LMU is master, so the above command will be modified as ZEFM:<mm>:CS=LMU,SENA=T,ADD=<s1>; <mm> = Master BCF number <s1> = Slave BCF number For MetroSite with LMU Define the synchronization chain in the BSC using the MML command: ZEFM:<BCF no>:CS=LMU,SENA=T;

Synchronisation chain is successfully defined.

Enable intra-cell handovers using the MML command: ZEHG:SEG=<seg num>:EIC=Y,EIH=Y; Set the interval between handovers to 15 seconds using the MML command: ZEHG:SEG=<seg num>:MIH=15,MIU=15; Set the interference threshold very low so that even a small interference signal triggers intra-cell handovers: ZEHI:SEG=<seg num>:IDR=-110,IUR=-110; Set the quality threshold very low so that even a small quality variance triggers intra-cell handovers: ZEHB:BTS=<bts num>:QURF=0,QDRF=0,QDRH=0,QURH=0;

All parameters are successfully set.

Lock all TCH in the whole segment. Unlock the 7th TCH timeslot in the BCCH TRX and the 7th TCH timeslot on any non-BCCH TRX in the same segment.

Traffic channels are unlocked successfully.

Set up an AMR call in the BTS to an MS locked to a completely separate BTS and create continuous sound at both mobile stations.

An AMR call is established.

Monitor the MS displays for the ARFN used Every 15 seconds the MS handover to a new ARFN within the same Segment. All ARFN within the segment are used.

Monitor the Abis. DR TRAU Handover takes place during the process. There are no noticeable clicks, silent periods or other disturbances as the handovers occur.

Repeat the test on Segment 2 The scenario for Segment 2 is same as described for Segment 1.

Case Ref. BTS1/BTS2/BTS3/BTS4 Synchronisation/ Chaining

DN0694168 Issue 2-0



1 [Figure 14]

2 Omni EDGE, TCHD(900)/


2 Omni EDGE, TCHD/(1800)/

2 Omni EDGE, TCHD(1800)

BSS

2 [Figure 15]




2 Omni EDGE, TCHD(1800)

Chaining

25.9 Inter-Cell DR TRAU Handovers between UltraSite Multi-BCF Segments and Inter-Cell handovers between Chained MetroSite segments

Purpose: To ensure that circuit switched calls successfully perform DR TRAU synchronous handovers from one segment to another within the same synchronised chain and to ensure that circuit switched call successfully perform DR TRAU asynchronous handovers to and from cells outside the synchronised chain Hardware Tools Required


• Abis monitoring tool Input Expected Output Create the sites at the BSC as shown in the table and the diagrams below.

Sites are created and in supervisory state

Create an extra multi TRX BTS 5, which will be out of the Synchronisation chain.

BTS 5 is successfully created.

Configure the BTSs with the following Channel configuration: BTS1: TCHH BTS2: TCHH BTS3: TCHF BTS4: TCHF BTS5: TCHH

BTSs are successfully configured with the mentioned TCH configuration.

DN0694168 Issue 2-0


For UltraSite Define the synchronization chain in the BSC using the MML command: ZEFM:<mm>:CS=BCF,SENA=T,ADD=<s1>; <mm> = Master BCF number <s1> = Slave BCF number For BSS Sync, since LMU is master, so the above command will be modified as ZEFM:<mm>:CS=LMU,SENA=T,ADD=<s1>; <mm> = Master BCF number <s1> = Slave BCF number For MetroSite with LMU Define the synchronization chain in the BSC using the MML command: ZEFM:<BCF no>:CS=LMU,SENA=T;

Synchronisation chain is successfully defined.

Disable intra-cell handovers using the MML command: ZEHG:SEG=<seg num>:EIC=N,EIH=N; Set the interval between handovers to 3 seconds using the MML command: ZEHG:SEG=<seg num>:MIH=3,MIU=3; Set the RX signal level threshold so that a moderate drop in signal level triggers handovers: ZEHS:SEG=<seg num>:LDR=-80,LUR=-80;

Intra-cell handover is disabled. All parameters are successfully set.

Create the Segments as neighbours in a ring as shown in 0 using MML command: ZEAC:SEG=<seg num>:INDEX=<adjacent cell index>:ASEG=<adjacent seg number>:SYNC=Y; Create BTS5 as a neighbour as shown in Figure 16 using MML command: ZEAC:BTS=<bts num>:INDEX=<adjacent cell index>:ABTS=<adjacent bts number>; Cable each segment to an MS via variable attenuators

The neighbours are successfully defined as mentioned in Figure 16

BTS5 is successfully defined as neighbour according to Figure 16.

The MS is accordingly cabled.

Lock traffic channels of all segments. In the first segment unlock the 7th timeslot of the BCCH TRX and in the 2nd segment unlock the 7th timeslot of any non-BCCH TRX.

Necessary TCH’s are unlocked successfully.

Camp one MS to one of the Segments in the ring. Do not lock the MS using the field test software because it will not be able to see the neighbour. Set up an AMR call in the BTS to an MS locked to a completely separate BTS and create continuous sound at both mobile stations. Monitor the MS displays for the ARFN being used. Monitor the Abis.

The MS is latched on the segment.


DN0694168 Issue 2-0


Slowly increase the attenuation from the serving cell until a handover is triggered. Return the attenuation to its original value after the handover has occurred.

DR TRAU Handover takes place between the different segments during the process. The ARFN shown on the MS changes to the destination cell. There are no noticeable clicks, silent periods or other disturbances as the handovers occur.

Repeat the process on each cell to hand the call around the ring [Figure 16]

All DR TRAU handovers complete successfully

Repeat the test case with the following Traffic channel configuration on BTSs. BTS1: TCHF BTS2: TCHH BTS3: TCHF BTS4: TCHH BTS5: TCHF

DR TRAU Handover takes place between the different segments during the process successfully. There are no noticeable clicks, silent periods or other disturbances as the handover occur.

Case Ref. Config. BTS1 BTS2 BTS3 BTS4 Synchronisation/ Chaining

1 [Figure 14] 2 Omni EDGE

(800)

2 Omni EDGE

(800)

2 Omni EDGE

(1900)

2 Omni EDGE

(1900)

Site Sync

2 [Figure 15]

2 Omni EDGE

(1800)

2 Omni EDGE

(1800)

2 Omni EDGE

(1800)

2 Omni EDGE

(1800)

Chaining

25.10 IntraCell DR TRAU Handover during MS in motion

Purpose: To ensure that DR TRAU Intra Cell handover is successful while the MS is in motion and the maximum speech break during the handover process is no longer than 100 ms.




• RF-TA Rig

Input Expected Output Configure site as defined in the test case.


Configure approximately half the TCHs as of type TCHF and the rest as of type TCHH in each TRX.

The TCHs are configured accordingly.

Lock all the TCHs in the BTS. Unlock one TCHH and one TCHF time slot in one of the TRXs

All TCHs are locked with one TCHH and one TCHF unlocked.

DN0694168 Issue 2-0


Enable intra-cell handovers using the MML command: ZEHG:SEG=<seg num>:EIC=Y,EIH=Y; Set the interval between handovers to 15 seconds using the MML command: ZEHG:SEG=<seg num>:MIH=15,MIU=15; Set the interference threshold very low so that even a small interference signal triggers intra-cell handovers: ZEHI:SEG=<seg num>:IDR=-110,IUR=-110; Set the quality threshold very low so that even a small quality variance triggers intra-cell handovers: ZEHB:SEG=<seg num>:QURF=0,QDRF=0,QDRH=0,QURH=0;

All parameters are successfully set.

Connect an MS to the RF TA Rig and simulate the distance and speed as mentioned in the test case. Set up an AMR call in the BTS through the RF TA Rig, to an MS locked to a completely separate BTS and create continuous sound at both mobile stations. Monitor the Abis.

An AMR call is established. Every 15 seconds the call is handed over to the unused timeslot within the same TRX. DR TRAU Handover takes place during the process. There are no noticeable clicks, silent periods or other disturbances as the handovers occur.

Lock all the TCHs in the BTS. All TCHs are locked in the BTS. Unlock one TCHH time slot in one TRX and one TCHF time slot in another TRX.

TCHs are unlocked accordingly. Only one FR and two HR calls can be supported.

Connect an MS to the RF TA Rig and simulate the distance and speed as mentioned in the test case.


DN0694168 Issue 2-0


Set up an AMR call in the BTS through the RF TA Rig, to an MS locked to a completely separate BTS and create continuous sound at both mobile stations. Monitor the Abis.


DN0694168 Issue 2-0


Every 15 seconds the call is handed over to the unused timeslot within the same sector.


When the call is on it should be noticed that there are no noticeable clicks, silent periods or other disturbances as the handovers occur.

No noticeable clicks or silent periods are observed.

Case Ref. Configuration Speed Distance Hop

1 4 Omni EDGE 40 Km/h towards BTS 30 Kms RF

DN0694168 Issue 2-0


25.11 Synchronous Inter Cell DR TRAU Handover during MS in motion

Purpose:

To ensure that synchronous DR TRAU Inter Cell handover is successful while the MS is in motion.




• RF-TA Rig

Test Steps Input Expected Output Configure the site as defined in the test and define each of the sectors to be a neighbour of the other.


Disable intra-cell handovers using the MML command: ZEHG:SEG=<seg num>:EIC=N,EIH=N;

Intra cell handovers are disabled.

In the first sector, set threshold parameters so as to support HR calls and in the second sector, set parameters to support FR calls


Connect an MS to the RF TA Rig and simulate the distance and speed as mentioned in the test case.

The distance and speed are simulated as specified.

Set up an AMR call in the first sector through the RF TA Rig, to an MS locked to a completely separate BTS and create continuous sound at both mobile stations.


Trigger a to and fro handover between the two sectors by varying the signal strength and monitor the Abis.


Handovers are triggered to target cell at least 20 times during the same call by varying the signal strength.


Case Ref. Configuration Speed Distance Hop

1 2+2 EDGE, TCHD 100 Km/h away from BTS

0 RF + BB

DN0694168 Issue 2-0


25.12 DR TRAU Handover during Intelligent Shutdown

Purpose: To ensure that the DR TRAU handover is successfully performed during Intelligent Shutdown.

Note 166.

• The Intelligent shut down feature consists of three BTS Battery Backup procedures that may be applied on mains failure, these are:

o All shutdown mode - maintain full service,

o BCCH shutdown mode - maintain the BCCH TRXs, or

o None shutdown mode - maintain only the transmission equipment

• It is possible to Activate Intelligent Shutdown with Timer Control with the MML command ‘ZEFM’:

‘ZEFM:<bcf_id>:BBU=NONE,NTIM=<NTIM_timer>,NTIM2=<NTIM_timer2>,NTIM3=<NTIM_timer3>,BTIM=<BTIM_timer>;’.

Where:

NTIM : With this parameter you define the time period after which shutdown group 1 TRXs are powered down. The time begins after the TRX Shutdown Timer 2 has expired. Parameter is valid if BTS Battery Backup Procedure parameter has value "Transmission and BCCH Alive (1)" or "Transmission Alive (2)".

NTIM2 : With this parameter you define the time period after which shutdown group 2 TRXs are powered down. The time begins after the TRX Shutdown Timer 3 has expired. Parameter is valid only when BTS Battery Backup Procedure parameter has value "Transmission and BCCH Alive (1)" or "Transmission Alive (2)".

NTIM3 : With this parameter you define the time period after which shutdown group 3 TRXs are powered down. Parameter is valid only when BTS Battery Backup Procedure parameter has value "Transmission and BCCH Alive (1)" or "Transmission Alive (2)".

BTIM : With this parameter you define the time period after which shutdown group 0 TRXs are powered down. The time begins after the TRX Shutdown Timer1 has expired. Parameter is valid if BTS Battery Backup Procedure parameter has value “Transmission and BCCH Alive (1)” or “Transmission Alive (2)”. Also BCCH TRXs are powered down when battery backup procedure parameter has value “Transmission Alive (2)”.

DN0694168 Issue 2-0


• The testing shall be completed using an external BBU (EAC inputs) unless

otherwise stated. The EAC input should be set as detailed below using MML command ZEFX. For the MetroSite predefined external input for the Mains fail is EAC 01.

ZEFX:<bcf_id>:INBR=1:ROU=MAINS:POL=<OPEN - active or CLOSED - inactive>,SEV=AL3;

• For Intelligent Shutdown test case neighbour BTS is defined to handle the calls once handed over by the BSC unless otherwise stated.




• EAC Box

•

Input Expected Output Configure the site as defined in the test case The site is in supervisory state. Configure all the traffic channels of BTS1 to be of type TCHH.

Channels are configured to be of type TCHH.

Define a valid neighbour BTS that supports DR TRAU handover. The signal level of neighbour BTS is attenuated such that it is lower than that of main BTS Configure all the traffic channels of the neighbour to be of type TCHF.

The neighbour BTS is in supervisory.

For Shutdown Mode the service level is set at the BSC by using the MML command ‘ZEFM:<bcf_id>:BBU=<shutdown mode>,NTIM=<>,BTIM=<>;

The shutdown mode is configured for the BCF.

Lock all the traffic channels except one, in each of the BTSs on a non BCCH TRX

Only one timeslot remains unlocked in each BTS.

Set up an AMR call in BTS1 to an MS locked to a completely separate BTS and create continuous sound at both mobile stations..


DN0694168 Issue 2-0


The mains breakdown alarm is generated at BTS1. Monitor the Abis.

Alarm ‘7995:MAINS BREAKDOWN WITH BATTERY BACK-UP’ is reported at the BSC and BTS Manager. The BSC starts the NTIM timer. On the expiry of NTIM timer The call is handed over from the non-BCCH TRXs to the neighbour BTS DR TRAU Handover takes place during the process. There are no noticeable clicks, silent periods or other disturbances as the handovers occur When the Hand-off timer started by the BSC expires or all the calls are handed off then the BSC sends the BTS_PWR_SUPPLY_CONTROL (switch off each non BCCH TRX) message to the BCF. The BTIM timer is started

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

At the BSC the non-BCCH units are in ‘BL-PWR’ and at the BTS Manager the non-BCCH units are shown to be in shutdown state. At the BSC the BCCH units are in ‘WO’ and at the BTS Manager the BCCH units are shown to be in supervisory state. The set time for the BTIM expires, BSC starts hand-off timer After the expiry of Hand-Off timer BTS_PWR_SUPPLY_CONTROL (switch off each TRX) message is sent to the BCF from BSC for each BTS.


All fans associated to the TSxx’s are shutdown At the BSC all units are in ‘BL-PWR’ and at the BTS Manager all TRXs are shown to be in shutdown state.

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

The ‘7995:MAINS BREAKDOWN WITH BATTERY BACK-UP’ is cancelled at the BSC and BTS Manager. The BSC sends BTS_PWR_SUPPLY_CONTROL (switch on all TRXs) message to the BCF.

All the TRXs, and associated fans are restarted.

The call on neighbouring BTS is handed over to BTS1 as soon as the TRXs of BTS1 are operational. DR TRAU Handover takes place during the process.

There are no noticeable clicks, silent periods or other disturbances as the handovers occur


At the BSC all units are in ‘WO’ and at the BTS Manager all units are shown as in SUPERVISORY (objects/properties).

DN0694168 Issue 2-0


Configure all the traffic channels of BTS1 to be of type TCHF and that of BCCH TRX as TCHH Repeat the above steps again for this changed configuration.

The test case is executed successfully according to the above-mentioned scenario.

Case Ref. Configuration Hopping Shut Down Mode

1 4 Omni EDGE RF None

2 4 Omni EDGE BB None

25.13 DR TRAU HO and Cell Reselection between E- and N-Areas of the same BTS

Purpose: To ensure that DR TRAU handovers of AMR calls and cell reselection of packet switched data calls are successful between E and N areas of the same BTS( refer Generic Notes of section 25).




• RF TA Rig

Input Expected Output Configure the site as defined in the test case. Sites are in supervisory state. Set the radius extension to 30 km. Extended radius is set to 30 km. Set GENA=Y and EGENA=Y. Set the GTRX parameter of the BCCH TRX and ERACH ETRX to be Y. Set GTRX=N for the rest of the TRXs. Set CDED=1.

The parameters are set as stated.

Define the TCHs of the non BCCH TRX to be of type TCHH.

TCHs are set as defined.

Lock all TCHs of the BCCH TRX except the GPRS timeslot.

Only the GPRS and signalling timeslots remain unlocked on the BCCH TRX.

Connect 2 MSs to the RF TA rig, so that they are in the N area. With one MS make an AMR call to an MS latched to a completely different BTS.

An HR AMR call is established in the N Area.

Start a packet data transfer with the second MS. The transfer can be established on the E-Cell and data transfer begins successfully

Move the MSs from the N area to the E-Area, using the RF TA Rig, at a speed of 100 Kmph. Ensure that the data transfer continues during the transition from N Area to the E-Area by downloading or uploading a large data file.

As the distance of the MS changes, data call performs a cell reselection into the E-Area and the voice call performs a DR TRAU intra cell handover into the E-Area. Data Transfer continues successfully in the E-Area. As the voice call gets handed over to the E-Area, neither clipping sound nor any other disturbing noise is heard. The voice call is sustained.

DN0694168 Issue 2-0


Input Expected Output If the data transfer is complete, another data transfer is initiated. Move the MSs from the E-Area to the N area, using the RF TA Rig, at a speed of 100 Kmph. Ensure that the data transfer continues during the transition from E-Area to the N Area by downloading or uploading a large data file.

As the distance of the MS changes, data call performs a cell reselection into the N Area and the voice call performs a DR TRAU intra cell handover into the N Area. Data Transfer continues successfully in the N Area. As the voice call gets handed over to the N Area, neither clipping sound nor any other disturbing noise is heard.


1 Standard E-Cell Configuration

25.14 DR TRAU Handover with DFCA

Purpose: To ensure that DR TRAU handovers are successful in BTSs configured with DFCA.

Note 167.

• In case of synchronous handover test cases, BTS 1 and BTS 2 refer to the two sectors.

• In case of asynchronous handover test cases, BTS 1 refers to the DFCA site and BTS 2 refers to the non DFCA site. Both sites have identical hardware configuration.




Input Expected Output Configure the site as defined in the test case with DFCA


Define the channels to be of type TCHD. TCHs are configured to be of type TCHD. Neighbour definition is by adjacency and BA list for all cases.

Neighbour definition is successful.

In BTS 1, set threshold parameters so as to support HR calls and in BTS 2, set parameters to support FR calls.


Set up an AMR calls in BTS 1 to an MS locked to a completely separate BTS and create continuous sound at both mobile stations.

An AMR HR call is established in BTS 1.

DN0694168 Issue 2-0


Trigger a to and fro handover between BTS 1 and BTS 2. Monitor the Abis

Inter Cell DR TRAU handovers take place between the two BTSs.

During the handovers speech quality at both ends of the calls are observed for unexpected audio disturbances.

The perceived speech is unaffected by the handover procedure and there are no additional audio signals like clicks are noticed.

Handovers are triggered to target cell at least 50 times during the same call

Handovers take place continuously between the two BTSs and neither clipping sound nor any other disturbing noise is heard during this period.

For Asynchronous test case do the following: In BTS 1, set threshold parameters so as to support FR calls and in the BTS 2, set threshold parameters to support HR calls

An AMR FR call is established in BTS 1.

Now, repeat steps 4, 5 and 6. Identical outputs are observed.

Case Ref. Configuration Handover Type

1 4 Omni EDGE Asynchronous

2 4 Omni EDGE Synchronous

25.15 DR TRAU Handover with Packet Data calls ongoing

Purpose: To ensure that DR TRAU handovers are successful and that cell reselection of a packet switched data call is successful, when both packet switched data call and circuit switched voice call are ongoing.




Input Expected Output Configure the site as defined in the test case. Define each of the sectors to be a neighbour of the other.


Set GENA=Y and EGENA=Y for both sectors. GENA and EGENA are set accordingly. In the first sector, set threshold parameters so as to support HR calls and in the second sector, set parameters to support FR calls.




Start a packet switched data call in the first sector as stated in the test case.

Data transfer begins successfully.

DN0694168 Issue 2-0


Trigger a to and fro handover of the voice call and a to and fro cell reselection of the packet switched data call, between the two sectors. Monitor the Abis

Inter Cell DR TRAU handovers of the voice call takes place between the two sectors. Data transfer continues in the target cell after cell reselection.

During the handovers speech quality at both ends of the calls are observed for unexpected audio disturbances.

The perceived speech is unaffected by the handover procedure and there are no additional audio signals like clicks are noticed.

Case Ref. Configuration Data Transfer

1 2+2 EDGE, TCHD GPRS

25.16 DR TRAU Handover under Bad RF conditions

Purpose: To ensure that DR TRAU handovers are successful when the ICM of the target BTS is a less robust codec than the codec currently in use at the source BTS due to bad RF conditions of the downlink.

Note 168.

• Interference should be added at Source BTS and depending upon interference conditions Mode Modify Ack and Nack can be seen on A-Bis in FR to HR handovers.

• When the most robust codec is in use, the call may get dropped during FR to HR handover because of the interference being added




• Signal Generator

Input Expected Output Configure a 2+2 EDGE site as defined in the test. Define each of the sectors to be a neighbour of the other.


In the first sector, configure all the traffic channels to be of type TCHH and in the second sector, configure all the traffic channels to be of type TCHF.


Disable intra-cell handovers using the MML command: ZEHG:SEG=<seg num>:EIC=N,EIH=N;

Intra cell handovers are disabled.



DN0694168 Issue 2-0


Use a signal generator to introduce interference in the downlink till the codec in use is the most robust codec.

Call continues on the most robust codec.

Trigger a to and fro handover between the two sectors and monitor the Abis


Handovers are triggered to target cell at least 50 times during the same call


Case Ref. ICM1 ACS of BTS1 ICM2 ACS of BTS2

1 5.90 4.75, 5.15, 5.90, 6.70 6.70 4.75, 5.90, 6.70, 12.2

2 6.70 4.75, 5.15, 5.90, 6.70 5.90 4.75, 5.90, 6.70, 12.2 25.17 Continuous Synchronous Inter Cell DR TRAU Handovers

Purpose: To ensure that continuous DR TRAU handovers are successful over a long period of time.




Input Expected Output Configure a 2+2 EDGE site as defined in the test case. Define each of the sectors to be a neighbour of the other.


Disable Intra Cell handovers using the MML command: ZEHG:SEG=<seg num>:EIC=N,EIH=N;

Intra Cell handovers are disabled.

In the first sector BTS 1, set threshold parameters so as to support HR calls and in the second sector BTS 2, set parameters to support FR calls




Trigger a to and fro handover between the two sectors and monitor the Abis


Handovers are triggered to target cell continuously for an hour. After the completion of an hour, analyse the call and monitor the Abis.

The call is active. Inter Cell DR TRAU handovers take place between the two sectors and neither clipping sound nor any other disturbing noise is heard during this period.

Case Ref. TCH TYpe ACS of BTS 1 ICM1 ACS of BTS 2 ICM2

1 TCHD 4.75, 5.15, 5.90, 6.70

4.75 4.75, 5.15, 10.20, 12.2 5.15

DN0694168 Issue 2-0


25.18 Synchronous Inter Cell DR TRAU Handover with FACCH Repetition

Purpose: To ensure that when FACCH repetition is in effect, the Synchronous Inter Cell DR TRAU Handover is successful.

Note 169.

Basic AMR set for FR channel on BSC

Codec Mode

Threshold (C/I)

Hysteresis (C/I)

Lower threshold (C/I)

Upper threshold (C/I)

BER (%) FER (%)

12.2 11 1 11 - 2.97 0.08

7.4 7 1 7 12 6.72 0.15

5.9 4 1 4 8 10.83 0.98

4.75 - 5

Note 170. Basic AMR set for HR channel on BSC

Codec Mode

Threshold (C/I)

Hysteresis (C/I)



BER (%) FER (%)

7.4 14 1 14 - 0.62

5.9 11 1 11 15 1.08

4.75 - 12

• Lower threshold in the tables above means towards more robust Codec (more correction, lower bit rate) and upper threshold means less robust Codec (less correction, higher bit rate).

• Initial Codec mode is used to start the speech coding at call Setup and after handover. If the Initial Codec mode is not defined, it is governed by the following rule:




DN0694168 Issue 2-0


• Whenever ‘FACCH Repeat’ is enabled in the ‘Channel Activation’ message, the BTS LAPDm T200 timer gets modified as-

MAX(T200_default, 200ms) for AMR/FR

MAX(T200_default, 240ms) for AMR/HR

Where T200_default is the T200 timer value that would apply in the absence of Repeated Downlink FACCH according to the configuration mechanisms currently in use.

• A repeated FACCH block are sent in such a way that, if the first burst of the

downlink FACCH block containing the first instance of a LAPDm frame is sent in TDMA frame M, the first burst of the downlink FACCH block containing the repeated instance of the LAPDm frame is sent in TDMA frame M+8 or M+9 (the latter corresponding to the case where the two FACCH blocks are separated by either a SACCH frame or an idle frame).




• Air Interface Monitoring Tool

• Signal Generator

Input Expected Output Create sites with configurations as mentioned in the test case.

Sites are in supervisory state.

Configure the TCHs in first sector as TCHH and in second sector as TCHF.

Channels are configured accordingly.

Define the two sectors as neighbour of each other using the MML command: EAC:BTS=<bts num>::ABTS=<bts num>::SYNC=Y,;

Neighbour is defined.

Disable intra-cell handovers in both the sectors using the MML command: ZEHG:BTS=<bts num>:EIC=N,EIH=N;

Intra-cell handovers are disabled.

Define ARLT=64 in both the sectors using the MML command: EQY:BTS=<bts num>:ARLT=64;

ARLT=64 is set.

Set up an AMR call in the second sector to an MS locked to a completely separate BTS.

An AMR full rate call is successfully established in the second sector. ‘FACCH Repeat’ is enabled in the ‘ACCH control IE’ of the Channel Activation message.

DN0694168 Issue 2-0


Input Expected Output Trigger Inter Cell handover from sector 2 to sector1 by manipulating the signal level of both the sectors using variable attenuator. Monitor the Abis and Air i/f for FACCH messages

Inter Cell DR TRAU handover takes place. The source BTS receives a Mode Modify message from BSC containing ICM of target BTS, with 8 Kbit/s TRAU & FICM bits enabled. The source BTS, sends a CMR to TC to step the codec to ICM of target BTS and CMC to MS to change the codec mode to the first codec mode which is compatible with the 8Kbit/s DR TRAU format and which is a part of the ACS of source BTS. As soon as a CMI of 8Kbit/s compatible mode is received by the source BTS from MS, it sends a CMR to transcoder in the 8Kbit/s frame format on the 16Kbit/s Abis sub channel indicating ICM of target BTS. Upon receiving this message, TC sends a CMI in the 8Kbit/s frame format on the 16Kbit/s Abis sub channel indicating ICM of target BTS. Now the source BTS sends an ACK in response to the Mode Modify message. The BSC activates a HR channel at the target BTS. On receiving Channel Activation ACK message, the BSC duplicates TRAU data received from the A-ter interface both towards the source and target BTS. BSC sends HANDOVER COMMAND to the source BTS as seen on Abis. BTS sends this HANDOVER COMMAND encapsulated in DL I-frame on FACCH Since FACCH repetition is activated the transmissions of DL I-frame (carrying HANDOVER COMMAND) get repeated on Air i/f, as the CMR is 4.75, and is the most robust codec (CODEC_MODE_1) of the ACS [6]. The call is handed over to the HR channel, a HANDOVER COMPLETE message is sent to the BSC. Handover is successfully completed.

Call is disconnected. Call is successfully disconnected

ICM Case Ref Configuration ACS of BTS 1 ACS of BTS2

BTS1 BTS2

1 2+2 EDGE 4.75, 5.15, 5.90, 6.70

4.75, 7.40, 10.2, 12.2

4.75 4.75

DN0694168 Issue 2-0


25.19 Asynchronous Inter Cell DR TRAU Handover during MS in motion

Purpose: To ensure that asynchronous DR TRAU handover is successful while the MS is in motion.

Note 171.

• RF TA rig is setup of equipments (fading simulator and signal generator etc) that allow signal delay on the air interface so that distance can be simulated to adjust TA.




• RF-TA Rig

Input Expected Output Configure the sites as defined in the test case.

Both sites are in supervisory state.

Define the ARFNs of both sites to be such that, TA can be simulated using the same RF TA Rig. Define each of the sites to be a neighbour of the other.

ARFNs are defined as required. Neighbour definition is successful.

In the first site, set threshold parameters so as to support HR calls and in the second site, set parameters to support FR calls


Connect the two sites to a single RF TA Rig using RF cables and variable attenuators. Connect an MS to the RF TA Rig and simulate the distance and speed as mentioned in the test case.

Both the sites are connected to the same RF TA Rig. The distance and speed are simulated as instructed.

Set up an AMR call in the first site through the RF TA Rig, to an MS locked to a completely separate BTS and create continuous sound at both mobile stations. This can be done by attenuating the signal of the second site.

An AMR HR call is established in the first site.

Trigger a to and fro handover between the two sectors by varying the signal strength and monitor the Abis.

Asynchronous DR TRAU handovers take place between the two sites.

Handovers are triggered to the target cell at least 20 times during the same call by varying the signal strength.

Handovers take place continuously between the two sites and neither clipping sound nor any other disturbing noise is heard during this period.

Hop Case Ref. BTS 1/BTS 2 Speed Distance

BTS 1 BTS 2

1 4 Omni EDGE, TCHD/

4 Omni EDGE

100 Km/h to and from BTS

5 Kms BB RF

DN0694168 Issue 2-0


25.20 DR TRAU with ICE+ Configuration

Purpose: To ensure that DR TRAU handover takes place in a BTS configured with ICE+ when calls are shifted between the normal coverage and enhanced coverage areas.

Note 172.

• In case of MetroSite, for creating normal coverage TRXs the attenuation used should be at least 3dB more than that of enhanced coverage TRXs.

• The BCCH must be configured in one of the coverage area TRXs, “preferred BCCH TRX“ feature can be used to ensure this.





Configure the site as described in the test case. Site is in supervisory state.

In the coverage area TRXs, configure all the traffic channels to be of type TCHH and in the capacity area TRXs, configure all the traffic channels to be of type TCHF.

Channel types are configured as specified.

Lock all the traffic channels except one, in each of the coverage and capacity areas.

The coverage area can only support two half rate calls. The capacity area can only support a single full rate call.

Set up an AMR call in the BTS to an MS locked to a completely separate BTS. The call is triggered to handover between coverage and capacity areas by varying signal strength. Monitor the Abis

The call is handed over between the coverage and capacity areas without any problems. Intra Cell DR TRAU handovers take place.


1 MetroSite

4 Omni EDGE (2 Normal, 2 Enhanced)

DN0694168 Issue 2-0


25.21 Continuous Asynchronous Inter Cell DR TRAU Handovers

Purpose: To ensure that continuous DR TRAU handovers are successful over a long period of time.




Input Expected Output Configure two 4 Omni EDGE sites as defined in the test case. Define each site to be a neighbour of the other.


Disable IntracCell handovers using the MML command: ZEHG:SEG=<seg num>:EIC=N,EIH=N;

Intra Cell handovers are disabled

In the first site BTS 1, set threshold parameters so as to support HR calls and in the second site BTS 2, set parameters to support FR calls


Set up an AMR call in the first site to an MS locked to a completely separate BTS and create continuous sound at both mobile stations.

An AMR HR call is established in the first site.

Trigger a to and fro handover between the two sites and monitor the Abis

Inter Cell DR TRAU handovers take place between the two sites.

Handovers are triggered to target cell continuously for an hour. After the completion of an hour, analyze the call and monitor the Abis.

The call is active. Inter Cell DR TRAU handovers take place between the two sites and neither clipping sound nor any other disturbing noise is heard during this period.

Case Ref. TCH Type ACS of BTS 1 ICM ACS of BTS 2 ICM

1 TCHD 4.75, 5.15, 5.90, 6.70 4.75 4.75, 5.15, 10.20, 12.2 5.15

25.22 Asynchronous Inter Cell DR TRAU Handover with FACCH Repetition

Purpose: To ensure that when FACCH repetition is in effect, the Asynchronous Inter Cell DR TRAU Handover is successful.

Note 173. Basic AMR set for FR channel on BSC

DN0694168 Issue 2-0


Codec Mode

Threshold (C/I)

Hysteresis (C/I)



BER (%) FER (%)

12.2 11 1 11 - 2.97 0.08

7.4 7 1 7 12 6.72 0.15

5.9 4 1 4 8 10.83 0.98

4.75 - 5


Codec Mode

Threshold (C/I)

Hysteresis (C/I)



BER (%) FER (%)

7.4 14 1 14 - 0.62

5.9 11 1 11 15 1.08

4.75 - 12

• Lower threshold in the tables above means towards more robust Codec (more correction, lower bit rate) and upper threshold means less robust Codec (less correction, higher bit rate).

• Initial Codec mode is used to start the speech coding at call Setup and after handover. If the Initial Codec mode is not defined, it is governed by the following rule:




• Whenever ‘FACCH Repeat’ is enabled in the ‘Channel Activation’ message, the BTS LAPDm T200 timer gets modified as-




• A repeated FACCH block are sent in such a way that, if the first burst of the

downlink FACCH block containing the first instance of a LAPDm frame is sent in

DN0694168 Issue 2-0


TDMA frame M, the first burst of the downlink FACCH block containing the repeated instance of the LAPDm frame is sent in TDMA frame M+8 or M+9 (the latter corresponding to the case where the two FACCH blocks are separated by either a SACCH frame or an idle frame).




• Air Interface Monitoring Tool

• Signal Generator Test Steps Input Expected Output Create sites with configurations as mentioned in the test case.


Configure the TCHs in BTS1 as TCHH and in BTS2 as TCHF.

Channels are configured accordingly

Define the two BTS as neighbour of each other using the MML command: EAC:BTS=<bts num>::ABTS=<bts num>;


Disable intra-cell handovers in both the BTSs using the MML command: ZEHG:BTS=<bts num>:EIC=N,EIH=N;

Intra-cell handover is disabled in both the BTSs.

Define ARLT=64 in both the BTSs using the MML command: EQY:BTS=<bts num>:ARLT=64;

ARLT=64 is set in both the BTSs.

Set up an AMR call in the BTS2 to an MS locked to a completely separate BTS.

An AMR full rate call is successfully established in the BTS2 [7]. ‘FACCH Repeat’ is enabled in the ‘ACCH control IE’ of the Channel Activation message.

DN0694168 Issue 2-0


Input Expected Output Trigger Inter cell handover from BTS2 to BTS1 by manipulating the signal level of both the BTS using variable attenuator. Monitor the Abis and Air i/f for FACCH messages

Inter cell DR TRAU handover takes place. The source BTS receives a Mode Modify message from BSC containing ICM of target BTS, with 8 Kbit/s TRAU & FICM bits enabled. The source BTS, sends a CMR to TC to step the codec to ICM of target BTS and CMC to MS to change the codec mode to the first codec mode which is compatible with the 8Kbit/s DR TRAU format and which is a part of the ACS of source BTS. As soon as a CMI of 8Kbit/s compatible mode is received by the source BTS from MS, it sends a CMR to transcoder in the 8Kbit/s frame format on the 16Kbit/s Abis sub channel indicating ICM of target BTS. Upon receiving this message, TC sends a CMI in the 8Kbit/s frame format on the 16Kbit/s Abis sub channel indicating ICM of target BTS. Now the source BTS sends an ACK in response to the Mode Modify message. The BSC activates a HR channel at the target BTS. On receiving Channel Activation ACK message, the BSC duplicates TRAU data received from the A-ter interface both towards the source and target BTS. BSC sends HANDOVER COMMAND to the source BTS as seen on Abis. BTS sends this HANDOVER COMMAND encapsulated in DL I-frame on FACCH Since FACCH repetition is activated the transmissions of DL I-frame (carrying HANDOVER COMMAND) get repeated on Air i/f, as the CMR is 4.75, and are the most robust codec (CODEC_MODE_1) of the ACS [6]. The call is handed over to the HR channel, a HANDOVER COMPLETE message is sent to the BSC. Handover is successfully completed.

ICM Case Ref BTS1/

BTS2

ACS of BTS 1 ACS of BTS2

BTS1 BTS2

1 4 Omni EDGE/

4 Omni EDGE

4.75, 5.15, 5.90, 6.70

4.75, 7.40, 10.2, 12.2

4.75 4.75

DN0694168 Issue 2-0


LMU –ULTRA-ULTRA Chained Multi-BCF

1

Segment1 BTS3

Segment 2

BTS2

TRX colour indicates the segment, which it belongs to.

B= BCCH

Figure 14

LMU Master

BTS1

BTS2

3 B

BTS3

BTS4

2

1 B

4

1

2

3

4

DN0694168 Issue 2-0


Metro-Metro Chained

1

Segment1 BTS3

Segment 2

BTS2


B= BCCH

Figure 15

BTS1

BTS2

BTS3

BTS4

1B 2

3B 4

1 2

3 4

DN0694168 Issue 2-0


Ring of Adjacent Cells/Segments

Figure 16

SEGMENT 1

BTS1

BTS3

SEGMENT 2

BTS2

BTS4

BTS 5

Extra BTS, separate from synchronised chain. Neighbour of Segment 1.

Neighbour of Segment 2

Neighbour of BTS 5

DN0694168 Issue 2-0


LMU –Metro-Metro Chained

1

Segment1 BTS3

Segment 2

BTS2


B= BCCH

Figure 17

26. EGPRS IN EXTENDED TRXS

General Notes for Testing

Note 175. The TA value for the E-Area can be calculated by subtracting the Extension Radius from the Distance between BTS and MS. Then dividing the result by 0.553 and rounding up to nearest integer and TA value for N-Area can be simply calculated by dividing the distance between MS and BTS by 0.553.

Note 176.

BTS1

BTS2

BTS3

BTS4

1B 2

3B 4

1 2

3 4

LMU Master

DN0694168 Issue 2-0


GPRS and EGPRS throughput should lie between 85% and 100% of the maximum theoretical value. Convert from KByte/s to Kbit/s by multiplying by 8.47.

GPRS

CS scheme Data rate CS1 9.05 CS2 13.4 CS3 15.6 CS4 21.4

EGPRS

MCS scheme Data rate MCS1 8.5 Kbps MCS2 10.7 Kbps MCS3 14.3 Kbps MCS4 16.6 Kbps MCS5 21.7 Kbps MCS6 27.6 Kbps MCS7 43.4 Kbps MCS8 50.3 Kbps MCS9 54.7 Kbps

Note 177. RF TA rig is setup of equipments (fading simulator and signal generator etc) that allow signal delay on the air interface so that distance can be simulated to adjust TA, for TA simulation.

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

This is done using the MML command:

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

Note 179. In Acknowledged RLC Mode, the receiver acknowledges the data sent. If data is not correctly received the data is retransmitted. In this mode Incremental Redundancy is automatically enabled.

DN0694168 Issue 2-0


Table 16

Initial transmission,

prior to transition

MCS transition Retransmission After transition


Air Interface conditions improving MCS 1 MCS 1 → 2 MCS 1 MCS 2 MCS 2 → 3 MCS 2 MCS 3 MCS 3 → 4 MCS 3 MCS 4 MCS 4 → 5 MCS 4 MCS 5 MCS 5 → 6 MCS 5 MCS 6 MCS 6 → 7 MCS 6 MCS 7 MCS 7 → 8 MCS 7 MCS 8 MCS 8 → 9 MCS 8

On the A-bis this is part of the PCU data block within the PCU MASTER DATA FRAME.

Table 17

Coding Scheme


MCS 1 0 MCS 2 1 MCS 3 1 MCS 4 1 MCS 5 1 MCS 6 2 MCS 7 3 MCS 8 4 MCS 9 4

Note 180. The Reliability Class set within the subscriber information determines the mode (RLC Ack or RLC Unack mode) used for a given MS. The Reliability Class is one of the Quality of Service (QoS) parameters that exist for each subscriber in the HLR.

DN0694168 Issue 2-0


Note 181. The network shall increment counter N3101 for each radio block allocated to the TBF for which no RLC/MAC block is received. Whenever the network receives an RLC/MAC block from the mobile station, it shall reset counter N3101 for that TBF. If N3101 reaches the value N3101max, the network shall stop sending PACKET UPLINK ACK/NACK messages to the mobile station for that TBF and shall start timer T3169 for the TBF. If an RLC/MAC block is received from the TBF when timer T3169 is running, the network shall stop timer T3169 and resume sending PACKET UPLINK ACK/NACK messages to the TBF. When T3169 expires, the network may consider the TBF as released and reuse the TFI value

Note 182. In the uplink direction, the coding scheme used can be found in the uplink MCS indicator in the PCU Master Data Frame. In the downlink direction, the coding scheme to be used can be found in the downlink idle/header type.

Note 183. In GPRS Link adaptation different threshold are also set for optimised performance of Link adaptation mechanism:

DLA and ULA: Allowed probability (%) for the system to make a wrong decision in downlink (DLA) and uplink (ULA) adaptation is defined by these parameters.

DLB and ULB: With these parameters the RLC BLER (block error rate percentage) for CS-1 channel coding is defined. At this point CS-1 and CS-2 give the same effective bit rate and Coding Scheme selection criteria in RLC Acknowledged mode for downlink (DLB) and uplink (ULB) TBFs changes. These parameters are meaningful only if Link Adaptation is used in case of no frequency hopping.

Note 184. Timeslot 7 must always be left unlocked for synchronisation purposes. (E) GPRS transfers are loaded from timeslot 7 forward. In order to test other timeslots it is necessary to first occupy timeslot 7 with another transfer, and then begin the transfer under test. Configure EGTCH from timeslot 7 to the timeslot to be tested in test case. Lock up all timeslots except timeslot 7 and the timeslot under test. To test timeslot 6 in the downlink, it is acceptable to have a downlink transfer on two timeslots, one of which is timeslot 6.

Note 185. In Unacknowledged RLC Mode the data is not acknowledged. Incremental Redundancy does not take place. The system relies upon error correction using the redundancy incorporated in the coding scheme. Any data blocks that are not successfully error corrected remain corrupt.

DN0694168 Issue 2-0


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

Note 187. ST-IRC can be enabled at any time without locking/unlocking of the TRX/sector/site; this indicates that BTS_CONF_DATA containing the info field about ST-IRC enable/disable can be sent at anytime when BTS is running.

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

Note 189. There are three possible shutdown modes (BTS battery backup procedure):

NONE: where the non-BCCH TRXs are powered down after timer NTIM expires and the BCCH-TRX is powered down after timer BTIM expires. This means that the E-Area is lost after timer NTIM expires.

BCCH: where the non-BCCH TRXs are powered down after timer NTIM expires, while the BCCH-TRX remains working until the batteries are exhausted.

ALL: where the whole site remains working until the batteries are exhausted.

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

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

Where:

NTIM is Non BCCH TRX shutdown timer and BTIM is BCCH TRX shutdown timer.

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

When Intelligent Shutdown is used on a cell configured with E-Cell, the alarm 7749 E-RACH MISSING alarm will be raised when the E-TRXs are shut down.

For each TRX there will be a 7705 LAPD FAILURE alarm raised when the TRXs are shut down.

DN0694168 Issue 2-0


Note 190. Acceptable test results are: BER<0.1%, FER<0.1%

Note 191. Before starting the test case, check that Alarm 7601:BCF OPERATION DEGRADED: "Difference between PCM and base station frequency reference" should not be present. Leave the site idle for 12 hrs and verify that above alarm is not present.

Note 192. To Enable GPRS/ EGPRS in a Normal Sector (N- area):

ZEQV:BTS=<#>:GENA=Y,RAC=<RA_Number>,EGENA=Y,;

To Enable GPRS/ EGPRS in a E-cell (E-Area)

ZEQV:BTS=<#>:GENA=Y,RAC=<RA_Number>,EGENA=Y,EXGENA=Y;

26.1 GPRS Data transfer with changing timing advance in E-Cell

Purpose: To check that data transfer does not fail when the MS distance varies over a wide range of E-Cell and random access bursts are successfully received over the full range of timing advance values.


BTS with given configuration, RF TA rig

Input Expected Output Set up a site of standard E-Cell configuration. Set radius extension to 29 km.


Set the RF TA rig and simulate the distance specified in the test case [Note 177]

Specified distance can be simulated.

Connect MS to the RF TA rig, so that MS is in the area specified in the test case. Attempt a circuit switched call from MS to see the TA value on net monitor screen. For calculating TA see [Note 175]

On Net Monitor screen 01-01, check that the correct TA value is displayed for MS.

Start packet data transfer in the timeslot with coding scheme and direction as specified in the case. The user data rate is monitored. As the transfer of one file completes, promptly begin the transfer of a new file. Repeat this process until the MS reaches the distance specified in the test case.

The data is transferred with BER of 0%. The reliable data rates for the coding scheme are achieved [Note 176]. Correct TA value is shown in PCU RANDOM ACCESS FRAME, IMMEDIATE ASSIGNMENT COMMAND and Master data frame (UL).

DN0694168 Issue 2-0


Input Expected Output Repeat the data transfer for three times to get the reliable throughput.

Reliable throughput is achieved [Note 176]

Case Ref.

BCCH Configuration

CS34 Coding Scheme

Starting Distance. /Speed

Travel Ending distance


Configuration

01 MBCCHC

Disabled

CS-1 56 km / 100 km/hr

Towards BTS

18 km Uplink and Downlink 1Mb file

4 OMNI Standard E-cell

02 Any Enabled

CS3 62Km/ 100 km/hr

Towards BTS

12 Km Uplink 2 OMNI E-cell (1 N-TRX and 1 E-TRX)

26.2 EGPRS MCS1 to MCS9 and IR in E-Area

Purpose: To ensure that all EGPRS coding schemes MCS1 to MCS9 with IR are supported in E-Area

Equipment and BTS Set-Up BTS with standard E-Cell configuration, RF TA rig, signal generator, spectrum

analyser

Input Expected Output Set up a site as per the test configuration. Set radius extension to 29 km.


Set the RF TA rig and simulate the distance of 40 km [Note 177]

Distance of 40 km is simulated.

Connect 2MSs to the RF TA rig, so that MSs are in the E-Area. Attempt a circuit switched speech call to see the value of TA on net monitor screen.

On Net Monitor screen 01-01; check that the correct TA value is displayed for MSs. At a distance of 40 km, MS displays=22, values between 20 and 24 are acceptable.

Disable link adaptation: ZEQV: BTS=##: ELA=0; Set initial coding scheme as defined in the test case: ZEQV: BTS=##: MCEA=#, MCEU=#;

Link adaptation is disabled. Initial coding scheme is set

Set C/I = >30dB in the direction specified for data transfer.

C/I is set.

DN0694168 Issue 2-0


Input Expected Output Lock the timeslots to force transfer on timeslot Under test as shown in the table. Set-up EGPRS data transfer of file as specified in the test case in specified direction using TCP/IP.

File transfer begins. PCU MASTER DATA FRAME shows data is sent using correct MCS. No retransmissions are seen. Reliable data rate is achieved for the MCS being used [Note 176]

Change C/I gradually to the value as specified in test case. Monitor A-bis for PCU fames

Retransmissions are observed on MCS 4 to 9. Data rate for the coding schemes are achieved as specified in test case.

Repeat data transfer for three times to get the reliable throughput.

Reliable throughput is achieved.

Data Rate for C/I Case Ref. MCS Direction of data transfer

File Size

Timeslot Data

rate C/I

01 4 UL 512 Kb

3 9.1 Kbps

5 dB

02 5 DL 500 Kb

4 10.2 Kbps

5 dB

26.3 EGPRS Link Adaptation and IR in E-Area

Purpose:

To check that in E-Area with Acknowledged RLC Mode, Link Adaptation occurs in accordance with changes in radio condition and Dynamic A-bis can allocate the correct number of slave frames for the MCS being used.

Equipment and BTS Set-Up BTS with given configuration, RF TA rig, spectrum analyser, signal generator

Input Expected Output Set up a site of standard E-Cell configuration. Set radius extension to 29 km.


Configure EGTCH on the TRX as specified in the test case.

EGTCH is configured on the TRX, specified in the test case.

Set the RF TA rig and simulate the distance of 40 km. For more information [Note 177]

Distance of 40 km can be simulated.

Set Link Adaptation = on, for Acknowledged RLC mode [Note 179]. (ZEQV: BTS=##: ELA=1;)

Link adaptation is enabled.

Use the MML command ZEQV: BTS=##: BLA=100; To set the maximum limit for block error rate to 100%. Check that no offsets are applied to the BEP values. For more information see [Note 178]

Block error rate is set to 100%.

Choose an MS so that RLC mode=Acknowledged mode [Note 180]. Connect MS to the RF TA rig, so that MS is in the E-Area and attempt a circuit switched call to see the value of TA on net monitor screen.

On Net Monitor screen 01-01; check that the correct TA value is displayed for the MS. At a distance of 40 km MS displays TA=22, values between 20 and 24 are acceptable.

DN0694168 Issue 2-0


Input Expected Output Set up equipment to adjust Carrier / Interference (C/I) conditions in the air interface in the direction of data transfer, specified in the test case. Initially set C/I > 30dB.

C/I is set.

Transfer a file using the TCP/IP protocol in the direction as specified in the test case.


Record an A-bis trace for PCU frames Slowly change the C/I from 30dB to 0dB and back to 30dB at the rate of approx 1 dB/sec. Repeat this step for 2 times.


In the A-bis trace track the MCS used for the initial transmissions of RLC data blocks. Track the retransmission of RLC data blocks either side of each MCS transition.

Retransmissions of the same RLC data block occurs in the coding scheme as shown in [Error! Reference source not found.]


Dynamic A-bis allocates PCU SLAVE DATA FRAMES correctly as the MCS changes see [Table 17]

Case Ref. Direction of data transfer

TRX Configuration

1 Uplink ERACH E-TRX 4 OMNI Standard E-cell 2 Downlink ERACH E-TRX 2 OMNI, IDD/4UD E-cell

26.4 Cell Reselection with GPRS/EGPRS in E-Cell

Purpose: To ensure that during GPRS/EGPRS data transfer MS can make various possible cell reselections in E-Cell.

Equipment and BTS Set-Up 2 BTSs with E-Cell configuration, RF TA rig, variable attenuator.

Input Expected Output Set up 2 sites as per the test configuration. Set radius extension to 29 km for both BTSs.

Sites are in supervisory state. Extended radius is set to 29 km.

Set the RF TA rig (for source and target cells as per the requirement of the test cases.) and simulate the distance of 40 km [Note 177]


Connect MS to the RF TA rig, so that MS is in the E-Area. Attempt a circuit switched speech call from MS to see the TA value on net monitor screen.

On Net Monitor screen 01-01; check that the correct TA value is displayed for MS. At a distance of 40 km, MS displays TA=22, values between 20 and 24 are acceptable.

DN0694168 Issue 2-0


Input Expected Output Source and Target cells (with RA specified in the test case) are defined as neighbours. Latch the MS to the BCCH frequency of the source BTS, then turn BTS Test off and reset the MS.

Net Monitor screen 01-03 displays the BCCH frequencies of the active cell and its adjacent cells. The correct neighbours are displayed.

Start data transfers in source cell as specified in the test case.

The transfer can be established on the source cell and data transfer begins successfully.

Use a variable attenuator to cause cell reselection during the data transfer.

Data transmission continues after cell reselection to the target cell. The user data rate does not degrade after reselection procedure.

The A-bis TRX links and PCU RANDOM ACCESS FRAME frames are monitored on source and target cells.

Actual TA value can be seen in the IMMEDIATE ASSIGNMENT message, PCU RANDOM ACCESS FRAME & PCU master data frames (UL).

The reselection between cells is made at least 10 times for each case.

Cell reselection is successful every time.

Case Ref. Data transfer

Source Area

Target Area

Direction of data transfer

RA of source and target cell

Configuration

1 GPRS E-Area N-Area UL Same 2 BTSs with standard E-Cell configuration

2 EGPRS E-Area E-Area DL Same 2 BTSs with standard E-Cell configuration

3 GPRS E-Area E-Area UL Different BTS1: Standard IDD/4UD E-Cell configuration BTS2: Standard E-Cell configuration

4 EGPRS E-Area E-Area DL Different BTS1: 2 TRX IDD/4UD E-Cell configuration BTS2: Standard E-Cell configuration

5 EGPRS Normal Cell area

E-Area DL Same BTS1: 4 TRX (GSM/EDGE) Normal cell BTS2: 6Omni E-cell configuration with RTC (3N-TRX+3E-TRX)

DN0694168 Issue 2-0


26.5 GPRS/EGPRS Reliability at Various MS Speeds in E-Area

Purpose:

To check that data transfer does not fail when the MS speed varies in E-Area.

Equipment and BTS Set-Up BTS with standard E-Cell configuration, RF TA rig

Input Expected Output Set up a site as per the test case configuration. Set radius extension to 29 km.




Set Link Adaptation = on (ZEQV: BTS=##: ELA=1;)


Use the MML command ZEQV: BTS=##: BLA=50; To set the maximum limit for block error rate to 50%. Check that no offsets are applied to the BEP values. For more information see [Note 178].



On Net Monitor screen 01-01; check that the correct TA value is displayed for MS. At a distance of 40 km MS displays TA=22, values between 20 and 24 are acceptable.

Transfer a 1 MB file using protocol and direction as specified in the test case.


Slowly increase the MS speed from stationary to 100Km/h and back to stationary. Perform this step for 3 times.

As MS speed increases the reported BEP increases. Link Adaptation responds accordingly and Incremental Redundancy recovers blocks successfully.

Monitor the A-bis for BEP values, coding scheme used and TA.

Actual TA can be seen on PCU RANDOM ACCESS FRAME and PCU master Data Frame (UL).Coding scheme is as per [Note 176]


Protocol Data Transfer Configuration

1 DL UDP EGPRS Standard E-Cell 2 DL TCP/IP GPRS Standard E-Cell

with BB2F(For N-TRXs) and BB2E (for E-TRXs)

DN0694168 Issue 2-0


26.6 EGPRS power control in E-Area

Purpose: To check that EGPRS power level is always equal to BCCH power level and speech power level varies according to signal strength in E-Area.

Equipment and BTS Set-Up BTS with standard E-Cell configuration, RF TA rig, spectrum analyser, variable attenuator

Input Expected Output Set up a site of standard E-Cell configuration. Set the radius extension to 29 km.




Set BTS to use specified MCS schemes (Disable link adaptation: ZEQV: BTS=##: ELA=0; Set initial coding scheme: ZEQV: BTS=##: MCEA=#, MCEU=#;)

Link adaptation is disabled and coding scheme is set.


On Net Monitor screen 01-01, check that the correct TA value is displayed for all MSs.At a distance of 40 km MS displays TA=22 Values between 20 and 24 are acceptable.

Start EGRPS data transfer on ERACH E-TRX in the direction and the time slot as specified in test case.


Start Circuit switched speech call on E-TRX (other than ERACH E-TRX) using time slot as specified in test case. Start another speech call on ERACH E-TRX on any time slot.

Circuit switched speech calls are successful & unaffected by EGPRS data transfer.

Using spectrum analyser monitor power level of EGPRS & Circuit switched speech call timeslots.

EGPRS power level is equal to BCCH power level. Speech call power level is dependent on signal strength.

Attenuate UL & DL. Monitor Abis interface. EGPRS power level remains equal to BCCH power level; circuit switched speech call power level increases with attenuation. Power control message is seen on A-bis.

Terminate all the calls. Calls are terminated successfully. Case Ref. Coding scheme Circuit switched

speech Call Time Slot

EGPRS Data Time Slot

Download Direction

1 MCS9 4 7 Downlink

DN0694168 Issue 2-0


26.7 Break in Abis interface during GPRS/EGPRS data transfer in E-Area

Purpose:

To check that both UL & DL GPRS/EGPRS data transmission using TCP/IP is able to recover in E-Area after a short break in the Abis interface.

Equipment and BTS Set-Up BTS with standard E-Cell configuration, RF TA rig, Abis breaker





Connect MS to the RF TA rig, so that MS is in the E-Area and attempt a circuit switched call to see the value of TA on net monitor screen.


Start data transfer of 5 Mb file as specified in the test case using TCP/IP.


For a period of 10 seconds the whole Abis is disrupted with random short (<0.5 s) breaks.

After breaks the link recovers, PCU frame resynchronises. Data transfer continues. Note that the Abis may be broken while the BSC is polling the BTS. This will cause the LAPD to drop. It may take over 30 sec to recover the site once the Abis is reconnected, during this time the TCP/IP connection will probably be dropped and it becomes necessary to re-activate the PDP Context

Terminate data transfer. Data transfer is stopped. Repeat steps 4 to 6, 5 times. Consistency in expected output is maintained. Case Ref. Data transfer Direction Configuration 1. EGPRS Downlink Standard E-Cell

26.8 GPRS Link adaptation in E-Area

Purpose:

To check that GPRS Link Adaptation selects the appropriate coding scheme for the changing air interface conditions and Dynamic A-bis allocates correct number of slave sub timeslot for the CS being used during GPRS link adaptation in E-Area.

DN0694168 Issue 2-0


Equipment and BTS Set-Up BTS with given configuration, RF TA rig, spectrum analyser, signal generator

Input Expected Output Set up a site of given configuration. Set the radius extension to 29 km.


Enable GPRS link adaptation by using the command ZEQV and set the below parameters [Note 183] DLA = 5%, ULA = 5% DLB = 10%, ULB = 10 COD = 0, DCSEA= 3 (if CS34 is disabled), DCSEA = 7 (if CS34 is enabled)

GPRS Link Adaptation is activated.

Set the RF TA rig and simulate the distance of 40 km [Note 177] for E-Cell BTS.


Set up equipment to adjust Carrier / Interference (C/I) conditions in the air interface in the direction of data transfer shown in the table. Initially set C/I > 27dB.

C/I is set.

Choose a non EDGE MS so that RLC mode=Acknowledged [Note 180], Connect MS to the RF TA rig, so that MS is in the E-Area. Attempt a circuit switched call from MS to see the TA value on net monitor screen.

On Net Monitor screen 01.01, check that the correct TA value is displayed for MS. At a distance of 40 km, MS displays TA=22, values between 20 and 24 are acceptable

Transfer a 1 Mb file using the TCP/IP protocol in the direction as specified in the test case.


Record an A-bis trace for PCU frames to verify the coding scheme used [Note 179] and slave frames allocated.

The PCU MASTER DATA FRAME indicates that CS2 is used is used.

Deteriorate the radio conditions gradually to C/I = 0dB.

The PCU MASTER DATA FRAME indicates that coding scheme is changed from CS2 to CS1. No slave frame is allocated.

Improve the radio conditions gradually to C/I > 27dB.

The PCU MASTER DATA FRAME indicates that CS2 is used again. Dynamic A-bis allocates one slave frame

Repeat the steps 8 &9 for three times. The coding scheme switches reliably. Case Ref. Direction

of data transfer

Configuration CS34

1 DL 6 OMNI E-Cell configuration (3 N TRX +3 E-TRX (with BB2E/BB2F))1

Disabled

1Use BSC S13

DN0694168 Issue 2-0


26.9 Multiple Dynamic A-bis Allocation for E-TRXs

Purpose:

To ensure that one BCF can utilise two dynamic A-bis connection for different E-TRXs and packet data can be transferred reliably on both E-TRXs

Equipment and BTS Set-Up BTS with given configuration, RF TA rig

Input Expected Output Set up a site of the configuration given in the test case. Set radius extension to 29 km for E-Cell BTS.


Create two DAPs on contiguous timeslots of the same PCM. Attach DAP1 to BCCH TRX and ERACH E-TRX. Attach DAP2 to non BCCH N-TRX and E-TRX (other than ERACH). (ZESE:ID=<DAP ID>,CRCT=PCM-TS,SIZE=#,BCSU=<BCSU_ID>,PCU=<PCU_ID>:;)

DAPS are successfully attached to respective TRXs.

Set the RF TA rig and simulate the distance of 40 km for E-Cell BTS [Note 177]


Choose two MSs (At least one MS should be only GPRS capable) Connect both MSs to the RF TA rig, so that MSs are in E-Area and attempt a circuit switched call to see the value of TA on net monitor screen.

On Net Monitor screen 01-01; check that the correct TA value is displayed for all MSs. At a distance of 40 km, TA=22, values between 20 and 24 are acceptable.

Start one EGPRS data transfer of 1 Mb file in DL on ERACH E-TRX and GPRS data transfer of 2 Mb file in UL direction in E-TRX other than ERACH E-TRX

Data is transferred successfully

Monitor Abis for PCU frames and Verify that Slave frames

Data is transferred with correct coding scheme and Slave Frames are used from both DAPs during data transfer.

Case Ref. Configuration 1 2(Normal Cell with GSM TRXs) +4 (Standard E-

Cell) +3 (Normal Cell with BB hopping and EDGE TRXs)

26.10 EGPRS Modulation coding schemes and IR in E-Area

Purpose:

To check that various EGPRS coding schemes with IR are supported in E-Area.

DN0694168 Issue 2-0


Equipment and BTS Set-Up BTS with given configuration, RF TA rig, signal generator, spectrum analyser





Connect 2MSs to the RF TA rig, so that MSs are in the E-Area. Attempt a circuit switched speech call to see the value of TA on net monitor screen.

On Net Monitor screen 01-01; check that the correct TA value is displayed for MSs. At a distance of 40 km, MS displays=22, values between 20 and 24 are acceptable.

Disable link adaptation: ZEQV: BTS=##: ELA=0; Set initial coding scheme: ZEQV: BTS=##: MCEA=#, MCEU=#;

Link adaptation is disabled. Initial coding scheme is set

Set C/I = >30dB in the direction specified for data transfer.

C/I is set.

Lock the timeslots to force transfer on timeslot Under test as shown in the table. Establish extra data transfer on timeslot 7 [Note 184] Setup EGPRS data transfer of 2 MB file as specified in the table below using TCP/IP.

File transfer begins. PCU MASTER DATA FRAME shows data is sent using correct MCS. No retransmissions are seen. Reliable data rate is achieved for the MCS being used [ Note 176]

Change C/I gradually to the value as specified in test case. Monitor A-bis for PCU fames

Retransmissions are observed on MCS 4 to 9 with different puncturing schemes. Data rate for the coding schemes are achieved as specified in test case.

Repeat data transfer for three times to get the reliable throughput.

Reliable throughput is achieved.

Data Rate for C/I Case Ref. MCS Direction of data transfer

TS Configuration

Data rate

C/I

1 1 DL 7 4(Standard IDD/4UD E-Cell)+3 (Normal Cell with EDGE TRXs and BB hopping)

8.5 Kbps

5 dB

2 9 UL 4 Standard IDD/4UD E-Cell configuration

28.1 Kbps

10 dB

26.11 EGPRS Link Adaptation in Unack Mode in E-Area

Purpose:

To check that in E-Area with Unacknowledged RLC Mode, Link Adaptation occurs dynamically in accordance with changes in radio condition.


DN0694168 Issue 2-0


BTS with given configuration, RF TA rig, signal generator, spectrum analyser

Input Expected Output Set up a site as given in the test case configuration. Set radius extension to 29 km for E-Cell BTS.


Set up the RF TA rig and simulate the distance of 40 km for E-Cell BTS. For more information see [Note 177]


Set Link Adaptation = on for the Unack mode [Note 185] (ZEQV: BTS=##: ELA=2;)

Link adaptation is enabled for Unack mode.

Use the MML command ZEQV: BTS=##: BLU=10; To set the maximum limit for block error rate to 10%. [Note 186] Check that no offsets are applied to the BEP values. For more information see [Note 178]


Choose an MS so that RLC Mode = Unacknowledged RLC Mode [Note 180] Connect MS to the RF TA rig, so that MS is in the E-Area. Attempt a circuit switched call from MS to see the TA value on net monitor screen.

On Net Monitor screen 01.01, check that the correct TA value is displayed for the MS. At a distance of 40 km MS displays TA=22, values between 20 and 24 are acceptable.

Set up equipment to adjust Carrier / Interference (C/I) conditions in the air interface in the direction of data transfer, specified in the test case. Initially set C/I > 30dB.

C/I is set.

Start a transfer a 1 MB file in the direction and timeslot as specified in the test case.


Record an A-bis trace for PCU frames. Slowly change the C/I from 30dB to 0dB and back to 30dB. Repeat this step for two times. Rate of change of C/I = 1 dB/sec approx. Stop recording.



Dynamic A-bis allocates PCU SLAVE DATA FRAMES correctly as the MCS changes. See [Table 17]


Configuration

1 DL Standard IDD/4UD E-Cell configuration

DN0694168 Issue 2-0


26.12 EGPRS data transfer with changing timing advance in E-Cell

Purpose:

To check that EGPRS data transfer does not fail when the MS distance varies over a wide range of E-Cell and random access bursts are successfully received over the full range of timing advance values.


Input Expected Output Set up a site of the configuration, specified in the test case. Set radius extension to 29 km.


Set the RF TA rig and simulate the distance for E-Cell BTS as specified in the test case. For more information see [Note 177]

Specified distance can be simulated.

Set Link Adaptation = on (ZEQV: BTS=##: ELA=1;)


Use the MML command ZEQV: BTS=##: BLA=90; To set the maximum limit for block error rate to 90%. Check that no offsets are applied to the BEP values. For more information see [Note 178]


Choose an EGPRS MS so that RLC Mode = Acknowledged RLC Mode [Note 180]. Connect MS to the RF TA rig, so that MS is in the area specified in the test case. Attempt a circuit switched call from MS to see the TA value on net monitor screen. For calculating TA refer [Note 175].


Start the transfer of a 2 MB file using the FTP in the direction, specified in the test case. Start Abis monitoring for PCU frames.

P-Channel required message is seen on the A-bis which reports the timing advance corresponding to the distance of the MS. Data transfer begins, and continues successfully.

As the transfer of one file completes, promptly begin the transfer of a new 2 MB file. Repeat this process until the MS reaches the distance, specified in the test case and the final file completes its transfer.

Each new file transfer begins successfully Actual TA value can be seen in the IMMEDIATE ASSIGNMENT message, PCU RANDOM ACCESS FRAME (UL) & PCU MASTER DATA FRAME (UL).

Repeat the above two steps for at least 3 times for reliable throughput.

Reliable throughput is achieved. [Note 176]


Travel direction

Starting distance

Ending distance

Speed Configuration

1 UL & DL Towards BTS

55 km 15 km 120 km/hr

Standard IDD/4UD E-Cell configuration

DN0694168 Issue 2-0


26.13 Simultaneous packet data transfer in both areas of E-Cell

Purpose:

To check that packet data transfer is possible in E-Area and N-Area simultaneously


Input Expected Output Set up a site of given configuration. Set the radius extension to 29 km for E-Cell BTS.


Set the RF TA rig and simulate the distance of 40 km [Note 177] for E-Cell BTS.


Connect one MS to the RF TA rig so that MS is in the E-Area. Attempt a circuit switched speech call from MS to see the TA value on net monitor screen. Latch one MS in N-Area.

On Net Monitor screen 01-01; check that the correct TA value is displayed for MSs connected to RF TA rig. At a distance of 40 km, MSs display TA=22, values between 20 and 24 are acceptable.

Start data transfer of 1 MB file in DL in E-Area and 2 MB file in UL in N-Area as specified in the table. Monitor the A-bis for PCU frames. For testcase3: Run testcase for 8 hrs Start 2 EGPRS and2 GPRS data transfer in N-area and 2 EGPRS and 2 GPRS data transfer in E-area.(In both areas UL and DL should have at least one GPRS and one EGPRS transfers) Also make 8 speech calls( 4 in N area & 4 in E-area)

The data is transferred successfully with correct coding scheme in both areas [Note 176]. The data is transferred successfully in both areas [Note 176]. Speech calls are successful

Case Ref. N-Area/coding

scheme E-Area/coding scheme Configuration

1 EGPRS/MCS9 GPRS/CS2 4(Standard E-Cell configuration)+4 (Normal cell with EDGE TRXs)

2 GPRS/CS1/DL1 EGPRS/MCS9/UL Standard E-Cell configuration E-TRXs and N-TRXs are on different BCSUs

3 GPRS& EGPRS with LA on2

GPRS& EGPRS with LA on

Standard E-Cell configuration

1Use BSC S13 CD3.0 SW 2 Use BSC S13 CD3.0 SW, BCSU need to be changed in between of continuous data transfer file size UL: 2 MB, DL: 3 MB

DN0694168 Issue 2-0


26.14 EGPRS/GPRS data transfer in E-Area with BER in Abis

Purpose:

To verify that GPRS/EGPRS Data transfer is successful with BER (< 1E-3) in Abis. Also verify that PCU resynchronises after loosing synchronisation due to high BER (>1E-3).

Equipment and BTS Set-Up BTS with given configuration, RF TA rig, Data Channel simulator

Input Expected Output Set up a site of the configuration given in the test case. Set radius extension to 29 km for E-Cell BTS(s).


Set the RF TA rig and simulate the distance of 40 km for E-Cell BTS(s) [Note 177]


Choose two MSs (one MS should be only GPRS capable) Connect MSs to the RF TA rig, so that MSs are in E-Area and attempt a circuit switched call to see the value of TA on net monitor screen.


Start GPRS data transfer of 1 MB file in DL with GPRS MS and EGPRS data transfer of 2 MB file in UL with other MS. Monitor the A-bis for PCU frames.

The data transfers begin successfully with correct coding schemes[Note 176]

The BER (Bit Error Ratio) of < 1E-3 is generated on Abis using the Data Channel Simulator simultaneously in both directions.

For BER greater than 1E-6 and less than 1E-3 the alarm “8102 RECEIVED BIT ERROR RATIO (BER) > 1E-6” is raised. Data transfer remains continue.

The BER (Bit Error Ratio) > 1E-3 is generated Alarms are checked on the BSC and BTS manager for both scenarios.

For BER greater than 1E-3 the alarm “8099 RECEIVED BIT ERROR RATE RATIO (BER) > 1E-3” is raised, site gets down and EGPRS/GPRS data transfers cut off.

Remove the inserted error from Abis. EGPRS timeslots regain synchronisation. Start EGPRS data transfer a 1 Mb file in DL. Data is transferred successfully. Case Ref. Configuration 1 Standard E-Cell configuration

DN0694168 Issue 2-0


26.15 EGPRS/GPRS Data Transfer after E-Cell Recovery from Power Breakdown

Purpose:

To check that EGPRS/GPRS data transfer can be performed at the expected throughput even after recovery from power breakdown.

Equipment and BTS Set-Up BTS with given configuration, RF TA rig.





Choose two MSs (one MS should be only GPRS capable) Connect MSs to the RF TA rig, so that MSs are in E-Area and attempt a circuit switched call to see the value of TA on net monitor screen.



The data transfer begins successfully with correct coding scheme and reliable data rate [Note 176]

Power off the cabinet (i.e. PWSx is switched OFF)

BCF is powered off. Data transfer is stopped.

Power is restored after 15 minutes (i.e. PWSx is switched ON)

The BCF initialises correctly after the power is restored. The site returns to operational state.

Again start GPRS data transfer of 2 MB file in DL with GPRS MS and EGPRS data transfer of 1 MB file in UL with other MS. Monitor the A-bis for PCU frames.

The data is transferred successfully with correct coding scheme and reliable data rates [Note 176]

Make AMR FR and HR speech calls in N as well as E area.


Case Ref. Configuration 1 4 (Normal Cell with GSM TRXs) +4 (Standard E-Cell configuration

with RF hopping in N-Area)

26.16 GPRS/EGPRS data transfer Stability in E-TRX of E-Cell

Purpose:

To check that BTS SW is stable; over a period of time with PS and Circuit switched speech calls are ongoing in E-TRX.

DN0694168 Issue 2-0


Equipment and BTS Set-Up BTS with given configuration, RF TA rig, Traffic generator



Set the RF TA rig for E-Cell and simulate the distance of 40 km [Note 177]


Connect MSs to the RF TA rig so that MSs are in the E-Area. Attempt circuit switched speech call from MSs to see the TA value on net monitor screen.


Start the data transfer (as defined in table) using script of 1 MB file in DL and 2 MB file in UL simultaneously, and make speech calls Monitor the A-bis for PCU frames.

The data is transferred successfully with correct coding scheme.[Note 176] Speech call is successful

Case Ref. Number Type and of Data transfer

Number, Type and duration of Speech call

Configuration Duration of the test case

1 4GPRS & 4 EGPRS throughout the test case

8 speech calls ,any type, throughout the test case

Standard E-Cell 24 hrs

2 EGPRS throughout the test case

2FR, 2EFR, 2AFS, 2AHS and 2HR calls ,Duration:60sec

6 OMNI IDD Ecell with RTC(2N-TRX+4E-TRX)

6hrs

26.17 GPRS/EGPRS data transfer with STIRC in E-Area

Purpose:

To ensure that data transfers continue in the E-TRX when STIRC is enabled in the sector.

Equipment and BTS Set-Up BTS with given configuration, RF TA rig.



Set the RF TA rig and simulate the distance of 40 km. [Note 177]


DN0694168 Issue 2-0


Input Expected Output Choose four MSs (At least one MS should be only GPRS capable) Connect MSs to the RF TA rig, so that MSs are in E-Area and attempt a circuit switched call to see the value of TA on net monitor screen.


Start GPRS data transfer of 1 MB file in DL with GPRS MS and EGPRS data transfer of 2 MB file in UL with other MS in both sectors. Monitor the A-bis for PCU frames. Also make a speech call.

The data is transferred successfully with appropriate coding scheme and reliable throughput. [Note 176]. Speech call is successful

Enable ST-IRC for both sectors using MML command: ZEQM:BTS=<bts no>:STIRC=Y;[Note 187]

The BSC sends the ST-IRC enable for the sector in the BTS_CONF_DATA (BTS-id, ST-IRC mode ‘ON’). The BTS sends ACK, on BTS_BSC_ACK to the BSC. The BTS remains WO state. The GPRS/EGPRS data transfer and the speech calls remain unaffected after ST-IRC is enabled.

Case Ref. Configuration 1 4 (Standard E-Cell) + 2 (Normal Cell )

26.18 GPRS /EGPRS in E-Cell segment with Site Synch Improvement

Purpose:

To check that GPRS/EGPRS data transfer remains unaffected during Synch recovery from LMU synch to Abis synch and vice versa.

Equipment and BTS Set-Up BTSs with given configuration, RF TA rig, LMUB with latest available SW.

Input Expected Output Set up the BCFs as per given configuration, define the synchronization chain in the BSC using the MML command: ZEFM:<s1>:CS=LAB,SENA=T,ADD=<s2>; <s1> = slave 1 BCF number <s2> = slave 2 BCF number Set the radius extension to 29 km for E-cell BTS.

Synch chain is in working state. Extended radius is set to 29 km.

In LMU manager, open the ‘Clock out timing Settings’ from the dialogue box. Set the ‘Time from fix lost to clocks out Alarm’ to 120secs.

Clock out timing is set.

Set the RF TA rig for E-Cell segment and simulate the distance of 40 km [Note 177]


DN0694168 Issue 2-0


Connect 2 MSs to the RF TA rig (ensure that at least 1 MS will support only GPRS) so that MSs are in the E-Area. Attempt a circuit switched speech call from MS to see the TA value on net monitor screen.



The data transfers begin successfully with correct coding schemes.

Establish circuit switched speech calls in both N and E areas.


Disconnect the GPS signal from the LMU. Alarm 8048 ‘Loss of Incoming Signal’ is seen on BSC. After 120 seconds of GPS signal outage, alarm 7602 ‘BCF Notification’ with Alarm detail 28 ‘External Synchronisation Signals disabled is seen on BSC The synch chain takes switchover from LMU Sync to Abis Sync and ongoing CS speech calls and the data transfer remains unaffected.

Re-establish the GPS signal. Alarm 8048 and 7602 gets cancelled. The synch chain resynchronises back to LMU sync from Abis sync. Data transfers and the CS speech calls remain unaffected during this switchover.

Case Ref. Configuration 1 E-Cell segment with Synch chain LMU + UltraSite + UltraSite

26.19 GPRS/EGPRS data transfer reliability during Intelligent shutdown modes

Purpose:

To verify that PCU synchronises and GPRS/EGPRS Data transfer is successful in E-Area after site recovers from different shutdown modes.

Equipment and BTS Set-Up BTS with given configuration, RF TA rig, Alarm Box, one BTS for neighbour cell of any EDGE configuration.

Input Expected Output Set up a site of the configuration given in the test case. Set radius extension to 29 km for E-Cell BTS. Define Bi-directional neighbour for E-Cell BTS.[Note 188]

Site is in supervisory state. Extended radius is set to 29 km. Bi-directional neighbour is defined successfully.



DN0694168 Issue 2-0


Choose two MSs, MS1 should be EGPRS capable and MS2 should be GPRS capable. Connect MSs to the RF TA rig, so that MSs are in E-Area and attempt a circuit switched call to see the value of TA on net monitor screen. Latch one MS in N-Area.

On Net Monitor screen 01-01; check that the correct TA value is displayed for all MSs. At a distance of 40 km, TA=22, values between 20 and 24 are acceptable. MS is latched successfully in N-Area.

In E-Area, Start GPRS data transfer of 1 Mb file in DL and EGPRS data transfer of 2 Mb file in UL.

Data transfer begins in E-Area.

In N-Area start GPRS data transfer of 2 Mb file in UL on the N-TRX other than BCCH.

Data transfer begins in the TRX specified.

Configure Intelligent Shutdown mode as specified in the test case. ZEFM:<bcf>:BBU=<BCCH/NONE>,NTIM=1,BTIM=3; [Note 189]

Intelligent Shutdown mode is configured as specified in the test case.

The mains breakdown alarm is generated. For BCCH shutdown mode the BSC starts the NTIM Timer. The set time for the NTIM timer expires. For None Shutdown the BSC first starts the NTIM timer. After the expiry of NTIM timer BTIM timer is started. The set time for the BTIM timer expires.


BCCH Shutdown:

Site enters in BCCH shutdown mode, all Non BCCH TRXs goes in BL-PWR state; ongoing GPRS/EGPRS call either reselects BCCH TRX of the same BTS (for the transfer going on N-TRX other than BCCH) or neighbour cell to continue the transfer.

None Shutdown: After the expiry of NTIM timer all Non BCCH TRXs goes in BL-PWR state; ongoing GPRS/EGPRS call either reselects BCCH TRX of the same BTS (for the transfer going on N-TRX other than BCCH) or neighbour cell to continue the transfer.

After the expiry of BTIM timer site enters in None shutdown mode and all working BCCH TRXs goes in BL-PWR state.

GPRS/EGPRS transfer, going on BCCH TRX of E-Cell BTS reselects the neighbour cell.

The mains breakdown alarm is cancelled. The ‘7995:MAINS BREAKDOWN WITH BATTERY BACK-UP’ is cancelled at the BSC and BTS Manager. Site recovers successfully and PCU synchronises.

Terminate the previous data transfer. Data transfer is terminated. Restart GPRS data transfer of 1 Mb file in DL and EGPRS data transfer of 2 Mb file in UL

Data transfer successful.

Case Ref. Configuration Shutdown mode 1 4 (Normal cell with RF

hopping)+4 (standard IDD/4UD E-Cell)

NONE

DN0694168 Issue 2-0


26.20 Abis loop test from BSC for EGPRS enabled E-TRX

Purpose:

To ensure that Abis loop test from BSC is supported for EGPRS enabled E-TRX.


Input Expected Output Set up a site of the configuration given in the test case. Set radius extension to 29 km for E-Cell.

Site is in supervisory state. Extended radius is set to 29 km



Choose four MSs (At least one MS should be only GPRS capable) Connect MSs to the RF TA rig, so that MSs are in E-Area and attempt a circuit switched call to see the value of TA on net monitor screen.


Start GPRS data transfer of 1 MB file in DL with GPRS MS and EGPRS data transfer of 2 MB file in UL with other MS. Monitor the A-bis for PCU frames. Also make a speech call.

The data transfer begins successfully with correct coding scheme. Speech call is successful

An Abis loop test is started from the BSC on both E-TRXs using MML command ZUBK.

The test is successfully started.

The loop test results are checked with the MML command ZUBP. Monitor the Abis.

The test status indicates success. The test results are acceptable. Time Slots carrying control channels, (E) GPRS traffic and circuit switched traffic are not tested. [Note 190] Test does not affect EPRS/GPRS transfer and circuit switched call.

Case Ref. Configuration 1 4 (Normal Cell)+4 (standard E-Cell)

26.21 GPRS/EGPRS Data transfer with Fast Tune Synchronisation enabled

Purpose:

To check that GPRS/EGPRS data can be transferred reliably in E-TRX when fast tune synchronisation is in progress.


DN0694168 Issue 2-0




Set the RF TA rig for E-Cell segment and simulate the distance of 40 km [Note 177]


Connect 2 MSs to the RF TA rig (ensure that one MS is only GPRS capable) so that MSs are in the E-Area. Attempt a circuit switched speech call from MS to see the TA value on net monitor screen.


Perform Attach and then activate PDP Contexts for both MSs. DAC word not less than 100 is changed from BTS Manager.

Attach and PDP context activation is successful. BCF starts to synchronize in Fast Tune mode. Trace master logs will show the progress of Fast tune process

Start GPRS data transfer of 1 MB file in DL with GPRS MS and EGPRS data transfer of 2 MB file in UL with other MS. Monitor the A-bis for PCU frames and user data rate is also monitored.

Data transfer is successful with correct coding schemes. Predominantly GPRS will chose CS2 and EGPRS will chose MCS9 to transfer the data [Note 176]. Data transfer continues correctly while fast tune synchronisation is in progress

Case Ref. Configuration 1 Standard E-Cell

27. STIRC

27.1 STIRC enabled sector and EGPRS Link Adaptation

Purpose:

The purpose of this test case is to check that the EGPRS Link Adaptation occurs dynamically as the prevailing radio conditions change in a ST-IRC enabled sector (blind detection).

Note 193. ST-IRC licensing can be interrogated on the BSC using MML command ZW7I ST-IRC licensing can be enabled/disabled on the BSC using MML command ZW7M

ST-IRC capacity licensing is based on the number of TRXs at the BSC, which have ST-IRC enabled.

The BSC will check the operator has enough licenses for the TRXs in the BTS objects, and checks that allowed amount of STIRC enabled TRXs is not exceeded.

When enabled, STIRC technology is deployed in the UL by BTS. When disabled, the current IRC technology is deployed by the BTS.

Note 194. STIRC can be enabled at any time without locking/unlocking of the TRX/sector/site, this indicates that BTS_CONF_DATA containing the info field about STIRC enable/disable can be sent at anytime when BTS is running.

Test Tools Required: Signal Generator, Spectrum Analyser.

DN0694168 Issue 2-0


Coding Scheme


CS 1 0

CS 2 1

MCS 1 0

MCS 2 1

MCS 3 1

MCS 4 1

MCS 5 1

MCS 6 2

MCS 7 3

MCS 8 4

MCS 9 4

Table 18

Initial transmission

, prior to transition

MCS transition Retransmission After transition


Air Interface conditions improving MCS 1 MCS 1 → 2 MCS 1 MCS 2 MCS 2 → 3 MCS 2 MCS 3 MCS 3 → 4 MCS 3 MCS 4 MCS 4 → 5 MCS 4 MCS 5 MCS 5 → 6 MCS 5 MCS 6 MCS 6 → 7 MCS 6 MCS 7 MCS 7 → 8 MCS 7 MCS 8 MCS 8 → 9 MCS 8 Table 19

DN0694168 Issue 2-0


Input Expected Output Create a BCF with the Configuration mentioned in the test case.

The BCF is in WO state.

Enable STIRC for the EDGE sector using MML command: ZEQM:BTS=<bts no>:STIRC=Y; Monitor O&M messages on Abis.

The BSC sends the STIRC enable for the sector in the BTS_CONF_DATA (BTS-id, STIRC mode ‘ON’). The BTS sends ACK, on BTS_BSC_ACK to the BSC.

Enable EGPRS in the sector and set the values of CDED, CDEF & CMAX such that it configures 2 GP TSs on BCCH TRX. Set Link Adaptation = ON

EGPRS is enabled and the GP TSs are configured successfully.

To set the max. limit for a Block Error rate to 10 per 1000 use the MML command: ZEQV:BTS=<bts no>:BLU=10;

The Block Error rate is set successfully.

Check that there are no offsets applied to the BEP values Set up the equipment to adjust the Carrier/Interference (C/I) conditions in the air interface in the Uplink direction. Initially set the C/I > 25dB

The equipment is configured successfully to provide the required interference in the uplink direction.

Transfer a 500 kB file using the UDP/IP protocol in the UL direction (use 1 TS)

Transfer starts successfully.

Record the Abis trace and monitor the PCU data frames. Slowly change the C/I from 25 dB to 0 dB and back to 25 dB. Repeat. The rate of change = 1 dB/sec approx. Stop recording the Abis trace and check the trace for the MCS used, and the allocation of the PCU Slave Data Frames (detailed in Error! Reference source not found.)

The coding scheme used steps down through the coding schemes from the least robust (MCS9) to the most robust (MCS1) and back again to match the changing air interface conditions. MCS4 may be skipped as the Link Adaptation switches from 8PSK to GMSK and vice versa (Table 19). The data rate changes to reflect the changing MCS. The Dynamic Abis allocates the PCU SLAVE DATA FRAMES correctly as the MCS changes

Case Ref. Configuration/Site type Band BCCH type 1 2+2 (EDGE) /Ultra Site Any BCCH

27.2 EMR measurement reporting and comparison testing of STIRC and IRC

Purpose:

The purpose of this test case is to check that with (CX7.0) STIRC enabled, the quality of the uplink radio signal is accurately reflected in the measurements reported by the BTS to the BSC and a comparison measurement is made against the BTS SW CX7 (IRC), STIRC disabled.

Note 195. The RX level, RX quality, Mean BEP, CV BEP and UL FER are part of Measurement Results and not part of the Enhanced Measurement Report Layer 3 message.

DN0694168 Issue 2-0


The Mean BEP, CV BEP and UL FER are coded in the Suppl Info field in the Measurement Result in the BTSM layer.

Note 196. When DTX is ON the RxQual Full will always be reported as 7 and may be ignored. The RxQual Sub should reflect the true radio conditions.

Test Tools Required: Signal Generator, Spectrum Analyser, Variable attenuator.

Input Expected Output Create a BTS with the Configuration mentioned in the test case.

The BTS is in WO state.

Enable STIRC for the EDGE sector using MML command: ZEQM:BTS=<bts no>:STIRC=Y; Monitor O&M messages on Abis.

The BSC sends the STIRC enable for the sector in the BTS_CONF_DATA (BTS-id, STIRC mode ‘ON’). The BTS sends ACK, on BTS_BSC_ACK to the BSC. The BTS is in WO state.

Set uplink DTX as shown in the configuration below. DTX is set successfully. Set 2-way Diversity ON. The main and diverse receiver paths must be each tested separately. Set up the RF path in the uplink direction. IMPORTANT – Ensure that there is no direct path from the MS to the BTS through the air. The MS must be in a screened box. All cables must be correctly tightened.

Diversity is enabled and RF path is setup successfully.

Fix the transmit power of the MS to near its minimum using the MML command: ZEQM:BTS=<bts no>:PMAX1=7,PMAX2=6,PMIN=7; This stops the carrier power from varying during the test, and minimises the chances of a leakage signal via the air reaching the BTS

The transmit power of MS is fixed successfully using MML commands.

Make a speech call to a PSTN number or to a MS locked to a different BTS. Monitor the TRXSIG for the STIRC enabled BTS on the Abis for MEASUREMENT RESULTS messages. Adjust the variable attenuator so that the signal level seen at the BTS is reported as -84 to – 85 dBm

Call is established successfully.

With the interferer switched off, measure the power of the uplink bursts as shown in Figure 5. Calculate the input power at the receiver taking into account the coupler, any attenuators and any duplexers in the path

The input power to the receiver is between -83 and -88 dBm

DN0694168 Issue 2-0


Input Expected Output Disconnect the call. Set up the signal generator to provide a continuous interferer, with digital modulation = GSM standard. Set the reference level to 10dB below the uplink carrier power measured above (i.e. C/I = 10dB). Switch off the interferer

Call is disconnected successfully. Signal Generator is configured correctly to provide the required interference.

Make a speech call to a PSTN or to a MS locked to a different BTS. Check that the carrier power is the same as previously measured. Switch on the interferer (make any slight adjustments to the level if the carrier power has changed) Monitor the Abis for MEASUREMENT RESULT messages. Record a trace for 1 minute at C/I = 10 dB. Reduce the C/I in 1 dB steps from 10 to 0 dB, recording a minute trace for each step. Disconnect the call and switch off the interferer.

Call is established successfully.

Analyse the traces for UL Mean BEP, UL FER and DTX off – RxQual Full DTX on – RxQual Sub

The UL Mean BEP, UL: FER and RxQual are within the limits shown below as per Table 1 & 2.

Repeat case with BTS SW CX7 with STIRC disabled.(IRC)

Compare results with CX7.0 STIRC enabled and with STIRC disabled, No RX Quality degradation is observed with IRC. Results are within limits shown below.

Case Ref. Configuration / Band UL DTX Activation

Limits

1 4 OMNI (EDGE) /Any ON FER always reported as 0 with no interference. RxQual and Mean BEP see Table 1

2 4 OMNI (EDGE) /Any OFF See Table 1 & Table 2

Table 20 RxQual and UL BEP

C/I dB RxQual level reported UL Mean BEP level reported Max Min Max Min

10 0 0 31 31 9 0 0 31 31 8 0 0 31 25 7 1 0 31 19 6 3 0 24 15 5 4 1 19 11 4 5 3 14 8 3 6 4 11 5 2 6 5 8 4

DN0694168 Issue 2-0


1 7 6 6 3 0 7 6 4 1

Table 21 UL FER

C/I dB UL FER reported

Max Min 10 0 0 9 0 0 8 0 0 7 0 0 6 0 0 5 0 0 4 0 0 3 3 0 2 11 0 1 17 01 0 20

27.3 Enable and Disable STIRC in the first sector whilst Packet Data calls and speech calls ongoing in the second sector.

Purpose:

To confirm that STIRC can be enabled and disabled in the first sector without disturbing the speech calls and the packet data calls (MCS 3, 6 & 9) that are ongoing in the other sector.



Enable STIRC in the second sector using MML command: ZEQM:BTS=<bts no>:STIRC=Y; Monitor O&M messages on the Abis.

The BSC sends the STIRC enable for the sector in the BTS_CONF_DATA (BTS-id, STIRC mode ‘ON’). The BTS sends ACK, on BTS_BSC_ACK to the BSC.

Make packet data calls in the second sector as mentioned in the test case. Make a MS to MS speech call on the same sector.

Packet data calls are successful Speech call is established successfully.

DN0694168 Issue 2-0


Input Expected Output Enable STIRC in the first sector using MML command: ZEQM:BTS=<bts no>:STIRC=Y; Monitor O&M messages on the Abis.

The BSC sends the STIRC enable for the sector in the BTS_CONF_DATA (BTS-id, STIRC mode ‘ON’). The BTS sends ACK, on BTS_BSC_ACK to the BSC. Enabling STIRC in the first sector does not affect the packet data calls and the speech calls in the second sector.

Case Ref. Configuration Codec Hopping 1 2+2 ( EDGE) MCS 9 Any

27.4 Enable and Disable STIRC in the first sector whilst AFS, AHS and CS Data calls ongoing in the second sector.

Purpose:

The purpose of this test case is to check that STIRC can be enabled and disabled in the first sector without disturbing the AMR FR, AMR HR and CS data calls that are ongoing in the other sector.



Make the call as mentioned in the test case in the second sector.

Calls are successful and remain ongoing throughout the test

Enable STIRC for the first sector using MML command: ZEQM:BTS=<bts no>:STIRC=Y;

The calls remain unaffected in the second sector.

Monitor messages on the Abis. The BSC sends the STIRC enable for the sector in the BTS_CONF_DATA (BTS-id, STIRC mode ‘ON’). The BTS sends ACK, on BTS_BSC_ACK to the BSC.

Make calls on the first sector Calls are successful Disable STIRC in the first sector using MML command: ZEQM:BTS=<bts no>:STIRC=N;

BTS receives BTS_CONF_DATA containing STIRC information STIRC mode, BTS id). BTS sends BTS_BSC_ACK to the BSC. The calls in both the sectors are not affected after disabling STIRC in the first sector.

Case Ref. Configuration/Channel config Call Type Hopping 1. 2+2 (EDGE)

/MBCCH+SDCCH+TCH AMR FR RF

DN0694168 Issue 2-0


27.5 Speech Emergency call Setup via SDCCH

Purpose:

The purpose of these tests is to verify that speech and emergency calls can be activated from SDCCH channels, that EFR, FR & AFS are supported on TCHF and EFR, FR, HR, AFS & AHR are supported on TCHD, and all paging groups available in configuration are used.

Note 197. For Emergency call normal HR call is not possible, only AHS call is possible. EFR call is possible in 900/1800/1900 band sites. All test cases for emergency call will activate FR/EFR/AFS TCH and normal call should be activated on TCH specified by test case.

Input Expected Output Calls are made from MS to MS on the test BTS using minimum call repetition criteria. Each call must be held for the duration of the test case.

All calls are successful and held until user terminates the calls. The received audio quality is good with no distortion and there are no additional disturbing sounds heard at the receiving end during speech or silence periods.

Enable STIRC in the test sector by MML command ZEQM: BTS=<BTS ID>: STIRC=Y;

STIRC is enabled successfully. Calls remain ongoing with no disturbance.

A-bis interface is monitored after enabling STIRC.

BSC sends the STIRC enable for the sector in the BTS_CONF_DATA (BTS-id, ST_IRC mode ‘ON’) BTS sends “ACK” on “BTS ACK” message to the BSC.

Trace master is used to monitor the UC-DSP traces.

STIRC information is sent to the EQDSP in the INI message for the sector.

Disable ST-IRC in the sector by MML command ZEQM: BTS=<BTS ID>: STIRC=N;

ST-IRC is disabled successfully.

A-bis interface is monitored after disabling STIRC.

BSC sends the STIRC disable for the sector in the BTS_CONF_DATA (BTS-id, ST_IRC mode ‘OFF’) BTS sends “ACK” on “BTS ACK” message to the BSC.


STIRC information is sent to the EQDSP in the INI message the test sector.


In A-bis Measurement Result values for RX Qual in both UL/DL and UL FER and DL FER( in case of EMR calls) are predominantly 0. A-bis RF RES IND message for a reserved TCH timeslot shall include the active interference measurement. In CCCH LOAD IND message (uplink), BTS should report non-zero values for RACH access count.

DN0694168 Issue 2-0



All emergency calls are successful and held until user terminates the call


On A-bis Channel Required message will contain ‘Emergency Call’ for field Request reference.

Case Ref.


Codec Configura-tion

AG blocks in BCCH

Hopp-ing Mode

Emer-gency Call

1 Combined BCCH + TCHD, 2 Channels Configured as TCHH

HR/FR/AFS/AHS/EFR

6 Omni EDGE

1 Non-hopping

Yes

28. AMR SIGNALLING IMPROVEMENTS

Note 198. DTX is disabled in both Uplink and downlink unless otherwise stated.

Note 199. ASI is supported by all TRXs configured only with EDGE BB cards.

Note 200. SACCH Repetition is possible only with RSC MS.

Note 201. FACCH Repetition is possible with both RSC & Non-RSC MS

Note 202. Repetition of LAPDm Response frames on FACCH is possible only with RSC MS.

Note 203. All test cases need to be executed with ASI features enabled at the BSC unless otherwise stated.

Note 204. Nokia Siemens Networks UltraSite and Nokia Siemens Networks MetroSite EDGE BTSs support FR modes of 12.2, 10.2, 7.95, 7.4, 6.7, 5.9, 5.15 and 4.75 and HR modes of 7.4, 6.7, 5.9, 5.15, and 4.75.

The AMR set includes AMR Codecs, their threshold and hysteresis values and Initial Codec mode used to start the speech coding at call Setup and after handover.

Note 205. Basic AMR set for FR channel on BSC

DN0694168 Issue 2-0


Codec Mode

Threshold (C/I)

Hysteresis (C/I)

Lower threshold

(C/I)

Upper threshold

(C/I)

BER (%)

FER (%)

12.2 11 1 11 - 2.97 0.08 7.4 7 1 7 12 6.72 0.15 5.9 4 1 4 8 10.83 0.98 4.75 - 5


Codec Mode

Threshold (C/I)

Hysteresis (C/I)

Lower threshold

(C/I)

Upper threshold

(C/I)

BER (%)

FER (%)

7.4 14 1 14 - 0.62 5.9 11 1 11 15 1.08 4.75 - 12

Lower threshold in the tables above means towards more robust Codec (more correction, lower bit rate) and upper threshold means less robust Codec (less correction, higher bit rate).

Note 207. Initial Codec mode is used to start the speech coding at call Setup and after handover. If the Initial Codec mode is not defined, then the default Initial Codec Mode is given by the following implicit rule. If the Active Codec Set contains:

1 mode, then this shall be the Initial Codec Mode;

2 or 3 modes, then the Initial Codec mode shall be the most robust mode of the set (with lowest bit rate);

4 modes, then the Initial Codec Mode shall be the second most robust mode of the set (with second lowest bit rate).

Note 208. Whenever ‘FACCH Repeat’ is enabled in the ‘Channel Activation’ message, the BTS LAPDm T200 timer gets modified as-




DN0694168 Issue 2-0


Note 209. A repeated FACCH block are sent in such a way that, if the first burst of the downlink FACCH block containing the first instance of a LAPDm frame is sent in TDMA frame M, the first burst of the downlink FACCH block containing the repeated instance of the LAPDm frame is sent in TDMA frame M+8 or M+9 (the latter corresponding to the case where the two FACCH blocks are separated by either a SACCH frame or an idle frame).

Note 210. In FACCH repetition cases, the level of interference should be kept near about the maximum signal level that the MS can transmit, so that at some moments during the test execution, the START / STOP DTMF messages are decoded but not the uplink RR Response frames by the BTS.

As the RR Response frames in uplink are not decoded by the BTS, the BTS retransmits START / STOP DTMF ACKNOWLEDGE message in downlink due to T200 expiry.

DTMF Message Transmission

Note 211. DFCA operation requires that the network be synchronised. Location Measurement Unit (LMU) is used for the purpose of synchronisation. The LMU is installed in the site and it derives the synchronized clock signal from a GPS time reference. Consecutive sites may then be synchronised in the normal manner (i.e. synchronisation cable), thus also acquiring the GPS time reference from the LMU on the 1st site.

DN0694168 Issue 2-0


Note 212. MA list setup for DFCA :

a) Create MA list(e.g, 1) using the MML command ZEBE (e.g., ZEBE:1,900:FREQ=4&30&35;)

b) Attach MA list 1 AS DFCA UNSYNCHRONIZED MODE MA LIST TO BTS (e.g., ZEQA:BTS=xxx:DUMAL=1;)

c) Create MA list(e.g., 2016) as a DFCA MA list (e.g., ZEBE:2016,900:FREQ=1&5&6;)

d) Put DFCA MA list 2016 in use (e.g., ZEBT:2016,C:MALS=IN;)

e) Attach DFCA MA list(e.g., 2017) to the BTS; DUMAL=1 indicates the MA list 1

(e.g., ZEQA:BTS=xxx:DMAL=2016,OPE=A,DUMAL=1,;)

f) Create MA list 2017 as a DFCA MA list (e.g.,ZEBE:2017,900:FREQ=2&7&8;)

g) Put DFCA MA list 2017 in use (e.g.,ZEBT:2017,C:MALS=IN;)

h) Attach DFCA MA list 2017 to the BTS; DUMAL=1 indicates the MA list 1

(e.g.,ZEQA:BTS=xxx:DMAL=2017,OPE=A,DUMAL=1,;)

28.1 Capability Notification - Lock/Unlock from BSC

Purpose: To ensure that ‘Air i/f modulation’ element of the Abis O&M BTS_STATE_CHANGED message, indicating the GMSK/EDGE capabilities of the TRX, is reported correctly for a TRX after the lock/unlock command is given from BSC.

Equipment and BTS Set-Up Site - as per configuration defined in test case.

Input Expected Output Create a site with the configuration mentioned in the test case


Perform ‘Action 1’ as defined in the test case. To lock TRX use MML command: ZERS:BTS=<bts num>,TRX=<trx num>,:L; To lock Sector use MML command: ZEQS:BTS=<bts num>:L; To lock BCF use MML command: ZEFS:<bcf num>:L;

The object (TRX/Sector/BCF) gets locked.

Check the status of the object (TRX/Sector/BCF) at BSC with the help of MML command: ZEEI:BCF=<bcf num>;

The status of the object (TRX/Sector/BCF) is shown as ‘BL-USR’ at the BSC

DN0694168 Issue 2-0


Input Expected Output Perform ‘Action 2’ as defined in the test case. To unlock TRX use MML command: ZERS:BTS=<bts num>,TRX=<trx num>,:U; To unlock Sector use MML command: ZEQS:BTS=<bts num>:U; To unlock BCF use MML command: ZEFS:<bcf num>:U;

The object (TRX/Sector/BCF) gets unlocked.

Check the status of the object (TRX/Sector/BCF) at BSC with the help of MML command: ZEEI:BCF=<bcf num>;

The status of the object (TRX/Sector/BCF) is shown as ‘WO’ at the BSC

Monitor the Abis O&M interface for every BTS_STATE_CHANGED message.

For MetroSite For GSM TRXs, the BTS_STATE_CHANGED message will omit the ‘Air i/f modulation’ information element. For EDGE TRXs, the BTS_STATE_CHANGED message will include the ‘Air i/f modulation’ information element with Modulation Capability set to ‘GMSK and 8-PSK’. For UltraSite The BTS_STATE_CHANGED message will include the ‘Air i/f modulation’ information element with Modulation Capability set to ‘GMSK’.

For case 2, Block/Unblock the individual BTSs from the BTS manager.

The BTS is blocked/Unblocked successfully. The alarm 7208 LOCAL BLOCK: TRX / BTS / BCF is sent to BSC and BTS Manager when the TRX / BTS / BCF is blocked from BTS Manager. The alarm gets cleared when it is unblocked

For case 2, Monitor the Abis O&M interface during the re-initialization of the BTS.

For MetroSite For GSM TRXs, the BTS_STATE_CHANGED message will omit the ‘Air i/f modulation’ information element. For EDGE TRXs, the BTS_STATE_CHANGED message will include the ‘Air i/f modulation’ information element with Modulation Capability set to ‘GMSK and 8-PSK’.

For case 2, Block/Unblock the BCF from the BTS manager.

The BCF is blocked/Unblocked successfully. The BCF takes a reset and then re-initializes. The alarm 7208 LOCAL BLOCK: TRX / BTS / BCF is sent to BSC and BTS Manager when the TRX / BTS / BCF is blocked from BTS Manager. The alarm gets cleared when it is unblocked

DN0694168 Issue 2-0


Input Expected Output For case 2, Monitor the Abis O&M interface during the re-initialization of the BCF

For MetroSite For GSM TRXs, the BTS_STATE_CHANGED message will omit the ‘Air i/f modulation’ information element. For EDGE TRXs, the BTS_STATE_CHANGED message will include the ‘Air i/f modulation’ information element with Modulation Capability set to ‘GMSK and 8-PSK’.

Case Ref. Configuration Action 1 Action 2 1. 2 (Hybrid-BB2E)+ 2 (Hybrid-

BB2F) Lock every sector one by one

Unlock every sector one by one

2. 2 (GSM)+2 (EDGE) Lock every TRX one by one

Unlock every TRX one by one

28.2 Capability Notification - Block/Unblock from BTS Manager

Purpose: To ensure that ‘Air i/f modulation’ element of the Abis O&M BTS_STATE_CHANGED message, indicating the GMSK/EDGE capabilities of the TRX, is reported correctly for a TRX after the block/unblock command is given from BTS manager.

Input Expected Output Create a site with the configuration mentioned in the test case.


Launch the BTS Manager application and connect to the BTS.

BTS Manager application is launched and connected to the BCF successfully.

Block/Unblock every TRX one by one from the BTS Manager (Objects/Properties).

The alarm 7208 LOCAL BLOCK: TRX / BTS / BCF is sent to BSC and BTS Manager when the TRX / BTS / BCF is blocked from BTS Manager. The alarm gets cleared when it is unblocked.


For UltraSite For GSM TRXs configured with BB2A card, the BTS_STATE_CHANGED message will omit the ‘Air i/f modulation’ information element. For GSM TRXs configured with BB2E or BB2F card, the BTS_STATE_CHANGED message will include the ‘Air i/f modulation’ information element with Modulation Capability set to ‘GMSK’. For EDGE TRXs configured with BB2E or BB2F card, the BTS_STATE_CHANGED message will include the ‘Air i/f modulation’ information element with Modulation Capability set to ‘GMSK and 8-PSK’.

DN0694168 Issue 2-0


Input Expected Output Block/Unblock the BCF from the BTS manager. The BCF is blocked/unblocked successfully.

The BCF takes a reset and then re-initializes. The alarm 7208 LOCAL BLOCK: TRX / BTS / BCF is sent to BSC and BTS Manager when the TRX / BTS / BCF is blocked from BTS Manager. The alarm gets cleared when it is unblocked

Monitor the Abis O&M interface during the re-initialization of the BTS

For UltraSite For GSM TRXs configured with BB2A card, the BTS_STATE_CHANGED message will omit the ‘Air i/f modulation’ information element. For GSM TRXs configured with BB2E or BB2F card, the BTS_STATE_CHANGED message will include the ‘Air i/f modulation’ information element with Modulation Capability set to ‘GMSK’. For EDGE TRXs configured with BB2E or BB2F card, the BTS_STATE_CHANGED message will include the ‘Air i/f modulation’ information element with Modulation Capability set to ‘GMSK and 8-PSK’.

Case Ref. Configuration 1. 2 (GSM) + 2 (EDGE-BB2E) + 2 (Hybrid-BB2E)

28.3 Capability Notification - TRX Replacement and Power Reset

Purpose: To ensure that ‘Air i/f modulation’ element of the Abis O&M BTS_STATE_CHANGED message, indicating the GMSK/EDGE capabilities of the TRX, is reported correctly for a TRX either after replacing the EDGE TRX with GSM TRX or after replacing the GSM TRX with EDGE TRX.

Input Expected Output Create a site with the configuration mentioned in the test case


Reset the BCF using the MML command: EFR:<bcf num>:SITE:;

The BCF is initialised and BCF returns to operational state.


For UltraSite For GSM TRXs configured with BB2E or BB2F card, the BTS_STATE_CHANGED message will include the ‘Air i/f modulation’ information element with Modulation Capability set to ‘GMSK’. For EDGE TRXs configured with BB2E or BB2F card, the BTS_STATE_CHANGED message will include the ‘Air i/f modulation’ information element with Modulation Capability set to ‘GMSK and 8-PSK’.

DN0694168 Issue 2-0


Input Expected Output Lock the BCF using the MML command: EFS:<bcf num>:L; Replace every existing TRX unit in the BCF with the TRX unit of the same frequency band as mentioned in the test case.

The BCF gets locked

Unlock the BCF using the MML command: EFS:<bcf num>:U;

The BCF is initialised and BCF returns to operational state.


For UltraSite For GSM TRXs configured with BB2E or BB2F card, the BTS_STATE_CHANGED message will include the ‘Air i/f modulation’ information element with Modulation Capability set to ‘GMSK’. For EDGE TRXs configured with BB2E or BB2F card, the BTS_STATE_CHANGED message will include the ‘Air i/f modulation’ information element with Modulation Capability set to ‘GMSK and 8-PSK’. The BTS_STATE_CHANGED message observed in this step must be accordingly changed with that one observed in step 3.

Switch ‘OFF’ and switch ‘ON’ the cabinet power. BCF is reset. Monitor the Abis O&M interface for every BTS_STATE_CHANGED message.

The BTS_STATE_CHANGED message for each TRX includes the ‘Air i/f modulation’ information element with Modulation Capability set to ‘GMSK’.

Case Ref. Configuration TRX to be replaced 1. 4 Omni (EDGE-BB2E) EDGE by GSM

28.4 Capability Notification - Capability Notification after Sector Reconfiguration with BB Hopping

Purpose:

To ensure that ‘Air i/f modulation’ element of the Abis O&M BTS_STATE_CHANGED message, indicating the GMSK/EDGE capabilities of the TRX, is reported correctly for a TRX after the TRX is pulled out from a sector with BB hopping enabled.


Input Expected Output Create a site with the configuration as mentioned in the test case.


Pull out one TRX from every sector. Sector reconfiguration takes place in every sector.

DN0694168 Issue 2-0


Input Expected Output Monitor the Abis O&M interface for every BTS_STATE_CHANGED message.

BTS_STATE_CHANGED message will appear for the TRX(s) which is/are present in the cabinet. For GSM TRXs, the BTS_STATE_CHANGED message will omit the ‘Air i/f modulation’ information element. For EDGE TRXs, the BTS_STATE_CHANGED message will include the ‘Air i/f modulation’ information element with Modulation Capability set to ‘GMSK and 8-PSK’.

Case Ref. Configuration Hopping Mode 1. 2(GSM) + 2(EDGE) BB

28.5 Feature Control - SACCH Repetition

Purpose: To check that when the Repeat SACCH Criteria are met, repetition of uplink or downlink SACCH is triggered and the subsequent SI and MI messages on downlink SACCH get repeated but the SMS segments are not repeated.

Note 213. For, N=1, SRO bit is set if preceding SACCH block single decode failed.

For, N=2…15, SRO bit is set if 2 of the N preceding SACCH block single decodes failed

Where, N is the value of SRW

Note 214. The default value of ‘Invalid BSIC Reporting’ at the GSM cell is ‘0’.Its value can be changed using MML command ZEHN.

Note 215. If the MSC's TC1 timer was expiring too early, this may cause a re-send of SMS to occur before the acknowledgement was received. It is advisable to set the value of MSC's TC1 Minimum parameter as 10 seconds. Its value can be changed using MML command ZWOC.

The parameter 000 TC1 MINIMUM has default value 0 seconds and allowed range is from 0 (0 s) to 3000 (30 s).

Equipment and BTS Set-Up Sites - as per configuration defined in test case.

Signal generator, Spectrum Analyser, Abis monitoring tool, Air i/f monitoring tool.

DN0694168 Issue 2-0




Set ARLT=64 with the help of MML command: ZEQY:BTS=<bts num>:ARLT=64;

ARLT is set to 64.

Set the value ‘SACCH Repeat Window (SRW)’ as mentioned in the test case with the help of MML command: ZEEQ:SRW=<x>;

SRW is set.

Start a speech call as specified in the test case and monitor the Abis i/f.

‘SACCH Repeat’ is enabled and ‘SACCH Repeat Window (SRW)’ as specified in the test case is present in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages. Call is successful.

Monitor the Air i/f On Channel activation, the SI message on downlink SACCH gets repeated exactly once in the SACCH period next to the SACCH period in which the first SI message is sent. The BTS stops repeating the SI message on downlink SACCH once the MS acknowledges the receipt of first SI message with SACCH Repeat Request (SRR) set to 0 in the L1 header of the uplink SACCH.

Add interference on Air i/f in the direction as specified in the test case and start increasing it slowly until the repetition starts. Analyse the Air i/f messages.

For interference added in downlink: The MS, being unable to decode the downlink SACCH, sets the SACCH Repeat Request (SRR) to 1 and sends it to the BTS in the L1 header of the uplink SACCH. The SI message on downlink SACCH gets repeated exactly once in the SACCH period next to the SACCH period in which the SRR=1 is received by the BTS For interference added in uplink: The BTS, being unable to decode the uplink SACCH, sets SACCH Repeat Order (SRO) to 1 and send it to the MS in the L1 header of the downlink SACCH [Note 213] The SI message on downlink SACCH gets repeated exactly once in the SACCH period next to the SACCH period in which the SRO=1 is sent by the BTS.

Change the status of ‘Invalid BSIC reporting’ of the BTS with the help of the MML command: ZEHN:BTS:<bts num>::IBR=<1->;

The status of ‘Invalid BSIC reporting’ of the BTS changes to 1.

Monitor the Abis i/f for MI message. The MI message containing the status of ‘Invalid BSIC reporting’ is sent to the BTS by the BSC.

Monitor the Air i/f. The MI message on downlink SACCH gets repeated (as SACCH repetition is in effect) in the SACCH period very next to the SACCH period in which the original instance of the MI message was sent.

Send an SMS to the MS latched on to the BTS under test.

The SMS segment is sent on the downlink SACCH to the MS latched on to the BTS under test.

DN0694168 Issue 2-0


Input Expected Output Monitor the Air i/f. The SMS segment is sent only once on the

downlink SACCH. Monitor the screen of the MS latched on to the BTS under test.

The SMS segment is received only once.

Terminate the speech call. The speech call is terminated. Case Ref. Configuration Call

Type SRW Interference

1. 4 Omni (Hybrid – BB2E) AHS Default DL 2. 4 Omni EDGE AHS 15 UL 3 4 Omni (EDGE) AFS 10 UL

28.6 Feature Control - Downlink FACCH Repetition with Asynchronous Handover

Purpose: To ensure that the LAPDm UI frames (carrying Physical Information message) as well as Response frames in case of asynchronous handover and LAPDm Command frames on downlink FACCH get repeated whenever the downlink FACCH Repetition criteria are met.

Note 216.

Set the MS maximum transmit power using MML command: ZEQM:BTS=<bts num>:PMAX1=5,PMAX2=6;


Signal generator, Abis interface monitoring tool, Air interface monitoring tool.



Define neighbour using the MML ZEAC Neighbour is defined. Disable intra-cell handovers at source BTS using the MML command: ZEHG:BTS=<bts num>:EIC=N,EIH=N;


Define ARLT=64 at source and target BTSs using the MML command: ZEQY:BTS=<bts num>:ARLT=64;

ARLT=64 is set.

For case 2,Lock all the channels of the source cell except 6 & 7.

The channels are locked successfully.

DN0694168 Issue 2-0


Input Expected Output Make a speech call in the source BTS and terminate it in a separate test cell. The call type and MS type are as defined in the test case. Monitor the Abis i/f.

‘FACCH Repeat’ is enabled in the ‘ACCH control IE’ of the Channel Activation message. Call is successful.

During the AMR call, C/I conditions are gradually changed in downlink at the source BTS to manipulate the air interface so that the downlink codec mode changes and reaches to the most robust codec of the ACS.

Downlink Codec mode changes to the most robust codec of the ACS.

Lock all the traffic channels at target BTS (to prevent inter-cell handover) using MML command: ZERS:BTS=<bts num>,TRX=<trx num>,CH=0&&7,:L;

All the traffic channels at target BTS get locked.

Now add interference [Note 210] in uplink to the source BTS and start sending DTMF messages to generate FACCH traffic by pressing the keys on keypad of the MS. (About 30 DTMF messages should be enough). Monitor the Abis and Air i/f for FACCH messages.

‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’ message encapsulated in DL I-frame will appear on DL FACCH. For AMR/FR Call: The transmissions of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) as well as its retransmission, after T200 F expiry, gets repeated on Air i/f, if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. No repetition will be seen if the most robust codec is any codec other than 4.75, 5.15 or 5.90 kbps or if CMR sent is for a codec mode other than the most robust codec. For AMR/HR Call: Only the retransmission of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) after T200 F expiry gets repeated on Air i/f, if the CMR is 4.75 kbps. No repetition will be seen if the most robust codec is any codec other than 4.75 kbps or if CMR sent is for a codec mode other than the most robust codec.

Disconnect the call. Call is disconnected. Unlock one traffic channel at target BTS using MML command: In case 2 unlock 2 channels CH 6&7 of the BCCH TRX, of the target BTS. ZERS:BTS=<bts num>,TRX=<trx num>,CH=<channel num>,:U;

The required number of traffic channel(s) at target BTS are unlocked successfully.

Remove all interference sources from the source BTS. Then again make a speech call in the source BTS and terminate it in a separate test cell. The call type and MS type are as defined in the test case. Monitor the Abis i/f.


DN0694168 Issue 2-0


Input Expected Output At the target BTS set C/I conditions in downlink so that when call arrives at target BTS the downlink codec mode used, is the most robust codec of the ACS and also add interference with C/I~1-3 in uplink to the target BTS. Initiate handover from source to target BTS as mentioned in the test case by varying the signal level with the help of variable attenuators (set the signal level of target BTS higher than the source BTS). Monitor the Abis and Air i/f for FACCH messages.

‘FACCH Repeat’ is enabled in the ‘ACCH control IE’ of the Channel Activation message at the target BTS. The target BTS sends DL response frames and PHYSICAL INFORMATION encapsulated in DL UI-frame on FACCH to the MS. The timer T3105 expires. The retransmission of DL UI-frame (carrying only PHYSICAL INFORMATION) due to expiry of T3105 timer gets repeated on Air i/f. Also For AMR/FR Call: All DL response frames on FACCH are repeated if CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. No repetition will be seen if the most robust codec is any codec other than 4.75, 5.15 or 5.90 kbps or if CMR sent is for a codec mode other than the most robust codec. For AMR/HR Call: Only the DL UA response frames on FACCH get repeated, if CMR is 4.75 kbps. No repetition will be seen if the most robust codec is any codec other than 4.75 kbps or if CMR sent is for a codec mode other than the most robust codec. Call is successfully handed over.

Disconnect the call. Call is disconnected.

DN0694168 Issue 2-0


Input Expected Output Case Ref ACS having

codecs as Source BTS Configuration

Target BTS Configuration


MS Type

Ho Type

1. 10.2 and 4.75

4 Omni Hybrid-BB2F

4 Omni Hybrid-BB2F

TCHD / AFS

Non-RSC

Intra BSC

2. 12.2 and 5.15

4 Omni Hybrid-BB2F, EDGE TRXs


TCHF / AFS

RSC

Inter BSC

3. 6.7 and 4.75 4 Omni Hybrid-BB2F, EDGE TRXs


TCHH / AHS

Non-RSC

Inter BSC

4. 10.2 and 5.15

4 Omni EDGE 4 Omni EDGE TCHF / AFS

RSC

Intra BSC

5 10.2 and 5.901

Hybrid configuration

4 Omni EDGE-BB2E

TCHF / AFS

RSC

Intra BSC

1 Use 7390 and 6220 MS, UL DTX is OFF Ensure that voice quality is good. Also listen to speech and verify that there is no distortion. 28.7 Feature Control - Downlink FACCH Repetition with Synchronous Handover

Purpose: To ensure that the LAPDm Response frames in case of Inter-cell synchronous handover on downlink FACCH get repeated whenever downlink FACCH Repetition criteria are met.


Signal generator, Abis Interface monitoring tool, Air i/f monitoring tool.



Define a neighbour (on the same BCF) using the MML command: ZEAC:BTS=<bts num>::ABTS=<bts num>::SYNC=Y,;


Define ARLT=64 at source and target BTSs using the MML command: ZEQY:BTS=<bts num>:ARLT=64;

ARLT=64 is set.

Lock the TSs on the source and the target BTSs such that only TS7 of the BCCH TRX on each cell remains unlocked.

The TSs are locked successfully.

DN0694168 Issue 2-0


Input Expected Output Make a speech call in the source BTS and terminate it in a separate test cell. The call type is as defined in the test case. Monitor the Abis i/f.

‘FACCH Repeat’ is enabled in the ‘ACCH control IE’ of the Channel Activation message. Call is successful

At the target BTS set C/I conditions in downlink so that when call arrives at target BTS the downlink codec mode used, is the most robust codec of the ACS. Initiate inter-cell handover from source to target BTS by varying the signal level with the help of variable attenuators (set the signal level of target BTS higher than the source BTS). Monitor the Abis and Air i/f for FACCH messages.

‘FACCH Repeat’ is enabled in the ‘ACCH control IE’ of the Channel Activation message at the target BTS. For AMR/FR Call: All DL response frames on FACCH are repeated if CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. No repetition will be seen if the most robust codec is any codec other than 4.75, 5.15 or 5.90 kbps or if CMR sent is for a codec mode other than the most robust codec. For AMR/HR Call: Only the DL UA response frames on FACCH get repeated, if CMR is 4.75 kbps. No repetition will be seen if the most robust codec is any codec other than 4.75 kbps or if CMR sent is for a codec mode other than the most robust codec. Call is successfully handed over.

Disconnect the call. Call is disconnected. Case Ref ACS having

most robust codec as

Source BTS Configuration

Target BTS Configuration


1. 12.2 and 5.15

4 Omni EDGE–BB2E

4 Omni EDGE–BB2E

TCHF / AFS

2. 7.4 and 4.75 4 Omni EDGE-BB2F

4 Omni EDGE-BB2F

TCHD / AHS

3. 7.4 and 4.75 4 Omni EDGE 4 Omni EDGE TCHD / AHS 28.8 Downlink Message Transmission on SACCH

Purpose:

To ensure that when downlink SACCH repetition is in effect, each SI message from the normal schedule of the SI messages on the downlink SACCH is repeated exactly once in the very next SACCH period of it’s occurrence.



DN0694168 Issue 2-0





‘SACCH Repeat’ is enabled in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages. Call is successful.

Monitor the Air i/f. The scheduling of SI messages on the downlink SACCH is like SI 5, SI 6, SI 5, SI 6, SI 5, SI 6, …….

Add interference on Air i/f in the direction as mentioned in the test case and start increasing it slowly until the repetition starts. Monitor the Air i/f.

For interference added in downlink: The MS, being unable to decode the downlink SACCH, sets the SACCH Repeat Request (SRR) to 1 and sends it to the BTS in the L1 header of the uplink SACCH. The SI message on downlink SACCH gets repeated and the scheduling of SI messages on the downlink SACCH becomes SI 5, SI 5, SI 6, SI 6, SI 5, SI 5, SI 6, SI 6, ……. For interference added in uplink: The BTS, being unable to decode the uplink SACCH, sets SACCH Repeat Order (SRO) to 1 and send it to the MS in the L1 header of the downlink SACCH. The SI message on downlink SACCH gets repeated and the scheduling of SI messages on the downlink SACCH becomes SI 5, SI 5, SI 6, SI 6, SI 5, SI 5, SI 6, SI 6, …….

Remove the interference and monitor the Air i/f. The repetition of SI messages is stopped. Create more than 16 neighbours to the BTS under test.

The scheduling of SI messages on the downlink SACCH is in the following manner:……., SI 5, SI 6, SI 5bis, SI 6, SI 5, SI 6, SI 5, SI 6, SI 5bis, SI 6, SI 5, SI 6,….


For interference added in downlink: The MS, being unable to decode the downlink SACCH, sets the SACCH Repeat Request (SRR) to 1 and sends it to the BTS in the L1 header of the uplink SACCH. The SI message on downlink SACCH gets repeated and the scheduling of SI messages on the downlink SACCH becomes ….,SI 5, SI 5, SI 6, SI 6, SI 5bis, SI 5bis, SI 6, SI 6, SI 5, SI 5, SI 6, SI 6,SI 5, SI 5, SI 6, SI 6, SI 5bis, SI 5bis, SI 6, SI 6, SI 5, SI 5, SI 6, SI 6, …. For interference added in uplink: The BTS, being unable to decode the uplink SACCH, sets SACCH Repeat Order (SRO) to 1 and send it to the MS in the L1 header of the downlink SACCH. The SI message on downlink SACCH gets repeated and the scheduling of SI messages on the downlink SACCH becomes …….,SI 5, SI 5, SI 6, SI 6, SI 5bis, SI 5bis, SI 6, SI 6, SI 5, SI 5, SI 6, SI 6, SI 5, SI 5, SI 6, SI 6, SI 5bis, SI 5bis, SI 6, SI 6, SI 5, SI 5, SI 6, SI 6, ….

DN0694168 Issue 2-0


Input Expected Output Remove the interference and delete all neighbours. Monitor the Air i/f.

The repetition of SI messages is stopped. The occurrence of SI 5bis is stopped.

Terminate the speech call. The speech call is terminated. Create neighbours of 1800 band to the BTS under test and again start a speech call as specified in the test case and monitor the Abis i/f and Air i/f.

‘SACCH Repeat’ is enabled in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages on Abis i/f. Call is successful. . The scheduling of SI messages on the downlink SACCH is in the following manner: …, SI 5, SI 6, SI 5ter, SI 6, SI 5, SI 6, SI 5, SI 6, SI 5ter, SI 6, SI 5, SI 6,….


For interference added in downlink: The MS, being unable to decode the downlink SACCH, sets the SACCH Repeat Request (SRR) to 1 and sends it to the BTS in the L1 header of the uplink SACCH. The SI message on downlink SACCH gets repeated and the scheduling of SI messages on the downlink SACCH becomes …., SI 5, SI 5, SI 6, SI 6, SI 5ter, SI 5ter, SI 6, SI 6, SI 5, SI 5, SI 6, SI 6, SI 5, SI 5, SI 6, SI 6, SI 5ter, SI 5ter, SI 6, SI 6, SI 5, SI 5, SI 6, SI 6, …. For interference added in uplink: The BTS, being unable to decode the uplink SACCH, sets SACCH Repeat Order (SRO) to 1 and send it to the MS in the L1 header of the downlink SACCH. The SI message on downlink SACCH gets repeated and the scheduling of SI messages on the downlink SACCH becomes ….,SI 5, SI 5, SI 6, SI 6, SI 5ter, SI 5ter, SI 6, SI 6, SI 5, SI 5, SI 6, SI 6, SI 5, SI 5, SI 6, SI 6, SI 5ter, SI 5ter, SI 6, SI 6, SI 5, SI 5, SI 6, SI 6, ….

Remove the interference. Monitor the Air i/f.

The repetition of SI messages is stopped.

Create more than 16 neighbours (comprising neighbours of primary 900 band and extended 900 band) additional to previously created neighbours to the BTS under test.

The scheduling of SI messages on the downlink SACCH is in the following manner : SI 5, SI 6, SI 5bis, SI 6, SI 5ter, SI 6, SI 5, SI 6, SI 5bis, SI 6, SI 5ter, SI 6, SI 5, SI 6,….

DN0694168 Issue 2-0


Input Expected Output Add interference on Air i/f in the direction as mentioned in the test case and start increasing it slowly until the repetition starts. Monitor the Air i/f.

For interference added in downlink: The MS, being unable to decode the downlink SACCH, sets the SACCH Repeat Request (SRR) to 1 and sends it to the BTS in the L1 header of the uplink SACCH. The SI messages on downlink SACCH get repeated and the scheduling of SI messages on the downlink SACCH becomes SI 5, SI 5, SI 6, SI 6, SI 5bis, SI 5bis, SI 6, SI 6, SI 5ter, SI 5ter, SI 6, SI 6, SI 5, SI 5, SI 6, SI 6, SI 5bis, SI 5bis, SI 6, SI 6, SI 5ter, SI 5ter, SI 6, SI 6, …. For interference added in uplink: The BTS, being unable to decode the uplink SACCH, sets SACCH Repeat Order (SRO) to 1 and send it to the MS in the L1 header of the downlink SACCH. The SI message on downlink SACCH gets repeated and the scheduling of SI messages on the downlink SACCH becomes SI 5, SI 5, SI 6, SI 6, SI 5bis, SI 5bis, SI 6, SI 6, SI 5ter, SI 5ter, SI 6, SI 6, SI 5, SI 5, SI 6, SI 6, SI 5bis, SI 5bis, SI 6, SI 6, SI 5ter, SI 5ter, SI 6, SI 6, ….

Remove the interference and monitor the Air i/f. The repetition of SI messages is stopped. Terminate the speech call. The speech call is terminated. Case Ref. Configuration Call Type Interference 1. 4 Omni EDGE (E-GSM900) AFS DL 2. 4 Omni EDGE (E-GSM900) AHS UL

28.9 UL DTX estimation and estimation validity

Purpose:

To ensure that the EDGE BTS does the estimation of UL DTX as well the validation of this estimation all the time during the call and reports these values in the ‘DTXu-est’ and ‘DTXu-valid’ fields respectively in the Uplink Measurement IE of Measurement Result message on Abis i/f.

Note 217. For DTXu_est =0, the BTS does estimate that the DTX is not used.

For DTXu_est =1, the BTS does estimate that the DTX is used.

For DTXu_valid =0, the BTS has not estimated uplink DTX usage.

For DTXu_valid =1, the estimation is valid.

Note 218. It is essential to have exactly same (synchronized) ‘Time Stamp’ on both Air interface monitoring tool and the Abis interface monitoring tool in order to compare messages in SACCH periods on Air and Abis interface.

DN0694168 Issue 2-0






Disable ‘FACCH and SACCH repetition for repeated ACCH capable mobiles on AMR’ from BSC.

‘FACCH and SACCH repetition for repeated ACCH capable mobiles on AMR’ is disabled.

Set DTX mode as mentioned in the test case with the help of MML command: ZEQM:BTS=<bts num>:DTX=<x>;

DTX mode is set.


‘SACCH Repeat’ is disabled in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages The call is successful.

Monitor the call for about 20 seconds and introduce both silent periods (no speech over the phone) as well as active periods (speech is present over the phone) in the UL during the call.

Call remains connected.

Monitor the Air i/f for ‘Measurement Report’ message and the Abis interface for ‘Uplink Measurement’ IE of ‘Measurement Result’ message for the period mentioned in the above step.

For DTX ‘ON’: If the ‘Measurement Report’ on uplink SACCH contains the ‘DTX USED’ field with value 0, the corresponding values of DTXu_est and DTXu_valid in ‘Uplink Measurement’ IE of ‘Measurement Result’ message on Abis i/f are 0 and 1 respectively [Note 217] If the ‘Measurement Report’ on uplink SACCH contains the ‘DTX USED’ field with value 1, the corresponding values of DTXu_est and DTXu_valid in ‘Uplink Measurement’ IE of ‘Measurement Result’ message on Abis i/f are 1 and 1 respectively [Note 217]. For DTX ‘OFF’: The ‘Measurement Report’ on uplink SACCH contains the ‘DTX USED’ field with value 0 and the corresponding values of DTXu_est and DTXu_valid in ‘Uplink Measurement’ IE of ‘Measurement Result’ message on Abis i/f are 0 and 0 respectively [Note 217].

Terminate the speech call. The speech call is terminated. Case Ref. Configuration Call Type UL DTX 1. 4 Omni Hybrid AFS ON 2. 4 Omni EDGE AHS OFF 3 4 Omni EDGE AFS ON

DN0694168 Issue 2-0


28.10 ASI Statistics - ASI Statistics for DL SACCH Repetition

Purpose: To ensure that there is a correct correlation between the DL_SRR parameter in AMR Signalling Data IE(s) of the Measurement Result message on Abis i/f and in the messages on the UL SACCH on Air i/f. And also to ensure that the DL_SRS parameter in AMR Signalling Data IE(s) of the Measurement Result message on Abis i/f conforms to the sequence of the messages in DL SACCH on Air i/f.

Note 219. In case averaging is used, i.e., BMA =2,3,or 4, then ‘AMR Signalling Data IE’ will contain as many entries in Measurement Result => Uplink Measurements => Supplementary Measurement Information => AMR Signalling Data IE as the number of SACCH periods covered by the averaging; if more than one they shall be presented in descending age order (i.e. oldest first).

Note 220. For, m=1; p=0

For, m=2; p=0,1

For, m=3; p=0,1,2

For, m=4; p=0,1,2,3

Where, ‘m’ is the BMA value and the total count of values of ‘p’ is the number of SACCH periods included in averaging.

Note 221. All test cases need to be executed with RSC mobiles.

Note 222. It is essential to have exactly same (synchronized) ‘Time Stamp’ on both Air interface monitoring tool and the Abis interface monitoring tool in order to compare messages in SACCH periods on Air and Abis interface.




Create a site with the configuration as mentioned in the test case.


Set the BMA value as given in the test case with the help of MML command: ZEQM:BTS=<bts num>:BMA=<x>;

BMA value is set.


‘SACCH Repeat’ is enabled in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages on the Abis i/f. Call is successful.

DN0694168 Issue 2-0



Add interference on Air i/f in the downlink direction and start increasing it slowly until the repetition starts. Monitor the Air i/f messages.

The MS, being unable to decode the downlink SACCH, sets the SACCH Repeat Request (SRR) to 1 and sends it to the BTS in the L1 header of the uplink SACCH on Air i/f. The SI messages on downlink SACCH get repeated exactly once in the SACCH period next to the SACCH period in which the SRR=1 is received by the BTS

Monitor the Abis i/f for ‘Measurement Result’ message.

DL_SRR and DL_SRS fields can be seen in the ‘AMR Signalling Data IE’ of ‘Supplementary Info’ in ‘Uplink Measurement’ of ‘Measurement Result’ message.

Compare the value of SRR bit in uplink SACCH message on Air i/f with the value of DL_SRR field of ‘AMR Signalling Data IE’. on Abis i/f.

The value(s) of SRR bit set on the uplink SACCH in the (n+p)th SACCH period(s) is(are) in compliance with the corresponding value(s) of DL_SRR in ‘AMR Signalling Date IE’ of ‘Supplementary Info’ in ‘Uplink Measurement’ of ‘Measurement Result’ message in the (n+m)th SACCH period.

Check the value of DL_SRS field of ‘AMR Signalling Data IE’ on Abis i/f and correlate it with the repetition of downlink SACCH.

If the downlink SACCH is sent in (n+p)th SACCH period(s), the corresponding value(s) of DL_SRS will be sent in ‘AMR Signalling Date IE’ of ‘Supplementary Info’ in ‘Uplink Measurement’ of ‘Measurement Result’ message sent in (n+m)th SACCH period. If the downlink SACCH is a repetition, the corresponding value of DL_SRS is set to 1 otherwise it is set to 0

Terminate the speech call. The speech call is terminated.

Case Ref. Configuration Call Type BMA

1. 4 Omni EDGE AFS 1

2. 4 Omni EDGE AHS 2

28.11 ASI Statistics - ASI Statistics for UL SACCH Repetition

Purpose: To ensure that there is a correct correlation between the UL_SRO parameter in AMR Signalling Data IE(s) of the Measurement Result message on Abis i/f and in the messages on the DL SACCH on Air i/f and, also to ensure whether the BTS is performing soft combining to recover the reported SACCH message.



DN0694168 Issue 2-0





Set ARLT=64 with the help of MML command: ZEQY:BTS=<bts num>:ARLT=64;

ARLT is set to 64.

Set the BMA value as given in the test case with the help of MML command: ZEQM:BTS=<bts num>:BMA=<x>;

BMA value is set.


‘SACCH Repeat’ is enabled in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages on the Abis i/f. Call is successful.

Add interference on Air i/f in the uplink direction and start increasing it slowly until the repetition starts. Analyse the Air i/f messages.

The BTS, being unable to decode the uplink SACCH, sets SACCH Repeat Order (SRO) to 1 and send it to the MS in the L1 header of downlink SACCH. The SI message on downlink SACCH gets repeated exactly once in the SACCH period next to the SACCH period in which the SR0=1 is sent by the BTS

Monitor the Abis i/f to see the ‘AMR Signalling Date IE’ of ‘Supplementary Info’ in ‘Uplink Measurement’ of ‘Measurement Result’ message.

UL_SRO and ULSC fields can be seen in the ‘AMR Signalling Data IE’ of ‘Supplementary Info’ in ‘Uplink Measurement’ of ‘Measurement Result’ message.

Compare the value of SRO bit in downlink SACCH message on Air i/f with the value of UL_SRO field of ‘AMR Signalling Data IE’. on Abis i/f.

The value(s) of SRO bit set on the downlink SACCH in the (n+p)th SACCH period(s) is(are) in compliance with the corresponding value(s) of UL_SRO in ‘AMR Signalling Date IE’ of ‘Supplementary Info’ in ‘Uplink Measurement’ of ‘Measurement Result’ message in the (n+m)th SACCH period.

Check the value of ULSC field of ‘AMR Signalling Data IE’ of ‘Supplementary Info’ on Abis i/f correlate it with the soft combining done by the BTS.

If the soft combining is done in (n+p)th SACCH period(s), the corresponding value(s) of ULSC will be sent in ‘AMR Signalling Date IE’ of ‘Supplementary Info’ in ‘Uplink Measurement’ of ‘Measurement Result’ message sent in (n+m)th SACCH period. If the BTS has performed soft combining, the corresponding value of ULSC is set to 1 otherwise it is set to 0.


Case Ref. Base Station Configuration

Call Type BMA

1. UltraSite 4 Omni EDGE

AFS 4

2. MetroSite 4 Omni EDGE

AHS 3

28.12 ASI Statistics - ASI Statistics for DL FACCH Repetition

Purpose: To ensure that there is a correct correlation between the FF_rep & FF_non_rep parameters in AMR Signalling Data IE(s) of the Measurement Result

DN0694168 Issue 2-0


message on Abis i/f and in the messages on the DL FACCH frames on Air i/f when DL FACCH Repeat is in effect and also when DL FACCH Repeat is disabled.

Note 223. All test cases need to be executed with RSC mobiles. To check ASI statistics when DL FACCH Repeat is disabled, all ASI features other than ‘FACCH and SACCH repetition for repeated ACCH capable mobiles on AMR’ are enabled at BSC.

Note 224. In case averaging is used, i.e., BMA =2,3,or 4, then ‘AMR Signalling Data IE’ will contain as many entries in Measurement Result => Uplink Measurements => Supplementary Measurement Information => AMR Signalling Data IE as the number of SACCH periods covered by the averaging; if more than one they shall be presented in descending age order (i.e. oldest first).

Note 225. For, m=1; p=0

For, m=2; p=0,1

For, m=3; p=0,1,2

For, m=4; p=0,1,2,3

Where, ‘m’ is the BMA value and the total count of values of ‘p’ is the number of SACCH periods included in averaging.


Signal generator, Abis monitoring tool, Air i/f monitoring tool.




Disable intra-cell handovers at the BTS under test using the MML command: ZEHG:BTS=<bts num>:EIC=N,EIH=N;


Set the BMA value as given in the test case at the BTS using the MML command: ZEQM:BTS=<bts num>:BMA=<x>;

BMA value is set.

Make a speech call and terminate it in a separate test cell. The call type is as defined in the test case.




DN0694168 Issue 2-0



Now add interference [Note 210] in uplink to the BTS and start sending DTMF messages to generate FACCH traffic by pressing the keys on keypad of the MS. The T200 F timer gets expired. (About 30 DTMF messages should be enough). Monitor the Abis and Air i/f for FACCH messages.

RR response frame and ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’ message encapsulated in DL I-frame will appear on DL FACCH. For AMR/FR Call: The transmissions of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) as well as its retransmission, after T200 F expiry, gets repeated on Air i/f, if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. Also the RR response frame gets repeated on DL FACCH if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. No repetition will be seen if the most robust codec is any codec other than 4.75, 5.15 or 5.90 kbps or if CMR sent is for a codec mode other than the most robust codec. For AMR/HR Call: Only the retransmission of DL I-CMD frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) after T200 F expiry gets repeated on Air i/f, if the CMR is 4.75 kbps. No repetition will be seen if the most robust codec is any codec other than 4.75 kbps or if CMR sent is for a codec mode other than the most robust codec. Also the RR response frame does not get repeated on DL FACCH even if the CMR is 4.75 kbps and is the most robust codec of the ACS.

Monitor the Abis i/f for ‘Measurement Result’ message at target BTS.

FF_non_rep and FF_rep fields can be seen in the ‘AMR Signalling Data IE’ of ‘Supplementary Info’ in ‘Uplink Measurement’ of ‘Measurement Result’ message.

Compare the values in FF_non_rep and FF_rep field of ‘AMR Signalling Data IE’ in the ‘Supplementary Info’ on Abis i/f with the number of DL FACCH blocks (excluding repetitions) and repeated DL FACCH blocks sent on Air i/f respectively at the source BTS.

The number of DL FACCH blocks (excluding repetitions) and repeated DL FACCH blocks sent on Air i/f in the (n+p)th SACCH period(s) is(are) in compliance with the corresponding value(s) in FF_non_rep and FF_rep field of ‘AMR Signalling Data IE’ of ‘Supplementary Info’ in ‘Uplink Measurement’ of ‘Measurement Result’ message in the (n+m)th SACCH period.

Disconnect the call. Call is disconnected. Disable ‘FACCH and SACCH repetition for repeated ACCH capable mobiles on AMR’ at BSC]. Again make a speech call and terminate it in a separate test cell. The call type is as defined in the test case.

‘FACCH Repeat’ is disabled in the ‘ACCH control IE’ of the Channel Activation message. Call is successful.

DN0694168 Issue 2-0






RR response frame and ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’ message encapsulated in DL I-frame will appear on DL FACCH. For AMR/FR Call: The transmissions of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) as well as its retransmission, after T200 F expiry, gets repeated on Air i/f, if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. No repetition will be seen if the most robust codec is any codec other than 4.75, 5.15 or 5.90 kbps or if CMR sent is for a codec mode other than the most robust codec. Also the RR response frame get repeated on DL FACCH if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. For AMR/HR Call: Only the retransmission of DL I-CMD frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) after T200 F expiry gets repeated on Air i/f, if the CMR is 4.75 kbps. No repetition will be seen if the most robust codec is any codec other than 4.75 kbps or if CMR sent is for a codec mode other than the most robust codec. Also the RR response frame do not get repeated on DL FACCH even if the CMR is 4.75 kbps and is the most robust codec of the ACS. The transmissions of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) as well as its retransmission, after T200 F expiry, do not get repeated on Air i/f, even if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. Also the DL RR Response frames do not get repeated on Air i/f, even if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS.

DN0694168 Issue 2-0



Monitor the Abis i/f for ‘Measurement Result’ message at target BTS. Compare the values in FF_non_rep and FF_rep field of ‘AMR Signalling Data IE’ on Abis i/f with the number of DL FACCH blocks (excluding repetitions) and repeated DL FACCH blocks sent on Air i/f respectively at the source BTS.

The number of DL FACCH blocks sent on Air i/f in the (n+p)th SACCH period(s) is (are) in compliance with the corresponding value(s) in FF_non_rep of ‘AMR Signalling Data IE’ of ‘Supplementary Info’ in ‘Uplink Measurement’ of ‘Measurement Result’ message in the (n+m)th SACCH period. There should be none in the FF_rep of ‘AMR Signalling Data IE’ of ‘Supplementary Info’ as DL FACCH block do not get repeated.

Disconnect the call. Call is disconnected.

Case Ref. BTS Configuration ACS Channel Configuration / Speech Codec

BMA

1. 4 Omni EDGE

7.40 and 4.75 TCHH / AHS 1

2. 4 Omni EDGE

12.2 and 4.75 TCHF / AFS 2

28.13 Non-Repetition of FACCH and SAACH - No Downlink FACCH Repetition with AMR disabled

Note 226. Set the MS maximum transmit power using MML command: ZEQM:BTS=<bts num>:PMAX1=5,PMAX2=6;





Define neighbour using the MML command: ZEAC:BTS=<bts num>::ABTS=<bts num>;


Disable intra-cell handovers at source BTS using the MML command: ZEHG:BTS=<bts num>:EIC=N,EIH=N;


Disable AMR calls at source and target BTSs using the MML command: ZEQY:BTS=<bts num>:FRC=0,HRC=0:;

AMR calls are disabled in the BTS.

DN0694168 Issue 2-0


Input Expected Output Define RLT=64 at source and target BTSs using the MML command: ZEQG:BTS=<bts num>:RLT=64,;

RLT set to 64.

Make a speech call in the source BTS and terminate it in a separate test cell. The call type and MS type are as defined in the test case. Monitor the Abis i/f.

‘ACCH control IE’ is not present in the Channel Activation message. Call is successful.

Lock all the traffic channels at target BTS using MML command: ZERS:BTS=<bts num>,TRX=<trx num>,CH=0&&7,:L;

All the traffic channels at target BTS get locked.


‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’ message encapsulated in DL I-frame will appear on DL FACCH. The transmissions of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) as well as its retransmission after T200 F expiry do not get repeated on Air i/f.

Disconnect the call. Call is disconnected. Unlock one traffic channel at target BTS using MML command: ZERS:BTS=<bts num>,TRX=<trx num>,CH=<channel num>,:U;

One traffic channel at target BTS get unlocked.

Remove all interference sources from the source BTS. Then again make a speech call in the source BTS and terminate it in a separate test cell. The call type and MS type are as defined in the test case. Monitor the Abis i/f.

‘ACCH control IE’ is not present in the Channel Activation message. Call is successful.

At the target BTS, add interference with C/I~1-3 in uplink direction. Initiate handover from source to target BTS as mentioned in the test case by varying the signal level with the help of variable attenuators (set the signal level of target BTS higher than the source BTS). Monitor the Abis and Air i/f for FACCH messages.

‘ACCH control IE’ is not present in the Channel Activation message at target BTS on Abis Interface. The target BTS sends DL response frames and PHYSICAL INFORMATION encapsulated in DL UI-frame on FACCH to the MS. The re-transmission of DL UI-frame (carrying only PHYSICAL INFORMATION) due to expiry of T3105 timer do not get repeated on Air i/f. Also any DL response frames on FACCH should not be repeated. Call is successfully handed over

Disconnect the call. Call is disconnected. Case Ref Source BTS Target BTS Channel

Configuration / Speech Codec

MS Type

1. 4 Omni EDGE 4 Omni EDGE TCHF / EFR Non-RSC

2. 4 Omni EDGE 4 Omni EDGE TCHH / HR RSC

DN0694168 Issue 2-0


28.14 ASI with DFCA - SACCH Repetition with DFCA

Purpose: To ensure that the SACCH messages for a cell with DFCA enabled get repeated when the Repeat SACCH Criteria are met.

Note 227. All test cases need to be done with SACCH Repeat Window set as 15 unless otherwise stated. Its value can be set using MML command ZEEQ.

Note 228. For, SACCH Repeat Window = 15, SRO bit is set if 2 of the 15 preceding SACCH block single decodes fail.

Note 229. All test cases need to be done with ARLT set as 64 unless otherwise stated. Its value can be set using MML command ZEQY. Equipment and BTS Set-Up Sites - as per configuration defined in test case.

Signal generator, Spectrum Analyser, Abis monitoring tool, Air i/f monitoring tool

Input Expected Output Create a site with DFCA configured as mentioned in the test case.


Start a speech call on the TRX as specified in the test case and monitor the Abis i/f.

‘SACCH Repeat = Enabled’ and ‘SACCH Repeat Window (SRW)’ are present in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages. Call is successful.


Add interference on Air i/f in the downlink direction and start increasing it slowly until the repetition starts. Analyse the Air i/f messages.

The MS, being unable to decode the downlink SACCH, sets the SACCH Repeat Request (SRR) to 1 and sends it to the BTS in the L1 header of the uplink SACCH. The SI message on downlink SACCH gets repeated exactly once in the SACCH period next to the SACCH period in which the SRR=1 is received by the BTS

Remove the interference and terminate the call.

The call is terminated.

DN0694168 Issue 2-0


Input Expected Output Start a speech call on the TRX as specified in the test case and monitor the Abis i/f.



The BTS, being unable to decode the uplink SACCH, sets SACCH Repeat Order (SRO) to 1 and send it to the MS in the L1 header of the downlink SACCH [Note 228]. The SI message on downlink SACCH gets repeated exactly once in the SACCH period next to the SACCH period in which the SRO=1 is sent by the BTS.



Monitor the Air i/f. The SMS segment is sent only once on the downlink SACCH.

Monitor the screen of the MS latched on to the BTS under test.


Terminate the speech call. The speech call is terminated. Case Ref. BTS Configuration/Site Type TRX Type 1. 4 Omni EDGE [1x BCCH + 1x non DFCA +

2x DFCA TRX] DFCA

2. 4 Omni EDGE [1x BCCH + 1x non DFCA + 2x DFCA TRX]

Non-DFCA

28.15 ASI with DFCA - Downlink FACCH Repetition with DFCA

Purpose:

To ensure that the DL FACCH messages for a cell with DFCA enabled get repeated when the Repeat FACCH Criteria are met.

Note 230. Set the MS maximum transmit power using MML command: EQM:BTS=<bts num>:PMAX1=5,PMAX2=6;



DN0694168 Issue 2-0




Define ARLT=64 at the BTS under test using the MML command: EQY:BTS=<bts num>:ARLT=64;

ARLT=64 is set.



Lock all the TCHs except one on the TRX as stated in the test case.

Only one TCH on the TRX stated in the test case is unlocked.

Make a speech call on the TRX as specified in the test case and terminate it in a separate test cell. The call type and MS type are as defined in the test case. Monitor the Abis i/f

Call is successful. ‘FACCH Repeat’ is enabled in the ‘ACCH control IE’ of the Channel Activation message.

During the AMR call, C/I conditions are gradually changed in downlink at the BTS to manipulate the air interface so that the downlink codec mode changes and reaches the most robust codec of the ACS.


Now add interference [Note 210] in uplink to the BTS and Start sending DTMF messages to generate FACCH traffic by pressing the keys on keypad of the MS. The T200 F timer gets expired. (About 30 DTMF messages should be enough). Monitor the Abis and Air i/f for FACCH messages.

RR response frame and ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’ message encapsulated in DL I-frame will appear on DL FACCH. For AMR/FR Call: The transmissions of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) as well as its retransmission, after T200 F expiry, gets repeated on Air i/f, if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. The RR response frames on DL FACCH are also repeated if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. For AMR/HR: Only the retransmission of DL I-CMD frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) after T200 F expiry gets repeated on Air i/f, if the CMR is 4.75 kbps.

Remove all the source of interference and disconnect the call.

Call is disconnected.

Case Ref ACS BTS Configuration MS Type


Call on the TRX

1. 4.75, 10.2 and 12.2

4 Omni EDGE [1x BCCH + 1x non DFCA + 2x DFCA TRX]

RSC TCHD / AFS Non-DFCA

2. 4.75 and 7.40

4 Omni EDGE [1x BCCH + 1x non DFCA + 2x DFCA TRX]

RSC TCHH / AHS Non-DFCA

DN0694168 Issue 2-0


28.16 ASI with DFCA - Uplink DTX estimation and estimation validity with DFCA

Purpose:

To ensure that the ASI capable BTS [Note 234] with DFCA enabled does the estimation of UL DTX as well the validation of this estimation all the time during the call and reports these values in the ‘DTXu-est’ and ‘DTXu-valid’ fields respectively in the Uplink Measurement IE of Measurement Result message on Abis i/f.





Note 232. It is essential to have exactly same (synchronized) ‘Time Stamp’ on both Air interface monitoring tool and the Abis interface-monitoring tool in order to compare messages in SACCH periods on Air and Abis interface.

Note 233. All the test cases need to be executed with uplink DTX set to ‘ON’.

Note 234. For Ultrasite: - ASI capable BTS consists of any TRX (EDGE or GSM) configured only with EDGE BB card.

For MetroSite: - ASI capable BTS is one that consists of only EDGE TRX(s).






‘SACCH Repeat’ is enabled in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages The call is successful.

Monitor the call for about one minute and introduce both silent periods (no speech over the phone) as well as active periods (speech is present over the phone) in the UL during the call.


DN0694168 Issue 2-0


Input Expected Output Monitor the Air i/f for ‘Measurement Report’ message and the Abis interface for ‘Uplink Measurement’ IE of ‘Measurement Result’ message for the period mentioned in the above step.

If the ‘Measurement Report’ on uplink SACCH contains the ‘DTX USED’ field with value 0, the corresponding values of DTXu_est and DTXu_valid in ‘Uplink Measurement’ IE of ‘Measurement Result’ message on Abis i/f are 0 and 1 respectively [Note 231]. If the ‘Measurement Report’ on uplink SACCH contains the ‘DTX USED’ field with value 1, the corresponding values of DTXu_est and DTXu_valid in ‘Uplink Measurement’ IE of ‘Measurement Result’ message on Abis i/f are 1 and 1 respectively [Note 231].

Terminate the speech call. The speech call is terminated. Case Ref. Configuration Call on the TRX 1. 4 Omni EDGE [1x BCCH + 1x non DFCA + 2x DFCA TRX] DFCA

28.17 ASI with IDD/4UD - SACCH Repetition with IDD/4UD

Purpose: To ensure that the SACCH messages for a cell with IDD/4UD enabled get repeated when the Repeat SACCH Criteria are met.



Note 237. All test cases need to be done with ARLT set as 64 unless otherwise stated. Its value can be set using MML command ZEQY.

Note 238. In IDD cell coverage area is extended by sending simultaneously the same downlink signal through minimum of two transmitters, with slight delay. Two antennas (or X-polarised antenna) are needed for one cell.


DN0694168 Issue 2-0


Note 240. The Abis transmission has to be defined only to TRXs defined at the BSC. Signalling and traffic timeslots are branched only to IDD main TRXs and normal TRXs. This has to be done manually by BTS Manager or automatically by the Auto configuration. Auto configuration has knowledge, which TRXs are auxiliary TRXs.



Input Expected Output Create a site with IDD/4UD configured as mentioned in the test case.







Remove the interference and terminate the call. The call is terminated. Start a speech call on the TRX as specified in the test case and monitor the Abis i/f.




DN0694168 Issue 2-0


Input Expected Output Send an SMS to the MS latched on to the BTS under test.





Terminate the speech call. The speech call is terminated. Case Ref. BTS Configuration TRX Type 1. 3 Omni IDD/Normal with 4UD (2*(main+aux)+1*Normal

TRX) IDD

28.18 ASI with IDD/4UD - Downlink FACCH Repetition with IDD/4UD

Purpose:

To ensure that the DL FACCH messages for a cell with IDD/4UD enabled get repeated when the Repeat FACCH Criteria are met.

Note 241. The term “High Interference” used in Test cases means that MS/BTS is not able to decode the SACCH messages in DL/UL direction e.g. Interference greater than Signal level. This would imply that MS/BTS would not be able to decode FACCH message also.





DN0694168 Issue 2-0







ARLT=64 is set.



Lock all the TCHs except one on the TRX as stated in the test case.

Only one TCH on the TRX stated in the test case is unlocked.

Make a speech call on the TRX as specified in the test case and terminate it in a separate test cell. The call type and MS type are as defined in the test case. Monitor the Abis i/f


During the AMR call, C/I conditions are gradually changed in downlink at the BTS to manipulate the air interface so that the downlink codec mode changes and reaches to the most robust codec of the ACS.


Now add interference [Note 210] in uplink to the BTS and Start sending DTMF messages to generate FACCH traffic by pressing the keys on keypad of the MS. The T200 F timer gets expired. (About 30 DTMF messages should be enough). Monitor the Abis and Air i/f for FACCH messages.

‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’ message encapsulated in DL I-frame will appear on DL FACCH. For AMR/FR Call: The transmissions of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) as well as its retransmission, after T200 F expiry, gets repeated on Air i/f, if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. Also, DL RR Response frames are repeated, if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. For AMR/HR: Only the retransmission of DL I-CMD frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) after T200 F expiry gets repeated on Air i/f, if the CMR is 4.75 kbps.

Terminate the speech call. The speech Call is terminated. Case Ref ACS BTS Configuration Channel


TRX

1. 5.90 and 12.2

3 Omni IDD/Normal with 4UD (2*(main+aux)+1*Normal TRX)

TCHF / AFS IDD

2. 4.75 and 7.40

3 Omni IDD/Normal with 4UD (2*(main+aux)+1*Normal TRX)

TCHH / AHS Normal

DN0694168 Issue 2-0


28.19 ASI with IDD/4UD - UL DTX estimation and estimation validity with IDD/4UD

Purpose:

To ensure that the ASI capable BTS [Note 248] with IDD/4UD enabled does the estimation of UL DTX as well as the validation of this estimation all the time during the call and reports these values in the ‘DTXu_est’ and ‘DTXu_valid’ fields respectively in the Uplink Measurement IE of Measurement Result message on Abis i/f.






Note 248. ASI capable BTS consists of any TRX (EDGE or GSM) configured only with EDGE BB card.






DN0694168 Issue 2-0




Set DTX to ‘ON’ using the MML command: ZEQM:BTS=<bts num>:DTX=<1>;

DTX mode is set.







Terminate the speech call. The speech call is terminated. Case Ref. Configuration TRX 1.

3 Omni IDD/Normal with 4UD (2*(main+aux)+1*Normal TRX) IDD

28.20 ASI with E-Cell - SACCH Repetition with E-Cell

Purpose: To ensure that the SACCH messages for a cell with E-TRXs get repeated when the Repeat SACCH Criteria are met




Note 255.

DN0694168 Issue 2-0


RF TA rig is a set up of equipment that allows signal delay on the air interface so that distance can be simulated.

Note 256. This test case with call on E-TRX must be performed in a screened environment.


Signal generator, Spectrum Analyser, Abis monitoring tool, Air i/f monitoring tool, RF TA Rig.

Input Expected Output Set up a site as per test case. Set the radius extension to 35 km. Note that BTS and TRXs must be in locked administrative state in order to activate the E-Cell feature. ZEQM:BTS=<nr>:EXT=35; ZERM:BTS=<bts nr>,TRX=<bcch trxnr>:CH0=MBCCH,CH1=NOTUSED,CH2=SDCCH; ZERM:BTS=<bts nr>,TRX=<trx nr>:ETRX=E,CH0=ERACH,CH1=SDCCH;

Site comes up to working state. Listing with command ZEEI:BCF=<bcf nr>; displays that site, BTS and TRXs in WO state. The E-TRXs are shown as such and one of them has ERACH configured to it.

Set up the RF TA rig [Note 255] and connect the MS to it so that the distance of the MS from the BTS varies throughout the range of the Normal Cell and Extended Cell.









DN0694168 Issue 2-0











Terminate the speech call. The speech call is terminated. Case Ref. BTS Configuration TRX 1. E-Cell Standard configuration Extended

28.21 ASI with E-Cell - Downlink FACCH Repetition with E-Cell

Purpose: To ensure that the DL FACCH messages for a moving MS in a cell with E-TRXs get repeated when the Repeat FACCH Criteria are met

Note 257. Set the MS maximum transmit power using MML command:

EQM:BTS=<bts num>:PMAX1=5,PMAX2=6;

Note 258. RF TA rig is a set up of equipment that allows signal delay on the air interface so that distance can be simulated.


Equipment and BTS Set-Up Sites – As per configuration.

Variable attenuators, Spectrum Analyser, Signal Generator, Abis monitoring tool, Air interface monitoring tool, RF TA Rig.

DN0694168 Issue 2-0


Input Expected Output Set up a site as per test case. Set the radius extension to 35 km. Note that BTS and TRXs must be in locked administrative state in order to activate the E-Cell feature.


Set up the RF TA rig [Note 258] and connect the MS to it so that the distance of the MS from the BTS varies throughout the range of the Normal Cell and Extended Cell.


Define ARLT=64 using the MML command: EQY:BTS=<bts num>:ARLT=64;

ARLT=64 is set.

Lock all but one TCH on all TRX type as stated in the test case.

Only one TCH on the TRX type stated in the test case is unlocked.


‘FACCH Repeat = Enabled’ is present in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages. Call is successful.



Now add interference [Note 210][ in uplink to the TCH on which the call is going on and start sending DTMF messages to generate FACCH traffic by pressing the keys on keypad of the MS. The T200 F timer gets expired. (About 30 DTMF messages should be enough). Monitor the Abis and Air i/f for FACCH messages.

‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’ message encapsulated in DL I-frame will appear on DL FACCH. For AMR/FR Call: The transmissions of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) as well as its retransmission after T200F expiries get repeated on Air i/f, if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec (CODEC_MODE_1) of the ACS. Also, DL RR Response frames are repeated, if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. For AMR/HR Call: Only the retransmission of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) after T200F expiry gets repeated on Air i/f, if the CMR is 4.75 kbps.

Terminate the speech call. The speech call is terminated. Case Ref. Base Station/Site Type ACS TRX Call

Type HO Type

1. E-Cell Standard configuration[Note 115]

12.2, 10.2, and 4.75

Normal AFS Normal cell to Extended cell

2. E-Cell Standard configuration[Note 115]

7.40, 6.70, and 4.75

Extended

AHS Extended cell to Normal cell

DN0694168 Issue 2-0


28.22 ASI with E-Cell - UL DTX estimation and estimation validity with E-Cell

Purpose:

To ensure that the ASI capable BTS [Note 248] with E-TRXs does the estimation of UL DTX as well the validation of this estimation all the time during the call and reports these values in the ‘DTXu-est’ and ‘DTXu-valid’ fields respectively in the Uplink Measurement IE of Measurement Result message on Abis i/f.






Note 262. ASI capable BTS consists of any TRX (EDGE or GSM) configured only with EDGE BB card.

Note 263. RF TA rig is a set up of equipment that allows signal delay on the air interface so that distance can be simulated.



Signal generator, Spectrum Analyser, Abis monitoring tool, Air i/f monitoring tool, RF TA Rig.

Input Expected Output Set up a site as per test case. Set the radius extension to 35 km. Note that BTS and TRXs must be in locked administrative state in order to activate the E-Cell feature.


Set up the RF TA rig [Note 263] and connect the MS to it so that the distance of the MS from the BTS varies throughout the range of the extended radius


Set DTX to ‘ON’ using the MML command: ZEQM:BTS=<bts num>:DTX=<1>;

DTX mode is set.

DN0694168 Issue 2-0








Terminate the speech call. The speech call is terminated. Case Ref. Configuration/UltraSite TRX 1.

E-Cell Standard configuration/ UltraSite E-TRX

28.23 ASI with Early Classmark Sending - SACCH Repetition with ESI Disabled

Purpose: To ensure that when ‘Early Sending Indication’ parameter is set to ‘N’ at the BSC, the SACCH messages on Air i/f do not get repeated Note 265. All test cases need to be done with SACCH Repeat Window set as 15 unless otherwise stated. Its value can be set using MML command ZEEQ.

Note 266. For, SACCH Repeat Window = 15, SRO bit is set to ‘1’ if 2 of the 15 preceding SACCH block single decodes fail.


Note 268. The default value of ‘Early Sending Indication (ESI)’ parameter is ‘Y’, i.e., it is enabled by default and the MS needs to support the "Controlled Early Classmark Sending" option in order to respond to the ESI parameter

DN0694168 Issue 2-0




Input Expected Output Create a site as mentioned in the test case. Site is in supervisory state. Disable the ‘Early Sending Indication (ESI)’ parameter using the MML command: ZEQM:BTS=<bts no.>:ESI=N;

‘Early Sending Indication (ESI)’ is disabled.

Start a speech call and monitor the Abis i/f. ‘SACCH Repeat = Disabled’, ‘SACCH Repeat Window (SRW)=0’ and ‘RSC MS = False’ are present in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages. Call is successful.

Monitor the Air i/f On Channel activation, the SI message on downlink SACCH does not get repeated in the SACCH period next to the SACCH period in which the first SI message is sent

Add interference on Air i/f in the downlink direction and start increasing it slowly until the MS sets SRR=1. Analyse the Air i/f messages.

The MS, being unable to decode the downlink SACCH, sets the SACCH Repeat Request (SRR) to 1 on every uplink SACCH and sends it to the BTS in the L1 header of the uplink SACCH. None of the SI messages on downlink SACCH is sent as a repetition of the SI message sent in the previous SACCH period



Start a speech call and monitor the Abis i/f. ‘SACCH Repeat = Disabled’, ‘SACCH Repeat Window (SRW)=0’ and ‘RSC MS = False’ are present in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages. Call is successful.

Add interference on Air i/f in the uplink direction and start increasing it slowly until the BTS stops decoding the uplink SACCH. Analyse the Air i/f messages.

The BTS, even on being unable to decode the uplink SACCH, sets the SACCH Repeat Order (SRO) to 0 on every downlink SACCH and send it to the MS in the L1 header of the downlink SACCH [Note 266]. None of the SI messages on downlink SACCH is sent as a repetition of the SI message sent in the previous SACCH period

Terminate the speech call. The speech call is terminated. Case Ref. BTS Configuration 1. 4 Omni EDGE

DN0694168 Issue 2-0


28.24 ASI with Early Classmark Sending - Downlink FACCH Repetition with ESI Disabled

Purpose:

To ensure that when ‘Early Sending Indication’ parameter is set to ‘N’ at the BSC, the Response frames on DL FACCH on Air i/f do not get repeated. Note 269. Set the MS maximum transmit power using MML command: EQM:BTS=<bts num>:PMAX1=5,PMAX2=6;

Note 270. For all test cases a neighbour is defined for BTS under test. The neighbour defined for BTS under test shall not be involved within the testing of the feature other than to handle the calls once handed over by the BSC unless otherwise stated.

Note 271. The level of interference should be kept near about the maximum signal level that the MS can transmit, so that at some moments during the test execution, the START / STOP DTMF messages are decoded but not the uplink RR Response frames by the BTS.

As the RR Response frames in uplink are not decoded by the BTS, the BTS retransmits START / STOP DTMF ACKNOWLEDGE message in downlink due to T200 expiry.






ARLT=64 is set.



Disable the ‘Early Class mark sending’ by setting the ‘ESI’ parameter as ‘NO’ at the BTS under test using the MML command: ZEQM:BTS=<bts num>:ESI=N;

The ‘Early Class mark sending’ parameter is disabled at the BTS under test.

Make a speech call at the BTS under test and terminate it in a separate test cell. The call type is as defined in the test case. Monitor the Abis i/f

Call is successful. ‘FACCH Repeat’ is enabled and ‘RSC MS’ is set to false in the ‘ACCH control IE’ of the Channel Activation message.

DN0694168 Issue 2-0


Input Expected Output During the AMR call, C/I conditions are gradually changed in downlink at the source BTS to manipulate the air interface so that the downlink codec mode changes and reaches the most robust codec of the ACS.

Downlink codec mode changes to the most robust codec of the ACS.

Now add interference [Note 271] in uplink to the BTS under test and start sending DTMF messages to generate FACCH traffic by pressing the keys on keypad of the MS. The T200 F timer gets expired. (About 30 DTMF messages should be enough). Monitor the Abis and Air i/f for FACCH messages.

RR response frame and ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’ message encapsulated in DL I-frame will appear on DL FACCH. For AMR/FR Call: The transmissions of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) as well as its retransmission after T200F expiries get repeated on Air i/f, if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. But the RR response frames on DL FACCH are not repeated even if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. For AMR/HR Call: Only the retransmission of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) after T200F expiry gets repeated on Air i/f, if the CMR is 4.75 kbps.



Make a speech call in the neighbour BTS and terminate it in a separate test cell. The call type is as defined in the test case.

Call is successful.

At the BTS under test set C/I conditions in downlink so that when call arrives at this BTS the downlink codec mode used, is the most robust codec of the ACS and also add interference with C/I~1-3 in uplink. Initiate inter-cell handover from neighbour BTS to the BTS under test by varying the signal level with the help of variable attenuators. Monitor the Abis and Air i/f for FACCH messages.

‘FACCH Repeat’ is enabled and ‘RSC MS’ is set to false in the ‘ACCH control IE’ of the Channel Activation message at the BTS under test. The target BTS (the BTS under test) sends DL response frames and PHYSICAL INFORMATION encapsulated in DL UI-frame on FACCH to the MS. The timer T3105 expires. The retransmission of DL UI-frame (carrying only PHYSICAL INFORMATION) due to expiry of T3105 timer gets repeated on Air i/f. Also No DL response frames on FACCH get repeated even when the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. Call is successfully handed over.

DN0694168 Issue 2-0


Input Expected Output Case Ref ACS BTS Configuration/Site Type Channel


1. 12.2 and 5.90 4 Omni EDGE/UltraSite TCHD / AFS 2. 7.40, and 4.75 4 Omni EDGE/MetroSite TCHD / AHS

28.25 ASI with DR TRAU Handover - SACCH Repetition after DRTRAU handover

Purpose:

To ensure that after DRTRAU handover, the SACCH messages on Air i/f get repeated on target BTS when the Repeat SACCH Criteria are met.




Note 275. ICM of target BTS must be a part of ACS of source side.

Note 276. Codec mode of ICM of target BTS must be either of 4.75, 5.15, 5.90 or 6.70.

Note 277. Use a different ICM for each sector.

Note 278. Define the ACS such that all the codecs available in FR and HR codec set are used in the different test cases.

Note 279. Handover can be triggered in two ways

1) By varying the signal level through variable attenuators manually.

2) By changing the parameters QDRF, QURF, QDRH and QURH for Intercell Handover and IHRF and IHRH for Intracell handover with following MML command ZEHB:BTS=<XX>:QDRF=<X>,QURF=<X>,QDRH=<X>,QURH=<X>,IHRF=<X>,IHRH=< X>;

DN0694168 Issue 2-0


Equipment and BTS Set-Up Sites – As per configuration, a separate UltraSite/MetroSite for call termination.

Variable attenuators, Spectrum Analyser, Signal Generator, Abis monitoring tool, Air interface monitoring tool.

Input Expected Output Configure the site as defined in the test case.

The site is in supervisory state

Define each of the two sectors as a neighbour of the other.

The neighbours are defined successfully.

Lock all the traffic channels except the one in any non BCCH TRX in each of the sectors.

Only one traffic channel remains unlocked in each sector.

Start a speech call as specified in the test case in the first sector and terminate it in a completely separate BTS. Create continuous sound at both mobile stations. Monitor the Abis.

The speech call is established in the first sector.

DN0694168 Issue 2-0


Input Expected Output Trigger a handover from sector1 to sector2 [Note 279].

For HR to FR Handover: The source BTS receives a Mode Modify message from BSC containing ICM of target BTS, with 8 Kbit/s TRAU bit disabled and the FICM bit enabled. The source BTS sends CMR and CMC command to TC and MS respectively to step the codec to ICM of target BTS. The MS and TC start to encode with the ICM of target BTS and this is reflected in the CMI message sent both by TC and MS. The BTS now sends an ACK in response to the Mode Modify received earlier At the target BTS a Channel Activation message for FR is received with 8 Kbit/s TRAU & FICM bits enabled. An ACK is sent to the BSC. Target BTS starts receiving 8 Kbit/s TRAU frames on 16 Kbit/s sub-channel and synchronizes to it. A Handover command is sent to MS MS tunes to the new channel and starts receiving valid speech frames immediately. In the uplink, BTS sends 8 Kbit/s TRAU frames on 16 Kbit/s sub-channel. As soon as BSC receives handover complete message, a Mode Modify is message sent to target BTS with 8 Kbit/s TRAU & FICM bits disabled. A CMR is sent to TC using 16 Kbit/s TRAU frame indicating the ICM. TC sends CMI on 16 Kbit/s TRAU frame. Mode Modify ACK is sent now. CMC and CMR commands are sent to MS and TC respectively to start using any codec from ACS of the serving BTS. The MS and TC start to encode with codecs from ACS of serving BTS and this is reflected in the CMI message sent both by TC and MS. Channel is released for source BTS. The handover is successfully completed.

DN0694168 Issue 2-0


Input Expected Output For FR to HR Handover:

The source BTS receives a Mode Modify message from BSC containing ICM of target BTS, with 8 Kbit/s TRAU & FICM bits enabled. The source BTS, sends a CMR to TC to step the codec to ICM of target BTS and CMC to MS to change the codec mode to the first codec mode which is compatible with the 8Kbit/s DR TRAU format and which is a part of the ACS of source BTS. As soon as a CMI of 8Kbit/s compatible mode is received by the source BTS from MS, it sends a CMR to transcoder in the 8Kbit/s frame format on the 16Kbit/s Abis sub channel indicating ICM of target BTS. Upon receiving this message, TC sends a CMI in the 8Kbit/s frame format on the 16Kbit/s Abis sub channel indicating ICM of target BTS. Now the source BTS sends an ACK in response to the Mode Modify message. The BSC activates a HR channel at the target BTS. On receiving Channel Activation ACK message, the BSC duplicates TRAU data received from the A-ter interface both towards the source and target BTS. A Handover command is sent to MS MS tunes to the new channel and starts receiving valid speech frames immediately. MS sends Handover Complete message to the BSC. Channel is released for source BTS. The handover is successfully completed. The call runs successfully in the target BTS.

In the target BTS, add interference on Air i/f in the direction as specified in the test case and start increasing it slowly until the repetition starts. Analyse the Air i/f messages.

For interference added in downlink: The MS, being unable to decode the downlink SACCH, sets the SACCH Repeat Request (SRR) to 1 and sends it to the BTS in the L1 header of the uplink SACCH. The SI message on downlink SACCH gets repeated exactly once in the SACCH period next to the SACCH period in which the SRR=1 is received by the BTS For interference added in uplink: The BTS, being unable to decode the uplink SACCH, sets SACCH Repeat Order (SRO) to 1 and send it to the MS in the L1 header of the downlink SACCH [Note 273]. The SI message on downlink SACCH gets repeated exactly once in the SACCH period next to the SACCH period in which the SRO=1 is sent by the BTS.


DN0694168 Issue 2-0



Configuration Source/Target BTS

Call Type/ Sector1

Call Type/ Sector2

TCH/ Sector1

TCH/ Sector2

Interference

1. 4 Omni EDGE AFS AHS TCHF TCHH DL 2. 4 Omni EDGE AHS AFS TCHF TCHF UL

28.26 ASI with DR TRAU Handover - Downlink FACCH Repetition during Inter Cell DRTRAU handover

Purpose:

To ensure that during Inter cell AMR/FR to AMR/HR DRTRAU handover, the DL FACCH messages on Air i/f get repeated.





Sites are in supervisory state. Channels are configured accordingly.

Configure the TCHs in BTS1 as TCHF and in BTS2 as TCHH.


Define BTS2 as a neighbour of BTS1 using the MML command: EAC:BTS=<bts num>::ABTS=<bts num>;


Define ARLT=64 for both the BTSs using the MML command: EQY:BTS=<bts num>:ARLT=64;

ARLT=64 is set.

Disable intra-cell handovers for both the BTSs using the MML command: ZEHG:BTS=<bts num>:EIC=N,EIH=N;


Make a speech call in BTS1 and terminate it in a separate test cell with the MS type as defined in the test case.


DN0694168 Issue 2-0


Input Expected Output Add interference with C/I~1-3 dB in uplink to BTS2 and at the same time Initiate inter-cell handover from BTS1 to BTS2 by varying the signal level with the help of variable attenuators. Monitor the Abis and Air i/f for FACCH messages.

Inter cell DR TRAU handover takes place. BSC sends HANDOVER COMMAND to the BTS 1 as seen on Abis. BTS sends this HANDOVER COMMAND encapsulated in DL I-frame on FACCH At BTS1: The transmission of DL I-frame (carrying HANDOVER COMMAND) get repeated on Air i/f, as the CMR is 4.75 5.15 or 5.90, and is the most robust codec of the ACS. At BTS2: BTS2 sends DL response frames and PHYSICAL INFORMATION encapsulated in DL UI-frame to the MS. The timer T3105 expires. The retransmission of DL UI-frame (carrying only PHYSICAL INFORMATION) due to expiry of T3105 timer gets repeated on Air i/f. Also the DL UA response frames (Not any other response frames) on FACCH get repeated if CMR is 4.75 kbps. No repetition of DL UA response frames will be seen if the most robust codec is any codec other than 4.75 kbps or if CMR sent is for the codec mode other than 4.75 kbps. (Response frames will not be repeated for case ref. 2, 3, 5 and 6 as CMR would be other than 4.75 during handover.) Handover is successfully completed.

Case Ref Base Station

ACS of BTS-1 ACS of BTS-2

ICM of BTS-2

BTS 1 BTS 2 MS Type

1. UltraSite

12.2, 10.2, 7.40 and 5.90

5.90, 5.15 and 4.75

5.90 4 Omni EDGE

4 Omni EDGE

RSC

Input Expected Output Create sites with configuration as mentioned in the test case.

Site is in supervisory state. Channels are configured accordingly.

Configure approximately half the TCHs as TCHF and the rest as TCHH in each TRX.


Lock all the TCHs in the BTS. Unlock one TCHH and one TCHF time slot on BCCH TRX.

Commands entered successfully.

DN0694168 Issue 2-0


Input Expected Output Define ARLT=64 for both the BTSs using the MML command: EQY:BTS=<bts num>:ARLT=64;

ARLT=64 is set.

Enable intra-cell handovers for both the BTSs using the MML command: ZEHG:BTS=<bts num>:EIC=Y,EIH=Y;

Intra-cell handovers are enabled.

Make an AMR half rate speech call in the BTS and terminate in a separate test cell with the MS type as defined in the test case.


Introduce very high interference in the UL direction to initiate Intra Cell handover.

BSC sends ASSINGMENT COMMAND to the BTS as seen on Abis i/f. BTS sends this ASSINGMENT COMMAND encapsulated in DL I-frame on FACCH to the MS. ASSIGNMENT COMPLETE message sent on the UL cannot be decoded (call do not get handed over to full rate channel). Only the retransmission of DL I-CMD frame (carrying ASSINGMENT COMMAND) after T200 F expiry gets repeated on Air i/f, if the CMR is 4.75 kbps.

RF Channel gets released. (In any case the DL I-frames (carrying ASSINGMENT COMMAND) will not be repeated for case ref. 2, 3, 5 and 6).

Now again make an AMR half rate speech call in the BTS and terminate in a separate test cell with the MS type as defined in the test case.


Add interference in uplink to the BTS to Initiate intra-cell handover Monitor the Abis and Air i/f for FACCH messages.

Intra cell DR TRAU handover takes place The BTS sends DL response frames on FACCH to the MS. All DL response frames on FACCH are repeated if CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. No repetition will be seen if the most robust codec is any codec other than 4.75, 5.15 or 5.90 kbps or if CMR sent is for a codec mode other than the most robust codec. Handover is successfully completed.

Case Ref Base Station

AMR/FR ACS AMR/HR ACS

ICM of BTS

BTS Configuration

MS Type

2. MetroSite

12.2, 10.2, 7.40 and 5.90

6.70, 5.90, 5.15 and 4.75

5.90 4 Omni EDGE RSC

DN0694168 Issue 2-0


28.27 ASI with Separate UL/DL AMR thresholds - Downlink FACCH Repetition with Separate UL/DL AMR thresholds

Purpose:

To ensure that for a cell with separate UL/DL AMR thresholds defined, DL FACCH messages get repeated when the Repeat FACCH Criteria are met. Note 281. Set the MS maximum transmit power using MML command: EQM:BTS=<bts num>:PMAX1=5,PMAX2=6;



Input Expected Output Create site with configuration as mentioned in the test case.


Define separate AMR thresholds in uplink and downlink directions for the call type to be tested as defined in the test case using MML ZEQY.

Commands are successful.

Define ARLT=64 at BTS under test using the MML command: ZEQY:BTS=<bts num>:ARLT=64;

ARLT=64 is set.

Disable intra-cell handovers at BTS under test using the MML command: ZEHG:BTS=<bts num>:EIC=N,EIH=N;


Make a speech call and terminate it in a separate test cell. The call type and MS type are as defined in the test case. Monitor the Abis i/f




DN0694168 Issue 2-0


Input Expected Output Now add interference [Note 210] in uplink to the BTS to the BTS under test and start sending DTMF messages to generate FACCH traffic by pressing the keys on keypad of the MS. The T200 F timer gets expired. (About 30 DTMF messages should be enough). Monitor the Abis and Air i/f for FACCH messages.

RR response frame and ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’ message encapsulated in DL I-frame will appear on DL FACCH. For AMR/FR Call: The transmissions of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) as well as its retransmission after T200F expiries get repeated on Air i/f, if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. The RR response frames on DL FACCH are also repeated if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. For AMR/HR Call: Only the retransmission of DL I-CMD frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) after T200F expiry gets repeated on Air i/f, if the CMR is 4.75 kbps.



Case Ref ACS Source BTS/Site Type

Target BTS/Site Type


MS Type

1. 5.15, 10.2 and 12.2

4 Omni EDGE/UltraSite

4 Omni EDGE/UltraSiteSite

TCHD / AFS RSC

2. 4.75 and 12.2

4 Omni EDGE/MetroSite

4 Omni EDGE/MetroSite

TCHD / AHS RSC

28.28 ASI with STRIC - SACCH Repetition with STIRC

Purpose:

To ensure that the SACCH messages for a cell with STIRC enabled get repeated when the Repeat SACCH Criteria are met.



DN0694168 Issue 2-0


Input Expected Output Create a site with configuration as mentioned in the test case.


Disable intra-cell handovers using the MML command: ZEHG:BTS=<bts num>:EIC=N,EIH=N;


Enable STIRC using the MML command: ZEQM: BTS=<bts num>: STIRC=Y;

STIRC is enabled successfully.

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

Start a speech call and monitor the Abis i/f. ‘SACCH Repeat’ is enabled and ‘SACCH Repeat Window (SRW)’ is present in the ‘ACCH Control IE’ of the ‘Channel Activation’ messages. Call is successful.




Remove the interference and terminate the call. The call is terminated. Again start a speech call and monitor the Abis i/f. ‘SACCH Repeat’ is enabled and ‘SACCH Repeat

Window (SRW)’ is present in the ‘ACCH Control IE’ of the ‘Channel Activation’ messages. Call is successful.


DN0694168 Issue 2-0


Input Expected Output Add interference on Air i/f in the uplink direction and start increasing it slowly until the repetition starts. Analyse the Air i/f messages.

The BTS, being unable to decode the uplink SACCH, sets SACCH Repeat Order (SRO) to 1 and send it to the MS in the L1 header of the downlink SACCH. The SI message on downlink SACCH gets repeated exactly once in the SACCH period next to the SACCH period in which the SRO=1 is sent by the BTS.






Terminate the speech call. The speech call is terminated. Case Ref. BTS Configuration 11 4 Omni EDGE

1Use BSC SW S13 28.29 ASI with STRIC - Downlink FACCH Repetition with STIRC

Purpose: To ensure that the FACCH messages for a cell with STIRC enabled get repeated when the Repeat FACCH Criteria are met. Note 284. Set the MS maximum transmit power using MML command: EQM:BTS=<bts num>:PMAX1=5,PMAX2=6;




DN0694168 Issue 2-0





ARLT=64 is set.



Enable STIRC at the BTS under test using the MML command: ZEQM: BTS=<bts num>: STIRC=Y;


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

Make a speech call at the BTS under test and terminate it in a separate test cell. The call type and MS type are as defined in the test case. Monitor the Abis i/f


During the AMR call, C/I conditions are gradually changed in downlink at the source BTS to manipulate the air interface so that the downlink codec mode changes and reaches the most robust codec of the ACS.



RR response frame and ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’ message encapsulated in DL I-frame will appear on DL FACCH. For AMR/FR Call: The transmissions of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) as well as its retransmission after T200F expiries get repeated on Air i/f, if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS The RR response frames on DL FACCH are also repeated if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS No repetition will be seen if the most robust codec is any codec other than 4.75, 5.15 or 5.90 kbps or if CMR sent is for the codec mode other than the most robust codec. For AMR/HR Call: Only the retransmission of DL I-CMD frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) after T200F expiry gets repeated on Air i/f, if the CMR is 4.75 kbps. No repetition will be seen if the most robust codec is any codec other than 4.75 kbps or if CMR sent is for the codec mode other than the most robust codec.



DN0694168 Issue 2-0


Input Expected Output Make a speech call in the neighbour BTS and terminate it in a separate test cell. The call type and MS type are as defined in the test case.

Call is successful.

At the BTS under test set C/I conditions in downlink so that when call arrives at this BTS the downlink codec mode used, is the most robust codec of the ACS and also add interference with C/I~1-3 in uplink. Initiate inter-cell handover from neighbour BTS to the BTS under test by varying the signal level with the help of variable attenuators. Monitor the Abis and Air i/f for FACCH messages.

‘FACCH Repeat’ is enabled in the ‘ACCH control IE’ of the Channel Activation message at the BTS under test. The target BTS (the BTS under test) sends PHYSICAL INFORMATION encapsulated in DL UI-frame and DL response frames on FACCH to the MS. The timer T3105 expires. The retransmission of DL UI-frame (carrying only PHYSICAL INFORMATION) due to expiry of T3105 timer gets repeated on Air i/f. Also For AMR/FR Call: All DL response frames on FACCH are repeated if CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. No repetition will be seen if the most robust codec is any codec other than 4.75, 5.15 or 5.90 kbps or if CMR sent is for the codec mode other than the most robust codec. For AMR/HR Call: Only the DL UA response frames on FACCH get repeated, if CMR is 4.75 kbps. No repetition will be seen if the most robust codec is any codec other than 4.75 kbps or if CMR sent is for the codec mode other than the most robust codec. Call is successfully handed over.

Case Ref ACS BTS Configuration Channel Configuration / Speech Codec

MS Type

1. 7.40, and 4.75 4 Omni EDGE TCHD / AHS RSC

DN0694168 Issue 2-0


28.30 ASI with STRIC - UL DTX estimation and estimation validity with STIRC

Purpose:

To ensure that the ASI capable BTS [Note 248] with STIRC enabled does the estimation of UL DTX as well the validation of this estimation all the time during the call and reports these values in the ‘DTXu-est’ and ‘DTXu-valid’ fields respectively in the Uplink Measurement IE of Measurement Result message on Abis i/f.






Note 288. For UltraSite: ASI capable BTS consists of any TRX (EDGE or GSM) configured only with EDGE BB card.

For MetroSite: ASI capable BTS is one that consists of only EDGE TRX(s).

Note 289. The STIRC capacity licensing feature BSS20494 together with STIRC Feature BSS20063 is a BSS12 level feature that enable\disables the use of STIRC technology in the BTS.

STIRC licensing can be interrogated on the BSC using MML command ZW7I STIRC licensing can be enabled/disabled on the BSC using MML command ZW7M

STIRC capacity licensing is based on the number of TRXs at the BSC, which have STIRC enabled.

The BSC will check the operator has enough licenses for the TRXs in the BTS objects, and checks that allowed amount of STIRC enabled TRXs is not exceeded.

When enabled, STIRC technology is deployed in the UL by BTS. When disabled, the current IRC technology is deployed by the BTS.

Note 290. STIRC can be enabled at any time without locking/unlocking of the TRX/sector/site, this indicates that BTS_CONF_DATA containing the info field about STIRC enable/disable can be sent at anytime when BTS is running.


DN0694168 Issue 2-0



Input Expected Output Create a site with configuration as mentioned in the test case.


Enable STIRC for the sector using MML command: ZEQM:BTS=<bts no>:STIRC=Y;


Set DTX mode as mentioned in the test case with the help of MML command: ZEQM:BTS=<bts num>:DTX=<x>;

DTX mode is set.

Start a speech call and monitor the Abis i/f. ‘SACCH Repeat’ is enabled in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages The call is successful.




For DTX ON If the ‘Measurement Report’ on uplink SACCH contains the ‘DTX USED’ field with value 0, the corresponding values of DTXu_est and DTXu_valid in ‘Uplink Measurement’ IE of ‘Measurement Result’ message on Abis i/f are 0 and 1 respectively [Note 286]. If the ‘Measurement Report’ on uplink SACCH contains the ‘DTX USED’ field with value 1, the corresponding values of DTXu_est and DTXu_valid in ‘Uplink Measurement’ IE of ‘Measurement Result’ message on Abis i/f are 1 and 1 respectively [Note 231]. For DTX ‘OFF’: The ‘Measurement Report’ on uplink SACCH contains the ‘DTX USED’ field with value 0 and the corresponding values of DTXu_est and DTXu_valid in ‘Uplink Measurement’ IE of ‘Measurement Result’ message on Abis i/f are 0 and 0 respectively [Note 217].

Terminate the speech call. The speech call is terminated. Case Ref. Configuration DTX 1. 4 Omni EDGE ON

2. 4 Omni EDGE OFF

DN0694168 Issue 2-0


28.31 ASI with Different Hopping Modes - SACCH Repetition with Different Hopping modes

Purpose: To ensure that the SACCH messages for a cell with Hopping enabled get repeated when the Repeat SACCH Criteria are met.






Input Expected Output Create a site as mentioned in the test case. Site is in supervisory state. Start a speech call and monitor the Abis i/f. ‘SACCH Repeat = Enabled’ and ‘SACCH

Repeat Window (SRW)’ are present in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages. Call is successful.




Remove the interference and terminate the call. The call is terminated.

DN0694168 Issue 2-0


Input Expected Output Start a speech call and monitor the Abis i/f. ‘SACCH Repeat = Enabled’ and ‘SACCH

Repeat Window (SRW)’ are present in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages. Call is successful.



Terminate the speech call. The speech call is terminated. Case Ref. BTS Configuration Hopping 1. 4 Omni EDGE (GSM 1800) with RTxx BB 2. 4 Omni EDGE (GSM 800) RAH 3. 4 Omni EDGE (GSM 900) RF

28.32 ASI with Different Hopping Modes - Downlink FACCH Repetition with Different Hopping modes

Purpose:

To ensure that the DL FACCH messages for a cell with Hopping enabled get repeated when the Repeat FACCH Criteria are met. Note 294. Set the MS maximum transmit power using MML command: EQM:BTS=<bts num>:PMAX1=5,PMAX2=6;




DN0694168 Issue 2-0





ARLT=64 is set.



Make a speech call at the BTS under test and terminate it in a separate test cell. The call type and MS type are as defined in the test case. Monitor the Abis i/f


Now add interference [Note 210] in uplink to the BTS under test and start sending DTMF messages to generate FACCH traffic by pressing the keys on keypad of the MS. The T200 F timer gets expired. (About 30 DTMF messages should be enough). Monitor the Abis and Air i/f for FACCH messages.

RR response frame and ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’ message encapsulated in DL I-frame will appear on DL FACCH. For AMR/FR Call: The transmissions of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) as well as its retransmission after T200F expiries get repeated on Air i/f, if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS The RR response frames on DL FACCH are also repeated if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. For AMR/HR Call: Only the retransmission of DL I-CMD frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) after T200F expiry gets repeated on Air i/f, if the CMR is 4.75 kbps.



Make a speech call in the neighbour BTS and terminate it in a separate test cell. The call type and MS type are as defined in the test case.

Call is successful.

DN0694168 Issue 2-0


Input Expected Output At the BTS under test, add interference with C/I~1-3 in uplink direction. Initiate inter-cell handover from neighbour BTS to the BTS under test by varying the signal level with the help of variable attenuators. Monitor the Abis and Air i/f for FACCH messages.

‘FACCH Repeat’ is enabled in the ‘ACCH control IE’ of the Channel Activation message at the BTS under test. The target BTS (the BTS under test) sends DL response frames and PHYSICAL INFORMATION encapsulated in DL UI-frame on FACCH to the MS. The timer T3105 expires. The retransmission of DL UI-frame (carrying only PHYSICAL INFORMATION) due to expiry of T3105 timer gets repeated on Air i/f. Also For AMR/FR Call: All DL response frames on FACCH are repeated if CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS For AMR/HR Call: Only the DL UA response frames on FACCH get repeated, if CMR is 4.75 kbps Call is successfully handed over.

Case Ref ACS Band

BTS Configuration Channel Configuration / Speech Codec

MS Type

Hopping Mode

1. 4.75 800

4 Omni EDGE TCHD / AHS

RSC RAH

2. 4.75 1800

4 Omni EDGE TCHD / AFS

RSC BB

28.33 ASI with Different Hopping Modes - Uplink DTX Estimation and Estimation Validity with Different Hopping modes

Purpose:

To ensure that the ASI capable BTS [Note 299] with Hopping enabled does the estimation of UL DTX as well the validation of this estimation all the time during the call and reports these values in the ‘DTXu-est’ and ‘DTXu-valid’ fields respectively in the Uplink Measurement IE of Measurement Result message on Abis i/f.





DN0694168 Issue 2-0










Start a speech call and monitor the Abis i/f. ‘SACCH Repeat’ is enabled in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages The call is successful.





Terminate the speech call. The speech call is terminated. Case Ref. Configuration / Band Hopping Mode 1. 4 Omni EDGE / 1800 (with RTxx) BB

2. 4 Omni EDGE / 900 NAH

3. 4 Omni EDGE / 900 RF

4 4 Omni EDGE / 1900 BB1 1Use 6220 and 7370 MS and UL DTX is ON

DN0694168 Issue 2-0


28.34 ASI with BSS and Site Synchronization - SACCH Repetition with BSS and Site Synchronization

Purpose: To ensure that when the Repeat SACCH Criteria are met, the SACCH messages get repeated in case of BSS and Site synchronisation. Note 300. All test cases need to be done with SACCH Repeat Window set as 15 unless otherwise stated. Its value can be set using MML command ZEEQ.



Input Expected Output Create the Sites at the BSC as mentioned in the test case.

Sites are in supervisory state

Define the synchronization chain in the BSC using the MML command: For Test cases 1 ZEFM:<mm>:CS=BCF,SENA=T,ADD=<s1>&<s2>; For Test cases 2 ZEFM:<s1>:CS=LMU,SENA=T; <mm> = master BCF number <s1> = Slave 1 BCF number Physically create and commission the sites, so that they are in working order, synchronised to the master clock.

Sites are synchronised to the master clock.

Lock all the TCHs in the common segment except one TCH.

Only one TCH remains ‘WO’ in the segment.

Start a speech call in the common segment and terminate it in a separate test cell and monitor the Abis i/f.


DN0694168 Issue 2-0


Input Expected Output Monitor the Air i/f On Channel activation, the SI message on

downlink SACCH gets repeated exactly once in the SACCH period next to the SACCH period in which the first SI message is sent. The BTS stops repeating the SI message on downlink SACCH once the MS acknowledges the receipt of first SI message with SACCH Repeat Request (SRR) set to 0 in the L1 header of the uplink SACCH.



Remove the interference and terminate the call. The call is terminated. Start a speech call in the common segment and terminate it in a separate test cell and monitor the Abis i/f.









Terminate the speech call. The speech call is terminated. Case Ref. BTS Configuration/Site Type 1. Talk(DF7.0) – UltraSite(CX6) – UltraSite(CX6) 2. LMU(4.4) – MetroSite(CXM6) – MetroSite(CXM6)

DN0694168 Issue 2-0


28.35 ASI with BSS and Site Synchronization - Downlink FACCH Repetition with BSS and Site Synchronization

Purpose:

To ensure that when the Repeat FACCH Criteria are met, the FACCH messages get repeated in case of BSS and Site synchronisation. Note 303. Set the MS maximum transmit power using MML command: EQM:BTS=<bts num>:PMAX1=5,PMAX2=6;



Input Expected Output Create the Sites at the BSC depending upon the configuration indicated in the test case and in the diagrams below.


Define the synchronization chain in the BSC using the MML command: For Test cases 1, 2,4 and 5 ZEFM:<mm>:CS=BCF,SENA=T,ADD=<s1>&<s2>; For Test cases 3 and 6 ZEFM:<s1>:CS=LMU,SENA=T,ADD=<s2>; For Test cases 7, and 10 ZEFM:<mm>:CS=BCF,SENA=T,ADD=<s1>; For Test cases 9 and 12 ZEFM:<s1>:CS=LMU,SENA=T; <mm> = master BCF number <s1> = Slave 1 BCF number <s2> = Slave 2 BCF number

Commands entered successfully. Sites are synchronised to master clock.

Define ARLT=64 for each BTS using the MML command: EQY:BTS=<bts num>:ARLT=64;

ARLT=64 is set.

Enable intra-cell handovers in the segment using the MML command: ZEHG:SEG=<seg num>:EIC=Y,EIH=Y;

Intra-cell handovers are enabled in the segment.

Lock all the TCHs in the common segment except one TCH.

Only one TCH remains ‘WO’ in the segment.

Make a speech call and terminate in a separate test cell. The call type and MS type are as defined in the test case. Monitor the Abis i/f.




DN0694168 Issue 2-0


Input Expected Output Now add interference [Note 210] in uplink to the TCH on which the call is going on and start sending DTMF messages to generate FACCH traffic by pressing the keys on keypad of the MS. The T200 F timer gets expired. (About 30 DTMF messages should be enough). Monitor the Abis and Air i/f for FACCH messages.

RR response frame and ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’ message encapsulated in DL I-frame will appear on DL FACCH. For AMR/FR Call: The transmissions of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) as well as its retransmission after T200F expiries get repeated on Air i/f, if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. The RR response frames on DL FACCH are also repeated if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. For AMR/HR Call: Only the retransmission of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) after T200F expiry gets repeated on Air i/f, if the CMR is 4.75 kbps.



Unlock one more TCH in the segment on a different cabinet.

One more TCH gets unlocked in the segment. Now ensure that the two unlocked TCHs belong to different cabinet in the chain.

Again make a speech call using one unlocked TCH and terminate it in a separate test cell. The call type and MS type are as defined in the test case.


Set C/I conditions in downlink at the second unlocked TCH such that when call arrives at this TCH after handover the codec mode used in downlink, is the most robust codec of the ACS. Add interference in uplink to the first TCH to Initiate synchronous handover. Monitor the Abis and Air i/f for FACCH messages.

‘FACCH Repeat’ is enabled in the ‘ACCH control IE’ of the Channel Activation message at the second TCH. During handover: For AMR/FR Call: All DL response frames on FACCH are repeated if CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. For AMR/HR Call: Only the DL UA response frames on FACCH get repeated if CMR is 4.75 kbps Call is successfully handed over.

DN0694168 Issue 2-0


Input Expected Output Case Ref Chain Configuration

(Software) ACS for each BTS

Speech Codec

MS Type

Sync Mode

1. LMU(4.4) – Ultra(CX6) – Ultra(CX6)

7.40, 6.70, and 4.75

AHS Non-RSC

BSS Sync

2. Talk(DF7.0) – Metro(CXM6) – Metro(CXM6)

12.2, 10.2, and 4.75

AFS RSC

Site Sync

28.36 ASI with RLT - ARLT with SACCH Repetition

Purpose: To ensure that under same C/I condition and ARLT value, the call for which SACCH repetition is in effect sustains for a longer duration than the call for which SACCH repetition is not in effect.

Note 304. The radio link failure criterion is based on the radio link counter. The counter is equal to the ARLT (for AMR call) parameter defined on BSC. If the MS is unable to decode a SACCH message, then the counter is decremented by one. In case of a successful reception of a SACCH message the counter is increased by 2. In any case the counter shall not exceed the value of AMR RADIO_LINK_TIMEOUT (ARLT). If the counter continues to decrease and reaches to 0, a radio link failure shall be declared.

When a radio link failure on Layer 1 is detected on a dedicated channel (TCH or SDCCH), the BTS sends a CONN_FAIL message with cause 1 = radio link failure to the BSC.



Input Expected Output Create a site as mentioned in the test case. Site is in supervisory state. Define ARLT=64 for the BTSs under test using the MML command: EQY:BTS=<bts num>:ARLT=64;

ARLT=64 is set.

Lock all the TCHs except two on the same TRX in the sector.

Only two TCHs remain unlocked on the same TRX. All other timeslots in the sector are locked.

DN0694168 Issue 2-0


Input Expected Output Start two speech calls on the TRX under test and terminate these calls on separate test cells. One should be established with RSC MS and other one with Non-RSC MS at the TRX under test.

For RSC MS: ‘SACCH Repeat’ is enabled and ‘SACCH Repeat Window (SRW)’ is present in the ‘ACCH Control IE’ of the ‘Channel Activation’ message. For Non-RSC MS: ‘SACCH Repeat’ is disabled and ‘SACCH Repeat Window (SRW)’ is present in the ‘ACCH Control IE’ of the ‘Channel Activation’ message. Calls are successful.

Add interference on Air i/f in the uplink direction and start increasing it slowly until the repetition starts as seen with RSC MS. Analyse the Air i/f messages.

With RSC MS, the BTS, being unable to decode the uplink SACCH, sets SACCH Repeat Order (SRO) to 1 and send it to the MS in the L1 header of the downlink SACCH. The SI message on downlink SACCH gets repeated exactly once in the SACCH period next to the SACCH period in which the SRO=1 is sent by the BTS. With Non-RSC MS, SACCH messages are never get repeated neither in uplink direction nor in downlink direction. The BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC for the call with Non-RSC MS much before than the call with RSC MS. Calls get released [Note 304].

Remove all the interference from uplink. Again start two speech calls on the TRX under test and terminate these calls on separate test cells. One should be established with RSC MS and other one with Non-RSC MS at the TRX under test. Now repeat the subsequent steps 3 to 5 times.

Ensure that every time the BTS sends CONN_FAIL message(s) with cause 1 = radio link failure to the BSC for the call with Non-RSC MS much before than the call with RSC MS.

Case Ref. BTS Configuration/Site Type Call Type 1. 4 Omni EDGE/UltraSite AFS 2. 4 Omni EDGE/MetroSite AHS

28.37 Power Control with SACCH Repetition - Power Control with SACCH Repetition

Purpose: To ensure that when SACCH repetition is in effect, the power control algorithm works fine and power control messages are sent to MS by the BTS.


Note 306.

DN0694168 Issue 2-0


All test cases need to be done with ARLT set as 64 unless otherwise stated. Its value can be set using MML command ZEQY.

Note 307. The difference between PMAX & PMIN of the MS should be large enough (e.g., PMAX1= 33 & PMIN= 5) so that a number of MS power control could take place.






‘SACCH Repeat’ is enabled and ‘SACCH Repeat Window (SRW)’ as specified in the test case is present in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages. Call is successful.


Add interference on Air i/f in the direction as specified in the test case and start increasing it slowly until the repetition starts [Note 210] Analyse the Air i/f messages.

For interference added in downlink: The MS, being unable to decode the downlink SACCH, sets the SACCH Repeat Request (SRR) to 1 and sends it to the BTS in the L1 header of the uplink SACCH. The SI message on downlink SACCH gets repeated exactly once in the SACCH period next to the SACCH period in which the SRR=1 is received by the BTS For interference added in uplink: The BTS, being unable to decode the uplink SACCH, sets SACCH Repeat Order (SRO) to 1 and send it to the MS in the L1 header of the downlink SACCH The SI message on downlink SACCH gets repeated exactly once in the SACCH period next to the SACCH period in which the SRO=1 is sent by the BTS.

Attenuate the signal from the MS to BTS with help of a variable attenuator and monitor the Abis i/f.

The uplink MS-BTS signal level varies and the ‘MS Power Control’ message is sent by the BSC to the BTS.

DN0694168 Issue 2-0


Input Expected Output Monitor the Air i/f. If the BTS intends to send the new MS power

level to the MS in the SACCH period in which the original SACCH is sent then this new MS power level is also repeated in the repeated SACCH in the next SACCH period. If the BTS intends to send the new MS power level in the SACCH period in which the repeated SACCH is sent then it would send this new MS power level in the SACCH period next to the SACCH period having the repeated SACCH. In any case, the new MS power level will be sent to the MS.

Terminate the speech call. The speech call is terminated. Case Ref. Configuration/Site Type Call Type Interferenc

e 1. 4 Omni EDGE/UltraSite AFS DL 2. 4 Omni EDGE/MetroSite AHS UL

28.38 SACCH Repetition with MS Speed and Distance

Purpose: To ensure that SACCH repetition is performed while the MS – BTS distance is varying due to moving MS Note 308. For, SACCH Repeat Window = 15, SRO bit is set if 2 of the 15 preceding SACCH block single decodes fail.


Note 310. In case of AFS, calls are made on timeslots 0,1,3,5,6 & 7 so that timeslots 2 & 4 are left unused whereas in case of AHS, two half-rate traffic channels of any one timeslot are left unused.

Note 311. The interference should be increased to such an extent that the calls do not get dropped but the SACCH repetition happens to occur most of the time for the RSC MS as Non-RSC MS does not support SACCH repetition.


DN0694168 Issue 2-0


Signal generator, Abis Interface monitoring tool, Air i/f monitoring tool, RF TA Rig



Disable UL DTX using the MML command: ZEQM:BTS=<bts num>:DTX=<2>; Check the status of the UL DTX using the MML command ZEQO:BTS=<bts num>:MIS;

UL DTX is disabled as ‘DTX MODE’ is 2.

Lock all the traffic channels except the traffic channels of any one Non-BCCH TRX

Traffic channels are locked successfully.

Make speech calls on the Non-BCCH TRX having the unlocked traffic channels so that only two traffic channels are left unused [Note 310].

Calls are successful.

Set up the RF TA rig and connect both MSs to it so that the MS-BTS distance for the two MSs (1 RSC + 1 Non-RSC) can be varied.


Start speech calls for both RSC and Non-RSC MSs moving towards and away from the BTS at a speed as specified in the test case and terminate the calls in some other cell. Monitor the Abis i/f.

For RSC MS ‘SACCH Repeat=Enabled’ and ‘RSC MS=TRUE’ are present in the ‘ACCH Control IE’ element of the ‘Channel Activation’ message. For Non-RSC MS ‘SACCH Repeat=Disabled’ and ‘RSC MS=FALSE’ are present in the ‘ACCH Control IE’ element of the ‘Channel Activation’ message. Calls are successful.

DN0694168 Issue 2-0


Input Expected Output Add interference on Air i/f to speech calls from RSC MS as well as Non-RSC MS in the direction as specified in the test case and start increasing it slowly [Note 311]. Analyse the Air i/f messages.

A) For interference added in downlink: i) For RSC MS The MS, being unable to decode the downlink SACCH, sets the SACCH Repeat Request (SRR) to 1 and sends it to the BTS in the L1 header of the uplink SACCH. The SI message on downlink SACCH gets repeated exactly once in the SACCH period next to the SACCH period in which the SRR=1 is received by the BTS ii) For Non-RSC MS The MS does not set SRR=1 and hence no downlink SACCH repetition takes place. B) For interference added in uplink: i) For RSC MS The BTS, being unable to decode the uplink SACCH, sets SACCH Repeat Order (SRO) to 1 and send it to the MS in the L1 header of the downlink SACCH [Note 228]. The SI message on downlink SACCH gets repeated exactly once in the SACCH period next to the SACCH period in which the SRO=1 is sent by the BTS. ii) For Non-RSC MS The BTS does not set SRO=1 and hence no uplink or downlink SACCH repetition takes place.

Hold the speech calls for about 5 minutes with the MSs moving at the specified speed.

The speech calls for RSC and Non-RSC MSs are maintained and none of them gets dropped because of the varying MS-BTS distance.

Terminate all speech calls. The speech calls are terminated. Case Ref. Configuration Call

Type/Channel Configuration

MS Speed Interference

1. 4 Omni EDGE AFS / TCHF

80km/h DL

2. 4 Omni EDGE AHS / TCHH

200km/h DL

DN0694168 Issue 2-0


28.39 UL DTX Estimation Accuracy

Purpose:

To ensure that for an AMR call with codec 4.75kbps, the accuracy of the estimation of DTX reported by the BTS to BSC in the ‘Measurement Result’ message on Abis i/f is greater than or equal to 95% with an UL FER of utmost 2%.






Note 314. A tool is required for the generation of an audio for a SACCH period with 120ms of silence within the SACCH period.



Input Expected Output Create a site as mentioned in the test case. Site is in supervisory state. Set DTX to ‘ON’ using the MML command: ZEQM:BTS=<bts num>:DTX=<1>;

DTX mode is set.


‘SACCH Repeat’ is disabled in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages The call is successful.

Add interference on Air i/f in the uplink direction and start increasing it slowly. Monitor the Abis i/f and decode the value of UL FER from the ‘Supplementary Information’ field of the ‘Measurement Result’ message.

The UL Speech FER reaches almost 2%.

Monitor the call for about 20 seconds and introduce, in the UL, an audio in the every following SACCH period with 120ms of silence within each SACCH period during the call. [Note 314]


DN0694168 Issue 2-0


Input Expected Output Monitor the Air i/f for ‘Measurement Report’ message and the Abis interface for ‘Uplink Measurement’ IE of ‘Measurement Result’ message for the time period mentioned in the above step.

If the ‘Measurement Report’ on uplink SACCH contains the ‘DTX USED’ field with value 0, the corresponding values of DTXu_est and DTXu_valid in ‘Uplink Measurement’ IE of ‘Measurement Result’ message on Abis i/f are 0 and 1 respectively [Note 231]. The ‘Measurement Report’ on uplink SACCH contains the ‘DTX USED’ field with value 1, the corresponding values of DTXu_est and DTXu_valid in ‘Uplink Measurement’ IE of ‘Measurement Result’ message on Abis i/f are 1 and 1 respectively [Note 231].

Many hundreds of samples (SACCH periods =Measurement Result message) need to be monitored for checking the accuracy of the estimated value of the UL DTX.

For UL DTX is set as ‘ON’, the UL DTX estimated by the BTS should be ‘UL DTX is used’, i.e., DTX_est & DTX_valid should be 1. The DTX estimation accuracy should be at least for the 95% of the sample period. This feat should be achieved with UL FER of utmost 2%.

Terminate the speech call. The speech call is terminated. Case Ref. Configuration Call Type 1. 4 Omni EDGE AFS

2. 4 Omni EDGE AHS 28.40 Downlink FER Reporting without SACCH Repetition

Purpose: To ensure that DL FER is reported by the BTS in the ‘Supplementary Info’ of ‘Measurement Result’ on the Abis i/f when SACCH repetition is disabled as well as when SACCH repetition is enabled but not in effect.

Note 315. For BTS to report DL FER, the MS must be capable of sending ‘Enhanced Measurement Report’.


Note 317. All test cases need to be executed with UL & DL DTX disabled.

DN0694168 Issue 2-0



Abis monitoring tool,

Input Expected Output Create a site as mentioned in the test case. Site is in supervisory state. Select an MS that supports Enhanced Measurement Reporting [Note 315] and start a speech call. Monitor the Abis i/f.

‘SACCH Repeat = Enabled’ is present in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages. Call is successful.

Monitor the TRXSIG for BTS on the Abis for MEASUREMENT RESULTS / ENHANCED MEASUREMENT REPORT messages. Also, decode the ‘Supplementary Information Field’ within the Measurement Result message to ensure that the DL FER is being calculated and reported by the BTS.

Enhanced Measurement Reports (Layer 3) are sent up to the Abis [Note 104]. DL FER is always calculated and reported by the BTS.

Disconnect the speech call. The speech call is disconnected. Disable ‘FACCH and SACCH repetition for repeated ACCH capable mobiles on AMR’ from BSC.

‘FACCH and SACCH repetition for repeated ACCH capable mobiles on AMR’ is disabled.

Start a speech call and monitor the Abis i/f. ‘SACCH Repeat’ is disabled in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages The call is successful.


Enhanced Measurement Reports (Layer 3) are sent up to the Abis [Note 104]. DL FER is always calculated and reported by the BTS

Terminate the speech call. The speech call is terminated. Case Ref. BTS Configuration Call Type 1. 4 Omni EDGE AFS 2. 4 Omni EDGE AHS

28.41 Downlink FER Reporting with UL SACCH Repetition

Purpose: To ensure that when UL SACCH repetition is in effect, DL FER is reported by the BTS to BSC in the ‘Supplementary Info’ of ‘Measurement Result’ on the Abis i/f.

Note 318. For BTS to report DL FER, the MS must be capable of sending ‘Enhanced Measurement Report’.

DN0694168 Issue 2-0



Note 320. If the BTS cannot be sure whether or not the MS is performing uplink repetition (i.e. it does not know the period to which a received EMR relates), then it shall calculate and report the DL FER only if the BTS sent the same number of speech blocks in both of the last 2 SACCH periods

Note 321. All test cases need to be executed with UL & DL DTX disabled.



Input Expected Output Create a site as mentioned in the test case. Site is in supervisory state. Select an MS that supports Enhanced Measurement Reporting [Note 315] and start a speech call. Monitor the Abis i/f.

‘SACCH Repeat = Enabled’ is present in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages. Call is successful.




Enhanced Measurement Reports (Layer 3) are sent up to the Abis [Note 104]. DL FER is calculated and reported depending on the number of speech blocks sent by the BTS in the last 2 SACCH periods [Note 320].

Terminate the speech call. The speech call is terminated. Case Ref. BTS Configuration Call Type 1. 4 Omni EDGE AHS 2. 4 Omni EDGE AFS

DN0694168 Issue 2-0


28.42 ASI with IUO - SACCH Repetition with IUO

Purpose: To ensure that the SACCH messages for a cell with IUO enabled get repeated when the Repeat SACCH Criteria are met.




Note 325. A cell configured with IUO has two layers: Regular layer & Super Reuse layer.



Input Expected Output Create a site with IUO configured as mentioned in the test case.







DN0694168 Issue 2-0


Input Expected Output Remove the interference and terminate the call. The call is terminated. Start a speech call on the TRX as specified in the test case and monitor the Abis i/f.









Terminate the speech call. The speech call is terminated. Case Ref. BTS Configuration TRX 1. 4 Omni EDGE (Each layer is having 2 TRXs) Regular

28.43 ASI with IUO - Downlink FACCH Repetition with IUO

Purpose:

To ensure that the FACCH messages for a cell with IUO enabled get repeated when the Repeat FACCH Criteria are met. Equipment and BTS Set-Up Sites - as per configuration defined in test case.


Input Expected Output Create sites with IUO configured as mentioned in the test case. For the test cases that involves handover from Super reuse TRX to Super reuse TRX, do not configure Regular TRX at source as well at target BTS.


Define neighbour using the MML command: EAC:BTS=<bts num>::ABTS=<bts num>;

Neighbours are defined.

DN0694168 Issue 2-0


Input Expected Output Define ARLT=64 for each BTS using the MML command: EQY:BTS=<bts num>:ARLT=64;

ARLT=64 is set.

Disable intra-cell handovers at the source and target BTSs using the MML command: ZEHG:BTS=<bts num>:EIC=N,EIH=N;


Lock all the TCHs except one on each BTS on the TRX as required by the HO type.

Only one TCH in each BTS on the TRX as required by the HO type is unlocked.

Lock the neighbour BTS using the MML command: ZEQS:BTS=<bts num>:L;

The neighbour BTS gets locked

Make a speech call in the source BTS and terminate it in a separate test cell. The call type and MS type are as defined in the test case. Monitor the Abis i/f.




Now add interference [Note 210] in uplink to the source BTS and start sending DTMF messages to generate FACCH traffic by pressing the keys on keypad of the MS. The T200 F timer gets expired. (About 30 DTMF messages should be enough). Monitor the Abis and Air i/f for FACCH messages.

RR response frame and ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’ message encapsulated in DL I-frame will appear on DL FACCH. For AMR/FR Call: The transmissions of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) as well as its retransmission after T200F expiries get repeated on Air i/f, if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. The RR response frames on DL FACCH are also repeated if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. For AMR/HR Call: Only the retransmission of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) after T200F expiry gets repeated on Air i/f, if the CMR is 4.75 kbps.



Unlock the neighbour BTS using the MML command: ZEQS:BTS=<bts num>:U;

The neighbour BTS gets Unlocked

Again make a speech call in the source BTS and terminate it in a separate test cell. The call type and MS type are as defined in the test case.


DN0694168 Issue 2-0


Input Expected Output At the target BTS set C/I conditions in downlink so that when call arrives at this BTS the downlink codec mode used, is the most robust codec of the ACS and also add interference with C/I~1-3 in uplink. Initiate inter-cell handover from source BTS to the target BTS by varying the signal level with the help of variable attenuators. Monitor the Abis and Air i/f for FACCH messages.

‘FACCH Repeat’ is enabled in the ‘ACCH control IE’ of the Channel Activation message at the target BTS. The target BTS sends PHYSICAL INFORMATION encapsulated in DL UI-frame and DL response frames on FACCH to the MS. The timer T3105 expires. The retransmission of DL UI-frame (carrying only PHYSICAL INFORMATION) due to expiry of T3105 timer gets repeated on Air i/f. Also For AMR/FR Call: All DL response frames on FACCH are repeated, if CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. For AMR/HR Call: Only the DL UA response frames on FACCH get repeated, if CMR is 4.75 kbps. Call is successfully handed over.

Case Ref

Source BTS Target BTS ACS for each BTS

Speech Codec

MS Type

HO Type

1. 4 Omni EDGE

4 Omni EDGE

12.2, 10.2, and 5.90

AFS Non-RSC

Super reuse TRX to Super reuse TRX

28.44 ASI with IUO - Uplink DTX Estimation and Estimation Validity with IUO

Purpose:

To ensure that the ASI capable BTS [Note 329] with IUO enabled does the estimation of UL DTX as well as the validation of this estimation all the time during the call and reports these values in the ‘DTXu-est’ and ‘DTXu-valid’ fields respectively in the Uplink Measurement IE of Measurement Result message on Abis i/f.






DN0694168 Issue 2-0







Input Expected Output Create a site with IUO configured as mentioned in the test case.



‘SACCH Repeat’ is Enabled and ‘SACCH Repeat Window (SRW)’ is present in the ‘ACCH Control IE’ element of the ‘Channel Activation’ messages. Call is successful.





Terminate the speech call. The speech call is terminated. Case Ref. Configuration Call on the TRX 1. 4 Omni EDGE Regular TRX

DN0694168 Issue 2-0


28.45 Scheduling of MI Messages on Air Interface

Purpose:

To ensure that when MI messages are supplied to the BTS and the hold off period [Note 330] has elapsed or the repeat period [Note 331] has elapsed then the BTS shall send a contiguous group of MI messages comprising N unique MI Indexes (where each MI message is followed by its repeat whenever DL SACCH repetition is in effect) chosen from consecutive entries in the schedule starting from MI Index = 0, where: N = min (4, M) and M is the number of MI messages in the schedule.

Note 330. If MI messages are supplied to the BTS, then BTS shall start transmission of the supplied MI messages on the traffic channel in SACCH period SPn+10 when the channel is deemed to have settled in SPn. The BTS shall deem the newly activated traffic channel to have settled in SACCH period SPn, where SPn-3 is the first SACCH period by the end of which at least two blocks (SACCH, FACCH or TCH) in total have been successfully decoded since receipt of the Channel Activation message.

Note 331. If MI messages are supplied to the BTS and 25 SACCH periods have elapsed following transmission of the original instance of the final message in the previous MI schedule, then the schedule shall be repeated.

Note 332. A SAPI = 3 frame takes precedence over the next message in the MI schedule (the MI schedule then resumes from where it left off). A SAPI = 3 frame takes precedence over the first message in the next block of the MI schedule (the start of the next MI block is deferred).

Note 333. The SI message repetition takes precedence over the first message in the next block of the MI schedule (the start of the next MI block is deferred).

Note 334. The SI message repetition takes precedence over the SAPI = 3 frame (which is deferred) which itself takes precedence over the start of the next MI schedule. The start of the next MI schedule is delayed by 2 SACCH periods to accommodate the SI message repetition and the pending SAPI = 3 frame.

Note 335. All test cases need to be executed with RSC mobiles.

Note 336. The default value of ‘Invalid BSIC Reporting’ at the GSM cell is ‘0’.Its value can be changed using MML command ZEHN.



DN0694168 Issue 2-0




Create many 3G neighbours BTSs to the BTS under test.

Neighbours are created successfully.



Monitor the Abis i/f. MI messages are sent to the BTS under test by the BSC.

Monitor the Air i/f. The MI messages are inserted between the SI messages sent on the downlink SACCH by the BTS exactly from the SACCH period SPn+10 onwards [Note 330].

Send multiple SMSs to the MS latched on to the BTS under test so that at least one of the SAPI = 3 frame takes precedence over the next message in the MI schedule. Monitor the Air i/f.

The SAPI=3 frame gets inserted between the SI & MI messages on Air i/f and delays the occurrence of MI message by one SACCH period [Note 332]

Add interference on Air i/f in the downlink and start increasing it slowly until the repetition starts. Monitor the Air i/f.

The MS, being unable to decode the downlink SACCH, sets the SACCH Repeat Request (SRR) to 1 and sends it to the BTS in the L1 header of the uplink SACCH. The SI messages on downlink SACCH get repeated and the scheduling of MI messages on the downlink SACCH is delayed by one SACCH period due to repetition. The MI messages also get repeated.


The SAPI=3 frame gets inserted between the SI & MI messages on Air i/f and delays the occurrence of MI message [Note 334].

Remove the interference from the downlink direction on Air i/f and monitor the Air i/f. Wait for few seconds.

The repetition of SI & MI messages on downlink SACCH is stopped. The scheduling of MI messages on Air i/f is stopped.

Wait for another few seconds and then monitor the Air i/f.

The MI messages are scheduled again on the downlink SACCH on Air i/f.depending upon the time elapsed after the last instance of the original MI message in the previous MI schedule [Note 331].

Terminate the speech call. The speech call is terminated. Start a speech call as specified in the test case and monitor the Abis i/f.


Monitor the Abis i/f. MI messages are sent to the BTS under test by the BSC.

Monitor the Air i/f. The MI messages are inserted between the SI messages sent on the downlink SACCH by the BTS exactly from the SACCH period SPn+10 onwards [Note 330].

DN0694168 Issue 2-0


Input Expected Output Add interference on Air i/f in the uplink and start increasing it slowly until the repetition starts. Monitor the Air i/f.

The BTS, being unable to decode the uplink SACCH, sets SACCH Repeat Order (SRO) to 1 and send it to the MS in the L1 header of the downlink SACCH. The SI messages on downlink SACCH get repeated and the scheduling of MI messages on the downlink SACCH is delayed by one SACCH period due to repetition. The MI messages also get repeated.


The SAPI=3 frame gets inserted between the SI & MI messages on Air i/f. The occurrence of MI message is delayed by two SACCH periods [Note 334].

Remove the interference from the uplink direction on Air i/f and monitor the Air i/f. Wait for few seconds.

The repetition of SI & MI messages on downlink SACCH is stopped. The scheduling of MI meassages on Air i/f is stopped.

Wait for another few seconds and then monitor the Air i/f.

The MI messages are scheduled again on the downlink SACCH on Air i/f.depending upon the time elapsed after the last instance of the original MI message in the previous MI schedule [Note 331].

Terminate the speech call. The speech call is terminated. Case Ref. Configuration Call Type 1. 4 Omni EDGE AFS 2. 4 Omni EDGE AHS

28.46 ASI with EGPRS - SACCH Repetition with EGPRS

Purpose: To ensure that SACCH messages are repeated (as per the repetition criteria on a timeslot used previously for EGPRS data transfer Note 337. All test cases need to be done with SACCH Repeat Window set as 15 unless otherwise stated. Its value can be set using MML command ZEEQ.

Note 338. Timeslot 7 must always be left unlocked for synchronisation purposes. (E) GPRS transfers are loaded from timeslot 7 forward. In order to test other timeslots it is necessary to first occupy timeslot 7 with another transfer, then begin the transfer under test. Lock up all timeslots except timeslot 7 and the timeslot under test. To test timeslot 6 in the downlink, it is acceptable to have a downlink transfer on two timeslots, one of which is timeslot 6.


DN0694168 Issue 2-0


Input Expected Output Create a site as mentioned in the test case and Dynamic A-bis is enabled.


Lock all timeslots except timeslot 7 and timeslot under test. Establish extra transfer on timeslot 7 if necessary. [See Note 338.]

Timeslot 7 and one another timeslot remains unlocked on the TRX under test. All other timeslot in the sector are locked.

Set up EGPRS data transfer of 1MB file once in uplink then again in downlink direction on the timeslot under test using TCP/IP.

File transfer begins.

Monitor A-bis for PCU frames. PCU MASTER DATA FRAME shows data is sent. No retransmissions are seen.

After completing the data transfer start a speech call as defined in the test case on the timeslots previously used for EGPRS transfer. The call type is as defined in the test case. Monitor the Abis i/f.

‘SACCH Repeat’ is enabled and ‘SACCH Repeat Window (SRW)’ is present in the ‘ACCH Control IE’ of the ‘Channel Activation’ messages. Call is successful.




Remove all the source interference from downlink direction.

Call is still continued.

Again add interference on Air i/f in the uplink direction and start increasing it slowly until the repetition starts. Analyse the Air i/f messages.








DN0694168 Issue 2-0


Input Expected Output Case Ref. BTS Configuration Channel Configuration / Speech Codec 1. 4 Omni EDGE TCHF / AFS 2. 4 Omni EDGE TCHD / AHS

28.47 ASI with EGPRS - Downlink FACCH Repetition with EGPRS

Purpose:

To ensure that DL FACCH messages are repeated (as per the repetition criteria) on a timeslot used previously for EGPRS data transfer.

Note 340. Timeslot 7 must always be left unlocked for synchronisation purposes. (E) GPRS transfers are loaded from timeslot 7 forward. In order to test other timeslots it is necessary to first occupy timeslot 7 with another transfer, then begin the transfer under test. Lock up all timeslots except timeslot 7 and the timeslot under test. To test timeslot 6 in the downlink, it is acceptable to have a downlink transfer on two timeslots, one of which is timeslot 6.



Input Expected Output Create a site as mentioned in the test case and Dynamic A-bis is enabled.



ARLT=64 is set.



Lock all timeslots except timeslot 7 and timeslot under test. Establish extra transfer on timeslot 7 if necessary. (See Note 340)

Timeslot 7 and one another timeslot remains unlocked on the TRX under test. All other timeslot in the sector are locked.

Setup EGPRS data transfer of 1MB file once in uplink then again in downlink direction using TCP/IP.

File transfer begins.

Monitor A-bis for PCU frames. PCU MASTER DATA FRAME shows data is sent. No retransmissions are seen.

DN0694168 Issue 2-0


Input Expected Output After completing the data transfer make a speech call on the timeslot previously used for EGPRS transfer and terminate it in a separate test cell. The call type is as defined in the test case. Monitor the Abis i/f.


During the AMR call, C/I conditions are gradually changed in downlink at the BTS under test to manipulate the air interface so that the downlink codec mode changes and reaches the most robust codec of the ACS.



RR response frame and ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’ message encapsulated in DL I-frame will appear on DL FACCH. For AMR/FR Call: The transmissions of DL I-frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) as well as its retransmission after T200F expiries get repeated on Air i/f, if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. The RR response frames on DL FACCH are also repeated if the CMR is 4.75, 5.15 or 5.90 kbps and is the most robust codec of the ACS. For AMR/HR Call: Only the retransmission of DL I-CMD frame (carrying ‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’) after T200F expiry gets repeated on Air i/f, if the CMR is 4.75 kbps.

Remove all the interferences and disconnect the call.


Case Ref ACS BTS Configuration Channel Configuration / Speech Codec

1. 4.75 and 10.2 4 Omni EDGE TCHD / AHS 2. 5.90 and 12.2 4 Omni EDGE TCHF / AFS

28.48 Downlink FACCH Power Increment

Purpose:

To ensure that the power of a DL FACCH burst is incremented for a Non-RSC MS when the FACCH Power Increment criteria is met.


Note 342. In case of AFS, two full-rate traffic channels are left unlocked whereas in case of AHS, two half-rate traffic channels are left unlocked.

Note 343. The power of FACCH burst is incremented only for Non-RSC MS.

DN0694168 Issue 2-0


Note 344. The interference should be added to such an extent that the calls do not get dropped but the some loss of downlink FACCH messages is ascertained.

Note 345. Unless otherwise stated specified non-BCCH TRX transmission power should be at least 2dB lower than BCCH TRX transmission power.





Lock all the traffic channels except two traffic channels [Note 310].

Only two traffic channels are unlocked in the sector.

Start speech calls for both RSC and Non-RSC MSs as specified in the test case and terminate the calls in some other cell. Monitor the Abis i/f.

For RSC MS ‘FACCH Power Increment=Disabled’, ‘FACCH Repeat=Disabled’ and ‘RSC MS=TRUE’ are present in the ‘ACCH Control IE’ element of the ‘Channel Activation’ message. For Non-RSC MS ‘FACCH Power Increment=Disabled’, ‘FACCH Repeat=Disabled’ and ‘RSC MS=FALSE’ are present in the ‘ACCH Control IE’ element of the ‘Channel Activation’ message. Calls are successful.

Now add interference [Note 311] in downlink to the TCHs on which the calls are going on and start sending DTMF messages to generate FACCH traffic by pressing the keys on keypad of the MS (About 30 DTMF messages should be generated for both MSs). Monitor the Abis and Air i/f for FACCH messages.

‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’ message encapsulated in DL I-frame will appear on DL FACCH.

Compare the number of downlink FACCH messages received by both type of MSs, i.e., RSC and Non-RSC MSs.

The number of downlink FACCH messages received by both type of MSs is nearly same. Due to interference, there will be some loss of FACCH messages by both type of MSs and the losses for both MSs should nearly be same.

Remove the interference and disconnect the speech calls made by both RSC and Non-RSC MSs.

The speech calls are disconnected.

DN0694168 Issue 2-0


Input Expected Output Enable ‘FACCH Power Increment’ and start speech calls again for both RSC and Non-RSC MSs as specified in the test case and terminate the calls in some other cell. Monitor the Abis i/f.

For RSC MS ‘FACCH Power Increment=Disabled’, ‘FACCH Repeat=Disabled’ and ‘RSC MS=TRUE’ are present in the ‘ACCH Control IE’ element of the ‘Channel Activation’ message. For Non-RSC MS ‘FACCH Power Increment=Enabled’, ‘FACCH Repeat=Disabled’ and ‘RSC MS=FALSE’ are present in the ‘ACCH Control IE’ element of the ‘Channel Activation’ message. Calls are successful

Now add interference [Note 311] in downlink to the TCHs on which the calls are going on and start sending DTMF messages to generate FACCH traffic by pressing the keys on keypad of the MS. (About 50 DTMF messages should be generated for both MSs). Monitor the Abis and Air i/f for FACCH messages.

‘Start DTMF Acknowledge’ or ‘Stop DTMF Acknowledge’ message encapsulated in DL I-frame will appear on DL FACCH.

Compare the number of downlink FACCH messages received by both type of MSs, i.e., RSC and Non-RSC MSs.

Depending on expected output (FACCH Power Increment) for specific case (see last column below) : TRUE: The number of downlink FACCH messages received by the Non-RSC MS is noticeably greater than that received by the RSC MS. This result is achieved because there is an increment in power of the FACCH bursts only to the Non-RSC MS [Note 343]. FALSE: The number of downlink FACCH messages received by both type of MSs is nearly same.

Terminate all speech calls. The speech calls are terminated.

DN0694168 Issue 2-0



Configuration Input: Call Type/ Channel Configuration

Input: BCCH power= TRXMAXpower

Input: ACS [kbps]

Input: Kind of TRX carrying call

Output: FACCH Power Increment

1. 4 Omni EDGE AFS / TCHH on BCCH TRX and TCHF on Non-BCCH TRX

FALSE 4.75 BCCH and non BCCH

TRUE

2. 4 Omni EDGE AFS / TCHF FALSE 5.15 non BCCH

TRUE

3. 4 Omni EDGE AHS / TCHH FALSE 4.75 non BCCH

TRUE

4. 4 Omni EDGE AFS / TCHF FALSE 5.9 non BCCH

TRUE

5. 4 Omni EDGE AHS / TCHH FALSE 4.75 non BCCH

TRUE

6. 4 Omni EDGE AFS / TCHF TRUE 4.75 non BCCH

FALSE

7. 4 Omni EDGE AFS / TCHF FALSE 5.15 BCCH FALSE 8 4 Omni EDGE1 AFS / TCHF FALSE 4.75 non

BCCH TRUE

1Use 7390 and 7270 MS, UL DTX is OFF also ensure that voice quality is good. Also listen to speech and verify that there is no distortion.

29. COMMON MAL FOR BOTH PGSM AND EGSM FREQUENCIES

Purpose:

The purpose of these test cases is to check that common MA list is possible for P-GSM and E-GSM frequencies.

Input Expected Output Configure site as defined in test case. Site is in supervisory state.

Lock the sector. Sector is locked.

Create MA list containing both P-GSM and E-GSM frequencies.

Common MA list is created.

Attach MA list to the sector. MA list is attached successfully.

Unlock the sector. Sector comes into supervisory state.

Observe messages on TRX signalling. ‘BTS CONF DATA’ contains MA list attached to the sector.

DN0694168 Issue 2-0


Setup a MS- MS speech call in the sector. Call is initiated.

Observe messages on TRX signalling. ‘Assignment Command’ message contains MA list assigned to MS. Call is successful

Enable GENA=Y in the sector. GPRS is enabled in the sector.

Start GPRS data transfer in downlink direction.

GPRS data transfer starts.

Observe messages on TRX signalling. ‘Immediate Assignment’ message contains MA list assigned to MS. Data transfer is successful.

Case Ref Configuration Used /Site Type Hopping Mode 1. 4 Omni EDGE, UltraSite & Metro Site RF-hopping

30. DIRECTED RETRY

Purpose:

The purpose of these test cases is to check that directed retry is successful and when there is temporarily congestion in the serving cell, call does not get dropped but assigned to neighbour cell.

Note 346. Activate Directed Retry in the BTS: ZEQF:BTS=<bts_id>:DR=Y;

Note 347. Set the Directed Retry target cell list creation time minimum and maximum values: ZEQF:BTS=<bts_id>:MIDR=x;

ZEQF:BTS=<bts_id>:MADR=x;

The value of the timer MADR should be smaller than the value of the timer T10. If the MADR value is more than the T10 value, the call is released after the T10 timer has stopped and the MADR is still ticking.

Note 348. If the Directed Retry threshold method is going to be used, set the directed retry method (DRM) parameter: ZEQF:BTS=<bts_id>:DRM=1;

Note 349. At least one neighbour should be defined for the serving cell to enable handover of speech calls from the serving cell to the target cell.

Note 350. The parameter Directed Retry threshold (DRT) (set for each of the adjacent cells) is the level which the signal level of the adjacent cell must exceed before the directed retry to the adjacent cell is possible.

DN0694168 Issue 2-0


Set the Directed Retry Threshold parameter: ZEAC:BTS=xx::ABTS=xx::DRT=xx;

Note 351. If SDCCH handover is supported make sure that it is disabled:

ZEHG:BTS=1:ESD=N;

Input Expected Output Lock all the traffic channels of all the TRXs in the serving cell.

All the traffic channels of the serving cell are locked.

Setup a MS – MS speech call in the serving cell.

Call is initiated.

Observe assignment of SDCCH on TRX signalling of Abis interface for originating MS.

SDCCH of serving cell is assigned to the originating MS which can be verified in the respective ‘CHAN. ACT.’ message sent by the BSC to the serving cell.

Observe assignment of TCH on TRX signalling of Abis interface for originating MS.

Directed retry comes into act and traffic channel of neighbouring cell is assigned to the originating MS which can be verified in the respective ‘CHAN. ACT.’ message sent by the BSC to the neighbour cell

Verify that a traffic channel is allocated to the originating MS.

Assignment of a traffic channel is verified by ‘Handover Complete’ message sent by MS to the BSC.

Observe assignment of SDCCH on TRX signalling of Abis interface for terminating MS.

SDCCH of serving cell is assigned to the terminating MS which can be verified in the respective ‘CHAN. ACT.’ message sent by the BSC to the serving cell.

Observe assignment of TCH on TRX signalling of Abis interface for terminating MS.

Directed retry comes into act and traffic channel of neighbouring cell is assigned to the terminating MS which can be verified in the respective ‘CHAN. ACT.’ message sent by the BSC to the neighbour cell.

Verify that a traffic channel is allocated to the terminating MS.

Assignment of a traffic channel is verified by ‘Handover Complete’ message sent by MS to the BSC

Monitor audio quality during handover of speech calls.

Audio quality is good and no distortion or additional disturbing noise is heard during handover of speech calls. Call is successful

Case Ref Serving Cell Target Cell 1. 4 Omni Mixed-3e 4 Omni GSM 2. 4 Omni GSM 4 Omni EDGE

DN0694168 Issue 2-0


31. INTRACELL SDCCH HANDOVER WITH SMS

Purpose:

The purpose of these test cases is to check that SDCCH handovers are successful when SMS is sent from one MS to another. During SMS sending and receiving, static and dynamic SDCCH are activated and handovers are performed over them.

Note 352. SDCCH handover is enabled at the BSC using script or through MML command.

Note 353. Dynamic_SDCCH feature is ON at the BSC.

Input Expected Output Send SMS from a MS in idle state to another MS in idle state.

SMS sending is initiated.

Observe messages on TRX signalling for first SDCCH sub-channel assignment.

’Immediate assignment’ message for call setup contains TSL and SDCCH Sub-channel allocated for SMS sending.

Observe messages on TRX signalling for SDCCH handover.

BSC will send ‘Assignment Command’ to MS for new SDCCH sub-channel. SMS sent successfully.

Monitor audio quality during reception of SMS. Audio quality is good and no distortion or additional disturbing noise is heard during reception of SMS. SMS is received successfully.

Reserve static SDCCH of BCCH TRX with the help of script or MML command.

Static SDCCH of BCCH TRX is reserved.

Send SMS from a MS in idle state to another MS in idle state.

SMS sending is initiated.

Observe messages on TRX signalling for first SDCCH sub-channel assignment.

A traffic channel is used as a Dynamic SDCCH. ’Immediate assignment’ message for call setup contains TSL and SDCCH Sub-channel allocated for SMS sending.

Observe messages on TRX signalling for SDCCH handover.

BSC will send ‘Assignment Command’ to MS for new SDCCH sub-channel. SMS sent successfully.

Monitor audio quality during reception of SMS. Audio quality is good and no distortion or additional disturbing noise is heard during reception of SMS. SMS is received successfully.

Case Ref Configuration Used Hopping Mode 1. 4 Omni EDGE, UltraSite BB-hopping

2. 4 Omni EDGE, MetroSite RF-hopping

DN0694168 Issue 2-0


32. NETWORK CONTROLLED CELL RE-SELECTION

Purpose:

The purpose of these test cases is to check that Network Controlled Cell Re-selection (NCCR) takes place successfully.

Note 354. NCCR configured with NC0 Broadcast using ZEEM::NCM=2;

Note 355. The MS is in cabled environment receiving signals from both the source and the target

BTS with variable attenuators connected in the path between BTS and MS for both

source and target BTS.

Note 356. The signal of target BTS is attenuated to a greater extent so that MS remains camped

on the source BTS only.

Note 357. Define at least one neighbour for source BTS.

Input Expected Output Start EGPRS data transfer of 10 Mb file in downlink direction.

Data transfer starts successfully

Observe UL PCU frames for measurement messages reported by MS on Abis interface.

Data Frames are exchanged on Abis which confirms that data transfer has been initiated. No Packet Measurement reports are sent

Attenuate the signal of source BTS and simultaneously reduce the attenuation for the target BTS so that the level of the target BTS seen by the mobile is greater than that of the source BTS.

The signal level can be altered successfully using the variable attenuators.

Observe the messages exchanged over Abis interface.

Following messages are exchanged between MS and PCU: 1. PACKET MEASUREMENT ORDER from Network. 2. PACKET MEASUREMENT REPORT from MS. 3. PACKET CELL CHANGE ORDER is sent from network to MS. 4. PACKET CONTROL ACK is sent from MS to network. The contents of the above messages are consistent on the Abis interface.

Observe the status of the PS data transfer.

Since the level seen by the mobile is greater for the target BTS, cell re-selection takes place to the target BTS. Data transmission continues after cell

DN0694168 Issue 2-0


reselection and received data is accurate. The throughput is not affected significantly by the cell re-selection procedure.

Case Ref Source Cell Target Cell 1. 4 Omni EDGE 2+2 EDGE

33. STIRC

33.1 Enable/Disable STIRC from BSC

Purpose:

The purpose of this testcase is to check that STIRC can be enabled/disabled successfully.


Refer this document for details of configurations BTS Configurations definitions.

Input Expected Output Enable STIRC in the sector by MML command ZEQM: BTS=<BTS ID>: STIRC=Y;


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


STIRC information is sent to the EQDSP in the INI message for both the sectors.

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

Call is successful. In case of GPRS, file transfer is successful.

Disable STIRC in the sector by MML command ZEQM: BTS=<BTS ID>: STIRC=N;

STIRC is disabled successfully.

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


STIRC information is sent to the EQDSP in the INI message for both the sectors.

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

Calls are successful In case of GPRS, file transfer is successful.

Case Ref. Type of Call Configuration 1 GPRS 4 omni

DN0694168 Issue 2-0


33.2 STIRC enabled sectors and IDD/4UD

Purpose: The purpose of this test case is to check that STIRC can be enabled in an IDD /4UD configuration. Equipment and BTS Set-Up Site - as per configuration defined in figure 18



Monitor O&M messages on the Abis Enable STIRC for the sectors using MML command: ZEQM:BTS=<bts no>:STIRC=Y;


Speech calls are made in the sectors. Remove an Auxiliary RX cable from the TRX with ongoing call. Replace the auxiliary RX cable Remove the Main RX cable from the TRX with ongoing call. Replace the Main RX cable

Calls are successful and speech quality is checked on the Abis trace. Calls are unaffected Calls are unaffected

Case Ref. Configuration Band Hopping 1 IDD/4UD - 2+2+2 (EDGE) 900 BB

DN0694168 Issue 2-0


MTRX

MTRX

ATRX

ATRX

MTRX = Main TRX

ATRX = Auxiliary TRX

MHAMHA

4-WAY DIVERSITY UPLINK AND IDD DOWNLINK

•2+2+2

• Four feeders /cell

UltraSite IDD Configurations

Figure 18

33.3 STIRC enabled sector and Intelligent Shutdown

Purpose: The purpose of this test case is to check that STIRC can be enabled after NONE and BCCH shutdown modes have been executed and the acknowledgement is sent to the BSC on the Abis by the BTS.

Equipment and BTS Set-Up:Site - as per configuration defined in test case.

DN0694168 Issue 2-0



The BTS is in WO state

The mains breakdown alarm with both the timers is generated for NONE shutdown mode. Refer Note [Note 166]


For NONE shutdown mode – after the expiry of timers: After the expiry of N-TIM all non-BCCH Slave TRX’s are put to BL-PWR state at the BSC and BTS Manager shows the status as shutdown in properties while the TRXs disappear from the BTS Manager Equipment View. The Master TRX and the BCCH TRX’s remain operational.

After the expiry of B-TIM the BCCH TRX is BL-PWR at the BSC and BTS Manager shows the status of the shutdown BCCH TRX in properties.

Enable STIRC for the sector using MML command: ZEQM:BTS=<bts no>:STIRC=Y; Monitor O&M messages on the Abis.

The BSC sends the STIRC enable for the sector in the BTS_CONF_DATA (BTS-id, STIRC mode ‘ON’). The BTS sends ACK, on BTS_ACK to the BSC.

Monitor the status of the BTS using BTS manager.

During Intelligent Shutdown, the shutdown TRX’s shall get powered off. The TRX’s shall no longer report to the BTS Manager and therefore shall not be visible on the equipment view of the BTS Manager. The administrative state of the TRX’s for the shutdown TRX ‘s shall not be possible to be verified.

The exception to this rule shall be the Master TRX. This shall remain powered even in the shutdown mode. The Master TRX of the Master Cabinet shall also power off the Master TRX of the Slave cabinets, if all TRX’s in the Slave cabinet are in the Shutdown mode. The Master TRX when left powered during shutdown mode shall be visible on the equipment view and could be verified as shutdown.

The TRX’s not in shutdown mode shall be shown as supervisory.

The TRX’s could be verified as being in shutdown or supervisory mode on the BTS Manager using the objects/properties command.

The mains Breakdown alarm is cancelled All shutdown TRX’s are restarted and back in WO. Speech calls are made on all TRXs. Calls are successful. Case Ref. Configuration Shutdown mode Hopping 1 4 (EDGE), Preferred BCCH on

Master TRX NONE BB

DN0694168 Issue 2-0


33.4 STIRC enabled sector and hopping modes

Purpose: The purpose of this test case is to check that STIRC can be enabled on a BTS with hopping.

Equipment and BTS Set-Up: as per configuration defined in test case.



Enable STIRC on the sector using MML command: ZEQM:BTS=<bts no>:STIRC=Y; Monitor O&M messages on the Abis


Speech calls are made. Calls are successful Case Ref. Configuration Band Hopping 1 4 OMNI (EDGE) Any RF

DN0694168 Issue 2-0


Appendix A – Antenna Hopping Monitoring To monitor the antenna hopping a similar set-up to figure 3 is used. The variable attenuators for each antenna are set to different attenuations. This allows different power levels to be displayed at the spectrum analyser for the separate antennas. If antenna hopping is disabled for the configuration (sector), the same antenna would be used for the call and therefore the powered levels would remain the same.

When using the set-up to monitor the R-AH hopping (cyclic or Random), two frequencies from the MA List are viewed on the spectrum analyser to verify Antenna hopping. The MS is also used to verify that all the frequencies are being used.

Antenna Hopping test equipment setup for a 4-antenna configuration

The Frequency to be used is entered as the centred frequency and the Span is set to Zero. The Amplitude (Amplitude\Scale, Amplitude\Ref) and the Sweep function may be used to modify the display settings to best view the trace.

DN0694168 Issue 2-0


Appendix B

Site Sync Improvement with E-Cell

Note that not all Site Sync configurations can be combined with E-Cell. (ERACH and BCCH need to be in the same cabinet.)

UltraSiteSlave

N-TRX

N-TRX

N-TRX

N-TRX

TRX

BCCH TRX

UltraSiteSlave

BCCH N-TRX

N-TRX

TRX

TRX

E-TRX

ERACH E-TRX

SEG 1

SEG 2

LMU

DN0694168 Issue 2-0


Disclaimer

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given “as is” and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

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

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

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

Copyright © Nokia Siemens Networks 2009. All rights reserved.

cx(m)7 common telecom regression test specification

Documents