Guide to CDMA 1X EVDO BSS Network Planning Parameter Configuration-20050820-C-1.0

7/22/2019 Guide to CDMA 1X EVDO BSS Network Planning Parameter Configuration-20050820-C-1.0

1/88

Document No. Product name

Intended audience Huawei customers Product version

Drafted by Document version

Guide to CDMA 1x EVDO BSS Network

Planning Parameter Configuration

Prepared by Radio network planning department Date August 2005

Reviewed by Radio network planning department Date August 2005

Reviewed by Date

Approved by Date

Huawei Technologies Co., Ltd.

All rights reserved


2/88

Table of Contents

Chapter 1 About This Document ............................................................................................... 6Chapter 2 System Parameters ................................................................................................... 7

2.1. Sector Parameters..................................................................................................... 72.2. Control Channel Parameters ................................................................................ 152.3. Neighbor AN Parameters........................................................................................ 16

Chapter 3 Access Parameters................................................................................................... 19Chapter 4 Power Control Parameters..................................................................................... 34

4.1 Power Control Parameters ............................................................................................. 34Chapter 5 Handoff Parameters................................................................................................. 49

5.1 Module Handoff Parameters.................................................................................. 495.3 Carrier Configuration Negotiation Handoff Parameters ................................... 535.4 Sector Carrier Idle Handoff Parameters .............................................................. 645.5 Same-frequency Neighbor Handoff Parameters ................................................. 675.6 Algorithm Module Handoff Parameters ............................................................... 72

Chapter 6 Configuration Negotiation Parameters .............................................................. 816.1 Global Configuration Negotiation Parameters ............................................................ 816.2 Service Parameters ......................................................................................................... 836.3 Carrier Configuration Negotiation Parameters ........................................................... 84


3/88

Guide to CDMA 1x EVDO BSS Network Planning Parameter _v1.0 For internal use only

2006-06-01 All rights reserved Page 3 of 88

Guide to CDMA 1x EVDO BSS Network Planning

Parameter Configuration

Key words: EVDO, parameter configuration, configuration negotiation, power control,

and handoff

Abstract: This document gives an in-depth description of the relevant parameters in

EVDO network planning, suggestions on parameter configurations, and advantages &

disadvantages of different configurations. It provides references for network

optimization engineers to make the best of these radio resource management

algorithms to optimize the network coverage, network capacity and performances of

traffic measurement indexes.

Acronyms and Abbreviations:

AN Access Network

ANID Access Network Identifiers

AT Access Termination

ATI Access Termination Identifier

BTS Base Transmitter Station

BSC Base Station Controller

DRC Data Rate Control

FMR Frame Processing Board

HRPD High Rate Packet Data

IMSI International Mobile Subscriber Identity

MAC Medium Access Control

MATI Multicast Access Termination Identifier

NAI Network Access Identifier

NID Network Identification

PCF Packet Control Function

PDSN Packet Data Serving Node


4/88



PER Packet Error Ratio

PZID Packet Zone Identification

RA Reverse Activity

RATI Random Access Termination Identifier

RLP Radio Link Control

RPC Reverse Power Control

RRI Reverse Rate Indicator

SID System Identification

UATI Unicast Access Termination Identifier


5/88

Note:

This guide is used only by the customers of Huawei-related products. Thecustomers must conform to the non-disclosure agreement entered by two parities.

No part of this document may be reproduced or transmitted in any form or by anymeans without prior written consent of Huawei Technologies Co., Ltd.


6/88



Chapter 1 About This Document

In this guide, the corresponding BSC version is BSC6600-- OMCV200R001C02B014.

The fields about parameters in this guide are explained as follows

[Type] This field specifies the parameter type: An algorithm parameter or an Um

interface parameter. For an Um interface parameter, the system message that

contains the parameter and corresponding domain are given. For the configuration

negotiation parameter, the default value of system is also provided.

[Range and unit]This field specifies the range of the parameter. The value range is

closely related to the data structure.

[Operating range]This field specifies the allowable adjustment range of parameter in

practice. Modify the parameter within the above available range during the network

optimization.

[Recommended value]It is a default value of system, but not always applicable in

any case. In combination with the practical requirements, refer to the description of

Setting tradeoff to define the parameter value. If the default value is inconsistent

with recommended value in this guide, the recommended value prevails.

[Setting tradeoff] This field means the effect after increasing or decreasing the

parameter based on recommended value.

[Remarks]This field describes further the meanings of some parameters.


7/88

C hapter 2 System Parameters

2.1. Sector Parameters

SUBNETMASK (Subnet Mask)

[Description]

Refer to AN subnet mask of EV-DO carrier determined by [Cell ID], [Sector ID] and

[Carrier ID].

[Type]

Um interface parameter, and sent in SubnetMask of SectorParameters Message.

[Command name]

MOD DOSPM

LST DOSPM

[Range and unit]

0104

[Operating range]

0104

[Recommended value]

Set the value as required.

[Setting tradeoff]

None

DOLTMOFF (Local Time Offset)

[Description]

AN sets the parameter as offset of local time offset system. The set parameter

value is in the unit of 30 minutes. The unit is automatically converted into minute


8/88



when the system delivers a message, indicating the symbol number in binary

supplemental code. The system adopts Greenwich Mean Time (GMT) to represent the

parameter. The East time zone adopts "GMT+ time" and West time zone adopts"GMT-time". For example, GMT+08:00andGMT-05:00.

[Type]

Um interface parameter, and sent in the LocalTimeOffset of SectorParameter

Message.

[Command name]

MOD DOSPM

LST DOSPM

[Range and unit]

063 (corresponding to -32 31), in the unit of 30 minutes

[Operating range]

063

[Recommended value]

Refer to time zone setting of system. Default value is set to 48, that is, LF4848

(GMT+08:00)

[Setting tradeoff]

None

[Remarks]

The time offset settings of each time zone is shown below:

LF88(GMT-12:00) --GMT-12:00

LF1010(GMT-11:00)

LF1212(GMT-10:00)

LF1414(GMT-09:00)

LF1616(GMT-08:00)

LF1818(GMT-07:00)


9/88



LF2020(GMT-06:00)

LF2222(GMT-05:00)

LF2424(GMT-04:00)

LF2626(GMT-03:00)

LF2828(GMT-02:00)

LF3030(GMT-01:00) --GMT 01:00

LF3232(GMT+00:00) --GMT

LF3434(GMT+01:00) -- GMT+01:00

LF3636(GMT+02:00)

LF3838(GMT+03:00)

LF4040(GMT+04:00)

LF4242(GMT+05:00)

LF4444(GMT+06:00)

LF4646(GMT+07:00)

LF4848(GMT+08:00)

LF5050(GMT+09:00)

LF5252(GMT+10:00)

LF5454(GMT+11:00)

LF5656(GMT+12:00) -- GMT + 12:00

DOREDIRECTAT (Redirection Identification)

[Description]

Refer to access network redirection.


10/88



If AN redirects all the ATs to enable them to leave the AN, set the filed to 1 (YES).

Otherwise, set the filed to 0 (NO), indicating no support of AT redirection.

[Type]

Um interface parameter, and sent in the Redirect of QuickConfig Message.

[Command name]

MOD DOQCM

LST DOQCM

[Range and unit]

YES (redirection)/NO (non-redirection)

[Operating range]

NO---Do not support AT redirection.

[Recommended value]

NO

[Setting tradeoff]

None

COLORCODE (Color Code)

[Description]

