Sie sind auf Seite 1von 72

Flexent/AUTOPLEX

Wireless Networks
RF Call Trace
Optional Feature Description
Release 21.0

401-612-052
Issue 17
August 2003
Lucent Technologies - Proprietary
This document contains proprietary information of
Lucent Technologies and is not to be disclosed or used except in
accordance with applicable agreements
Copyright 2003 Lucent Technologies
Unpublished and Not for Publication
All Rights Reserved

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 in
any fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts, or licensing, without
the 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 are
designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment
generates, uses, and can radiate radio frequency energy, and if not installed and used in accordance with the documentation, may cause harmful interference to
radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct
the 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 make
any 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 the
documentation 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 Wireless
Networks System Documentation CD-ROM or documentation web site at https://wireless.support.lucent.com/amps/rls_info/rls_doc/cd_docs/.

Lucent Technologies - Proprietary


See Notice on first page

Contents

401-612-052, Issue 17

Contents

1.

2.

3.

4.

Page

Introduction

Reason for Reissue

Historical Record of Revisions

Intended Audience

Availability

Supported Technologies

HLR Configurations

Software Requirements

Hardware Requirements

Benefits

RFCT CCU Changes to Support 3G-IX HSPD

Improved RF Call Trace for 3G-1X HSPD

Enhanced RF Call Trace for 3G-1X Calls

Feature Description

RF Call Trace Data Collection

AMPS Mode

MSC OA&M Support for 384 Cells

TDMA Mode

Increased TDMA MAHO List Feature

RF Call Trace for Dual-Mode Mobiles (DMRFCT)

CDMA Mode

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)

19

August 2003

Lucent Technologies Proprietary


See notice on first page

Page iii

Contents

401-612-052, Issue 17

Contents

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 FeatureImpact on RF Call Trace

23

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

24

Stop Indicator

24

Improved RF Call Trace for 3G-1X HSPD

25

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

7.

8.

Subscriber Perspective

30

Service Provider Perspective

30

Caveats

30

CDMA IMSI

30

RFCT for Dual Mode

31

Multiple DN RFCTB

31

Basic RFCT for 3G-1X HSPD

31

Feature Implementation

Page iv

32

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

32

Improved RF Call Trace for 3G-1X HSPD

32

Enhanced RF Call Trace for 3G-1X Calls

33

Lucent Technologies Proprietary


See notice on first page

August 2003

Contents

401-612-052, Issue 17

Contents
9.

10.

11.

11.

11.

Page

Supplemental Information

34

Abbreviations

34

References

36

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

Appendix A - FTrftrace(1)

39

Name

39

Synopsis

39

Description

39

Options

40

Examples

42

Files

42

User Environment

42

Appendix B - FTrfstop(1)

43

Name

43

Synopsis

43

Description

43

Options

43

Examples

44

User Environment

44

Appendix C - FTrfclear(1)

August 2003

45

Lucent Technologies Proprietary


See notice on first page

Page v

Contents

401-612-052, Issue 17

Contents

11.

Page
Name

45

Synopsis

45

Description

45

Options

45

Examples

45

Files

46

User Environment

46

Appendix D - FTrfdump(1)

47

Page vi

Name

47

Synopsis

47

Description

47

Options

47

Examples

62

Files

62

User Environment

62

Lucent Technologies Proprietary


See notice on first page

August 2003

401-612-052, Issue 17

Figure
A.

Page
21

MDN RFCT Bandwidth formula

August 2003

Lucent Technologies Proprietary


See notice on first page

Page vii

401-612-052, Issue 17

Figure

Page viii

Page

Lucent Technologies Proprietary


See notice on first page

August 2003

401-612-052, Issue 17

Table
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Page

RF Call Trace Availability


Mobile Forward Traffic Frame Count Definitions - Voice
Mobile Retrievable Parameters for Reverse Traffic Channels
Mobile Reverse Traffic Frame Count Definitions - Markov
Primary Cell Mapping for Mobile Received Markov Statistics on the Forward Link
Mobile Reverse Traffic Frame Count Definitions - Markov
Mobile Forward Traffic Frame Count Definitions - Markov
Minimum Equivalent Polling Interval
2G/3G Voice RFCT Capabilities Across Different Software Releases
3G-1X HSPD RFCT Capabilities

August 2003

Lucent Technologies Proprietary


See notice on first page

2
11
12
15
15
17
17
20
28
28

Page ix

401-612-052, Issue 17

Table

Page x

Page

Lucent Technologies Proprietary


See notice on first page

August 2003

Introduction

401-612-052, Issue 17

1. Introduction
This document describes the Radio Frequency (RF) Call Trace optional feature of
Flexent/AUTOPLEX wireless networks. This document provides the following
information:

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 on
page 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 who
implement or maintain the RF Call Trace feature for the Flexent/AUTOPLEX wireless
networks.

August 2003

Lucent Technologies Proprietary


See notice on first page

Page 1

Availability

401-612-052, Issue 17

2. Availability
Refer to the following table for availability:
Table 1.

RF Call Trace Availability


Feature

ECP Release

RF Call Trace

4.1 (or later) and Series II Cell


Release

RF Call Trace for the


AMPS/TDMA
Dual-Mode Mobiles

6.1 (or later) and Series II Cell


Release 5.1 (or later)

RF Call Trace for the


AMPS/CDMA
Dual-Mode Mobiles

7.0 (or later) and Series II Cell


Release 6.0 (or later)

Notes

The default signal strength


measurements of a TDMA
mobile are in IS-54B units. The
option of using dBm is
supported.

Enhanced RF Call
10.0/CDMA Release 5.0
Trace/Markov - Phase 2 (or later)
CDMA Multiple DN

11.0/CDMA Release 6.0 and


Series II Cell CDMA Release
11.0 (or later)

Migration from the ECP


to the OMP

11.0/CDMA Release 6.0 (or


later)

CDMA Adding and


Deleting DN(s) during a
RF Call Trace session
enhancement

5.0/CDMA Release 15.0 and


Series II Cell CDMA Release
13.0 (or later)

15 Digit DN

16.0

Increased TDMA
MAHO List

16.1

MSC OA&M Support for


384 Cells

17.0 (or later)

Basic RF Call Trace for


3G-1X HSPD

18.0 (or later)

Page 2

This feature is for 3G data that is


