3G RF Optimization Guide

7/23/2019 3G RF Optimization Guide

1/278

CDMA

3G Data and Capacity SolutionsRF Optimization Guide

NBSS 10.1 Draft 01.01 April 2001

411-2133-004


2/278

test


3/278

CDMA

3G Data and Capacity SolutionsRF Optimization Guide

Document number: 411-2133-004

Product release: NBSS 10.1

Document version: Draft 01.01

Date: April 2001

Copyright Country of printing Confidentiality Legal statements Trademarks

Copyright 19962001 Nortel Networks, All Rights Reserved

Printed in the United States of America/Canada

NORTEL NETWORKS CONFIDENTIAL

The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in

writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees

with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree

of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in

writing by Nortel Networks, the holder is granted no rights to use the information contained herein.

Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as

progress in engineering and manufacturing may warrant.

Legal statement:Part1




* Nortel Networks, the Nortel Networks logo, the Globemark HOW the WORLD SHARES IDEAS, and Unified Networks are

trademarks of Nortel Networks. Planet is a Trademark of Mobile Systems International (MSI)Surveyor is a Trademark of Grayson

Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.


4/278

iv Nortel Networks Confidential

411-2133-004 Draft 01.01 April 2001


5/278

Nortel Networks Confidential v

CDMA 3G Data and Capacity Solutions RF Optimization Guide NBSS 10.1

Publication history

January 2001

Issue no. 02.01.

Updated to new NBSS 9.0 Software revision

July 2000

Issue no. 01.03

NBSS 8.1 standard release

December 1999

Issue no. 01.02

NBSS 8.1 preliminary release

September 1999Issue no. 01.01

NBSS 8.2 preliminary release

August 1999

Issue no. 01.00

Initial Release

April 1999

Draft Version

Initial release for technical review


6/278

vi Publication history Nortel Networks Confidential

411-2133-004 Draft 01.01 April 2001


7/278

vii


About this document 1

This document provides technical reference material to aid in the RFoptimization of Nortel Networks 2G and 3G CDMA wireless systems. It isnot all inclusive and it should not be inferred that the information containedwill produce desired results in all cases. However, it does describe the use ofdiagnostic tools and established optimization methods that have been

developed and employed by Nortel Networks engineers and technicians.

Audience for this documentThe intended audience for this document are RF engineers and techniciansthat are responsible for optimizing new or existing Nortel Networks CDMAwireless systems.

Related documentsList of other Nortel Networks NTPs related to this document:

NTP 411-2133-121, CDMA Inter-System/Intra-BSC Soft Handoff

(ISSHO) Handbook

NTP 411-2133-130, MTX CDMA Deployment Guide

NTP 411-2133-199, CDMA NBSS Software Delta for Planners Manual

NTP 411-2133-504, CDMA 1900MHz Outdoor BTS RF TroubleshootingGuide

NTP 411-2133-535, CDMA-NBSS Operational Measurements

NTP 411-2133-560, CDMA 800MHz Schroff BTS RF TroubleshootingGuide


8/278

viii About this document

411-2133-004 Draft 01.01 April 2001


9/278

About this document ix



10/278

x About this document

411-2133-004 Draft 01.01 April 2001


11/278

xi


Contents 1

About this document viiAudience for this document viiRelated documents vii

Chapter 1Optimization Overview and Procedures 1-1Optimization Overview 1-1

Stages of Optimization 1-1

Pre-Commercial 1-2

Commercial Launch 1-2

System Growth and Maturation 1-2

Optimization Procedures 1-3

Entrance Criteria 1-3Pre-Commercial 1-4

From Commercial Launch to Maturation 1-5

Exit Criteria 1-6

Chapter 2

Initial System Parameters 2-1New Features Relevant to RF Optimization 2-1

Access Robustness Package 2-1

2-3Intelligent Zone Paging 2-3

Overhead Channel Manager (OCM) Paging Congestion Control 2-4

BTS No Call Processing Alarm Management 2-5

Intelligent Voice Services Negotiation (IVSN) 2-5

Flexible Forward F.E.R 2-7

Cell ID Expansion, InterSystemCellId 2-7

NBSS 9.0 New Settable Parameters 2-8Types of RF Optimization Parameters 2-8

IS-95/J-STD-008 as compared to Nortel Specific 2-9

Global Parameters as compared to Sector Specific Parameters 2-9

BTS and BSC Datafill Parameters 2-9

Access Mode of Parameters (C, G, S) 2-10

Values in Datafill Tables in this Document 2-11

BSC static datafill 2-11


12/278

xii Contents

411-2133-004 Draft 01.01 April 2001

SelectorBank Subsystem Managed Object (SBS M.O) 2-11

Refer to Table 2-6 above for a desription of when the following FPC parameters are

used 2-34

Radio Link Protocol Parameters for Packet Data (SBS M.O) 2-41

2-48

General SBS M.O Parameters 2-48Page Zone Table Managed Object 2-52

Packet Control Unit (PCU) Managed Object (M.O) 2-52

Pilot Beacon Sector Parameters 2-61

Search Windows 2-62

Enhanced Hard Handoff Parameters 2-77

BTS static datafill 2-83FA managed object 2-91

SECTOR (Legacy) and Advanced Sector (MetroCell) Managed Object 2-92

AccessParameters: 2-108

BTS Calibration 2-127

PN Planning 2-129

Co-Channel PN Interference 2-129Adjacent Channel PN Interference 2-130Initial Neighbor List Generation 2-131

Neighbor Configuration File, Setneighbor and Checkneighbor 2-131

Chapter 3

Data Collection 3-1RF Performance Indicators 3-1

Frame Error Rate 3-1

Mobile Receive Power 3-1

Pilot Strength (Ec/Io) 3-1Handset Transmit Power (TXPO) 3-2

Transmit Gain Adjust 3-2Ew/No Setpoint 3-2

Data Collection Tools 3-2

Simulated Loading 3-3

Forward Link 3-3

Reverse Link 3-5Drive Testing and SBS Logging 3-5

Drive Testing 3-6

Test Van RF Configuration 3-6

Shakedown 3-7

Drive Routes 3-7

Test Calls 3-8

Mobile Log Mask 3-8

SBS Logging 3-10Selector Log Mask 3-10

Data Collection Restrictions 3-12

Logging Strategy 3-13

Drive Test Data Management 3-13

Data Transfer and Tracking 3-13Conditional and Unconditional SBS Logging of Active Users 3-14

Data Collection Strategy 3-15


13/278

Contents xiii


Conditional Logging Procedure 3-15

Creating the Log Templates 3-15

Starting and Suspending the Logs 3-16

Uploading the Logs 3-17

Copying the Logs 3-18

Terminating the Logs 3-18Log Sizes for Different Attributes 3-19

BSM Logging Procedure using GUI 3-21

Data Management 3-22

Obtaining a Pilot Database Dump 3-22

Chapter 4

Data Analysis Procedures 4-1Nortel Networks RF Optimizer 4-1

Input Files 4-1

System Level Analysis (Macro) 4-1

File Level Analysis (Micro) 4-3

Datafill Audit and Shakedown 4-4Datafill Audit 4-4

Shakedown Data Analysis 4-4

System Access 4-4Access Failure Analysis 4-4

Access Success Rate 4-5

Access Parameter Tuning 4-6

Dropped Calls 4-6

Link Supervision 4-6

Analysis 4-6

Dropped Call Rate 4-7RF Coverage and Handoff Control 4-8

Soft Handoff Reduction 4-11Search Windows 4-14

SRCH_WIN_A 4-16

SRCH_WIN_N 4-18

SRCH_WIN_R 4-18

BTS AccessChannelDemodulationSearchWidth,TrafficChannelDemodulationSearchWidth 4-19

Neighbor Lists 4-19

Performance/Trend Analysis 4-22

Per-Site Analysis 4-23

Capacity 4-24

Capacity Equations for the Reverse Link 4-25

Capacity Equations for the Forward Link 4-27

Optimizing for Forward Link Capacity 4-29Hard Handoff (HHO) 4-30

Inter-Frequency HHO 4-31

Inter-Frequency Band HHO 4-31

Inter-System/Inter-BSC HHO and Inter-System SHO 4-31

CDMA-AMPS HHO 4-31HHO Triggers 4-32

HHO Optimization 4-37


14/278

xiv Contents

411-2133-004 Draft 01.01 April 2001

HHO Interaction with Traffic Distribution 4-40

Hashing to full time GSR implementation 4-43

Assumptions 4-43

Advantages 4-43

Disadvantages 4-44

Implementation 4-44Hashing to Part Time GSR Implementation 4-51

Assumptions: 4-52

Advantages: 4-52

Disadvantage: 4-52

Implementation: 4-52

Maintaining the Split 4-58Technical Info On GSR 4-58

