lucent call trace.pdf

Lucent Technologies - ProprietaryThis document contains proprietary information of

Lucent Technologies and is not to be disclosed or used except inaccordance with applicable agreements

Copyright © 2003 Lucent TechnologiesUnpublished and Not for Publication

All Rights Reserved

Flexent®/AUTOPLEX®

Wireless NetworksRF Call TraceOptional Feature Description

Release 21.0

401-612-052Issue 17

August 2003

Lucent Technologies - ProprietarySee Notice on first page

Copyright © 2003 Lucent Technologies. All Rights Reserved.

This material is protected by the copyright and trade secret laws of the United States and other countries. It may not be reproduced, distributed, or altered inany fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts, or licensing, withoutthe express written consent of Lucent Technologies and the business management owner of the material.

Notice

Every effort was made to ensure that this document was complete and accurate at the time of printing. However, information is subject to change.

Mandatory Customer Information

This document does not contain any mandatory customer information.

Interference information: Part 15 of FCC rules

NOTE: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits aredesigned to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipmentgenerates, uses, and can radiate radio frequency energy, and if not installed and used in accordance with the documentation, may cause harmful interference toradio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correctthe interference at his/her own expense.

Security statement

In rare instances, unauthorized individuals make connections to the telecommunications network through the use of remote access features. In such event,applicable tariffs require the customer to pay all network charges for traffic. Lucent Technologies cannot be responsible for such charges and will not makeany allowance or give any credit for charges that result from unauthorized access.

Trademarks

AUTOPLEX is a registered trademark of Lucent Technologies.Flexent is a registered trademark of Lucent Technologies.UNIX is a registered trademark of The Open Group in the United States and other countries.WatchMark Prospect for Lucent is a trademark of WatchMark Corporation.

Ordering information

The ordering number for this document is 401-612-052. To order this or other Lucent Technologies information products, see “To obtain documentation,training, and technical support or submit feedback” on the 401-010-001 Flexent®/AUTOPLEX® Wireless Networks System Documentation CD-ROM or thedocumentation web site at https://wireless.support.lucent.com/amps/rls_info/rls_doc/cd_docs/.

Technical support

For technical support, see “To obtain documentation, training, and technical support or submit feedback” on the 401-010-001 Flexent®/AUTOPLEX® WirelessNetworks System Documentation CD-ROM or documentation web site at https://wireless.support.lucent.com/amps/rls_info/rls_doc/cd_docs/.

https://wireless.support.lucent.com/amps/rls_info/rls_doc/cd_docs/

https://wireless.support.lucent.com/amps/rls_info/rls_doc/cd_docs/

Contents 401-612-052, Issue 17

August 2003 Lucent Technologies — Proprietary Page iiiSee notice on first page

Contents Page

1. Introduction 1

Reason for Reissue 1

Historical Record of Revisions 1

Intended Audience 1

2. Availability 2

Supported Technologies 3

HLR Configurations 3

Software Requirements 3

Hardware Requirements 3

3. Benefits 4

RFCT CCU Changes to Support 3G-IX HSPD 4

Improved RF Call Trace for 3G-1X HSPD 5

Enhanced RF Call Trace for 3G-1X Calls 5

4. Feature Description 5

RF Call Trace Data Collection 6

AMPS Mode 6

MSC OA&M Support for 384 Cells 7

TDMA Mode 8

Increased TDMA MAHO List Feature 8

RF Call Trace for Dual-Mode Mobiles (DMRFCT) 9

CDMA Mode 9

Markov RF Call Trace 14

Enhanced RF Call Trace/Markov - Phase 1 14

Enhanced RF Call Trace/Markov - Phase 2 16

Calculating Frame Error Rates 18

CDMA RF Call Trace (CDMARFCT) 1919

18

16

14

14

9

9

8

8

7

6

6

5

5

5

4

4

3

3

3

3

2

1

1

1

1

Contents Page


Page iv Lucent Technologies — Proprietary August 2003See notice on first page

CDMA Multiple Directory Number (DN) RF Call Trace (CDMA MDNRFCT) 20

CDMA Adding and Deleting DN(s) During a RF Call Trace 20

CDMA Enhancement Adding and Deleting DN(s) During a RF Call Trace Session 21

UNIX® System Commands 22

FTrftrace Command 22

FTrfstop Command 23

FTrfdump Command 23

FTrfclear Command 23

15 Digit DN Feature—Impact on RF Call Trace 23

Basic RF Call Trace for 3G-1X High Speed Packet Data (HSPD) 24

Stop Indicator 24


Feature Description for Enhanced RF Call Trace for 3G-1X Calls 25

Overload Conditions 27

Major RFCT Metrics Summary 28

5. Feature Interactions 29

6. Special Considerations 29

Subscriber Perspective 30

Service Provider Perspective 30

7. Caveats 30

CDMA IMSI 30

RFCT for Dual Mode 31

Multiple DN RFCTB 31

Basic RFCT for 3G-1X HSPD 31

8. Feature Implementation 32

Basic RF Call Trace for 3G-1X High Speed Packet Data (HSPD) 32


Enhanced RF Call Trace for 3G-1X Calls 3333

32

32

32

31

31

31

30

30

30

30

29

29

28

27

25

25

24

24

23

23

23

23

22

22

21

20

20


August 2003 Lucent Technologies — Proprietary Page vSee notice on first page

Contents Page

9. Supplemental Information 34

Abbreviations 34

References 36

10. History of Revisions 37

Issue 16 37

Issue 15 37

Issue 14 37

Issue 13 38

Issue 12 38

Issue 11 38

Issue 10 38

Issue 9 38

11. Appendix A - FTrftrace(1) 39

Name 39

Synopsis 39

Description 39

Options 40

Examples 42

Files 42

User Environment 42

11. Appendix B - FTrfstop(1) 43

Name 43

Synopsis 43

Description 43

Options 43

Examples 44

User Environment 44

11. Appendix C - FTrfclear(1) 4545

44

44

43

43

43

43

43

42

42

42

40

39

39

39

39

38

38

38

38

38

37

37

37

37

36

34

34

Contents Page


Page vi Lucent Technologies — Proprietary August 2003See notice on first page

Name 45

Synopsis 45

Description 45

Options 45

Examples 45

Files 46

User Environment 46

11. Appendix D - FTrfdump(1) 47

Name 47

Synopsis 47

Description 47

Options 47

Examples 62

Files 62

User Environment 6262

62

62

47

47

47

47

47

46

46

45

45

45

45

45

Figure Page

401-612-052, Issue 17

August 2003 Lucent Technologies — Proprietary Page viiSee notice on first page

A. MDN RFCT Bandwidth formula 2121

Figure Page

401-612-052, Issue 17

Page viii Lucent Technologies — Proprietary August 2003See notice on first page

Table Page

401-612-052, Issue 17

August 2003 Lucent Technologies — Proprietary Page ixSee notice on first page

1. RF Call Trace Availability 22. Mobile Forward Traffic Frame Count Definitions - Voice 113. Mobile Retrievable Parameters for Reverse Traffic Channels 124. Mobile Reverse Traffic Frame Count Definitions - Markov 155. Primary Cell Mapping for Mobile Received Markov Statistics on the Forward Link 156. Mobile Reverse Traffic Frame Count Definitions - Markov 177. Mobile Forward Traffic Frame Count Definitions - Markov 178. Minimum Equivalent Polling Interval 209. 2G/3G Voice RFCT Capabilities Across Different Software Releases 2810. 3G-1X HSPD RFCT Capabilities 2828

28201717151512112

Table Page

401-612-052, Issue 17

Page x Lucent Technologies — Proprietary August 2003See notice on first page

Introduction 401-612-052, Issue 17

August 2003 Lucent Technologies — Proprietary Page 1See notice on first page

1. Introduction

This document describes the Radio Frequency (RF) Call Trace optional feature ofFlexent®/AUTOPLEX® wireless networks. This document provides the followinginformation:

■ Availability and special system requirements

■ Feature capabilities and interactions with other Flexent®/AUTOPLEX® features

■ Information about how this feature affects other system interfaces (for example,Recent Change/Verify (RC/V) forms and Automatic Message Accounting (AMA)records)

■ Feature implementation procedures

Reason for Reissue

Issue 17 of this document provides the following changes/additions:

■ adds feature information for the Enhanced RF Call Trace for 3G-1X Calls feature(Feature Identifier 2137.5):

— “Availability” on page 2

— “Supported Technologies” on page 3

— “Enhanced RF Call Trace for 3G-1X Calls” on page 5

— “Feature Description for Enhanced RF Call Trace for 3G-1X Calls” onpage 25

— “Feature Interactions” on page 29

■ adds feature information for the AUTOPLEX Series II Traffic Overload Control(Part 1) feature (Feature Identifier 5042.6):

— “RF Call Trace Data Collection” on page 6

Historical Record of Revisions

For a list of previous revisions of this document, see “History of Revisions” on page 37.

Intended Audience

This document is intended for engineers, technicians, and administrators whoimplement or maintain the RF Call Trace feature for the Flexent®/AUTOPLEX® wirelessnetworks.

Availability 401-612-052, Issue 17

Page 2 Lucent Technologies — Proprietary August 2003See notice on first page

2. Availability

Refer to the following table for availability:

Table 1. RF Call Trace Availability

Feature ECP Release Notes

RF Call Trace 4.1 (or later) and Series II CellRelease

RF Call Trace for theAMPS/TDMADual-Mode Mobiles

6.1 (or later) and Series II CellRelease 5.1 (or later)

The default signal strengthmeasurements of a TDMAmobile are in IS-54B units. Theoption of using dBm issupported.

RF Call Trace for theAMPS/CDMADual-Mode Mobiles

7.0 (or later) and Series II CellRelease 6.0 (or later)

Enhanced RF CallTrace/Markov - Phase 2

10.0/CDMA Release 5.0(or later)

CDMA Multiple DN 11.0/CDMA Release 6.0 andSeries II Cell CDMA Release11.0 (or later)

Migration from the ECPto the OMP

11.0/CDMA Release 6.0 (orlater)

CDMA Adding andDeleting DN(s) during aRF Call Trace sessionenhancement

5.0/CDMA Release 15.0 andSeries II Cell CDMA Release13.0 (or later)

15 Digit DN 16.0

Increased TDMAMAHO List

16.1

MSC OA&M Support for384 Cells

17.0 (or later)

Basic RF Call Trace for3G-1X HSPD