supplemental in R18.0. This
feature is an enhancement of the
existing 2G Radio Frequency Call
Trace (RFCT) [Feature
Identification (FID) # 2137.10].

Lucent Technologies Proprietary


See notice on first page

August 2003

Availability

Table 1.

401-612-052, Issue 17

RF Call Trace Availability (Continued)


Feature

ECP Release

Notes

Improved RF Call for


3G-1X HSPD

20.0 (or later)

The Improved RF Call for 3G-1X


HSPD feature (FID #2137.4)
provides additional 3G-1X HSPD
RF Call Trace relative to Basic
RF Call Trace for 3G-1X HSPD
(FID #2137.3).

Enhanced RF Call
Trace for 3G-1X Calls

21.0 (or later)

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 Release
20.0 (or later) must be installed.
For Enhanced RF Call Trace for 3G-1X Calls, ECP Release 21.0 (or later) must be
installed.

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

August 2003

Lucent Technologies Proprietary


See notice on first page

Page 3

Benefits

401-612-052, Issue 17

3. Benefits
When a mobile is operating in the AMPS mode, the RF Call Trace feature allows a
system operator to make periodic signal strength measurements on up to ten Directory
Numbers (DNs) in a given cluster of up to eight cell sites or the neighbor-1 neighbors of
the serving cell.
NOTE:
Only mobiles that are on a CDMA cell release cell (APXDx.xx) can trace multiple DNs
on their AMPS calls.
When a mobile is operating in TDMA mode, the periodic measurements on a specified
single DN are made by the mobile of the Mobile Assisted Handoff (MAHO) neighbors of
the serving face.
For CDMA mode, mobiles report signal strength of pilots in the active set and candidate
list. The maximum number of active members is six, and the maximum number of
candidate members is five. However, the initial release of CDMA limits the active set to
three.
For all call modes, AMPS, TDMA, or CDMA, the operator can also specify the periodic
measurement interval and the duration of the call trace for signal strength
measurements.
For AMPS and CDMA modes, the CDMA Multiple DN feature allows up to ten DNs to
be traced during a single session.
NOTE:
Only mobiles that are on a CDMA cell release cell (APXDx.xx) can trace multiple DNs.
Users of the CDMA Adding and Deleting DNs during a RF Call Trace enhancement can
add and delete DN(s) from a RF Call Trace session without having to interrupt the
session.
NOTE:
Only mobiles that are on a CDMA cell release cell can trace multiple DNs.

RFCT CCU Changes to Support 3G-IX HSPD


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

Page 4

Lucent Technologies Proprietary


See notice on first page

August 2003

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 and
Radio Frequency (RF) performance engineers with measurements to optimize voice
and data calls. New power measurements include the sector transmit power (Ior)
referenced to the pilot power for the forward direction and the Fundamental and
Supplemental bit energy (EbNo) for the reverse direction. Newly provided frame counts
are the forward and After Frame Selection (AFS) reverse supplemental channel null
frames (DTX frames), and the mobile reported supplemental channel frames and
Logical Transmission Unit (LTU) packet statistics.
In addition, previously disabled mobile-reported data for pilot strengths and mobile
frame 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 and
RF performance engineers measurements to optimize voice and data calls. New frame
counts include the forward supplemental channel null frames (DTX frames) used in the
Ects calculation for the interval for each burst rate when the Forward Supplemental
Channel (F-SCH) is in softer hand-off, and the number of DTX F-SCH frames for each
burst rate when the F-SCH is in softer hand-off.

4. Feature Description
The Radio Frequency (RF) Call Trace (RFCT) optional feature provides the system
operator 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 as
measured on all antenna faces of the cell sites included in a study. The data collected is
correlated with the measurements recorded at the mobile unit by means of the System
Access Monitor (SAM) recorder.
System operators can use these tools to analyze the mobile RF environment and
fine-tune system parameters relating to handoffs and interference. An RF Call Trace
study can be executed while a mobile is driving through the system.
The following features affect certain RF Call Trace users:

August 2003

AMPS Mode on page 6

CDMA RF Call Trace (CDMARFCT) on page 19

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


page 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

Lucent Technologies Proprietary


See notice on first page

Page 5

Feature Description

401-612-052, Issue 17

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 overload


conditions (Release 21.0 and later releases)

RF Call Trace Data Collection


When a secondary CDMA Cluster Controller (CCC) receives a request from the
primary CCC to collect data for RF Call Trace, the secondary CCC checks its own CCC
Overload Status. If the CCC is in overload, the request is discarded. Similarly, if a
Radio Cluster Controller (RCC), Time Division Multiplex (TDM) Bus Control Channel, or
primary CCC are in overload, RF Call Trace collecting, storing, and reporting of data is
not performed.
NOTE:
Overload control is applied to both FID 5042.6, AUTOPLEX Series II Traffic Overload
Control (Part 1) and FID 5042.7, FLEXENT Traffic Overload Control (Part 1).
For details on how the Flexent/AUTOPLEX system handles overload conditions, see
401-610-009, System Capacity Monitoring and Engineering Guidelines.

AMPS Mode
When the RFCT feature is active, the Mobile Switching Center (MSC) periodically
sends an RF Call Trace Location Request messagespecifying the voice channel
serving the mobileto the cell sites. These cells are typically the serving cell and its
neighbors.
Upon receipt of an RF Call Trace Location Request message, the cell tunes its locate
radio to the specified voice channel, measures the signal quality, and detects
Supervisory Audio Tone (SAT) on each of its equipped faces. Rather than applying the
normal signal strength adjustment rules, the cell adjusts each location measurement
only by the per-cell frame gain differential.
The cell applies the normal SAT detect rules. That is, if no SAT, wrong SAT, or multiple
SATs 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 specified
DN is active on a call.
The cell then returns the Location Reply message, containing the adjusted signal
strength measurements, to the requesting process in the MSC. The MSC logs the

Page 6

Lucent Technologies Proprietary


See notice on first page

August 2003

Feature Description

401-612-052, Issue 17

replies for later processing. If the call is in the process of handoff at the time of
measurement, 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 signal
strengths of the mobile that were measured at the specified cell site. However, the cell
site did not provide the Stored Dynamic Mobile Attenuation Code (SDMAC) in effect at
the time of measurement.
For Series II Cell Release 4.3, the RF Call Trace feature provides the SDMAC, which is
accessed from the serving cell whenever RF Call Trace signal strength measurements
are requested by the OMP. This parameter permits adjustment of the signal strength
data 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 as
measured by the serving Radio Channel Unit (RCU). In addition, with the CDMA
Multiple 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 Call
Trace feature now provides an abbreviated Neighbor-1 neighbor list with the following
information supplied for each local neighbor (field identifiers are the same as those
defined in 401-610-036, Database Update Manual, for the Neighbor-1 neighbor list on
the 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 384
cells 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.

August 2003

Lucent Technologies Proprietary


See notice on first page

Page 7

Feature Description

401-612-052, Issue 17

TDMA Mode
When the RFTC feature is active, the MSC periodically sends an RF Call Trace
Location Request message that specifies the voice channel and time slot serving the
mobile to the serving cell.
The RF Call Trace feature uses readily available data at the radio. Therefore, regardless
of whether the serving cell receives the RF Call Trace Location Request message, the
serving cell sends a measurement order to the dual-mode mobile. This measurement
order causes the mobile to report measurements on up to 24 voice channels that were
previously 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 signal
strength, the BER, and the Frame Error Rate (FER) as measured by the serving DRU
or Enhanced Digital Radio Unit (EDRU).
As an aid to analysis, the RF Call Trace for Dual-Mode Mobiles feature provides an
abbreviated MAHO list for each MAHO neighbor measured. The following information
is provided for each MAHO neighbor (field identifiers are the same as those defined in
401-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 of
neighbors that a TDMA sector can support from 12 to 24 (neighbors). The Increased
TDMA MAHO List feature adds the following enhancements:

Page 8

Enhances the capabilities of the RF Call Trace feature by allowing a mobile


being served on an active TDMA traffic channel to handoff to as many as 24
other sectors specified by the service provider.

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

Lucent Technologies Proprietary


See notice on first page

August 2003

Feature Description

401-612-052, Issue 17

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

These changes are supported by an increase in the maximum number of entries in the
Measurement Order/Hyperband Measurement Order (MO/HMO) message sent to IS136 mobiles on active TDMA traffic channels. For each neighbor entry in the MO/HMO
message, IS-136 mobiles on the TDMA traffic channel report the measured downlink
channel quality to the cell site. These downlink measurements are used to support
MAHO and FLCA.
As a result of this feature supporting a maximum number of 24 entries in the MO/HMO
message, the number of dropped calls is reduced and the quality of channels selected
by the FLCA algorithm for assignment to calls is improved.
For more information on this feature, refer to 401-612-311, Increased TDMA MAHO
List.

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 mobile
in TDMA mode and its serving Digital Radio Unit (DRU). This data is used to assist in
engineering and troubleshooting Flexent/AUTOPLEX cell sites. For example, the
data may be used to explore RF conditions in areas experiencing inconsistent handoffs
and can assist in the selection of optimum neighbor lists.

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

August 2003

Pprimary antenna face: The primary antenna face is the antenna face that is
considered to be in control of the call. Service measurements that are related to
this call are incremented for the primary antenna face.

S1 S5secondary antenna faces: For CDMA calls that are in soft handoff,
there may be one or five secondary antenna faces in the active set. Forward and
reverse traffic is transported between the mobile and speech handler
simultaneously via the primary and all secondary antenna faces. The secondary
antenna faces are labeled S1 through S5 based on the order in which they were
added to the call.

Ccandidate antenna face: A candidate antenna face is an antenna face for


which the mobile has measured a pilot strength that exceeds the T_ADD
threshold, but which has not been added to the call. The candidate antenna face
must be populated in the CDMA neighbor list (fci form) for either the primary or
one of the secondary antenna faces.

Lucent Technologies Proprietary


See notice on first page

Page 9

Feature Description

401-612-052, Issue 17

R remaining set pilot: A remaining set pilot is a pilot for which the mobile has
measured a pilot strength that exceeds the T_ADD threshold, but does not
appear in the CDMA neighbor list of either the primary or one of the secondary
antenna faces. Since a remaining set pilot is not present in the database, the
system is not able to determine the ECP, cell site, and antenna face associated
with that pilot. Only the pilot Pseudo Noise (PN), pilot strength, and round trip
delay are printed for remaining set pilots.

Once the FTrftrace command is executed for a CDMA call, the Call Processing
Database Node (CDN) sends a CDMA measurement request message to all cells that
are associated with the call. This message is a pilot strength measurement request and
is sent to the primary cell and five secondary cells. Only the primary cell responds by
sending a CDMA measurement response message that contains the measured pilot
strength 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 the
CDMA call mode and later assigned to the AMPS call mode (after a CDMA to AMPS
handoff). If both RFCT and CDMARFCT are activated in the Feature Activation File
(FAF), signal strength measurements are collected regardless of whether the call mode
is CDMA or AMPS. When the CDMA MDNRFCT FAF is active, the capability to trace up
to ten mobiles at one time per trace is provided.
For a mobile-originated call, an RF Call Trace begins when the call enters the
conversation state. For a mobile-terminated call, an RF Call Trace begins as soon as
the call enters the Waiting for Answer state. The serving cell(s) associated with the
CDMA mobile for the RF Call Trace receive a CDMA measurement request message
from the OMP per polling interval. The cell requests that the mobile report all
measurements back to the cell. However, the OMP expects the report from only the
Primary cell. Some of the major information that is displayed as a result of an OMP
request 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.

Page 10

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

Lucent Technologies Proprietary


See notice on first page

August 2003

Feature Description

401-612-052, Issue 17

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 on
page 11:

Table 2.

Mobile Forward Traffic Frame Count Definitions - Voice

RF Call Trace
Counter Name

August 2003

IS-95* Name

Description
8K

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_3

1/4 rate dim & burst

MUX1_FOR_3

MUX2_FOR_3

M_F_4

1/8 rate dim & burst

MUX1_FOR_4

MUX2_FOR_4

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_7

1/4 rate

MUX1_FOR_7

MUX2_FOR_19

M_F_8

1/8 rate

MUX1_FOR_8

MUX2_FOR_24

M_F_9

full rate likely

MUX1_FOR_9

N/A

M_F_10

erasure

MUX1_FOR_10

MUX2_FOR_26

Lucent Technologies Proprietary


See notice on first page

Page 11

Feature Description

401-612-052, Issue 17

* The IS-95 names are from the following EIA/TIA Standards documents:
Mobile Station-Base Station Compatibility Standard for Dual-Mode Wideband Spread Spectrum Cellular System plus Telecommunications Systems Bulletin: Support for 14.4 Kbps Data Rate and PCS Interaction for
Wideband Spread Spectrum Cellular Systems, February 27, 1996.
Rate indicates the rate of the primary data. For example, 1/2 rate dim
and burst means that the frame was a full rate dim and burst frame with 1/
2 rate primary data.
NOTE:
The mobile counters are not cleared after a handoff nor after reporting measurements
to the cell. These parameters are taken from the mobile on a snap-shot basis for each
polling interval. All of the frame counts that are displayed for the mobile, except for the
counts in the first response message, are the difference between current and previous
polls. The frame counts that are displayed for the mobile in the first response message
are not the difference between the current and previous poll because there are no
previous counts to use as a base to determine the difference. Because mobile counters
are not reset, the frame counts that are displayed for the mobile in the first response
message are larger than normal. The polling interval for CDMA measurements are in
the range of 2 seconds to 60 seconds, with a default of 30 seconds. When more than
one DN is traced, the minimum polling interval is defined in the formula in Figure A on
page 21.

Mobile retrievable parameters for reverse traffic channels are listed in Table 3 on
page 12:

Table 3.

Mobile Retrievable Parameters for Reverse Traffic Channels

RF Call Trace
Counter Name

Page 12

IS-95* Name
8K
13K

Description

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_3

1/4 rate dim & burst

MUX1_REV_3

MUX2_REV_3

M_R_4

1/8 rate dim & burst

MUX1_REV_4

MUX2_REV_4

M_R_5

blank & burst

MUX1_REV_5

MUX2_REV_5

M_R_6

1/2 rate

MUX1_REV_6

MUX2_REV_11

M_R_7

1/4 rate

MUX1_REV_7

MUX2_REV_19

M_R_8

1/8 rate

MUX1_REV_8

MUX2_REV_24

Lucent Technologies Proprietary


See notice on first page

August 2003

Feature Description

401-612-052, Issue 17

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

Cell reverse traffic frame statistics from each serving cell site (before the frame
selection process) and from the primary cell site (after the frame selection
process)
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
Number of 2400 bps frames
Number of 1200 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. The
following coder/decoder types are currently supported:
0 = 8k voice
1 = 13k voice
2 = EVRC voice
3 = 8k Markov
4 = 13k Markov
5 = invalid SOR

August 2003

Lucent Technologies Proprietary


See notice on first page

Page 13

Feature Description

401-612-052, Issue 17

Markov RF Call Trace


The Markov RFCT is based on the Markov Service Option (SO), which provides
pseudo-random data for testing the traffic channel between the mobile station and the
base 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 the
variable-rate test is governed by a pseudo-random process. The contents of each
packet type are also generated by a pseudo-random process. The pseudo-random
processes are synchronized between the mobile station and the base station, thus the
receiving 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 traffic
channel. The Markov SO also counts the number of various frames that are received on
the traffic channel and the number of bit errors found by comparing the information bits
that 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)


0x801E (that is, New 8K Markov Call)

For Rate Set 2 (13Kbps)


0x801F (that is, New 13K Markov Call)

NOTE:
Mobile station forward and reverse frame statistics are only available to RFCT during
voice calls. Therefore, running RFCT on a New 8K or 13K Markov call produces only
cell counts; no mobile data is retrieved. Additionally, cell counts are collected by and
reported 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 retrieve
mobile station forward and reverse frame statistics that are collected at the cell during
New 8K and New 13K Markov calls and makes these statistics available to RFCT. Cell
counts remain as multiplexor statistics in this phase.
This enhancement makes use of the Service_Option_Control message counter
retrieval mechanism to collect and compute the required RFCT statistics. This
mechanism allows for the retrieval of all required vector sets2 and manages data
collection such that counter retrieval requests to the mobile are done at the appropriate
Markov synchronization frames.

Page 14

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

Lucent Technologies Proprietary


See notice on first page

August 2003

Feature Description

401-612-052, Issue 17

NOTE:
Because the retrievable Markov statistics for the mobile are updated once per Markov
synchronization interval, the Markov RFCT polling interval, if possible, should be a
multiple 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 screen
display. 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

RF Call Trace
Counter Name

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_R4

1/8 rate dim & burst

MSO_E8_TD

MK_R5

blank & burst (all rates)

sum of MSO_Ex_TB (where


x=1, 2, 4, or 8)

MK_R6

1/2 rate

MSO_E2_T2

MK_R7

1/4 rate

MSO_E4_T4

MK_R8

1/8 rate

MSO_E8_T8

* The Markov counters are those that are received from the mobile. For more
information, refer to the manufacturers documentation.
Table 5.

August 2003

Primary Cell Mapping for Mobile Received Markov Statistics on the


Forward Link (Sheet 1 of 2)

RF Call Trace
Counter Name

Description

Markov Counter* Name

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, received


dim & burst

MSO_E4_RD

MK_F4

expected 1/8, received


dim & burst

MSO_E8_RD

Lucent Technologies Proprietary


See notice on first page

Page 15

Feature Description

Table 5.

401-612-052, Issue 17

Primary Cell Mapping for Mobile Received Markov Statistics on the


Forward Link (Sheet 2 of 2)

RF Call Trace
Counter Name

Description

Markov Counter* Name

MK_F5

expected x, received blank


& burst

sum of MSO_Ex_RB (where


x=1, 2, 4, or 8)

MK_F6

expected 1/2, received 1/2

MSO_E2_R2

MK_F7

expected 1/4, received 1/4

MSO_E4_R4

MK_F8

expected 1/8, received 1/8

MSO_E8_R8

MK_F9

expected x, received full


rate likely or bit errors

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

MK_10

expected x, received
erasure

sum of MSO_Ex_RE where


x=1, 2, 4, or 8)

* For more information, refer to the manufacturers documentation.

Enhanced RF Call Trace/Markov - Phase 2


In addition to the capabilities described under Enhanced RF Call Trace/Markov - Phase
1, the Enhanced RF Call Trace/Markov - Phase 2 feature provides the ability to retrieve
cell Markov statistics maintained by the Markov packet processing function and make
them available to RFCT.
With this enhancement, cell frame statistics are reported to RFCT based on the call
type (voice or Markov). In the case of a voice call, cell frame statistics are reported to
RFCT from the Multiplex layer. In the case of a Markov call, reporting are done from the
Markov subsystem after Markov analysis and include the following new data:

Page 16

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

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

the forward and reverse tick IDs of the respective Forward and Reverse Markov
Synchronization frames

Lucent Technologies Proprietary


See notice on first page

August 2003

Feature Description

401-612-052, Issue 17

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

Mobile Reverse Traffic Frame Count Definitions - Markov

RF Call Trace
Counter Name

Description

Markov Counter* Name

MK_R1

full rate

MSO_E1_T1

MK_R2

full rate dim & burst

MSO_E1_TD

MK_R3

1/4 rate dim & burst

MSO_E4_TD

MK_R4

1/8 rate dim & burst

MSO_E8_TD

MK_R5

blank & burst (all rates)

sum of MSO_Ex_TB (where


x=1, 2, 4, or 8)

MK_R6

1/2 rate

MSO_E2_T2

MK_R7

1/4 rate

MSO_E4_T4

MK_R8

1/8 rate

MSO_E8_T8

MK_R9

1/2 rate dim & burst

MSO_E2_TD

* The Markov counters are those received from the mobile. For more
information, refer to the manufactures documentation.
Table 7.

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

RF Call Trace
Counter Name

August 2003

Description

Markov Counter* Name

MK_F1

expected full, receive


full

MSO_E1_R1

MK_F2

expected full, received


dim & burst

MSO_E1_RD

MK_F3

expected 1/4, received


dim & burst

MSO_E4_RD

MK_F4

expected 1/8, received


dim & burst

MSO_E8_RD

MK_F5

expected x, received
blank & burst

sum of MSO_Ex_RB (where


x=1, 2, 4, or 8)

MK_F6

expected 1/2, received


1/2

MSO_E2_R2

Lucent Technologies Proprietary


See notice on first page

Page 17

Feature Description

Table 7.

401-612-052, Issue 17

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

RF Call Trace
Counter Name

Description

Markov Counter* Name

MK_F7

expected 1/4, received


1/4

MSO_E4_R4

MK_F8

expected 1/8, received


1/8

MSO_E8_R8

MK_F9

excepted x, received
full rate likely +
excepted x, received y
(rate mismatches)

sum of MSO_Ex_RFL (where


x=1, 2, 4, or 8) + sum of
MSO_Ex_Ry (where
x=1, 2, 4, or 8 and
y=1, 2, 4, or 8)

MK_10

expected x, received
erasure

sum of MSO_Ex_RE (where


x=1, 2, 4, or 8)

MK_11

expected 1/2, received


dim & burst

MSO_E2_RD

MK_12

expected x, received
frame with bit errors

sum of MSO_Ex_RERR, (where


x=1, 2, 3, 4)

* The Markov SO counters are those maintained at the primary cell. For more
information, refer to the manufacturers documentation.

Calculating Frame Error Rates


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

Page 18

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)

Lucent Technologies Proprietary


See notice on first page

August 2003

Feature Description

401-612-052, Issue 17

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

Voice:

Divide the sum of full rate with bit error + quality insufficient by the
total number of frames in the report (for example, the sum of all
six rows)

Markov
(Phase 1)
&
(Phase 2):

Divide the sum of frames with bit errors + quality insufficient by


the total number of frames in the report (for example, the sum of
all six rows)

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 Trace


Session

CDMA RF Call Trace (CDMARFCT)


The CDMA RF Call Trace (CDMARFCT) feature (for AMPS/CDMA mode) is used to
trace a mobile call that is operating in the Code Division Multiple Access (CDMA) mode
and is based on AMPS/TDMA RF Call Trace with two new message types for request
and response. CDMA RF Call Trace also supports the reporting of Markov statistics
with 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:

August 2003

The Enhanced RF Call Trace/Markov - Phase 1 feature is based upon the


Markov Service Option (SO), which provides pseudo-random data for testing the
traffic channel between the mobile station and the base station. Phase 1
provides the ability to retrieve mobile station forward and reverse frame statistics
collected at the cell during New 8K and New 13K Markov calls and makes these
statistics 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 the
mobile station and the base station. Phase 2 is an enhancement to Phase 1 and
provides the ability to retrieve cell Markov statistics that are maintained by the
Markov packet processing function and make them available to RFCT.

Lucent Technologies Proprietary


See notice on first page

Page 19

Feature Description

401-612-052, Issue 17

CDMA Multiple Directory Number (DN) RF Call Trace


(CDMA MDNRFCT)
The CDMA Multiple Directory Number (DN) RF Call Trace (CDMA MDNRFCT) feature
allows the recording of signal strength and other information for up to ten designated
CDMA or AMPS mobiles (during a single session) on CDMA cells (APXDx.xx), within
the system coverage area.
NOTE:
The CDMA MDNRFCT feature is not supported by TDMA cells (APXBx.xx). When the
CDMA MDNRFCT feature is active, RF Call Trace does not record information for
TDMA and AMPS mobiles on TDMA cells (APXBx.xx).

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


Trace
The CDMA Adding and Deleting DN(s) During a RF Call Trace feature is an
enhancement to the CDMA MDNRFCT feature. This enhancement provides RFCT tool
users with the capability to add DNs to a RF Call Trace session, delete DNs from a RF
Call Trace session, and report RF Call Trace status.
NOTE:
The CDMA Adding and Deleting DN(s) during RF Call Trace enhancement does not
record information for TDMA/AMPS cells (APXBx.xx).
When more than one DN is traced, the minimum polling interval is defined as follows:
Table 8.

Minimum Equivalent Polling Interval

Polling Interval

Number of DNs

2 seconds

1 to 4 DNs

3 seconds

5 to 6 DNs

4 seconds

7 to 8 DNs

5 seconds

9 to 10 DNs

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

Page 20

Lucent Technologies Proprietary


See notice on first page

August 2003

Feature Description

401-612-052, Issue 17

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 session
enhancement to be on the CDMA MDNRFCT FAF must be marked active. For the
CDMA Adding and Deleting DN(s) During a RF Call Trace Session enhancement, the
requested polling period for a MDN RFCT session is accepted as long as the Number
of DN versus the Polling-Period is represented by the following equation:

PollingPeriodi 2
1

per second

i=1

where N is the number of DNs in the RF Call Trace session, and Polling Period i is the
requested 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, all
analog 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, the
difference can cause erroneous results for all analog DNs in the session, and all
subsequent call trace request records for analog calls will indicate that the data may be
invalid.
The -F parameter of the FTrfdump command sends subsequent log records, which
match the specified input parameters, to the standard output in real-time. The log
records are written to the RFCT log files as well as the user terminal. The interrupt
signal stops neither the RFCT for any DN, nor the writing of any RFCT records to the
log file.
NOTE:
The real-time output capability has been moved to the FTrfdump command. The
FTrftrace -o real-time option is not supported for MSCs with the CDMA MDNRFCT
FAF. If the user enters the obsolete FTrftrace command, the OMP returns an error
message that refers the user to the new FTrfdump -F parameter.
The -s parameter of the FTrftrace command returns the following information for
each call in the RFCT session:

August 2003

DN

Tag

Lucent Technologies Proprietary


See notice on first page

Page 21

Feature Description

401-612-052, Issue 17

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 in
conjunction with any other options for the FTrftrace command.

UNIX System Commands


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

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 Call
Trace feature. Once invoked, FTrftrace verifies that the feature is activated in the
Feature Activation File (FAF). FTrftrace then checks the command line input and
sends a message to the Administrative Call Processing Data Base Node (ACDN) to
begin call trace measurements. If any errors are detected, FTrftrace terminates and
prints an error message. See Appendix A - FTrftrace(1) on page 39 for the FTrftrace
command and its options.

FTrftrace runs in the background (unless real-time output is requested) and collects
the trace information that is sent from the cell site nodes. As each locate reply is
collected, FTrftrace records the time and writes the data to log files and, with the
real-time dump option, to standard out (terminal). If desired, the data may then be
copied to a user-named file to be saved for later processing.
With the FTrftrace command, up to eight cell sites may be specified for
measurements, along with the measurement rate and total measurement interval. The
user may also specify the use of the serving cells neighbor-1 neighbors in AMPS
mode.
When the CDMA MDNRFCT FAF is marked active, the FTrftrace command can be
used to add one or more DNs to the active session. Also, with the -s option the status
of a particular session and the available bandwidth for adding a single DN are available.

Page 22

Lucent Technologies Proprietary


See notice on first page

August 2003

Feature Description

401-612-052, Issue 17

NOTE:
When the CDMA MDNRFCT FAF is marked active the FTrftrace -o option is no longer
available. 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 occurs
when the trace duration time expires. A manual termination command, FTrfstop, can
be executed to stop the call trace at any point before normal termination. When more
than one DN is traced, this command terminates the traces on a given call, a list of
DNs, all DNs for a tag, or all DN(s) in the session. Appendix B contains the command
information for FTrfstop.

FTrfdump Command
FTrfdump is a UNIX System command that searches the FTRFTRACE file for records
that match the given input parameters. FTrfdump scans the log files (FTRFTRACE0
and FTRFTRACE1 located in the /omp-data/logs/rfct/ directory) for matches based on
either 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 be
optionally selected.
See Appendix D for the FTrfdump command and its options, along with samples of
both the formatted and raw ASCII outputs.
NOTE:
When the CDMA MDNRFCT FAF is active, the real-time output capability (-o option) is
moved from the FTrftrace command to the FTrfdump command.

FTrfclear Command
FTrfclear is a UNIX System command that reads records from the binary log file
and 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 FeatureImpact on RF Call Trace


The 15 Digit DN feature provides a new and more flexible DN structure to meet the
needs of international markets, while preserving the ability to handle the traditional 10Digit Mobile Directory Number (MDN) which meets the needs of current service
providers.
The impact of the15 Digit DN feature on RF Call Trace is that each of the DNs specified
for call trace can be a string of 1 to 14 digits. Therefore, the 15 Digit DN feature impacts
the following UNIX System Commands for RF Call Trace:

August 2003

Lucent Technologies Proprietary


See notice on first page

Page 23

Feature Description

401-612-052, Issue 17

FTrftraceRefer to Appendix A - FTrftrace(1) on page 39

FTrftstopRefer to Appendix B - FTrfstop(1) on page 43

FTrfdumpRefer 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 in
either the HLR database or the VLR database, then the trace is not performed. This is
because 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 by
Basic 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 average
forward transmit power on the fundamental channel (Ectf). (This information was
previously 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 the
same display for 2G and 3G voice calls. There are five new data measurements
displayed by this feature for each burst rate (2x, 4x, 8x, and 16x):

the forward average transmit power for the Forward Supplemental Channel (FSCH) 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 6
legs-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 (4
values)

Stop Indicator
The request message includes a new stop indicator. The Ectf and Ects power
measurements 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 is
received with a stop indicator.
The time out of each RFCT session is removed and replaced by the stop indicator
functionality.

Page 24

Lucent Technologies Proprietary


See notice on first page

August 2003

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 allows the display (verbose and
raw formatted outputs) of new data values for 3G HSPD calls and continues to support
the same display for 2G and 3G voice calls. There are nine new data measurements
displayed 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 each
rate
5. num_rsch_mob_frames - number of R-SCH mobile frame transmitted for
each 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 the
polling interval in scaled linear units -6 values)

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

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

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

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

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

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

Feature Description for Enhanced RF Call Trace for


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

August 2003

Lucent Technologies Proprietary


See notice on first page

Page 25

Feature Description

401-612-052, Issue 17

The Enhanced RF Call Trace for 3G-1X Calls feature allows the display (verbose and
raw formatted outputs) of new data values for 3G HSPD calls and continues to support
the same display for 2G and 3G voice calls. There are five new data measurements
displayed 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 during
polling interval.
2. ECTSSofter - The average transmit power for the softer F-SCH during polling
interval.
3. NSFDTXSofter - The number of DTX F-SCH frames in softer hand-off during
polling 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 to
10. The anchor ID consists of the MSC number, the Cell number, the face
number, and the PN Offset of the face. The history is empty if there are no
anchor setups during the interval.
6. Burst_Info - The history of burst information, both forward and reverse for the
polling interval. The system remembers information of up to 12 forward-direction
and 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 old
primary to the new primary. Before a secondary leg drops, the Enhanced RF Call Trace
for 3G-1X Calls feature sends NSFFSofter , NSFDTXSofter, and Forward burst
information to the primary cell.

Page 26

Lucent Technologies Proprietary


See notice on first page

August 2003

Feature Description

401-612-052, Issue 17

Release 21.0 also supports the following 3G displays:

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

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

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

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

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

num rsch frames (R-SCH) - the number of R-SCH frames received during
the 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 each


rate

num_rsch_mob_frames - number of R-SCH mobile frames transmitted for


each 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 15
existing 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, the
secondary CCC checks its own CCC Overload Status. If the CCC is in overload, the
request is discarded. Similarly, RFCT does not collect, store, or report data when a
Radio Cluster Controller (RCC), Time Division Multiplex (TDM) Bus control channel, or
Primary CCC are in overload.
For details on how the Flexent/AUTOPLEX system handles overload conditions, see
401-610-009, System Capacity Monitoring and Engineering Guidelines.

August 2003

Lucent Technologies Proprietary


See notice on first page

Page 27

Feature Description

401-612-052, Issue 17

Major RFCT Metrics Summary


Table 9 on page 28 and Table 10 on page 28 shows the major RFCT metrics
supported/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)

2G
CCU

3G
CCU

2G
CCU

3G
CCU

Frame counts (2G/3G: RFER)

Yes

Yes

Yes

Yes

Traffic power (2G)

Yes

Yes

Yes

Yes

Traffic power (3G:FCH) [This data, also


known as Ectf, is not available in the raw
output format in R17.1, but is available in
R18.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

Page 28

Lucent Technologies Proprietary


See notice on first page

August 2003

Feature Interactions

Table 10.

401-612-052, Issue 17

3G-1X HSPD RFCT Capabilities


Metric

Release 18.0
(and later)
3G CCU

Call status info

Yes

Reverse Eb/No (RFCH/RSCH)

No

Forward Pilot Ec/Io

No

Round trip delay

No

Multiple Dial Number RFCT

Yes

5. Feature Interactions
The RF Call Trace Dual-Mode TDMA/AMPS Mobiles feature is dependent on the RF
Call Trace feature being active.
The RF Call Trace CDMA/AMPS Mobiles feature is dependent on the RF Call Trace
feature being active.
CDMA Multiple DN RF Call Trace support for AMPS mobiles is dependent on the RF
Call Trace feature being active. The CDMA MDNRFCT is not currently supported by
TDMA cells (APXBx.xx). When the CDMA MDNRFCT feature is active, RF Call Trace
does 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 on
the CDMARFCT feature being active.
CDMA RF Call Trace works with the CDMA Circuit-Mode Data service. The appropriate
service 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 HSPD
feature.

6. Special Considerations
This section gives any special considerations of this feature.

August 2003

Lucent Technologies Proprietary


See notice on first page

Page 29

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 UNIX
command on the OMP is used to maintain the RF Call Trace binary log files. These
commands 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 these
commands.
The OMP Scheduler (OSCHED) tool on the OMP also provides the capability to
schedule a call trace for later execution.
The OMP shell and OSCHED can be accessed through the MISCELLANEOUS
APPLICATIONS item in the OMP main menu. On-line manual pages for these UNIX
commands 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, have
permission 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 separated
mobiles after inter-MSC handoffs.

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

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

Page 30

Lucent Technologies Proprietary


See notice on first page

August 2003

Caveats

401-612-052, Issue 17

The technician enters the DN of the mobile as part of the RF Call Trace
command to specify the mobile whose call is to be traced. If the MSC does not
have the subscriber record or vlr of the mobile, the MSC attempts to perform the
trace as if the mobile is programmed with a MIN-based IMSI and as if the MIN
and the DN of the mobile are the same. If the MIN and the DN of the mobile are
not the same as a result of MIN-MDN separation or if the mobile is programmed
with 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 to
another MSC. For a RF Call Trace attempted at the target MSC for a hard
handoff or at the remote MSC for a soft or semi-soft handoff, the trace can be
performed only if the mobile is programmed with a MIN-based IMSI and the DN
of the mobile and MIN are the same.

If a VLR does not exist for this roamer, RF Call Trace cannot be done for a
roaming 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 following
limitations:

All the limitations of the RF Call Trace feature.

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

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 RF
Call 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 record
information 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 3G1X HSPD feature can send RFCT requests to cells that are running older software
loads, as well as cells running the 3G (18.0 or later) software. This includes the
possibility that any given call (except 3G packet data calls) can undergo a primary
transfer between old and new cells during the RFCT session.

August 2003

Lucent Technologies Proprietary


See notice on first page

Page 31

Feature Implementation

401-612-052, Issue 17

In addition, the cells themselves must be able to handoff with other cells running older
software loads. The inter-cell messaging must be backward compatible so that a
handoff 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 Markov
enhancements (see Markov RF Call Trace in this document), a FAF must be installed
on the ECP with the appropriate entries marked active. The entries associated with the
RF Call Trace features are

RFCTRF Call Trace.

DMRFCTRF Call Trace for Dual-Mode -TDMA/AMPS- Mobiles. The RFCT FAF
must also be marked active.

CDMARFCTRF Call Trace for CDMA/AMPS- Mobiles. The CDMARFCT FAF


also activates the CDMA Markov enhancements. The RFCT FAF must also be
marked active.

CDMA MDNRFCTCDMA Multiple DN RF Call Trace. The RFCT FAF must also
be marked active. The CDMA MDNRFCT feature does not record information for
TDMA cells (APXBx.xx). CDMA MDNRFCT FAF also activates the CDMA Adding
and 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, the
FTrftrace command exits with an error message that indicates that only one DN can
be 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 for
this feature.

Improved RF Call Trace for 3G-1X HSPD


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

Page 32

Lucent Technologies Proprietary


See notice on first page

August 2003

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 Calls
feature. No changes are made to what is supported with the FAF. No new FAFs are
required for this feature.

August 2003

Lucent Technologies Proprietary


See notice on first page

Page 33

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.

Page 34

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/AMPSMobiles

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

Lucent Technologies Proprietary


See notice on first page

August 2003

Supplemental Information

401-612-052, Issue 17

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

August 2003

Lucent Technologies Proprietary


See notice on first page

Page 35

Supplemental Information

401-612-052, Issue 17

References
The following Flexent/AUTOPLEX Wireless Networks documents contain
information related to the RF Call Trace feature:

Page 36

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

Lucent Technologies Proprietary


See notice on first page

August 2003

History of Revisions

401-612-052, Issue 17

10. History of Revisions


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

Issue 16
This document was reissued to include support of the Improved RF Call Trace for 3G1X HSPD feature as of ECP Release 20.0. For changes as a result of the Improved RF
Call 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

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

"Major RFCT Metrics Summary" on page 28

"Feature Interactions" on page 29

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

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

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

"Availability" on page 2

"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 384
Cells feature as of ECP Release 17.1. For changes as a result of the MSC OA&M
Support for 384 Cells feature, refer to the following sections:

August 2003

"Availability" on page 2

"Feature Description" on page 5

Lucent Technologies Proprietary


See notice on first page

Page 37

History of Revisions

401-612-052, Issue 17

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

"Availability" on page 2

"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:

"Availability" on page 2

"15 Digit DN FeatureImpact 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 a
RF Call Trace session which is an enhancement to the CDMA MDNRFCT feature (ECP
Release 15.0 and later).

Issue 10
This document was reissued to include more information about the MK_F9 counter and
information about CDMA Soft Handoff RF Call Trace Request (type 15) and CDMA
6-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 and
AMPS RF Call Trace. Additionally, this document is being reissued to include
information relating to the migration of the RF Call tool from the ECP to the Operations
and Maintenance Platform (OMP). This feature impacts all call modes including AMPS,
AMPS/TDMA, and AMPS/CDMA. This document is also being reissued to include
information about interactions with the CDMA Circuit-Mode Data optional feature.

Page 38

Lucent Technologies Proprietary


See notice on first page

August 2003

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 the
Multiple DN FAF is active (CDMA/Analog) the command allows the user to start a new
trace, add DNs to an existing session (for a maximum of 10), and obtain status
information of current traces along with available bandwidth.
NOTE:
The Multiple DN FAF is available only in the CDMA cells (APXDx.xx) for tracing calls in
CDMA or Analog mode. Also the FTrfstop command may be used to delete individual
DNs from an active session.
On an active call in analog mode measurements are made by each cell in the list of
cells.
On an active call in TDMA/AMPS mode, if the -c option is used, mobile measurements
are collected if the mobile is on an ECP Release 5.1 (or later) and if that cell is on the -c
list. Otherwise, no measurements are made. The MAHO list for the serving cell is used
to determine which radio channels to measure. In TDMA mode, when -c and -f appear
together on the command line, this is equivalent to -n. The -f option is used to force
measurements to be taken from cells not listed in the -c list. The -n option causes the
use 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 cell
and two Secondary cells. The Primary cell will respond by sending a reply message
containing the measured pilot strength to the ECP. This message contains the CDMA
neighbor list that includes up to 12 measurements per serving cell.

August 2003

Lucent Technologies Proprietary


See notice on first page

Page 39

Appendix A - FTrftrace(1)

401-612-052, Issue 17

For CDMA calls, the -c, -f and -n options will be ignored. If the cell is in the middle of a
CDMA-to-Analog handoff, hard handoff or primary transfer, and unable to get a
measurement, no measurement will be recorded for this instance. The cell may either
respond with a CDMA measurement response message with the field valid=FALSE
and measurement data invalid, or no CDMA measurement response at all.
Each measurement is stored in binary form in log files FTRFTRACE1 and
FTRFTRACE0 located in the /omp-data/logs/rfct directory. FTRFTRACE1 is
always the active file. When this file reaches a tunable maximum size, it is moved into
FTRFTRACE0. The default for this maximum is to 6MB, at this time. The FTrfdump
command 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 VLR
database, 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. Must
specify at least one DN.

NOTE:
If a non -10 digit DN is specified, which does not appear in the HLR database or VLR
database, 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.

Page 40

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

Lucent Technologies Proprietary


See notice on first page

August 2003

Appendix A - FTrftrace(1)

401-612-052, Issue 17

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

Number of DNs

2 seconds

1 to 4 DNs

3 seconds

5 to 6 DNs

4 seconds

7 to 8 DNs

5 seconds

9 to 10 DNs

All analog 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 it can cause
erroneous results for all analog DNs in the session, and all subsequent call trace request
records for analog calls will indicate the data may be invalid. This data will be formatted for
printing 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 polling
period supported for an additional DN. Available only with the CDMA Multiple DN FAF.

4
5

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

August 2003

Lucent Technologies Proprietary


See notice on first page

Page 41

Appendix A - FTrftrace(1)

401-612-052, Issue 17

-n
Use the neighbor-1 neighbors for the list of cells to be traced for analog mode. Use the MAHO
neighbors for the list of mobile measurements. With this option, the -f and -c options are
ignored.
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 valid
range is 0 to 5.
-R
Support 3G RFCT optional parameter. To specify the reverse supplemental rate. The valid
range is 0 to 4.

Examples
FTrftrace -c 24 26 25 2 -d 12345678901 -t mytag -i 20 -p 45
FTrftrace -s
FTrftrace -c 10 2 106 -d 12345678901234 7085551234
FTrftrace -c 12 14 9 -d 1234567890 -i 5 -o -r > file&
FTrftrace -c 200 1 77 267 -d 123 -i 15 -p 60 -f
FTrftrace -n -m dnfile -i 15 -p 60
FTrftrace -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 must
have the UNIX group_id pace as enforced by the /etc/group file on the OMP. The user
must also execute the /omp/etc/ompprofile and /omp/etc/ompenv to obtain a consistent
environment.

Page 42

Lucent Technologies Proprietary


See notice on first page

August 2003

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 Call
Trace session, and an entry will be made in the log file indicating the time the trace was
stopped.
With the CDMA Multiple DN FAF, the command is capable of stopping one or more
DNs selectively. The DNs may be specified by the tag or DN. The FTrftrace -s
command 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 it
stops 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.

August 2003

Lucent Technologies Proprietary


See notice on first page

Page 43

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
The RF Call Trace tools must be executed from the OMP Shell. The user login must
have the UNIX group_id pace as enforced by the /etc/group file on the OMP. The user
must also execute the /omp/etc/ompprofile and /omp/etc/ompenv to obtain a consistent
environment.

Page 44

Lucent Technologies Proprietary


See notice on first page

August 2003

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 that
match the specified tag name. All the matched records will then be deleted from the log
file.
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

August 2003

Lucent Technologies Proprietary


See notice on first page

Page 45

Appendix C - FTrfclear(1)

401-612-052, Issue 17

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

User Environment
The RF Call Trace tools must be executed from the OMP Shell. The user login must
have the UNIX group_id pace as enforced by the /etc/group file on the OMP. The user
must also execute the /omp/etc/ompprofile and /omp/etc/ompenv to obtain a consistent
environment.

Page 46

Lucent Technologies Proprietary


See notice on first page

August 2003

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 that
match the specified input parameters. For each record match found, FTrfdump will
print the trace data in different formats based on the technology type. The data is
arranged 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 option
replaces the -o option of the FTrftrace command.
By default, measurements will be Receive Signal Strength Units (RSSUs) for analog or
in 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 an
interrupt 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. If
the -d option alone is specified, all call trace records for this mobile will be printed; if used with
the -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.

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

August 2003

Lucent Technologies Proprietary


See notice on first page

Page 47

Appendix D - FTrfdump(1)

401-612-052, Issue 17

-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 should
be 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 strength
measurements are in RSSU for analog or in IS-54B for TDMA (default).
The following are the layout of the different message types from FTrfdump:

Page 48

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:Bsg1: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:Zsg0: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:Zsg0: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:MAH
O]*...: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]...