Example:GSR Clear/Check Script 4-60

Hashing to Full Time GSR Implementation 4-61

Assumptions: 4-61

Advantages: 4-61

Disadvantages: 4-62Implementation 4-62Maintaining the Split 4-66

Maintaining the Split 4-69

Technical Info On GSR 4-69

Chapter 5 - Dropped Call and Access Failure Reasons and Solutions

5-1Successful Call 5-1

Indications in Mobile Data 5-1

Analysis with Selector Logs 5-2Access Failures and Dropped Call Reasons in Single Frequency System 5-5

Hard Handoff 5-8External Interference 5-12

Indications in Mobile Data 5-12

Appendix A- QCP Tech Mode Screen A-1Handset Monitor Mode A-1

Appendix B- Calculating Required Power Reduction for Unwanted PNB-1


15/278

Contents xv


List of Tables

Table 2-1 Possible Service Redirections 2-6

Table 2-2 Old (prior to NBSS 9.0) 16 bit InterSystemCellId 2-7

Table 2-3 New NBSS 9.0 InterSystemCellId 2-7

Table 2-4 Settable Access Modes for NBSS 9.0 BTS Parameters 2-8

Table 2-5 SelectorSubSystem MO parameters (Legacy and MetroCell

products) 2-13Table 2-6 Relationship between FPC Parameters and RC 2-31

Table 2-7 FwdPwrCtrlRefGain 2-34

Table 2-8 PWR_REP_THRESH 2-39

Table 2-9 SelectorSubsystem:RLPParameters 2-41

Table 2-10 SelectorSubsystem:RLPQParameters 2-43

Table 2-11 SelectorSubsystem:MaxFwdSCHSHOLinks 2-44

Table 2-12 SelectorSubsystem:MaxRevSCHSHOLinks 2-44Table 2-13 SelectorSubsystem:PowerControlSyncSwitch 2-44

Table 2-14 SelectorSubsystem:SCHDurationParameters 2-45Table 2-15 MODE_SELECTION_INDEX 2-46

Table 2-16 SelectorSubsystem:SCHRevDTXThreshold 2-47

Table 2-17 SelectorSubsystem:SCHSetupOverheadTime 2-48

Table 2-18 Backhaul delay 2-51

Table 2-19 Spare 3 Markov Call Functionality 2-51Table 2-20 Intelligent Zone Paging - Page Zone Table M.O 2-52

Table 2-21 Packet Control Unit (PCU) M.O 2-53

Table 2-22 Pilot Database MO Parameters (Legacy and MetroCell products) 2-55

Table 2-23 Bit positions for ExtendedBaseId 2-60

Table 2-24 CellType 2-61

Table 2-25 Datafill Values for Different Window Sizing 2-62

Table 2-26 Acceptable Search Window Combinations 2-63Table 2-27 SRCH_WIN_A/N/R parameter 2-64

Table 2-28 T_TDROP parameter 2-67

Table 2-29 T_ADD_OFFSET_A 2-69

Table 2-30 T_ADD_OFFSET_B 2-69

Table 2-31 T_DROP_OFFSET_A 2-70

Table 2-32 T_DROP_OFFSET_B 2-70Table 2-33 T_COMP_OFFSET_A 2-71

Table 2-34 T_COMP_OFFSET_B 2-71

Table 2-35 T_TDROP_OFFSET_B 2-72

Table 2-36 DELTA_3 2-72



Table 2-39 DELTA_6 2-74Table 2-40 BeaconTargetCellIdList 2-75

Table 2-41 BorderRefPilotRTDThresh 2-76

Table 2-42 BorderTargetCellIdList 2-77

Table 2-43 EHHOTARGET_CELL 2-78

Table 2-44 BTSC MO (Legacy), BTSCallProcessing MO (MetroCell), and FA MO

parameters 2-84Table 2-45 BAND_CLASS - 800 MHz 2-87


16/278

xvi Contents

411-2133-004 Draft 01.01 April 2001

Table 2-46 BAND_CLASS - 1900 MHz 2-87

Table 2-47 CDMA_FREQ - 800 MHz 2-91

Table 2-48 CDMA_FREQ - 1900 MHz 2-91

Table 2-49 Sector MO (Legacy) and Advanced Sector MO (MetroCell)

Parameters 2-92

Table 2-50 PagingChannel1: 2-102Table 2-51 MAX_REQ_SEQ 2-115

Table 2-52 MAX_RSP_SEQ 2-116

Table 2-53 BASE_CLASS 2-117

Table 2-54 ExtendedNeighborList tuple 2-119

Table 2-55 ExtendedNeighborList 2-120

Table 2-56 Radio Sector Managed Object 2-123Table 2-57 TCC/RFU MO (Legacy) and PowerManagement MO (MetroCell)

parameters 2-124

Table 2-58 Datafill Associated with NCF File 2-131

Table 3-1 Attenuation Calculation 3-6

Table 3-2 Mobile Log Mask 3-9

Table 3-3 Selector Log Mask 3-11Table 3-4 Attribute Data Rates 3-19Table 4-1 Acceptable Search Window Combinations 4-15

Table 4-2 Window Size Datafill 4-15

Table 4-3 Histogram Example 4-16

Table 4-4 Neighbor List Tuning Array Example 4-19

Table 4-5 Transmit Gain Adjust Analysis 4-23

Table 5-1 Access Failures 5-5Table 5-2 Dropped Calls 5-6

List of FiguresFigure 2-1 Flexible Power Control Array 2-12

Figure 2-2 Backhaul delay breakdown 2-50Figure 2-3 EHHOEBNOMAX Parameter 2-82

Figure 2-4 New Managed Object Relationships for NBSS 10.1 MFRM 2-83

Figure 4-1 Neighbor List Tuning 4-20

Figure 4-2 Neighbor List example 4-22

Figure 5-1 Messaging Example of Successful Call 5-3


17/278

1-1


Chapter 1Optimization Overview andProcedures 1

Optimization Overview

RF optimization is the process of engineering a wireless network to reach apre-defined level of performance and maintain this level as the systemmatures. There is no right way of performing RF optimization. There are,however time tested methods that help the engineer in improving theirnetwork.

There are three primary reasons for optimizing a network. All are related andas one aspect changes, this change has an effect on others. These reasonsinclude the following:

Improve Call Performance- This aspect includes reducing dropped callswhile increasing access completion rates.

Handoff Control- This aspect includes making sure enough handoff existsto take advantage of soft handoff gain, without using excess capacity. Thisaspect also includes setting hard hand-off boundaries as to minimize droppedcalls.

Efficient Capacity Management- This aspect includes maintaining enoughnetwork resources to meet the needs of the current customer base with theleast possible blocking.

Stages of Optimization

The RF optimization process occurs in three stages as a network develops.The optimization stages are (1) pre-commercial, (2) commercial launch, and(3) system growth and maturation. Each of these stages provide the RFengineer with a different set of objectives and tests.


18/278

1-2 Chapter 1 Optimization Overview and Procedures

411-2133-004 Draft 01.01 April 2001

Pre-CommercialThis stage of optimization is key to successful future system management.This stage sets the baseline or benchmark that RF system performance is builton from commercial launch to network maturity. There is a great deal of both

theoretical and practical applications planned during this phase. The efforts ofthis stage apply to the following:

system or cluster shakedown, de-bug, and datafill audit

RF coverage and handoff control

establish neighbor lists

minimize dropped calls

increase access completion

determine best search window settings

increase hard handoff completion rate

Note: A simulated load must be applied to the system or cluster for someperiod during this stage of optimization.

Commercial LaunchAfter the benchmark is established during the pre-commercial launch, it mustbe noted that this benchmark was set with simulated loading that may or maynot reflect actual system behavior after launch. For this reason, one mustcontinue the optimization efforts to make sure of new customer approval.

This is the first stage of optimization that reveals the personality of the

network shown as customers are added after launch. This stage is controlledby analyzing drive test data and call performance OMs. The efforts now applyto the following:


decreasing dropped calls

increasing access completion

increasing hard handoff completion

monitoring capacity and traffic growth

System Growth and MaturationOptimization is an on going process that requires constant attention. As timepasses, customers are added to the network, the topography of the areachanges, and business plans require for footprint expansion. All of theseconditions require additional optimization.

As your system develops and matures, daily monitoring of call performancemetrics is very important in determining the impact of adding more


19/278



customers. Control route drive testing will be an important factor indetermining the effect of additional system loading. These practices are key indetermining what actions must be taken. Multiple carrier deployment,capacity fill in site deployment, footprint expansion, and other decisions are

based on the results of this work.

The work during this stage of optimization look at:

integrating new sites into the existing network


monitoring capacity and traffic growth

minimizing dropped calls

maximizing access success

maximizing hard handoff success

