Professional Documents
Culture Documents
RF Call Trace
RF Call Trace
Wireless Networks
RF Call Trace
Optional Feature Description
Release 22.0
401-612-052
Issue 18
May 2004
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 2004 Lucent Technologies
Unpublished and Not for Publication
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.
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
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/.
Contents
May 2004
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
RF Call Trace for Dual-Mode Mobiles (DMRFCT)
CDMA Mode
Markov RF Call Trace
Enhanced RF Call Trace/Markov - Phase 1
Enhanced RF Call Trace/Markov - Phase 2
Calculating Frame Error Rates
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
UNIX System Commands
15 Digit DN FeatureImpact on RF Call Trace
Basic RF Call Trace for
3G-1X High Speed Packet Data (HSPD)
Improved RF Call Trace for 3G-1X HSPD
Lucent Technologies Proprietary
See notice on first page
1
1
1
1
2
3
3
3
4
4
5
5
5
5
6
6
7
8
8
9
9
14
14
16
18
19
20
20
21
22
23
24
25
Page iii
401-612-052, Issue 18
Page iv
25
27
28
29
29
29
30
30
30
30
32
33
33
33
34
34
36
37
37
37
38
38
38
38
39
39
39
39
44
46
48
May 2004
Figures
A.
May 2004
21
Page v
401-612-052
Figures
May 2004
Page vi
Tables
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
May 2004
2
11
12
15
16
17
17
20
28
28
Page vii
401-612-052
Tables
May 2004
Page viii
Introduction
401-612-052, Issue 18
1. Introduction
This document describes the Radio Frequency (RF) Call Trace optional feature of
Flexent/AUTOPLEX Wireless Networks. This document provides the following
information:
Information about how this feature affects other system interfaces (for example,
Recent Change/Verify (RC/V) forms and Automatic Message Accounting (AMA)
records)
adds feature information for the Support for Up to 600 Cells feature [Feature
Identifier (FID)8875.0]:
Availability on page 2
Support for Up to 600 Cells on page 29
adds feature information for the Radio Network Controller (RNC) Call Trace
feature [Feature Identifier (FID)10668.0]:
Availability on page 2
RNC Call Trace on page 29
Abbreviations on page 34
Appendix D - FTrfdump(1) on page 48
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.
May 2004
Page 1
Availability
401-612-052, Issue 18
2. Availability
Refer to the following table for availability:
Table 1.
ECP Release
RF Call Trace
Notes
Enhanced RF Call
10.0/CDMA Release 5.0
Trace/Markov - Phase 2 (or later)
CDMA Multiple DN
15 Digit DN
16.0
Increased TDMA
MAHO List
16.1
Page 2
May 2004
Availability
Table 1.
401-612-052, Issue 18
ECP Release
Notes
Enhanced RF Call
Trace for 3G-1X Calls
Supported Technologies
The RF Call Trace feature is supported in the following air-interface technologies:
analog
CDMA cellular
CDMA PCS
TDMA cellular
TDMA PCS
NOTE:
The Support for Up to 600 Cells feature is supported only in the CDMA air-interface
technology.
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.
May 2004
Page 3
Benefits
401-612-052, Issue 18
For Enhanced RF Call Trace for 3G-1X Calls, ECP Release 21.0 (or later) must be
installed.
For Support for Up to 600 Cells, ECP Release 22.0 (or later) and Cell Release 21.0 (or
later) must be installed.
For RNC Call Trace, ECP Release 22.0 (or later) and Cell Release 21.0 (or later) must
be installed.
Hardware Requirements
There are no specific hardware requirements for the RF Call Trace features.
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.
Page 4
May 2004
Feature Description
401-612-052, Issue 18
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:
May 2004
Page 5
Feature Description
401-612-052, Issue 18
Basic RF Call Trace for 3G-1X High Speed Packet Data (HSPD) on page 24
Feature Description for Enhanced RF Call Trace for 3G-1X Calls on page 25
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.
Page 6
May 2004
Feature Description
401-612-052, Issue 18
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
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
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
May 2004
Page 7
Feature Description
401-612-052, Issue 18
For more information, refer to 401-612-422, MSC OA&M Support for 384 Cells feature.
TDMA Mode
When the RFTC feature is active, the MSC periodically sends an RF Call 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
Page 8
The ESID consists of three parts: System Identifier, ECP Identifier, and DCS Identifier.
May 2004
Feature Description
401-612-052, Issue 18
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.
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.
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:
May 2004
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.
Page 9
Feature Description
401-612-052, Issue 18
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
Time stamp
Flag that indicates if some of the data is invalid and the reason for invalid data
CDMA channel
May 2004
Feature Description
401-612-052, Issue 18
CDMA tick ID
Cell site ID
ECP ID
Pilot set
Antenna face
Pilot PN
Priority group
Received Eb/No
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.
RF Call Trace
Counter Name
May 2004
IS-95* Name
Description
8K
13K
M_F_1
full rate
MUX1_FOR_1
MUX2_FOR_1
M_F_2
MUX1_FOR_2
MUX2_FOR_2
M_F_3
MUX1_FOR_3
MUX2_FOR_3
M_F_4
MUX1_FOR_4
MUX2_FOR_4
M_F_5
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
Page 11
Feature Description
Table 2.
401-612-052, Issue 18
RF Call Trace
Counter Name
IS-95* Name
Description
8K
13K
M_F_8
1/8 rate
MUX1_FOR_8
MUX2_FOR_24
M_F_9
MUX1_FOR_9
N/A
M_F_10
erasure
MUX1_FOR_10
MUX2_FOR_26
* 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.
RF Call Trace
Counter Name
Page 12
Description
8K
IS-95* Name
13K
M_R_1
full rate
MUX1_REV_1
MUX2_REV_1
M_R_2
MUX1_REV_2
MUX2_REV_2
M_R_3
MUX1_REV_3
MUX2_REV_3
M_R_4
MUX1_REV_4
MUX2_REV_4
M_R_5
MUX1_REV_5
MUX2_REV_5
May 2004
Feature Description
Table 3.
401-612-052, Issue 18
RF Call Trace
Counter Name
IS-95* Name
8K
13K
Description
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
* 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)
Current coder/decoder type remains the same for the duration of the call. The
following coder/decoder types are currently supported:
0 = 8k voice
May 2004
Page 13
Feature Description
401-612-052, Issue 18
1 = 13k voice
2 = EVRC voice
3 = 8k Markov
4 = 13k Markov
5 = invalid SOR
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.
Page 14
May 2004
Feature Description
401-612-052, Issue 18
Table 4.
RF Call Trace
Counter Name
Description
MK_R1
full rate
MSO_E1_T1
MK_R2
MSO_E1_TD + MSO_E2_TD
MK_R3
MSO_E4_TD
MK_R4
MSO_E8_TD
MK_R5
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.
May 2004
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.
Page 15
Feature Description
Table 5.
401-612-052, Issue 18
Primary Cell Mapping for Mobile Received Markov Statistics on the Forward
Link
RF Call Trace
Counter Name
Description
MK_F1
MSO_E1_R1
MK_F2
MK_F3
MSO_E4_RD
MK_F4
MSO_E8_RD
MK_F5
MK_F6
MSO_E2_R2
MK_F7
MSO_E4_R4
MK_F8
MSO_E8_R8
MK_F9
sum of MSO_Ex_RFL +
MSO_Ex_RERR (where x=1,
2, 4, or 8)
MK_10
expected x, received
erasure
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
May 2004
Feature Description
401-612-052, Issue 18
the forward and reverse tick IDs of the respective Forward and Reverse Markov
Synchronization frames
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.
RF Call Trace
Counter Name
Description
MK_R1
full rate
MSO_E1_T1
MK_R2
MSO_E1_TD
MK_R3
MSO_E4_TD
MK_R4
MSO_E8_TD
MK_R5
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
MSO_E2_TD
* The Markov counters are those received from the mobile. For more
information, refer to the manufactures documentation.
Table 7.
RF Call Trace
Counter Name
May 2004
Description
MK_F1
MSO_E1_R1
MK_F2
MSO_E1_RD
MK_F3
MSO_E4_RD
MK_F4
MSO_E8_RD
MK_F5
expected x, received
blank & burst
Page 17
Feature Description
Table 7.
401-612-052, Issue 18
RF Call Trace
Counter Name
Description
MK_F6
MSO_E2_R2
MK_F7
MSO_E4_R4
MK_F8
MSO_E8_R8
MK_F9
excepted x, received
full rate likely +
excepted x, received y
(rate mismatches)
MK_10
expected x, received
erasure
MK_11
MSO_E2_RD
MK_12
expected x, received
frame with bit errors
* The Markov SO counters are those maintained at the primary cell. For more
information, refer to the manufacturers documentation.
Page 18
Voice:
Markov
(Phase 1):
Markov
(Phase 2):
May 2004
Feature Description
401-612-052, Issue 18
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):
The following features are described as part of RF Call Trace in CDMA mode:
May 2004
Page 19
Feature Description
401-612-052, Issue 18
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
May 2004
Feature Description
401-612-052, Issue 18
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.
May 2004
DN
Tag
Page 21
Feature Description
401-612-052, Issue 18
Polling Period
Interval Remaining
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
May 2004
Feature Description
401-612-052, Issue 18
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.
May 2004
Page 23
Feature Description
401-612-052, Issue 18
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.
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
May 2004
Feature Description
401-612-052, Issue 18
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.
May 2004
Page 25
Feature Description
401-612-052, Issue 18
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
Radio Configuration
Forward/Reverse Flag
Allocated Duration
Allocation Flags
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
May 2004
Feature Description
401-612-052, Issue 18
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 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.
May 2004
Page 27
Feature Description
401-612-052, Issue 18
Table 9.
Release 17.10
Release 18.0
(and later)
2G
CCU
3G
CCU
2G
CCU
3G
CCU
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
N/A
Yes
N/A
Yes
Yes
Yes
Yes
Yes
N/A
No
N/A
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
N/A
No
N/A
No
Yes
Yes
Yes
Yes
N/A
No
N/A
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Table 10.
Release 18.0
(and later)
3G CCU
Yes
Yes
Yes
Yes
Yes
Page 28
May 2004
Feature Interactions
Table 10.
401-612-052, Issue 18
Release 18.0
(and later)
3G CCU
Yes
No
No
No
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.
May 2004
Page 29
Special Considerations
401-612-052, Issue 18
6. Special Considerations
This section gives any special considerations of this feature.
Subscriber Perspective
The subscriber does not have any direct interaction with the RF Call Trace features.
7. Caveats
The RF Call Trace feature has the following limitations:
Page 30
May 2004
Caveats
401-612-052, Issue 18
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:
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.
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:
May 2004
Because of the possible increase in call trace message traffic, use of MDN RF
Call Trace is not recommended at times of peak traffic.
Page 31
Feature Implementation
401-612-052, Issue 18
All the analog DNs must use the same polling period.
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
DMRFCTRF Call Trace for Dual-Mode -TDMA/AMPS- Mobiles. 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.
Page 32
May 2004
Feature Implementation
401-612-052, Issue 18
May 2004
Page 33
Supplemental Information
401-612-052, Issue 18
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
AMPS
BER
CCC
CCU
CDMA
CDMA RFCT
CE
CRFCT
dBm
DCS
DMRFCT
DN
Directory Number
DPC
DRU
DVCC
ECP
EDRU
EIA
ESID
May 2004
Supplemental Information
May 2004
401-612-052, Issue 18
EVRC
FAF
FER
FLCA
GPS
IMSI
IS-54B
MAHO
MB
Megabyte
MDNRFCT
MIN
MO/HMO
MSC
OMP
OSCHED
OMP Scheduler
PN
Pseudo Noise
RCU
RC/V
RF
Radio Frequency
RFCT
RF Call Trace
RNC
RSSU
SAM
SAT
SCM
SDMAC
SO
Service Option
SOR
TDMA
TIA
TRFCT
VMAC
Page 35
Supplemental Information
401-612-052, Issue 18
References
The following Flexent/AUTOPLEX Wireless Networks documents contain information
related to the RF Call Trace feature:
Page 36
May 2004
History of Revisions
401-612-052, Issue 18
Issue 17
Issue 17 of this document provided the following changes/additions:
added 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
added 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
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:
May 2004
Availability
Supported Technologies
Feature Interactions
Appendix D - FTrfdump(1)
Page 37
History of Revisions
401-612-052, Issue 18
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
Supported Technologies
Benefits
Basic RF Call Trace for 3G-1X High Speed Packet Data (HSPD)
Caveats
Feature Implementation
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:
Availability
Feature Description
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
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:
Page 38
Availability
Appendix A - FTrftrace(1)
Appendix B - FTrfstop(1)
Appendix D - FTrfdump(1)
May 2004
Appendix A - FTrftrace(1)
401-612-052, Issue 18
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.
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.
May 2004
Page 39
Appendix A - FTrftrace(1)
401-612-052, Issue 18
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.
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.
Page 40
May 2004
Appendix A - FTrftrace(1)
401-612-052, Issue 18
-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.
-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!**
May 2004
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).
Page 41
Appendix A - FTrftrace(1)
401-612-052, Issue 18
-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.
-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&
4
5
Page 42
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.
May 2004
Appendix A - FTrftrace(1)
401-612-052, Issue 18
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.
May 2004
Page 43
Appendix B - FTrfstop(1)
401-612-052, Issue 18
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.
Page 44
May 2004
Appendix B - FTrfstop(1)
401-612-052, Issue 18
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.
May 2004
Page 45
Appendix C - FTrfclear(1)
401-612-052, Issue 18
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
Page 46
May 2004
Appendix C - FTrfclear(1)
401-612-052, Issue 18
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.
May 2004
Page 47
Appendix D - FTrfdump(1)
401-612-052, Issue 18
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/
Page 48
This option must be used when dumping the trace output of a Multiple DN session, in order to
generate consistent data.
May 2004
Appendix D - FTrfdump(1)
401-612-052, Issue 18
-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:
May 2004
Page 49
Appendix D - FTrfdump(1)
401-612-052, Issue 18
7
8
9
10
Output optionally for all 2G calls and also on 3G calls with cell releases<=R19.
11
12
This message is only applicable to 3g1x data calls in ECP releases 18 and 19.
Page 50
May 2004
Appendix D - FTrfdump(1)
401-612-052, Issue 18
rev_sup_afs:rev_sup_tfn]
14
[:rev_ebno:rev_ebno:rev_ebno:rev_ebno:rev_ebno:rev_ebno]
:_:_:_:_:_
13
14
Repeated #_of_rates.
Repeated #_of_rates.
15
16
17
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.
18
19
20
21
22
23
24
This message is only applicable to 3g1x data calls in ECP release >=20.
May 2004
Page 51
Appendix D - FTrfdump(1)
401-612-052, Issue 18
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
]
:rtd_valid[:rtd_updated]:ia_forming_width:ia_forming_width:ia_forming_width:ia_
forming_width:ia_forming_width:ia_forming_width
Field explanations::
25
26
27
28
29
30
31
Page 52
type
time
a 12-digit number showing the date and time the message was
logged, in the format mmddyyhhmmss.
cell
cells
DN
tag
Vrg
Ra
May 2004
Appendix D - FTrfdump(1)
May 2004
401-612-052, Issue 18
Ts
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
ant
paf
laf
sg
DCS
tg
mem
poll
serving
indicates if the serving cell was included in the call trace, 1=valid
or 0=invalid cell
valid
measurement
SCM
mcell
carr
SDMAC
sderr
Page 53
Appendix D - FTrfdump(1)
Page 54
401-612-052, Issue 18
X-sg Y
RCU
MAHO
#_of_nbr
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
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
MFA
Hobias
cell_CD
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
May 2004
Appendix D - FTrfdump(1)
May 2004
401-612-052, Issue 18
sgX_DTH
DCSID
the DCS number serving the neighbor cell. This is one part of the
unique identification of 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
sec_cel
valid
HO
freq
rsn
Page 55
Appendix D - FTrfdump(1)
Page 56
401-612-052, Issue 18
seq
ctype
tic
tic_hi
tic_lo
gain
elapsed
#_of_pn
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
May 2004
Appendix D - FTrfdump(1)
May 2004
401-612-052, Issue 18
pn
Pilot Pn (9 bits)
p_grp
chn_elm
p_str
trp_dly
eb_no
keep
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).
Page 57
Appendix D - FTrfdump(1)
Page 58
401-612-052, Issue 18
1/4_frm
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
ectf
iorf -
average total forward transmit power for the call (ECTF) per HO
leg. (Floating point number).
#_of_rates
#_of_f_rate
etcs
iors
num_frm
rev_sup
rev_sup_afs
rev_sup_tfn
rev_ebno Reverse
May 2004
Appendix D - FTrfdump(1)
May 2004
401-612-052, Issue 18
RfRate
RrRate
board
Itu_rcv
Itu_good
fsch_m_frm
rsch_m_frm
fsch_dtx_frm
fsch_dtx_frm
ancr_cell
ancr_paf
f_smv_mode
r_smv_mode
Page 59
Appendix D - FTrfdump(1)
num_fsch_softer
num_dtx_fsch_softer
num_fwd_entries
startime
frm_trans
401-612-052, Issue 18
frm_req
msc_asi
MSC number
fsh_smpl_softr_flag
first_pilot_pn
cellid
first_paf
RC
second_paf
second_pilot_pn
simul
fwd_rvs_flag
aloc_rate
req_rate
Page 60
Allocated rate
Requested rate
May 2004
Appendix D - FTrfdump(1)
aloc_flag
401-612-052, Issue 18
allocation flags
0-undefined
1-new burst
2-continuation
blk_rate_limit_ind
fsh_cts_denied
May 2004
Page 61
Appendix D - FTrfdump(1)
early_rel
401-612-052, Issue 18
avg_ects_softer
num_rvs_entries
num_anchor_setup
num_anchor _entries
timestamp
pilot_pn
paf
rtd_valid
Page 62
Forward average transmit power for the F-SCH for each burst
rate R during the time of the softer bursts
May 2004
Appendix D - FTrfdump(1)
401-612-052, Issue 18
rtd_updated
ia_forming_width
pktcore
RNC pktcore call. Value 1 indicates that this is a packet data call
whose frame selector is served by a RNC.
fsrnc
[ ]...
May 2004
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
Page 63
Appendix D - FTrfdump(1)
401-612-052, Issue 18
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 64
May 2004