Refer to color code corresponding to EV-DO carrier determined by [Cell ID], [Sector

ID] and [Carrier ID]. Color code identifies a subnet.

[Type]

Um interface parameter, and sent in the ColorCode field of QuickConfig Message.

[Command name]

MOD DOQCM

LST DOQCM

[Range and unit]


11/88



0255

[Operating range]

0255

[Recommended value]

Set the value as required and default the value to 0.

[Setting tradeoff]

None

[Remarks]

ClolorCode is unique in the local office and varies with subnet ID. Plan the

multiplexing of color code. UATI high 8bit is the color code of Sector. The AN (BSC)

should contain a color code table, recording the color code of neighbor sector and

neighbor AN for each color code. After AT removes to new AN, determine the original

AN based on oldUATI reported by AT.

Figure 2-1 Color code area

SECTORID128 (SECTOR ID128)

[Description]

Refer to unique identification of a sector carrier determined by [Cell ID], [Sector ID]

and [Carrier ID] and the value is set to 128bit.

[Type]


12/88



Um interface parameter, and sent in the SectorID field of SectorParameters

Message.

[Command name]

LST DOQCM

[Range and unit]

Refer to hex with no more than 32 digits starting with 0x

[Operating range]


[Recommended value]

None

[Setting tradeoff]

None

[Remarks]

SectorID128 SectorID104+SectorID24ColorCode+SectorID24

On the maintenance console, set SECTORID128 based on high 104bit

(SECTORID104) and low 24bit (SECTORID24).


[Description]

Refer to high 104 bit of SECTORID128

[Type]

Um interface parameter, and sent in the SectorID field in the SectorParameters

Message.

[Command name]

ADD DOCS


13/88



RMV DOCS

MOD DOCS

LST DOCS

[Range and unit]

Refer to hex with no less than 32 digits starting with 0x

[Operating range]


[Recommended value]

None

[Setting tradeoff]

None


[Description]

Refer to low 24bit of SECTORID128

[Type]

Um interface parameter, and sent in SectorID field of SectorParameters Message.

[Command name]

MOD DOQCM

LST DOQCM

[Range and unit]


[Operating range]



14/88



[Recommended value]

None

[Setting tradeoff]

None

SECTOR_GAIN (Sector Gain)

[Description]

Set the baseband gain to control the attenuation, in the unit of dB. The modified

parameter takes effect after the reset of EVDO channel board (BECM).

[Type]

Internal parameter of BTS

[Command name]

MOD CDMACH

LST CDMACH

[Range and unit]

04095

[Operating range]

5003200

[Recommended value]

3000

[Setting tradeoff]

Set the value based on actual output power. The mapping between setting value and

actual transmit power: P = 20*log (SECTOR_GAIN / 3000) + 43 - TX_GAIN (dBm).

You can calculate the following table base on this formula. Currently, it is

recommended to use TX_GAIN and external attenuator instead of modifying BTS

gain to change forward output power.


15/88



Table 2-1 Mapping between sector gain and output power

Sector gain Output power (dBm)

3000 43

2500 41.4

2000 39.5

1500 37

1000 33.5

500 27.3

[Remarks]

To restrict the output power, modify RF gain first and then baseband gain.

To change forward output power, adjust RF gain first.

2.2. Control Channel Parameters

CCHRATE (Control Channel Rate)

[Description]

Refer to the settings of control channel rate.

The MACIndex comparison when MAC channel and preamble are used is shown in 0:

Table 2-2 MACIndex Comparison

MACIndex Use MAC channel or not Use Preamble or not

0 and 1 NO NO

2 NO Control channel at the

rate of 76.8kbps


16/88



3 NO Control channel at the

rate of 38.4kbps

4 RA channel NO

563 Used for RPC channel

and DRCLock channel

transmission

Used for forward

traffic channel

transmission

[Type]

System parameter

[Command name]

MOD DOCCHP

LST DOCCHP

[Range and unit]

76.8kbps/38.4kbps

[Operating range]

76.8kbps/38.4kbps

[Recommended value]

76.8kbps(default value: 38.4kbps)

[Setting tradeoff]

If the control channel rate is high, the timeslots occupied for sending control

channel capsule, increase the control channel and traffic channel capacity but

decrease the coverage area of control channel.

2.3. Neighbor AN Parameters


17/88



NBRANID (IP Address of Neighbor AN)

[Description]

Add IP address of neighbor AN

[Type]

Internal parameter

[Command name]

ADD DONBRAN

RMV DONBRAN

MOD DONBRAN

LST DONBRAN

[Range and unit]

0.0.0.0255.255.255.255

[Operating range]

0.0.0.0255.255.255.255

[Recommended value]


[Setting tradeoff]

None

NBRCOLORCODE (Color Code of Neighbor AN)

[Description]

Add the color code of neighbor AN.

The color code identifies different subnets, and one PCF configures a color code.

[Type]


18/88



Internal parameter

[Command name]

ADD DONBRAN

RMV DONBRAN

MOD DONBRAN

LST DONBRAN

[Range and unit]

0255

[Operating range]

0255

[Recommended value]


[Setting tradeoff]

None

NBRSID104 (SECTORID104 of Neighbor AN)

[Description]

Modify new [Sector ID] value of neighbor AN determined by [IP Address of Neighbor

AN] and [Color Code of Neighbor AN].

[Type]

Internal parameter

[Command name]

ADD DONBRAN

RMV DONBRAN


19/88



C

MOD DONBRAN

LST DONBRAN

[Range and unit]


[Operating range]


[Recommended value]

Set the value as required

[Setting tradeoff]

None

hapter 3 Access Parameters

ACYCLEDURATION (Access Channel Probe Period)

[Description]

Mobile station sends a new access probe when system time T is multiples of access

channel period. The parameter is of carrier class. The access probe starts only at T

satisfying the following condition:

T mode AccessCycleDuration = 0

Wherein, T is the system time, in the unit of timeslot.

[Type]

Um interface parameter, and sent in the AccessCycleDuration filed of Access

Parameters Message.

[Command name]


20/88



MOD DOAPM

LST DOAPM

[Range and unit]

8, 16, 32, 64, or 128 (unit: timeslot)

[Operating range]

8, 16, 32, 64, or 128timeslots

[Recommended value]

64 timeslots

[Setting tradeoff]

If the parameter is set to a small value, reduce the time of access probe and increase

access channel capacity but increase access collision probability and reduce access

success ratio.

PRBLEN (Access Probe Preamble Frame Length)

[Description]

[PRBLEN] and [CAPSULELENMAX] define the structure of access probe in the

EVDO and the parameter is of carrier class. As shown in 0, pilot (I-channel) is enabled

first and functions as preamble in each access probe and probe data (Q-channel) is

enabled after [PreambleLength] frame (that is, PreambleLength16 timeslots) to

reach [CapsuleLengthMax (access probe preamble frame length)]16 timeslots.


21/88



Figure 3-1 Access probe structure

[Type]

Um interface parameter, and sent in the PreambleLength field of Access

Parameters Message.

[Command name]

MOD DOAPM

LST DOAPM

[Range and unit]

17(unit: frame, that is, 16 timeslots)

[Operating range]

17

[Recommended value]

2

[Setting tradeoff]

If the parameter is set to a large value, increase the probability that AN detects

access probe but increase the time of access probe success and reduce access

channel capacity.

If the parameter is set to a small value, AN may be unable to detect successfully

access probe. The parameter setting must be related to access search window and


22/88



their mapping is shown in 0. The access window is related to coverage radius of

sector.

Table 3-1 Mapping between PreambleLength and access window size

