trace window for dropped calls nsn

Activating and Testing BSS8121:Trace Window for Dropped Calls

dn992307Issue 5-0 en

# Nokia CorporationNokia Proprietary and Confidential

1 (15)

2003353Nokia BSC/TCSM S11.5 ProductDocumentation

The information in this documentation is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia's customers only for the purposes of the agreement under which the documentationis submitted, and no part of it may be reproduced or transmitted in any form or means without theprior written permission of Nokia. The documentation has been prepared to be used byprofessional and properly trained personnel, and the customer assumes full responsibility whenusing it. Nokia welcomes customer comments as part of the process of continuous developmentand improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products cannot be considered binding butshall be defined in the agreement made between Nokia and the customer. However, Nokia hasmade all reasonable efforts to ensure that the instructions contained in the documentation areadequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the documentation.

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

This documentation and the product it describes are considered protected by copyrightaccording to the applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

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

Copyright © Nokia Corporation 2005. All rights reserved.

2 (15) # Nokia CorporationNokia Proprietary and Confidential


Activating and Testing BSS8121: Trace Window for Dropped Calls

Contents

Contents 3

List of tables 4

List of figures 5

Summary of changes 7

1 Trace Window for Dropped Calls 9

2 Activating and testing Trace Window for Dropped Calls 112.1 Activating Trace Window for Dropped Calls 112.2 Testing Trace Window for Dropped Calls 12

3 Deactivating and testing Trace Window for Dropped Calls 15



3 (15)

Contents

List of tables




List of figures



5 (15)

List of figures

Summary of changes

Summary of changes

Changes between document issues are cumulative. Therefore, the latest documentissue contains all changes made to previous issues.

Changes made between issues 5 and 4

The document has been revised throughout to comply with the latestdocumentation standards. No changes have been made due to changes insoftware.

The document name has been changed from BSS8121: Trace Window forDropped Calls to Activating and Testing BSS8121: Trace Window for DroppedCalls .


The document has been revised throughout to comply with the latestdocumentation standards. No changes have been made in the document due tonew features.


Chapter Activating and testing BSS8121: Trace Window for Dropped Calls,section Installation and activation

Command ZWOF:10-51:1; changed to ZWOC:10,51,FF;

Command ZWOO; changed to ZWOI:10,51;

Chapter Activating and testing BSS8121: Trace Window for Dropped Calls,section Testing, sub-section Test execution and expected results

Command ZTPM:OBSERV,DC_OBS:<measurement day>,<measurementinterval>, <output interval>:BTS=BTS_ID>:; changed to ZTPM:OBSERV,DC_OBS:<measurement day>,<measurement interval>, <output interval>:BTS=<BTS_ID>,TRX=<TRX_ID>:;

Deactivating and testing BSS8121: Trace Window for Dropped Calls

Command ZWOF:10-51:0; changed to ZWOC:10,51,0;

Command ZWOO; changed to ZWOI:10,51;

The document has been revised throughout to comply with the latestdocumentation standards.



7 (15)

Summary of changes

1 Trace Window for Dropped Calls

Trace Window for Dropped Calls provides you with detailed information on thelast seconds of a call after the call has been dropped unexpectedly, providing youwith reasons for possible problems. The software is implemented as anobservation type Dropped Call Observation (DC_OBS).

This observation collects some key parameters of the call, for example:

. MS Power,

. BS Power,

. RX Level and Quality of the BS measured by the MS,

. RX Level of the neighbouring cells measured by the MS,

. RX Level and Quality of the MS measured by the BS,

. MS Speed,

. MS's distance (Timing Advance) from the BS, and

. Handover causes.

The scope of the Trace Window for Dropped Calls is by default one BTS, that is,all the TRXs and TSLs within. But the Trace Window for Dropped Calls can alsobe focused on a single TRX. With MMI, you can define the BTS to be observedand when the observation starts and stops. A set of counter values ofapproximately the last 10 - 16 seconds is stored continuously while the call isgoing on. The collected data is discarded when the call is released, but if the callis interrupted abnormally, the data is stored. This dropped calls window tracing isfocused on channels, but each dropped call is stored as a separate case.

The radio measurement data is collected and forwarded after 32 radiomeasurement reports, 480 ms each, resulting in a minimum interval ofapproximately 16 seconds between messages to the BSC. The handoverobservation data is forwarded when a handover has occurred, and the channelrelease is reported when it has happened. The traffic channel observation report isused for identifying a dropped call. The BSC stores the values with a time stamp.



