System Test STIRC DN0691283x1x0xen

8/22/2019 System Test STIRC DN0691283x1x0xen

http://slidepdf.com/reader/full/system-test-stirc-dn0691283x1x0xen 1/84

Nokia MetroSite EDGE Base Station

System Test Specification for STIRC in BTS SW Release CXM5

DN0691283Issue 1-0 en

©Nokia CorporationNokia Proprietary and Confidential

1 (84)




The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is intended for theuse of Nokia's customers only for the purposes of the agreement under which the document issubmitted, and no part of it may be reproduced or transmitted in any form or means withoutthe prior written permission of Nokia. The document has been prepared to be used by

professional and properly trained personnel, and the customer assumes full responsibilitywhen using it. Nokia welcomes customer comments as part of the process of continuousdevelopment and improvement of the documentation.

The information or statements given in this document concerning the suitability, capacity, orperformance of the mentioned hardware or software products cannot be considered bindingbut shall be defined in the agreement made between Nokia and the customer. However,Nokia has made all reasonable efforts to ensure that the instructions contained in thedocument are adequate and free of material errors and omissions. Nokia will, if necessary,explain issues which may not be covered by the document.

Nokia's liability for any errors in the document is limited to the documentary correction of errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDINGMONETARY LOSSES), that might arise from the use of this document or the information in it.

This document and the product it describes are considered protected by copyright accordingto the applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

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

Copyright ©Nokia Corporation 2007. All rights reserved.

Hereby, Nokia Corporation declares that this Nokia Base Station is in compliance withthe essential requirements and other relevant provisions of Directive: 1999/5/EC. Theproduct is marked with the CE marking and Notified Body number according to theDirective 1999/5/EC.

2 (84) ©Nokia CorporationNokia Proprietary and Confidential




Contents

Contents

1 About this document .............................................................................5

1.1 Scope.......................................................................................................5 1.2 Hardware requirements............................................................................7 1.3 Software requirements .............................................................................8 1.4 Specialist test equipment requirements ...................................................9

2 Test cases .............................................................................................10 2.1 Interaction with other features/SW versions...........................................10 2.1.1 STIRC and Intelligent Shutdown............................................................11 2.1.2 STIRC-enabled sectors and Multi-BCF ..................................................17 2.1.3 STIRC-enabled sector and hopping modes...........................................19 2.1.4 STIRC-enabled sector and RF hopping using GSM HW .......................19 2.1.5 STIRC-enabled sector and BB hopping using GSM HW .......................20

2.1.6 STIRC-enabled sectors and DFCA ........................................................21 2.1.7 STIRC-enabled sectors and RSSI..........................................................22 2.1.8 Intra-Cell Synchronous Handovers in a STIRC-enabled

Common BCCH configuration................................................................23 2.1.9 EMR measurement reporting and comparison of STIRC & IRC ............25 2.1.10 STIRC-enabled sector and EPCR ..........................................................29 2.1.11 STIRC-enabled sectors and EGPRS Link Adaptation............................31 2.2 RACH.....................................................................................................33 2.2.1 Ghost (P)RACH with STIRC enabled.....................................................33 2.2.2 RACH load whilst BSC background software loading with

STIRC enabled.......................................................................................37

2.2.3 PRACH load whilst BSC background software loading withSTIRC enabled.......................................................................................38 2.3 Voice, Data, GPRS and EGPRS ............................................................40 2.3.1 Enable STIRC whilst AFS, AHS and CS Data calls are ongoing...........40 2.3.2 Disable STIRC whilst AFS, AHS and CS Data calls are ongoing ..........41 2.3.3 Enable and Disable STIRC in the first sector whilst AFS, AHS

and CS Data calls are ongoing in the second sector .............................41 2.3.4 Enable STIRC whilst Packet Data calls are ongoing..............................42 2.3.5 Disable STIRC whilst Packet Data calls are ongoing.............................43 2.3.6 Enable and Disable STIRC in the first sector whilst Packet Data

calls are ongoing in the second sector...................................................44 2.4 Stability of a STIRC-enabled BTS Site under load conditions................45

2.5 Recovery Actions ...................................................................................46 2.5.1 Recovery on BTS Manager Actions with STIRC enabled......................46 2.5.2 Recovery on BSC Actions with STIRC enabled.....................................48 2.5.3 Recovery on HW Actions .......................................................................51 2.6 Miscellaneous ........................................................................................69 2.6.1 Stability with STIRC enabled..................................................................69

2.6.3 Enable STIRC via NetAct.......................................................................74 2.6.2 TRX Test with STIRC enabled from the BSC and BTS Manager ..........71

2.6.4 Enable STIRC during background software downloading......................75 2.6.5 STIRC enabled sector and FACCH........................................................76



3 (84)




References ........................................................................................... 78

Appendix A: Feature/HW/Configurat ion Matrix ................................ 79

Appendix B: RF set-up to establish known C/I condi tions.............. 81

Appendix C: Measuring Co-Channel C/I............................................ 84





About this document

1 About this document 1.1 Scope

This document incorporates System test phase and defines the test cases for the

Space-Time Interference Rejection Combining (STIRC) feature of BTS

software release CXM5 for MetroSite. The test cases are used to verify that the

BTS configured with the feature works as specified.

The document tests the STIRC capacity licensing feature BSS20494 and BTS

level requirements as defined in BSS20063. It is assumed that the RF

Performance of the Algorithm has been verified prior to this test phase. The

STIRC license is a BSS level feature that enables/disables the STIRC BTS

feature.

The STIRC capacity licensing feature is implemented by the O&M SW in both

the BTS and the BSC. The STIRC features are to be implemented for the EDGE

Baseband DSP SW in the UltraSite/MetroSite BTSs.

The comparison testing of CX4.1 (IRC) and CX5 (STIRC) will be carried out in

the RF performance test phase.

Note 1.

All test cases shall be performed using BSC SW S12 unless otherwise stated.

It is assumed that the STIRC licence capacity for STIRC-enabled TRXs will not

be exceeded in the lab network.

Note 2.

At the BSC, Base Transceiver Stations (sites) are seen as BCFs. Sectors are

referred to as BTS. This principle is followed in the test descriptions in this

document.



5 (84)




Note 3.

All test cases are performed with BTS Manager connected, unless otherwise

stated.

Note 4.

For all tests that require TRX test to be run, the PMAX value should be set as

maximum (that is, 0).

Note 5.

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

TRX operates with Telecom functions only.

The Master TRX is always located in slot 1 and slave TRXs in slots 2 -4.Both the Master TRX and Slave TRX can be the BCCH TRX or NON BCCH

TRX.

BSS8103: In Nokia MetroSite BTS, the Master TRX is by default not a BCCH

TRX, unless it is defined as the preferred BCCH TRX.

Note 6.

For a Nokia MetroSite BTS, the TRX test can be executed with Pseudo BB

hopping configurations.

Note 7.

An invalid BB Hopping configuration exists in a sector that has TRXs of

different power types in the same hopping group. That is, GSM/EDGE HVTx

(5W) + CTxA (10W) in the same BTS.





About this document

Note 8.

The maximum number of MetroSite cabinets combined is three and the total

length of a bus cable between two cabinets is limited to five metres.

The maximum number of installed TRXs can be up to 12.

The first cabinet in the chain is called the Master cabinet; further cabinets in the

chain are called Slaves.

Cabinet Master TRXs are located in position 1, logical TRX 5 and 9 in a 3

cabinet chain.

BTS Manager can be connected at any one of the cabinets. However, it is

recommended to connect only to the Chain Master cabinet. Only one BTS

Manager can be connected at the same time.

Note 9.

All test cases must be performed with 2-way Rx diversity enabled at the BSC,

unless otherwise stated.

1.2 Hardware requirements

The following HW configurations are used during testing:

• GSM TRX Units HVTx (5W), VTxA (1W)

• EDGE TRX Units WTxA (5W), CTxA (10W)

• GSM/EDGE (HVTx + WTxA or HVTx + CTxA in the same BTS)

• Low Power Supply unit: VSxA

• High Power Supply unit: HVSx/CVSx

• High Power Fan unit: HVMF

• Low Power Fan unit: VMF

A cabinet can be configured as a dual-band BCF, which can use GSM 800 +

1900 bands, or GSM 900 + 1800 bands. Each sector has to be configured with

the same band TRXs.

Note 10.

If there is CVSx, HVSC or HVSx12 PSU and HVMF Fan present in a single

cabinet, then there is no limitation on the number of TRX units or configuration

of TRX units that can be supported.

However, there are configuration limitations which result in a TRX shutdown

using configurations outside the above statement when using low power VSxA

and VMF with high power GSM/EDGE TRX units.



7 (84)




Other Network Elements

• BSC

• Core Network with GPRS and EDGE capabilities

• 1 LMU and associated cables

Mobile stations Feature Specific options

Speech channels FR, HR, EFR

Single data channels 9600, 14400 Non-Transparent

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

GPRS Class B and Class C, Multi, PBCCH Support

EGPRS Class B and Class C, Multi, PBCCH Support

EGPRS Channel Request on PBCCH and BCCH

Adaptive Multi-Rate AMR FR and HR

General SMS MO and MT

Enhanced MeasurementReports

EMR Capable

PC applications

• Internet browser

• FTP, UDP software

• Terminal Emulator

1.3 Software requirements

• SiteWizard 5.0

• LMU Manager 4.4

• Latest available Pre-Release of CXM5 containing the feature under test

• LMU SW 4.4

• BSC S12 SW





About this document

1.4 Specialist test equipment requirements

The following test equipment is required in some test cases:

• Assortment of combiners

• Attenuators

• Terminators

• Signal Generator

• Spectrum Analyser

• GSM Protocol Analyser

• GPRS/EGPRS laptop

• (HS)CSD rig

• Traffic Generator



9 (84)




2 Test cases 2.1 Interaction with other features/SW versions

The following Notes apply for the test cases in this chapter. Additional Notes

are indicated wherever relevant.

Note 11.

The STIRC capacity licensing feature BSS20494 together with the STIRC

Feature BSS20063 is a BSS12-level feature that enables\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 commandZW7M

- STIRC capacity licensing is based on the number of TRXs at the BSC, which

have STIRC enabled.

The BSC will check that the operator has enough licenses for the TRXs in the

BTS objects, and checks that the allowed amount of STIRC-enabled TRXs is

not exceeded.

When enabled, STIRC technology is deployed in the UL by the BTS. When

disabled, the current IRC technology is deployed by the BTS.

Note 12.

STIRC can be enabled at any time without locking/unlocking the

TRX/sector/site. This indicates that BTS_CONF_DATA containing the

information field about STIRC enable/disable can be sent at anytime when the

BTS is running.





Test cases

2.1.1 STIRC and Intell igent Shutdown

Prior to executing this test case, refer to notes in the Scope section of this

document.

See the following Notes about the testing of Intelligent Shutdown and STIRC.

Note 13.

BCCH shutdown mode allows all the BCCH TRXs and all units required to

sustain BCCH transmission to remain operational. All non-BCCH TRXs are

shutdown.

For all test cases relevant to the BCCH Shutdown Mode, the service level is set

at the BSC accordingly using the MML command:ZEFM: <bcf _i d>: BBU=BCCH;

NONE shutdown mode allows the BTS common units and transmission units to

remain operational. All TRXs and non-essential units are shutdown.

For all test cases relevant to the NONE Shutdown Mode, the service level is set

at the BSC accordingly using the MML command:ZEFM: <bcf _i d>: BBU=NONE;

Note 14.

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

For all test cases relevant to the BCCH Shutdown Mode, the service level is setat the BSC accordingly using the MML command:ZEFM: <bcf _i d>: BBU=BCCH;



11 (84)




Note 15.

It is possible to activate Intelligent Shutdown with Timer Control with the

MML command ‘EFM’:

ZEFM: <bcf _i d>: BBU=<BTS bat t er y backuppr ocedur e>, NTI M=1, BTI M=3;

Where:

ZEFM:<BCF identification>:BBU<BTS battery backup

procedure>,NTIM<TRX shutdown timer>, BTIM<BCCH TRX shutdown

timer> where <TRX shutdown timer> and <BCCH TRX shutdown timer> are

given as a decimal number.

NTIM=1 means that after a mains failure, there is full service on the BTS site

for one minute before the service level is changed. This can be any value from 1

minute to 600 minutes.

BTIM=3 means that the BCCH TRXs will be maintained for three minutes after the non-BCCH TRXs are shut down, that is, until the BTIM timer expires. This

can be any value from 1 minute to 600 minutes.

The following figure illustrates the TRX’s powers and operational states during

shutdown procedure, when only transmission equipment is left alive.





Test cases

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

Power State Power State Power State Power State Power State

TRX 1 -BCCH

ON WO ON WO ON WO ON BL-SHD

OFF BL-PWR

TRX 2 - TCH ON WO ON BL-SHD

OFF BL-PWR

OFF BL-PWR

OFF BL-PWR

TRX 3 - TCH ON WO ON BL-SHD

OFF BL-PWR

OFF BL-PWR

OFF BL-PWR

Note 16.

Intelligent Shutdown can only be used if the BTS is supported by a battery

back-up system. This could be an Integrated BBU (IBBU), a separate UltraSite

Site Support system (SSS), or an external battery back-up system (external

BBU).

The UltraSite BTS must know if it is connected to a battery back-up system.

The UltraSite Site Support system, integrated BBU and external customer

specific BBU (fitted with a Q1 Adaptor) will be auto detected by the UltraSite

BTS.

In case an external battery back-up system (not fitted with a Q1 Adaptor) is

used, the BSC sends to the UltraSite BTS information that an EAC input is

connected to external battery backup device.

For all the Intelligent Shutdown test cases, it is assumed that the testing shall be

completed using an external BBU (EAC inputs) unless otherwise stated or if SSS or IBBU are not available. The PSM manager should be used to verify

what EAC line the Mains Breakdown alarm has been defined to. The EAC input

shall need to be set as detailed below for the same external input number as that

shown in the PSM manager.

ZEFX: <bcf _i d>: I NBR=<external I nputnumber >: ROU=MAI NS: POL=<OPEN - act i ve or CLOSED -i nact i ve>, SEV=AL3;

The PSM manager external input check:

• The Alarms/View option is chosen from the tools bar

• The properties option is chosen by right mouse clicking in the alarmswindow

• The 4.PDU option is chosen from the pull down menu

• The ‘Mains Breakdown Phase 1’ alarm is highlighted and right clicked.

• The settings option is chosen



13 (84)




Note 17.

The predefined external input for MetroSite for the Mains fail is EAC 01.

Note 18.

For all test cases relevant to the BCCH Shutdown Mode, the service level is set

at the BSC accordingly using the MML commandZEFM: <bcf _i d>: BBU=BCCH;

Note 19.

During Intelligent Shutdown, the shutdown TRXs shall get powered off. The

TRXs should no longer report to BTS Manager and therefore, shall not be

visible on the equipment view of BTS Manager. The Administrative state of the

TRXs for the shutdown TRXs shall not be possible to be verified.

The exception to this rule is the Master TRX. This should remain powered even

in the shutdown mode. The Master TRX of the Master Cabinet should also

power off the Master TRX of the Slave cabinets, if all TRXs in the Slave

cabinet are in the Shutdown mode. When left powered during the shutdown

mode, the Master TRX shall be visible on the equipment view and could be

verified as shutdown.

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

The TRX’s could be verified as being in Shutdown or Supervisory mode on

BTS Manager using the objects/properties command.

Note 20.

Antenna hopping is enabled in the sector with the following command:

ZEQE: BTS=<bt s i d>: AHOP=Y;

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 issent to the BSC on the Abis by the BTS.

Equipment and BTS Set-Up

As defined in the test case below.





Test cases

Input Expected Output

1. Create the BTS with the configurationmentioned in the test case. The BTS is in WO state.

2. The mains breakdown alarm with bothtimers is generated for the NONE/BCCHshutdown modes.

Alarm 7995 MAINS BREAKDOWN WITHBATTERY BACK-UP is reported at the BSC andBTS Manager.

For BCCH shutdown mode after the expiry of N-TIM:

After the expiry of N-TIM, all the non-BCCH Slave TRXs are put to BL-PWR state at the BSC, andBTS Manager shows the status as shutdown in

properties, while the TRXs disappear from theBTS Manager Equipment View. The Master TRXand the BCCH TRXs remain operational

For NONE shutdown mode – after the expiry of timers:

After the expiry of N-TIM, all non-BCCH Slave TRXs are put to BL-PWR state at the BSC, andBTS Manager shows the status as shutdown inproperties, while the TRXs disappear from theBTS Manager Equipment View. The Master TRX

and the BCCH TRX’s remain operational.

After the expiry of B-TIM:

At the BSC, the BCCH units are BL-PWR andBTS Manager shows the status of the shutdownBCCH TRXs in Properties. All the TSxx and BBsLEDs are amber.

3. Monitor O&M messages on the Abis.

4. Enable STIRC for the sector using MMLcommand:

ZEQM:BTS=<bts no>:STIRC=Y;

The BSC sends the STIRC enable for the sectorin the BTS_CONF_DATA (BTS-id, STIRC mode‘ON’).

The BTS sends ACK, on BTS_ACK to the BSC.

5. Monitor the status of the BTS using BTSmanager.

6. The mains breakdown alarm is cancelled All of the shutdown TRXs are restarted and backin WO state.

7. Speech calls are made on all TRXs. Calls are successful and speech quality ischecked on the Abis trace.



15 (84)





Case Ref. Configuration Shutdown mode Hopping

366451.03 4+4+4 (EDGE) Chain NONE BB366451.04 4+4+4 (EDGE) Chain BCCH RF

Purpose:

The purpose of this test case is to check that a STIRC-enabled sector can

shutdown in the NONE and BCCH shutdown modes, and the acknowledgement

is sent to the BSC on the Abis by the BTS.




1. Create a BTS with the configurationmentioned in the test case. The test canbe performed on the BTS without BBU.

The timers are activated with thefollowing command:

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

The BTS is in WO state.


3. Enable STIRC for the sector:


The BSC sends the STIRC enable for the sector inthe BTS_CONF_DATA (BTS-id, STIRC mode ‘ON’).







Test cases


4. The mains breakdown alarm with bothtimers is generated for the NONE/BCCH

shutdown modes.

Alarm 7995 MAINS BREAKDOWN WITH BATTERYBACK-UP is reported at the BSC and BTS Manager.

For BCCH shutdown mode after the expiry of N-TIM:

After the expiry of N-TIM, all the non-BCCH Slave TRXs are put to ‘BL-PWR’ state at the BSC and BTSManager shows the status as shutdown inproperties, while the TRXs will disappear from theBTS Manager Equipment View. The Master TRXand the BCCH TRXs remain operational.

For NONE shutdown mode after the expiry of timers:

After the expiry of N-TIM all non-BCCH Slave TRXsare put to ‘BL-PWR’ state at the BSC and BTSManager shows the status as shutdown inproperties, while the TRXs will disappear from theBTS Manager Equipment View. The Master TRXand the BCCH TRXs remain operational.

After the expiry of B-TIM:

After the expiry of B-TIM the BCCH TRX is BL-PWRat the BSC and BTS Manager shows the status of the shutdown BCCH TRX in properties.

5. Monitor the status of the BTS using BTSmanager. See Note 16.

The state of the TRXs is shown as defined inNote19.

6. The mains breakdown alarm iscancelled.

All of the shutdown TRXs are restarted and back inthe WO state.

7. Speech calls are made on all TRXs. Calls are successful and speech quality is checkedon the Abis trace.

Case Ref. Configuration Shutdown mode Hopping

366457.03 4+4+4 (EDGE) Chain NONE RF

366457.04 4+4+4 (EDGE) Chain BCCH BB

2.1.2 STIRC-enabled sectors and Mult i-BCF

Purpose:

The purpose of this test case is to check that STIRC can be enabled on a Multi-

BCF configuration.



17 (84)




Equipment and BTS set-up



1. Create a BTS with the configurationmentioned in the test case.



3. Enable STIRC for each of the sectors usingMML command:


For Talk Metro: enable STIRC for MetrositeBTSs only.

The BSC sends the STIRC enable for the sectorin the BTS_CONF_DATA (BTS-id, ST-IRC mode‘ON’).

The BTS sends ACK, on BTS_BSC_ACK to theBSC. The BTS is in WO state.

The above message is seen for each of thesectors in the segment.

4. Speech calls are made in all the sectors of the segment.

Calls are successful and speech quality ischecked on the Abis trace.

Case Ref. Configuration Band Hopping

366476.02 Talk Family – 2+2+2 and Metrosite – 4 (EDGE)+4 (EDGE) +4 (EDGE)

See the figure below.

Any BTS1=None

BTS4=RF





Test cases

2.1.3 STIRC-enabled sector and hopping modes

Purpose:

The purpose of this test case is to check that STIRC can be enabled on a BTSwith RF or BB hopping.







3. Enable STIRC for each of the sectors usingMML command:



The BTS sends ACK, on BTS_BSC_ACK to theBSC.


4. Speech calls are made. Calls are successful and speech quality ischecked on the Abis trace.


366480.03 4 OMNI (EDGE) Any RF

366480.04 2 (GSM) +2 (EDGE) Any RF

366480.05 4 OMNI (EDGE) Any BB

366480.06 2 (GSM) +2 (EDGE) Any BB

2.1.4 STIRC-enabled sector and RF hopping using GSM HW

Purpose:The purpose of this test case is to check that if STIRC is enabled on a sector

with GSM hardware, an alarm is raised for the BTS and TRXs.





19 (84)







2. Speech calls are made in the EDGEsector.

Calls are ongoing throughout the test.

3. Enable STIRC on the GSM sector usingMML command: ZEQM: BTS=<bt sno>: STI RC=Y;

Alarm 7606 NON-EDGE TRX ACCIDENTALLYUSED IN EDGE CAPABLE MODE is reported onBTS Manager and on BSC for all the GSM TRXsexcept for one TRX.

Alarm 7603 for the sector is reported.

4. Reset the sector. Alarms are cancelled and then reported again.

5. Disable STIRC on the GSM sector usingMML command:

ZEQM:BTS=<bts no>:STIRC=N;

The alarms are cancelled and the site returns toWO state.

6. Speech calls are made in both the sectors. Calls are successful and speech quality ischecked on the Abis trace.

7. The test is performed on the GSM/EDGEsector.

Alarm 7606 is reported for the GSM TRXs


366483.02 4 (GSM) +4 (EDGE) +4 (GSM/EDGE) Any RF

2.1.5 STIRC-enabled sector and BB hopping using GSM HW

Purpose:

The purpose of this test case is to check that if STIRC is enabled on a sector

with GSM hardware (OMNI & Mixed configurations), an alarm is raised for the

BTS and TRXs.






2. For test case .03 speech calls are made inthe EDGE sector.

Calls are ongoing throughout the test.





Test cases


3. Enable STIRC for each of the sectorscontaining GSM HW using MML command:


Alarm 7606 NON-EDGE TRX ACCIDENTALLYUSED IN EDGE CAPABLE MODE is reported on

BTS Manager and on BSC for all the GSM TRXsexcept for one TRX for purely GSM sector inMetroSite.

4. Reset the sector. Alarms are cancelled and then reported again.

5. Disable ST-IRC on the GSM sector usingMML command:

ZEQM:BTS=<bts no>:STIRC=N;

Reset the sector.

The site returns to WO state and the alarms arecancelled.

6. Speech calls are made in both the sectors. Calls are successful and speech quality ischecked on the Abis trace.

7. For the third test case, the test is performedon the GSM/EDGE sector.

Alarm 7606 is reported for the GSM TRXs.


366491.03 4 (GSM) +4 (EDGE) +4 (GSM/EDGE) Any BB

