Customer Corrections DN0691186x1x0xen

8/22/2019 Customer Corrections DN0691186x1x0xen

http://slidepdf.com/reader/full/customer-corrections-dn0691186x1x0xen 1/18

Nokia MetroSite EDGE Base Station

Test Specification for ValidatingCustomer Corrections of BTS SW

Release CXM5

DN0691186Issue 1-0 en

©Nokia CorporationNokia Proprietary and Confidential

1 (18)



Test Specification for Validating Customer Corrections of BTS SW Release CXM5

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 (18) ©Nokia CorporationNokia Proprietary and Confidential




Contents

Contents

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

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

2 Test cases ...............................................................................................9 2.1 PR 4029C02: RSSI values and alarm are reported before the

antenna supervision timer expires............................................................9 2.2 PR 3709C02: No calls on sector after BCCH reconfiguration

into GSM TRX..........................................................................................9 2.3 PR 1-200449991: MetroSite BTS enters sleeping mode in high

traffic conditions .....................................................................................11

2.4 PR 1-62223179, 1-77993775: Bad FER Call Time percentagefor the AMR full rate is higher than for the EFR .....................................11

References ............................................................................................18



3 (18)



About this document

1 About this document 1.1 Scope

This document describes the test cases to verify the fault corrections detailed in

the Generic Failure Report for Nokia MetroSite EDGE Base Station [1] in

CXM5 BTS SW release documentation.

Note 1.

The BSC version to be used is S12 unless otherwise specified.

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.

Note 3.

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

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

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



5 (18)




Note 4.

A multi-TRX configuration is a site that has several TRXs, for example, 2+2

TRXs, 4 TRXs, and so on.

A 1-TRX configuration is a site that has one TRX unit (a master TRX).

Note 5.

HVTx: HPCATS, 5 W High Power GSM TRX

CTxA: XPCATS, 10 W EDGE TRX for GSM 900, and 1800 bands

VSxx: Low Power Supply unit

HVSx/CVSx: High Power Supply unit

HVMF: High Power Fan unit

VMFA: Low Power Fan unit

Note 6.

There can be a maximum of one HVTx or WTxA in the cabinet when low

power supply unit (VSxx) and low power fan (VMFA) are used.

Note 7.

BSC parameters are set to default values unless otherwise stated.

Note 8.

It should be made a testing practice to use the help provided in BTS Manager

from the Help Menu or by using help button (F1).

1.2 Hardware requirements

Base stations Single MetroSite cabinet.

Other Network Elements

• BSC S12

• Core Network with GPRS and EDGE capabilities





About this document

Mobile stations Feature Specific options

Speech channels FR, HR, EFRSingle 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

• Terminal Emulator

1.3 Software requirements

• SiteWizard 5.0

• BTS SW and BTS Manager software on which the Pronto were raised.

• CXM5 containing the feature under test.

• CXM5 release of BTS Manager and HW Configurator.

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



7 (18)




• GSM Protocol Analyser





Test cases

2 Test cases 2.1 PR 4029C02: RSSI values and alarm are reported

before the antenna supervision timer expires

This problem was corrected by the implementation of Change Request CR105.

More information for testing this Pronto is available in chapter “CRQ105 -

Output Raw RSSI Results to MMI [BSS20694]” of Test Specification for

Customer Change Requests in BTS SW Release CXM5 [Reference 2].

2.2 PR 3709C02: No calls on sector after BCCH

reconfiguration into GSM TRX

The purpose of this test case is to check that speech calls and GPRS transfer are

working and MS signal does not fluctuate after BCCH reconfiguration from

EDGE TRX to GSM TRX.

Note 9.

The fault correction also relates to the following Pronto:

• PR 27439ES09P: Problem in GPRS transfer and speech call after BCCHreconfiguration in MetroSite for GSM hardware.

Note 10.In case of 4 OMNI(EDGE/GSM) configuration, the first two TRXs are EDGE-

capable and the next two are GSM TRXs.



9 (18)




Input to Reproduce the Problem Expected Output

Configure the site as described in this test case.BTS SW Used: CXM4.1 CD3.0

BCCH is on TRX2, which is the preferred BCCH TRX.

PBCCH is configured and GPRS is enabled forthe sector.

The site is in supervisory state. No unexpectedalarms are observed on BTS Manager and theBSC.

Establish a speech call in the sector. The speech call is established successfully.

The Block command is given for TRX2 from BTSManager.

The alarm 7208 LOCAL BLOCK is sent to theBSC and BTS Manager.

Intra-cell handover takes place, and calls are

handed over from the blocked TRX.

BCCH is reconfigured to TRX3.

Disconnect the call. The call is disconnected.

Establish speech calls and perform GPRS datatransfer in the sector.