18.0 (or later) This feature is for 3G data that issupplemental in R18.0. Thisfeature is an enhancement of theexisting 2G Radio Frequency CallTrace (RFCT) [FeatureIdentification (FID) # 2137.10].

Availability 401-612-052, Issue 17


Supported Technologies

The RF Call Trace feature is supported in the following air-interface technologies:

■ analog

■ CDMA cellular

■ CDMA PCS

■ TDMA cellular

■ TDMA PCS

HLR Configurations

The RF Call Trace feature is independent of the Home Location Register (HLR)configuration.

Software Requirements

For Basic RF Call Trace for 3G-1X High Speed Packet Data (HSPD), ECP Release 18.0(or later) must be installed.

For Improved RF Call Trace for 3G-1X High Speed Packet Data (HSPD), ECP Release20.0 (or later) must be installed.

For Enhanced RF Call Trace for 3G-1X Calls, ECP Release 21.0 (or later) must beinstalled.

Hardware Requirements

There are no specific hardware requirements for the RF Call Trace features.

Improved RF Call for3G-1X HSPD

20.0 (or later) The Improved RF Call for 3G-1XHSPD feature (FID #2137.4)provides additional 3G-1X HSPDRF Call Trace relative to BasicRF Call Trace for 3G-1X HSPD(FID #2137.3).

Enhanced RF CallTrace for 3G-1X Calls

21.0 (or later)

Table 1. RF Call Trace Availability (Continued)

Feature ECP Release Notes

Benefits 401-612-052, Issue 17


3. Benefits

When a mobile is operating in the AMPS mode, the RF Call Trace feature allows asystem operator to make periodic signal strength measurements on up to ten DirectoryNumbers (DNs) in a given cluster of up to eight cell sites or the neighbor-1 neighbors ofthe serving cell.

NOTE:Only mobiles that are on a CDMA cell release cell (APXDx.xx) can trace multiple DN’son their AMPS calls.

When a mobile is operating in TDMA mode, the periodic measurements on a specifiedsingle DN are made by the mobile of the Mobile Assisted Handoff (MAHO) neighbors ofthe serving face.

For CDMA mode, mobiles report signal strength of pilots in the active set and candidatelist. The maximum number of active members is six, and the maximum number ofcandidate members is five. However, the initial release of CDMA limits the active set tothree.

For all call modes, AMPS, TDMA, or CDMA, the operator can also specify the periodicmeasurement interval and the duration of the call trace for signal strengthmeasurements.

For AMPS and CDMA modes, the CDMA Multiple DN feature allows up to ten DNs tobe traced during a single session.

NOTE:Only mobiles that are on a CDMA cell release cell (APXDx.xx) can trace multiple DN’s.

Users of the CDMA Adding and Deleting DN’s during a RF Call Trace enhancement canadd and delete DN(s) from a RF Call Trace session without having to interrupt thesession.

NOTE:Only mobiles that are on a CDMA cell release cell can trace multiple DN’s.

RFCT CCU Changes to Support 3G-IX HSPD

The RFCT CCU Changes to Support 3G-1X HSPD feature enables the service providerto collect and view 3G Radio Frequency (RF) measurements for voice and data calls.Power measurements include the average forward transmit power on the fundamentalchannel (Ectf) and the forward transmit power on the supplemental channel (Ects).

Feature Description 401-612-052, Issue 17


Improved RF Call Trace for 3G-1X HSPD

The Improved RF Call Trace for 3G-1X HSPD feature provides the service provider andRadio Frequency (RF) performance engineers with measurements to optimize voiceand data calls. New power measurements include the sector transmit power (Ior)referenced to the pilot power for the forward direction and the Fundamental andSupplemental bit energy (EbNo) for the reverse direction. Newly provided frame countsare the forward and After Frame Selection (AFS) reverse supplemental channel nullframes (DTX frames), and the mobile reported supplemental channel frames andLogical Transmission Unit (LTU) packet statistics.

In addition, previously disabled mobile-reported data for pilot strengths and mobileframe counts for voice calls are now being enabled.

Enhanced RF Call Trace for 3G-1X Calls

The Enhanced RF Call Trace for 3G-1X Calls feature provides the service provider andRF performance engineers measurements to optimize voice and data calls. New framecounts include the forward supplemental channel null frames (DTX frames) used in theEcts calculation for the interval for each burst rate when the Forward SupplementalChannel (F-SCH) is in softer hand-off, and the number of DTX F-SCH frames for eachburst rate when the F-SCH is in softer hand-off.

4. Feature Description

The Radio Frequency (RF) Call Trace (RFCT) optional feature provides the systemoperator with a tool that traces a mobile call from an RF perspective for the analog(AMPS) call mode. This tool records signal strength information for a mobile asmeasured on all antenna faces of the cell sites included in a study. The data collected iscorrelated with the measurements recorded at the mobile unit by means of the SystemAccess Monitor (SAM) recorder.

System operators can use these tools to analyze the mobile RF environment andfine-tune system parameters relating to handoffs and interference. An RF Call Tracestudy can be executed while a mobile is driving through the system.

The following features affect certain RF Call Trace users:

■ “AMPS Mode” on page 6

■ “CDMA RF Call Trace (CDMARFCT)” on page 19

■ “CDMA Multiple Directory Number (DN) RF Call Trace (CDMA MDNRFCT)” onpage 20

■ “CDMA Adding and Deleting DN(s) During a RF Call Trace” on page 20

■ “Basic RF Call Trace for 3G-1X High Speed Packet Data (HSPD)” on page 24



■ “Improved RF Call Trace for 3G-1X HSPD” on page 25

■ “Feature Description for Enhanced RF Call Trace for 3G-1X Calls” on page 25

The following changes affect all RF Call Trace users:

■ new FTrfdump real-time output option

■ FTrftrace command option changes for CDMA MDNRFCT users

■ RF Call Trace data collection blocked or inhibited under certain overloadconditions (Release 21.0 and later releases)

RF Call Trace Data Collection

When a secondary CDMA Cluster Controller (CCC) receives a request from theprimary CCC to collect data for RF Call Trace, the secondary CCC checks its own CCCOverload Status. If the CCC is in overload, the request is discarded. Similarly, if aRadio Cluster Controller (RCC), Time Division Multiplex (TDM) Bus Control Channel, orprimary CCC are in overload, RF Call Trace collecting, storing, and reporting of data isnot performed.

NOTE:Overload control is applied to both FID 5042.6, AUTOPLEX Series II Traffic OverloadControl (Part 1) and FID 5042.7, FLEXENT Traffic Overload Control (Part 1).

For details on how the Flexent®/AUTOPLEX® system handles overload conditions, see401-610-009, System Capacity Monitoring and Engineering Guidelines.

AMPS Mode

When the RFCT feature is active, the Mobile Switching Center (MSC) periodicallysends an “RF Call Trace Location Request” message—specifying the voice channelserving the mobile—to the cell sites. These cells are typically the serving cell and itsneighbors.

Upon receipt of an “RF Call Trace Location Request” message, the cell tunes its locateradio to the specified voice channel, measures the signal quality, and detectsSupervisory Audio Tone (SAT) on each of its equipped faces. Rather than applying thenormal signal strength adjustment rules, the cell adjusts each location measurementonly by the per-cell frame gain differential.

The cell applies the normal SAT detect rules. That is, if no SAT, wrong SAT, or multipleSATs are detected on a face, the adjusted measurement for that face is set to zero.Also, other than one of the specified cells, no measurement is returned if the specifiedDN is active on a call.

The cell then returns the “Location Reply” message, containing the adjusted signalstrength measurements, to the requesting process in the MSC. The MSC logs the



replies for later processing. If the call is in the process of handoff at the time ofmeasurement, this information is also stored in the log file for later processing.

Prior to Series II Cell Release 4.3, the RF Call Trace feature provided the raw signalstrengths of the mobile that were measured at the specified cell site. However, the cellsite did not provide the Stored Dynamic Mobile Attenuation Code (SDMAC) in effect atthe time of measurement.

For Series II Cell Release 4.3, the RF Call Trace feature provides the SDMAC, which isaccessed from the serving cell whenever RF Call Trace signal strength measurementsare requested by the OMP. This parameter permits adjustment of the signal strengthdata for analysis. This data can be used to optimize the following system settings:

■ Neighbor list

■ Values for primary Voice Mobile Attenuation Code (VMAC)

■ Mobile Dynamic Power Control (DPC) target level

The RF Call Trace feature has been enhanced to provide the mobile signal strength asmeasured by the serving Radio Channel Unit (RCU). In addition, with the CDMAMultiple DN feature, up to ten DNs can be traced during a single session.

As an aid to analysis, for the case where Neighbor-1 neighbors were used, the RF CallTrace feature now provides an abbreviated Neighbor-1 neighbor list with the followinginformation supplied for each local neighbor (field identifiers are the same as thosedefined in 401-610-036, Database Update Manual, for the Neighbor-1 neighbor list onthe fci form):

■ Cell Site

■ Antenna Faces

■ Srv Grp

■ Sub Grp

■ MFA

■ HO Bias

MSC OA&M Support for 384 Cells

The MSC OA&M Support for 384 Cells feature gives the capability to connect up to 384cells to a single MSC. This feature expands the current cell limit of 222 for the Flexent®/AUTOPLEX® wireless networks to 384.

For more information, refer to 401-612-422, MSC OA&M Support for 384 Cells feature.



TDMA Mode

When the RFTC feature is active, the MSC periodically sends an “RF Call TraceLocation Request” message that specifies the voice channel and time slot serving themobile to the serving cell.

The RF Call Trace feature uses readily available data at the radio. Therefore, regardlessof whether the serving cell receives the “RF Call Trace Location Request” message, theserving cell sends a measurement order to the dual-mode mobile. This measurementorder causes the mobile to report measurements on up to 24 voice channels that werepreviously downloaded to the mobile from the MAHO list of the current serving face.The mobile also reports the measured Bit Error Rate (BER). The cell reports the signalstrength, the BER, and the Frame Error Rate (FER) as measured by the serving DRUor Enhanced Digital Radio Unit (EDRU).

As an aid to analysis, the RF Call Trace for Dual-Mode Mobiles feature provides anabbreviated MAHO list for each MAHO neighbor measured. The following informationis provided for each MAHO neighbor (field identifiers are the same as those defined in401-610-036, Database Update Manual, for the MAHO list on the fci form):

■ Cell Site

■ PAF

■ Cell CD

■ SG0 Bias

■ SG1 Bias

■ SG0 VMAC

■ SG1 VMAC

■ SG0 DTH

■ SG1 DTH

■ Extended System/Switch Identifier (ESID)1

Increased TDMA MAHO List Feature

For IS-136 (TDMA) and later revision mobiles, this feature increases the number ofneighbors that a TDMA sector can support from 12 to 24 (neighbors). The IncreasedTDMA MAHO List feature adds the following enhancements:

■ Enhances the capabilities of the RF Call Trace feature by allowing a mobilebeing served on an active TDMA traffic channel to handoff to as many as 24other sectors specified by the service provider.

1 The ESID consists of three parts: System Identifier, ECP Identifier, and DCS Identifier.



■ Enhances the ability of the Flexible Channel Allocation (FLCA) feature to obtaindownlink measurements to support selection of channels to serve calls whenless than 24 handoff neighbors are specified by the service provider.

These changes are supported by an increase in the maximum number of entries in theMeasurement Order/Hyperband Measurement Order (MO/HMO) message sent to IS-136 mobiles on active TDMA traffic channels. For each neighbor entry in the MO/HMOmessage, IS-136 mobiles on the TDMA traffic channel report the measured downlinkchannel quality to the cell site. These downlink measurements are used to supportMAHO and FLCA.

As a result of this feature supporting a maximum number of 24 entries in the MO/HMOmessage, the number of dropped calls is reduced and the quality of channels selectedby the FLCA algorithm for assignment to calls is improved.

For more information on this feature, refer to 401-612-311, Increased TDMA MAHOList.

RF Call Trace for Dual-Mode Mobiles (DMRFCT)

The RF Call Trace for Dual-Mode Mobiles (DMRFCT) feature (for AMPS/TDMA mode)allows the recording of signal strength information as measured by a dual-mode mobilein TDMA mode and its serving Digital Radio Unit (DRU). This data is used to assist inengineering and troubleshooting Flexent®/AUTOPLEX® cell sites. For example, thedata may be used to explore RF conditions in areas experiencing inconsistent handoffsand can assist in the selection of optimum neighbor lists.

CDMA Mode

Unlike the TDMA operation, CDMA mobiles report signal strength of pilots in the activeset and candidate list. The maximum number of active members is six, and themaximum number of candidate members is five. Pilot sets are defined as follows:

■ P—primary antenna face: The primary antenna face is the antenna face that isconsidered to be in control of the call. Service measurements that are related tothis call are incremented for the primary antenna face.

■ S1 – S5—secondary antenna faces: For CDMA calls that are in soft handoff,there may be one or five secondary antenna faces in the active set. Forward andreverse traffic is transported between the mobile and speech handlersimultaneously via the primary and all secondary antenna faces. The secondaryantenna faces are labeled S1 through S5 based on the order in which they wereadded to the call.

■ C—candidate antenna face: A candidate antenna face is an antenna face forwhich the mobile has measured a pilot strength that exceeds the T_ADDthreshold, but which has not been added to the call. The candidate antenna facemust be populated in the CDMA neighbor list (fci form) for either the primary orone of the secondary antenna faces.



■ R —remaining set pilot: A remaining set pilot is a pilot for which the mobile hasmeasured a pilot strength that exceeds the T_ADD threshold, but does notappear in the CDMA neighbor list of either the primary or one of the secondaryantenna faces. Since a remaining set pilot is not present in the database, thesystem is not able to determine the ECP, cell site, and antenna face associatedwith that pilot. Only the pilot Pseudo Noise (PN), pilot strength, and round tripdelay are printed for remaining set pilots.

Once the FTrftrace command is executed for a CDMA call, the Call ProcessingDatabase Node (CDN) sends a CDMA measurement request message to all cells thatare associated with the call. This message is a pilot strength measurement request andis sent to the primary cell and five secondary cells. Only the primary cell responds bysending a CDMA measurement response message that contains the measured pilotstrength to the OMP. The primary cell also responds with cell and mobile counts.

Feature activation is relevant to the call mode. A call may be initially assigned to theCDMA call mode and later assigned to the AMPS call mode (after a CDMA to AMPShandoff). If both RFCT and CDMARFCT are activated in the Feature Activation File(FAF), signal strength measurements are collected regardless of whether the call modeis CDMA or AMPS. When the CDMA MDNRFCT FAF is active, the capability to trace upto ten mobiles at one time per trace is provided.

For a mobile-originated call, an RF Call Trace begins when the call enters theconversation state. For a mobile-terminated call, an RF Call Trace begins as soon asthe call enters the Waiting for Answer state. The serving cell(s) associated with theCDMA mobile for the RF Call Trace receive a CDMA measurement request messagefrom the OMP per polling interval. The cell requests that the mobile report allmeasurements back to the cell. However, the OMP expects the report from only thePrimary cell. Some of the major information that is displayed as a result of an OMPrequest to the mobile/cell is listed as follows.

Refer to “Field explanations” in Appendix D under the heading “Options” on page 44,for a more complete list of field reporting information.

■ Serving cell site ID

■ Time stamp

■ Call trace 10-digit directory number (DN)

■ Tag associated with the call trace

■ Flag that indicates if some of the data is invalid and the reason for invalid data

■ Station class mark (SCM)

■ CDMA channel

■ CDMA traffic sequence number

■ Current voice coder/decoder rate

■ CDMA tick ID

■ CDMA primary digital gain



■ CDMA elapsed time

■ Cell site ID

■ ECP ID

■ Pilot set

■ Antenna face

■ Pilot PN

■ Priority group

■ Channel element (CCC-CCU-CE)

■ Pilot strength measurement

■ Round trip delay

■ Received Eb/No

■ Keep indicator identifies active candidate member(s)

■ Mobile forward traffic tick ID (displayed with Markov-Phase 2 call type only)

■ Mobile reverse traffic tick ID (displayed with Markov-Phase 2 call type only)

■ Mobile retrievable parameters for forward traffic channels are listed in Table 2 onpage 11:

Table 2. Mobile Forward Traffic Frame Count Definitions - Voice

RF Call TraceCounter Name

Description IS-95* Name8K 13K

M_F_1 full rate MUX1_FOR_1 MUX2_FOR_1

M_F_2 1/2 rate† dim & burst MUX1_FOR_2 MUX2_FOR_2



M_F_5 blank & burst MUX1_FOR_5 MUX2_FOR_5

M_F_6 1/2 rate MUX1_FOR_6 MUX2_FOR_11



M_F_9 full rate likely MUX1_FOR_9 N/A

M_F_10 erasure MUX1_FOR_10 MUX2_FOR_26



NOTE:The mobile counters are not cleared after a handoff nor after reporting measurementsto the cell. These parameters are taken from the mobile on a snap-shot basis for eachpolling interval. All of the frame counts that are displayed for the mobile, except for thecounts in the first response message, are the difference between current and previouspolls. The frame counts that are displayed for the mobile in the first response messageare not the difference between the current and previous poll because there are noprevious counts to use as a base to determine the difference. Because mobile countersare not reset, the frame counts that are displayed for the mobile in the first responsemessage are larger than normal. The polling interval for CDMA measurements are inthe range of 2 seconds to 60 seconds, with a default of 30 seconds. When more thanone DN is traced, the minimum polling interval is defined in the formula in Figure A onpage 21.

■ Mobile retrievable parameters for reverse traffic channels are listed in Table 3 onpage 12:

* The IS-95 names are from the following EIA/TIA Standards documents:Mobile Station-Base Station Compatibility Standard for Dual-Mode Wide-band Spread Spectrum Cellular System plus Telecommunications Sys-tems Bulletin: Support for 14.4 Kbps Data Rate and PCS Interaction forWideband Spread Spectrum Cellular Systems, February 27, 1996.† Rate indicates the rate of the primary data. For example, “1/2 rate dimand burst” means that the frame was a full rate dim and burst frame with 1/2 rate primary data.

Table 3. Mobile Retrievable Parameters for Reverse Traffic Channels


Description IS-95* Name8K 13K

M_R_1 full rate MUX1_REV_1 MUX2_REV_1

M_R_2 1/2 rate† dim & burst MUX1_REV_2 MUX2_REV_2



M_R_5 blank & burst MUX1_REV_5 MUX2_REV_5

M_R_6 1/2 rate MUX1_REV_6 MUX2_REV_11





■ Cell reverse traffic frame statistics from each serving cell site (before the frameselection process) and from the primary cell site (after the frame selectionprocess)

— Number of 9600 bps frames without detected errors

— Number of 9600 bps frames with bit errors

— Number of frames with insufficient-quality-to-decide-upon rate

— Number of 4800 bps frames



— From the primary cell site (after the frame selection process)

■ Cell forward traffic frame statistics

— Number of full-rate frames transmitted to the mobile

— Number of half-rate frames transmitted to the mobile

— Number of quarter-rate frames transmitted to the mobile

— Number of eighth-rate frames transmitted to the mobile

— Number of blank-and-burst signaling frames transmitted to the mobile

— Number of dim-and-burst signaling frames transmitted to the mobile

■ Current coder/decoder type remains the same for the duration of the call. Thefollowing coder/decoder types are currently supported:

— 0 = 8k voice

— 1 = 13k voice

— 2 = EVRC voice

— 3 = 8k Markov

— 4 = 13k Markov

— 5 = invalid SOR

* The IS-95 names are from the following EIA/TIA Standards docu-ments: Mobile Station-Base Station Compatibility Standard for Dual-ModeWideband Spread Spectrum Cellular System plus TelecommunicationsSystems Bulletin: Support for 14.4 Kbps Data Rate and PCS Interactionfor Wideband Spread Spectrum Cellular Systems, February 27, 1996.† Rate indicates the rate of the primary data. For example, “1/2 rate dimand burst” means that the frame was a full rate dim and burst frame with1/2 rate primary data.



Markov RF Call Trace

The Markov RFCT is based on the Markov Service Option (SO), which providespseudo-random data for testing the traffic channel between the mobile station and thebase station. A Markov test can be performed at a fixed data rate (full-, half-, quarter-,or eighth-rate) or a variable data rate. The selection of data rate of each packet in thevariable-rate test is governed by a pseudo-random process. The contents of eachpacket type are also generated by a pseudo-random process. The pseudo-randomprocesses are synchronized between the mobile station and the base station, thus thereceiving side can reproduce the same packet that the transmitting station generates.The Markov SO counts the number of various frames that are transmitted on the trafficchannel. The Markov SO also counts the number of various frames that are received onthe traffic channel and the number of bit errors found by comparing the information bitsthat are received with the locally generated information bits.

A mobile may initiate a Markov SO test for Rate Set 1 (8Kbps) or Rate Set 2 (13Kbps)at call setup time. The cell assigns the default rate (fixed full rate) to the Markov test.The following Markov Service Options are currently supported:

■ For Rate Set 1 (8Kbps)

— 0x’801E’ (that is, New 8K Markov Call)

■ For Rate Set 2 (13Kbps)

— 0x’801F’ (that is, New 13K Markov Call)

NOTE:Mobile station forward and reverse frame statistics are only available to RFCT duringvoice calls. Therefore, running RFCT on a New 8K or 13K Markov call produces onlycell counts; no mobile data is retrieved. Additionally, cell counts are collected by andreported from the Multiplex layer prior to Markov frame rate and frame content analysis.

Enhanced RF Call Trace/Markov - Phase 1

The Enhanced RF Call Trace/Markov - Phase 1 feature provides the ability to retrievemobile station forward and reverse frame statistics that are collected at the cell duringNew 8K and New 13K Markov calls and makes these statistics available to RFCT. Cellcounts remain as multiplexor statistics in this phase.

This enhancement makes use of the Service_Option_Control message counterretrieval mechanism to collect and compute the required RFCT statistics. Thismechanism allows for the retrieval of all required vector sets2 and manages datacollection such that counter retrieval requests to the mobile are done at the appropriateMarkov synchronization frames.

2 A vector set consists of counter values based on the test-mode (that is, data rate). There are fivetypes of test-mode: variable rate and four fixed rates -full, 1/2, 1/4, and 1/8.



NOTE:Because the retrievable Markov statistics for the mobile are updated once per Markovsynchronization interval, the Markov RFCT polling interval, if possible, should be amultiple of the synchronization frame interval (that is, 512 frames or 10.24 seconds).

The Markov data retrieved in this phase is mapped into the existing RFCT screendisplay. See Table 4 on page 15 and Table 5 on page 15 for specific mapping details.

Table 4. Mobile Reverse Traffic Frame Count Definitions - Markov


Description Markov Counter* Name

MK_R1 full rate MSO_E1_T1

MK_R2 full rate & 1/2 rate dim &burst

MSO_E1_TD + MSO_E2_TD

MK_R3 1/4 rate dim & burst MSO_E4_TD


MK_R5 blank & burst (all rates) sum of MSO_Ex_TB (wherex=1, 2, 4, or 8)

MK_R6 1/2 rate MSO_E2_T2



* The Markov counters are those that are received from the mobile. For moreinformation, refer to the manufacturer’s documentation.

Table 5. Primary Cell Mapping for Mobile Received Markov Statistics on theForward Link (Sheet 1 of 2)



MK_F1 expected full, received full MSO_E1_R1

MK_F2 expected full or 1/2,received dim & burst

MSO_E1_RD & MSO_E2_RD

MK_F3 expected 1/4, receiveddim & burst

MSO_E4_RD


MSO_E8_RD



Enhanced RF Call Trace/Markov - Phase 2

In addition to the capabilities described under Enhanced RF Call Trace/Markov - Phase1, the Enhanced RF Call Trace/Markov - Phase 2 feature provides the ability to retrievecell Markov statistics maintained by the Markov packet processing function and makethem available to RFCT.

With this enhancement, cell frame statistics are reported to RFCT based on the calltype (voice or Markov). In the case of a voice call, cell frame statistics are reported toRFCT from the Multiplex layer. In the case of a Markov call, reporting are done from theMarkov subsystem after Markov analysis and include the following new data:

■ additional counts for the "Dim & Burst" and "Blank & Burst" categories

■ separate counts for "Full Rate Likely" and frames containing bit errors asdetermined by Markov frame analysis

■ the forward and reverse tick IDs of the respective Forward and Reverse MarkovSynchronization frames

MK_F5 expected x, received blank& burst

sum of MSO_Ex_RB (wherex=1, 2, 4, or 8)

MK_F6 expected 1/2, received 1/2 MSO_E2_R2



MK_F9 expected x, received fullrate likely or bit errors

sum of MSO_Ex_RFL +MSO_Ex_RERR (where x=1,2, 4, or 8)

MK_10 expected x, receivederasure

sum of MSO_Ex_RE wherex=1, 2, 4, or 8)

* For more information, refer to the manufacturer’s documentation.

Table 5. Primary Cell Mapping for Mobile Received Markov Statistics on theForward Link (Sheet 2 of 2)





The existing Markov data retrieved in this phase is mapped into a new RFCT responsemessage which also includes the additional data previously described. See Table 6 onpage 17 and Table 7 on page 17 for specific mapping details.

Table 6. Mobile Reverse Traffic Frame Count Definitions - Markov



MK_R1 full rate MSO_E1_T1

MK_R2 full rate dim & burst MSO_E1_TD



MK_R5 blank & burst (all rates) sum of MSO_Ex_TB (wherex=1, 2, 4, or 8)





* The Markov counters are those received from the mobile. For moreinformation, refer to the manufacture’s documentation.

Table 7. Mobile Forward Traffic Frame Count Definitions - Markov (Sheet 1 of 2)



MK_F1 expected full, receivefull

MSO_E1_R1

MK_F2 expected full, receiveddim & burst

MSO_E1_RD


MSO_E4_RD


MSO_E8_RD

MK_F5 expected x, receivedblank & burst

sum of MSO_Ex_RB (wherex=1, 2, 4, or 8)

MK_F6 expected 1/2, received1/2

MSO_E2_R2



Calculating Frame Error Rates

To calculate forward Frame Error Rates (FERs) use the calculations in the followingtable::


MSO_E4_R4


MSO_E8_R8

MK_F9 excepted x, receivedfull rate likely +excepted x, received y(rate mismatches)

sum of MSO_Ex_RFL (wherex=1, 2, 4, or 8) + sum ofMSO_Ex_Ry (wherex=1, 2, 4, or 8 andy=1, 2, 4, or 8)

MK_10 expected x, receivederasure

sum of MSO_Ex_RE (wherex=1, 2, 4, or 8)

MK_11 expected 1/2, receiveddim & burst

MSO_E2_RD

MK_12 expected x, receivedframe with bit errors

sum of MSO_Ex_RERR, (wherex=1, 2, 3, 4)

* The Markov SO counters are those maintained at the primary cell. For moreinformation, refer to the manufacturer’s documentation.

Voice: (M_F_9 + M_F_10) / (sum of M_F_x where x = 1 - 10)

Markov(Phase 1): (MK_F9 + MK_10) / (sum of MK_x where x = F1 - F9, and 10)

Markov(Phase 2):

(MK_F9 + MK_10 + MK_12) / (sum of MK_x where x = F1 - F9,10,11, and 12)

Table 7. Mobile Forward Traffic Frame Count Definitions - Markov (Sheet 2 of 2)





To calculate reverse link FERs, using the After-Frame-Selection Data on the RFCTreport, use the following table::

The following features are described as part of RF Call Trace in CDMA mode:

■ CDMA RF Call Trace (CDMARFCT)

■ CDMA Multiple Directory Number (DN) RF Call Trace (CDMA MDNRFCT)

■ CDMA Adding and Deleting DN(s) During a RF Call Trace

■ CDMA Enhancement Adding and Deleting DN(s) During a RF Call TraceSession

CDMA RF Call Trace (CDMARFCT)

The CDMA RF Call Trace (CDMARFCT) feature (for AMPS/CDMA mode) is used totrace a mobile call that is operating in the Code Division Multiple Access (CDMA) modeand is based on AMPS/TDMA RF Call Trace with two new message types for requestand response. CDMA RF Call Trace also supports the reporting of Markov statisticswith the addition of the Enhanced RF Call Trace/Markov - Phase 1 and 2 features.

The following features are enhancements to CDMA RF Call Trace for a Markov call:

■ The Enhanced RF Call Trace/Markov - Phase 1 feature is based upon theMarkov Service Option (SO), which provides pseudo-random data for testing thetraffic channel between the mobile station and the base station. Phase 1provides the ability to retrieve mobile station forward and reverse frame statisticscollected at the cell during New 8K and New 13K Markov calls and makes thesestatistics available to RFCT.

■ The Enhanced RF Call Trace/Markov - Phase 2 feature is an enhancement,which provides pseudo-random data for testing the traffic channel between themobile station and the base station. Phase 2 is an enhancement to Phase 1 andprovides the ability to retrieve cell Markov statistics that are maintained by theMarkov packet processing function and make them available to RFCT.

Voice: Divide the sum of full rate with bit error + quality insufficient by thetotal number of frames in the report (for example, the sum of allsix rows)

Markov(Phase 1) &(Phase 2):

Divide the sum of frames with bit errors + quality insufficient bythe total number of frames in the report (for example, the sum ofall six rows)



CDMA Multiple Directory Number (DN) RF Call Trace(CDMA MDNRFCT)

The CDMA Multiple Directory Number (DN) RF Call Trace (CDMA MDNRFCT) featureallows the recording of signal strength and other information for up to ten designatedCDMA or AMPS mobiles (during a single session) on CDMA cells (APXDx.xx), withinthe system coverage area.

NOTE:The CDMA MDNRFCT feature is not supported by TDMA cells (APXBx.xx). When theCDMA MDNRFCT feature is active, RF Call Trace does not record information forTDMA and AMPS mobiles on TDMA cells (APXBx.xx).

CDMA Adding and Deleting DN(s) During a RF CallTrace

The CDMA Adding and Deleting DN(s) During a RF Call Trace feature is anenhancement to the CDMA MDNRFCT feature. This enhancement provides RFCT toolusers with the capability to add DNs to a RF Call Trace session, delete DNs from a RFCall Trace session, and report RF Call Trace status.

NOTE:The CDMA Adding and Deleting DN(s) during RF Call Trace enhancement does notrecord information for TDMA/AMPS cells (APXBx.xx).

When more than one DN is traced, the minimum polling interval is defined as follows:

NOTE:The Minimum Equivalent Polling Interval table is only valid when all the polling periodsare the same. Analog mobiles must have the same polling period.

Table 8. Minimum Equivalent Polling Interval

Polling Interval Number of DNs

2 seconds 1 to 4 DNs






CDMA Enhancement Adding and Deleting DN(s)During a RF Call Trace Session

For the CDMA Adding and Deleting DN(s) During a RF Call Trace sessionenhancement to be “on” the CDMA MDNRFCT FAF must be marked active. For theCDMA Adding and Deleting DN(s) During a RF Call Trace Session enhancement, therequested polling period for a MDN RFCT session is accepted as long as the “Numberof DN” versus “the Polling-Period” is represented by the following equation:

where N is the number of DNs in the RF Call Trace session, and Polling Period i is therequested polling period of the i th DN.

Figure A. MDN RFCT Bandwidth formula

NOTE:The formula for the enhancement applies to both CDMA and analog calls; however, allanalog mode calls in a MDN RF Call Trace session must have the same polling period.If any analog call has a polling period that is different from any other analog call, thedifference can cause erroneous results for all analog DNs in the session, and allsubsequent call trace request records for analog calls will indicate that the data may beinvalid.

The -F parameter of the FTrfdump command sends subsequent log records, whichmatch the specified input parameters, to the standard output in real-time. The logrecords are written to the RFCT log files as well as the user terminal. The interruptsignal stops neither the RFCT for any DN, nor the writing of any RFCT records to thelog file.

NOTE:The real-time output capability has been moved to the FTrfdump command. TheFTrftrace -o real-time option is not supported for MSCs with the CDMA MDNRFCTFAF. If the user enters the obsolete FTrftrace command, the OMP returns an errormessage that refers the user to the new FTrfdump -F parameter.

The -s parameter of the FTrftrace command returns the following information foreach call in the RFCT session:

■ DN

■ Tag

N1 ≤2 per second

i=1PollingPeriodiΣ



■ Polling Period

■ Interval Remaining

The -s parameter also returns the RFCT bandwidth available.

NOTE:An error message is provided if the user attempts to use the -s parameter inconjunction with any other options for the FTrftrace command.

UNIX® System Commands

The following sections describe more fully the UNIX software commands that are usedto

■ initiate or add DNs (FTrftrace)

■ stop/delete DNs (FTrfstop)

■ obtain outputs (FTrfdump) from the RF Call Trace feature

■ to delete log file records (FTrfclear)

FTrftrace Command

The FTrftrace command is the main UNIX System function that controls the RF CallTrace feature. Once invoked, FTrftrace verifies that the feature is activated in theFeature Activation File (FAF). FTrftrace then checks the command line input andsends a message to the Administrative Call Processing Data Base Node (ACDN) tobegin call trace measurements. If any errors are detected, FTrftrace terminates andprints an error message. See Appendix A - FTrftrace(1) on page 39 for the FTrftracecommand and its options.

FTrftrace runs in the background (unless real-time output is requested) and collectsthe trace information that is sent from the cell site nodes. As each locate reply iscollected, FTrftrace records the time and writes the data to log files and, with thereal-time dump option, to standard out (terminal). If desired, the data may then becopied to a user-named file to be saved for later processing.

With the FTrftrace command, up to eight cell sites may be specified formeasurements, along with the measurement rate and total measurement interval. Theuser may also specify the use of the serving cell’s neighbor-1 neighbors in AMPSmode.

When the CDMA MDNRFCT FAF is marked active, the FTrftrace command can beused to add one or more DNs to the active session. Also, with the -s option the statusof a particular session and the available bandwidth for adding a single DN are available.



NOTE:When the CDMA MDNRFCT FAF is marked active the FTrftrace -o option is no longeravailable. The real-time output capability has been moved to the FTrfdump command.

FTrfstop Command

The call trace process can be terminated in two ways. A normal termination occurswhen the trace duration time expires. A manual termination command, FTrfstop, canbe executed to stop the call trace at any point before normal termination. When morethan one DN is traced, this command terminates the traces on a given call, a list ofDNs, all DNs for a tag, or all DN(s) in the session. Appendix B contains the commandinformation for FTrfstop.

FTrfdump Command

FTrfdump is a UNIX System command that searches the FTRFTRACE file for recordsthat match the given input parameters. FTrfdump scans the log files (FTRFTRACE0and FTRFTRACE1 located in the /omp-data/logs/rfct/ directory) for matches based oneither the mobile DN or a message tag that identifies an individual trace or set of traces.

Either a fully interpreted, formatted output or a raw ASCII output format may beoptionally selected.

See Appendix D for the FTrfdump command and its options, along with samples ofboth the formatted and raw ASCII outputs.

NOTE:When the CDMA MDNRFCT FAF is active, the real-time output capability (-o option) ismoved from the FTrftrace command to the FTrfdump command.

FTrfclear Command

FTrfclear is a UNIX System command that reads records from the binary log fileand deletes records that match the tag name specified on the command line.

See Appendix C for the FTrfclear command and its options.

15 Digit DN Feature—Impact on RF Call Trace

The 15 Digit DN feature provides a new and more flexible DN structure to meet theneeds of international markets, while preserving the ability to handle the traditional 10-Digit Mobile Directory Number (MDN) which meets the needs of current serviceproviders.

The impact of the15 Digit DN feature on RF Call Trace is that each of the DNs specifiedfor call trace can be a string of 1 to 14 digits. Therefore, the 15 Digit DN feature impactsthe following UNIX System Commands for RF Call Trace:



■ FTrftrace—Refer to “Appendix A - FTrftrace(1)” on page 39

■ FTrftstop—Refer to “Appendix B - FTrfstop(1)” on page 43

■ FTrfdump—Refer to “Appendix D - FTrfdump(1)” on page 47

NOTE:With the 15 Digit DN feature, if a non-10 Digit DN is specified but does not appear ineither the HLR database or the VLR database, then the trace is not performed. This isbecause only a 10-digit DN can be transformed into a MIN that is used for paging.

Basic RF Call Trace for 3G-1X High Speed Packet Data(HSPD)

The Basic RF Call Trace for 3G-X HSPD feature builds on additions made previously byBasic RF Call Trace for 3G-1X Voice using 2G Message Unused Fields (FID# 2137.10).A new field is added to the CCU->CCC response message to contain the averageforward transmit power on the fundamental channel (Ectf). (This information waspreviously placed in the Eb/No field.)

This feature enables the display (verbose output and WatchMark Prospect for LucentTM

software output) of new data values for 3G HSPD calls and continues to support thesame display for 2G and 3G voice calls. There are five new data measurementsdisplayed by this feature for each burst rate (2x, 4x, 8x, and 16x):

■ the forward average transmit power for the Forward Supplemental Channel (F-SCH) for each burst rate during the time of the burst (4 values)

■ the number of F-SCH frames transmitted during the interval for each burst rate(4 values)

■ the average Frame Error Counts (FEC) for each burst rate for each leg (up to 6legs-24 values)

■ the average After Frame Selection FEC for each burst rate (4 values)

■ the number of R-SCH frames received during the interval for each burst rate (4values)

Stop Indicator

The request message includes a new stop indicator. The Ectf and Ects powermeasurements are CPU intensive and are done only when an RFCT session is active.The session is considered active from the first request and continues until a request isreceived with a stop indicator.

The time out of each RFCT session is removed and replaced by the stop indicatorfunctionality.




The Improved RF Call Trace for 3G-1X HSPD feature allows the display (verbose andraw formatted outputs) of new data values for 3G HSPD calls and continues to supportthe same display for 2G and 3G voice calls. There are nine new data measurementsdisplayed by the Improved RF Call Trace for 3G-1X HSPD feature:

1. avg_ior_fwd - average forward transmit power

2. rfch_ebno - 3G R-FCH EbNo for each serving cell

3. rsch_ebno - 3G R-SCH EbNo for each rate of each serving cell

4. num_fsch_mob_frames - number of F-SCH mobile frame received for eachrate

5. num_rsch_mob_frames - number of R-SCH mobile frame transmitted foreach rate

6. num_sch_Itu - number of LTUs received by the mobile

7. num_sch_Itu_good - number of F-SCH DTX frames for each rate

8. num_dtx_fsch_frames - number of F-SCH DTX frames for each rate

9. num_dtx_rsch_frames - number of R-SCH AFS DTX frames for each rate

Release 20.0 also supports the following 3G displays:

■ avg ectf (average forward fundamental transmit power for the call for thepolling interval in scaled linear units -6 values)

■ avg ects (F-SCH) - forward average transmit power for the F-SCH for eachburst rate during the time of the burst (4 values)

■ num fsch frames (F-SCH) - the number of F-SCH frames transmitted duringthe interval for each burst rate (4 values)

■ rsch fec per leg (R-SCH) - the average Frame Error Counts (FEC) foreach burst rate for each leg (up to 6 legs - 24 values)

■ rsch afs fec (R-SCH) - the average after frame selection FEC for each burstrate (4 values)

■ num rsch frames (R-SCH) - the number of R-SCH frames received duringthe interval for each burst rate (4 values)

Up to 104 new values will be displayed on the output of FTrftrace, including the 6existing fields and the 9 new fields.

Feature Description for Enhanced RF Call Trace for3G-1X Calls

The Enhanced RF Call Trace for 3G-1X Calls feature provides additional 3G-1X RF CallTrace functionality relative to FID 2137.4. This additional functionality includes thecapability of testing a 3G-1X system to provide time stamp burst information.



The Enhanced RF Call Trace for 3G-1X Calls feature allows the display (verbose andraw formatted outputs) of new data values for 3G HSPD calls and continues to supportthe same display for 2G and 3G voice calls. There are five new data measurementsdisplayed by the Enhanced RF Call Trace for 3G-1X Calls feature:

1. NSFFSofter - The number of non-DTX F-SCH frames in softer hand-off duringpolling interval.

2. ECTSSofter - The average transmit power for the softer F-SCH during pollinginterval.

3. NSFDTXSofter - The number of DTX F-SCH frames in softer hand-off duringpolling interval.

4. NAXFER - The number of anchor setups during the polling interval.

5. Anch_Hist - The history of the anchor setups during the polling interval, up to10. The anchor ID consists of the MSC number, the Cell number, the facenumber, and the PN Offset of the face. The history is empty if there are noanchor setups during the interval.

6. Burst_Info - The history of burst information, both forward and reverse for thepolling interval. The system remembers information of up to 12 forward-directionand 12 reverse-direction bursts. Each structure contains

■ Start Time

■ Requested SCH Rate

■ Radio Configuration

■ Forward/Reverse Flag

■ Allocated SCH Rate

■ Simultaneous FCH Flag

■ Allocated Duration

■ F-SCH Simplex/Softer Flag

■ F-SCH Simplex or First Softer Path Information

■ F-SCH Second Softer Path Information (if any)

■ Allocation Flags

■ Resource Block/Rate Limit Indicator

■ Early Release Indicator

■ F-SCH Continuation Denied Indicator

■ Actual Duration (frames, both normal and early releases)

When the primary transfer occurs, number 1 through 5 are transmitted from the oldprimary to the new primary. Before a secondary leg drops, the Enhanced RF Call Tracefor 3G-1X Calls feature sends NSFFSofter , NSFDTXSofter, and Forward burstinformation to the primary cell.



Release 21.0 also supports the following 3G displays:

■ avg ectf (average forward fundamental transmit power for the call for thepolling interval in scaled linear units -6 values)

■ avg ects (F-SCH) - forward average transmit power for the F-SCH for eachburst rate during the time of the burst (4 values)

■ num fsch frames (F-SCH) - the number of F-SCH frames transmitted duringthe interval for each burst rate (4 values)

■ rsch fec per leg (R-SCH) - the average Frame Error Counts (FEC) foreach burst rate for each leg (up to 6 legs - 24 values)

■ rsch afs fec (R-SCH) - the average after frame selection FEC for each burstrate (4 values)

■ num rsch frames (R-SCH) - the number of R-SCH frames received duringthe interval for each burst rate (4 values)

■ avg_ior_fwd - average forward transmit power

■ rfch_ebno - 3G R-FCH EbNo for each serving cell

■ rsch_ebno - 3G R-SCH EbNo for each rate of each serving cell

■ num_fsch_mob_frames - number of F-SCH mobile frames received for eachrate

■ num_rsch_mob_frames - number of R-SCH mobile frames transmitted foreach rate

■ num_sch_Itu - number of LTUs received by the mobile

■ num_sch_Itu_good - number of F-SCH DTX frames for each rate

■ num_dtx_fsch_frames - number of F-SCH DTX frames for each rate

■ num_dtx_rsch_frames - number of R-SCH AFS DTX frames for each rate.

Up to 149 new values are displayed on the output of FTrftrace, including the 15existing fields and the 4 new fields.

Overload Conditions

In Release 21.0 and later releases, when a secondary CDMA Cluster Controller (CCC)receives a request from the primary CCC for a call to collect data for RFCT, thesecondary CCC checks its own CCC Overload Status. If the CCC is in overload, therequest is discarded. Similarly, RFCT does not collect, store, or report data when aRadio Cluster Controller (RCC), Time Division Multiplex (TDM) Bus control channel, orPrimary CCC are in overload.

For details on how the Flexent®/AUTOPLEX® system handles overload conditions, see401-610-009, System Capacity Monitoring and Engineering Guidelines.



Major RFCT Metrics Summary

Table 9 on page 28 and Table 10 on page 28 shows the major RFCT metricssupported/not supported in recent releases.

Table 9. 2G/3G Voice RFCT Capabilities Across Different Software Releases

Metric Release 17.10 Release 18.0(and later)

2GCCU

3GCCU

2GCCU

3GCCU

Frame counts (2G/3G: RFER) Yes Yes Yes Yes

Traffic power (2G) Yes Yes Yes Yes

Traffic power (3G:FCH) [This data, alsoknown as Ectf, is not available in the rawoutput format in R17.1, but is available inR18.0.]

N/A Yes N/A Yes

Reverse Eb/No (2G call) Yes Yes Yes Yes

Reverse Eb/No (3G call) N/A No N/A No

Call status info Yes Yes Yes Yes

Forward Pilot Ec/Io (2G call) Yes Yes Yes Yes

Forward Pilot Ec/Io (3G call) N/A No N/A No

Round trip delay (2G call) Yes Yes Yes Yes

Round trp delay (3G call) N/A No N/A No

Multiple Dial Number RFCT Yes Yes Yes Yes

2G/3G simultaneous RFCT Yes Yes Yes Yes

Table 10. 3G-1X HSPD RFCT Capabilities

Metric Release 18.0(and later)

3G CCU

Frame counts/RFER (RFCH) Yes

Traffic power (FFCH) Yes

Frame counts /RFER (RSCH) Yes

Frame counts (FSCH) Yes

Traffic power (FSCH) [This data is also known as Ects.] Yes

Feature Interactions 401-612-052, Issue 17


5. Feature Interactions

The RF Call Trace Dual-Mode TDMA/AMPS Mobiles feature is dependent on the RFCall Trace feature being active.

The RF Call Trace CDMA/AMPS Mobiles feature is dependent on the RF Call Tracefeature being active.

CDMA Multiple DN RF Call Trace support for AMPS mobiles is dependent on the RFCall Trace feature being active. The CDMA MDNRFCT is not currently supported byTDMA cells (APXBx.xx). When the CDMA MDNRFCT feature is active, RF Call Tracedoes not record information for TDMA and AMPS mobiles on TDMA cells (APXBx.xx).

NOTE:The CDMA MDNRFCT and TDMA cells (APXBx.xx) are mutually exclusive.

CDMA Multiple DN RF Call Trace support for CDMA/AMPS mobiles is dependent onthe CDMARFCT feature being active.

CDMA RF Call Trace works with the CDMA Circuit-Mode Data service. The appropriateservice options used for data calls are added to the trace output.

NOTE:CDMA RFCT and CDMA Multiple DN Feature Activation Files (FAF) must be activated.No new FAF files are needed to activate the Improved RF Call Trace for 3G-1X HSPDfeature.

6. Special Considerations

This section gives any special considerations of this feature.

Call status info Yes

Reverse Eb/No (RFCH/RSCH) No

Forward Pilot Ec/Io No

Round trip delay No

Multiple Dial Number RFCT Yes

Table 10. 3G-1X HSPD RFCT Capabilities

Metric Release 18.0(and later)

3G CCU

Caveats 401-612-052, Issue 17


Subscriber Perspective

The subscriber does not have any direct interaction with the RF Call Trace features.

Service Provider Perspective

The service provider initiates, stops, and prints the call traces using the FTrftrace,FTrfstop, and FTrfdump UNIX commands on the OMP. The FTrfclear UNIXcommand on the OMP is used to maintain the RF Call Trace binary log files. Thesecommands may be executed directly from the OMP shell. See Appendix A, Appendix B,Appendix D, and Appendix C, respectively, for information on how to use thesecommands.

The OMP Scheduler (OSCHED) tool on the OMP also provides the capability toschedule a call trace for later execution.

The OMP shell and OSCHED can be accessed through the MISCELLANEOUSAPPLICATIONS item in the OMP main menu. On-line manual pages for these UNIXcommands may be obtained through the man command on the OMP.

NOTE:Only users under the “pace” group-id, as enforced by the /etc/group file, havepermission to execute the RFCT tools on the OMP. The user must also execute /omp/etc/ompprofile and /omp/etc/ompenv to obtain a consistent environment.

7. Caveats

The RF Call Trace feature has the following limitations:

■ Call traces can be run only on cell sites within the local system; that is,inter-MSC tracing is not possible.

■ Only one RF call trace session per system can be active at any one time.

■ Call Traces do not work for Mobile Identification Number (MIN)/DN separatedmobiles after inter-MSC handoffs.

NOTE:If the Multiple DN RF Call Trace feature is active, still only one RF call trace session persystem can be active at any one time. However, multiple users can add and delete DNsfrom the active session.

CDMA IMSI

The RF Call Trace feature has the following limitations when the CDMA FullInternational Mobile Station Identity (IMSI) optional feature is activated:

Caveats 401-612-052, Issue 17


■ The technician enters the DN of the mobile as part of the RF Call Tracecommand to specify the mobile whose call is to be traced. If the MSC does nothave the subscriber record or vlr of the mobile, the MSC attempts to perform thetrace as if the mobile is programmed with a MIN-based IMSI and as if the MINand the DN of the mobile are the same. If the MIN and the DN of the mobile arenot the same as a result of MIN-MDN separation or if the mobile is programmedwith only a True IMSI, then the trace fails.

■ When the CDMA Full IMSI feature is activated, due to the preceding limitation,RF Call Trace cannot be done for some CDMA calls that are handed off toanother MSC. For a RF Call Trace attempted at the target MSC for a hardhandoff or at the remote MSC for a soft or semi-soft handoff, the trace can beperformed only if the mobile is programmed with a MIN-based IMSI and the DNof the mobile and MIN are the same.

■ If a VLR does not exist for this roamer, RF Call Trace cannot be done for aroaming mobile that is programmed with only a True IMSI.

RFCT for Dual Mode

The RF Call Trace for Dual Mode for the AMPS/TDMA feature has the followinglimitations:

■ All the limitations of the RF Call Trace feature.

■ Cells must be on the serving face MAHO list in order to be measured by themobile.

Multiple DN RFCTB

The Multiple DN RF Call Trace feature has the following limitations:

■ Because of the possible increase in call trace message traffic, use of MDN RFCall Trace is not recommended at times of peak traffic.

■ All the analog DNs must use the same polling period.

■ The CDMA MDNRFCT feature is not supported by TDMA cells (APXBx.xx).When the CDMA MDNRFCT feature is active, RF Call Trace does not recordinformation for TDMA and AMPS mobiles on TDMA cells (APXBx.xx).

Basic RFCT for 3G-1X HSPD

The Basic RFCT for 3G-1X HSPD feature does not affect retrofit procedures. However,the ECP and OMP must remain backward compatible so that the Basic RFCT for 3G-1X HSPD feature can send RFCT requests to cells that are running older softwareloads, as well as cells running the 3G (18.0 or later) software. This includes thepossibility that any given call (except 3G packet data calls) can undergo a primarytransfer between old and new cells during the RFCT session.

Feature Implementation 401-612-052, Issue 17


In addition, the cells themselves must be able to handoff with other cells running oldersoftware loads. The inter-cell messaging must be backward compatible so that ahandoff can occur while RFCT is running from a new cell to an older cell.

8. Feature Implementation

To activate the RF Call Trace features, including both phases of the Markovenhancements (see “Markov RF Call Trace” in this document), a FAF must be installedon the ECP with the appropriate entries marked active. The entries associated with theRF Call Trace features are

■ RFCT—RF Call Trace.

■ DMRFCT—RF Call Trace for Dual-Mode -TDMA/AMPS- Mobiles. The RFCT FAFmust also be marked active.

■ CDMARFCT—RF Call Trace for CDMA/AMPS- Mobiles. The CDMARFCT FAFalso activates the CDMA Markov enhancements. The RFCT FAF must also bemarked active.

■ CDMA MDNRFCT—CDMA Multiple DN RF Call Trace. The RFCT FAF must alsobe marked active. The CDMA MDNRFCT feature does not record information forTDMA cells (APXBx.xx). CDMA MDNRFCT FAF also activates the CDMA Addingand Deleting DN(s) During a RF Call Trace enhancement.

NOTE:If the CDMA MDNRFCT FAF is not activated and more than one DN is requested, theFTrftrace command exits with an error message that indicates that only one DN canbe traced without CDMA MDNRFCT active.

Basic RF Call Trace for 3G-1X High Speed Packet Data(HSPD)

There are no activation issues with the Basic RF Call Trace for 3G-1X HSPD feature.No changes are made to what is supported with the FAF. No new FAFs are required forthis feature.


There are no activation issues with the Improved RF Call Trace for 3G-1X HSPDfeature. No changes are made to what is supported with the FAF. No new FAFs arerequired for this feature.

Feature Implementation 401-612-052, Issue 17


Enhanced RF Call Trace for 3G-1X Calls

There are no activation issues with the Enhanced RF Call Trace for 3G-1X Callsfeature. No changes are made to what is supported with the FAF. No new FAFs arerequired for this feature.

Supplemental Information 401-612-052, Issue 17


9. Supplemental Information

This section gives the abbreviations and references used in this document.

Abbreviations

The following abbreviations are used in this document.

ACDN Administrative Call Processing Data Base Node

AMPS Advanced Mobile Phone Service (analog radios/service)

BER Bit Error Rate

CCC CDMA Cluster Controller

CCU CDMA Channel Unit

CDMA Code Division Multiple Access

CDMA RFCT RF Call Trace for Dual-Mode — CDMA/AMPS–Mobiles

CE Channel Element (CDMA)

CRFCT AMPS/CDMA RF Call Trace

dBm 0 Dbm = 1Mw @ 1004 Hz Terminated by 600 Ohm Impedance

DCS Digital Cellular Switch

DMRFCT RF Call Trace for Dual-Mode Mobiles (AMPS/TDMA)

DN Directory Number

DPC Dynamic Power Control

DRU Digital Radio Unit

DVCC Digital Verification Color Code

ECP Executive Cellular Processor

EDRU Enhanced Digital Radio Unit

EIA Electronic Industries Association

ESID Extended System/Switch Identifier



EVRC Enhanced Variable Rate Coding

FAF Feature Activation File

FER Frame Error Rate

FLCA Flexible Channel Allocation

GPS Global Positioning System

IMSI International Mobile Station Identity

IS-54B Interim Standard 54 Revision B

MAHO Mobile Assisted Handoff

MB Megabyte

MDNRFCT Multiple DN RF Call Trace

MIN Mobile Identification Number

MO/HMO Measurement Order/Hyperband Measurement Order

MSC Mobile Switching Center

OMP Operations and Maintenance Platform

OSCHED OMP Scheduler

PN Pseudo Noise

RCU Radio Channel Unit

RC/V Recent Change and Verify

RF Radio Frequency

RFCT RF Call Trace

RSSU Receive Signal Strength Units

SAM System Access Monitor

SAT Supervisory Audio Tone

SCM Station Class Mark

SDMAC Stored Dynamic Mobile Attenuation Code

SO Service Option

SOR Service Option Request

TDMA Time Division Multiple Access

TIA Telecommunications Industries Association

TRFCT AMPS/TDMA RF Call Trace

VMAC Voice Mobile Attenuation Code



References

The following Flexent®/AUTOPLEX® Wireless Networks documents containinformation related to the RF Call Trace feature:

■ 401-610-036, Database Update Manual

■ 401-610-055, Input Message Manual

■ 401-610-057, Output Message Manual

■ 401-612-311, Increased TDMA MAHO List

■ 401-612-422, MSC OA&M Support for 384 Cells

History of Revisions 401-612-052, Issue 17


10. History of Revisions

This section summarizes the changes that were made for previous issues of thisdocument.

Issue 16

This document was reissued to include support of the Improved RF Call Trace for 3G-1X HSPD feature as of ECP Release 20.0. For changes as a result of the Improved RFCall Trace for 3G-1X HSPD feature, refer to the following sections:

■ "Availability" on page 2

■ "Supported Technologies" on page 3

■ "Improved RF Call Trace for 3G-1X HSPD" on page 5


■ "Major RFCT Metrics Summary" on page 28

■ "Feature Interactions" on page 29


■ "Appendix D - FTrfdump(1)" on page 47

Issue 15

This document was reissued to include support of the Basic RF Call Trace for 3G-1XHSPD feature as of ECP Release 18.0. For changes as a result of the Basic RF CallTrace for 3G-1X HSPD feature, refer to the following sections:


■ "Supported Technologies" on page 3

■ "Benefits" on page 4

■ "Basic RF Call Trace for 3G-1X High Speed Packet Data (HSPD)" on page 24

■ "Caveats" on page 30

■ "Feature Implementation" on page 32

Issue 14

This document was reissued to include support of the MSC OA&M Support for 384Cells feature as of ECP Release 17.1. For changes as a result of the MSC OA&MSupport for 384 Cells feature, refer to the following sections:


■ "Feature Description" on page 5

History of Revisions 401-612-052, Issue 17


Issue 13

This document was reissued to include support of the Increased TDMA MAHO Listfeature as of ECP Release 16.1. For changes as a result of the Increased TDMAMAHO List feature, refer to the following sections:


■ "Increased TDMA MAHO List Feature" on page 8

Issue 12

This document was reissued to include support of the 15 Digit Directory Number (DN)feature as of ECP Release 16.0. For changes as a result of the 15 Digit DN feature,refer to the following sections:


■ "15 Digit DN Feature—Impact on RF Call Trace" on page 23

■ "Appendix A - FTrftrace(1)" on page 39

■ "Appendix B - FTrfstop(1)" on page 43

■ "Appendix D - FTrfdump(1)" on page 47

Issue 11

This document was reissued to include the CDMA Adding and Deleting DN(s) during aRF Call Trace session which is an enhancement to the CDMA MDNRFCT feature (ECPRelease 15.0 and later).

Issue 10

This document was reissued to include more information about the MK_F9 counter andinformation about CDMA Soft Handoff RF Call Trace Request (type 15) and CDMA6-way Soft Handoff RF Call Trace Reply (type 17).

Issue 9

This document was reissued to include information required for the ECP Release 11.0/CDMA Release 6.0 feature Multiple DN RF Call Trace. This feature impacts CDMA andAMPS RF Call Trace. Additionally, this document is being reissued to includeinformation relating to the migration of the RF Call tool from the ECP to the Operationsand Maintenance Platform (OMP). This feature impacts all call modes including AMPS,AMPS/TDMA, and AMPS/CDMA. This document is also being reissued to includeinformation about interactions with the CDMA Circuit-Mode Data optional feature.

Appendix A - FTrftrace(1) 401-612-052, Issue 17


11. Appendix A - FTrftrace(1)

FTrftrace(1) AUTOPLEX(1000) FTrftrace(1)

Name

FTrftrace - Start (or add DNs to) RF Call Trace.

Synopsis

FTrftrace [-c cells] [-d dirnumbers] [-m dnfile] [-i interval] [-p period] [-t tag] [-o][-r] [-D] [-f] [-n]

[-F forward rate] [-R reverse rate]FTrftrace [-s status]

Description

FTrftrace allows a service provider to make power level measurements. When theMultiple DN FAF is active (CDMA/Analog) the command allows the user to start a newtrace, add DNs to an existing session (for a maximum of 10), and obtain statusinformation of current traces along with available bandwidth.

NOTE:The Multiple DN FAF is available only in the CDMA cells (APXDx.xx) for tracing calls inCDMA or Analog mode. Also the FTrfstop command may be used to delete individualDNs from an active session.

On an active call in analog mode measurements are made by each cell in the list ofcells.

On an active call in TDMA/AMPS mode, if the -c option is used, mobile measurementsare collected if the mobile is on an ECP Release 5.1 (or later) and if that cell is on the -clist. Otherwise, no measurements are made. The MAHO list for the serving cell is usedto determine which radio channels to measure. In TDMA mode, when -c and -f appeartogether on the command line, this is equivalent to -n. The -f option is used to forcemeasurements to be taken from cells not listed in the -c list. The -n option causes theuse of group 1 neighbors for the list of cells to be traced.

For active calls in the CDMA mode, the measurement request is sent to the Primary celland two Secondary cells. The Primary cell will respond by sending a reply messagecontaining the measured pilot strength to the ECP. This message contains the CDMAneighbor list that includes up to 12 measurements per serving cell.



For CDMA calls, the -c, -f and -n options will be ignored. If the cell is in the middle of aCDMA-to-Analog handoff, hard handoff or primary transfer, and unable to get ameasurement, no measurement will be recorded for this instance. The cell may eitherrespond with a CDMA measurement response message with the field valid=FALSEand measurement data invalid, or no CDMA measurement response at all.

Each measurement is stored in binary form in log files FTRFTRACE1 andFTRFTRACE0 located in the /omp-data/logs/rfct directory. FTRFTRACE1 isalways the active file. When this file reaches a tunable maximum size, it is moved intoFTRFTRACE0. The default for this maximum is to 6MB, at this time. The FTrfdumpcommand is used to dump the data to the standard output device.

The maximum allowable size of the log file may be tuned by editing the value in the file/omp-data/user/etc/rfct.ini. The “ompadmin” users have write permission to this file.

Options

FTrftrace Optional Parameters

-c cells

List of up to 8 cells separated by spaces. Must have at least 1 cell when this option is used.

-d dirnumbers3

List of up to 10 mobile directory numbers each of 1 to 14 digits in length, separated by spaces.Must specify at least one DN.

NOTE:If a non -10 digit DN is specified, which does not appear in the HLR database or VLRdatabase, then the trace is not performed.

-m dnfile1

File containing up to 10 mobile DNs each of 1 to 14 digits in length, listed one per line. Mustspecify at least one DN.

NOTE:If a non -10 digit DN is specified, which does not appear in the HLR database or VLRdatabase, then the trace is not performed.

-h

Print help message.

-i interval

Duration of trace requested in minutes. Minimum is 15, maximum is 240, default is 30.

3 The Multiple DN FAF is required for tracing more than one DN in a session. This feature iscurrently supported for the CDMA cell release (APXDx.xx).



-p period

Polling period in seconds. Minimum is 2, maximum is 60, default is 30. In order to limit themessage traffic, “bandwidth” is defined as the allowable combination of the number of DNsand Polling Periods. The bandwidth is defined by the formula. The available bandwidth at anytime may be obtained by executing FTrftrace -s, which is expressed as the minimum periodsupported for an additional DN. To serve as a guideline, when the periods are the same for allDNs being traced, the Period versus DNs will be the following:

All analog mode calls in a MDN RF Call Trace session must have the same polling period. Ifany analog call has a polling period that is different from any other analog call it can causeerroneous results for all analog DNs in the session, and all subsequent call trace requestrecords for analog calls will indicate the data may be invalid. This data will be formatted forprinting via the FTrfdump UNIX command:

** WARNING! Analog DNs using different polling periods.**

**Data may be invalid!**

-t tag

The up to 8-character tag to identify your trace.

-o4

Real time output to the terminal. Data will also be collected in the files.

-r5

Real-time output in raw mode. Ignored if -o option not used.

-D3

Convert real-time output to dBm. Ignored if -o option not used.

-f

Force measurements even if call is on a cell not in the list.

-s

Status of traces in progress, available bandwidth info will be displayed as the minimum pollingperiod supported for an additional DN. Available only with the CDMA Multiple DN FAF.

Polling Interval Number of DNs





4 This option will not be supported with the CDMA Multiple DN FAF. Instead, the new FTrfdump -F option may be used.

5 This option will not be supported with the CDMA Multiple DN FAF.



-n

Use the neighbor-1 neighbors for the list of cells to be traced for analog mode. Use the MAHOneighbors for the list of mobile measurements. With this option, the -f and -c options areignored.

NOTE:If the command list contains neither the -c, nor the -n options, FTrftrace defaults to the-n option.

-F

Support 3G RFCT optional parameter. To specify the forward supplemental rate. The validrange is 0 to 5.

-R

Support 3G RFCT optional parameter. To specify the reverse supplemental rate. The validrange is 0 to 4.

Examples

FTrftrace -c 24 26 25 2 -d 12345678901 -t mytag -i 20 -p 45FTrftrace -sFTrftrace -c 10 2 106 -d 12345678901234 7085551234FTrftrace -c 12 14 9 -d 1234567890 -i 5 -o -r > file&FTrftrace -c 200 1 77 267 -d 123 -i 15 -p 60 -fFTrftrace -n -m dnfile -i 15 -p 60FTrftrace -d 9185551212 -i 15 -p 60

Files

/omp/bin/FTrftrace/omp-data/logs/rfct/FTRFTRACE0/omp-data/logs/rfct/FTRFTRACE1/omp-data/user/etc/rfct.ini/omp-data/logs/rfct/.rfct_roster

User Environment

The RF Call Trace tools must be executed from the OMP Shell. The user login musthave the UNIX group_id “pace” as enforced by the /etc/group file on the OMP. The usermust also execute the /omp/etc/ompprofile and /omp/etc/ompenv to obtain a consistentenvironment.

Appendix B - FTrfstop(1) 401-612-052, Issue 17


Appendix B - FTrfstop(1)

FTrfstop(1) AUTOPLEX(1000) FTrfstop(1)

Name

FTrfstop - Stop part or all of any running RF Call Trace session.

Synopsis

With CDMA Multiple DN FAF:FTrfstop (-A | -t tag | -d dirnumbers) [-h]

Without CDMA Multiple DN FAF:FTrfstop [-h]

Description

When the CDMA Multiple DN FAF is not active, FTrfstop will halt the running RF CallTrace session, and an entry will be made in the log file indicating the time the trace wasstopped.

With the CDMA Multiple DN FAF, the command is capable of stopping one or moreDNs selectively. The DNs may be specified by the tag or DN. The FTrftrace -scommand may be used in conjunction to examine the status of traces in progress.

This command should be executed on the OMP Shell.

Options

-A

Stop the traces for all DNs in the current session. This option should be used with care as itstops traces for all users sharing the current session.

-t tag

Stop all the DNs associated with this tag.

-d DN1 [DN2..]

Stop the traces for up to 10 specified DN(s) only.

-h

Print the usage message.

Appendix B - FTrfstop(1) 401-612-052, Issue 17


Examples

To stop 3 DNs from a CDMA Multiple DN RF Call Trace session:FTrfstop -d 7085551212 630555121212 567891

To stop all DNs for a given tag from a CDMA Multiple DN RF Call Trace session:FTrfstop -t mytag

To stop all DNs from a CDMA Multiple DN RF Call Trace session:FTrfstop -A

To stop a running RF Call Trace process when CDMA Multiple DN FAF is not active:FTrfstop

User Environment


Appendix C - FTrfclear(1) 401-612-052, Issue 17


Appendix C - FTrfclear(1)

FTrfclear(1) AUTOPLEX(1000) FTrfclear(1)

Name

FTrfclear - Delete log file records for a given trace tag.

Synopsis

FTrfclear -t tag [-f logfile] [-h]

Description

FTrfclear is a tool that scans a binary log file looking for RF Call Trace records thatmatch the specified tag name. All the matched records will then be deleted from the logfile.

FTrfclear will not clear the default log files (FTRFTRACE*) when FTrftrace is running.

Options

FTrfclear Required Parameters

-t tag

The up to 8-character or less trace identifier tag for which call trace records are to be deleted.

FTrfclear Optional Parameters

-f logfile

The binary file to delete call trace records from. If the -f option is not used, the /omp-data/logs/rfct/FTRFTRACE log files will be used by default.

-h

Prints the help message.

Examples

To delete all call trace records that have a tag “tracetst” from the default log files:FTrfclear -t tracetst

To delete all call trace records that have a tag “tracetst” from the binary log file /tmp/logfile:

FTrfclear -t tracetst -f /tmp/logfile

Appendix C - FTrfclear(1) 401-612-052, Issue 17


Files

/omp-data/logs/rfct/FTRFTRACE0/omp-data/logs/rfct/FTRFTRACE1

User Environment


Appendix D - FTrfdump(1) 401-612-052, Issue 17


Appendix D - FTrfdump(1)

FTrfdump(1) AUTOPLEX(1000) FTrfdump(1)

Name

FTrfdump - prints out RF Call Trace records.

Synopsis

FTrfdump [-F] [-t tag] [-d dirnumber] [-f file] [-o outfile] [-D] [-r] [-x] [-h]

Description

FTrfdump is a tool that scans a binary log file looking for RF Call Trace records thatmatch the specified input parameters. For each record match found, FTrfdump willprint the trace data in different formats based on the technology type. The data isarranged in pairs of one request message from CDN and a reply message from Cell.The directory number and message tag form the key to the messages.

The -F option delivers the data in real time mode. For MDNRFCT users, this optionreplaces the -o option of the FTrftrace command.

By default, measurements will be Receive Signal Strength Units (RSSUs) for analog orin Interim Standard 54 Revision B (IS-54B) for TDMA. SDMAC is also provided.

Options

FTrfdump Optional Parameters

-F

Real time output when the trace is active. The user terminates real-time output with aninterrupt signal (usually Control-c or the [Delete] key).

-d dirnumber6

The 1 to14 digit mobile Directory Number (DN) that call trace records are to be printed for. Ifthe -d option alone is specified, all call trace records for this mobile will be printed; if used withthe -t option, all records matching this DN and the tag will be printed.

-f file

The binary file used to dump call trace records. If the -f option is not used, the /omp-data/logs/rfct/FTRFTRACE log files will be searched by default.

6 This option must be used when dumping the trace output of a Multiple DN session, in order togenerate consistent data.



-h

Prints a help message explaining all options to FTrfdump.

-o outfile

May specify a filename to send the output of FTrfdump.

-r

Call trace data is printed in a raw ASCII format.

-t tag

The 8-character or less trace identifier tag for which call trace records are to be printed.

-x

With the -x option, all data for Cell Release 5.1 (and later) will be printed. This option shouldbe used with TDMA traces in order to dump the time slot data.

-D

Signal strength measurements are printed in dBm. Without the -D option, signal strengthmeasurements are in RSSU for analog or in IS-54B for TDMA (default).

The following are the layout of the different message types from FTrfdump:

■ RF Calltrace Locate Request (Type1):type:time:DN:tag:cell:Vrg:Ra:Ts:SAT/DVCC:chnl:ant:sg:DCS:tg:mem:poll:cells:serving:HO:SCM:mcell:carr

■ Location Reply from 3-sector Cell (Type 3):type:cell:time:DN:tag:measurement:O-sg0:A-sg0:B-sg0:G-sg0:O-sg1:A-sg1:B-sg1:G-sg1

■ Location Reply from 6-sector Cell (Type 6):type:cell:time:DN:tag:measurement:O-sg0:A-sg0:B-sg0:G-sg0:D-sg0:E-sg0:Z-sg0:O-sg1:A-sg1:B-sg1:G-sg1D-sg1:E-sg1:Z-sg1:SDMAC:sderr

■ Stop message (Type 2):type:time:DN:tag

■ RF Calltrace AMPS Reply from 6-sector Cell (Type 7):type:cell:time:DN:tag:measurement:O-sg0:A-sg0:B-sg0:G-sg0:D-sg0:E-sg0:Z-sg0:O-sg1:A-sg1:B-sg1:G-sg1D-sg1:E-sg1:Z-sg1:SDMAC:sderr:RCU

■ RF Calltrace TDMA Reply from 6-sector Cell (Type 8):type:cell:time:DN:tag:measurement:#_of_nbr[:cell:paf:DCSID:ECPID:SID:MAHO]*...:m_chnl:m_BER:r_chnl:r_BER:r_FER:SDMAC:sderr

■ RF Calltrace Group 1 Neighbor List (Type 9):type:time:DN:tag:cell:sg:paf:#_OF_nbr[:cell:laf:sg:sub:MFA:HObias]*...

■ RF Calltrace MMAHO List (Type 10):type:time:DN:tag:cell:sg:paf:#_OF_nbr[:cell:laf:cell_CD:sg0_bias:sg1_bias:sg0_VMAC:sg1:_VMAC:sg0_DTH:sg1_DTH:DCSID:ECPID:SID]...



■ CDMA RF Call Trace Request (Type 15):type:time:DN:tag:pri_cell:sec_cell:sec_cell:sec_cell:sec_cell:sec_cell:DCS:tg:mem:SCM:poll:HO:RfRate:RrRate

■ CDMA RF Call Trace Reply (Type 16)type:cell:time:DN:tag:valid:rsn:HO:SCM:freq:seq:ctype:tic:gain:elapsed:#_of_pn[:cell:ECPID:ps:paf:pn:p_grp:chn_elm:chn_elm:chn_elm:p_str:trp_dly:eb_no:keep:]7:tic:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:c_stat:c_stat:c_stat:c_stat:c_stat:c_stat:tic:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:full_wo_err:full_wo_err:full_wo_err:full_wo_err:full_w_err:full_w_err:full_w_err:full_w_err:bad_qual:bad_qual:bad_qual:bad_qual:1/2_frm:1/2_frm:1/2_frm:1/2_frm:1/4_frm:1/4_frm:1/4_frm:1/4_frm:1/8_frm:1/8_frm:1/8_frm:1/8_frm:

■ CDMA 6-way Soft Handoff RF Calltrace Reply (Type 17):8

type:cell:time:DN:tag:valid2:rsn:HO:SCM:freq:seq:ctype:tic_hi:tic_lo:gain:elapsed:#_of_pn[:cell:ECPID:ps:paf:pn:p_grp:chn_elm:chn_elm:chn_elm:p_str:trp_dly:eb_no:keep:]9:tic_hi:tic_lo:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:c_stat:c_stat:c_stat:c_stat:c_stat:c_stat:tic_hi:tic_lo:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:full_wo_err:full_wo_err:full_wo_err:full_wo_err:full_wo_err:full_wo_err:full_wo_err:full_w_err:full_w_err:full_w_err:full_w_err:full_w_err:full_w_err:full_w_err:bad_qual:bad_qual:bad_qual:bad_qual:bad_qual:bad_qual:bad_qual:1/2_frm:1/2_frm:1/2_frm:1/2_frm:1/2_frm:1/2_frm:1/2_frm:1/4_frm:1/4_frm:1/4_frm:1/4_frm:1/4_frm:1/4_frm:1/4_frm:1/8_frm:1/8_frm:1/8_frm:1/8_frm:1/8_frm:1/8_frm:1/8_frm:gen:ectf:ectf:ectf:ectf:ectf:ectf:iorf:iorf:iorf:iorf:iorf:iorf10[:board:board:board:board:board:board:_:_:_:_:_:_]:f_smv_mode:r_smv_mode

■ CDMA 6-way Soft Handoff RF Calltrace Reply (Type 20):11 12

type:cell:time:DN:tag:valid:rsn:HO:SCM:freq:seq:ctype:tic_hi:tic_lo:gain:elapsed:#_of_pn[:cell:ECPID:ps:paf:pn:p_grp:chn_elm:chn_elm:chn_elm:p_str:trp_dly:eb_no:keep:]*:tic_hi:tic_lo:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:c_stat:c_stat:c_stat:c_stat:c_stat:c_stat:tic_hi:tic_lo:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:full_wo_err:full_wo_err:full_wo_err:full_wo_err:full_wo_err:full_wo_err:full_wo_err:full_w_err:full_w_err:full_w_err:full_w_err:full_w_err:full_w_err:full_w_err:bad_qual:bad_qual:bad_qual:bad_qual:bad_qual:bad_qual:bad_qual:1/2_frm:1/2_frm:1/2_frm:1/2_frm:1/2_frm:1/2_frm:1/2_frm:1/4_frm:1/4_frm:1/4_frm:1/4_frm:1/4_frm:1/4_frm:1/4_frm:1/8_frm:1/8_frm:1/8_frm:1/8_frm:1/8_frm:1/8_frm:1/8_frm:gen:ectf:ectf:ectf:ectf:ectf:ectf:iorf:iorf:iorf:iorf:iorf:iorf:#_of_rates[:ectcs:num_frm]13[:rev_sup:rev_sup:rev_sup:rev_sup:rev_sup:rev_sup:

7 Null values for any of the fields will be represented as “_”.8 Null values for any of the fields will be represented as “_”.9 Null values for any of the fields will be represented as “_”.10 Output optionally for all 2G calls and also on 3G calls with cell releases<=R19.11 Null values for any of the fields will be represented as “_” or N/A.12 This message is only applicable to 3g1x data calls in ECP releases 18 and 19.



rev_sup_afs:rev_sup_tfn]14[:rev_ebno:rev_ebno:rev_ebno:rev_ebno:rev_ebno:rev_ebno]:_:_:_:_:_

■ CDMA 6-way Soft Handoff RF Call Trace Reply (Type 20):15 16

type:cell:time:DN:tag:valid:rsn:HO:SCM:freq:seq:ctype:tic_hi:tic_lo:gain:elapsed:#_of_pn[:cell:ECPID:ps:paf:pn:p_grp:chn_elm:chn_elm:chn_elm:p_str:trp_dly:eb_no:keep:]*:tic_hi:tic_lo:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:c_stat:c_stat:c_stat:c_stat:c_stat:c_stat:tic_hi:tic_lo:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:full_wo_err:full_wo_err:full_wo_err:full_wo_err:full_wo_err:full_wo_err:full_wo_err:full_w_err:full_w_err:full_w_err:full_w_err:full_w_err:full_w_err:full_w_err:bad_qual:bad_qual:bad_qual:bad_qual:bad_qual:bad_qual:bad_qual:1/2_frm:1/2_frm:1/2_frm:1/2_frm:1/2_frm:1/2_frm:1/2_frm:1/4_frm:1/4_frm:1/4_frm:1/4_frm:1/4_frm:1/4_frm:1/4_frm:1/8_frm:1/8_frm:1/8_frm:1/8_frm:1/8_frm:1/8_frm:1/8_frm:gen:ectf:ectf:ectf:ectf:ectf:ectf:iorf:iorf:iorf:iorf:iorf:iorf:#_of_rates17[:ects:#_of_f_rates:num_frm]18[:rev_sup:rev_sup:rev_sup:rev_sup:rev_sup:rev_sup:rev_sup_afs:rev_sup_tfn]19[:rev_ebno:rev_ebno:rev_ebno:rev_ebno:rev_ebno:rev_ebno]:ltu_rcv:ltu_good:20[fsch_m_frm:]21[rsch_m_frm:]22[fsch_dtx_frm:][rsch_dtx_frm:]ancr_cell:ancr_paf:f_smv_mode:r_smv_mode

■ CDMA 6-way Soft Handoff RF Call Trace Reply (Type 20):23 24

type:cell:time:DN:tag:valid:rsn:HO:SCM:freq:seq:ctype:tic_hi:tic_lo:gain:elapsed:#_of_pn[:cell:ECPID:ps:paf:pn:p_grp:chn_elm:chn_elm:chn_elm:p_str:trp_dly:eb_no:keep:]*:tic_hi:tic_lo:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:m_ftf:c_stat:c_stat:c_stat:c_stat:c_stat:c_stat:tic_hi:tic_lo:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:m_rtf:full_wo_err:full_wo_err:full_wo_err:full_wo_err:full_wo_err:full_wo_err:full_wo_err:full_w_err:full_w_err:full_w_err:full_w_err:full_w_err:full_w_err:full_w_err:bad_qual:bad_qual:bad_qual:bad_qual:bad_qual:bad_qual:bad_qual:1/2_frm:1/2_frm:1/2_frm:1/2_frm:1/2_frm:1/2_frm:1/2_frm:1/4_frm:1/4_frm:1/4_frm:1/4_frm:1/4_frm:1/4_frm:1/4_frm:1/8_frm:1/8_frm:1/8_frm:1/8_frm:

13 Repeated #_of_rates.14 Repeated #_of_rates.15 Null values for any of the fields will be represented as “_” or N/A.16 This message is only applicable to 3g1x data calls in ECP release >=20.17 In cell releases <20, #_of_f_rates is same as #_of_rates so it is always set to ‘_’. In cell release

>=20, #_of_f_rates will be repeated with the same value.18 Repeated #_of_rates.19 Repeated #_of_rates.20 Repeated #_of_f_rates.21 Repeated #_of_rates.22 Repeated #_of_f_rates.23 Null values for any of the fields will be represented as “_” or N/A.24 This message is only applicable to 3g1x data calls in ECP release >=20.



1/8_frm:1/8_frm:1/8_frm:gen:ectf:ectf:ectf:ectf:ectf:ectf:iorf:iorf:iorf:iorf:iorf:iorf:#_of_rates25[:ects:#_of_f_rates:num_frm]26[:rev_sup:rev_sup:rev_sup:rev_sup:rev_sup:rev_sup:rev_sup_afs:rev_sup_tfn]27[:rev_ebno:rev_ebno:rev_ebno:rev_ebno:rev_ebno:rev_ebno]:ltu_rcv:ltu_good:28[fsch_m_frm:]29[rsch_m_frm:]30[fsch_dtx_frm:][rsch_dtx_frm:]ancr_cell:ancr_paf:f_smv_mode:r_smv_mode:[num_fsch_softer:]:[num_dtx_fsch_softer]:num_fwd_entries[:startime:frm_trans:frm_req:msc_asl:fsch_smpl_softr_flag:first_pilot_pn:cellid:first_paf:RC:second_paf:second_pilot_pn:simul:fwd_rvs_flag:aloc_rate:req_rate:aloc_flag:blk_rate_limit_ind:fsch_cts_denied:early_rel]31[:avg_ects_softer]:num_rvs_entries[:startime:act_dur:RC:fwd_rvs_flag:aloc_rate:req_rate:aloc_flag:blk_rate_limit_ind:early_rel:]:num_anchor_setup:num_anchor_entries[:timestamp:msc_as1:pilot_pn:cellid:paf]

Field explanations::

25 In cell releases <20, #_of_f_rates is same as #_of_rates so it is always set to ‘_’.26 Repeated #_of_rates.27 Repeated #_of_rates.28 Repeated #_of_f_rates.29 Repeated #_of_rates.30 Repeated #_of_f_rates.31 Repeated #_of_rates.

type - number indicating the type of the call trace message.

time - a 12-digit number showing the date and time the message waslogged, in the format mmddyyhhmmss.

cell - the cell sending the message

cells - all cells included in the locate request call trace session.

DN - the Directory Number (up to 14 digits) of the call trace.

tag - the tag associated with the call trace (if any).

Vrg - the Voice Radio Group of the radio serving the call.

Ra - the radio number serving the call.

Ts - Indicates the timeslot of the TDMA radio.



SAT/DVCC - the Supervisory Audio Tone for the radio serving the call or theDigital Verification Color Code. If the time slot is0 (AMPS) thenthis field is SAT. Otherwise, (TDMA) this field is DVCC.

chnl - the radio channel number serving the call.

ant - the antenna face serving the call, where 0=Omni, A=Alpha,B=Beta, G=Gamma, D=Delta, E=Epsilon, Z=Zeta, or I=Invalid

paf - the physical antenna face serving the call, where 0=Omni,1=Alpha, 2=Beta, 3=Gamma, 4=Delta, 5=Epsilon, and 6=Zeta.

laf - the logical antenna face as a hex. number where bit 3 is theserver group and bits 0-2 is the face as follows: 0=Omni,1=Alpha, 2=Beta, 3=Gamma, 4=Delta, 5=Epsilon, and 6=Zeta.

sg - the logical Server Group serving the call.

DCS - the Digital Cellular Switch serving the call.

tg - the cell site trunk group serving the call.

mem - the cell trunk member serving the call.

poll - the signal poll count for the call trace session.

serving - indicates if the serving cell was included in the call trace, 1=validor 0=invalid cell

valid - Flag that indicates if some of the data is invalid (0=invalid or1=valid).

measurement - a character indicating the units. The cell signal measurementsare made in R=RSSUs, I=IS-54B, or d=dBm.

SCM - Station Class Mark

mcell - the Microcell number (1-6).

carr - TDMA carrier number (1-2).

SDMAC - Stored Dynamic Mobile Attenuation Code (SDMAC)

sderr - error status of SDMAC. The error status can be interpreted asfollows:0 = The measurement is valid1 = Signal Strength Estimate is not valid2 = Did not receive SDMAC from Voice Radio3 = Errors 1 and 2

X-sg Y - the signal strength measurement for logical face. Where X isOmni, Alpha, Gamma, etc. and Y is 0 for server group 0 and 1 forserver group 1.



RCU - the Radio Control Unit serving the call.

MAHO - the signal strengths of the MAHO neighbors as measured by themobile.

#_of_nbr - the number of entries in the neighbor list.

m_chnl - the signal strength measured from the mobile serving the call.

m_BER - the Bit Error Rate (BER) measured from the mobile serving thecall.

r_chnl - the signal strength as measured from the Digital Radio Unit(DRU) serving the call.

r_BER - the Bit Error Rate (BER) measured from the Digital Radio Unit(DRU) serving the call.

r_FER - the Frame Error Rate (FER) measured from the Digital RadioUnit (DRU) serving the call.

sub - the sub group identifying the neighbor priority.

MFA - indicates if all responding neighbor faces may be considered ashandoff candidates or only the strongest responding face.y=yes, all responding facesn=no, only strongest face

Hobias - indicates the bias value (hysteresis) to be used forhandoffshandoffs.

cell_CD - indicates the configuration of the neighbor cell site associatedwith the cell site.1=single omnidirectional2=single sectorized3=server group 0 Omni server group 1 Omni4=server group 0 sectorized server group 1 Omni5=server group 0 sectorized server group 1 sectorized6=server group 0 Omni server group 1 sectorized

sgX_bias - specifies the server group X bias value from the serving cell’slogical face to the server group X of the neighbor’s physical face.Where X is the server group number (0 or 1).

sgX_VMAC - specifies the nominal attenuation code assigned to mobile unitsserved by this server group X face for a Class IV mobile unit.Where X is the server group number (0 or 1).



sgX_DTH - the Server Group X Decision Threshold field. This fieldrepresents one of the following when the handoff candidate faceis the primary server group (for a dual cell or nondual cell).Dual Cell: This field represents the hysteresis adjusted primarythreshold for handoff.Nondual Cell: This field represents the handoff interferenceprotection threshold, which may be higher than the setupinterference protection threshold.

DCSID - the DCS number serving the neighbor cell. This is one part of theunique identificationof a system known as the Extended SystemID (ESID).

ECPID - the ECP number serving the neighbor cell. This is one part ofthe unique identification of a system known as the ExtendedSystem ID (ESID).

SID - the system number serving the neighbor cell. This is one part ofthe unique identification of a system known as the ExtendedSystem ID (ESID).

pri_cell - the primary cell site number in a CDMA handoff (hard, soft,semi-soft, or softer)(1-384).

sec_cel - the secondary cell site number in a CDMA soft handoff(secondary 1 or 2). If there are no secondary cells involved in thesoft HO then this value will be zero (1-384).

valid - Flag that indicates if some of the data is invalid (1 - invalid or 0 -valid).

HO - indicates if the call was in a handoff during the signalmeasurement period, 1=in a handoff or 0=not in a handoff.

freq - assigned CDMA frequency (16 bits).

rsn - Reason why some data is invalid: _ = all data valid 0x00 = data not valid -- error 0x01 = some data may be valid 0x02 = all data collected and valid 0x04 = mobile HOTRIG data missing 0x08 = mobile PARMS data missing 0x10 = primary CE data missing 0x20 = secondary #1 CE data missing 0x40 = secondary #2 CE data missing 0x80 = RFCT received-not TALK state0x100 = secondary #3 CE data missing0x200 = secondary #4 CE data missing0x400 = secondary #5 CE data missing



seq - CDMA traffic sequence number (4 bits) or_for not applicable.

ctype - CDMA vocoder type:0 = 8kbps/voice1 = 13kbps/voice2 = EVRC/voice3 = 8kbps/markov4 = 13kbps/markov5 = 9.6Kbps/Async6 = 14.4Kbps/Async7 = 9.6Kbps/Fax8 = 14.4Kbps/Fax9 = 8kbps/CMLT10 = 13kbps/CMLT11= 9.6kbps/IP12=14.4kbps/IP13=9.6kbps/CDPD14=14.4kbps/CDPD15=9.6kbps/Fax (Analog)16=14.4kbps/Fax (Analog)17=3G1X/IP18=3G1X/CDPD19=SMV999 = INVALID

tic - CDMA Tick ID (GPS time reference)(16 bits)

tic_hi - CDMA Tick ID (GPS time reference) (High order 32 bits inhexadecimal of the tic or_if N/A). Derived from mobile HOTRIGdata. Disabled for r18 3G calls is now re-enabled in r19

tic_lo - CDMA Tick ID (GPS time reference) (Low order 32 bits inhexadecimal of the tic or_if N/A). Derived from mobile HOTRIGdata. Disabled for r18 3G calls is now re-enabled in r19

gain - CDMA primary digital gain (8 bits, DGU) or_if N/A.

elapsed - CDMA elapsed time (in seconds).

#_of_pn - Number of pilot data records that follow (0-8).

ps - Pilot sets:P - primary cellS1 - first secondary cellS2 - second secondary cellS3 - third secondary cellS4 - fourth secondary cellS5 - fifth secondary cellC - candidate cellRC - null



pn - Pilot Pn (9 bits)

p_grp - Priority Group (2 bits)

chn_elm - Channel element of the CCU

p_str - Pilot strength (6 bits in db) or_if N/A. Derived from mobileHOTRIG data.

trp_dly - R-trip delay (16 bits decimal in microsecond) or_if N/A. Derivedfrom mobile HOTRIG data. Earlier disabled for 3G calls is nowre-enabled.

eb_no - Eb/No (in db with resolution of .01) or_if N/A. Value displayed isper antenna path. EbNo for 3G calls is now reported correctly.

keep - Keep indicator (1-yes, 0-no, or _). Derived from mobile HOTRIGdata.

m_ftf - Mobile forward traffic frame count (32 bits) or_. Derived frommobile PARMS data. Ordered as Full-rate, dim-burst half,quarter, and eight, blank-burst, half-rate, quarter rate, eight rate,full-rate with error and bad frames. First response at start of callor Rftrace session should be discarded. Earlier disabled for 3Gcalls is now re-enabled.

c_stat - Cell forward traffic frame statistic for full, half, quarter, and eighthsignaling rate frame and Dim & burst frame counts (16 bits).

m_rtf - Mobile reverse traffic frame count (32 bits) or_. Derived frommobile PARMS data. Ordered as Full-rate, dim-burst half,quarter, and eight, blank-burst, half-rate, quarter rate, eight rate.First response at start of call or Rftrace session should bediscarded. Earlier disabled for 3G calls is now re-enabled.

full_wo_err - Full rate without errors for the cell reverse traffic frame statistic.One for the Bfr-Frm-Sel of the P, S1, S2, S3, S4, S5 cells andone for the Aftr-Frm-Sel for the primary cell (16 bits).

full_w_err - Full rate with bit errors for the cell reverse traffic frame statistic.One for the Bfr-Frm-Sel of the P, S1, S2, S3, S4, S5 cells andone for the Aftr-Frm-Sel for the primary cell (16 bits).

bad_qual - Quality insufficient for the cell reverse traffic frame statistic. Onefor the Bfr-Frm-Sel of the P, S1, S2, S3, S4, S5 cells and one forthe Aftr-Frm-Sel for the primary cell (16 bits).

1/2_frm - Half-rate frames for the cell reverse traffic frame statistic. One forthe Bfr-Frm-Sel of the P, S1, S2, S3, S4, S5 cells and one for theAftr-Frm-Sel for the primary cell (16 bits).



1/4_frm - Quarter-rate frames for the cell reverse traffic frame statistic.One for the Bfr-Frm-Sel of the P, S1, S2, S3, S4, S5 cells andone for the Aftr-Frm-Sel for the primary cell (16 bits).

1/8_frm - Eighth-rate frames for the cell reverse traffic frame statistic. Onefor the Bfr-Frm-Sel of the P, S1, S2, S3, S4, S5 cells and one forthe Aftr-Frm-Sel for the primary cell (16 bits).

gen - generation type. (0-2G, and 1-3G)

ectf - average forward fundamental transmit power for the call (ECTF)per HO leg. (Floating point number).

iorf - average total forward transmit power for the call (ECTF) per HOleg. (Floating point number).

#_of_rates - number of Reverse Rate.

#_of_f_rate - number of Forward Rate. If this is not a 3G enhanced call (cell<r20), this value will be “_”.

etcs - forward IS-2000 supplemental channels information - AverageECTS. (Floating point number).

iors - forward IS-2000 supplemental channels information -AverageIORS. (Floating point number).

num_frm - Forward IS-2000 supplemental channels information - Number ofFrames.

rev_sup - Reverse IS-2000 supplemental channel frame error rateinformation - Before Frame Selector per Handoff leg.Incremental decimal, for 2x, 4x, 8x, 16x.

rev_sup_afs - Reverse IS-2000 supplemental channel frame error rateinformation - After Frame Selector per Handoff leg. Incrementaldecimal, for 2x, 4x, 8x, 16x.

rev_sup_tfn - Reverse IS-2000 supplemental channel frame error rateinformation - Total Frame Number at Primary. Incrementaldecimal , for 2x, 4x, 8x, 16x.

rev_ebno Reverse - IS-2000 supplemmental channel Eb/No information per Handoffleg. Displayed as per antenna path in resolution of 0.01 db. Nullvalues may be_or N/A.



RfRate - Requested forward supplemental rate, default to 0 (see Ftrftraceoptions).0 - none requested in commmand line1 - 2x rate2 - 4x rate3 - 8x rate4 - 16x rate5 - 32x rate

RrRate - Requested reverse supplemental rate, default to 0 (see Ftrftraceoptions).0 - none requested in commmand line1 - 2x rate2 - 4x rate3 - 8x rate4 - 16x rate5 - 32x rate

board - Board type of a 2G call.1 indicates call is on 3G board.0 indicates call is on 2G board._ for 3G voice call or legs not involved in a 2G call.

Itu_rcv - incremental mobile reported SCH0 LTUs received. Derived frommobile PARMS data.

Itu_good - incremental mobile reported SCH0 Good LTUs received.Derived from mobile PARMS data.

fsch_m_frm - incremental mobile reported number of F-SCH frames in thefollowing order: 2X, 4X, 8X, 16X, 32X. Derived from mobilePARMS data.

rsch_m_frm - incremental mobile reported number of R-SCH frames in thefollowing order: 2X, 4X, 8X, 16X, 32X. Derived from mobilePARMS data.

fsch_dtx_frm - incremental number of DTX frames of F-SCH in the followingorder: 2X, 4X, 8X, 16X, 32X. Derived from mobile PARMS data.

fsch_dtx_frm - incremental number of DTX frames of R-SCH in the followingorder: 2X, 4X, 8X, 16X, 32X. Derived from mobile PARMS data.

ancr_cell - forward SCH anchor cell number.

ancr_paf - forward SCH anchor physical antenna face.

f_smv_mode - forward SMV mode.

r_smv_mode - reverse SMV mode.



num_fsch_softer Number of non-DTX F-SCH frames in softer handoff of rate R

num_dtx_fsch_softer Number of DTX F-SCH frames in softer handoff of rate R

num_fwd_entries Number of valid entries in the forward burst table

startime Start time of the burst. It is the GPS time in 20ms unit.

frm_trans Number of frames transferred

frm_req Number of frames requested. In the forward direction, thisnumber could be 0,1, 2, 3, 4, 5, 6, 7, 8,16, 32, 64, 96, 128, 0r256. In the reverse direction, this number could be 0 (no burst)or 32767 (infinite).

msc_asi MSC number

fsh_smpl_softr_flag F-SCH transfer mode

0-undefined

1-simplex mode

2-softer mode

first_pilot_pn pn offset of the first softer leg

cellid Cell number

first_paf Face of the first softer leg

RC Radio configuration

second_paf Face of the second softer leg

second_pilot_pn pn offset of the second softer leg

simul Simultaneous FCH and SCH transfer

0-SCH only

1-FCH and SCH

fwd_rvs_flag Forward or Reverse burst

0-reverse

1-forward

aloc_rate Allocated rate

req_rate Requested rate



aloc_flag allocation flags

0-undefined

1-new burst

2-continuation

blk_rate_limit_ind Resource black/rate limit indicator

0-undefined

1-DCS backlog is not large enough to warrent a higher rate

2-internal error at the secondary leg

3-power/RSSI limitation

4-power overload

5-processor overload

6-walsh code limitation

7-packet pipe limitation

8-channel fragment limitation

9-mobile requested rate less than the system maxrate

10-moble maxrate less than the system maxrate

11-exceed maximum number of R-SCH soft handoff legs

12-can not grant the maxrate because it is a continuation

fsh_cts_denied F-SCH continuation denied reason

0-Undefined

1-To allocate a higher rate

2-Preempted by other user

3Request arrives out of the scheduling window

4-No backlog



early_rel Early release reason

0-Undefined

1-Power overload

2-Revoking of the walsh code

3-Packet pipe contention

4-Skew group contention

5-Channel fragment contention

6-Anchor transfer

7-Soft/softer leg added

8-Soft Handoff anchor drop

9-Semi-soft handoff

10-Primary transfer

11-Rate upgrade

12-Rate downgrade

13-Mobile initiated release (SCRM 0)

14-Mobile drop call

15-DCS initiated

16-No response from mobile

17-Internal error

18-Secondary leg release

avg_ects_softer Forward average transmit power for the F-SCH for each burstrate R during the time of the softer bursts

num_rvs_entries Number of valid entries in the reverse burst table

num_anchor_setup Number of anchor setup happened during the polling interval

num_anchor _entries Number of valid entries in the anchor history table

timestamp Time of the anchor transfer. It is the GPS time in 20ms unit.

pilot_pn Pn offset of the new anchor

paf Face of the anchor

[ ]... - Indicate that the data contained within the brackets are repeatedseveral times, one for each entry in the neighbor list (#_of_nbr),pilot list (#_of_pn), or rate list (#_of_rates, #_of_frates). Formessage types 17 and 20 items are ordered by pilot PN P, S1,S2, S3, S4, S5



Examples

To print all AMPS/TDMA call trace records for a recent cell release (5.1 or later) for DN312-867-5309 from the default log files in real time mode, when trace is running:

FTrfdump -x -d 3128675309 -F

NOTE:With the -x option, all data for Cell Release 5.1 (and later) will be printed.

To print all call trace records for DN 312-867-5309 from the default log files in real timemode, when trace is running:

FTrfdump -d 3128675309 -F

To print all call trace records for DN 312-867-5309 and send the output to a file nameddump.out:

FTrfdump -d 3128675309 -o dump.out

To print all call trace records for DN 312-867-5309 that have a tag of tracetst:FTrfdump -d 3128675309 -t tracetst

To print all AMPS/TDMA call trace records for a recent cell release (5.1 or later) for DN312-867-5309 that have a tag of tracetst with SDMAC and SCM:

FTrfdump -x -d 3128675309 -t tracetst

To print all call trace records for DN 312-867-5309 from the binary file /tmp/logfile andhave the signal strength measurements in dBm:

FTrfdump -f /tmp/logfile -D -d 3128675309

Files

/omp/bin/FTrfdump/omp-data/logs/rfct/FTRFTRACE1/omp-data/logs/rfct/FTRFTRACE0

User Environment


lucent call trace.pdf

Documents

lucent technologiesunpublished

interference information

correctthe interference

network charges

united states

unauthorized access

applicable agreementscopyright

applicable tariffs