2.1.6 STIRC-enabled sectors and DFCA

Purpose:

The purpose of this test case is to check that STIRC can be enabled on a sector

with DFCA configuration and ACK is sent by the BTS on the Abis.

Note 21.

Make sure the DFCA feature is activated on the BSC.

Note 22.

Non-DFCA (BCCH and Regular TRX’s) are non-hopping unless otherwise

stated.

Note 23.

When a DMA list is attached to a site, it must be attached to all DFCA sectors.

This also applies when more than one DMA list is used.



Configure DFCA



21 (84)





1. Create a BTS with the configurationmentioned in the test case. The BTS is in WO state.


3. Enable STIRC for the sectors using thecommand:

ZEQM: BTS=<bt s no>: STI RC=Y;




4. Speech calls are made in the sectors. Calls are successful and speech quality is

checked on the Abis trace.Calls are assigned to DFCA TRXs andfrequencies in DMAL list are used.


366502.02 4+4+4, 3 x [1x BCCH +1x Regular TRX +2xDFCA TRX]

1900 Sector 1- DFCAHopping

Sector 2 – RF/DFCAHopping

Sector 3– RF/DFCAHopping

2.1.7 STIRC-enabled sectors and RSSI

Purpose:

The purpose of this test case is to confirm that RSSI measurements can be made

in a STIRC-enabled sector with 2-way and 4-way RX diversity.

Note 24.

The antennae can only be supervised reliably if the BCCH power level is within

the acceptable range of power levels 0 to 6.

Note 25.

An IDD TRX contains main and auxiliary TRX pair.

The following kind of naming is used, when the IDD sector configurations are

referred later in this test case:

IDD(2+2+2) = 2*(main + aux) + 2*(main + aux) + 2*(main + aux) = 12 TSxBs





Test cases






2. Monitor O&M messages on Abis.

3. Enable ST-IRC for the EDGE sector/s usingthe following command:


The BSC sends the STIRC enable for thesector in the BTS_CONF_DATA (BTS-id, ST-IRC mode ‘ON’).



4. Monitor and record OMUSIG on Abis

5. Attenuate one of the RX path (main or Div) toget a difference in signal strength.

Calls are made via the BTS so that a hightraffic situation is realised.

Calls are successful. After 1 hour, the followingalarm is set at the BSC and BTS Manager for TRXs whose Rx path (Main or Diversity) isbeing affected: 7607 TRX OPERATIONDEGRADED: RX levels differ too muchbetween Main & Diversity antenna.

6. RSSI results are checked from BTS Manager. RSSI results can be requested from BTSManager.

Main and Diversity RX levels, TRX branchdifference and RX Relative difference valuesare displayed for TRXs that have high traffic.“n/a” text is displayed for TRXs that have lowtraffic.

7. Stop the Abis recording and analyse thetrace.

Transactions between the BTS and BSC for theRSSI can be followed: RX Difference limit canbe seen in BTS_CONF_DATA message. Thealarm is set with BTS_ALARM message.

Case Ref. Configuration Band

366504.03 4 OMNI (EDGE) Any

2.1.8 Intra-Cell Synchronous Handovers in a STIRC-enabled CommonBCCH conf iguration

Purpose:

To confirm that a BCF can be configured with a common BCCH and that the

Segment can be brought into working order with a STIRC-enabled BTS in the

Segment, and to verify call handling under handover conditions.



23 (84)




Note 26.

The handovers are triggered by the mobiles moving away from/to the BTS. The

relevant Handover Quality thresholds (ZEHQand ZEHB) are set to achieve this.




1. The configuration in use is as listed in thetest case.

2. Create both BTSs in the same Segment(BTS 1 & 2).

Check for any alarms at the BSC:

ZEOL: <bcf number >;

Site is in a working order state.

BSC command: ZEEI : BCF=<bcf nr>;

No unexpected alarms are shown.

3. Monitor the Abis. Abis monitoring of OMU link and TRX links.

4. Enable STIRC in the EDGE BTS of theSegment using the following command:


BSC sends STIRC enable information for BTSobject (sector) in the BTS_CONF_DATA.

STIRC will only be enabled on those TRXs that donot exceed the STIRC licence capacity.

Site is in working order.

5. Check for any alarms at the BSC:ZEOL: <bcf number >;

No unexpected alarms.

6. Intra-cell handovers parameters are set. HO Test parameters are set.

6. An FR CS call is established, repeat anumber of times to ensure calls can beinitialised on the BCCH & NON BCCH TRX s̀ of the Segment.

Intra cell handovers are triggered to target TS at least 20 times during the same call,ensure calls are handed over between theSTIRC enabled EDGE BTS of the

Segment and the GSM BTS of thesegment.

During handovers, a conversation is held,and both directions are monitored for anyunexpected audio disturbances.

Calls are successful. Handovers can be performedfrom the target to source TS and back, the call isestablished and observed on both EDGE and GSMBTS of the Segment. Assignment failures are not

seen on the Abis, monitor MS display and observeBCCH frequency.

The speech is unaffected by the handoverprocedure and there are no additional audio signalsnoticed (such as clicks).

Case Ref. Configuration Signalling Hopping modesectors

Band





Test cases


367476.02 4 (GSM)+4 (EDGE) COMMONBCCH BCCH in EDGE BTS

16kb TRX signallinglinks

none 900

367476.04 4 (GSM)+4 (EDGE) COMMONBCCH BCCH in GSM BTS

16kb TRX signallinglinks

none 900

2.1.9 EMR measurement report ing and comparison of STIRC & IRC

Purpose:

The purpose of this test case is to check that with (CX5) 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 againstthe final release of BTS SW CX4.1(IRC) and BTS SW CX5(IRC), STIRC

disabled.

Note 27.

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.

The Mean BEP, CV BEP and UL FER are coded in the Suppl Info field in the

Measurement Result in the BTSM layer.

Note 28.

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.




• Variable attenuator

•

Site: as defined in test case below


1. Create a BTS with the configuration mentionedin the test case.





25 (84)





3. Enable STIRC for the EDGE sector:


The BSC sends the STIRC enable for thesector in the BTS_CONF_DATA (BTS-id, ST-

IRC mode ‘ON’).

The BTS sends ACK, on BTS_BSC_ACK tothe BSC.


4. Set uplink DTX as shown in the table.

5. Set 2-way Diversity ON.

The main and diverse receiver paths must beeach tested separately.

Set up the RF path in the uplink as shown inthe figures in Appendix B.

Important:

Ensure that there is no direct path from the MSto the BTS through the air. The MS must be ina screened box. All cables must be correctlytightened.

6. Fix the transmit power of the MS to near itsminimum using the MML command:

ZEQM: BTS=<bt sno>: PMAX1=7, PMAX2=6, PMI N=7;

This stops the carrier power from varying

during the test, and minimises the chances of aleakage signal via the air reaching the BTS.

7. Make a speech call to a PSTN number or anMS locked to a different BTS.

Monitor the TRXSIG for the STIRC-enabledBTS on the Abis for MEASUREMENTRESULTS messages.

Adjust the variable attenuator so that the signallevel seen at the BTS is reported as -84 to – 85dBm

8. With the interferer switched off, measure thepower of the uplink bursts as shown in thefigure in Appendix C.

Calculate the input power at the receiver takinginto account the coupler, any attenuators andany duplexers in the path

The input power to the receiver is between -83and -88 dBm.





Test cases


9. Disconnect the call.

Set up the signal generator to provide acontinuous interferer, with digital modulation =GSM standard.

Set the reference level to 10dB below theuplink carrier power measured above (that is,C/I =10dB). Switch off the interferer.

10. Make a speech call to a PSTN or an MSlocked to a different BTS. Check that thecarrier power is the same as previouslymeasured. Switch on the interferer (make anyslight adjustments to the level if the carrierpower has changed).

Monitor the Abis for MEASUREMENTRESULT messages. Record a trace for 1minute at C/I =10 dB. Reduce the C/I in 1 dBstepsfrom 10 to 0 dB, recording a minute tracefor each step.

Disconnect the call and switch off theinterferer.

11. Analyse the traces for UL Mean BEP, UL FERand:

DTX off – RxQual Full

DTX on – RxQual Sub

The UL Mean BEP, UL: FER and RxQual arewithin the limits shown below.

12. Repeat the test case with the final release of BTS SW CX4.1 (IRC) and with CX5 withSTIRC disabled (iRC).

(Note: STIRC is not supported in CX4.1)

Compare results with CX5 with STIRCenabled, no RX Quality degradation isobserved with IRC.

The results are within limits shown below.

Case Ref. Configuration / Band UL DTX Activation

Limits

366511.03 4 OMNI (EDGE) - Any ON FER always reported as 0 with nointerference.

RxQual and Mean BEP see tableRxQual and UL BEP below.

366511.04 4 OMNI (EDGE) - Any OFF See tables RxQual and UL BEP andUL FER below.



27 (84)




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 52 6 5 8 4

1 7 6 6 3

0 7 6 4 1

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





Test cases

2.1.10 STIRC-enabled sector and EPCR

Purpose:

The purpose of this test case is to check that the STIRC-enabled sector reportsits ability to receive EPCR correctly to the BSC, and that the BSC informs the

EPCR capability of the cell correctly to the MS.

Note 29.

When a BTS 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. An EDGE TRX should report as

supporting EPCR on CCCH and PCCCH (3).

Note 30.

The BSC informs the MS of the capability of the cell in the (PACKET)

SYSTEM INFORMATION 13 message. The information element can be found

as follows:

(PACKET) SYSTEM INFORMATION 13 Æ GPRS Cell Options Æ EGPRS

PACKET CHANNEL REQUEST


• Site as defined in the test case below.

• Edge-capable MS

• MS-capable of MCS1-4 only

• Non-Edge mobile MS



Ensure that the GP TSs are configured andthat GPRS and EGPRS is enabled(MCA/MCU to any MCS).

The BTS is in WO.




29 (84)





3. Enable STIRC for the sector using thecommand:


The BSC sends the STIRC enable for thesector in the BTS_CONF_DATA (BTS-id, ST-

IRC mode ‘ON’).



4. Reset the site.

5. Monitor Abis for BTS_OMU_STARTEDmessage on the O&M.

Each TRX configured for EDGE shall indicatethat EPCR capability is supported with 1 of thefollowing options:

0 =EPCR not supported

1 =EPCR supported on CCCH

2 =EPCR supported on PCCCH

3 =EPCR supported on CCCH and PCCCH

6. Monitor the TRX SIG timeslot for the BCCH TRX.

The GPRS/EGPRS related information is senton System Information 13 or Packet SystemInformation 13 (SI13 or PSI13), depending onwhether CCCH or PBCCH is in use.

If EDGE is enabled, then the optional extensioninformation within the GPRS cell options of SI13/PSI13 indicates that – EGPRS-capableMSs shall use EGPRS PACKET CHANNEL

REQUEST message for uplink TBF.If EDGE is enabled but the BTS SW does notsupport EPCR, then the optional extensioninformation within the GPRS cell options of SI13/PSI13 indicates that – EGPRS-capableMSs shall use two-phase packet access with aPACKET CHANNEL REQUEST.

7. Perform an EGPRS attach with an EDGEcapable MS.

Using (P)CCCH, the P-CHANNEL REQUIREDis seen on the (P)RACH. The P-CHANNELREQUIRED (EGPRS (PCR) section) isdecoded as:

TRS – TS 1 EPCR with 8PSK capability in theuplink

8. Perform an EGPRS attach with a MS capableof MCS1-4 only.

Using (P)CCCH, the P-CHANNEL REQUIREDis seen on the (P)RACH. The P-CHANNELREQUIRED (EGPRS (PCR) section) isdecoded as:

TRS – TS 2 EPCR without 8PSK capability inthe uplink.





Test cases


9. Perform a GPRS attach with a NON EDGEcapable MS.

P-CHANNEL REQUIRED is RECEIVED on the(P)RACH verifying TS 0 (there is no EGPRS

(PCR) section).

