Lucent RF Calltrace

7/30/2019 Lucent RF Calltrace

1/72

Lucent Technologies - ProprietaryThis document contains proprietary information of

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

Copyright 2004 Lucent TechnologiesUnpublished and Not for Publication

All Rights Reserved

Flexent/AUTOPLEXWireless Networks

RF Call TraceOptional Feature Description

Release 22.0

401-612-052Issue 18

May 2004


2/72

ucent ec no og es - ropr etarySee Notice on first page

Copyright 2004 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.

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/.
https://wireless.support.lucent.com/amps/rls_info/rls_doc/cd_docs/https://wireless.support.lucent.com/amps/rls_info/rls_doc/cd_docs/https://wireless.support.lucent.com/amps/rls_info/rls_doc/cd_docs/https://wireless.support.lucent.com/amps/rls_info/rls_doc/cd_docs/


3/72

Contents

May 2004 Lucent Technologies Proprietary Page iii

See notice on first page

Introduction 1

Reason for Reissue 1

Historical Record of Revisions 1

Intended Audience 1

Availability 2

Supported Technologies 3

HLR Configurations 3

Software Requirements 3

Hardware Requirements 4

Benefits 4RFCT CCU Changes to Support 3G-IX HSPD 5

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

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

Feature Description 5

RF Call Trace Data Collection 6

AMPS Mode 6

MSC OA&M Support for 384 Cells 7

TDMA Mode 8

Increased TDMA MAHO List 8

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

CDMA Mode 9Markov 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

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 21UNIX System Commands 22

15 Digit DN FeatureImpact on RF Call Trace 23

Basic RF Call Trace for

3G-1X High Speed Packet Data (HSPD) 24


24

23

2221

20

20

19

18

16

14

149

9

8

8

7

6

6

5

5

5

54

4

3

3

3

2

1

1

1

1


4/72

401-612-052, Issue 18

Page iv Lucent Technologies Proprietary May 2004


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

Overload Conditions 27

Major RFCT Metrics Summary 28

Support for Up to 600 Cells 29RNC Call Trace 29

Feature Interactions 29

Special Considerations 30

Subscriber Perspective 30

Service Provider Perspective 30

Caveats 30

Feature Implementation 32

Basic RF Call Trace for

3G-1X High Speed Packet Data (HSPD) 33


Enhanced RF Call Trace for 3G-1X Calls 33 Supplemental Information 34

Abbreviations 34

References 36

History of Revisions 37

Issue 17 37

Issue 16 37

Issue 15 38

Issue 14 38

Issue 13 38

Issue 12 38

Issue 11 39Issue 10 39

Issue 9 39

Appendix A - FTrftrace(1) 39

Appendix B - FTrfstop(1) 44

Appendix C - FTrfclear(1) 46

Appendix D - FTrfdump(1) 4848

46

44

39

39

3939

38

38

38

38

37

37

37

36

34

3433

33

33

32

30

30

30

30

29

2929

28

27

25


5/72

May 2004 Lucent Technologies Proprietary Page v


Figures

A. MDN RFCT Bandwidth formula 2121


6/72

401-612-052

Figures

May 2004 Lucent Technologies Proprietary Page vi



7/72

Tables

May 2004 Lucent Technologies Proprietary Page vii


1. RF Call Trace Availability 2

2. Mobile Forward Traffic Frame Count Definitions - Voice 11

3. Mobile Retrievable Parameters for Reverse Traffic Channels 12

4. Mobile Reverse Traffic Frame Count Definitions - Markov 15

5. Primary Cell Mapping forMobile Received Markov Statistics on the Forward Link 16

6. Mobile Reverse Traffic Frame Count Definitions - Markov 17

7. Mobile Forward Traffic Frame Count Definitions - Markov 17

8. Minimum Equivalent Polling Interval 20

9. 2G/3G Voice RFCT Capabilit ies AcrossDifferent Software Releases 28

10. 3G-1X HSPD RFCT Capabilities 2828

28

20

17

17

16

15

12

11

2


8/72

401-612-052

Tables