Lucent Technologies Proprietary


See notice on first page

August 2003

Appendix D - FTrfdump(1)

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:

7
8
9
10
11
12

401-612-052, Issue 17

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:

Null values for any of the fields will be represented as _.


Null values for any of the fields will be represented as _.
Null values for any of the fields will be represented as _.
Output optionally for all 2G calls and also on 3G calls with cell releases<=R19.

Null values for any of the fields will be represented as _ or N/A.


This message is only applicable to 3g1x data calls in ECP releases 18 and 19.

August 2003

Lucent Technologies Proprietary


See notice on first page

Page 49

Appendix D - FTrfdump(1)

401-612-052, Issue 17

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

13
14
15
16
17
18
19
20
21
22
23
24

Page 50

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_rates
17[: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:

Repeated #_of_rates.
Repeated #_of_rates.

Null values for any of the fields will be represented as _ or N/A.


This message is only applicable to 3g1x data calls in ECP release >=20.
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.
Repeated #_of_rates.
Repeated #_of_rates.
Repeated #_of_f_rates.
Repeated #_of_rates.
Repeated #_of_f_rates.

Null values for any of the fields will be represented as _ or N/A.


This message is only applicable to 3g1x data calls in ECP release >=20.

Lucent Technologies Proprietary


See notice on first page

August 2003

Appendix D - FTrfdump(1)

401-612-052, Issue 17

1/8_frm:1/8_frm:1/8_frm:gen:
ectf:ectf:ectf:ectf:ectf:ectf:iorf:iorf:iorf:iorf:iorf:iorf:#_of_rates
25
[: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:f
sch_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
26
27
28
29
30
31

type

number indicating the type of the call trace message.

time

a 12-digit number showing the date and time the message was
logged, 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.

In cell releases <20, #_of_f_rates is same as #_of_rates so it is always set to _.


Repeated #_of_rates.
Repeated #_of_rates.
Repeated #_of_f_rates.
Repeated #_of_rates.
Repeated #_of_f_rates.
Repeated #_of_rates.

August 2003

Lucent Technologies Proprietary


See notice on first page

Page 51

Appendix D - FTrfdump(1)

Page 52

401-612-052, Issue 17

SAT/DVCC

the Supervisory Audio Tone for the radio serving the call or the
Digital Verification Color Code. If the time slot is0 (AMPS) then
this 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 the


server 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=valid
or 0=invalid cell

valid

Flag that indicates if some of the data is invalid (0=invalid or


1=valid).

measurement

a character indicating the units. The cell signal measurements


are 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 as


follows:
0 = The measurement is valid
1 = Signal Strength Estimate is not valid
2 = Did not receive SDMAC from Voice Radio
3 = Errors 1 and 2

X-sg Y

the signal strength measurement for logical face. Where X is


Omni, Alpha, Gamma, etc. and Y is 0 for server group 0 and 1 for
server group 1.

Lucent Technologies Proprietary


See notice on first page

August 2003

Appendix D - FTrfdump(1)

August 2003

401-612-052, Issue 17

RCU

the Radio Control Unit serving the call.

MAHO

the signal strengths of the MAHO neighbors as measured by the


mobile.

#_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 the
call.

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 Radio
Unit (DRU) serving the call.

sub

the sub group identifying the neighbor priority.

MFA

indicates if all responding neighbor faces may be considered as


handoff candidates or only the strongest responding face.
y=yes, all responding faces
n=no, only strongest face

Hobias

indicates the bias value (hysteresis) to be used for


handoffshandoffs.

cell_CD

indicates the configuration of the neighbor cell site associated


with the cell site.
1=single omnidirectional
2=single sectorized
3=server group 0 Omni server group 1 Omni
4=server group 0 sectorized server group 1 Omni
5=server group 0 sectorized server group 1 sectorized
6=server group 0 Omni server group 1 sectorized

sgX_bias

specifies the server group X bias value from the serving cells
logical face to the server group X of the neighbors physical face.
Where X is the server group number (0 or 1).

sgX_VMAC

specifies the nominal attenuation code assigned to mobile units


served by this server group X face for a Class IV mobile unit.
Where X is the server group number (0 or 1).

Lucent Technologies Proprietary


See notice on first page

Page 53

Appendix D - FTrfdump(1)

Page 54

401-612-052, Issue 17

sgX_DTH

the Server Group X Decision Threshold field. This field


represents one of the following when the handoff candidate face
is the primary server group (for a dual cell or nondual cell).
Dual Cell: This field represents the hysteresis adjusted primary
threshold for handoff.
Nondual Cell: This field represents the handoff interference
protection threshold, which may be higher than the setup
interference protection threshold.

DCSID

the DCS number serving the neighbor cell. This is one part of the
unique identificationof a system known as the Extended System
ID (ESID).

ECPID

the ECP number serving the neighbor cell. This is one part of
the unique identification of a system known as the Extended
System ID (ESID).

SID

the system number serving the neighbor cell. This is one part of
the unique identification of a system known as the Extended
System 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 the
soft 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 signal


measurement 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 state
0x100 = secondary #3 CE data missing
0x200 = secondary #4 CE data missing
0x400 = secondary #5 CE data missing

Lucent Technologies Proprietary


See notice on first page

August 2003

Appendix D - FTrfdump(1)

August 2003

401-612-052, Issue 17

seq

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

ctype

CDMA vocoder type:


0 = 8kbps/voice
1 = 13kbps/voice
2 = EVRC/voice
3 = 8kbps/markov
4 = 13kbps/markov
5 = 9.6Kbps/Async
6 = 14.4Kbps/Async
7 = 9.6Kbps/Fax
8 = 14.4Kbps/Fax
9 = 8kbps/CMLT
10 = 13kbps/CMLT
11= 9.6kbps/IP
12=14.4kbps/IP
13=9.6kbps/CDPD
14=14.4kbps/CDPD
15=9.6kbps/Fax (Analog)
16=14.4kbps/Fax (Analog)
17=3G1X/IP
18=3G1X/CDPD
19=SMV
999 = INVALID

tic

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

tic_hi

CDMA Tick ID (GPS time reference) (High order 32 bits in


hexadecimal of the tic or_if N/A). Derived from mobile HOTRIG
data. Disabled for r18 3G calls is now re-enabled in r19

tic_lo

CDMA Tick ID (GPS time reference) (Low order 32 bits in


hexadecimal of the tic or_if N/A). Derived from mobile HOTRIG
data. 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 cell
S1 - first secondary cell
S2 - second secondary cell
S3 - third secondary cell
S4 - fourth secondary cell
S5 - fifth secondary cell
C - candidate cell
RC - null

Lucent Technologies Proprietary


See notice on first page

Page 55

Appendix D - FTrfdump(1)

Page 56

401-612-052, Issue 17

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 mobile


HOTRIG data.

trp_dly

R-trip delay (16 bits decimal in microsecond) or_if N/A. Derived


from mobile HOTRIG data. Earlier disabled for 3G calls is now
re-enabled.

eb_no

Eb/No (in db with resolution of .01) or_if N/A. Value displayed is


per antenna path. EbNo for 3G calls is now reported correctly.

keep

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


data.

m_ftf

Mobile forward traffic frame count (32 bits) or_. Derived from
mobile 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 call
or Rftrace session should be discarded. Earlier disabled for 3G
calls is now re-enabled.

c_stat

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

m_rtf

Mobile reverse traffic frame count (32 bits) or_. Derived from
mobile 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 be
discarded. 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 and
one 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 and
one for the Aftr-Frm-Sel for the primary cell (16 bits).

bad_qual

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

1/2_frm

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

Lucent Technologies Proprietary


See notice on first page

August 2003

Appendix D - FTrfdump(1)

401-612-052, Issue 17

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 and
one for the Aftr-Frm-Sel for the primary cell (16 bits).

1/8_frm

Eighth-rate frames for the cell reverse traffic frame statistic. One
for the Bfr-Frm-Sel of the P, S1, S2, S3, S4, S5 cells and one for
the 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 HO
leg. (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 - Average


ECTS. (Floating point number).

iors

forward IS-2000 supplemental channels information -Average


IORS. (Floating point number).

num_frm

Forward IS-2000 supplemental channels information - Number of


Frames.

rev_sup

Reverse IS-2000 supplemental channel frame error rate


information - Before Frame Selector per Handoff leg.
Incremental decimal, for 2x, 4x, 8x, 16x.

rev_sup_afs

Reverse IS-2000 supplemental channel frame error rate


information - After Frame Selector per Handoff leg. Incremental
decimal, for 2x, 4x, 8x, 16x.

rev_sup_tfn

Reverse IS-2000 supplemental channel frame error rate


information - Total Frame Number at Primary. Incremental
decimal , for 2x, 4x, 8x, 16x.

rev_ebno Reverse

IS-2000 supplemmental channel Eb/No information per Handoff


leg. Displayed as per antenna path in resolution of 0.01 db. Null
values may be_or N/A.

August 2003

Lucent Technologies Proprietary


See notice on first page

Page 57

Appendix D - FTrfdump(1)

Page 58

401-612-052, Issue 17

RfRate

Requested forward supplemental rate, default to 0 (see Ftrftrace


options).
0 - none requested in commmand line
1 - 2x rate
2 - 4x rate
3 - 8x rate
4 - 16x rate
5 - 32x rate

RrRate

Requested reverse supplemental rate, default to 0 (see Ftrftrace


options).
0 - none requested in commmand line
1 - 2x rate
2 - 4x rate
3 - 8x rate
4 - 16x rate
5 - 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 from


mobile 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 the


following order: 2X, 4X, 8X, 16X, 32X. Derived from mobile
PARMS data.

rsch_m_frm

incremental mobile reported number of R-SCH frames in the


following order: 2X, 4X, 8X, 16X, 32X. Derived from mobile
PARMS data.

fsch_dtx_frm

incremental number of DTX frames of F-SCH in the following


order: 2X, 4X, 8X, 16X, 32X. Derived from mobile PARMS data.

fsch_dtx_frm

incremental number of DTX frames of R-SCH in the following


order: 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.

Lucent Technologies Proprietary


See notice on first page

August 2003

Appendix D - FTrfdump(1)

num_fsch_softer
num_dtx_fsch_softer

num_fwd_entries
startime
frm_trans

401-612-052, Issue 17

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


Number of DTX F-SCH frames in softer handoff of rate R
Number of valid entries in the forward burst table
Start time of the burst. It is the GPS time in 20ms unit.
Number of frames transferred

frm_req

Number of frames requested. In the forward direction, this


number could be 0,1, 2, 3, 4, 5, 6, 7, 8,16, 32, 64, 96, 128, 0r
256. 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
cellid
first_paf
RC
second_paf
second_pilot_pn
simul

pn offset of the first softer leg


Cell number
Face of the first softer leg
Radio configuration
Face of the second softer leg
pn offset of the second softer leg
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
req_rate

August 2003

Allocated rate
Requested rate

Lucent Technologies Proprietary


See notice on first page

Page 59

Appendix D - FTrfdump(1)

aloc_flag

401-612-052, Issue 17

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

Page 60

Lucent Technologies Proprietary


See notice on first page

August 2003

Appendix D - FTrfdump(1)

401-612-052, Issue 17

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 burst
rate 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


Number of valid entries in the anchor history table

num_anchor _entries

timestamp

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

pilot_pn

Pn offset of the new anchor

paf
[ ]...

August 2003

Face of the anchor


-

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

Lucent Technologies Proprietary


See notice on first page

Page 61

Appendix D - FTrfdump(1)

401-612-052, Issue 17

Examples
To print all AMPS/TDMA call trace records for a recent cell release (5.1 or later) for DN
312-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 time
mode, 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 named
dump.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 DN
312-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 and
have 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
The RF Call Trace tools must be executed from the OMP Shell. The user login must
have the UNIX group_id pace as enforced by the /etc/group file on the OMP. The user
must also execute the /omp/etc/ompprofile and /omp/etc/ompenv to obtain a consistent
environment.

Page 62

Lucent Technologies Proprietary


See notice on first page

August 2003