CAPSULELENMAX (Max. Capsule Length of Access Channel)

[Description]

The parameter value is the length of the maximum capsule carrying probe data and

the parameter is of carrier class.

[Type]

Um interface parameter, and sent in the CapsuleLenghtMax field of Access

Parameters Message.

[Command name]

MOD DOAPM

LST DOAPM

[Range and unit]

27 (unit: frame, that is, 16 timeslots)

[Operating range]

27 (unit: frame, that is, 16 timeslots)

[Recommended value]

2

[Setting tradeoff]


23/88



If the parameter is set to a small value, fail to carry large data capsule of access

channel message but reduce access probe time and increase access channel

capacity.

[Remarks]

The access channel long code mask of EVDO is also related to the system time for

access probe transmission, besides, ColorCode and SectorID. The system time is the

first timeslot of access probe preamble. Transmit also the pilot while transmitting data

capsule.

PERSISTENCE0 (Persistence Vector 0)




[Description]

This group of parameters is used for setting. When the type-0, 1, 2, or 3 AT

performs persistence detection (PD) before sending the first probe of a probe

sequence, use the APersistence value respectively.

The AT determines persistence probability and carrier-class based on

APersistence value. [APersistence i] value is sent to AT at (i +1) times of

APeristence field of AccessParameters Message.

If AT does not define type, use i = 0, corresponding to non-urgent AT. If the

vector value n =0x3F, the persistence probability p =0. If n is unequal to 0x3F,

p=2^(-n/4). (For details, see C.S0024-0_v4.0)

[Type]

Um interface parameter, and sent in the APersistence field of Access Parameters

Message.

[Command name]

MOD DOAPM

LST DOAPM


24/88



[Range and unit]

Refer to hex with no more than 2 digits starting with 0x (maximum value: 0x3F)

[Operating range]

0x000x3F

[Recommended value]

1 (default value: 0x00)

[Setting tradeoff]

If the persistence vector is set to a large value, reduce the probability of PD and

prolong the time for sending access probe, but reduce the probability of access probe

collision.

Set persistence vector to a small value because of small load during the initial

stage of network construction to reduce access duration. Increase the value because

of the increment of network access load to reduce access collision and ensure access

success ratio.

[Remarks]

The AT must perform PD before sending the first probe of sequence. Generate

random number x (0< x< 1) distributed equally to compare with persistence probability

p.

If x< p, the PD succeeds. If successful PDs or PD failures are more than 4/p, AT

sends the first probe of sequence within the access channel period.

If p is unequal to 0, AT repeats above PDs starting from next access channel

period.

If p = 0, access is unavailable for the AT.

OLOOPADJUST (AT Open-loop Power Estimation)

[Description]

Refer to the reverse nominal power used in the open-loop power estimation by the

AT, in the unit of -1dB. The parameter is of carrier class. AT uses the parameter to

estimate the average output power of pilot channel open-loop X0 while accessing the


25/88



probe. The X0 ranges from -6dB to +6dB and also from -9dB to =9dB of the

following formula:

X 0 = - Received average power (dBm) + OpenLoopAdjust (AT

open-loop power estimation) + ProbeInitialAdjust (open-loop power

estimation adjustment factor)

[Type]

Um interface parameter, and sent in the OpenLoopAjust field of Access Parameters

Message. The value used by AT is -1 times of the value in the filed.

[Command name]

MOD DOAPM

LST DOAPM

[Range and unit]

0255 (unit: -1dB)

[Operating range]

0255

[Recommended value]

85

[Setting tradeoff]

If the parameter is set to a small value, increase the power of open-loop power

estimation and reduce the time for successful AT access, but add reverse transmit

power of AT to increase reverse interference of system.

If the parameter is set to a large value, AT accesses the system after several

probes.

[Remarks]

Factors affecting OpenLoopAdjust are shown in 0:

Table 3-2 Factors affecting OpenLoopAdjust

Factors Mark Value Remarks


26/88



BTS Transmit Power Ptx (bts) 10W = 40dBm

BTS Noise Figure (noise

coefficient)

NF (bts) 5dB

Cell Loading (sector reverse

load)

Lc 50% Not depend on link

Desired Total RL SINR

(-26dB/antenna)

Ecp/Nt -26dB/antenna

Ior/Ioc C1 1

No/Ior C2 1

Cell Thermal Noise NoW(bts) -113dBm/Hz

OpenLoopAdjust k 83.2 -174+

10*log10(1.23MHz

)

Wherein, k = -(Ecp/Nt + Ptx(ap) + NF(ap) + 10*log10(1+c1+c2) + NoW(ap)

- 10*log10(1-L(ap)))

PRBINIADJUST (Open Loop Power Estimation Adjustment Factor)

[Description]

The parameter and [AT open-loop power estimation] estimate the average open-loop

output power. The parameter is of carrier class. For details, see [OLOOPADJUST]

[Type]

Um interface parameter, and sent in the ProbeInitialAdjust field of Access

Parameters Message.

[Command name]

MOD DOAPM

LST DOAPM

[Range and unit]


27/88



-16 15 (unit:: dB)

[Operating range]

-1615

[Recommended value]

0

[Setting tradeoff]

If the parameter is set to a large value, impact on the reverse capacity to cause

large power redundancy.

If the parameter is set to a small value, the MS accesses the system after several

probes to prolong the MS access time and even result in the access failure.

[Remarks]

OpenLoopAjust and ProbeInitialAdjust are common data of access channel MAC

protocol, and OpenLoopAjust+ ProbeInitialAdjust ranges from -81dB to -66dB for

frequency band type 0, 2, 3, 5, or 7 and from -100dB to -69dB for frequency band type

1, 4, or 6.

PRBNUMSTEP (Number of Max. Access Probe)

[Description]

Refer to the max. access probe number of single access probe sequence and the

parameter is of carrier class. 0shows the components of access probe sequence.

Figure 3-2 Access process


28/88



Wherein, Np refers to max. access probe number in the probe sequence

and Ns refers to max. probe sequence number of an access attempt.

[Type]

Um interface parameter, and sent in the ProbeNumStep field of Access Parameters

Message.

[Command name]

MOD DOAPM

LST DOAPM

[Range and unit]

115 (unit: number)

[Operating range]

515

[Recommended value]

15

[Setting tradeoff]

The larger the parameter value, the more the probability for successful access

probe sequence. But increase the interference of reverse link, because the failed

access may be caused by collision. If the access fails, the interval for the origination of

call attempt will be longer.

[Remarks]

The parameter is considered together with [Probe Power UP Step (PowerStep)].When PWR_STEP is set to a smaller value, NUM_STEP should be set to a larger

value. If PWR_STEP is set to a larger value, NUM_STEP can be set to a smaller

value.

PWRSTEP (Probe Power UP Step)

[Description]


29/88


30/88



Figure 3-3 Access process

[Type]

Um interface parameter, and defined in the ProbeSequenceMax of

InitialConfiguration feature table when access channel configures feature negotiation.

The protocol default values of configuration features are shown in Table 3-3:

Table 3-3 Default values of InitialConfiguration features

[Command name]

MOD DOMCNP

LST DOMCNP

[Range and unit]

115

[Operating range]

115

[Recommended value]

3

[Setting tradeoff]


31/88



If the parameter is set to a large value, increase the access success ratio but affect

access channel capacity.

If the parameter is set to a small value (for example, 1), the sequence cannot be

retransmitted. The radio environment fluctuates. If the first access fails, the radio

environment may get better in the case of the second times of access.