May 2004 Lucent Technologies Proprietary Page viii



9/72

Introduction 401-612-052, Issue 18

May 2004 Lucent Technologies Proprietary Page 1


1. Introduction

This document describes the Radio Frequency (RF) Call Trace optional feature of

Flexent/AUTOPLEXWireless Networks. This document provides the followinginformation:

Availability and special system requirements

Feature capabilities and interactions with other Flexent/AUTOPLEXfeatures

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 18 of this document provides the following changes/additions:

adds feature information for the Support for Up to 600 Cells feature [FeatureIdentifier (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 Tracefeature [Feature Identifier (FID)10668.0]:


RNC Call Trace on page 29

Abbreviations on page 34

Appendix D - FTrfdump(1) on page 48

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/AUTOPLEXWirelessNetworks.


10/72

Availability 401-612-052, Issue 18

Page 2 Lucent Technologies Proprietary May 2004


2. Availability

Refer to the following table for availability:

Table 1. RF Call Trace Availability

Feature ECP Release Notes

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

RF Call Trace for the

AMPS/TDMADual-Mode Mobiles

6.1 (or later) and Series II Cell

Release 5.1 (or later)

The default signal strength

measurements of a TDMAmobile are in IS-54B units. The

option of using dBm issupported.

RF Call Trace for the

AMPS/CDMADual-Mode Mobiles

7.0 (or later) and Series II Cell

Release 6.0 (or later)

Enhanced RF Call

Trace/Markov - Phase 2

10.0/CDMA Release 5.0

(or later)

CDMA Multiple DN 11.0/CDMA Release 6.0 andSeries II Cell CDMA Release

11.0 (or later)

Migration from the ECPto the OMP

11.0/CDMA Release 6.0 (orlater)

CDMA Adding and

Deleting DN(s) during aRF Call Trace session

enhancement

5.0/CDMA Release 15.0 and

Series II Cell CDMA Release13.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 for3G-1X HSPD

18.0 (or later) This feature is for 3G data that issupplemental in R18.0. This

feature is an enhancement of the

existing 2G Radio Frequency CallTrace (RFCT) [Feature

Identification (FID) # 2137.10].


11/72

Availability 401-612-052, Issue 18



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

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.

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 HSPDRF 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)

Support for Up to 600Cells

22.0 (or later)

RNC Call Trace 22.0 (or later)

Table 1. RF Call Trace Availability (Continued)

Feature ECP Release Notes


12/72

Benefits 401-612-052, Issue 18



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

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 asystem 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 specifiedsingle 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 ofcandidate 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 strengthmeasurements.

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 canadd and delete DN(s) from a RF Call Trace session without having to interrupt the

session.


13/72

Feature Description 401-612-052, Issue 18



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 fundamentalchannel (Ectf) and the forward transmit power on the supplemental channel (Ects).

Improved RF Call Trace for 3G-1X HSPD

The Improved RF Call Trace for 3G-1X HSPD feature provides the service provider andRadio Frequency (RF) performance engineers with measurements to optimize 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 nullframes (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 mobileframe counts for voice calls are now being enabled.

Enhanced RF Call Trace for 3G-1X Calls

The Enhanced RF Call Trace for 3G-1X Calls feature provides the service provider and

RF performance engineers measurements to optimize voice and data calls. New framecounts 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 eachburst rate when the F-SCH is in softer hand-off.

4. Feature Description

The Radio Frequency (RF) Call Trace (RFCT) optional feature provides the systemoperator with a tool that traces a mobile call from an RF perspective for the analog

(AMPS) call mode. This tool records signal strength information for a mobile asmeasured on all antenna faces of the cell sites included in a study. The data collected is

correlated with the measurements recorded at the mobile unit by means of the SystemAccess Monitor (SAM) recorder.

System operators can use these tools to analyze the mobile RF environment andfine-tune system parameters relating to handoffs and interference. An RF Call Trace

study can be executed while a mobile is driving through the system.

The following features affect certain RF Call Trace users:

AMPS Mode on page 6


14/72




CDMA RF Call Trace (CDMARFCT) on page 19

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

CDMA Adding and Deleting DN(s) During a RF Call Trace on page 20 Basic RF Call Trace for 3G-1X High Speed Packet Data (HSPD) on page 24

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

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

The following changes affect all RF Call Trace users:

new FTrfdump real-time output option

FTrftrace command option changes for CDMA MDNRFCT users

RF Call Trace data collection blocked or inhibited under certain overload

conditions (Release 21.0 and later releases)

RF Call Trace Data Collection

When a secondary CDMA Cluster Controller (CCC) receives a request from theprimary CCC to collect data for RF Call Trace, the secondary CCC checks its own CCC

Overload Status. If the CCC is in overload, the request is discarded. Similarly, if a RadioCluster 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/AUTOPLEXsystem 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) periodicallysends 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 locateradio to the specified voice channel, measures the signal quality, and detects

Supervisory Audio Tone (SAT) on each of its equipped faces. Rather than applying thenormal signal strength adjustment rules, the cell adjusts each location measurement

only by the per-cell frame gain differential.


15/72




The cell applies the normal SAT detect rules. That is, if no SAT, wrong SAT, or multipleSATs are detected on a face, the adjusted measurement for that face is set to zero.

Also, other than one of the specified cells, no measurement is returned if the specifiedDN is active on a call.

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

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

Prior to Series II Cell Release 4.3, the RF Call Trace feature provided the raw 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 atthe 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 strengthdata for analysis. This data can be used to optimize the following system settings:

Neighbor list

Values for primary Voice Mobile Attenuation Code (VMAC)

Mobile Dynamic Power Control (DPC) target level

The RF Call Trace feature has been enhanced to provide the mobile signal strength asmeasured by the serving Radio Channel Unit (RCU). In addition, with the 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 followinginformation 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 onthe fci form):

Cell Site

Antenna Faces

Srv Grp

Sub Grp

MFA

HO Bias

MSC OA&M Support for 384 Cells

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

AUTOPLEXWireless Networks to 384.


16/72




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

TDMA Mode

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

mobile to the serving cell.

The RF Call Trace feature uses readily available data at the radio. Therefore, regardlessof whether the serving cell receives the RF Call Trace Location Request message, 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 werepreviously downloaded to the mobile from the MAHO list of the current serving face.

The mobile also reports the measured Bit Error Rate (BER). The cell reports the signalstrength, the BER, and the Frame Error Rate (FER) as measured by the serving 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 isprovided 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

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 IncreasedTDMA MAHO List feature adds the following enhancements:

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


17/72




Enhances the capabilities of the RF Call Trace feature by allowing a mobile beingserved 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 whenless than 24 handoff neighbors are specified by the service provider.

These changes are supported by an increase in the maximum number of entries in the

Measurement Order/Hyperband Measurement Order (MO/HMO) message sent to IS-136 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 downlinkchannel 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 selectedby the FLCA algorithm for assignment to calls is improved.

For more information on this feature, refer to 401-612-311, IncreasedTDMA 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 inengineering and troubleshooting Flexent/AUTOPLEXcell 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 activeset 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:

Pprimary antenna face: The primary antenna face is the antenna face that isconsidered 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 andreverse traffic is transported between the mobile and speech handlersimultaneously via the primary and all secondary antenna faces. The secondary

antenna faces are labeled S1 through S5 based on the order in which they wereadded to the call.


18/72




Ccandidate antenna face: A candidate antenna face is an antenna face forwhich 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 facemust be populated in the CDMA neighbor list (fci form) for either the primary or

one of the secondary antenna faces. 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, thesystem 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 tripdelay 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 andis 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 pilotstrength to the OMP. The primary cell also responds with cell and mobile counts.

Feature activation is relevant to the call mode. A call may be initially assigned to 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 upto 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 theCDMA 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 allmeasurements 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 OMPrequest to the mobile/cell is listed as follows.

Refer toField explanations in Appendix D under the heading Optionson page 44, fora more complete list of field reporting information.

Serving cell site ID

Time stamp

Call trace 10-digit directory number (DN)

Tag associated with the call trace

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

Station class mark (SCM)

CDMA channel


19/72




CDMA traffic sequence number

Current voice coder/decoder rate

CDMA tick ID

CDMA primary digital gain

CDMA elapsed time

Cell site ID

ECP ID

Pilot set

Antenna face

Pilot PN

Priority group

Channel element (CCC-CCU-CE)

Pilot strength measurement

Round trip delay

Received Eb/No

Keep indicator identifies active candidate member(s)

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

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

Mobile retrievable parameters for forward traffic channels are listed in Table 2 on

page 11:

Table 2. Mobile Forward Traffic Frame Count Definitions - Voice

RF Call TraceCounter Name

Description IS-95* Name8K 13K

M_F_1 full rate MUX1_FOR_1 MUX2_FOR_1

M_F_2 1/2 rate dim & burst MUX1_FOR_2 MUX2_FOR_2



M_F_5 blank & burst MUX1_FOR_5 MUX2_FOR_5

M_F_6 1/2 rate MUX1_FOR_6 MUX2_FOR_11



20/72




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 eachpolling interval. All of the frame counts that are displayed for the mobile, except for the

counts in the firstresponse message, are the difference between current and previous

polls. The frame counts that are displayed for the mobile in the first response messageare notthe difference between the current and previous poll because there are no

previous counts to use as a base to determine the difference. Because mobile countersare not reset, the frame counts that are displayed for the mobile in the first 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 thanone 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 onpage 12:


M_F_9 full rate likely 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 Wide-band Spread Spectrum Cellular System plus Telecommunications Sys-

tems Bulletin: Support for 14.4 Kbps Data Rate and PCS Interaction forWideband Spread Spectrum Cellular Systems, February 27, 1996.

Rate indicates the rate of the primary data. For example, 1/2 rate dim

and burst means that the frame was a full rate dim and burst frame with 1/

2 rate primary data.

Table 3. Mobile Retrievable Parameters for Reverse Traffic Channels



M_R_1 full rate MUX1_REV_1 MUX2_REV_1

M_R_2 1/2 rate dim & burst MUX1_REV_2 MUX2_REV_2



M_R_5 blank & burst MUX1_REV_5 MUX2_REV_5

Table 2. Mobile Forward Traffic Frame Count Definitions - Voice (Continued)




21/72




Cell reverse traffic frame statistics from each serving cell site (before the frame

selection process) and from the primary cell site (after the frame selectionprocess)

Number of 9600 bps frames without detected errors

Number of 9600 bps frames with bit errors

Number of frames with insufficient-quality-to-decide-uponrate

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. Thefollowing coder/decoder types are currently supported:

0 = 8k voice

M_R_6 1/2 rate MUX1_REV_6 MUX2_REV_11



* The IS-95 names are from the following EIA/TIA Standards docu-

ments: Mobile Station-Base Station Compatibility Standard for Dual-ModeWideband Spread Spectrum Cellular System plus Telecommunications

Systems Bulletin: Support for 14.4 Kbps Data Rate and PCS Interactionfor Wideband Spread Spectrum Cellular Systems, February 27, 1996.

Rate indicates the rate of the primary data. For example, 1/2 rate dim

and burst means that the frame was a full rate dim and burst frame with

1/2 rate primary data.

Table 3. Mobile Retrievable Parameters for Reverse Traffic Channels (Continued)




22/72




1 = 13k voice

2 = EVRC voice

3 = 8k Markov

4 = 13k Markov

5 = invalid SOR

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 thebase station. A Markov test can be performed at a fixed data rate (full-, half-, quarter-,

or eighth-rate) or a variable data rate. The selection of data rate of each packet in thevariable-rate test is governed by a pseudo-random process. The contents of 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 thereceiving side can reproduce the same packet that the transmitting station generates.

The Markov SO counts the number of various frames that are transmitted on the trafficchannel. The Markov SO also counts the number of various frames that are received on

the traffic channel and the number of bit errors found by comparing the information bitsthat are received with the locally generated information bits.

A mobile may initiate a Markov SO test for Rate Set 1 (8Kbps) or Rate Set 2 (13Kbps)

at call setup time. The cell assigns the default rate (fixed full rate) to the Markov test.

The following Markov Service Options are currently supported:

For Rate Set 1 (8Kbps)

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 duringvoice 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 andreported from the Multiplex layer priorto Markov frame rate and frame content analysis.

Enhanced RF Call Trace/Markov - Phase 1

The Enhanced RF Call Trace/Markov - Phase 1 feature provides the ability to retrievemobile station forward and reverse frame statistics that are collected at the cell during

New 8K and New 13K Markov calls and makes these statistics available to RFCT. Cellcounts remain as multiplexor statistics in this phase.


23/72




This enhancement makes use of the Service_Option_Control message counterretrieval mechanism to collect and compute the required RFCT statistics. This

mechanism allows for the retrieval of all required vector sets2 and manages datacollection such that counter retrieval requests to the mobile are done at the appropriate

Markov synchronization frames.

NOTE:Because the retrievable Markov statistics for the mobile are updated once per Markovsynchronization 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 screendisplay. See Table 4 on page 15 and Table 5 on page 16 for specific mapping details.

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

Table 4. Mobile Reverse Traffic Frame Count Definitions - Markov


Description Markov Counter* Name

MK_R1 full rate MSO_E1_T1

MK_R2 full rate & 1/2 rate dim &

burst

MSO_E1_TD + MSO_E2_TD

MK_R3 1/4 rate dim & burst MSO_E4_TD


MK_R5 blank & burst (all rates) sum of MSO_Ex_TB (where

x=1, 2, 4, or 8)

MK_R6 1/2 rate MSO_E2_T2



* The Markov counters are those that are received from the mobile. For more

information, refer to the manufacturers documentation.


24/72




Enhanced RF Call Trace/Markov - Phase 2

In addition to the capabilities described under Enhanced RF Call Trace/Markov - Phase1, the Enhanced RF Call Trace/Markov - Phase 2 feature provides the ability to 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 calltype (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:

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

Table 5. Primary Cell Mapping for Mobile Received Markov Statistics on the Forward

Link



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, receiveddim & 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



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.


25/72




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

The existingMarkov data retrieved in this phase is mapped into a new RFCT response

message which also includes the additional data previously described. See Table 6 onpage 17 and Table 7 on page 17 for specific mapping details.

Table 6. Mobile Reverse Traffic Frame Count Definitions - Markov



MK_R1 full rate MSO_E1_T1

MK_R2 full rate dim & burst MSO_E1_TD



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





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

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



MK_F1 expected full, receive

full

MSO_E1_R1

MK_F2 expected full, received

dim & burst

MSO_E1_RD


dim & burst

MSO_E4_RD


dim & burst

MSO_E8_RD

MK_F5 expected x, received

blank & burst

sum of MSO_Ex_RB (where

x=1, 2, 4, or 8)


26/72




Calculating Frame Error Rates

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

table::

MK_F6 expected 1/2, received1/2

MSO_E2_R2

MK_F7 expected 1/4, received1/4

MSO_E4_R4


1/8

MSO_E8_R8

MK_F9 excepted x, receivedfull rate likely +

excepted x, received y(rate mismatches)

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

MSO_Ex_Ry (wherex=1, 2, 4, or 8 and

y=1, 2, 4, or 8)


erasure

sum of MSO_Ex_RE (where

x=1, 2, 4, or 8)

MK_11 expected 1/2, receiveddim & burst

MSO_E2_RD


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.

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

Markov

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

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

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




27/72




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

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

CDMA RF Call Trace (CDMARFCT)

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

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

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

Session

CDMA RF Call Trace (CDMARFCT)

The CDMA RF Call Trace (CDMARFCT) feature (for AMPS/CDMA mode) is used totrace a mobile call that is operating in the Code Division Multiple Access (CDMA) mode

and is based on AMPS/TDMA RF Call Trace with two new message types for requestand response. CDMA RF Call Trace also supports the reporting of Markov 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:

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

Markov Service Option (SO), which provides pseudo-random datafor testing thetraffic channel between the mobile station and the base station. Phase 1

provides the ability to retrieve mobile station forward and reverse frame statisticscollected 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 datafor 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 theMarkov packet processing function and make them available to RFCT.

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

Markov(Phase 1)

&(Phase 2):

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

all six rows)


28/72




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 designatedCDMA 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 theCDMA 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 anenhancement 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 RFCall 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:

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

Table 8. Minimum Equivalent Polling Interval

Polling Interval Number of DNs

2 seconds 1 to 4 DNs





29/72




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 theCDMA 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 Numberof DN versus the Polling-Period is represented by the following equation:

where N is the number of DNs in the RF Call Trace session, and Polling Period iis the

requested polling period of the ith 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 allsubsequent 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 logrecords 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 thelog file.

NOTE:The real-time output capability has been moved to the FTrfdump command. TheFTrftrace -o real-time option is not supported for MSCs with the CDMA 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 foreach call in the RFCT session:

DN

Tag

N

12 per second

i=1PollingPeriodi


30/72




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 UNIXsoftware commands that are usedto

initiate or add DNs (FTrftrace)

stop/delete DNs (FTrfstop) obtain outputs (FTrfdump) from the RF Call Trace feature

to delete log file records (FTrfclear)

FTrftrace Command

The FTrftrace command is the main UNIX System function that controls the RF CallTrace feature. Once invoked, FTrftrace verifies that the feature is activated in the

Feature Activation File (FAF). FTrftrace then checks the command line input andsends a message to the Administrative Call Processing Data Base Node (ACDN) to

begin call trace measurements. If any errors are detected, FTrftrace terminates andprints 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 iscollected, 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 formeasurements, along with the measurement rate and total measurement interval. The

user may also specify the use of the serving cells neighbor-1 neighbors in AMPSmode.

When the CDMA MDNRFCT FAF is marked active, the FTrftrace command can beused to add one or more DNs to the active session. Also, with the -s option the status

of a particular session and the available bandwidth for adding a single DN are available.


31/72




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 occurswhen 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 morethan 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 Bcontains the commandinformation 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 (FTRFTRACE0and FTRFTRACE1 located in the/omp-data/logs/rfct/directory) for matches based on

either the mobile DN or a message tagthat 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 Dfor the FTrfdump command and its options, along with samples ofboth the formatted and raw ASCII outputs.

NOTE:When the CDMA MDNRFCT FAF is active, the real-time output capability (-o option) 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 Cfor 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 10-Digit 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 specifiedfor 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:


32/72




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 isbecause only a 10-digit DN can be transformed into a MIN that is used for paging.

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

(HSPD)

The Basic RF Call Trace for 3G-X HSPD feature builds on additions made previously 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 waspreviously placed in the Eb/No field.)