Case Ref. Configuration Band BCCH type

366507.03 4 OMNI (EDGE) Any BCCH

366507.04 4 OMNI (EDGE) Any PBCCH

2.1.11 STIRC-enabled sectors 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 STIRC-enabledsector (blind detection).




• Site as defined in test case below.

Input Expected Output1. Create a BTS with the configuration mentioned in

the test case. The BTS is in WO state.


3. Enable STIRC for the EDGE sector using MMLcommand:


The BSC sends the STIRC enable for thesector in the BTS_CONF_DATA (BTS-id,ST-IRC mode ‘ON’).





31 (84)





4. Use the EDGE sector to perform test:

1. Set the EDGE sector TRXs to GPRS:ZERM: BTS=<bt s no>, TRX=<t r xno>: GTRX=Y;

2. Enable EGPRS on the BCCH TRX usingCDED, CDEF & CMAX to enable 2 TSs asEGPRS.

3. Set Link Adaptation =ON.

4. To set the max. limit for a Block Error rateto 10 per 1000 use the MML command:ZEQV: BTS=<bt s no>: BLU=10;

5. Check that there are no offsets applied to

the BEP values.6. Set up the equipment to adjust the

Carrier/Interference (C/I) conditions in theair interface in the Uplink direction. Initiallyset the C/I >25dB.

7. Transfer a 500 kB file using the UDP/IPprotocol in the UL direction (use 1 TS).

5. Record the Abis trace.

Slowly change the C/I from 25 dB to 0 dB andback to 25 dB. Repeat. The rate of change =1

dB/sec approximately.

Stop recording the Abis trace and check the tracefor the MCS used, and the allocation of the PCUSlave Data Frames (detailed in the table below).

The coding scheme used steps downthrough the coding schemes from the leastrobust (MCS9) to the most robust (MCS1)

and back again to match the changing airinterface conditions.

MCS4 may be skipped as the LinkAdaptation switches from 8PSK to GMSK and vice versa. The data rate changes toreflect the changing MCS.

The Dynamic Abis allocates the PCU SLAVEDATA FRAMES correctly as the MCSchanges.

Case Ref. Configuration Band BCCH type

366509.03 2+2 (EDGE) Any BCCH

366509.04 2+2 (EDGE) Any BCCH +PBCCH





Test cases

CodingScheme

Number of Slave Frames

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

2.2 RACH

2.2.1 Ghost (P)RACH with STIRC enabled

Purpose:

The purpose of this test case is to check that the number of ghost (P)RACH with

ST-IRC enabled is within the specified limit with RDIV on and off.

Note 31.

The number of ghosts is affected by the receiver performance. This test should

be performed once the final tuning of the EQDSP has been carried out.

Note 32.

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.



33 (84)




Note 33.

Because the antennas in this test are terminated with loads in this test, the BTS

should not detect any real (P)RACHs. Only internally generated noise that is

detected as having a valid training sequence should result in a low level of ghost(P)RACHs.

Note 34.

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


As defined in Figure MetroSite configuration below.


1. Create the configuration indicated in FigureMetroSite configuration below.

1. Ensure all the RF cables are correctlytorqued.

2. Configure the BCCH and remainingtimeslots as shown in table Timeslot

configuration below.3. Set the ARFN as shown in table ARFN to

set below.

4. Set Cell Bar =Y using MML command:ZEQF: BTS=<bt s number >: BAR=Y;

5. Create an EDAP and enable GPRS andEGPRS.

6. Set diversity as shown in the table usingMML command: ZEQM: BTS=<bt snumber >: RDI V=<Y or N>;

7. Commission the site and bring it intoworking order.



Split the Abis recording into 3-4-hour blocks.





Test cases


3. Enable STIRC for the sectors using MMLcommand:

ZEQM: BTS=<bt s number >: STI RC=Y;

The BSC sends the STIRC enable for thesector in the BTS_CONF_DATA (BTS-id,

ST-IRC mode ‘ON’).



4. Maximise the number of paging blocks in themulti-frame and reduce the number of multi-frames before paging group is repeated usingthe MML command:

ZEQJ:BTS=<bts number>:AG=1,MFR=2;

Use a script to generate paging on each paging

block on the CCCH.5. 50 ohm, 50W terminating loads must be put on

each antenna.

Firmly close the door of the cabinet.

6. Set up an Abis trace for the channels indicatedin table Messages and Channels to monitor on Abis below.

7. Record traces every 24 hours for a total of 72hours.

8. Analyse the traces and count the messages

indicated in table Messages and Channels tomonitor on Abis below, for each type of BCCH.

As PBCCH is being tested the MBCCHC mustbe counted as well, but the results should beconsidered separately. Only valid frames mustbe counted.

Calculate the number of ghosts per BCCHchannel 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 isbelow the acceptance limit in the table.

Case Ref Configuration / Band RDIV Acceptance Limit(Ghosts per channelper 24 hours)

366513.03 Figure 2 (EDGE) – Any Y 50

366513.04 Figure 2 (EDGE) – Any N 20



35 (84)




Timeslot configuration

MBCCHC + PBCCH

0 MBCCHC

1 SDCCH

2 PBCCH

3 TCHF

4 TCHF

5 GP

6 GP

7 GP

ARFN to set for Figure “MetroSi te Conf iguration”

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

Messages and Channels to monitor on Abis

BCCH Channels Messages

MBCCHC TRXsig Abis TS for eachBCCH TRX

Stack = GSM Abis

CHANNEL REQ

P-CHANNEL REQ

EGPRS PACKET CHANNELREQUEST

PBCCH PDTCH Abis TS for eachPBCCH

Stack =PCU 16Kb

EGPRS PACKET CHANNELREQUEST

PACKET CHANNEL REQUEST





Test cases

MetroSite configuration

2.2.2 RACH load whi lst BSC background software loading with STIRCenabled

Purpose:

The purpose of this test case is to check that RACH with STIRC enabled is

within the specified limits whilst under load conditions and background

software loading.


As defined in the test case below - use 64kb signalling.

L1 MSs


1. Memory block reservations are checkedbefore and after the test.

After the test there are as many memory blocksreserved as there were before the test.

2. BMA is defined as 1, using MMLcommand:

ZEQM: BTS=<bt s no>: BMA=1;



37 (84)





3. Configure the channels as defined in thebottom part of this table.

Bring the site into working order.

Speech calls are made via every TS of BCCH TRX and data transfer is started.

Calls remain ongoing for the duration of the test.


5. L1 MSs are used for making RACH load tothe BTS.4000 RACH/min is generatedusing the tool.

Background SW downloading is activatedfrom the BSC. Whilst the SW isbackground downloading, enable STIRC

for the sectors using MML command:ZEQM: BTS=<bt s number >: STI RC=Y;

The TRX works normally during the test.

SW downloading is successful.

STIRC is enabled. The BSC sends the STIRCenable for the sector in the BTS_CONF_DATA(BTS-id, ST-IRC mode ‘ON’).



6. The quality of the calls is checked duringRACH load by listening to the voice.

The Abis is monitored.

Quality of calls is good.

The Abis indicates that the CHANNELREQUIRED and IMMEDIATE ASSIGNCOMMAND is used.

In CCCH LOAD IND message (uplink), BTSshould report non-zero values for RACH busyand RACH access count.

The duration of the test is one hour.Case Ref . Conf igurat ion /

BandChannel Conf igurat ion Cal l types

366538.02 2+2 (EDGE) – Any (MBCCHC, SDCCH,5*TCHD, 1 TS for(E)GPRS) + (8*TCHD)

4 HR, 3 EFR

1* Data transfer from an EGPRSphone (download a file largerthan 10 Mb – downloading to berepeated during test period)

2.2.3 PRACH load whi lst BSC background software loading with STIRCenabled

Purpose:

The purpose of this test case is to check that PRACH with STIRC enabled is

within the specified limits whilst under load conditions and background

software loading.





Test cases


As defined in the test case below - use 64kb signalling.

L1 MSs


1. Memory block reservations are checkedbefore and after the test.

After the test there are as many memory blocksreserved as there were before the test.

2. BMA is defined as 1, using MMLcommand:

ZEQM: BTS=<bt s no>: BMA=1;

3. Configure the channels as defined in thebottom part of this table.

Configure at least one EGPRS timeslot inthe sector. Enable EGPRS in the sector.Bring the site into working order.

Speech calls are made via every TS of BCCH TRX and data transfer is started.

Calls remain ongoing for the duration of the test.


5. L1 MSs are used for making PRACH loadto the BTS.

Background SW downloading is activatedfrom the BSC. Whilst the SW is

background downloading, enable STIRCfor the sectors using MML command:

ZEQM: BTS=<bt s number >: STI RC=Y;

The TRX works normally during the test.

SW downloading is successful.

STIRC is enabled. The BSC sends the STIRC

enable for the sector in the BTS_CONF_DATA(BTS-id, ST-IRC mode ‘ON’).



6. The quality of the calls is checked duringthe PRACH load by listening to the voice.

The Abis is monitored.

Quality of calls is good.

The Abis indicates that the CHANNELREQUIRED, P-CHANNEL REQUIRED andIMMEDIATE ASSIGN COMMAND is used.

In CCCH LOAD IND message (uplink), BTSshould report non-zero values for RACH busyand RACH access count.

The duration of the test is one hour.

Case Ref . Conf igurat ion / Band Channel Configuration Call t ypes



39 (84)





366542.02 4 OMNI (EDGE) / Any (MBCCHC, SDCCH, ,4*TCHD, 2 TS for

(E)GPRS) + (8*TCHD)

2 FR, 2 EFR, 2HR

1* Data transfer from anEGPRS phone (download a filelarger than 10 Mb –downloading to be repeatedduring test period)

2.3 Voice, Data, GPRS and EGPRS

2.3.1 Enable STIRC whilst AFS, AHS and CS Data calls are ongoing

Purpose:

The purpose of this test case is to check that STIRC can be enabled whilst AMR

FR, AMR HR and CS data calls are ongoing.






2. Make the call as mentioned in the testcase.

Calls are successful.







5. Monitor the status of the calls. Calls are not affected/dropped after STIRC isenabled in the sector.

Case Ref Configuration Call Type Hopping

370239.04 4 OMNI (EDGE) AMR FR BB

370239.05 4 OMNI (EDGE) AMR HR RF

370239.06 4 OMNI (EDGE) NT, 9600 BB





Test cases

2.3.2 Disable STIRC whilst AFS, AHS and CS Data calls are ongoing

Purpose:

The purpose of this test case is to check that STIRC can be disabled whilstAMR FR, AMR HR and CS data calls are ongoing.












4. Make a call as mentioned in the test casebelow.


5. Disable STIRC for the sector using MML

command:ZEQM: BTS=<bt s no>: STI RC=N;

The BTS receives BTS_CONF_DATA containing

STIRC information (STIRC mode, BTS id). The BTS sends BTS_BSC_ACK to the BSC.

The calls are not affected after disabling STIRC.


370247.04 4 OMNI (EDGE) AMR FR RF

370247.05 4 OMNI (EDGE) AMR HR BB

370247.06 4 OMNI (EDGE) NT, 14400 BB

2.3.3 Enable and Disable STIRC in the first sector whi lst AFS, AHS andCS Data calls are 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.



41 (84)










3. Make a call in the second sector asmentioned in the test case below.

Calls are successful and on-going throughout thetest.

4. Enable STIRC for the first sector usingMML command:


The calls remain unaffected in the second sector.

5. Monitor messages on the Abis. The BSC sends the STIRC enable for the sectorin the BTS_CONF_DATA (BTS-id, STIRC mode‘ON’).



6. Make calls on the first sector. Calls are successful.

7. Disable STIRC in the first sector usingMML command:

ZEQM: BTS=<bt s no>: STI RC=N;

The BTS receives BTS_CONF_DATA containingSTIRC information (STIRC mode, BTS id).

The BTS sends BTS_BSC_ACK to the BSC.