Mobile signal fluctuates, and no speech calls andGPRS data transfer are possible.

Switch Off/On the mobile. The mobile is latched on the sector and signalfluctuation does not occur.

Establish a speech call in the sector. After the call is matured, BCCH TRX goes intoBL-DGN state for around 10 seconds, and theBCCH TRX stops transmitting for that period.

BCCH TRX then returns to supervisory state.

Case Ref. Configuration

3709C02.01 4 OMNI (EDGE/GSM)

Input to Verify the Correction Expected Output

Configure the site as described in this test case.

BCCH is on TRX2, which is the preferred BCCH TRX.

PBCCH is configured and GPRS is enabled forthe sector.


Establish a speech call in the sector. The speech call is established successfully.

The Block command is given for TRX2 from BTSManager.

The alarm 7208 LOCAL BLOCK is sent to theBSC and BTS Manager.

Intra-cell handover takes place and calls arehanded over from the blocked TRX.

BCCH is reconfigured to TRX3.





Test cases


Disconnect the calls. The calls are disconnected.

Establish speech calls and perform GPRS datatransfer in the sector. Mobile signal does not fluctuate, and speech callsand GPRS data transfer are possible.

Switch Off/On the mobile. The mobile is latched on the sector and signalfluctuation does not occur.

Establish speech calls and GPRS data transfer inthe sector.

Speech calls and GPRS data transfer areperformed successfully.

The Unblock command is given for TRX2 fromBTS Manager.

The alarm 7208 LOCAL BLOCK is cancelled atthe BSC and BTS Manager.

BCCH is reconfigured back to TRX2.

Both TRX2 and TRX3 return to supervisory state.

Establish a speech call and GPRS data transferin the sector.

The speech call and GPRS data transfer areperformed successfully.

Repeat the test case without configuring PBCCH


3709C02.02 4 OMNI (EDGE/GSM)-MetroSite

2.3 PR 1-200449991: MetroSite BTS enters sleepingmode in high traffic conditions

The correction was verified with a customer-specific CD, in a customer network

where the problem was seen. No specific test case was done to validate the

correction for this problem during the CXM5 release testing. The issue was not

seen during the release testing and piloting of CXM5.

2.4 PR 1-62223179, 1-77993775: Bad FER Call Timepercentage for the AMR ful l rate is higher than for

the EFR

The purpose of this test case is to check that bad FER is not reported during an

AMR speech call.



11 (18)




Note 11.

The correction is covered with the following Prontos in this section:

•

PR 3562C02• PR 3560C02

• PR3611C02

• PR 13589ES10P

PR 3562C02: Slow link adaptation does not work in some scenario for AMR calls

The purpose of this test case is to check that an AMR codec does not change

more than once within a SACCH multi-frame with slow link adaptation.

Note 12.

Slow LA can be changed at the BSC using the MML command ZEEM. If Fast

LA is in use, the codec mode change is allowed in every second TCH frame (~

40 ms). With Slow LA, the codec mode changes are allowed on the SACCH

frame interval (480 ms). (CMI and CMR values are seen on the Abis).

Note 13.

The number of AMR codecs should be more than 2 and start the call with the

most robust one.


Configure the site as described in the test case.

BTS SW Used: CX4.1 CD3.0.


Set the AMR (AFS/ AHS) MTC mobile withringtone “Nokia Tune” and profile other than“silent”.

Make an AMR speech call. After getting the Alerting message in AMR MTCmobile, all the multi-frames are with 24 FER until

a CONNECT message is received. In the multi-frame in which the CONNECT message comesAMR codec changes unexpectedly from thelowest to the highest codec in a single multi-frame. This violates the condition for Slow LA.


3562C02.01 4 OMNI





Test cases


Configure the site as described in the test case. The site is in supervisory state. No unexpectedalarms are observed on BTS Manager and the

BSC.

Set the AMR (AFS/ AHS) MTC mobile withringtone “Nokia Tune” and profile other than“silent”.

Make an AFS call. In the multi-frame in which a CONNECT messagecomes, the AMR codec changes only in a singlestep. Also, in multi-frames before and after theCONNECT message, the codec does not changemore than once in a multi-frame. This actioncould be verified with AMR UL CODEC FIRSTand LAST sent to the Abis.

Repeat the test case with AHS call.


3562C02.02 4 OMNI EDGE with BB2F and BB2E

3562C02.03 4 OMNI GSM

PR 3560C02: Bad rx_quality and rx_level are observed in firstmeasurement report of call establishment

The purpose of this test case is to check that the first measurement report (report0) does not have bad rx_qual and rx_level in ideal conditions.

In the verification of the correction test cases, there may be some timing

difference (delay of 1 or 2 SACCH block period) between the Channel

Activation message and First Measurement report message.