Optimization ProceduresThis section shows possible procedures that can be used to make sure ofsuccessful completion of optimization.

Entrance Criteria

Before optimization begins there is a list of activities, referred to as entrancecriteria, that must be completed. The successful completion of your effortdepends on the accuracy and logistics of these activities. For example, if theBTSs have not been correctly calibrated, the optimization effort suffers.

The following items represent the minimum entrance requirements for asuccessful optimization exercise:

1. All BTSs must have been correctly installed and calibrated. Thecalibration values must be entered in the datafill.

2. The spectrum must be cleared down to a level of -110dBm (800MHz) or -111dBm (1900MHz) (total power per 1.25MHz) at all locations in theservice area.

3. The network must have stability. In other words, all required sectors areon the air, can originate calls, and make handoffs into and out of thesector.

4. Personnel must be available to carry out selector logging, parameterchanges, enabling or disabling OCNS, wilting or blossoming of sectors.

5. An up to date site database must be available in the prediction tool.(Planet* for example)

6. All test vehicles, tools, maps, etc. should be available; data collectiontools installed; GPS installed and calibrated.


20/278


411-2133-004 Draft 01.01 April 2001

7. A PN plan must have been created and entered in the datafill.

8. Preliminary neighbor lists must have been created and entered in thedatafill.

9. The required results (exit criteria) must have been defined.

Pre-CommercialSystems that are being optimized for the first time (before launch) require agreat deal of specialized attention. This is the time that allows theoptimization engineer the flexibility to try procedures that they can not tryafter the system is in service. The engineer can also see the system respond toboth loaded and unloaded conditions.

Note: The most common method of loading a pre-commercial system isby enabling OCNS (Orthogonal Channel Noise Simulator) in the BSM.OCNS is described in greater detail in Chapter 3.

The following is a basic list of items that must be addressed during anoptimization exercise on a pre-commercial system. The post-processing andanalysis of data collected during this stage of optimization is discussed ingreater detail in later chapters of this document.

First Set of Tests on Unloaded System (no OCNS)Note: Simulated load is NOT applied at this stage (because straysectors need to be found)

1. Perform datafill audit and shakedown.

2. Perform a full network or cluster drive while running 2 minute Markovcalls and collecting mobile and SBS selector logs.

3. OPTIMIZE SRCH_WIN_A and BTS demodulation windows based onrake finger offset analysis.

4. OPTIMIZE SRCH_WIN_N/R based on offsets in Pilot StrengthMeasurement Messages.

5. Perform the RF coverage analysis; plot handoff state (by sectors), mobileTX, mobile RX, best finger Ec/Io, per-PN plots as necessary (best finger/any finger/PSMM occurrence).

6. Perform dropped call analysis; plot locations in the data analysis tool.

7. Perform failed access analysis; plot locations in the data analysis tool.

8. Tune the neighbor lists using an automated neighbor list audit tool,dropped call or failed access analysis, and candidates that came from theRemaining Set.

9. Generate the per site Transmit Gain Adjust averages to find site problems.

10. Create baseline data for the performance and trend analysis.


21/278



11. Make all the necessary changes to the network.

12. Use spot check drives to re-create problems and validate changes.

13. If changes are small, go to second set of tests with system loaded (OCNS

enabled).14. If important system changes were made, repeat steps 2 through 12 until

required results are reached.

Second Set of Tests on Loaded System (OCNS enabled)1. Apply simulated load and perform full network or cluster drive while

running 2 minute Markov calls and collecting mobile and selector logs

2. Regenerate the RF coverage analysis plots; plot handoff state (by sectors),mobile TX, mobile RX, best finger Ec/Io, per-PN plots as necessary (bestfinger or any finger or PSMM occurrence).

3. Perform dropped call analysis; plot locations in the data analysis tool.

Note: Pay close attention to coverage related issues.

4. Perform failed access analysis; plot locations in the data analysis tool.

Note: Pay close attention to coverage related issues.

5. Create new dataset for the performance and trend analysis.

6. Perform analysis of special occurrences that are peculiar to the system.(geographic or traffic "hot spot")

Note: If the coverage control changes are acceptable, the average numberof sectors per user is not excessive, and the dropped call and access failurerates are acceptable, then initial optimization is complete. If not, make allthe necessary changes to the network and repeat from item 1.

7. Complete the performance and trend analysis.

From Commercial Launch to Maturation

The main difference between the pre-commercial stage of optimization andthe other stages is that after the commercial launch of a network, theflexibility of experimentation is lost. The changes that are made have aneffect on revenue generating customers. This fact must be kept in mind. It isalso important to remember that any change made in the network will cause a

change, positive or negative, with some other aspect of the network.

Use the following list to determine when and how to perform optimization onyour network after commercial launch.

Use the MTX OMs and BTSPerformanceData as trend analysis data tolocate problem areas.


22/278


411-2133-004 Draft 01.01 April 2001

Enable unconditional SBS logging of RTD, NeighborListTuningArrayand VitalData.

Use unconditional SBS and BTS Diagnostic logging.

If distinct MINs are suspect, enable a full SBS optimization conditionallogmask for those mobiles.

Use drive testing as a "last resort" means of describing a problem area.

Use drive testing to complete the integration of new sites.

Exit CriteriaThe required results of optimization are known as exit criteria. These valuescan vary from area to area or network to network. For the most part, the exitcriteria that are of main value are:

achieving a target dropped call rate.

achieving a target access success rate.

achieving coverage over a indicated geographic area.

achieving a target capacity.

After these exit criteria are met, the optimization effort (for the time being)can stop. Remember, however that optimization is an on going process thatdepends on the maturity and performance of the network.


23/278

2-1


Chapter 2Initial System Parameters 2

Because an important part of optimization is devoted to control of systemparameters, every effort must be made to begin with a datafill that includesthe experiences found in other customer markets.

The datafill shown in the spreadsheets available from the Nortel NetworksTechnology Applications department provides a solid starting point foroptimizing a new system.

Note: Initial default system parameters provided by Nortel Networks arecontinually evolving, based on new field experiences and trials. Alwaysconsult your Nortel technical representative for the latest datafillspreadsheets and/or parameter guides. The values given in thisdocument should not be used for system deployment but are intendedto be used for illustrative and instructional purposes only.

New Features Relevant to RF OptimizationSubsequent to the NBSS 9.0 software load are several new features withcorresponding new datafill parameters. Here is a brief summary of these newfeatures:

Access Robustness Package

The Access Robustness Package contains a number of features designed toprovide the support requirements for IS-95B and improve the radio linkperformance of the IS-95B mobile stationaccessing the system byorigination or page response.

Prior to IS-95B and NBSS 9.0, mobile accesses to the CDMA system havebeen restricted to call set-up on a single pilot. This limitation has led toincreased access failures due to significant interference of other pilots to thecurrent reference pilot where the set-up attempt is being made. The majorityof access failures can be attributed to the ineffectiveness of the standard in thefollowing areas:


24/278

2-2 Chapter 2 Initial System Parameters

411-2133-004 Draft 01.01 April 2001

i. IS-95A was not designed to allow mobiles to be in soft handoffduring call set-up

ii. Lack of diversity on the forward link in the previous situationmakes messaging vulnerable to RF channel interference and

fading

iii. The mobile may not necessarily originate on the best pilot, or thebest pilot may deteriorate and the access attempt fail.

The following feature improvements in NBSS 9.0 improve the probability ofIS-95B mobile accesses leading to successful call set-up.

1. Channel Assignment Into Soft Handoff

Each IS-95B mobile station keeps a list of up to six (6) pilots which isused to determine the best pilot to access the network.

When accessing the system on this best pilot (origination or pageresponse) the mobile reports this list of additional pilots with theircorresponding PN phases and Ec/Io strengths. This list is always a subsetof the serving pilots extended neighbor list.

The CDMA system (BSC-MSC) uses the additional pilot strengthmeasurements reported on the access channel message to allocateresources (assign traffic channels etc) for use by the mobile to establish asoft handoff while in the access state.

The list of pilots which the mobile can enter into soft handoff with is

provided in the Extended Channel Assignment Message (ECAM). TheECAM is sent on the paging channel of the primary pilot (where themobile originated the call or response was made).

The parameter MaxNumInitLinksapplies to this feature and is furtherdiscussed later in this section.

2. Access Handoff

The Access Handoff feature allows idle-mode handoff from originatingpilot to another more suitable pilot should the originating pilots Ec/Iobecome too weak during the system access state. This is in effect a hard

handoff from one pilot to another.

The MSC sends the Extended Channel Assignment Message (ECAM) tothe BTSs with the strongest reported pilots that allow access handoffs.

This information is presented to the mobile via the Extended SystemParameters Message.


25/278

New Features Relevant to RF Optimization 2-3


