B9 Twin TRA Introduction and BTS With 24 TRE System Test Strategy BSS ed01.pdf

ED01 Released TWIN TRA Introduction and BTS with 24 TRE System

Integration Test Strategy BSS Release B9

3BK130240191DSZZA_E01.doc 13/06/2006 3BK 13024 0191 DSZZA 1/18

All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

Site STUTTGART

EVOLIUM SAS

Originator T. Glauner

TWIN TRA Introduction and BTS with 24 TRE System Integration Test Strategy BSS Release B9

System : ALCATEL GSM BSS Sub-system : SYS Document Category : VALIDATION

ABSTRACT This document contains the test strategy at System Integration level for the new TWIN TRA HW, in B9 MR4. This strategy ensures also a full Hardware qualification, as all the tests are done in a real system environment.

Approvals

Name App.

Grégory ACBARD B9 VAL DPM

Daniel BOMY B9 TPL

Bruno FERNIER B9 QM




All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

REVIEW Ed. 01 Proposal 01 03/03/2006 EVOLIUM/R&D/BTS-DP/TG-cw609-5 Ed. 01 Proposal 02 17/03/2006 EVOLIUM/R&D/BTS-DP/TG-cw611-5 Ed. 01 Proposal 03 27/03/2006 EVOLIUM/R&D/BTS-DP/TG-cw613-1 Ed. 01 Proposal 04 02/05/2006 no comment received

HISTORY Ed. 01 Proposal 01 03/03/2006 Creation Ed. 01 Proposal 02 17/03/2006 Taking into account the remarks from

- Rainer Wohlfahrt BTS-DP - Stefan Rosewig BTS-DP - Gregory Acbard VAL DPM For details refer to review report with the reference: “EVOLIUM/R&D/BTS-DP/TG-cw609-5”

ED. 01 Proposal 03 27/03/2006 Taking into account the remarks from - Gregory Acbard VAL DPM - Ciprian Carlig (no remark) - Cristian Carpinisan SED - Eric Bruth VAL For details refer to review report with the reference: “EVOLIUM/R&D/BTS-DP/TG-cw611-5”

ED. 01 Proposal 04 02/05/2006 Taking into account the remarks from - Bernd Dreher BTS-DP - Elena Ciocan TPR-MBS - Mihai Brateanu TPR-MXM - removal of SUMP related test cases from the test list - correction of table 3, some test cases have been counted twice - removal of already closed OP1 and OP2 from §10.2 - removal of OP 3 of §10.2: nothing needed for LASER - removal of OP 4 of §10.2: TTX (MTI) list completed with remarks from Elena Ciocan and Mihai Brateanu For details refer to review report with the reference: “EVOLIUM/R&D/BTS-DP/TG-cw613-1”

ED. 01 Released 08/06/2006 Some minor editorial updates mainly in the embedded test list




All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

TABLE OF CONTENTS

1 SCOPE..........................................................................................................................................................7 1.1 Document Coverage .........................................................................................................................7 1.2 Split of Responsibility ......................................................................................................................7

2 FEATURE OR DOMAIN OVERVIEW...........................................................................................................8 2.1 Marketing Requirements ..................................................................................................................8 2.2 System impacts.................................................................................................................................9

3 HARDWARE COVERAGE .........................................................................................................................10 3.1 Hardware and Software Impact .....................................................................................................10 3.2 Configuration Coverage .................................................................................................................11

4 SYSTEM PRE-INTEGRATION TEST STRATEGY ....................................................................................11 5 SYSTEM INTEGRATION OR VALIDATION TEST STRATEGY ...............................................................12

5.1 Main Principles................................................................................................................................12 5.2 Detailed Strategy.............................................................................................................................12

5.2.1 Installation...............................................................................................................................12 5.2.2 O&M scenarios .......................................................................................................................13 5.2.3 Logical Configurations ............................................................................................................13 5.2.4 Hardware variants...................................................................................................................13 5.2.5 CS – telecom tests / Voice Quality .........................................................................................13 5.2.6 PS – telecom tests..................................................................................................................13 5.2.7 RMS / EME .............................................................................................................................13