Set the parameter to 2.

PRBBKOFF (inter-probe backoff)

[Description]

Used to calculate the start time of next access probe and the parameter is of carrier

class. The AN should set the parameter as the upper threshold of backoff range used

by AT during the access probe.

[Type]

Um interface parameter, and defined in the ProbeBackoff field of

InitialConfiguraiton feature table when access channel configures feature

negotiation.

[Command name]

MOD DOMCNP

LST DOMCNP

[Range and unit]

015 (unit: AccessCycleDuration)

[Operating range]

015

[Recommended value]

4

[Setting tradeoff]

If the parameter is set to a large value, delay the MS access in the case of many

access attempt probes but reduce access load.


32/88



If the parameter is set to a small value, increase the probability of probe collision in

the case of high system load.

PRBSEQ_BKOFF (inter-probe sequence backoff)

[Description]

The parameter is of carrier class. The AN should set the parameter as the upper

threshold of backoff range used by AT during the probe sequence.

[Type]

Um interface parameter, and defined in the ProbeSequenceBackoff field of

InitialConfiguration feature table when access channel configures feature

negotiation.

[Command name]

MOD DOMCNP

LST DOMCNP

[Range and unit]

015 (unit: AccessCycleDuration)

[Operating range]

015

[Recommended value]

8

[Setting tradeoff]

See [PRBBKOFF].

[Remarks]

Refer to inter-sequence backoff. AT generates a positive pseudorandom number k

between 0 and ProbeSequenceBackoff , and AT should wait for S = (k

AccessCycleDuration) + TACMPATProbeTimeout timeslots after the last probe in the former

sequence.


33/88



ACCDATAOFF (Access Channel Nominal Power Offset)

[Description]

The parameter is of carrier class, and identifies nominal power offset of access

channel and pilot channel, in the unit of 0.5db.

[Type]

Um interface parameter, and defined in the DataOffsetNom filed of

PowerParameters feature table in the default access channel MAC protocol

configuration features.

In the Um interface message, the parameter refers to binary supplemental code value,in the unit of 0.5dB.

[Command name]

MOD DOMCNP

LST DOMCNP

[Range and unit]

-8 7 (unit: 0.5dB)

[Operating range]

-8 7

[Recommended value]

0

[Setting tradeoff]

If the parameter is set to a large value, facilitate successful AT access to shorten

access time, but increase reverse power consumption of AT and reverse interference

of system and reduce reverse capacity of system.


34/88



C hapter 4 Power Control Parameters

4.1 Power Control Parameters

REVPER (Reverse Target PER)

[Description]

Refer to convergence target of reverse PER under the normal condition.

[Type]

Internal parameter

[Command name]

MOD DOPCPP

LST DORRMP

[Range and unit]

199 (unit: %)

[Operating range]

110

[Recommended value]

1

[Setting tradeoff]

To set target PER, find a balance between data transfer performance and reverse

transmit power and system load.

If target PER is set to a smaller value, the reverse transmission rate is higher, so

does for the transmit power of MS to increase also the reverse load of system.


35/88



MINPCT (Min. PCT)

[Description]

Refer to the minimum PCT value adjusted by BSC outer loop power control.

[Type]

Internal parameter

[Command name]

MOD DOPCPP

LST DORRMP

[Range and unit]

-28672 -12416 (unit: 1/1024dB)

[Operating range]

-28672 -12416

[Recommended value]

-22528 (-22dB), and default 21504(-21dB)

[Setting tradeoff]

Converge the same target PER and PCT value varies with the link condition, such

as, change of soft handoff branch. Therefore, a dynamical change range exists in the

PCT and defined by the parameter and [MAXPCT].

If the parameter is set to a small value, the dynamical change range of PCT is

larger. For the good reverse link, save reverse transmit power of AT and reduce

reverse load of system. For the instant fading, the power cannot increase in time to

affect the transmission performance of user.

MAXPCT (Max. PCT)

[Description]


36/88



Refer to the maximum PCT value adjusted by BSC outer loop power control. The

parameter and [MINPCT] define the dynamical change range of PCT. The parameter

value is larger than that of [MINPCT]

[Type]

Internal parameter

[Command name]

MOD DOPCP

LST DORRMP

[Range and unit]

-28672 -12416 (unit: 1/1024dB)

[Operating range]

-28672 -12416

[Recommended value]

-19456 (-19dB)

[Setting tradeoff]

A larger value facilitates the performance, especially for worse radio environment, but

increase reverse transmit power and decrease reverse capacity of system.

INITPCT (Initial PCT)

[Description]

BSC adjusts the PCT values from time to time starting at initial PCT value. The

parameter value must be one between maximum PCT and minimum PCT.

[Type]

Internal parameter

[Command name]

MOD DOPCPP


37/88



LST DORRMP

[Range and unit]

-28672 -12416 (Unit: 1/1024dB)

[Operating range]

-28672 -12416

[Recommended value]

-21504 (-21.0dB)

[Setting tradeoff]

A larger value can ensure the performance during the call setup. For the data service,

the data transfer is very important. Therefore, the initial PCT can be set to a larger

value.

NORMALGFRAMED (PCT DOWN Step of Good Frame in Normal Condition)

[Description]

Refer to the PCT DOWN Step of good frame in the Normal state.

[Type]

Internal parameter

[Command name]

MOD DOPCP

LST DORRMP

[Range and unit]

0255 (unit: 1/1024dB)

[Operating range]

0255

[Recommended value]

5


38/88



[Setting tradeoff]

To set the parameter, find a balance between power control accuracy and timeliness.

[Remarks]

To ensure that PER converges target setting value in the Normal state, the PCT

UP Step of bad frame and PCT DOWN Step of good frame must be in an appropriate

proportional relation.

If the call is always in NORMAL state and target PER is 1%, the total DOWN

Steps of good frames must equal total UP Steps of bad frames within 100 frames toensure 1% of PER. The following formula must be met:

PER / (1-PER) = PCT DOWN Step of good frames in Normal state/PCT UP Step of

bad frames in Normal state

When the algorithm is implemented, calculate automatically [PCT UP Step of bad

frames in Normal state] from [PCT DOWN Step of good frames in Normal state]

and PER based on the above formula. Therefore, you can query [PCT UP Step ofbad frames in Normal state], instead modify it.

NORMALBRAMEU (PCT UP Step of Bad Frame in Normal State)

[Description]

Refer to PCT UP Step of bad frames in Normal state.

[Type]

Internal parameter

[Command name]

LST DORRMP

[Range and unit]

0255 (unit: 1/1024dB)


39/88



[Operating range]

0255

[Recommended value]

495

[Setting tradeoff]

None

[Remarks]

When the algorithm is implemented, calculate automatically [PCT UP Step of bad

frames in Normal state] from [PCT DOWN Step of good frames in Normal state]