The calls in both sectors are not affected afterdisabling STIRC in the first sector.


370249.04 2+2 (EDGE) – MBCCH+SDCCH+TCHD AMR FR RF

370249.05 2+2 (EDGE) – MBCCHC+TCHD AMR HR BB

370249.06 2+2 (EDGE) – Any 9600,NT RF/BB

2.3.4 Enable STIRC whilst Packet Data calls are ongoing

Purpose:

To confirm STIRC can be enabled whilst packet data calls are ongoing (MCS 1,

4 &7).







Test cases


1. Create a BTS with the configurationmentioned in the test case. The BTS is in WO state.

2. Make EGPRS data transfer in the firstsector, as mentioned in the test case, andsimultaneous speech calls in the firstsector.



4. Enable STIRC for the first sector usingMML command:



The BTS sends ACK, on BTS_BSC_ACK to the

BSC.


The EGPRS data transfer and the speech callsare unaffected after STIRC is enabled.

Case Ref. Configuration Codec Direction Hopping

370251.04 2+2 (EDGE) MCS 1 DL BB

370251.05 2+2 (EDGE) MCS 4 DL RF

370251.06 2+2 ( EDGE) MCS 7 UL BB/RF

2.3.5 Disable STIRC whilst Packet Data calls are ongoing

Purpose:

To confirm that STIRC can be disabled whilst packet data calls are ongoing

(MCS 2, 5 &8).









43 (84)





3. Enable STIRC for both sectors using MMLcommand:


The BSC sends the STIRC enable for the sectorin the BTS_CONF_DATA (BTS-id, STIRC mode

‘ON’).



4. Make EGPRS data transfers in the firstsector and speech calls in the secondsector simultaneously.


5. Disable STIRC for the sectors using MMLcommand:




The Packet Data calls and speech calls are notaffected after disabling STIRC.

Case Ref. Configuration Codec Direction Hopping

370252.04 2+2 (EDGE) MCS 2 UL BB

370252.05 2+2 (EDGE) MCS 5 DL RF

370252.06 2+2 ( EDGE) MCS 8 UL Any

2.3.6 Enable and Disable STIRC in the first sector whi lst Packet Datacalls are ongoing in the second sector

Purpose:

To confirm that ST-IRC can be enabled and disabled in the first sector without

disturbing the Packet Data calls that are ongoing in the other sector (MCS 3, 6

& 9).











Test cases


3. Enable STIRC in the second sector usingMML command:


The BSC sends the STIRC enable for the sectorin the BTS_CONF_DATA (BTS-id, STIRC mode

‘ON’).



4. Make data calls in the second sector asmentioned in the test case.


5. Enable STIRC in the first sector using MMLcommand:




Enabling STIRC in the first sector does not affectthe packet data calls in the second sector.


370254.04 2+2 (EDGE) MCS 3 BB

370254.05 2+2 (EDGE) MCS 6 RF

370254.06 2+2 ( EDGE) MCS 9 BB/RF

2.4 Stabil ity of a STIRC-enabled BTS Site under loadconditions

Purpose:

To check the stability of a STIRC-enabled BTS Site under high load conditions.

Note 35.

The test case must be performed with Rx diversity enabled at the BSC unless

stated otherwise.

Note 36.

The test case must be performed on BSC S12 software unless stated otherwise.


Mobile call generator, set-up for EGPRS calls.



45 (84)





1. The site is up and working as per theconfiguration defined in the test case.

2. STIRC is enabled from the BSC using thecommand:

ZEQM: BTS=<bt s no. >: STI RC=Y, : ;

STIRC can be successfully enabled from theBSC.

3. Monitor the Abis O&M link. On the Abis link, it is observed thatBTS_CONF_DATA is sent to the BTS by theBSC, with the STIRC mode as enabled.


4. Monitor the UC-DSP traces using the Trace master.

STIRC information is sent from UC to the EQDSPin the INI message.

5. Enable EGPRS at the site. EGPRS can be successfully enabled at the site.6. Perform GPRS attach and start 2 EGPRS

data transfers. The EGPRS transfers are started and proceedwithout any problem.

7. With the EGPRS transfers ongoingthroughout the test case, make 10 callsdynamically using a mobile call generator.

The call type should be a combination of AHS & THR.

The calls are successful.

This test case is carried out for 4 hrs. The percentage of successful call is >99%.

Case Ref Site Type Configuration Hopping

DN0691283.01

MetroSite 4 OMNI EDGE HW None

2.5 Recovery Actions

The purpose of the following test cases is to check that the STIRC feature

recovers correctly. The following types of tests are run:

•

Recovery on BTS Manager Actions with STIRC enabled• Recovery on BSC Actions with STIRC enabled

• Recovery on HW Actions

2.5.1 Recovery on BTS Manager Act ions with STIRC enabled

Purpose:





Test cases

To check that a site configured with the STIRC feature recovers correctly after

BTS Manager actions.




1. Set up a site as per test case. Site is in WO state.


Monitor UC-DSP traces with Trace master.

3. Enable STIRC for the sector/s using theMML command:


Note: For test case .19, block the TCH TRXbefore enabling STIRC.





STIRC information is sent to the EQDSP in theINI message.

4. Check active alarms and alarm history. No unexpected alarms should be present.

5. Make a phone call on all TRXs. Call is successful 6. From BTS Manager, perform an action as

per the test case.Action is performed on object.

Corresponding alarms are raised.

7. Check active alarms and alarm history. No unexpected alarms have been generated.

8. From BTS Manager, reverse the action asper test case.

Action is reversed and site returns to WO state.

9. Make a phone call on all TRXs. Call is successful.


11. Stop the Abis trace. Check messages to verify that correct behaviour

has taken place.Case Ref. Heading Configuration

367698.11 Block/unblock of a STIRC enabled sector fromBTS Manager

4 OMNI (EDGE) –– RF hopping

367698.12 Block/unblock of a TCH TRX in a STIRCenabled sector from BTS Manager

2+2 (EDGE)

367698.13 Block/unblock of a BCCH TRX in a STIRCenabled sector from BTS Manager

2+2 (EDGE)



47 (84)





367698.14 Reset of a TCH TRX in a STIRC enabled sectorfrom BTS Manager

4 OMNI (EDGE)

367698.15 Reset of a BCCH TRX in a STIRC enabledsector from BTS Manager

4 OMNI (EDGE)

367698.16 Reset of a STIRC enabled sector from BTSManager

4 OMNI (EDGE) – BB hopping

367698.17 BCF reset with a STIRC enabled sector fromBTS Manager

4 OMNI (EDGE)

367698.18 BCF, slave BTS, & slave TRX reset with STIRCenabled sectors from BTS Manager

4 (GSM) +4 (EDGE) +4 (EDGE)Chain

(Enable STIRC for EDGE sectorsonly)

367698.19 Block a TCH TRX, Enable STIRC, unblock the TRX from BTS Manager and check thatBTS_CONF_DATA is sent correctly on the Abis

12 OMNI (EDGE) Chain

2.5.2 Recovery on BSC Act ions with STIRC enabled

Purpose:

To check that a site configured with the ST-IRC feature recovers correctly after

BSC actions.




1. Set up a site as per test case. Site is in WO state.


3. Enable STIRC for the sector/s using theMML command:


The BSC sends the STIRC enable for the sectorin the BTS_CONF_DATA (BTS-id, ST-IRC mode

‘ON’).




4. Check active alarms and alarm history. No unexpected alarms should be present.





Test cases


5. Make phone call on all TRXs. Call is successful.

6. From BSC, perform an action as per testcase. An action is performed on object.Corresponding alarms are raised.

7. Trace master is used to monitor the UC-DSP traces.

STIRC information is sent to the EQDSP in theINI message for the sector(s).


9. From BSC, reverse the action as per testcase.

Action is reversed and site returns to WO state.

10. Trace Master is used to monitor the UC-DSP traces.


11. Make a phone call on all TRXs. Call is successful.


13. Stop the Abis trace. Check messages to verify that correct behaviourhas taken place.

Case Ref. Heading Configuration

367687.09 Lock/unlock of a STIRC-enabled sector fromBSC

(Note: STIRC enabled on an EDGE sector)

2 (GSM) +2 (EDGE)

367687.10 Lock/unlock of a TCH TRX in a STIRC-enabledsector from BSC

2+2 (EDGE)

367687.11 Lock/unlock of a BCCH TRX in a STIRC-enabledsector from BSC

2+2 (EDGE)

367687.12 Lock/unlock of a STIRC-enabled sector fromBSC

4 OMNI (EDGE)– RF hopping

367687.13 Lock/unlock of BCF with a STIRC-enabledsector from BSC

4 OMNI (EDGE)– BB hopping

367687.14 Lock/unlock of BCF, slave BTS & slave TRX withSTIRC-enabled sectors from BSC

4+4+4 (EDGE) Chain

367687.15 Lock a TCH TRX. Enable STIRC, unlock the TRX from BSC and check that

BTS_CONF_DATA is sent correctly on the Abis

2+2 (EDGE)

Purpose:

The purpose of this test case is to check that a STIRC-enabled sector can

recover correctly after LAPD blocks on a BCCH TRX, TCH TRX and the

O&M link.



49 (84)





Site: as defined in the test case below.

A neighbouring cell is required for handovers.


1. Create a BTS with the Configurationmentioned in the test case.



3. Enable STIRC on the sector using the MMLcommand:


The BSC sends the STIRC enable for thesector in the BTS_CONF_DATA (BTS-id, ST-IRC mode ‘ON’).

The BTS sends ACK, on BTS_BSC_ACK to

the BSC.


4. The BCCH TRX is marked as the preferred TRX.

Calls are made on the BTS in such a way thatone call is on the BCCH TRX and another callis on the TCH TRXs.

The BCCH TRX signalling link is blocked usingthe MML command ZDTC.

Alarm 7705 LAPD FAILURE is activated at theBSC. The BCCH TRX is blocked at the BSC. The call active on the BCCH TRX is droppedand the call on the TCH TRXs are handedover to neighbouring cells.

BCCH TRX alarm is raised.

5. Calls are made on the reconfigured BTS. Calls are successful on the unblocked TRXs

and the voice quality is good.6. The signalling link is unblocked. The preferred TRX returns to operational state

and is reconfigured back to the BCCH TRX.

7. Calls are made via every TRX. Calls are successful.

8. Calls are made via the BTS.

A TCH TRX signalling link is blocked using theMML command ZDTC

Alarm 7705 LAPD FAILURE is activated at theBSC. The TCH TRX is blocked at the BSC. The calls on the TCH TRX are dropped. The TRX is blocked at the BSC.

9. The signalling link is unblocked. The TRX signalling link is re-established andthe TRX returns to operational state.

10. Calls are made via the TRX whose link hasbeen blocked/unblocked.


11. Calls are made via the BTS.

The O&M LAPD link is blocked using the MMLcommand ZDTC

Alarm 7706 BTS O&M LINK FAILURE isactivated at the BSC. Calls remain active.





Test cases


12. An alarm is generated by removing a TCH TRX.

The O&M LAPD link is unblocked. The alarmsare checked at the BSC. The time between theO&M LAPD link establishment and sending of alarms to the BSC is checked from the Abis.

When the LAPD link is unblocked, alarm 7706O&M LINK FAILURE is cancelled and alarm

7606 TRX FAULTY from the missing TRX issent to the BSC. If the BSC does notacknowledge the alarm, the BCF sends itagain after 10 seconds.

13. TRX is reinstalled. Calls are made via thereinstalled TRX.

TRX is initialised correctly and alarm 7606 iscancelled. Calls are successful.

Case Ref. Configuration / Band TRX Signalling Speed / FU Link Hopping

367703.02 4 OMNI (EDGE) – Any 16 Kbits/s / BCCH TRX BB

367703.04 4 OMNI (EDGE) – Any 32 Kbits/s / TCH TRX Non

367703.06 4 OMNI (EDGE) – Any 64 Kbits/s / O&M Non

2.5.3 Recovery on HW Act ions