5.3 Test Lists .........................................................................................................................................14 6 INTRA-RELEASE TEST STRATEGY ........................................................................................................16 7 IMPACT ON INTER-RELEASE TEST STRATEGY...................................................................................16 8 IMPACT ON TEST PLATFORM DEFINITION / TEST TOOLS..................................................................16

8.1 Impact on Test Platform Definition ...............................................................................................16 8.2 Impact on Test Tools ......................................................................................................................16

9 EXTERNAL DEPENDENCIES ...................................................................................................................16 10 RISKS ASSERTION / OPEN POINTS........................................................................................................17

10.1 Risks Assertion...............................................................................................................................17 10.2 Open Points .....................................................................................................................................17

11 GLOSSARY AND ABBREVIATIONS ........................................................................................................18

TABLE OVERVIEW Table 1: Frequency bands.......................................................................................................................... 10 Table 2: Impact on sub systems................................................................................................................. 10 Table 3: Number of test cases per test set ................................................................................................ 14 Table 4: Definition of CATE hardware platforms for legacy platforms ....................................................... 15 Table 5: Definition of CATE hardware platforms for Mx platforms............................................................. 15




All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

INTERNAL REFERENCED DOCUMENTS Not applicable

REFERENCED DOCUMENTS [ 1 ] SFD: BTS with up to 24 TRE

3BK 10204 0022 DSZZA [ 2 ] SFD: GERAN TWIN TRA Introduction in B8 and B9

3BK 10244 0073 DSZZA [ 3 ] O&M ABIS INTERFACE B9

3BK 11204 0322 DSZZA [ 4 ] Logical Configuration Management

3BK 11204 0336 DSZZA [ 5 ] Hardware Configuration Management

3BK 11204 0335 DSZZA [ 6 ] ENGINEERING RULES AND CONFIGURATIONS

3BK 15015 BAAA PWZZA [ 7 ] G3 / M4M / G4 / M5M BTS O&M SPECIFICATION AND ARCHITECTURE

3BK 11210 0491 DSZZA [ 8 ] BCB SPECIFICATION

3BK 11210 0162 DSZZA [ 9 ] BSII SPECIFICATION

3BK 11210 0237 DSZZA [ 10 ] B9 Abis: Operation code of Preload file service to be lined up with B8 one

3BK A20 CBR156649 [ 11 ] BTS with up to 24 TREs BSC Test Strategy

3BK 11206 0868 QTZZA [ 12 ] SFD: Radio Measurements Statistics

3BK 10204 0486 DTZZA [ 13 ] RMS improvements

3BK 10204 0544 DTZZA [ 14 ] Electromagnetic Environment (EME) Supervision B9

3BK 10204 0626 DTZZA [ 15 ] RFD: GERAN TWIN TRA Introduction in B8 and B9

3BKA55CBR160097




All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

REFERENCED DOCUMENTS continued [ 16 ] CRQ: BSCGP interface impacts of the RFD "More than 12 TREs in the BTS" (MR4).

3BKA20CBR161111 [ 17 ] CRQ: MIB impacts by BTS with more than 12 TRE feature

3BKA20CBR162436 [ 18 ] CRQ: BOP B9:"BTS with up to 24 TRE" impact: add 2 parameters: Max-FR-TRE-Primary and

Max-DR-TRE-Primary. 3BKA20CBR165990

[ 19 ] CRQ: MR4: Twin configuration control - impact on Abis O&M 3BKA20CBR166870

[ 20 ] CRQ: Add two new error codes for remote configuration Twin TRE 3BKA20CBR167274

[ 21 ] CRQ: Changes of error codes for BTS with up to 24 TRE 3BKA20CBR167906

[ 22 ] CRQ: Support of the "BTS with up to 24 TRE" feature (RFD161918) 3BKA20CBR168762

[ 23 ] CRQ: Removal 2PCM_capability for BTS with more than 12 TRE Feature 3BKA20CBR168997