Access Handoff increases the probability that the mobile will receive theExtended Channel Assignment Message and consequently move to thetraffic channel.

The parameters of interest for Access Handoff are ACCESS_HOandACCESS_HO_ALLOWED_LIST which are further described later inthis section of the document.

3. Access Entry Handoff

This access improvement allows the mobile to respond to a page with anyof the cells identified as a neighbor provided that in each neighborsdatafill the Access Entry Handoff feature is enabled.

Access Entry Handoff increases the probability that a base station willreceive the mobiles page response message which further increases the

chances of successful call completion.

The parameters of interest for Access Entry Handoff areACCESS_ENTRY_HO_ORDER and ACCESS_ENTRY_HO_LIST which are further described later in this section of the document.

In general, other relevant parameters to the Access Robustness Packageinclude MIN_P_REVand P_REV.

Intelligent Zone Paging

Previous software releases have been restricted to system-wide paging withconsequently high paging channel useage. The purpose of the new IntelligentZone Paging (IZP) feature is to increase Paging Channel capacity by reducingthe number of page messages processed and sent within the CDMA network.This is accomplished in the following ways:

i. Assigning a Page Zone ID to a set of BTSs

ii. Keeping track of a mobiles current zone using Zone BasedRegistration

iii. Sending valid pages only to the BTSs located within the particularZone

iv. For MetroCell BTSs; paging only on the frequency the mobile iscurrently listening to

This functionality applies to the following paging related services:

General Page Message

Message Waiting Indicator Page Message


26/278


411-2133-004 Draft 01.01 April 2001

Short Message Service Page Message

Unique Challenge (Authentication) Page Message

In previous NBSS releases, system-wide paging was adopted followed by a

system-wide page retry for call processing terminations. With NBSS 9.0 andIZP, the system will perform a zone-based page followed by either a system-wide repage or a zone-based retry for call processing terminations.

Frequency Based PagingIn addition to the functionality described above, Frequency Based Paging isalso available with NBSS 9.0 but only with Metro Cell products. This featureallows the page message to be transmitted over a single carrier rather than allcarriers. The carrier over which the page message is transmitted is determinedby the same hashing algorithm that was used by the mobile to originally selectthe carrier. Frequency Based Paging is supported for the following messages:

General Page Message

Feature Notification

Data Burst

Authentication - Unique Challenge

Note: The feature is datafilled on a per MetroCell basis and when enabledboth the page and the repage is frequency-based. When Global ServiceRedirect (GSR) is activated, Frequency Based Paging is notperformed.Also, the feature is not performed on MetroCells with V5.2 carriers.Frequency Based Paging is not beneficial when multi-carrier MetroCellsare configured with a single paging channel.

Intelligent Zone Paging ToolNortel Networks Network Engineering Tools group have developed anIntelligent Zone Paging Tool to aid customers in the evaluation of their pagingzones. This is accomplished through characterization of Traffic and Mobilitywithin and between zones, based on previously collected SBS data. Contactyour Nortel representative for more information on this tool and itsapplication.

There are several new parameters which have been added to accomodate theIntelligent Zone Paging feature. These include: NumberofZones,

PageZoneRecord, ZoneNumber, RepageMethod, CellList,NumberofCells, CellNumber and are configurable via the PageZoneTableM.O. These parameters are futher discussed later in this section.

Overhead Channel Manager (OCM) Paging Congestion Control

The aim of this feature is to protect the base station from overload whennetwork traffic exceeds the engineering limits of the system. It will perform


27/278



this by progressively shedding paging traffic received from the MTX/BSC.The shedding of this messaging follows a priority rule, with lower prioritymessages being shedded first (eg: Feature Notification Messages FNM andData Burst Messages DBM). As congestion becomes more severe, higher

priority messages are sequentially shedded. This feature may also be referredto as the Paging Throttle Mechanism.

OCM Paging Congestion Control utilizes the following parameters in theBTSC/BTSCallProcessing M.O;

OCM_PTM_ThrottleWindow,OCM_PTM_PageMsgThreshold,OCM_PTM_CpuThreshold,OCM_PTM_CpuOverloadPageMsgThreshold,OCM_PTM_RestorePagingTimeout

These parameters are further discussed in the BTS Static Datafill later in thissection.

BTS No Call Processing Alarm Management

This new feature provides additional alarm capability on the BTS to detectand report Call Processing failures and is intended to significantly shortenproblem resolution time. Five new alarms are defined for this feature;

1. Alarm 1: When the BTS detects complete failure of call setups orcomplete call handoff failure with complete loss of call processingresources.

2. Alarm 2: When the BTS detects call setup or handoff failure rates on asector equal to or greater than the new settable parameterNoCallPAlarmThreshold.

3. Alarm 3: When a BTS has partially lost resources on a sector.

4. Alarm 4: When all sectors on a frequency have a critical NoCallP alarm.

5. Alarm 5: When any sector on a frequency has a critical NoCallP alarm.

There are two new parameters defined for this feature;NoCallPAlarmEnabledand NoCallPAlarmThreshold; both in the BTSC(Legacy) or BTSCallProcessing (MetroCell) M.O. These parameters arefurther discussed in the BTS Static Datafill later in this section.

Intelligent Voice Services Negotiation (IVSN)

This feature was first introduced in NBSS 8.0 and has been further enhancedfor NBSS 9.0. IVSN allows the system operator to specify the type of voiceservice option (vocoder type) to be used for a call, based on a combination ofthe operators and mobiles preferences.


28/278


411-2133-004 Draft 01.01 April 2001

Note: The IVSN feature does notallocate resources, then redirect andset-up new resources. All of the redirection occurs beforeany SBSresources are ever allocated for a call. Consequently, once a call is set-upwith a traffic channel, it is not possible to redirect that call to anotherservice option. Note also that a redirection is the term used in IVSN toindicate when a requested service option has been substituted with adifferent service option due to either system preference or unavailableresources.

The main advantages of IVSN are as follows:

Offers a service option that is preferred by the system (operator) but

different than the one requested by a mobile. Provides for an alternate service option when resources for a desired

service option are not available.

An overall system capacity increase is possible by redirecting Rate Set 2(13K) calls to Rate Set 1(eg: EVRC). The primary intended use for this isto redirect BASIC_13K calls to EVRC.

Most of the datafill for IVSN is accomplished in the MTX and is beyond thescope of this document. Refer to Nortel NTP 411-2133-205 and CDMANBSS Operational Measurements NTP 411-2133-535, Chapter 6 for moredetailed information.

The two RF datafill parameters relevant to IVSN are MAX_CAP_SZ(Sector/AdvancedSector M.Os) and MAX_NUM_ALT_SO(BTSC/BTSCallProcessing M.Os). These are discussed in further detail later in thissection.

Table 2-1

Possible Service Redirections

From To

EVRC EVRC, BASIC_8K, BASIC_13K, IS733_13K

BASIC_8K EVRC, BASIC_8K, BASIC_13K, IS733_13K

BASIC_13K EVRC, BASIC_8K, BASIC_13K, IS733_13K

IS733_13K EVRC, BASIC_8K, BASIC_13K, IS733_13K

NIL (Termination only) EVRC, BASIC_8K, BASIC_13K, IS733_13K


29/278



Flexible Forward F.E.RThis feature allows the system operator to specify one set of sectors with oneset of forward target Frame Error Rate (FER) and another set of sectors withan alternative forward target FER. There can be a total of two (2) sets of

sectors (one regular and one alternate) per BSC.

This feature allows a higher or lower Quality of Service (QOS) to be specifiedfor an alternate set of sectors and could be useful for sectors where there isrelatively low traffic and soft handoffs do not occur frequently. It may also bebeneficial for fixed wireless access (FWA) or hybrid (Mobility and FWA)applications.

Note: Soft Handoff updates of Flexible Forward FER are not supported.This means that the first links target FER is used for the duration of acall, even across soft handoff boundaries. This feature should only be usedfor very large sectors where handoffs occur infrequently; eg: Rural cells.

This feature makes use of a previously unused parameter ForwardGaininthe SBS Pilot Database to identify Regular or Alternate sectors. In addition,the Spare3parameter field of the SBS MO is used to set the target ForwardFER for alternate sectors. These parameters are discussed in more detail laterin this section.

Cell ID Expansion, InterSystemCellId

As part of the CellId expansion feature, the bit interpretation for theInterSystemCellIds has changed as follows:

Refer to the following table which describes the bit positions for the newNBSS 9.0 InterSystemCellId:

Table 2-2

Old (prior to NBSS 9.0) 16 bit InterSystemCellId

BC Cell Number Sector

x x x x x x x x x x x x x x x x

Table 2-3New NBSS 9.0 InterSystemCellId

BC Cell Number Sector