This feature enables the display (verbose output and WatchMark Prospect for LucentTMsoftware 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 measurementsdisplayed by this feature for each burst rate (2x, 4x, 8x, and 16x):

the forward average transmit power for the Forward Supplemental Channel (F-

SCH) for each burst rate during the time of the burst (4 values)

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

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

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

the number of R-SCH frames received during the interval for each burst rate (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.


33/72





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 measurementsdisplayed by the Improved RF Call Trace for 3G-1X HSPD feature:

1. avg_ior_fwd - average forward transmit power

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

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

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

rate

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

6. num_sch_Itu - number of LTUs received by the mobile

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

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

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

Release 20.0 also supports the following 3G displays:

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

avg ects (F-SCH) - forward average transmit power for the F-SCH for each

burst rate during the time of the burst (4 values)

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

rsch fec per leg (R-SCH) - the average Frame Error Counts (FEC) 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 burstrate (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 6existing 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 thecapability of testing a 3G-1X system to provide time stamp burst information.


34/72




The Enhanced RF Call Trace for 3G-1X Calls feature allows the display (verbose andraw formatted outputs) of new data values for 3G HSPD calls and continues to support

the same display for 2G and 3G voice calls. There are five new data measurementsdisplayed by the Enhanced RF Call Trace for 3G-1X Calls feature:

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

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

3. NSFDTXSofter - The number of DTX F-SCH frames in softer hand-off 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 noanchor 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-directionand 12 reverse-direction bursts. Each structure contains

Start Time

Requested SCH Rate

Radio Configuration

Forward/Reverse Flag

Allocated SCH Rate

Simultaneous FCH Flag

Allocated Duration

F-SCH Simplex/Softer Flag

F-SCH Simplex or First Softer Path Information

F-SCH Second Softer Path Information (if any)

Allocation Flags

Resource Block/Rate Limit Indicator

Early Release Indicator

F-SCH Continuation Denied Indicator

Actual Duration (frames, both normal and early releases)

When the primary transfer occurs, number 1 through 5 are transmitted from the old

primary to the new primary. Before a secondary leg drops, the Enhanced RF Call Tracefor 3G-1X Calls feature sends NSFFSofter, NSFDTXSofter, and Forward burst

information to the primary cell.


35/72




Release 21.0 also supports the following 3G displays:

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

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

num fsch frames (F-SCH) - the number of F-SCH frames transmitted during

the interval for each burst rate (4 values)

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

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

rate (4 values)

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

avg_ior_fwd - average forward transmit power

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

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

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

num_rsch_mob_frames - number of R-SCH mobile frames transmitted 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, orPrimary CCC are in overload.

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


36/72




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)

2GCCU

3GCCU

2GCCU

3GCCU

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

Traffic power (2G) Yes Yes Yes Yes

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

known as Ectf, is not available in the rawoutput format in R17.1, but is available inR18.0.]

N/A Yes N/A Yes

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

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

Call status info Yes Yes Yes Yes

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

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

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

Round trp delay (3G call) N/A No N/A NoMultiple 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


37/72

Feature Interactions 401-612-052, Issue 18



Support for Up to 600 Cells

The Support for Up to 600 Cells feature provides the capability to expand the cell limitfor the Flexent/AUTOPLEXWireless Networks from 384 to 600.

For more information, refer to 401-612-648, Support for Up to 600 Cells.

RNC Call Trace

The RNC Call Trace feature supports the call trace functionality on the RNC. This

functionality is important in debugging the RNC system for errant behaviors. The RFCall Trace is invoked from the Call Processing/Database Node (CDN) and the Radio

Control Server (RCS). The RCS and the CDN provide the RNC information about this

call. There is no direct impact to the RNC hardware or software for this type of trace.

5. Feature Interactions

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

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

CDMA Multiple DN RF Call Trace support for AMPS mobiles is dependent on the 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 Tracedoes not record information for TDMA and AMPS mobiles on TDMA cells (APXBx.xx).

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

Call status info Yes

Reverse Eb/No (RFCH/RSCH) No

Forward Pilot Ec/Io No

Round trip delay No

Multiple Dial Number RFCT Yes

Table 10. 3G-1X HSPD RFCT Capabilities

Metric Release 18.0(and later)

3G CCU


38/72

Special Considerations 401-612-052, Issue 18



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

CDMA RF Call Trace works with the CDMA Circuit-Mode Data service. The 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.

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 FTrfclearUNIX

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 toschedule a call trace for later execution.

The OMP shell and OSCHED can be accessed through the MISCELLANEOUS

APPLICATIONS item in theOMP main menu. On-line manual pages for these UNIX

commands may be obtained through the mancommand 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/ompenvto obtain a consistent environment.

7. Caveats

The RF Call Trace feature has the following limitations:


39/72

Caveats 401-612-052, Issue 18



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

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

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

NOTE:If the Multiple DN RF Call Trace feature is active, still only one RF call trace session per

system can be active at any one time. However, multiple users can add and delete DNsfrom the active session.

CDMA IMSI

The RF Call Trace feature has the following limitations when the CDMA Full

International Mobile Station Identity (IMSI) optional feature is activated:

The technician enters the DN of the mobile as part of the RF Call Tracecommand to specify the mobile whose call is to be traced. If the MSC does 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 MINand 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 programmedwith only a True IMSI, then the trace fails.

When the CDMA Full IMSI feature is activated, due to the preceding limitation,

RF Call Trace cannot be done for some CDMA calls that are handed off toanother MSC. For a RF Call Trace attempted at the target MSC for a hard

handoff or at the remote MSC for a soft or semi-soft handoff, the trace can beperformed only if the mobile is programmed with a MIN-based IMSI and the 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 aroaming mobile that is programmed with only a True IMSI.

RFCT for Dual Mode

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

All the limitations of the RF Call Trace feature.

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

Multiple DN RFCTB

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

Because of the possible increase in call trace message traffic, use of MDN RF

Call Trace is not recommended at times of peak traffic.


40/72

Feature Implementation 401-612-052, Issue 18



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 3G-1X

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 oldand new cells during the RFCT session.

In addition, the cells themselves must be able to handoff with other cells running oldersoftware loads. The inter-cell messaging must be backward compatible so that 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 Markovenhancements (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 theRF 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 alsobe marked active. The CDMA MDNRFCT feature does not record information for

TDMA cells (APXBx.xx). CDMA MDNRFCTFAF 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.


41/72

Feature Implementation 401-612-052, Issue 18



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 suppor ted with the FAF. No new FAFs are required forthis feature.


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 arerequired for this feature.

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 arerequired for this feature.


42/72

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.

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


43/72




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

RNC Radio Network Controller

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


44/72




References

The following Flexent/AUTOPLEXWireless Networks documents contain information

related to the RF Call Trace feature:

401-610-009, System Capacity Monitoring and Engineering Guidelines

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

401-612-648, Support for Up to 600 Cells


45/72

History of Revisions 401-612-052, Issue 18



10. History of Revisions

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

document.

Issue 17

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

added feature information for the Enhanced RF Call Trace for 3G-1X Callsfeature (Feature Identifier 2137.5):


Supported Technologies on page 3

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

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

Feature Interactions on page 29

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 3G-

1X HSPD feature as of ECP Release 20.0. For changes as a result of the Improved RFCall Trace for 3G-1X HSPD feature, refer to the following sections:

Availability




Major RFCT Metrics Summary

Feature Interactions


Appendix D - FTrfdump(1)


46/72

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


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&MSupport 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 TDMAMAHO List feature, refer to the following sections:

Availability

Increased TDMA MAHO List

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

15 Digit DN FeatureImpact on RF Call Trace

Appendix A - FTrftrace(1)

Appendix B - FTrfstop(1)

Appendix D - FTrfdump(1)


47/72

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 CDMA6-way Soft Handoff RF Call Trace Reply (type 17).

Issue 9

This document was reissued to include information required for the ECP Release 11.0/

CDMA Release 6.0 feature Multiple DN RF Call Trace. This feature impacts CDMA andAMPS RF Call Trace. Additionally, this document is being reissued to include

information relating to the migration of the RF Call tool from the ECP to the Operationsand Maintenance Platform (OMP). This feature impacts all call modes including AMPS,

AMPS/TDMA, and AMPS/CDMA. This document is also being reissued to include

information about interactions with the CDMA Circuit-Mode Data optional feature.

11. Appendix A - FTrftrace(1)

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

Name

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

Synopsis

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

[-F forward rate] [-R reverse rate]

FTrftrace [-s status]

Description

FTrftrace allows a service provider to make power level measurements. When theMultiple DN FAF is active (CDMA/Analog) the command allows the user to start a new

trace, add DNs to an existing session (for a maximum of 10), and obtain statusinformation of current traces along with available bandwidth.


48/72

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 individualDNs 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 -clist. 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 appeartogether 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 messagecontaining the measured pilot strength to the ECP. This message contains the CDMAneighbor list that includes up to 12 measurements per serving cell.

For CDMA calls, the -c, -f and -n options will be ignored. If the cell is in the middle of aCDMA-to-Analog handoff, hard handoff or primary transfer, and unable to get a

measurement, no measurement will be recorded for this instance. The cell may eitherrespond 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 isalways 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 FTrfdumpcommand is used to dump the data to the standard output device.

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

Documents

Lucent RF Calltrace