[ 24 ] CRQ: BOP B9 MR4: Twin remote control: add two parameters: Twin-Configuration-Request and Twin-Capabilities-Usage 3BKA20CBR170128

[ 25 ] CRQ: IMO, B9 MR4, Impact of GERAN TWIN TRA 3BKA20CBR170698

[ 26 ] CRQ: Additional changes of MIB for more up to 24 TRE feature 3BKA20CBR172529

[ 27 ] CRQ: Addition of GERAN TWIN TRA Impacts in document HCM B9 3BKA20CBR172644

[ 28 ] CRQ: B9 NSR: Impact of the twin TRE on Network supervision 3BKA20CBR172769

[ 29 ] Changes of the message bts-config-display-report to avoid the message buffer more than 2K bytes 3BKA20CBR177149

[ 30 ] CRQ: BTP : no more than 12 TRX PS capable per cell 3BKA20CBR177321




All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

REFERENCED DOCUMENTS continued [ 31 ] CRQ: SBL concept B9: impact "BTS with up to 24 TRE" (MR4): increase of range for the SBLs:

RSL, CU, FU 3BKA20CBR172965

[ 32 ] CRQ: BTP: no more than 12 TRX PS capable per cell 3BKA20CBR177321

[ 33 ] CRQ: OMC/BSC HW/SW file format: doc for TRE G5 file numbers 3BKA20CBR180687

[ 34 ] TWIN TRA Introduction and BTS with 24 TRE - Impact on BSS O&M System Integration Test Strategy B9 3BK 13024 0192 DSZZA

RELATED DOCUMENTS [ a ] Test Impact Analysis - Template

8BL 14308 0005 PTZZA [ b ] B9 TTF – Proposal for a Test Strategy Document

R&D/VAL-GSM/04-872/GAC [ c ] General System Integration Test Strategy - BSS Release B9

3BK 13024 0151 DSZZA [ d ] General System Validation Test Strategy - BSS Release B9

3BK 13024 0171 DSZZA [ e ] System Validation Documentation Plan - BSS Release B9

3BK 10242 0015 DCZZA




All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

1 SCOPE

1.1 Document Coverage

This Document describes the test strategy at System Integration level for the new TWIN TRA Hardware in B9 MR4.

1.2 Split of Responsibility

The SI is either done by the BTI-team in Stuttgart or the MXM and MBS team located in Timisoara. It covers the writing of this SI test strategy and the related CATE test sheets and as well the test execution itself. Contributors to the Document: The main author of this document is Thomas Glauner (BTI). Document is reviewed within the TTF-WG4.




All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

2 FEATURE OR DOMAIN OVERVIEW

2.1 Marketing Requirements

The request for development of “GERAN TWIN TRA Introduction in B8 and B9” (RFD: 3BKA55CBR160097) was made due to following reasons:

- Reduction of network installation and operation costs - Introduction of new features

o TX Diversity / 4 RX Diversity o TX Diversity / 2 RX Diversity o Support of BTS Configurations > 12 TRX

- Shop cost reduction to compensate decreasing market prices - Support of 3GPP GERAN 5 & 6 Features - Support of EDGE Evolution (under definition at 3GPP) - Support of IP transport in BSS

Constraints:

- GERAN TWIN TRA has to be compatible to G4.2 TRA Module o in terms of external electrical interfaces o in terms of external physical dimensions o in terms of power dissipation and heat distribution

It is intended to mix all TRE/TRA (G3, G4, EDGE+) versions or a subset of them in the same sector of a BTS. However some restrictions regarding the mixture of G3/G4 and TWIN TRA are existing, for details refer to [ 1 ] and [ 4 ].




All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

2.2 System impacts