x x x x x x x x x x x x x x x x


30/278


31/278

Types of RF Optimization Parameters 2-9


IS-95/J-STD-008 as compared to Nortel SpecificSome parameters are defined by the standards and are found in IS-95 or J-STD-008. Other parameters are Nortel specific and are found in the NMISdocuments.

Global Parameters as compared to Sector Specific ParametersThe difference between these descriptions is important and not always easy tosee. Global parameters apply to the whole system (one BSC/MTX) and anychanges made effect the operation of the complete system. Sector specificparameters apply only to specific sectors.

If a mobile is in soft handoff with more than one sector containing differentvalues for a parameter, there are parameter related rules for which of thefollowing values are used:

6. For SRCH_WIN_A the SBS sends the widest value

7. For SRCH_WIN_N the SBS sends the widest value

8. For SRCH_WIN_R the SBS sends the widest value

9. For T_ADD, T_DROP the SBS sends the lowest or most negative value(For example, an option of -12dB and -13dB results in the SBS sendingthe more negative -13dB value.)

10. For T_TDROP, the SBS sends the maximum value

11. For T_COMP, the SBS sends the minimum value

BTS and BSC Datafill Parameters

Several parameters are datafilled in both BTS managed objects (MOs) andBSC MOs. This method of datafill is necessary because the mobile can be inone of several states when it requires this parameter information. For the mostpart, the BTS datafill parameters discussed are used by the mobile while it isin the idle state and the BSC datafill parameters discussed are used in thetraffic state.

Values in the BTS datafill appear on sync and paging channels. When themobile starts a new call, it has the settings that it got from the last sector onwhich it was idle.

Values at the BSC apply to the traffic channel. SRCH_WIN_A, T_ADD,

T_DROP, T_TDROP and T_COMP are all sent in the Extended HandoffDirection Message according to the preceding rules if the SBS detects that themobile does not have the current values.

Each time a handoff occurs, the SBS works out the new values according tothe new active set. If these values don't match what was last sent to themobile, the SBS sets the "Search Included" flag and sends the new values inthe Extended Handoff Direction Message. Currently, the "In Traffic System


32/278


411-2133-004 Draft 01.01 April 2001

Parameters Message" is not implemented. This fact makes it impossible toupdate the mobile's settings for SRCH_WIN_N/R during a call. While thesevalues can be set per sector at the BSC, the mobile only uses the values it getsfrom the paging channel.

For example, a call which originated in a rural cell with a largeSRCH_WIN_N that is carried into a urban cell with a smaller window settingdoes not update its search window until the call is released and the mobilemonitors the paging channel again.

Neighbor lists are somewhat of a special condition. As with other parameters,the settings at the BTS are for the paging channel. Because the mobile locksto one sector at a time during idle, its neighbor search procedure uses theneighbor list from that sector. When on a traffic channel, the BTS neighborlist continues to be used to until the first handoff completes. From that pointon, the mobile generates a composite neighbor list (up to a maximum of 20

entries) with the following priorities:

1. Any pilots recently removed from the active list but have not exceededNGHBR_MAX_AGE

2. The neighbor list as received on the most recent Neighbor List UpdateMessage from the BSC (although any pilots from 1 are not repeated)

Note: If the Neighbor List Update Message contains 20 entries, themobile gives priority to pilots defined in the first priority, 1, so all 20can not be used. These rules are in the IS-95 standard.

The neighbor list received from the SBS is a composite (up to a maximum of20 entries) of the neighbor lists of the sectors named in the most recentHandoff Completion Message.

Access Mode of Parameters (C, G, S)

Each parameter in the NBSS 9.0 CDMA system has a modification conditionwhich determines how and if changes can be made to that parameter. CertainBTS parameters (eg:HandoffBlockingThresholdin the Sector/AdvancedSector M.O) were previously modifiable via the BSM but would require thatthe BTS be removed from service, reloaded and then re-instated into servicewith the new modified parameter value. With the release of NBSS 9.0, most

BTS parameters are changeable on the fly meaning the parameter value canbe adjusted without taking the BTS out of service. Other parameters are onlyreadable and cannot be changed (eg: SYS_TIME). The followingdefinitions are used to describe each parameters access mode:

CREATABLE (C)......... A parameter that can be modified in value but notnecessarily on the fly


33/278



GETTABLE (G)........... A parameter value that is readable from theBSM

SETTABLE (S)............ A parameter value that can be modified on thefly which does not require taking the BTS out of service and reloading

the datafill

All parameters are in some combination of the above three access modes. Forexample,

SYS_TIME = G, .........................(value is readable or gettableonly)BCAST_INDEX = C,G ................( value is readable and also can be changedbut not on the fly)MAX_CAP_SZ = C,G,S .............(value is readable, can be changed on thefly, without reloading the BTS datafill)

The access mode for each parameter is identified in the following datafill

tables.

Values in Datafill Tables in this Document

Please note that values given in the Suggested Value column of thefollowing tables are DECIMAL values and must be converted to thecorresponding HEXADECIMAL equivalent for certain datafill tasks. Refer tothe Nortel Datafill Spreadsheets for both representations.

Note: Table cells that are shaded indicate a parameter value has beenchanged for NBSS 9.0 or the parameter is new.

BSC static datafillThis section describes the meaning and use of the RF/air interface-relatedstatic datafill at the BSC. This section does not address other forms of datafill(such as, OA&M, connectivity, MTX and so on).

RF-related parameter values are suggested starting points for networkoptimization and are not to be hard-and-fast rules. The values given in thisdocument should not be used for system deployment but are intended tobe used for illustrative and instructional purposes only.

SelectorBank Subsystem Managed Object (SBS M.O)There are considerable changes between the global power controlfunctionality of NBSS 9.0 (and previous releases) and that for NBSS 10.1 andlater versions. Due to the advent of 3G CDMA 2000 technology with releases10.1 and later, power control parameters must now be specified for variousRadioConfiguration (RC) rates (eg: RC1, RC2, RC3, RC4 and RC5). Inaddition, the previously global nature of the power control parameters is nowsettable in up to 16 different profiles which can each then be selected persector in the Pilot Database M.O. Refer to the following diagram Figure 2-1.


34/278


411-2133-004 Draft 01.01 April 2001

Figure 2-1Flexible Power Control Array

This diagram shows the various profiles (up to 16) that are contained withinthe Flexible Power Control Array within the SBS M.O. Each profile containsmany parameters relevant to the sub-profiles such as RC1 (previously RateSet 1), RC2 (Rate Set 2), RC3 FCH, RC4 SCH; as shown by the blocks insidethe appropriate profile. The name of the profile (PowerControlID) is thenused in the Pilot Database records to specify which profile to use for thatspecific sector.

Profile 16 (Pwr Control ID=15)

RC1 RC2 RC3

FCH

RC3

SCH

RC4

FCH

RC4

SCH

RC5

FCH

RC3DATA

During

192 SCH

General

Profile Specific

Pwr Control

Parameters

384 SCH

768 SCH

1536 SCH




Upto

16Diff

eren

tPow

erCon

trolProfil

esFlexible Power Control Array

NumProfiles eg: 16


35/278



Table 2-5

SelectorSubSystem MO parameters (Legacy and MetroCell products)

SELECTOR SUBSYSTEM SBS M.OParameter

Type

Parameter Name Access

Mode

Range Suggested

Value

(DECIMAL)

Note

FLEXIBLE POWER CONTROL ARRAY

NumProfiles C,G,S 0-15

PROFILE

GENERAL PROFILE SPECIFIC PARAMETERS

FlexiblePowerControlID C,G,S 0-15 Number of profile

Title C,G,S String Name of profile(eg:Default,Repeater etc)

FwdPwrCtrlRefGain C,G,S 0-255 DGUs Reference gain forForward PowerControl

RLTrafficPilotGain C,G,S -32/8 to +32/8 dB Mobile TFC powerrelative to RL Pilot

RLGain_Default C,G,S 0-255 Initial RL TFC Gainused by mobile

RADIO CONFIGURATION RC1 (Same as RateSet 1 8kb EVRC)

RC1

PrRXerror(FER%)

Reverse Full C,G,S 1/16 - 256/16% 8 0.5%

Reverse Half C,G,S 1/16 - 256/16% 24 1.5%

Reverse Quarter C,G,S 1/16 - 256/16% 40 2.5%

Reverse Eighth C,G,S 1/16 - 256/16% 40 2.5%

Reverse Unknown C,G,S 1/16 - 256/16% 8 0.5%

RRXincrease

Reverse Full C,G,S 1/256 - 4095/256 dB 42 0.164 dB

Reverse Half C,G,S 1/256 - 4095/256 dB 14 0.055 dB


36/278


411-2133-004 Draft 01.01 April 2001