and PER based on the formula (PCT UP Step of bad frames in Normal state = PCT

DOWN Step of good frames in Normal state/[ PER / (1-PER)]. Therefore, you can

query [PCT UP Step of bad frame in Normal state], instead modify it.

NODATAIFRAMEU (PCT UP Step of IDLE Frame in No Data State)

[Description]

Refer to PCT UP Step of IDLE frames in No Data state. If frames are not received

within continuous [NUMIDLEFORNODATA] time, transit the connection state to NO

DATA state.

[Type]

Internal parameter

[Command name]

MOD DOPCP

LST DORRMP

[Range and unit]

0255 (unit: 1/1024dB)

[Operating range]


40/88



0255

[Recommended value]

40

[Setting tradeoff]

The parameter value should be less than: UP Step of bad in Normal state = PCT

DOWN Step of good frame * (1-PER)/ PER

NODATAMAXINC (Max. PCT Increment in No Data State)

[Description]

Refer to the max. increment of calculated PCT in NoData state, that is, the max. PCT

increment during the time transited to NoData state and out of NoData state.

[Type]

Internal parameter

[Command name]

MOD DOPCP

LST DORRMP

[Range and unit]

01000 (unit: 1/1024dB)

[Operating range]

01000

[Recommended value]

500

[Setting tradeoff]


41/88



A larger value can back off link change in NoData state to ensure the

performance in the case of data transfer but may bring about excessive backoff to add

the power consumption.

To set the parameter, find a balance between power consumption and

transmission performance.

NODATAMAX (Max. PCT in NoData State)

[Description]

Refer to the maximum PCT value in NoData state. The parameter and [Max. PCT

increment in NoData state] prevent the excessive PCT increment in NoData state.

In the NoData state, each PCT increment should not be greater than [maximum PCT

increment in NoData state] and the set value. In addition, the parameter must be

less than [MAXPCT]

[Type]

Internal parameter

[Command name]

MOD DOPCP

LST DORRMP

[Range and unit]

-28672 -12416 (unit: 1/1024dB)

[Operating range]

-28672 -12416

[Recommended value]

-21504 (-21.0dB)

[Setting tradeoff]

See [NODATAMAXINC]


42/88



DATAGFRAMED (PCT DOWN Step of Good Frame in DataStart state)

[Description]

Refer to the PCT Down Step of good frame in DataStart state. If current state is DATA

START and good frame is received, PCT decreases one step [DATAGFRAMED].

If bad frame is received, transit the state from DataStart to NORMAL and process the

bad frame based on that in NORMAL state.

[Type]

Internal parameter

[Command name]

MOD DOPCP

LST DORRMP

[Range and unit]

0255 (unit: 1/1024dB)

[Operating range]

020 (unit: 1/1024dB)

[Recommended value]

5

[Setting tradeoff]

The value should not be greater than [NODATAMAXINC]

PCTMININCSTEP (Minimum Interval Frames for PCT UP Step)

[Description]


43/88



Refer to the interval frames between PCT UP Step of bad frame and PCT DOWN

Step of good frame in NORMAL state to avoid continuous bad capsule caused by

burst fading.

[Type]

Internal parameter

[Command name]

MOD DOPCP

LST DORRMP

[Range and unit]

0255 (unit: frame)

[Operating range]

04

[Recommended value]

2

[Setting tradeoff]

An over-small value may bring about excessive power in the case of burst fading but

an overlarge value may enable power to increase slowly incapable of backing off fast

fading.

PCTMINCHANGE (Mini. Changed PCT Sent to Carrier)

[Description]

Refer to minimum changed PCT value. Because PCT accuracy (1/1024dB)

maintained by the BSC is far smaller than that (0.125dB) of outer loop value set by the

BTS, send command to BTS only when the absolute value between current PCT and

the former PCT when notifying BTS is less than [PCTMINCHANGE]. Otherwise,

maintain it at the BSC to avoid sending frequent commands to BTS.

[Type]


44/88



Internal parameter

[Command name]

MOD DOPCP

LST DORRMP

[Range and unit]

0255 (unit: 0.125dB)

[Operating range]

1255, that is, 0.125dB 31.875dB

[Recommended value]

1, that is, 0.125dB

[Setting tradeoff]

A larger value enables PCT change scale to instable and inaccurate but reduces the

commands sent to BTS.

NUMIDLEFORNODATA (Number of IDLE Frames for NODATA State)

[Description]

Transit to NoData State after receiving continuously IDLE frames set by the parameter

[Type]

Internal parameter

[Command name]

MOD DOPCP

LST DORRMP

[Range and unit]

0255 (unit: frame)


45/88



[Operating range]

0255

[Recommended value]

100

[Setting tradeoff]

The larger the parameter value, the longer transited to NoData state. In this case,

increase the power consumption at the terminal and waste more system resources.

If an over-small value is set to the parameter, state transits frequently from

NODATA state to DATA to increase the processing load of system.

RTRAFDATAOFF (Reverse Traffic Channel Nominal Power Offset)

[Description]

Refer to nominal power offset of data/traffic channel in reverse link and the parameter

is of carrier class. The parameter identifies the nominal offset of data/traffic channel

power and pilot channel power in reverse link, in the unit of 0.5db.

[Type]

Um interface parameter, and defined in the DataOffsetNom filed of

PowerParameters feature table when the defaulted reverse traffic channel MAC

protocol configures negotiation. In the Um interface message, the field indicates

binary supplemental code value, in the unit of 0.5dB.

[Command name]

MOD DOMCNP

LST DOMCNP

[Range and unit]

-8 7 (unit: 0.5dB)

[Operating range]


46/88



-8 7

[Recommended value]

0

[Setting tradeoff]

None

[Remarks]

Table 4-2 specifies data channel power related to pilot channel power. DataOffsetNom,

DataOffset9k6, DataOffset19k2, DataOffset38k4, DataOffset76k8 and

DataOffset153k6 are common data of reverse traffic channel protocol and also can be

defined in the case of feature negotiation configuration.

Table 4-2 Reverse data channel power

DataOffset9k6

DataOffset19k2

DataOffset38k4

DataOffset76k8

DataOffset153k6

[Description]


47/88



Refer to the ratio of data channel power in the reverse link for the rate of

9.6/19.2/38.4/76.8/153.6 kbps to data channel nominal power in the reverse link for

the rates.

[Type]

Um interface parameter, and defined respectively in the DataOffset9k6 field,

DataOffset19k2 field, DataOffset38k4, DataOffset76k8 and DataOffset153k6

field of PowerParameters feature table in the configuration feature of defaulted

reverse traffic channel MAC protocol. In the Um interface message, the field indicates

binary supplemental code value, in the unit of 0.5dB.

[Command name]

Current version does not support dynamical configuration.

[Range and unit]

- 87 (unit: 0.5dB)

[Operating range]

-87

[Recommended value]

0

[Setting tradeoff]

None

RPCSTEP (Reverse Power Control Step)

[Description]

Refer to the size of power control step used by AT to control reverse link power. The

parameter sets the nominal change of average output power for each power control

bit.

[Type]


48/88



Um interface parameter, and defined in the RPCStep filed of PowerParameters

feature table when defaulted reverse traffic channel MAC protocol configures features.

[Command name]

MOD DOMCNP

LST DOMCNP

[Range and unit]

0.5dB or1.0dB

In the Um interface message, coding code for the parameter is shown in table 4-3:

Table 4-3: Coding mode of RPCStep

[Operating range]

0.5dB and 1.0dB

[Recommended value]

1.0dB

[Setting tradeoff]

The smaller the step, the more accurate the power control bit, and the more stable

the transmit power of AT.

The larger the step, the timelier the power control, and the more dramatic the power

control change.

[Remarks]

None


49/88



C hapter 5 Handoff Parameters

5.1 Module Handoff Parameters

DRCLEN1BRANCH (DRCLength for Branch 1)






[Description]

Refer to the number of timeslots used by AT to transmit single DRC value when there

are1, 2, 3, 4, 5, or 6 soft handoff branches. The system determines DRCLength value

to AT based on branches of AT. If AT has sent its DRC to sector A within n timeslots

and specifies r transmission rate, AT should search the preambles from sector A with

the r transmission rate between n+ 1 and n+ DRCLength timeslots. Table 5-1

shows DRCLength coding.

Table 5-1 DRCLength coding

[Type]

Um interface parameter, and sent in the DRCLength field of

TrafficChannelAssignment Message.


50/88



]