The introduction of the TWIN TRA has various impacts on the system architecture. The most relevant system adaptations and their impact on the test strategy are briefly described in this chapter. For all the detailed changes please refer to the relevant specifications [ 1 ], [ 2 ], [ 3 ] and [ 4 ]. The TWIN-TRA itself is a new RIT and therefore it must be ensured that this RIT is reported properly on each interface, in particular between the BTS and BSC and as well between BSC and OMC. It must be verified that it is correctly displayed on each HMI that includes the BTS-LMT, BSC-LMT and OMC. Furthermore it is obvious that all allowed O&M actions like LOCK, UNLOCK, RESTART and RESET are properly executed on this module according to the specifications. The Test sets “Installation” and “O&M scenarios” are mainly covering these aspects. Larger BTS and cell configurations are possible due to the introduction of the TWIN TRA. BTSes up to 24 TREs or cells up to 16 TRX are implying that data arrays in the sub systems are adapted to support these capacity improvements. It is therefore a must to include test cases that cover these configurations. These configurations are also used to verify some “worst case” consequences like USOD with 16 TRXes on one cell, BBH with 16 frequencies and error cases on TRE numbers 12 to 24 or TRX 12 to 16. Of course it is also verified that the network monitoring elements NPA and RNO are also able to handle these configurations. The test sets “O&M scenarios”, “Hardware variants” and “Logical configurations” are taking these requirements into account. Another aspect of the increased BTS and cell capcity is that now also normal CS scenarios are possible on the second Abis. This requires updates in the allocation and mapping strategy for RSLs/TRes in the BSC. The test cases with maximum configuration will explicitly cover this impact. A dedicated test to verify the behaviour for error situations either on the first or second Abis is added in the test list. In case of a removal of TREs from a certain cell it is possible, that a new mapping of RSLs is triggered using the function “Fill up primary Abis”. A specific test is covering this functionality. The TWIN TRA itself can be used either in “1 TRX mode” or “2 TRX mode”, which means that a single TWIN TRA carries either 1 TRX or 2 TRXes. These modes are also called “single mode” or “dual mode”. In 1 TRX mode the TWIN TRA can be operated in “TX Div” mode or “No TX Div” mode. Additionally the TRXes of a TWIN TRA in 2 TRX mode may belong either to one cell or to two different cells. These possible configurations are split over the different test sets, in order to have a huge variation of possible configurations. As the TWIN TRA is supporting all existing CS and PS functionalities and as well EME counters and RMS statistics, it is obvious that a large set of telecom scenarios have to be applied to ensure the telecom functionality. In order to reduce the overall number of test cases most of these basic scenarios are done in combination with voice quality tests in order to collect in parallel Qvoice measurement data that can be compared with legacy TRE modules. These tests are done in the “CS-telecom tests/voice quality”, “PS-telecom tests” and “RMS/EME” test sets. While doing the RMS tests it is also tested implicitly that the cell aggregation for PM counters on large cell configuration is working well. Although there is no direct dependency between the new TWIN TRA and a certain cell configuration various cell types are used in the different test cases. Despite normal cells, at least concentric cells, multiband cells and cell-shared configurations are used in the test cases. A dedicated test for extended cells is introduced, as this particular configuration requires a specific area in the TRE software. For completeness also the new B9 feature “Unbalanced output power per BTS sector” is verified with a TWIN TRA in 2 TRX mode connected to different sectors, one antenna path is not bridged in order to gain 3 dB more power at the antenna. All mentioned test sets in this paragraph are described more detailed in §5.2.x (with x = 1 to 7 ) of this document.




All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

3 HARDWARE COVERAGE

3.1 Hardware and Software Impact

System: GSM 900 Y DCS 1800 Y GSM 850 N DCS1900 N

Table 1: Frequency bands Network element: In the following tables, indicate: Xsw if feature supported by the NE with software impact, Xhw if feature supported by the NE with hardware impact Xsw+hw if feature supported by the NE with software and hardware impact. X : The feature is supported on the NE without hardware or software impacts. - : The feature is not supported by the NE or the NE is not concerned by the feature

Component / Variant Impact A9120 Evolium BSC (BSC G2) Xsw

A9130 BSC Evolution (MxBSC) Xsw POLO Xsw

BSC

OEF Xsw

TC G2 / DT16 -

TC G2 / MT120 -

TC

A9125 TC (TC G2.5) -

CS / AS800 Xsw