Reverse Quarter C,G,S 1/256 - 4095/256 dB 7 0.027 dB

Eighth C,G,S 1/256 - 4095/256 dB 7 0.027 dB

Reverse Unknown C,G,S 1/256 - 4095/256 dB 42 0.164 dB

(value changed for NBSS 9.0)

Reverse PRXlower C,G,S 1/256 - 4095/256 dB 1562 6.1dB Ew/Nt)

Reverse PRXupper C,G,S 1/256 - 4095/256 dB 3123 12.2dB (Ew/Nt)

Reverse PRXstart C,G,S 1/256 - 4095/256 dB 2611 10.2dB (Ew/Nt)

Note: Eb/No = Ew/Nt -3.0 dB for RS1 (eg: 10.2 dB Ew/Nt = 7.2 dB Eb/No)

Forward PrTxerror C,G,S 1/16 - 256/16 dB 24 1.5%

Forward RTXincrease C,G,S 1/256 - 4095/256 dB 24 0.1 dB

Forward PTXlower C,G,S -4095/256 - 0/256 dB -3584 -14 dB

Forward PTXupper C,G,S -4095/256 - 0/256 dB -512 -2 dB

Forward PTXstart C,G,S -4095/256 - 0/256 dB -1024 -4 dB

Forward PWR_REP_THRESH C,G,S 1 - 31 frames 2 8 kbps only. Namechanged fromTxFrameErrCnt

RADIO CONFIGURATION RC2 (Same as RateSet 2 13kb)

RC2 PrRXerror(FER%)

Reverse Full C,G,S 1/16 - 256/16% 8 .5%

Reverse Half C,G,S 1/16 - 256/16% 24 1.5%

Reverse Quarter C,G,S 1/16 - 256/16% 40 2.5%

Reverse Eighth C,G,S 1/16 - 256/16% 40 2.5%

Reverse Unknown C,G,S 1/16 - 256/16% 8 .5%

RRXincrease

Table 2-5


SELECTOR SUBSYSTEM SBS M.O

ParameterType

Parameter Name AccessMode

Range SuggestedValue

(DECIMAL)

Note


37/278



Reverse Full C,G,S 1/256 - 4095/256 dB 42 0.164 dB

Reverse Half C,G,S 1/256 - 4095/256 dB 14 0.055 dB

Reverse Quarter C,G,S 1/256 - 4095/256 dB 7 0.027 dB

Reverse Eighth C,G,S 1/256 - 4095/256 dB 7 0.027 dB

Reverse Unknown C,G,S 1/256 - 4095/256dB 14 0.055 dB

Reverse PRXlower C,G,S 1/256 - 4095/256dB 2023 7.9 dB (Ew/Nt)

Reverse PRXupper C,G,S 1/256 - 4095/256 dB 3584 14.0 dB (Ew/Nt)

Reverse PRXstart C,G,S 1/256 - 4095/256 dB 3072 12 dB (Ew/Nt)

Note: Eb/No = Ew/Nt -4.8 dB for RS2 (eg: 12 dB Ew/Nt = 7.2 dB Eb/No)

Forward PrTxerror C,G,S 1/16 - 256/16dB 24 1.5%

Forward RTXincrease C,G,S 1/256 - 4095/256dB 24 0.1 dB

Forward PTXlower C,G,S -4095/256 - 0/256dB -3072 -12 dB

Forward PTXupper C,G,S -4095/256 - 0/256dB 0 0 dB

Forward PTXstart C,G,S -4095/256 - 0/256dB -512 -2 dB

RADIO CONFIGURATION RC3 (due to continuing development of 1xRTT through field trials,Suggested Values are not included at this draft revision level)

RC3 FCHData (Fundamental Channel Data)

Reverse RxFER_Full C,G,S 1/16 - 255/16 %

Reverse RxFER_Half C,G,S 1/16 - 255/16 %

Reverse RxFER_Quarter C,G,S 1/16 - 255/16 %

Reverse RxFER_Eighth C,G,S 1/16 - 255/16 %

Reverse RxFER_Unknown C,G,S 1/16 - 255/16 %

Reverse RxMinSetPoint C,G,S -16320/256 to 0/256

dB

Table 2-5



ParameterType



(DECIMAL)

Note


38/278


411-2133-004 Draft 01.01 April 2001

Reverse RxMaxSetPoint C,G,S -16320/256 to 0/256

dB

Reverse RxInitSetPoint C,G,S -16320/256 to 0/256

dB

Reverse RRXIncrease_Full C,G,S 1/256 to 4095/256

Reverse RRXIncrease_Half C,G,S 1/256 to 4095/256

Reverse RRXIncrease_Quarter C,G,S 1/256 to 4095/256

Reverse RRXIncrease_Eighth C,G,S 1/256 to 4095/256

Reverse RRXIncrease_Unknown C,G,S 1/256 to 4095/256

Reverse SCHRC3

RRXIncrease_Unknown

C,G,S 1/256 to 4095/256 (when a RL SCH is inuse)

Forward TxFER C,G,S 0 to 31 %

Forward TxFER_PktData C,G,S 0 to 31 %

Forward TxMinGain C,G,S -128/4 to +127/4

Forward TxMaxGain C,G,S -128/4 to +127/4

TxInitGain C,G,S -128/4 to +127/4

Forward TxMinSetPoint C,G,S 0/8 to 255/8 dB Eb/

No

Forward TxMaxSetPoint C,G,S 0/8 to 255/8 dB Eb/

No

Forward TxInitSetPoint C,G,S 0/8 to 255/8 dB Eb/

No

RC3 FCHData During X SCH (FCH parms different when SCH in use. See below)

During a

192 kb SCH

RxMinSetPoint C,G,S -16320/256 - 0/256

dB

RxMaxSetPoint C,G,S -16320/256 - 0/256

dB

RxInitSetPoint C,G,S -16320/256 - 0/256

dB

Table 2-5



ParameterType



(DECIMAL)

Note


39/278



During a

384 kb SCH


dB


dB


dB

During a

768 kb SCH


dB


dB


dB

During a

1536 kb SCH


dB


dB

RxInitSetPoint C,G,S -16320/256 - 0/256dB

RC3 SCHData (Supplemental Channel Data)

Table 2-5



ParameterType



(DECIMAL)

Note


40/278


411-2133-004 Draft 01.01 April 2001

192 kb

RC3 SCH

TxFER_PktData C,G,S 0 to 31 %

TxMinGain C,G,S -128/4 to +127/4

TxMaxGain C,G,S -128/4 to +127/4

TxInitGain_Offset C,G,S -128/4 to +127/4

TxMinSetPoint C,G,S 0/8 to 255/8 dB Eb/

No

TxMaxSetPoint C,G,S 0/8 to 255/8 dB Eb/

No

TxInitSetPoint_Offset C,G,S 0/8 to 255/8 dB Eb/

No

RxFER_Full C,G,S 1/16 - 511/16 %

RxMinSetPoint C,G,S -16320/256 to 0/256

dB

RxMaxSetPoint C,G,S -16320/256 to 0/256

dB

RxInitSetPoint C,G,S -16320/256 to 0/256

dB

Table 2-5



ParameterType



(DECIMAL)

Note


41/278



384 kb

RC3 SCH






No


No


No

RxFER_Full C,G,S 1/16 - 511/16 %


dB


dB


dB

Table 2-5



ParameterType



(DECIMAL)

Note


42/278


411-2133-004 Draft 01.01 April 2001

768 kb

RC3 SCH






No


No


No

RxFER_Full C,G,S 1/16 - 511/16 %


dB


dB


dB

Table 2-5



ParameterType



(DECIMAL)

Note


43/278



1536 kb

RC3 SCH






No


No


No

RxFER_Full C,G,S 1/16 - 511/16 %


dB


dB


dB









dB

Table 2-5



ParameterType



(DECIMAL)

Note


44/278


411-2133-004 Draft 01.01 April 2001


dB


dB












No


No


No

RC4 SCHData (Supplemental Channel Data)

Table 2-5



ParameterType



(DECIMAL)

Note


45/278



192 kb

RC4 SCH






No


No


No

RxFER_Full C,G,S 1/16 - 511/16 %


dB


dB


dB

Table 2-5



ParameterType



(DECIMAL)

Note


46/278


411-2133-004 Draft 01.01 April 2001

384 kb

RC4 SCH






No


No


No

RxFER_Full C,G,S 1/16 - 511/16 %


dB


dB


dB

Table 2-5



ParameterType



(DECIMAL)

Note


47/278



768 kb

RC4 SCH






No


No


No

RxFER_Full C,G,S 1/16 - 511/16 %


dB


dB


dB

Table 2-5



ParameterType



(DECIMAL)

Note


48/278


411-2133-004 Draft 01.01 April 2001

1536 kb

RC4 SCH