ge and unit]

, see Table 5-1 DRCLength coding.

rating range]

Set the par r branches

The recomm

Qualcomm

[Command name

MOD DOMPP

LST DOMPP

[Ran

03

For specific meaning

[Ope

03

[Recommended value]

ameter to 1 (2 timeslots) for branch 1and 2 (4 timeslots) for othe

ended value by Qualcomm is shown in Table 5-2:

Table 5-2 Default DRC length value of

[Se

rate of DRC to unable to be consistent with that of radio

env

the

t

andoff gain, add DRCLength to increase the reliability of DRC transmission.

tting tradeoff]

The larger the value, the higher reliability the transmission of DRC value, but the

lower the change

ironment.

The smaller the value, the less the retransmission times of DRC value, the lower

reliability the transmission of DRC value, but the faster the change rate of DRC.

The DRC value varies with the soft handoff number of AT active set. Because DRC

value has no soft handoff gain received at AN side, but reverse traffic channel has sof

h


51/88



RC Channel Gain for Branch 6)

[De

s from -9dB through +6dB.AT should

all the values within the range.

in the DRCChannelGain field of

nment Message.

-1812 (unit: m converts the value into binary supplemental

ing range]

lue]

[Se

RC transmission, but the larger

the effect on throughput of reverse link is.

DRCCHGAIN1 (DRC Channel Gain for Branch 1)





DRCCHGAIN6 (D

scription]

Refer to the ratio of DRC channel power level (in the case of transmission) to

reverse traffic pilot channel power level when the number of AT active set soft handoff

branch is 1, 2, 3, 4, 5, or 6. The parameter range

support

[Type]

Um interface parameter, and sent

TrafficChannelAssig

[Command name]

MOD DOMPP

LST DOMPP

[Range and unit]

0.5dB), and the syste

code.

[Operat

-1812

[Recommended va

Refer to Table 5-3

tting tradeoff]

The larger the value, the higher the reliability of D


52/88



The smaller the value, the less the effect on throughput of reverse link, and the

lower the reliability of DRC transmission. The parameter value varies with the number

of soft handoff branch.

Table 5-3 Qualcomm recommended values for different branches

ACKCHGAIN1 (Ack Channel Gain for Branch 1)






[Description]

Refer to the ratio of ACK channel power level (in the case of transmission) to reverse

traffic/ pilot channel power level when there are 1, 2, 3, 4, 5, or 6 soft handoff

branches of AT active set. The parameter value ranges from -3dB through +6dB. AT

should support all the values within the range.

[Type]

Um interface parameter, and sent in the AckChannelGain field of

TrafficChannelAssignment Message.

[Command name]

MOD DOMPP

LST DOMPP


53/88



[Range and unit]

-612 (unit: 0.5dB)

[Operating range]

-612

[Recommended value]

6, that is, 3dB

[Setting tradeoff]

To set the parameter, concern the following:

Minimize the probability of ACK error and loss to not affect PER and forward

throughput dramatically.

The larger the value, the larger the effect on reverse capacity.

When the transmit power of AT is up to the maximum, AT disables ACK channel.

[Remarks]

AT uses the ACK sub-channel to notify whether AN has correctly received forward

traffic channel data capsule. If AT has been correctly demodulated, send ACK bit. If

not, send NAK bit.

After receiving ACK bit from AT, AN transmits a new capsule instead of current

one. The mechanism adjusts AT forward rate prediction to improve the system

performance.

5.2 Carrier Configuration Negotiation Handoff Parameters

PILOTADD (Pilot Good Available Threshold)

[Description]


54/88



If the pilot strength exceeds the parameter value, it can be added to the active set.

If the pilot strength of neighbor set or remaining set exceeds the threshold when AT is

in Connection state, send a RouteUpdate message.

[Type]

Um interface parameter, and defined in the PilotAdd field of

SetManagementSameChannelParameters feature table when route update protocol

configures negotiation. The protocol default value is set to 0x0e, corresponding to

-7dB.

[Command name]

MOD DOCNP

LST DOCNP

[Range and unit]

-630 (unit: 0.5dB)

[Operating range]

-630

[Recommended value]

-14

[Setting tradeoff]

If the value of this parameter is overlarge, the soft handoff threshold increases, so the

soft handoff area and the soft handoff ratio decrease. But the soft handoff may bedelayed to result in coverage dead zone. If the value is over-small, the soft handoff

threshold decreases, so the soft handoff area and the soft handoff ratio increase.

PILOTCMP (Pilot Compare Threshold)

[Description]


55/88



When a pilot of candidate set is the parameter higher than the pilot of active set, AT

sends a RouteUpdate message.

[Type]

Um interface parameter, and defined in the PilotCompare field of


configures negotiation. The protocol default value is set to 5.

[Command name]

MOD DOCNP

LST DOCNP

[Range and unit]

-3231 (unit: 0.5dB). The Um interface is represented through binary supplemental

code.

[Operating range]

-3231

[Recommended value]

5

[Setting tradeoff]

If the parameter is over-small, the pilots in candidate set are easy to replace the

pilots in active set to result in ping-Pong handoff.

If the parameter is overlarge, the pilots in candidate set are difficult to replace the

pilots in active set so that AT is unable to obtain services on the best pilots in time.

PILOTDROP (Pilot Dropt Threshold)

[Description]

When the strength of pilot in active set or candidate set is less than the threshold, AT

starts a pilot deactivation timer. If the pilot strength is higher than PilotDrop before the

timer expires, restart and disable the timer.


56/88



[Type]

Um interface parameter, and defined in the PilotDrop field of


configures negotiation. The protocol sets the default value to 18.

[Command name]

MOD DOCNP

LST DOCNP

[Range and unit]

-630 (unit: 0.5dB). The Um interface is represented through binary supplemental

code.

[Operating range]

-630

[Recommended value]

-18

[Setting tradeoff]

If the parameter is overlarge, an available signal can be deleted from active set easily.

If the parameter is over-small, soft handoff threshold may decrease and a pilot in

active set is difficult to be deleted from active set.

PILOTDROPTIMER (Pilot Removal Timer Length)

[Description]

When the pilot strength in the AT active set or candidate set is lower than [pilot

minimum available threshold], AT starts the pilot removal timer through the value. If

the timer expires, and the pilots in the active set are processed, AT sends a

RouteUpdate message. If the pilots in the candidate set are processed, AT moves

the pilot to neighbor set.

[Type]


57/88



Um interface parameter, and defined in the PilotDropTimer field of


configures negotiation. The protocol sets the default value to 3. The timer codingmode is shown in Table 5-7:

Table 5-7 PilotDropTimer coding mode

[Command name]

MOD DOCNP

LST DOCNP

[Range and unit]

015 and the parameter values on the maintenance console are listed in table.

[Operating range]

15

[Recommended value]

3, that is, 4s

[Setting tradeoff]

If the parameter value is overlarge, the pilot with a low strength in the active set

stays there for a long time.

If the parameter value is over-small, handoffs will frequently occur.


58/88



NBRMAXAGE (Neighbor Set Max. AGE)

[Description]

This parameter defines the maximum life duration of pilots in the neighbor set.

The MS provides a counter for each pilot in the neighbor set. When the MS receives

the Neighbor List Update Message (NLUM), it increases the counters of the original

pilots in the neighbor set by one. If the counter of a pilot exceeds the parameter value,

the MS removes this pilot from the neighbor set.

If the parameter value is set to 0, each time the MS receives NLUM, the MS

removes all pilots in the original neighbor set so that the MS uses the contents in the

latest NLUM.

If the value is set to 2, when a pilot falls from the active set or candidate set back

to the neighbor set but there is no such pilot in two successive NLUMs, this pilot will

be removed from the neighbor set.

[Type]

Um interface parameter, and defined in the NeighborMaxAge field of


configures negotiation. The protocol default value is set to 0.

[Command name]

MOD DOCNP

LST DOCNP

[Range and unit]

015

[Operating range]

015

[Recommended value]

0


59/88



PILOTINCREMENT (Pilot PN Sequence Increment)

[Description]

Refer to pilot PN sequence increment, in the unit of 64PN chips. AT uses the

parameter value to search remaining set. Set the parameter to the maximum gain

when all the PN sequences of neighbor access network are integer multiples of the

increment.

[Type]

Um interface parameter, and defined in the PilotIncrement filed ofSearchParameters feature table when route update protocol configures negotiation.

The protocol default value is set to 4. Table 5-8 shows the default values of the feature

table:

Table 5-8 Default values of SearchParameters

[Command name]

MOD DOCNP

LST DOCNP

[Range and unit]

015

[Operating range]

015

[Recommended value]

4

[Setting tradeoff]


60/88



The smaller the parameter value, the more the available pilot phase offset is. In

this case, the same-phase inter-pilot multiplexing distance increases to reduce the

interface of same-phase inter-pilot. At that time, the phase interval between differentpilots decreases to confuse the pilots.

The larger the parameter value, the less the available pilot phase offset is. In this

case, pilots in remaining set decreases, so does the time for MS to scan pilots. In

actual dynamic environment, the probability for one strong pilot signal loss decreases.

At that time, available pilot phase offset decreases, so does for same-phase inter-pilot

multiplexing distance, and the interference of same-phase inter-pilot increases.

In addition, the parameter determines the maximum value of SRCH_WIN_N and

SRCH_WIN_R.

SRCHWINA (Search Window Size for Active Set and Candidate Set)

[Description]

Corresponding AT is used for search window size for active set and candidate set.

When the MS searches pilots in the active and candidate sets, set their first arriving

available multi-paths as their search centers respectively. Therefore, this parameter is

only related to the multi-paths of pilots, instead of the relative propagation delay

between pilots.

[Type]

Um interface parameter, and defined in the SearchWindowActive field of

SearchParameters feature table when route update protocol configures negotiation.

[Command name]

MOD DOCNP

LST DOCNP

[Range and unit]

015

The mapping between coding mode and search window size is shown in Table 5-9:


61/88



Table 5-9 Search window size coding

[Operating range]

015

[Recommended value]

8, that is, 60chips

[Setting tradeoff]

According to the local propagation delay, the pilot signals after the propagation

delay should fall into the search window of the active set. If the parameter value of this

is over-small, some useful signals in the active set may fall beyond the search window

to affect seriously link quality.

If the parameter value of this is overlarge, some irrelevant signals (PN confusion)

may also fall into the search window, so the link quality may also be affected. A large

search window also slows down the MS search neighbor pilots so that the handoff

could not be triggered in time. Thus the system performance decreases


62/88



SRCHWINN (Search Window Size for Neighbor Set)

[Description]

AT uses the search window size here to search for carriers in neighbor set. Therefore,

this parameter is related to the multi-paths of neighbor pilots and relative propagation

delay from neighbor pilot to the reference pilot.

[Type]

Um interface parameter, and defined in the SearchWindowNeighbor field of


[Command name]

MOD DOCNP

LST DOCNP

[Range and unit]

015

The mapping between coding mode and search window size is shown in Table 5-9:

[Operating range]

015

[Recommended value]

10, that is, 100chips

[Setting tradeoff]

The larger the parameter value, the longer the search takes. But the pilot branches

are missed so the probability unable to add the neighbor pilots to active set is less.

SRCHWINR (Search Window Size for Remaining Set)

[Description]


63/88



Search windows size for remaining set, AT uses the search window size to search for

carrier in remaining set.

[Type]

Um interface parameter, and defined in the SearchWindowRemaining field of


The protocol default value is set to 10.

[Command name]

MOD DOCNP

LST DOCNP

[Range and unit]

015

For the coding code and search window size, see Table 5-9.

[Operating range]

015

[Recommended value]

10, that is, 100chips

[Setting tradeoff]

If the parameter value is set over-small, some useful pilots in the remaining set may

be missed. As a result, the function of BSC detecting the absent configuration of

neighbor cell can not be utilized fully. If the parameter value is overlarge, the MS may

search other irrelevant signals, and the time that the MS searches pilots in the

remaining set increases, so the search speed of the MS slows down.

[Remarks]

To use missed neighbor cell detection function to check whether missed neighbor

cells exist in the system, set the parameter.

While MS searches for remaining set pilots, all the remaining set PNs are integer

multiples of PILOT_INC. therefore, ensure that all the PNs in the system are integer

multiples of PILOT_INC while planning PN.


64/88



[Partner conditions]

MOT LUCENT

Not detailed 0

5.3 Sector Carrier Idle Handoff Parameters

SRCHWIN (Search Window Size)

[Description]

Refer to search window size while searing for neighbor carrier. The larger the

parameter value, the longer the search takes, but the less the possibility pilot is

missed.

[Type]

Um interface parameter, and sent in the NeighborSearchWindowSize field of

SectorParameters message.

[Command name]

MOD NBRPARA

LST NBRPARA

[Range and unit]

4452 (unit: chip). The parameter values on maintenance console are listed in table.

[Operating range]

4452

[Recommended value]

60


65/88



SRCHOFFS (Search Window Offset)

[Description]

Refer to PN code offset determined by [Neighbor Carrier] relative to search window

center while searching for neighbor carrier.

[Type]

Um interface parameter, and sent in NeighborSearchWindowOffset field of

SectorParameters message.

[Command name]

MOD NBRPARA

LST NBRPARA

[Range and unit]

06

The parameter values on maintenance console list all the Offset values in tables. For

the mapping between the value and search window offset, see Table 5-10.

[Operating range]

06

[Recommended value]

0

[Setting tradeoff]

The parameter and PN offset determine the center position of search window.

SRCHWININC (Search Window Size Included)

[Description]

Whether neighbor sector list message includes idle handoff search window size

If yes, use the [Search window size]. If not, use the negotiated parameter.


66/88



[Type]

Um interface parameter, and sent in the NeighborSearchWindowSizeIncluded field

of SectorParameters message.

[Command name]

MOD NBRPARA

LST NBRPARA

[Range and unit]

YES/NO

[Operating range]

YES/NO

[Recommended value]

NO

[Setting tradeoff]

None

SRCHOFFSINC (Search Window Offset Included)

[Description]

Whether neighbor list message includes idle handoff search window offset. If yes, use

the [Search window offset]. If not, use the default search window offset.

[Type]

Um interface parameter, and sent in the NeighborSearchWindowOffsetIncluded field

of SectorParameters message.

[Command name]

MOD NBRPARA

LST NBRPARA


67/88



[Range and unit]

YES/NO

[Operating range]

YES/NO

[Recommended value]

NO

[Setting tradeoff]

None

5.4 Same-frequency Neighbor Handoff Parameters

CCDMACH (Center Carrier)

[Description]

Refer to the carrier which the same-frequency carrier neighbor relation is to be

modified. BTS ID-Cell ID-Sector ID-- Carrier, and determine PN code of the carrier.

[Command name]

MOD DOSFNBRP

LST DOSFNBRP

[Recommended value]


NBRCDMACH (Same-frequency Neighbor Carrier)

[Description]


68/88



Refer to the same-frequency neighbor carrier which center carrier is to be modified.

BTS ID-Cell ID- Sector ID- Carrier and determine PN code of same-frequency

neighbor carrier.

[Type]

Um interface parameter, and neighbor list is sent in the NeighborList Message.

[Command name]

MOD DOSFNBRP

LST DOSFNBRP

[Recommended value]

Set the value as required

NSRCHWININC (Search Window Size of Neighbor Set Branch Included)

[Description]

Whether neighbor sector list message includes neighbor search window size

If yes, use the [Search window size of neighbor set branch]. If not, use negotiated

parameter.

[Type]

Um interface parameter, and sent in the SearchWindowSizeIncluded field of

NeighborList Message.

[Command name]

MOD DOSFNBRP

LST DOSFNBRP

[Range and unit]

YES/NO


69/88



[Operating range]

YES/NO

[Recommended value]

NO

NSRCHWINSIZE (Search Window Size of Neighbor Set Branch)

[Description]

Neighbor set branch search is performed PN code range determined by

[Same-frequency Neighbor Carrier] and the range is search window. If

SearchWindowSizeIncluded is set to 0 , it does not take effect to set the parameter.

If SearchWindowSizeIncluded is set to 1, corresponding AT is search window size

used by neighbor pilot.

[Type]

Um interface parameter, and sent in the SearchWindowSize field of NeighborListMessage. When the filed occurs for n times, correspondingly, PilotPN occurs for

ntimes.

[Command name]

MOD DOSFNBRP

LST DOSFNBRP

[Range and unit]

015

The values on the maintenance console list the optional chips number in table. The

mapping between the value of Um interface message and search window size is

shown in Table 5-9:

[Operating range]

015

[Recommended value]


70/88



8, that is, 60 chips

[Setting tradeoff]

According to the mulipath of neighbor pilot and the propagation delay size from

neighbor pilot to reference pilot, set the parameter to ensure that neighbor pilot signals

are located within the neighbor set search window that sets the earliest arriving

multipath components of reference pilot as time reference and PN offset of neighbor

pilot as search center.

If the parameter value is over-small, neighbor pilot signals may be located beyond

the search window to miss some neighbor pilots so that neighbor set pilots cannot be

added to active set and normal soft handoff fails.

If the parameter value is overlarge, the time for MS to search for each neighbor

pilot may increase to slow down the speed for searching neighbor pilot and miss the

best soft handoff opportunity to affect the handoff performance potentially.

NSRCHWINOFFSETINC (Search Window Offset of Neighbor Set Branch

Included)

[Description]

Whether neighbor sector list message includes search window offset of neighbor set

branch. If yes, use the [Search Window Offset of Neighbor Set Branch]. If no, use the

default [Search Window Offset of Neighbor Set Branch].

[Type]

Um interface parameter, and sent in the SearchWindowsOffset field of NeighborList

Message.

[Command name]

MOD DOSFNBRP

LST DOSFNBRP

[Range and unit]

YES/NO


71/88



[Operating range]

YES/NO

[Recommended value]

NO

[Setting tradeoff]

None

NSRCHWINOFFSET (Search Window Offset of Neighbor Set Branch)

[Description]

Refer to PN code offset determined by [Same-frequency Neighbor Carrier] relative to

search window center while searing for neighbor carrier.

[Type]

Um interface parameter, and sent in the SearchWindowsOffset field of NeighborList

Message.

[Command name]

MOD DOSFNBRP

LST DOSFNBRP

[Range and unit]

07

The parameter values on the maintenance console list all the Offset values in tables.

The mapping between value of Um interface message and search window offset is

shown in Table 5-10:

Table 5-10 Search window offset coding


72/88



[Operating range]

07

[Recommended value]

0

[Setting tradeoff]

The parameter and PN offset determine the center position of search window.

5.5 Algorithm Module Handoff Parameters

ANHOSWITCH (AN Assisted Inter-AN Handoff Switch)

[Description]

Whether to allow AN assisted inter-AN handoff. [Compare Difference of AN

Assisted Inter-AN Handoff] takes effect when the parameter is set to ON1.

[Type]

Internal parameter

[Command name]

MOD DORRMMP


73/88



LST DORRMMP

[Range and unit]

ON1/OFF0

[Operating range]

ON/OFF

[Recommended value]

ON

[Setting tradeoff]

None

[Remarks]

AN assisted inter-AN handoff decision means that AN judges the time for connection

release to originate the release. If [AN Assisted Inter-AN Handoff Decision Switch]

is enabled while processing RouteUpdate Message, check there are external AN

pilots in the pilots reported by RouteUpdate Message. If yes, and the strongest

external AN pilot is [Compare Difference of AN Assisted Inter-AN Handoff] higherthan the strongest pilot of this AN, AN automatically originates connection release.

ANHOCOMP (Compare Difference of AN Assisted Inter-AN Handoff)

[Description]

When the strength of the strongest external AN pilot is larger than that of this AN, andthe difference is greater than or equal to the parameter value, originate the handoff.

[Type]

Internal parameter

[Command name]

MOD DORRMMP

LST DORRMMP


74/88



[Range and unit]

063 (unit: 0.5dB)

[Operating range]

063

[Recommended value]

6

[Setting tradeoff]

If the parameter value is overlarge, AN is more difficult to automatically originate

connection release to facilitate decreasing Ping-Pong handoff.

POLLUTENUM (Branch Number at Pilot Pollution)

[Description]

When the number of pilots whose strength is larger than T_ADD in RouteUpdate

message is equal to or greater than the parameter value, it is called pilot pollution.

This parameter is one condition which is used to judge whether the pilot pollution

exists in the system. Like the 1X, set whether to perform pilot pollution detection in

soft parameter.

[Type]

Internal parameter

[Command name]

MOD DORRMMP

LST DORRMMP

[Range and unit]

46

[Operating range]


75/88



46

[Recommended value]

5

[Setting tradeoff]

If the parameter value is overlarge, the threshold for system to judge the pilot

pollution increases. Otherwise, the threshold decreases.

[Remarks]

Pilot pollution means that a large number of pilots with close strength are available

but preamble pilot is unavailable in the radio environment. The pilot pollution will

increases soft handoff ratio.

When processing the RouteUpdate Message reported by MS, the BSC analyzes

the pilot strength information to judge whether pilot pollution conditions are satisfied. If

yes, output the RouteUpdate Message through a log to facilitate the query of

network optimization personnel.

The pilot pollution conditions include:

(1) The pilot number that the strength in the RouteUpdate Message is more than

T_ADD is greater than or equal to the parameter POLLUTENUM.

(2) The strength balance of the strongest pilot and prior one in the RouteUpdate

Message is less than or equal to parameter POLLUTERELTRSHLD.

POLLUTERELTRSHLD (Relative Threshold at Pilot Pollution)

[Description]

When the strength difference between the strongest pilot and the second strongest

pilot in RouteUpdate message is less than or equal to the parameter value, it

Date post:	10-Feb-2018
Category:	Documents
Upload:	kateryna499258587
View:	218 times
Download:	0 times

Guide to CDMA 1X EVDO BSS Network Planning Parameter Configuration-20050820-C-1.0

Documents