2.5.3.1 Loss and re-gain of power to cabinet, no BBU System with a STIRC-enabledsector

Purpose:

To confirm that the STIRC-enabled sector recovers after power loss.





2. Monitor messages on the Abis. Abis monitoring of OMU link and TRX links.

3. Trace master is used to monitor the UC-

DSP traces throughout the test case.

STIRC information is sent to the EQDSP in the INI

message for the sector(s).4. Enable STIRC in the sector by the MML

command:

ZEQM : BTS= <bt s no>: STI RC=Y;





51 (84)





5. Check the BCF status.

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

Site is in working state.

BSC command ZEEI : BCF=<bcf nr>; No unexpected alarms.


7. Power is switched off to the BCF (Poweroff CVSB).

Check for any alarms at the BSC usingMML.

When the power is switched off, BCCH MISSINGalarm is active, and additional alarms related tolink failure are activated at the BSC.

No alarms are seen at BTS Manager. BTSManager connection is lost. Calls are released forcorrect termination reason.

8. Power is restored to the BCF. The BCF is initialised BSC sends

BTS_CONF_DATA ST_IRC enabled informationis checked in the BTS_CONF_DATA, (ST-IRCmode ‘ON’) BCF returns to working state.

BTS Manager connection establishes.


Check alarms at the BSC and BTSManager.



10. New calls are made. Calls are successful.

Case Ref. Configuration BTS PSU Unit TRXs

373335.01 4 OMNI (EDGE) CVSB CTxx

2.5.3.2 Swap of Slave EDGE TRX for GSM TRX wi th STIRC enabled

Purpose:

To confirm that an alarm is raised (Alarm 7606 NON-EDGE TRX

ACCIDENTALLY USED IN EDGE CAPABLE MODE) when an EDGE TRX

is replaced by a GSM TRX.










Test cases


3. Trace master is used to monitor the UC-DSP traces throughout the test case.


4. Enable ST-IRC in the sector by the MMLcommand





Check alarms at the BSC using MML:



BSC command ZEEI : BCF=<bcf nr>;


6. The Master TRX is configured as the

preferred BCCH. Calls are established onthe Master TRX.

Calls are successful

7. A Slave EDGE TRX is blocked from BTSManager.

At the BSC and BTS Manager, Slave EDGE TRXis seen to be in a blocked state, alarm 7208LOCAL BLOCK, calls are not dropped.

8. The blocked Slave EDGE TRX is removedfrom the cabinet and replaced with thesame band GSM TRX.

Replaced GSM TRX powers.

9. TRX is unblocked from BTS Manager. When the GSM Slave TRX is unblocked, the TRXinitialises, alarm 7208 LOCAL BLOCK cancels,and alarm 7606 (NON-EDGE TRX DEVICE TYPE USED ACCIDENTALLY IN EDGECAPABLE MODE) is reported on BTS Managerand at the BSC for the GSM TRX.

10. Disable STIRC in the sector using the MMLcommand:


BTS_CONF_DATA with STIRC disabled isreceived for the sector. The alarms are cancelledat BTS Manager and the BSC.

The BTS returns to working order state.





12. Calls are made via every Slave TRX. Calls are successful.

Case Ref Configuration Band

373352.01 4 OMNI (EDGE) 900

2.5.3.3 Swap of Master EDGE TRX for GSM TRX wi th STIRC enabled

Purpose:



53 (84)





ACCIDENTALLY USED IN EDGE CAPABLE MODE) when an EDGE TRX

is replaced by a GSM TRX.





2. Monitor messages on the Abis. Abis monitoring of OMU link.

3. Trace master is used to monitor the UC-

DSP traces throughout the test case.

STIRC information is sent to the EQDSP in the

INI message for the sector(s).4. Enable ST-IRC in the sector by the MML

command










6. Calls are established on every TRX. Calls are successful

7. The Master EDGE TRX is removed fromslot 1.

When the Master EDGE TRX is removed, alarm7767 BCCH MISSING and LAPD link alarms7705, and 7706 O&M alarms are active. Theconnection between the BTS Manager and theBTS is lost.

All calls from both BTSs are released due to lossof frame clock from the Master TRX and newcalls cannot be established.

8. The Master EDGE TRX is replaced with aGSM TRX of the same band.

The replaced GSM TRX initialises and alarm7606 (NON-EDGE TRX DEVICE TYPE USEDACCIDENTALLY IN EDGE CAPABLE MODE) is

reported on BTS Manager and at the BSC for theGSM TRX.

The remaining TRXs in the sectors return toworking state.



BTS_CONF_DATA with STIRC disabled isreceived for the sector.

The alarms are cancelled at BTS Manager andthe BSC.





Test cases






11. Calls are made via every Slave TRX. Calls are successful.


373400.01 2+2 (EDGE) Any

2.5.3.4 Swap of Slave GSM TRX for EDGE TRX then enable STIRC

Purpose:

To confirm that STIRC can be enabled after the GSM Slave TRX is replaced

with an EDGE TRX.




1. The configuration in use is as listed in thetest case. The Master TRX is configured asthe preferred BCCH. Calls are made on the

Master TRX.










5. Calls are made via every TRX. Calls are successful

6. The Slave GSM TRX is blocked from BTS

Manager.

At the BSC and BTS Manager, the Slave GSM

TRX is seen to be in blocked state, alarm 7208LOCAL BLOCK, calls are not dropped.

7. The blocked Slave EDGE TRX is removedfrom the cabinet and replaced with thesame band EDGE TRX.

Replaced EDGE TRX powers.

8. EDGE TRX is unblocked from BTSManager.

The Slave EDGE TRX is initialised, the TRXreturns to the working state, and all alarms arecancelled.



55 (84)





9. Enable STIRC in the configured EDGEsector by the MML command:


The BSC sends the STIRC enable for the sectorin the BTS_CONF_DATA (BTS-id, ST-IRC mode

‘ON’).








373416.01 2 TRX GSM/EDGE 900

2.5.3.5 Swap of Master GSM TRX for EDGE TRX then enable STIRC

Purpose:

To confirm that STIRC can be enabled after the GSM Master TRX is replaced

with an EDGE TRX.















6. The Master GSM TRX is removed from slot1.

When the Master TRX is removed, alarm 7767BCCH MISSING and 7705 LAPD FAILUREalarms for TRXs and 7706 BTS O&M LINK FALURE are active.

Reconfiguration cannot take place because theO&M link is not in working state. Alarms from theBTS are not sent to the BSC.





Test cases


7. The Master GSM TRX is replaced with anEDGE TRX of the same band.

The Master EDGE TRX initialises, the TRXreturns to the working state, and all alarms are

cancelled.











373424.01 2 TRX GSM/EDGE 900

2.5.3.6 Swap of Master EDGE TRX for EDGE TRX wi th older SW wi th STIRC enabled

Purpose:

To confirm that the old SW is replaced with the current BSC SW and STIRC is

still enabled.

Equipment and BTS Set-UpAs defined in the test case below.






4. SW downloading to Master TRX may bemonitored with service terminal extensionRPHASESX.

Monitoring active.

5. Enable STIRC in the sector by the MMLcommand:






57 (84)










8. Lock the Master EDGE TRX and remove it. When the Master TRX is removed, alarm 7767BCCH MISSING, 7706 BTS O&M LINK FALUREand alarm 7705 LAPD FAILURE alarms for allother TRXs are active.

9. A new EDGE TRX of the same band isinstalled. The SW in the memory of thenew TRX is different from the SW in theother TRX(s).

Unlock the replaced TRX.

When the TRX is inserted and unlocked, it startsto work as the Master TRX. The Master TRXdownloads SW, and the downloading issuccessful. Downloaded SW is saved to the

Master TRX flash memory (non-volatile memory). The Master EDGE TRX initialises, the TRXreturns to the working state, and all alarms arecancelled.

10. Monitor the Abis.

The BCF is reset from BTS Manager.

Check the BTS_CONF_DATA.

The BCF returns to the WO state along. BSCsends STIRC enable information for BTS object(sector) in the BTS_CONF_DATA.

11. Active SW is checked from BTS Manager. BTS SW shows the correct running package.



373429.01 4 TRX (OMNI) Any

2.5.3.7 Swap of 4*EDGE TRXs (STIRC enabled) for 4*GSM TRXs

Purpose:


ACCIDENTALLY USED IN EDGE CAPABLE MODE) when the EDGE

TRXs are replaced by the GSM TRXs.









Test cases



3. Trace master is used to monitor the UC-DSP traces throughout the test case. STIRC information is sent to the EQDSP in theINI message for the sector(s).











7. The BCF is blocked from BTS Manager. The calls are released.

The BCF is blocked alarm 7208 LOCAL BLOCK.BCCH transmission is stopped. When the BCCH TRX is not in working state, alarm 7767 BCCHMISSING is active.

8. The EDGE TRXs are removed from theBCF.

The EDGE TRXs are replaced by the sameband GSM TRXs.

Once the Master TRX is removed,communication is lost between BTS Manager andthe BTS.

The BTS Manager connection is re-established.

Alarm 7606 NON-EDGE TRX DEVICE TYPEUSED ACCIDENTALLY IN EDGE CAPABLEMODE is reported on BTS Manager and at theBSC for each TRX, except one where a sectoralarm 7600 is reported instead.





9. Monitor the Abis.

The BCF is reset from BTS Manager.

Check the BTS_CONF_DATA.

The BCF returns to the WO state along. BSC

sends STIRC enable information for BTS object(sector) in the BTS_CONF_DATA.









59 (84)





373453.01 4 OMNI (EDGE) 900

2.5.3.8 Swap of 4*GSM TRXs for 4*EDGE TRXs then enable STIRC

Purpose:

To confirm that STIRC can be enabled after the GSM TRXs are replaced with

the EDGE TRXs.












No unexpected alarms.5. Calls are made via every TRX. Calls are successful.

6. The BCF is blocked from BTS Manager. The calls are released.

The BCF is blocked, alarm 7208 LOCAL BLOCK.BCCH transmission is stopped. When the BCCH TRX is not in working state, alarm 7767 BCCHMISSING is active.

7. The GSM TRXs are removed from theBCF.

The GSM TRXs are replaced by the sameband EDGE TRXs.

Once the Master TRX is removed,communication is lost between BTS Manager andthe BTS.

The inserted TRXs power up, and the connectionto BTS Manager re-establishes.

8. Enable STIRC in the EDGE sector by theMML command:









Test cases







373466.01 4 OMNI (GSM) 900 None

2.5.3.9 Add an EDGE TRX into a STIRC-enabled sector

Purpose:

To confirm that when an EDGE TRX is added to a STIRC-enabled sector,

STIRC is not affected.






3. Trace master is used to monitor the UC-DSP traces throughout the test case. STIRC information is sent to the EQDSP in theINI message for the sector(s).











7. The LAPD link for the new TRX is created.

The TRX is created under the correct BCFand BTS (cabinet 3) at BSC.

The TRX is in locked state after it iscreated.

TRX creation at the BSC is successful.



61 (84)





8. A new EDGE TRX of the same band isinstalled.

The SW in the memory of the new TRX isdifferent from the SW in the other TRX(s).

When the new EDGE TRX is inserted into theBTS, the Master TRX detects that the

configuration has changed. The Master TRXdownloads the active SW to the new TRX.

9. A PC with BTS Manager is connected tothe BTS VIFA in cabinet 1 and the Abis TSallocation is updated for the new TRX with Traffic Manager.

The Abis TS allocation can be updated withoutdisturbing other TRXs.

9. The TRX is unlocked.

Check the status of the BCF.

Test calls are made on the new TRX.

The new TRX is successfully initialised, the BSCsends BTS_CONF_DATA ST_IRC enabledinformation is checked in the BTS_CONF_DATA,and the new TRX is made operative in thenetwork.


Case Ref. Configuration Updatedconfiguration

Band

373581.01 4 (GSM) +4 (EDGE) +2 (EDGE) Chain 4 (GSM) +4 (EDGE) +3 (EDGE) Chain