No


No


No

RxFER_Full C,G,S 1/16 - 511/16 %


dB


dB


dB









dB

Table 2-5



ParameterType



(DECIMAL)

Note


49/278




dB


dB












No


No


No

END OF FLEXIBLE POWER CONTROL ARRAY

RADIO LINK PROTOCOL PARAMETERS FOR PACKET DATA (SBS M.O)

RLP PARAMETERS

BufferThreshold_192 C,G,S 0 - 65535


Table 2-5



ParameterType



(DECIMAL)

Note


50/278


411-2133-004 Draft 01.01 April 2001



BufferThreshold_Releas

e

C,G,S

Init_Nak_Delay C,G,S 1 to 40 20mS frames

InterRound_Delay C,G,S 1 to 20 20mS frames

MaxSyncAttempts C,G,S 1 to 20 20mS frames

NAK_ROUNDS_FWD C,G,S 0-255

NAKS_PER_ROUND1 C,G,S 0-255



RLP_Delay C,G,S 0-255 Secs

SCH Release Hold Time C,G,S

RLPQ PARAMETERS

FwdBuffer_High C,G,S 0 - 100%

FwdBuffer_Low C,G,S 0 - 100%

FwdBufferSize C,G,S 0 - 4294967296

bytes

FwdTxOffGracePeriod C,G,S 0 - 255 20mS frames

RevBufferSize C,G,S 0 - 4294967296

bytes

RevRateXferLimit C,G,S 0 - 255

SCH DURATION PARAMETERS

FSCH_DURATION_TIME_

153600

C,G,S 0 - 255

Table 2-5



ParameterType



(DECIMAL)

Note


51/278



FSCH_DURATION_TIME_

19200

C,G,S 0 - 255

FSCH_DURATION_TIME_

38400

C,G,S 0 - 255

FSCH_DURATION_TIME_

76800

C,G,S 0 - 255

FSCH_FIXED_SCH_DUR

ATION_TIME

C,G,S 0 - 255

INFINITE_BURST_SUPP

ORT_FWD

C,G,S 0 or 1 (false/true)

INFINITE_BURST_SUPP

ORT_REV

C,G,S 0 or 1 (false/true)

MAXIMUM_SCH_DURATI

ON_TIME

C,G,S 0 - 255 20mS frames

MINIMUM_SCH_DURATI

ON_TIME

C,G,S 0 - 255 20mS frames

MODE_SELECTION_INDEX C,G,S 0 to 3

PERIOD_FUTURE_DATA C,G,S 0 - 255 20mS frames

RSCH_DURATION_TIME

_19200

C,G,S 0 - 255

RSCH_DURATION_TIME

_38400

C,G,S 0 - 255

RSCH_DURATION_TIME

_76800

C,G,S 0 - 255

RSCH_DURATION_TIME_153600 C,G,S 0 - 255

RSCH_FIXED_SCH_DUR

ATION_TIME

C,G,S 0 - 255

SCHRevDTXThreshold C,G,S 0 to 65535 20mS

frames

Table 2-5



ParameterType



(DECIMAL)

Note


52/278


411-2133-004 Draft 01.01 April 2001

SCHSetupOverheadTime C,G,S

SOFT HANDOFF PARAMETERS

MaxFwdSCHSHOLinks C,G,S 1 to 6

MaxRevSCHSHOLinks C,G,S 1 to 6

END OF PACKET DATA FUNCTIONALITY (SBS M.O)

IntersystemSystemResp

onseTimeout

C,G,S Word 32 12,000,000 micro seconds =

12 seconds

PowerControlSyncSwitc

h

C,G,S 0 or 1 (false/true) 1 enabled

Pilot Search

Parameters

NGHBR_MAX_AGE C,G,S 0 - 15 0

Minimum

Pilot

Spacing

PILOT_INC C,G,S 0 - 15 Most

systems

use 3 or 4

System Specific

Open Loop NOM_PWR C,G,S -8 to +7 dB 0 0 dB

NUM_PREAMBLE C,G,S 0 - 7 0

NOM_PWR_EXT C,G,S 0 - 1 0 Hard coded to

zero in the

software

Back Haul

Delay

BackHaulDelay C,G,S System

Specific

See notes below

Nearest

Neighbor

Spare 1 C,G,S Word 32 0 Algorithm not

recommended

Markov

functions