CS / DS10 - RC23 Xsw

CS / DS10 - RC40 Xsw

GPU2 Xsw

MFS

GPU2 / AC Xsw

A9130 MFS Evolution (MxMFS) Xsw G1 MKII BTS / DRFU -

G2 BTS / DRFU -

BTS

A9100 BTS Evolium BTS Xsw

A1353 RA Xsw

A9157 NPA Xsw

A9156 RNO Xsw

O&M

A9157 LASER -

Tools BTS-Terminal Xsw

BSC-Terminal Xsw

Table 2: Impact on sub systems




All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

3.2 Configuration Coverage

The following variants need to be tested for the new TWIN TRA Hardware: • mixture of different TRE-types (G3 / G4 / TWIN TRA) • GSM900 and DCS1800 • G4 BTS (SUMA) • MXBSC and BSC G2 • MXMFS and legacy MFS

4 SYSTEM PRE-INTEGRATION TEST STRATEGY The impact of the new TWIN TRA was covered by the three SPI activities SPI-401, SPI-402 and SPI-403.: Each of it covers a specific aspect in a dedicated part of the BSS. After passing successfully the three SPIs it should be possible to start smoothly the system integration for this feature. The name and content of each SPI is briefly presented below.

• SPI 401: BSC-OMC interface (MIB) Tests: This SPI is an interface SPI that covers the impact of the TWIN TRA including the new introduced parameters and as well the impact of some other features introduced or modified in B9 MR4. There are 3 basic tests related to the TWIN TRA.

• SPI 402: TWIN TRE ( w/o TWIN HW) (Declaration cases; HCM cases - except ABIS O&M; BSCGP) This SPI combines functional and interface (BSCGP) aspects around the introduction of the TWIN TRA and the functionality of BTS with 24 TREs and cells with 16 TRX. It contains 19 Hardware Configuration Management tests and two Logical Configuration Management tests.

• SPI 403: TWIN TRE (Abis O&M - with TWIN HW; Basic function) This SPI covers functional tests and interface aspects related to the TWIN-TRA introduction. It contains 21 test cases.

For more details related to each SPI please refer to the embedded documents below. As all the three documents are using a different layout that is also not homogenous to the structure of this document, the content of the documents is not inserted via “copy and paste”, but the whole document is embedded. SPI 401: SPI 402: SPI 403:

b9_twds_spi401_e02.doc

"MEMO_B9MR4_SPI 402_e1p2.doc"

B9_MEMO-TWIN_introduction_e01r1.doc




All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

5 SYSTEM INTEGRATION OR VALIDATION TEST STRATEGY

5.1 Main Principles

During the System Integration test phase the new TWIN TRA hardware will be tested with a BSS platform (real BTS, BSC, MFS, OMC-R, NPA, RNO and TC). The main purpose of this system test activity is to ensure that the new TRE hardware

• fulfils all the functions of the old G3/G4 TRE hardware • can replace all existing G3/G4 TRE modules in the GSM 900 and DCS 1800 frequency band • can be handled according the specification from the whole system.

Additional it is necessary to check all the new features: • ‘1’ and ‘2’ TRX mode • Tx Diversity • 2 Rx Diversity • 4 Rx Diversity • 24 TRX per BTS • 16 TRX per Cell

5.2 Detailed Strategy

The tests are split into basic test sets. Test sets that ensure the functionality and the handling of the new TWIN TRA hardware in the system and test sets that cover new and basic features. The main principles and scope of each test set is described in the next paragraphs. As already described in §2.2 of this document it is important to guarantee for each test set below that at least one a maximum configuration like 24 TREs per BTS and 16 TRX per cell is involved in each test set, or that a specific functionality that has been identified either in §2.2 or in one of the paragraphs below is tested on a maximum configuration.

5.2.1 Installation