Make speech calls with TFR, THR, EFR andAMR codecs.

Verify using GPA that some of the report 0 isshowing bad rx_qual and rx_level, while otherreports are showing good values for theseparameters.


3560C02.01 4 OMNI



13 (18)





Configure the site as described in the test case. The site is in supervisory state. No unexpectedalarms are observed on BTS Manager and the

BSC.

Make speech calls with TFR, THR, EFR and AMRcodecs.

Verify using GPA that the report 0 is not showingbad rx_qual and rx_level, if other reports areshowing good values. This means that for thegood channel condition report 0 is also showing agood measurement report.


3560C02.02 4 OMNI EDGE

3560C02.03 4 OMNI GSM

PR 3611C02: Bad FACCH can be decoded instead of NO_DATA or BadSpeech in AMR HR calls in BB2F

The purpose of this test case is to check that FACCH is correctly detected in

BB2F/E CHDSP SW.

Note 14.

Uplink DTX is disabled from the BSC.

Note 15.

Enable only one codec for AFS and one for AHS on BTS.





Set the AMR FR/HR codec at the mobile.Establish the call. Take the signalling and TRAUtraces of GPA.

Using the signalling message traces, verify thatthe FER of the measurement report in which theALERT and CONNECT messages come, is >=1.(There should be no interference and the RXquality should be zero for the abovemeasurement report.)

From the TRAU traces, verify that there should beall good speech frames in the multi-frame, inwhich ALERT or CONNECT message comes(besides the two NO_DATA, in which one block isDSP_BLOCK_NOT_READY and another isFACCH block).






Test cases


3611C02.01 4 OMNI EDGE


Configure the site as described in the test case. The site is in supervisory state. No unexpectedalarms are observed on BTS Manager and theBSC.

Set the AMR FR/HR codec at the mobile. Makean AFS Call. Take the signalling and TRAUtraces of GPA.

Using the signalling message traces, verify thatthe FER of the measurement report in whichALERT and CONNECT messages comes is =0.(There should be no interference and the RXquality should be zero for the abovemeasurement report.)

From the TRAU traces, verify that there should beall good speech frames in the multi-frame inwhich ALERT or CONNECT message comes(besides the two NO_DATA, in which one block isDSP_BLOCK_NOT_READY and another isFACCH block).

Repeat the test case with an AHS call.


3611C02.02 4 OMNI TSxB with BB2F

3611C02.03 4 OMNI TSxA with BB2E

PR 13589ES10P: In a Mobile terminated call, some mobi le phone types in AMR mode cause High FER values in BTS UL Measurement Repor tsduring Alerting-Connect Phase

The purpose of this test case is to check that no FER with value 24 is reported at

Rx qualities (0 to 3 ).

Note 16.

Uplink DTX is disabled from the BSC.



BTS SW Used: CX4.1.




15 (18)





Set the AMR (AFS/ AHS) MTC mobile withringtone “Nokia Tune” and a profile other than

“silent”.

Make an AMR speech call. After getting the Alerting message in the AMRMTC mobile, all the multi-frames are with 24 FERuntil the CONNECT message is received.


13589ES10P.01 4 OMNI EDGE


Configure the site as described in the test case. The site is in supervisory state. No unexpected

alarms are observed on BTS Manager and theBSC.

Set the AMR (AFS/ AHS) MTC mobile withringtone “Nokia Tune” and a profile other than“silent”.

Make AFS and AHS calls. Adjust the ULInterference level with signal generator so that RxQuality range is 0 and 1 only.

Between the ALERTING and CONNECTmessages for the AMR MTC mobile, there shouldbe no multi-frame with 24 FER till CONNECTmessage received, if rx_qual_full is 0.

The FER value should be 0 for the SACCH mf’swith rx_qual_full 0 and 1.

Increase the UL Interference with a signalgenerator so that Rx Qual is 2 or 3.

The FER value should be predominantly 0 forSACCH mf’s with rx_qual_full 2 and 3.

There could be cases where very few blocks failBER Threshold or 1 to 3 blocks fail CRC checkingat the BTS or combination of both, but thepercentage of non-zero FER should be muchless.

Increase the UL Interference with a signalgenerator so that Rx Qual is above 3.

The FER value should be 24 for most of theSACCH mf’s for rx_qual_full 4 to 7.


13589ES10P.02 4 OMNI EDGE13589ES10P.03 4 OMNI GSM





Test cases



17 (18)




References

1. Generic Failure Report for Nokia MetroSite EDGE Base Station,

DN00255445, issue 30-0.

2. Test Specification for Customer Change Requests in BTS SW ReleaseCXM5, DN0698004, issue 1-0.



Customer Corrections DN0691186x1x0xen

Documents

Transcript of Customer Corrections DN0691186x1x0xen