Spare 3 C,G,S 0-4 (0=variable, 1-4

is fixed; full half,

quarter,eighth

0 Used to control

whether Markov

uses fixed or

variable rates

END OF SBS M.O PARAMETERS

Table 2-5



ParameterType



(DECIMAL)

Note


53/278



The following table shows the relationships between the various powercontrol parameters and the Radio Configuration channels (eg: RC1 etc)

Table 2-6Relationship between FPC Parameters and RC

RC1

RC2

RC3FCH

RC3SCH

RC3FCHDuring

SCH

RC4FCH

RC4SCH

RC5FCH

RRXIncrease (Full/Half/Quarter/Eighth/Unknown)

PrRXerror (Full/Half/Quarter/Eighth/Unknown)

PrTXerror

PRXlower

PRXstart

PRXupper

PTXlower

PTXstart

PTXupper

RTXincrease

RXFER (Full/Half/Quarter/Eighth/Unknown)

RXInitSetPoint

RXMAxSetPoint

RXMinSetPoint

SCHRC3RRxIncreaseUnknown

TXFER

TXFER_PktData

TXInitGain

TXInitGainOffset


54/278


411-2133-004 Draft 01.01 April 2001

NumProfilesDescription:This is the only attribute in the Flexible Power Control Array(except for profiles themselves) and indicates the total number of datafilledFPC profiles.

FlexiblePowerControlIDDescription:Each FPC profile must have an individual ID number associatedwith it. This enables the particular profile to be selected for any sector in thePilotDatabase.

TitleDescription:The particular flavor of each profile can be given anappropriate name by datafilling this parameter per profile. For example, oneprofile could be titled IndoorMicrocells.

FwdPwrCtrlRefGain (profile specific, similar to previous TxPilotGain)Description:FwdPwrCtrlRefGain determines the forward link power controlreference point. During a call, the traffic channel gain is determined relativeto this reference . This value does not conform to an absolute power and doesnot affect the absolute power of the pilot. True output power is controlled withthe TXAttenNormal parameter at the BTS (Legacy calibration) and byindividual channel gains at the BTS Sector/AdvancedSector MOs.

TXInitSetPoint

TXInitSetPointOffset

TXMaxGain

TXMaxSetPoint

TXMinGain

TXMinSetPoint

Table 2-6Relationship between FPC Parameters and RC

RC1

RC2

RC3FCH

RC3SCH

RC3FCHDuring

SCH

RC4FCH

RC4SCH

RC5FCH


55/278



For example, assume a Legacy BTS has been calibrated so that a PilotGainsetting of 254 (DigitalGainUnits) corresponds to an absolute output power of4 watts. Then the PilotGainis reset to a DGU value of 148. This wouldcorrespond to a Pilot absolute output power calculated as shown below:

:

This is the absolute Pilot output power as set by the parameter PilotGaininthe Sector M.O. Next, assume that the FwdPwrCtrlRefGainparameterneeds to be set to a value of 164. Remember, this is only a reference power for

the forward traffic channels and is a profile specific setting, affecting all BTSsectors under the SBS M.O tagged with that specific profile.

Note: Digital Gain Units or DGUs are expressed in voltage units and notpower. This is why it is necessary to square the DGUs in the aboverelationships.

Now assume the following datafill for the forward traffic channel powercontrol parameters:

PTxUpper= 0 dBPTxStart = -2 dBPTxLower= -12 dB

With the above settings, the BTS Pilot Power output would be 1.36 watts (asset by PilotGain).

Every BTS sector under this SBS and this specific FPC profile would have a

traffic channel range relative to a FwdPwrCtrlRefGainof 1.7 watts asfollows:

Forward Traffic Channel Upper Limit ...... 1.7 watts (0dB down fromreference FwdPwrCtrlRefGain)

Forward Traffic Channel Start Power ...... 1.07 watts (-2dB down fromreference FwdPwrCtrlRefGain)

1482

2542

----------- 4 1.36W=

1642

2542

----------- 4 1.7W=


56/278


411-2133-004 Draft 01.01 April 2001

Forward Traffic Channel Lower Limit ..... 0.107 watts (-12dB down fromreference FwdPwrCtrlRefGain)

As for MetroCell BTSs, the calibration or mapping of DGUs to absolute

power is factory set. In addition there are differences in the actual powersetting parameters between older products and the newer MetroCell products.However, the relationship between FwdPwrCtrlRefGain and forward trafficchannel power dynamic range is consistent between the products.

Example datafill:

RLTrafficPilotGainDescription:Since there is now a reverse link pilot channel transmitted bythe mobile station in 1xRTT equipped systems, this parameter sets the trafficchannel gain the mobile should use, relative to the Pilot Power. This isdatafilled in units of 1/8th dB, from -32/8 to +32/8 or -4 to +4dB.

RLGain_DefaultDescription:This is the initial gain of the mobile stations traffic channel atthe beginning of a call, before closed-loop power control functionality has

initiated.

Refer to Table 2-6 above for a desription of when the following FPCparameters are used

PrRXerrorDescription:This is the target Frame Error Rate (FER) for the reverse link.

Values of PrRXerrorare required for each frame type: full-rate, half-rate,quarter-rate, eighth-rate and unknown-rate.

Note 1: The recommended target FER for half-rate frames is higher thanthat of full-rate, and the target FERs for quarter-rate and eighth-rateframes are also higher than that of full and half rate. The reason is becausethe lower the rate of the frame, the less voice data it contains, and the lessthe impact of a frame error on voice quality. In essence, the lower rateframes are more expendable from a voice quality point of view. Thisvery slight sacrifice in voice quality achieves slightly higher reverse linkcapacity.

Table 2-7

FwdPwrCtrlRefGain

Value Decimal Units

0xA4 164 Digital Gain

Units


57/278



Note 2: The target FER for unknown-rate frames (frames which are ofsuch poor quality that the Channel Element cannot determine their rate) isthe same as the full-rate target FER. The philosophy is that if theunknown-rate was actually a full-rate frame, the power control loop must

respond quickly to ensure good voice quality.

High values of this parameter result in lower voice quality and higherprobability of call drop, but also result in slightly higher system capacity andslightly larger cell sizes. The opposite is true for low values of the parameter.

RRXincreaseDescription:This parameter sets the step size of increment in the targetreverse Ew/Nt.

Note 1: The recommended step size for half-rate frames is lower than thatof full-rate, and the step sizes for quarter-rate and eighth-rate frames are

lower still. This is because the higher the rate of the frame, the more voicedata it contains, and the more the impact of a frame error on voice quality.The amount that the Ew/Ntsetpoint increases when a frame error isreceived is proportional to the amount of voice data that frame contains.This outcome is logical, because full- and eighth-rate frames occur inseries. If a full-rate frame is received in error, given that the next frame isprobably a full-rate frame also, the Ew/Ntsetpoint is increasedsignificantly because full-rate frames are most important in terms of voicequality. If an eighth-rate frame is received in error, one can increase theEw/Ntsetpoint slightly, because eighth-rate frames are expendable.

Note 2: The step size for unknown-rate frames (frames which are of suchpoor quality that the Channel Element cannot determine their rate) is thesame as the full-rate step size. The philosophy is that if the unknown-ratewas actually a full-rate frame, the Ew/Ntsetpoint must increase quickly toinsure good voice quality.

High values result in a fast response to large changes in RF conditions, butcan reduce air interface capacity caused by overshooting the Ew/Nttarget.Low values can result in a high FER because the power control loops cannotbe reliable for large changes in RF conditions quickly enough, but low valuescan increase air interface capacity.

Note: This parameter is used in all Radio Configuration (RC1, RC2, RC3FCH, RC4 FCH and RC5 FCH)

PRXlowerDescription:This parameter defines the minimum Ew/Nt(energy per Walshsymbol to total noise power spectral density) acceptable on the reverse link.Regardless of the FER, the outer loop power control algorithm is preventedfrom setting the reverse link Ew/Nttarget below this value.


58/278


411-2133-004 Draft 01.01 April 2001

The term Eb/Nt(energy per bit to total noise energy ratio) can be used to findEw/Ntas follows:

For the 8 kbps vocoder (two data bits per Walsh symbol), in dB:

For the 13 kbps vocoder (three data bits per Walsh symbol), in dB:

The values of 3 dB (RS1) and 4.8 dB (RS2) are derived from this simple

mathematical relationship shown below:

... and for Rate Set 1

The Modulation Symbol Rate of 4800 Walsh symbols per second is the samefor Rate Set 1 and 2.

High values of this parameter result in an excessively low reverse FER and amatching reduced reverse link capacity. Low values can result in an increasedcall drop rate if mobiles move into very favorable but temporary RFconditions.

PRXupperDescription:This parameter defines the maximum Ew/Ntpermitted on thereverse link. Regardless of the FER, the outer loop power control algorithm isprevented from setting the reverse link Ew/Nttarget above this value.

It is important to set this parameter to a high value for the following reason.Most (13 kbps) calls require a low Ew/Ntsetpoint, between 10 and 11dB.

EW

Nt

--------Eb

Nt

------ 3+=

EW

Nt

--------E

b

Nt

------ 4.8+=

dBvalue 1014400

4800---------------

log RateSet2 4.8dB==

dBvalue 109600

4800------------

log RateSet1 3.0dB==


59/278



However, a small fraction of calls require more. Although these calls reducenetwork capacity, failing to allow a call as much Ew/Ntas it needs, increasesthe probability of a dropped call.

High values result in a lower call drop rate but also in a lower system capacity.Low values can result in an increased call drop rate resulting from anexcessive reverse link FER.

PRXstartDescription:This parameter defines the reverse link Ew/Nttarget used at thebeginning of each call.

The outer loop power control algorithm does not vary the reverse link Ew/Ntsetpoint until the mobile acknowledges the Base Station AcknowledgmentOrder message sent on the Forward Traffic Channel at the beginning of thecall. Also, the initial setpoint required to reach a low reverse FER is not

known (it depends on the mobiles speed, the number of multipathcomponents the mobile receives, and the relative strengths of thosemultipaths). This parameter is set at its maximum with the assumption that, ifnecessary, the outer loop power control algorithm reduces the Ew/Ntsetpoint.In this way, reverse link capacity is sacrificed for call setup reliability.

A new quick reduction algorithm was introduced (NBSS 7.0) to reduce theEw/Nt setpoint faster if the additional power is not needed by the reverse linkat call set up. The algorithm decreases the set point ten times faster than thenormal decrease rate until two frame errors are encountered, at which time thedecrease rate returns to its normal value (0.006 dB).

PrTXerrorDescription:This parameter defines the target forward link Frame Error Rate(FER) which the selector uses as an input to the forward link power controlalgorithm. This FER set point is used to increase or decrease the trafficchannel gain assigned to a mobile, based on the FER reported by that mobile.There is a trade-off between this value and the voice quality, at the cost ofsystem capacity.

RTXincreaseDescription:This parameter controls the increment of increases in theforward power allocated to a mobile.

High values result in a fast response to large changes in RF conditions, butcan reduce air interface capacity caused by overshooting the forward powerallocation. Low values can result in a higher call drop rate because forwardpower control cannot respond to large changes in RF conditions quicklyenough. Low values can increase air interface capacity.


60/278


411-2133-004 Draft 01.01 April 2001

PTXlowerDescription: This parameter defines the minimum power (in dB relative tothe FwdPwrCtrlRefGainreference parameter) permitted on the forwardlink. Regardless of the forward link FER, the power control algorithm is

prevented from setting the forward link power below this value.

High values of this parameter result in an excessively low forward FER forsome mobiles and a reduction in forward link capacity. Low values can resultin an increased call drop rate if mobiles move into very favorable buttemporary RF conditions.

PTXupperDescription: This parameter defines the maximum power (in dB relative tothe FwdPwrCtrlRefGainreference parameter) permitted on the forwardlink. Regardless of the forward link FER, the power control algorithm isprevented from setting the forward link power above this value.

High values result in a lower call drop rate but also in a lower forward linkcapacity. Low values can result in an increased call drop rate.

PTXstartDescription:This parameter defines the forward link power (in dB relative tothe FwdPwrCtrlRefGainreference parameter) target assumed at thebeginning of each call. The forward link power control algorithm does notvary the forward link power until the mobile acknowledges the Base StationAcknowledgment Order message sent on the Forward Traffic Channel at thebeginning of the call. However, there is no determination what initial forward

power (PTXStart

) is high enough to generate a low forward FER. Thisparameter is set to a large value knowing that, if necessary, the forward linkpower control algorithm reduces the forward power allocation. In essence,forward link capacity is sacrificed for call setup reliability.

A new quick reduction algorithm was introduced in NBSS 7.0 to reduceforward link power faster if the additional power is not need by the forwardlink at call setup. The algorithm decreases the forward link power ten timesfaster than the normal decrease rate until two frame errors are found, at whichtime the decrease rate returns to its normal value.

PWR_REP_THRESH

Description:For Rate Set 1, this parameter determines the number ofconsecutive forward link frame errors which the mobile must count in themeasurement period before signaling a frame

3G RF Optimization Guide

Documents

Transcript of 3G RF Optimization Guide