The purpose of this test set is the checking of the SW DL part and the SW_ACTIVATE part. The objective is to check that the TWIN TRA can be loaded and initialised by the OMU taking into account all the decisions given in the specifications regarding the HW/SW/DB contents (CPF/CDM/HW), SBL states and SBL failures. It is done by using the methods of the GCD related to the installation of the new TWIN TRA Hardware in the network. The details are given in [ 1 ], [ 2 ], [ 3 ], [ 5 ], [ 6 ], [ 7 ], [ 8 ], [ 9 ] and [ 10 ].




All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

5.2.2 O&M scenarios

The purpose of this test set is to ensure that the BTS O&M part (i.e. Start up Procedure, Fault Management, Alarm Handling, BTS Configuration/Reconfiguration Management, Equipment Handling etc.) is working correctly for the new TWIN TRA hardware. The test cases are done on each relevant field configuration like, single mode, dual mode, and twin tre belonging to the same or different cell. The details are given mainly in [ 1 ] and [ 3 ]. Especially it is checked that the reporting of the new TWIN TRA is correctly done on each HMI (OMC, BSC-LMT and BTS-LMT).

5.2.3 Logical Configurations

With this test set all relevant logical configuration will be checked. The objective is to ensure that the TWIN TRA can be configured in all relevant logical configurations in “1” and “2” TRX mode. The focus is on worst-case situations like BBH with 16 frequencies in one cell, RH with 64 frequencies, specific ARFCNs like “0” and the mixture of P-GSM and E-GSM frequencies. For details refer [ 4 ].

5.2.4 Hardware variants

With these test cases all possible hardware mixtures will be checked. The objective is to ensure that the TWIN TRA can be mixed with all older hardware variants (G3 and G4) in “1” and “2” TRX mode. It is also scope of this test set that the existing restrictions regarding the mixture of G3 and TWIN TRA are properly respected by all involved sub systems. For details refer to [ 1 ], [ 2 ], [ 4 ], [ 5 ] and [ 6 ].

5.2.5 CS – telecom tests / Voice Quality

The purpose of this test set is the checking of the basic CS-call handling functionality. The objective is to ensure that the new TWIN TRA hardware is able to handle HR / FR, EFR, AMR-HR/FR and CS-Data calls in “1” and “2” TRX mode. Handovers between TWIN TRA and G3/G4 TREs and handovers between two TRX within the same TWIN hardware are tested. For these basic call tests the Qvoice equipment will be used to compare additionally the Voice Quality with the values achieved on older TRE modules.

5.2.6 PS – telecom tests

The objective of this test set is to ensure that the new TWIN TRA is able to do PS- calls in “1” and “2” TRX mode in different logical configurations. Multiple CS/MCS coding schemes are used in UL/DL.

5.2.7 RMS / EME

The purpose of this test set is to ensure that the new TWIN TRA is doing a correct reporting for RMS and EME, taking into account the different configuration aspects. It covers the correct message format and as well the correct counter increment. For this some test cases out of the CEE/RIS package are select and updated with the new hardware configuration.




All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

Note relevant for paragraphs 5.2.1 to 5.2.7: As not all tests can be done with each logical configuration possibility and in each frequency band, the test cases are distributed over several platform configurations and belonging to different frequency bands in order to reach a maximum possible test coverage.

5.3 Test Lists

Please refer to embedded Excel file:

TwinTra-08-06-2006-ed01-rel.xls

For a better overview, the total number of tests is summarized in the table below.

Features / Domain Number of test case on Legacy platforms

Number of test cases on Mx platforms

Installation 4 4 O&M scenarios 14 8 Logical Configurations 4 3 Hardware variants 5 2 CS Telecom tests / Voice Quality 21 1 PS - telecom tests 7 5 RMS / EME 2 Total 57 23

Table 3: Number of test cases per test set




All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

Following defined CATE hardware platforms are ensuring a huge coverage related to possible equipment mixtures and configuration variants in both frequency bands:

Configuration

Single Mode

Dual Mode

same cell

different cell

GSM 900 DCS 1800

SUMA 1 x x 2 x x x 3 x x x 4 x x x 5 x x x x 6 x x x x 7 x x x 8 x x x x 9 x x x x 10 x x 11 x x x 12 x x x 13 x x x x 14 x x x x