9 (15)

Trace Window for Dropped Calls

The benefit of Trace Window for Dropped Calls is that you can find informationon real reasons for SDCCH and TCH problems and detect the BTS with lowerquality.

Trace Window for Dropped Calls is an application software in the BSC.

There are no hardware or firmware effects, and no alarms are involved with TraceWindow for Dropped Calls.

Related file descriptions:

BSC Measurement Parameter File

The BSC adds the parameters which are specific to the measurement definition ofthe dropped call observation to the BSC Measurement Parameter File .

Dropped Call Observation is a GSM measurement type controlled by the GSMMeasurement Handling MML . Dropped Call Observation is added to the NokiaNetAct - BSC Q3 interface.

These activation instructions are for BSC S8 level or later.

For more information on the software, see 24 Dropped Call Observation.

For activation instructions, see Activating and testing Trace Window for DroppedCalls.

For deactivation instructions, see Deactivating and testing Trace Window forDropped Calls.




2 Activating and testing Trace Window forDropped Calls

Trace Window for Dropped Calls is carried out in the BSC.

For a description of the software, see Trace Window for Dropped Calls.

For deactivation instructions, see Deactivating and testing Trace Window forDropped Calls.

Before you start

The following equipment is needed for activating and testing:

. MSC

. Nokia NetAct (version OSS3.1 or later)

. BSC (version S8 or later)

. Several BTSs

. Two MSs

. An MMI terminal

2.1 Activating Trace Window for Dropped Calls

The dropped call observation can be started from the Nokia NetAct or from theBSC with an MML command. See GSM Measurement Handling , (TP ).

Trace Window for Dropped Calls is in use directly after the software upgrade.

Note

The dropped call observation can be activated only in one BTS per BSC at a time.



11 (15)

Activating and testing Trace Window for Dropped Calls

This parameter is handled via the Parameter Handling MML . After the softwareupdate, this parameter is in the OFF state.

Steps

1. Set the DC_OBSERVATION_USAGE parameter on (WOC).

ZWOC:10,51,FF;

2. Check the software activation (WOI).

ZWOI:10,51;

2.2 Testing Trace Window for Dropped Calls

Steps

1. Activate the dropped call observation (TPM).

ZTPM:OBSERV,DC_OBS:<measurement day>,<measurementinterval>,<output interval>:BTS=<BTS_ID>,TRX=<TRX_ID>:;

Example 1.

ZTPM:OBSERV,DC_OBS:ALL,00-00-24-00,15:BTS=8;

2. Start the observation (TPS).

ZTPS:OBSERV,DC_OBS:<start date>,<stop date>:;

3. Check that the observation is ENABLED (TPI).

ZTPI:OBSERV,DC_OBS:;

Expected outcome

The administrative state is now UNLOCKED and the operational state isENABLED.

4. Make a call.

Make a call using the MSs and the BTS which is observed. After a while,cause a call drop, for example by removing the battery of the MS.




5. Stop the observation (TPE).

ZTPE:OBSERV,DC_OBS:;

Expected outcome

The administrative state is now LOCKED and the operational state isDISABLED.

6. Wait for the next observation report.

Wait for the next observation report to be written within the next 15minutes.

7. Check the contents of the observation file.

Check the last observation file in Nokia NetAct. Check that there is data inthe file and that it is correct.

Expected outcome

There is data in the file and it is correct.



13 (15)

Activating and testing Trace Window for Dropped Calls

3 Deactivating and testing Trace Windowfor Dropped Calls

For a description of the software, see Trace Window for Dropped Calls.

For activation instructions, see Activating and testing Trace Window for DroppedCalls.

Steps

1. Set off the DC_OBSERVATION_USAGE parameter (WOC).

ZWOC:10,51,0;

2. Check the software deactivation (WOI).

ZWOI:10,51;

3. Try to activate the dropped call observation (TPM).

ZTPM:OBSERV,DC_OBS:<measurement day>,<measurementinterval>,<output interval>:BTS=<BTS_ID>,TRX=<TRX_ID>:;

Expected outcome

The system does not allow the use of the observation.



15 (15)

Deactivating and testing Trace Window for Dropped Calls

trace window for dropped calls nsn

Devices & Hardware