Any

2.5.3.10 Add a GSM TRX into a ST-IRC enabled sector

Purpose:

To confirm that an alarm is raised (Alarm 7606 NON-EDGE TRXACCIDENTALLY USED IN EDGE CAPABLE MODE) when a GSM TRX is

added to a STIRC-enabled sector.
















Test cases



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




7. LAPD link for the new TRX is created.

The TRX is created under the correct BCFand BTS (cabinet 3) at BSC.

The TRX is in locked state after it iscreated.

TRX creation at the BSC is successful.

8. A new GSM TRX of the same band isinstalled into cabinet 3.

The SW in the memory of the new TRX isdifferent from the SW in the other TRX(s).

When the new GSM TRX is inserted into theBTS, the Master TRX detects that the

configuration has changed. The Master TRXdownloads the active SW to the new TRX.

9. BTS Manager is connected to the BTSVIFA in cabinet 1 and the Abis TSallocation is updated for the new TRX with Traffic Manager.

The Abis TS allocation can be updated withoutdisturbing other TRXs.

9. The TRX is unlocked.

Check the status of the BCF.

Test calls are made on the new TRX.

The Chain Master TRX detects the hot-insertedSlave GSM TRX, and MMI shows new GSM TRX.

The Chain Master TRX synchronises andconfigures the new hot-inserted Slave GSM TRXand alarm 7606 (NON-EDGE TRX DEVICE TYPE USED ACCIDENTALLY IN EDGECAPABLE MODE) is reported on BTS Managerand at the BSC for the GSM TRX.



Check the BCF status.


The BTS is initialised, the BSC sendsBTS_CONF_DATA STIRC disabled (STIRCmode “off”). This information is checked in theBTS_CONF_DATA. BTS Manager connectionestablishes.

The BCF returns to working state.

11. Check alarms at the BSC and BTSManager.



Case Ref. Configuration Expanded to Band



63 (84)





373586.01 4(GSM) +4(EDGE) +2(EDGE)Chain

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

Any

2.5.3.11 Swap a GSM TRX into the Master slo t of the Master cabinet with STIRC enabled

Purpose:


ACCIDENTALLY USED IN EDGE CAPABLE MODE) when a GSM TRX is

placed in the Master slot of the Master cabinet.








4. Enable STIRC in the sector by the MML

command:ZEQM : BTS= <bt s no>: STI RC=Y;

The BSC sends the STIRC enable for the sector

in the BTS_CONF_DATA (BTS-id, ST-IRC mode‘ON’).



Check the alarms at the BSC using MML:






7. The Master EDGE TRX (TRX 1 of thechain Master cabinet 1) is removed.

When the Master EDGE TRX is removed, alarm7767 BCCH MISSING and LAPD link alarms

7705 and 7706 O&M alarms are active. Theconnection between the BTS Manager and theBTS is lost.

All calls from the BTSs are released due to theloss of frame clock from the Master TRX, andnew calls cannot be established.





Test cases


8. The Master EDGE TRX is replaced with aGSM TRX of the same band.

The replaced GSM TRX initialises and alarm7606 (NON-EDGE TRX DEVICE TYPE USED

ACCIDENTALLY IN EDGE CAPABLE MODE) isreported on BTS Manager and at the BSC for theGSM TRX.











373589.01 4 +4+4(EDGE) Chain Any BB hopping

2.5.3.12 Swap a GSM TRX into the Master slo t of a Slave cabinet wi th STIRC enabled

Purpose:



placed in the Master slot of a Slave cabinet.





2. Monitor the Abis. Abis monitoring of OMU link and TRX links.









65 (84)






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




7. The Master EDGE TRX (TRX in position 5or 9) in the Slave cabinets is removed.

When the Master TRX in the Slave cabinets isremoved, alarms 7767 BCCH MISSING and 7705LAPD LINK FAILURE are active for the Slavecabinets.

8. A new GSM TRX is inserted into the emptyposition of the previously removed MasterEDGE TRX, a BTS lock/unlock is requiredin order to take the new TRX into the BB-

hopping sequence.

The Chain Master TRX detects new insertedMaster TRX of the Slave cabinet, and MMI showsthe new TRX.

The Chain Master TRX synchronises andconfigures new hot-inserted Master TRX of theSlave cabinets.

Also Slave TRXs in the Slave cabinet aredetected, the MasterTRX initialises and alarm7606 (NON-EDGE TRX ACCIDENTALLY USEDIN EDGE CAPABLE MODE) is reported on BTSManager.




The BTS is initialised, the BSC sendsBTS_CONF_DATA STIRC disabled, information

is checked in the BTS_CONF_DATA, BCFreturns to working state and BTS Managerconnection establishes.







373593.01 4+4+4 (EDGE) Chain Any BB

2.5.3.13 Swap a GSM TRX into the Slave slot of a Slave cabinet wi th STIRC enabled

Purpose:



placed in the Slave slot of a Slave cabinet.





Test cases



















7. The Slave EDGE TRX in the Slave cabinetis removed. The Master TRXs (TRX isposition 5 and 9, cabinet 2 and 3).

When the Slave TRX is removed, alarm 7606 TRX FAULTY is active for the removed TRX.

8. A new GSM TRX is inserted into the emptyposition of the previously removed SlaveEDGE TRX, a BTS lock/unlock is requiredin order to take the new TRX into the BB-hopping sequence.

The Chain Master TRX detects hot-insertedSlave GSM TRX, and MMI shows the new GSM TRX.

The Chain Master TRX synchronises andconfigures new hot-inserted Slave GSM TRX,and alarm 7606 (NON-EDGE TRXACCIDENTALLY USED IN EDGE CAPABLEMODE) is reported on BTS Manager and theBSC for the GSM TRX.



BTS_CONF_DATA STIRC disabled is receivedfor the sector.








373596.01 4+4+4 (EDGE) Chain 900 BB Hopping



67 (84)




2.5.3.14 Expand a 4 TRX si te to an 8 TRX site with STIRC enabled

Purpose:


ACCIDENTALLY USED IN EDGE CAPABLE MODE) when the STIRC-

enabled site is expanded.




1. A cabinet with 4 OMNI TRXs is inOperational and Working state.

BCF is in working state.

No alarms are present.







4. New LAPD links and BTS are created at theBSC to expand the BCF with a 4 TRXGSM/EDGE BTS.

STIRC is enabled in the new BTS. A newcabinet with 4 TRXs and without Transmission card is chained to the Mastercabinet.

The expanded Slave site initialises, with theMaster cabinet, STIRC is enabled in the newsector, and alarm 7606 (NON-EDGE TRXDEVICE TYPE USED ACCIDENTALLY INEDGE CAPABLE MODE) is reported on BTSManager and at the BSC for the GSM TRXs, inthe BTSs. The remaining TRXs return to workingstate.

5. Disable STIRC in the new BTS using theMML command:


BTS_CONF_DATA with STIRC disabled isreceived.


6. Check BCF status check alarms at BSCusing MML:





7. Calls are made on all TRXs. Calls are successful.

Case Ref. Configuration Expanded to Band

373601.01 4 OMNI (EDGE) 4(EDGE)+4(GSM/EDGE) Any





Test cases

2.6 Miscellaneous

2.6.1 Stabil ity with STIRC enabled

Purpose:

To check the stability of STIRC-enabled sectors under heavy static load.


• Site as defined in the configuration below.

• MS stations capable of FR, EFR, HR, AMR FR, AMR HR. GPRS,

EGPRS

• Data call setup

• Traffic generator

• The Channel configuration is set as follows:

− BCF = , 1800, For UltraSite - BB2Fs with TSxA and TSxB

− Sector 1: BCCH TRX 1 (EDGE) = MBCCB, SDCCH, MPBCCH,

TCHH, TCHH, TCHF, TCHF(GP), TCHF(GP)

Non-BCCH TRX 2 (GSM)= TCHH, TCHH, TCHH, TCHF,

TCHF, TCHF, TCHF, TCHF

− Sector 2: BCCH TRX = MBCCB, SDCCH, MPBCCH, TCHH,

TCHH, TCHH, TCHF(GP), TCHF(GP)

Non-BCCH TRX = TCHH, TCHH, TCHH, TCHH, TCHH,

TCHH, TCHH, TCHH



The BCF is operational.



2. Memory block reservations are checked

before and after the test. Backgroundsoftware downloading is started.

After the test, there are as many memory blocks

reserved as there were before the test.

3. Monitor the Abis. Abis monitoring of OMU link, and TRX links.



69 (84)





4. Calls are set up according to table below.

Ciphering is used. Cell Broadcast is in usewith minimum spacing. Codec changes arenot allowed (ZEEM: HRI = 3).

The following load is on the BCFs:

• Paging commands =25 000 per hour

• Call Attempts =800 per hour

• SMSs =600 per hour

• Location Updates =600 per hour

Test parameters are set.

5. Set up the data call environment and latchthe phones to the BCCH

Ready for Data Transfer.

6. Enable STIRC for the sector duringbackground SW downloading using MMLcommand:


BSC sends STIRC enable information for BTSobject (sector) in the BTS_CONF_DATA.

STIRC will only be enabled on those TRXs thatdo not exceed the STIRC licence capacity.

7. Test duration is 4 hours (long enough forthe frame number counter to start againfrom the beginning).

Calls remain on-going, and no calls are droppedduring the duration of the test.

8. Stop the Abis monitor, analyse the Abistraces.

Check for any unexpected alarms active andhistory.

Case Ref. Configuration Signalling Hopping mode

sectors

Call Types

366546.02 2+2 (EDGE) 16 kbit/s,

Dynamic,

A-bis

Sect1: BB

Sect2: RF

Sect1: 4 AFS, 2 FR, 4 AHS,6 HR, GPRS data transfer(download a file larger than10 Mb downloading to berepeated during test period)

Sect2: 4 AHS, 4 HR, 2 FR,EGPRS data transfer2 HSCSD data calls (each 2 TS * 14.4 kbit/s) with file

transmission larger than 10MB.





Test cases

2.6.2 TRX Test with STIRC enabled from the BSC and BTS Manager

Purpose:

To check that the TRX test can be executed successfully from BTS Manager and the BSC in a STIRC-enabled (EDGE) sector and a non-STIRC (GSM)

sector, and that the BTS_CONF_DATA contains the STIRC option.

Note 37.

Sensitivity in the TRX test depends on:

• The actual sensitivity of the receiver.

• The accuracy of measurements (+/-4dB) (including MHA , gain and cableloss allowances)

• The interference from mobile stations in neighbouring cells.

Acceptable test results

The acceptable test results for this test are:

• BER = 0%

• RX Sensitivity:

− -110.5 dBm (or better) for GSM 900 and GSM 800

− -111 dBm (or better) for GSM 1800 and GSM 1900

− (Typical values non-interference in Lab conditions are from -112

dBm to -100 dBm.)

• The threshold values of TRX performance test need to be defined as thedefault values.

• The default threshold or TRX performance test values for MetroSite are:

Transmitted Metro Power (PWRM) = 30 dBm

Transmitted Metro HP Power (PWRH) = 37 dBm

Transmitted Metro XP Power (PWRX) = -40 dBm

BER (BER) = 0.2000%

RX Sensitivity (MSENS) = -100 dBm

At the BSC, the current threshold values of TRX performance test can be

verified using the following MML command:

ZUCV: TRP, CURRENT;

If the current threshold values differ from the default ones, they should be

modified with the following MML command:

ZUCV: TRP, MODI FY: PWRU=<pwr u_val >, BER=<ber _val >, MSENS=<msens_ val >;



71 (84)




Note 38.

EDGE TRX (EGPRS enabled):

When the TRX test is performed for an EDGE TRX, both the GMSK and 8-

PSK modulation methods are possible. The modulation scheme tested is

indicated in the report when BTS Manager is used.

EDGE TRX (EGPRS disabled):

When the TRX test is performed for an EDGE TRX, both the GMSK and 8-