Table 4: Definition of CATE hardware platforms for legacy platforms

Configuratio

n Single Mode

Dual Mode

same cell

different cell

GSM 900 DCS 1800

SUMA 1 x x 2 x x x 3 x x x 4 x x x 5 x x x x 6 x x x x 7 x x x x 8 x x 9 x x x 10 x x x 11 x x x x

Table 5: Definition of CATE hardware platforms for Mx platforms




All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

6 INTRA-RELEASE TEST STRATEGY No Intra – Release Test Strategy is required as this feature is completely new in B9-MR4.

7 IMPACT ON INTER-RELEASE TEST STRATEGY As described in $2.2 the introduction of the TWIN TRA and the “24 TREs per BTS” and “16 TRX per cell“ feature leads to various changes in the BSS-SW. It is covered via TWIN TRA Introduction and BTS with 24 TRE - Impact on BSS O&M System Integration Test Strategy B9 3BK 13024 0192 DSZZA.

8 IMPACT ON TEST PLATFORM DEFINITION / TEST TOOLS

8.1 Impact on Test Platform Definition

No specific need related to test platform definition, of course the required modules (GSM900 / DCS1800) and especially enough AGC – modules must be available.

8.2 Impact on Test Tools

The introduction of the new RIT (TWIN-TRA module) and the new features 24 TREs per BTS and up to 16 TRX per cell are requiring also an update of some test tools, as the number of supported items (TREs, TRXs) per instance (BTS, CELL) are changed and a new RIT is reported. Additionally new information elements are introduced on Abis, see [ 3 ] In particular following tools are concerned:

• K1205 – Monitor for Abis RSL and OML • PMCONVERT – decoding tool for PM binary files • CMISE decoding between OMC and BSC

The necessary adaptation of the K1205 has been already addressed to the SPI-403 activity from Rainer Wohlfahrt (refer to email from Gregory Acbard from 08.03.2006 7:08 to Rainer Wohlfahrt) The PMCONVERT and CMISE decoding changes should be introduced by the related DPs during the implementation of the feature related SFD. The development of the CMISE decoder is already done.

9 EXTERNAL DEPENDENCIES No external dependencies are identified.




All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

10 RISKS ASSERTION / OPEN POINTS

10.1 Risks Assertion

Currently no risk identified. Risk # Description Analysis result

none none none

10.2 Open Points

OP # Description Assigned to Action / Status

OP5 Impact on migration and SWR due to the new BTS MR4 software that supports the TWIN TRA

C. Camard Open: Indicate the reference in NEO that covers the migration aspects B8 – B9 and SWR B8-B8 due to the new TWIN TRA SW.

OP6 Impact of TWIN TRA introduction on OMC export files

C. Dulgheru Open: Describe the impacts and potential test cases of the TWIn TRA introduction on OMC export files. Which OMI tests are covering it ?




All rig

hts re

serve

d. Pa

ssing

on an

d cop

ying o

f this

docu

ment,

use a

nd co

mmun

icatio

n of it

s con

tents

not p

ermitte

d with

out w

ritten

autho

rizati

on fro

m Ev

olium

11 GLOSSARY AND ABBREVIATIONS BSC Base Station Controller BTI BTS-DP System Integration Team DP Development Project DPM Development Project Manager LMT Local Maintenance Terminal (BSC or BTS) MFS Multi Function Server MS Mobile Station MSC Mobile Switching Centre NE Network Element NPA Network Performance Analyzer O&M Operation & Maintenance QM Quality Manager RNO Radio Network Optimizer SED System Engineering Documentation team SI System Integration SPI System Pre Integration TPL Technical Project Leader TTF Test Task Force GCD Generic Customer Documentation WG Working Group RMS Radio Measurements Statistics EME Electromagnetic Emission

END OF DOCUMENT

B9 Twin TRA Introduction and BTS With 24 TRE System Test Strategy BSS ed01.pdf

Documents

Transcript of B9 Twin TRA Introduction and BTS With 24 TRE System Test Strategy BSS ed01.pdf