PSK modulation methods are possible. If the TRX test is performed from the

BSC using the 8-PSK modulation scheme, the test shall be performed using the

GMSK modulation as the TRXs are EGPRS disabled. The GMSK modulation

scheme shall be indicated in the report when BTS Manager is used.

GSM TRX:When TRX test is performed for a GSM TRX, both the modulation methods are

available at BSC. However, when the test is started using the 8-PSK

modulation, the BTS shall determine that the wrong modulation type is selected

for the TRX, change the TRX test to use GMSK modulation and indicate this in

the report. When the TRX test is started from BTS Manager modulation method

is not selectable and test will be performed using GMSK modulation.

Note 39.

When the test is started from BTS Manager, the alarm 7615 RTS IS IN TEST

USE for used TS is started. When the BTS Manager finishes the test, the alarm7615 RTS IS IN TEST USE for the used TS is cancelled.

This alarm may not be included in the alarm history at the BSC as the BSC uses

time-window based filtering for alarm reporting. That is, if an alarm is started

and cancelled within 10-seconds.

Note 40.

For all the tests that require the TRX test to be run, the PMAX value should be

set as maximum (that is, 0).

The expected range of TX power level from TRX test is transmitted power levelPMAX value ± 4dBm.

Note 41.

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

unless otherwise stated.





Test cases

Note 42.

BTS non-hopping unless otherwise stated.


• As defined in the test case below.

• Spectrum Analyzer


1. The configuration in use is as listed in the testcase.


2. Enable STIRC in the EDGE sector using MMLcommand:

ZEQM: BTS=<BTS I D>: STI RC=Y;

3. The Abis interface is monitored. The BSC sends BTS_CONF_DATAcontaining the STIRC option setting, STIRCON.

4. Trace master is used to monitor the UC-DSPtraces during the test.

STIRC information is sent to the EQDSP inthe INI message for the sector.

5. A CS call is made on the TRX to be tested. Call is successful.

6. A TRX test is started from the BSC using MML

command ZUBS

The TRX test is performed with bothmodulation methods consecutively; firstlyGMSK, then 8-PSK.

The test is repeated for unreserved timeslots inthe TRXs for both EDGE and GSM sectors.

Test is started for idle channels, test will not

start on control channels, or channels active ina call.

7. The BTS Manager Application is started.

A TRX test is started from the BTS Manager:click Test Æ TRX Test…

The TRX test is performed with both

modulation methods consecutively; firstlyGMSK, then 8-PSK.

The test is repeated for unreserved timeslots inthe TRXs for both EDGE and GSM sectors.

Test is started for idle channels, test will notstart on control channels, or channels active ina call.

Test results information displays in the BTSEvents window.



73 (84)





8. The test results are checked from the BSCusing MML command ZUBP

Check the results after every TRX test. The TXpower level and modulation scheme is verifiedwith a Spectrum Analyser.

The test results on BTS Manager are checked,the TX power level and modulation scheme isverified with a Spectrum Analyser.

The test is successful and the test results areacceptable as defined in the description

above.

TRX test is started on an idle channel.

Correct modulation scheme is observed onSpectrum Analyser. CS ongoing call is notaffected.


366549.03 2( GSM) + 2 (EDGE) Any none

366549.04 4 OMNI (EDGE) Any none

2.6.3 Enable STIRC via NetAct

Purpose:

To confirm that sectors can be STIRC enabled using NetAct.

Note 43.

Radio Network Manager can be started from Top-level User Interface under the

Utils menu. It provides the means to manage the radio network objects and

parameters in the BSS.


• As defined in the test case below.

• Fully operational BSS and NSS are required for the testing.


1. On the Top-level User Interface, selectUTILS Æ NETWORK CONFIGURATIONMGMT Æ RNW MANAGER

Select the BCF.

From the pull-down menu, select BTSSTIRC is enabled for the BTS.

2. The Abis interface is monitored. The BSC sends STIRC enable information for theBTS object (sector) in the BTS_CONF_DATA.

STIRC will only be enabled on those TRXs that donot exceed the STIRC licence capacity.





Test cases


3. Repeat the steps for different BTSs in thenetwork.

All BTSs are STIRC-enabled successfully.

4. Test calls are taken via the BCF. Calls are made successfully.

Case Ref. OSS Version BCF Configuration Band

366550.03 OSS3.1 ED3 Any Any

366550.04 OSS4.1 Any Any

2.6.4 Enable STIRC during background software downloading

Purpose:

To confirm that sectors can be STIRC-enabled during background software

downloading.




1. The configuration in use is as listed in the test

case. The BCF is operational.

2. BTS SW packages have been installed at theBSC.

The Abis is monitored whilst the SW isdownloading from the BSC to the BCF.

Service terminal extension RPHASESX is usedto monitor the process of SW downloading of the BCF.

Calls are made via TRX(s) and maintained

during background downloading of SW.CX5 is active and is latest in flash.

3. Use the MML command ZEWA to start CX4.1BTS SW background downloading.

The SW package starts backgrounddownloading from the BSC to the BCF.

Calls are not released during downloading.



75 (84)





4. Enable STIRC for the sector during backgroundSW downloading using MML command:


The BSC sends STIRC enable informationfor the BTS object (sector) in the

BTS_CONF_DATA.

STIRC will only be enabled on those TRXsthat do not exceed the STIRC licencecapacity.

The background downloading is not affectedcalls are not released and completes the SWdownload successfully.

5. After the background downloading is complete,the BTS SW package CX4.1 is not activated.

All ongoing calls are terminated by user.

6. Contents of the flash memory is checked. CX5 in use, CX5 and CX4.1 in flash.Case Ref. Configuration Active SW and flash

contents at the beginningBackgrounddownloaded(not activated)

End State

366555.02 12 TRX OMNI(EDGE) Chain –BB hopping

CX5 in use and in flash.

Ensure that CX4.1 is not inflash.

CX4.1 CX5 in use.CX5 andCX4.1 in flash

2.6.5 STIRC enabled sector and FACCH

Purpose:

To ensure that a TCH channel can be first used for signalling (call

establishment) and modified to speech channel on a TRX in a STIRC-enabled

sector.

Note 44.

Call setup on FACCH means that all the call set up signalling takes place on the

FACCH channel and that SDCCH is never used. The FACCH is sent on the

TCH and "steals" the whole TS from the TCH.

This can be verified by checking that the immediate assignment is carried out

directly on TCH/FACCH.





Test cases

Note 45.

To interrogate the status of Dynamic SDDCH, use the following MML

command:

ZWOI : 10, 42: ;

To change the status of the parameter (on/off), use the command:

ZWOC: 10, 42, <0000 ( f al se) or 00FF ( t r ue)>: ;




1. The configuration in use is as listed in the testcase.




3. The Abis interface is monitored. BSC sends STIRC enable information for BTSobject (sector) in the BTS_CONF_DATA.

STIRC will only be enabled on those TRXs thatdo not exceed the STIRC licence capacity.

4. Dynamic SDCCH feature is not active in theBSC. The static SDCCH are reserved.

5. Set up a CS call from MS to MS.

Monitor the Abis.

When the call has been up for 60 seconds,release it.

Check with ZEROthat the TSs return to idle.

Repeat the test 5 times.

All calls are established via FACCH on TCH TS. After signalling is complete the TS ischanged to appropriate codec via Mode Modifymessage. SDCCH is never used.

Calls are held until terminated.

The call is released OK. The TSs are returnedto idle.

The received audio quality is good and without

distortion.Case Ref Configuration Band

366557.02 4 OMNI (EDGE) Any



77 (84)




References

1. Nokia BSC/TCSM S11 Product Documentation, NED5.3, NOLS.





Appendix A: Feature/HW/Configuration Matrix

Appendix A: Feature/HW/Configurat ion Matrix

Feature Test Case TAG

Intelligent Shutdown 366451.03, 366451.04, 366457.03, 366457.04Multi BCF 366476.02RF hopping 366451.04, 366457.03, 366480.03, 366480.04,

366483.02, 370239.05, 370247.04, 370249.04,370251.05, 370252.05, 370254.05, 367698.11,367687.12, 366546.02

BB hopping 366451.03, 366457.04, 366480.05, 366480.06,366491.03, 370239.04, 370247.05, 370249.05,370251.04, 370252.04, 370254.04, 367698.16,367687.13, 367703.02, 373589.01, 373593.01,373596.01, 366546.02, 366555.02

DFCA 366502.02

Common BCCH 367476.02RSSI 366504.03EPCR 366507.03, 366507.04EMR 366511.03, 366511.04Link Adaptation 366509.03, 366509.04Administration (BCF/BTS/TRX lock/unlock/Block/Unblock/Reset

367698.11 – 19, 368687.09 – 15

LAPD Failure 367703.02, 367703.04, 367703.06Hardware Actions 373335.01, 373352.01, 373400.01, 373416.01,

373424.01, 373429.01, 373453.01, 373466.01,373581.01, 373586.01, 373589.01, 373593.01,373596.01, 373601.01

Stability 437813.01

Configuration Test Case TAG

4 OMNI (EDGE) 366480.03, 366480.05, 366504.03, 366507.03,366507.04, 366542.02, 370239.04, 370239.05,370239.06, 370247.04, 370247.05, 370247.06,367698.11, 367698.14, 367398.15, 367698.16,367398.17, 367687.12, 367687.13, 367703.02,367703.04, 367703.06, 373335.01, 373352.01,373429.01, 373453.01, 373466.01, 373601.01,366549.04, 366557.02, 437813.01

4 OMNI (GSM) 373453.01, 373466.012 TRX EDGE/GSM 373416.01, 373424.012 (GSM)+2 (EDGE) 366480.04, 366480.06, 367687.09, 366549.032+2 (EDGE) 366511.03, 366511.04, 366509.03, 366509.04,

366538.02, 370249.04, 370249.05, 370249.06,370251.04, 370251.05, 370251.06, 370252.04,370252.05, 370252.06, 370254.04, 370254.05,370254.06, 367698.12, 367698.13, 367687.10,367687.11, 367687.15, 373400.01, 366546.02

4 (GSM) +4 (EDGE) 367476.024+4+4 (Multi BCF – Talk – Metro – Metro - Metro) 366476.024 (GSM) +4 (EDGE) +4 (EDGE) 367698.184 (GSM) +4 (EDGE) +4 (GSM/EDGE) 366483.02, 366491.03



79 (84)




4+4+4 (EDGE) Chain 366451.03, 366451.04, 366457.03, 366457.04,366502.02, 367687.14, 373589.01, 373593.01,373596.01

4(GSM)+4(EDGE)+2(EDGE) 373581.01, 373586.01

12 OMNI (EDGE Chain) 367698.19, 366555.021+1+1+1 (EDGE) 366513.03, 366513.04





Appendix B: RF set-up to establish known C/I conditions

Appendix B: RF set-up to establ ish known C/I condit ions

The figures on the following pages illustrate the MetroSite RF set-up for uplink

quality measurements for main receiver and diverse receiver.



81 (84)








Appendix B: RF set-up to establish known C/I conditions



83 (84)




Appendix C: Measuring Co-Channel C/I

Measuring Carrier Power

Measure using a spectrum analyser (e.g. Rohde & Schwartz FSEB)

• Span set to zero.

• Trigger using frame clock output from BOIA.

• Switch off interferer.

• Capture a burst.

• Set time-lines at the beginning and end of the burst.

• Average power between time-lines.

• Repeat 5 times and take average of 5 measurements.

Setting the Interferer

Use a signal generator (e.g. Rhode & Schwartz SMIQ 03B).

• Switch off carrier source.

• On the spectrum analyser set a display line at the desired interferer level

below the carrier power measured above. For example, if required C/I is

15 dB set the display line 15 dB below the carrier power.

• Switch on a continuous interferer on the signal generator.

• If the carrier is from a speech call set digital modulation = GSM.

• If the carrier is from EGPRS transfer set digital modulation = EDGE (8-PSK).

Documents

System Test STIRC DN0691283x1x0xen