Config RF Parameters

CONFIGURABLE RF
PARAMETERS
RF Link Optimization
WP2003-007-2
WP2003-007-2
June
June 19,
19, 2006
2006
White Paper
Configurable RF Parameters
iDEN Technical Publications White Paper
Table of Contents
GENERAL................................................................................................................................................6
RADIO LINK CONTROL ......................................................................................................................6
POWER CONTROL ....................................................................................................................................6
Transmit Power/Carrier: OL; OLL....................................................................................................7
Transmit Power (Pto): OL .................................................................................................................8
Cell Maximum Transmit Power of MS: OL .......................................................................................8
Receiver/Transmitter Gain: OL .........................................................................................................9
Power Control Constant: OL .............................................................................................................9
INTERCONNECT HANDOVER ..................................................................................................................11
Handover Class of Cell ....................................................................................................................12
Handover Acknowledge Timer.........................................................................................................15
Maximum Candidates for Handover ................................................................................................16
Maximum Foreground Neighbor Cells: OL.....................................................................................17
Handover C/I+N Inbound Intercell Floor: OL ................................................................................17
Handover C/I+N Inbound Hysteresis: OL .......................................................................................18
Handover C/I+N Inbound Threshold: OL .......................................................................................19
Handover C/I+N Outbound Hysteresis: OL ....................................................................................19
Handover C/I+N Outbound Threshold: OL.....................................................................................21
Handover Switches...........................................................................................................................21
Handover Debugging ......................................................................................................................23
DISPATCH RECONNECTION....................................................................................................................24
Reconnection C/I+N Min: OL..........................................................................................................25
Reconnection C/I+N Outbound Hysteresis: OL...............................................................................26
Reconnection C/I+N Outbound Threshold: OL ...............................................................................27
Reconnection class ...........................................................................................................................27
PACKET DATA RECONNECTION .............................................................................................................28
PD Reconnect CINRo Hysteresis: OL..............................................................................................28
PD Reconnect CINRo Low: OL .......................................................................................................29
PD Reconnect CINRo Threshold: OL ..............................................................................................29
PD Reconnect Pro Hysteresis: OL...................................................................................................29
PD Reconnection Class....................................................................................................................30
IDLE MODE PROCEDURE (CELL RESELECTION).....................................................................................30
Reselection C/I+N Outbound Threshold: OL ..................................................................................31
Reselection C/I+N Outbound Hysteresis: OL..................................................................................31
Reselection Class .............................................................................................................................32
Reselection Measurement Period: OL .............................................................................................34
Idle Mobility Timers.........................................................................................................................35
CHANNEL QUALITY MEASUREMENTS ...................................................................................................36
Handover INI Window .....................................................................................................................36
Handover Inquire Interval ...............................................................................................................36
Handover Report Interval: OL.........................................................................................................37
Handover Server Window: OL.........................................................................................................38
Foreground Fail Threshold: OL ......................................................................................................38
Maximum Foreground Neighbor Cells: OL.....................................................................................39
Foreground Window (slots): OL ......................................................................................................39
Foreground C/(I+N) Outbound Threshold: OL...............................................................................40
Serving Window: OL ........................................................................................................................40
June 19, 2006
Page 2 of 69
WP2003-007-2
CHANNEL DISCONNECT AND FAILURE ..................................................................................................41

FNE Fail Threshold: OL..................................................................................................................41
FNE Fail Window: OL .....................................................................................................................42
MS Fail Threshold: OL ....................................................................................................................42
MS Fail Window: OL .......................................................................................................................43
CHANNEL ALLOCATION .................................................................................................................43
DYNAMIC CHANNEL ALLOCATION PROCEDURE FRAME SIZE (SLOTS) ..................................................44
PRIMARY CONTROL CHANNEL INTERLEAVE: OLL................................................................................44
BCCH INTERLEAVE: OL.......................................................................................................................45
NUMBER OF SECONDARY CONTROL CHANNEL: OLL............................................................................45
SECONDARY CONTROL CHANNEL INTERLEAVE: OLL...........................................................................45
MAXIMUM INTERLEAVE ........................................................................................................................45
TELEPHONE QUEUING TIMER: OL.........................................................................................................46
BUSY QUEUE MAX LENGTH ..................................................................................................................46
OPTIMAL NUMBER OF BRS FOR A GIVEN CELL ....................................................................................47
CHANNEL MINIMUMS............................................................................................................................47
Minimum Number of DCCH per cell: OL........................................................................................48
Minimum Number of I-6 Traffic Channels: OL ...............................................................................49
Minimum Number of I-3 TCH Per Cell: OL ....................................................................................49
CHANNEL HOLDBACKS .........................................................................................................................50
Holdback I12 DCCH: OL ................................................................................................................50
Holdback I6 TCH: OL......................................................................................................................51
Holdback I3 TCH: OL......................................................................................................................51
CHANNEL PREFERRED ...........................................................................................................................51
Preferred Number DCCH per Cell ..................................................................................................51
Preferred Number of I-6 TCHs per Cell ..........................................................................................52
Preferred Number I-3 TCH per Cell ................................................................................................52
NUMBER OF INTERCONNECT PAGING SUB-CHANNELS: OL...................................................................52
CELL ACCESS / PRIORITY ......................................................................................................................53
Bar from Cell ...................................................................................................................................53
Access Class .....................................................................................................................................53
Interconnect Call Class....................................................................................................................54
Interconnect Priority Value..............................................................................................................54
Public Access ...................................................................................................................................55
MULTIPLE PACKET DATA CHANNELS ...................................................................................................56
Cell PCH Auto Management: OL ....................................................................................................56
Maximum Number of Packet Channels: OL ....................................................................................57
Minimum Total Packet Channel Bandwidth: OL .............................................................................57
EBTS / RF PLANNING.........................................................................................................................58
HARDWARE PLATFORM: OLL ...............................................................................................................58
PRIMARY CONTROL CHANNEL: OLL ....................................................................................................58
BROADCAST CHANNEL CARRIER NUMBER: OLL..................................................................................59
NUMBER OF CARRIERS: OL; OLL ........................................................................................................59
TRANSMIT FREQUENCY, OL; OLL ........................................................................................................59
COLOR CODE: OL, OLL........................................................................................................................60
COLOR CODE EXTENSION: ....................................................................................................................61
COMBINER TYPE ...................................................................................................................................61
PCCH Redundancy ..........................................................................................................................61
CAVITY SWITCH TYPE...........................................................................................................................62
REDUNDANT BR ...................................................................................................................................62
COLOR CODE OF NEIGHBOR CELL.........................................................................................................63
CARRIER NUMBER OF NEIGHBOR CELL.................................................................................................63
SLOT TIMING ERROR THRESHOLD MODE: OL.......................................................................................64
June 19, 2006
Page 3 of 69
WP2003-007-2
RF CONGESTION RELIEF .......................................................................................................................64

Congestion Relief Trigger Threshold: OL .......................................................................................65
ProThreshold ...................................................................................................................................66
Congestion Relief Measurement Inquire Retry Timer: OL ..............................................................66
REFERENCES.......................................................................................................................................67
June 19, 2006
Page 4 of 69
WP2003-007-2
Table of Figures
Figure 1: Handover Process Summary ...................................................................................................11
Figure 2: SU-Initiated Handover: Class 1 Logic Diagram.....................................................................13
Figure 3: SU-Initiated Handover: Class 2 Logic Diagram ....................................................................14
Figure 4: SU-Initiated Handover: Class 3 Logic Diagram......................................................................14
Figure 5: FNE-Initiated Handover Logic Diagram ................................................................................15
Figure 6: Handover Timing Diagram .....................................................................................................16
Figure 7: Handover C/(I+N) Outbound Hysteresis Simulation Results..................................................20
Figure 8: Reconnection Mechanism........................................................................................................24
Figure 9: Dispatch Reconnection Logic Diagram ..................................................................................25
Figure 10: Packet Data Reconnection Logic Diagram ...........................................................................28
Figure 11: Cell Reselection Mechanism..................................................................................................30
Figure 12: Reselection Logic Diagram ...................................................................................................33
Figure 13: Frequency Band Specifier .....................................................................................................60
Notice to Users
While reasonable efforts have been made to assure the accuracy of this document, this document may contain technical or
typographical errors or omissions. Motorola, Inc. and its subsidiaries and affiliates disclaim responsibility for any labor,
materials, or costs incurred by any person or party as a result of using this document. Motorola, Inc., any of its subsidiaries
or affiliates shall not be liable for any damages (including, but not limited to, consequential, indirect, incidental, or special
damages or loss of profits or data) even if they were foreseeable and Motorola has been informed of their potential
occurrence, arising out of or in connection with this document or its use. Motorola, Inc. reserves the right to make changes
without notice to any products or services described herein and reserves the right to make changes from time to time in
content of this document and substitute the new document therefore, with no obligation to notify any person or party of such
changes or substitutions.
The information contained herein is Copyright 2006 Motorola, Inc. All rights reserved. Except as otherwise provided
herein, no part of this work may be reproduced or used in any form or by any means, electronic or mechanical (including
photocopying, recording, taping, or information storage and retrieval systems) without the express written permission of
Motorola, Inc. All authorized copies of this document must include the copyright notice as noted above and other
information contained in this notice.
SPECIFICATIONS SUBJECT TO CHANGE WITHOUT NOTICE
June 19, 2006
Page 5 of 69
WP2003-007-2
GENERAL
This white paper replaces iDEN update EBTIU029 (Significant RF Parameter) and presents
key, AIRGEN configurable, RF parameters. Whenever possible, guidance is provided as to
the impact of changing key parameters with the understanding that this addresses general
trends, rather than any specific case or scenario.
Parameters have been classified to correlate with their presentation and/or functional
description in complimentary documentation available on the iDEN customer documentation
web page. Where possible all associated parameters are grouped together.
RADIO LINK CONTROL

Radio Link Control comprises the functions of the EBTS (ACG/FNE) and Subscriber Unit
(SU/MS) required acquiring, monitoring and operating on the iDEN RF interface. It is
recommended that the latest revision of the Radio Link Control manual (68P81127E91) be
referenced. This manual may be obtained from the Motorola iDEN customer documentation
website.
NOTE:
The acronyms SU and MS are used interchangeably to describe the

iDEN subscriber unit.
Power Control
The iDEN system utilizes open loop power control to adjust the transmit power of the
subscriber unit. The reduction (cutback) in transmit power is a function of the downlink RSSI
(Pro) and a number of FNE parameters. The purpose of power control is essentially two fold:
1. Minimize near-far effect caused by adjacent channel interference.
2. Improve battery life.
Configurable EBTS parameters, associated with power control, are presented within this
section.
June 19, 2006
Page 6 of 69
WP2003-007-2
NOTE:
Discontinuous Transmission (DTX) is also employed by the SU,

when no audio is present at the microphone, to increase battery life.
During this operation the SU will transmit only on the mandatory
slots associated with the relevant interleave. For a 3:1 interconnect
call this is every 8th slot. It should be noted that excessive DTX
operation, for example extended muting during a conference call or
drive test, tends to result in decreased uplink SQE measurements.
In this instance, an increased number of Measurement Inquires may
be observed.
Transmit Power/Carrier: OL; OLL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Default Transmit Power Level

Once per BR per cell.
The transmit PA power per carrier for a Quad BR, or the total transmitted power
for a single BR.
This will be the same value for all carriers within a Quad BR.
Single BR (70W): 5W to 70W
Single BR (40W): 5W to 40W
1 Carrier Quad BR: 5W to 52.0W
2 Carrier Quad BR: 2.5W to 26.0W
Step Size:
Default Value:
Units:
Comments:
Note that pre-SR9.6, the minimum power per carrier for a Quad BR was 5W.
Post-SR9.6 the minimum composite power across all carriers on a Quad BR is
5W.
Single BR: 1W
Quad BR: 0.1W
5
Watts
The generally accepted practice is to set transmit power at or near balanced path
level determined from a link budget calculation. Additional gains from receive
diversity often allow the downlink to run 1-2dB hot, without a noticeable
degradation of performance.
Re Path Balance: It is recommended, that the power level of the BR be set to
balance the inbound and outbound paths. The path balance depends to some
extent on the amount of diversity gain achieved. Non-uniform balancing across a
system can result in inconstant reuse inference levels. Non-uniform balancing is
practiced frequently on the fringe of a system to provide maximum coverage in
less populated or less critical areas to higher power MSs. In such cases the reuse
interference must be carefully studied to determine the impact of higher powers on
sites using those frequencies closer to the core of the system. Please refer to
WP2003-010 for example link budgets and information on path balance issues.
June 19, 2006
Page 7 of 69
WP2003-007-2
Transmit Power (Pto): OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Default Value:
Units:
Comments:
Transmit Power (dBm): OL

Once per cell
Known as Pto, this parameter defines the average power output, measured in dBm,
at the transmit reference point. In standard configurations, this equates to output of
the RFDS rack (top of rack), i.e. where the antenna feedline connects to the cabinet.
The formula to calculate Pto is as follows: Pto = PCC - Desired_Pri + RxTxGain.
20 through 60 dBm
20
dBm (decibels with reference to 1 milliwatt)
Set to measured value, based on the cells link budget.
The standard GEN4 RFDS is designed such that a Pto value of 36dBm will provide
a balanced link.
Please reference WP2003-010 for example link budget information.
Cell Maximum Transmit Power of MS: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Related
Parameters:
Cell Maximum Transmit Power of MS

Once per cell
The maximum power a subscriber unit is allowed to transmit in a particular cell.
0 = 20 Watts
(43 dBm)
1 = 10 Watts
(40 dBm)
2 = 5 Watts
(37 dBm)
3 = 2 Watts
(33 dBm)
4 = 1 Watt
(30 dBm)
5 = 0.5 Watts
(27 dBm)
6 = reserved
7 = reserved
1
2 (enable mobiles)
Integer
Transmit power
Default transmit power output
Combiner type
Comments:
Setting this parameter higher than required will allow MSs to operate at higher
than required power. This could produce excessive inbound interference for MSs
that have their power limited due to power control algorithms.
Setting this parameter lower than required may limit the inbound path performance.
Typically, for urban designs, a setting of 5 is desirable to manage any potential
interference from any higher power portables, mobile subscriber units and control
stations. Please refer to WP2003-010 for additional information on settings to
balance inbound and outbound paths.
June 19, 2006
Page 8 of 69
WP2003-007-2
Receiver/Transmitter Gain: OL
Parameter Name:
Occurrence:
Definition:
Receiver/Transmitter Gain (dB): OL

Once per cell
This parameter defines the difference between receive and transmit antenna gains,
cable losses, and other gains.
Range of Values:
Default Value:
Units:
Comments:
0 thru 10 dB
0
dB
RxTxGain = Grx Gtx
Grx = the inbound path gain from the Rx reference point
Gtx = the outbound path gain from the Tx reference point
RxTxGain is calculated from the antenna to the reference point at the top of the RF
distribution rack and should be adjusted to accurately reflect the difference between
the gains in transmit and receive antenna systems. Any deviation can result in
unbalanced paths and system operational difficulties (handover and power control.
Since most cells use the same antenna and cables lines RxTxGain is normally 0 dB.
Special attention to this parameter is required whenever a Tower Top Amplifier
(TTA) or non-standard RFDS is deployed, which will typically require RxTxGain
to be increased to reflect an increase in the receive gain.
Note: System Gain is the total gains + losses from the top-of-the-rack to the BR
receiver for non-TTA configurations or gains + losses from the TTA to the BR
receiver for TTA configurations. Careful analysis is required whenever the setting
of this parameter and the associated parameters will change the System Gain from
its standard 8.5dB. Additional gain will reduce the IP3 intermodulation protection
of the receive system
Please refer to theWP2003-010 for information on TTA considerations.
Power Control Constant: OL

Parameter Name:
Occurrence:
Definition:
Power Control Constant (dBm): OL

Once per cell
The Power Control Constant (PCC) parameter is used by the SU to determine its
transmit power (Pti), based on the received signal strength (Pro).
PCC is defined as follows:
PCC = Pto + Desired_Pri RxTxGain
Where:
Desired_Pri = the desired receive power measured at the Rx reference point,
which is the BR antenna port. This parameter is derived.
A typical value is 88dBm.
June 19, 2006
Page 9 of 69
WP2003-007-2
Range of Values:
Default Value:
Units:
Comments:
-128 to +127 dBm

-100
dB
Typically values are 48dBm to 54dBm.
Adjustments to this parameter should carefully considered due to the direct impact
on SU transmit power, which is calculated as follows:
Since Desired_Pti = PCC - serving Pro, incorrect setting of this parameter will
cause poor uplink performance. Typical impact would be to uplink INI / poor SQE
as well as drop calls (LOT).
Desired_Pti = PCC - serving Pro
Thus, decreasing PCC will increase Pti.
Incorrect setting of this parameter will cause poor uplink performance. Typical
impact would be to uplink INI / poor SQE as well as drop calls (LOT).
Desired Pri
The Desired Pri is based upon maintaining a 36dB C/(I+N) (at the reference point) whether
using a TTA or not, and includes the effects of site noise and reuse interference.
The desired power level (Desired_Pri) is normally approximately -88dBm for a standard
hybrid/duplex system and will be approximately -81 to -85dBm with DTTA, which is a good
balance between operation with minimal frequency reuse and reasonable signal levels for
coverage. This will vary depending on system gain, whether a tower top amplifier is used, and
the effects of site noise or co-channel interference.
The following table can be used for a hybrid/duplex configuration in areas with moderate, high
and very high levels of uplink interference, typically due to co-channel interference from
frequency reuse.
Table 1: Desired_Pri
Desired_Pri
-88 dBm
-85 dBm
-82 dBm
-80 dBm
-75 dBm
Interference Condition
Approx. >-126dBm @ BR
No uplink interference
Approx. -117dBm @ BR
Low level of uplink interference
Moderate level of uplink interference
High level of uplink interference
Very high level of uplink interference
Please refer to WP2003-010 for further comments on this parameter.
June 19, 2006
Page 10 of 69
WP2003-007-2
Interconnect Handover
Handover is the mobility management function that occurs during an interconnect call and may
be initiated either by the FNE or, more commonly, by the SU. It is recommended that the
Handover Performance section of WP2003-011 also be referenced.
The following flow chart highlights the processes that control the point at which a handover is
requested.
SU
FNE
No
Measure downlink
SQE, RSSI on serving
and neighbor cells
foreground
nbr (s) meet downlink
handover requirement
?
FNE - Init. HO
Measure uplink
SQE on serving
cell
No
SQE < threshold?
Send measurement
inquire to SU
Yes
Yes
Handover Request
Build measurement report;
send into FNE via ACP *
FNE evaluates target

cell(s) one at a time
No
* SU must wait specified time before
sending new measurement report
** Neighbor cell list NOT updated after
intra-cell handover
resource
and sufficient uplink
C/(I+N) at target
No
?
All nbrs
checked?
Yes
Yes
Handover
successful
Read in new
neighbor
list**
SU handovers
to new freq
send handover
command with freq,
slot info
Handover
Blocked
Figure 1: Handover Process Summary

The previous diagram shows the SU continuously measuring channel quality on the serving
cell and neighbor cells and checking the results against the handover criteria. These actions
can be summarized as follows:
If the SU cannot find a foreground neighbor cell that meets downlink handover
requirement, measurements continue on serving and neighbor cells
If the SU finds an unconditional foreground neighbor cell that meets downlink handover
requirement, a handover request is made via a measurement report message, which is
sent to the FNE. The FNE evaluates the target cells one at a time.
o
If resources are not available or uplink channel quality is insufficient, at the handover
target cell, the next neighbor in the list is examined.
If all off the neighbors in the measurement report have been examined, the handover is
blocked.
June 19, 2006
Page 11 of 69
WP2003-007-2
If a handover target cell is found with resources and provides sufficient uplink channel
quality a handover command message is sent to the SU with carrier frequency, slot
number, and other information.
o
The SU hands over to the specified frequency and reads in new neighbor cell list,
which completes the handover operation.
There are 3 types scenarios than may result, as follows:
IntraCell: Between BRs or slots on a BR within the same cell.
IntraBSC: Between BRs on different cells, which may be on the same or different sites.
InterBSC: Between BRs on different cells on different BSCs.
The associated RF parameters are presented in the following sections.
Handover Class of Cell

Parameter
Name:
Occurrence:
Definition:
Range of
Values:
Step Size:
Default Value:
Units:
Comments:
Handover class of cell

Once per neighbor cell..
This parameter indicates, for each neighbor cell, whether the neighbor cell should
be considered for handover. Each neighbor cell (handover candidate) is assigned a
handover class based on desirability.
0 ... 3
1
2
None
This parameter is usually set to characterize closer neighbors with higher
desirability and further neighbors with lower desirability. Traffic loading and
coverage considerations may suggest a different strategy for assigning handover
class. A neighbor cell with more traffic capacity may be set with a higher
desirability while a neighbor cell with fewer channels may be set with lower
desirability.
This parameter is transmitted on the BCCH of the cell
IMPORTANT:
Changing this parameter has a drastic effect on

subscriber operation and hence system
performance.
Handover Class 0
This setting does not allow an interconnect handover to this neighbor. Such classification
occurs for Home Network Neighbor Search (HNNS) neighbors and also in cases where
extended neighbor lists are implemented to minimize dispatch call dragging. In this case the
Reconnect Class would be 1 and the Handover and Reselection Classes set to 0. It should be
noted that the Private Call Secondary Hang Timer feature was introduced to improve quality of
long dispatch calls and reduce the need to extended neighbor lists.
June 19, 2006
Page 12 of 69
WP2003-007-2
Handover Class 1
A Class 1 handover is purely SQE driven and is often phrased as handover to this neighbor
only if in trouble. The trigger for a Class 1 handover is defined as follows:
When the serving cell C/I+N falls below the threshold specified by hdvr C/I+N outbound
threshold.
AND
When the neighbor cell outbound C/I+N is better than the serving cell C/(I+N) + hdvr
C/I+N outbound hysteresis.
These rules are presented in the following logic diagram:
Downlink Serving SQE < OB Threshold

AND
Downlink Neighbor SQE >= Serving SQE + OB Hysteresis
AND
Uplink Neighbor C/(I+N) >= InterCell Floor
Figure 2: SU-Initiated Handover: Class 1 Logic Diagram
Handover Class 2
This is the default neighbor cell handover class and includes a Receive Signal Strength (RSSI)
component, which determines the SQE requirements (class 1 or class 3). The handover
triggers are as follows:
1.
If the RSSI of the neighbor is stronger than the serving cell by hdvr C/I+N outbound hysteresis dB,
handover to the neighbor under Class 3 SQE conditions:
When the serving cell C/(I+N) falls below the threshold specified by hdvr C/I+N
outbound threshold + hdvr C/I+N outbound hysteresis
OR
2.
When the neighbor outbound C/(I+N) is better than the serving cell outbound C/I+N.
If the RSSI of the neighbor is less than the serving cell + hdvr C/I+N outbound hysteresis,
handover to the neighbor under Class 1 SQE conditions:
When the servers C/(I+N) is better than the threshold specified by hdvr C/I+N
outbound threshold + hdvr C/I+N outbound hysteresis, handover to the neighbor if the
neighbors outbound C/(I+N) is better than this threshold. If the C/(I+N) of the
neighbor cell is lower than that of the server cell + hdvr C/I+N outbound hysteresis,
handover to the neighbor only if the outbound C/(I+N) of the server cell falls below
hdvr C/I+N outbound threshold and the neighbors outbound C/(I+N) is better than the
server cell by hdvr C/I+N outbound hysteresis.
June 19, 2006
Page 13 of 69
WP2003-007-2
These rules are presented in the following logic diagram:

Downlink Neighbor RSSI >= Serving RSSI + Hysteresis
AND
Downlink Neighbor SQE >= Threshold + Hysteresis

Downlink Neighbor SQE >= Serving SQE
OR
OR
Downlink Neighbor RSSI < Serving RSSI + Hysteresis

Downlink Serving SQE < Threshold
AND
AND


A typical phrase for class 2 is always handover to this neighbor if neighbor is better.
Handover Class 3
A Class 3 handover is typically used for traffic management to quickly off load traffic to
neighboring cells. Incorrect application of this handover can cause excessive handover
requests and subsequent performance issues. As previously stated, a class 3 handover request
is triggered under two conditions:
When the server cells C/(I+N) falls below the threshold specified by hdvr C/I+N
outbound threshold + hdvr C/I+N outbound hysteresis, handover whenever the neighbors
outbound C/(I+N) is better than the servers outbound C/(I+N).
When the servers C/(I+N) is better than the threshold specified by hdvr C/I+N outbound
threshold + hdvr C/I+N outbound hysteresis, handover to the neighbor if the neighbors
outbound C/(I+N) is better than this threshold.
These conditions are presented in the following logic diagram:

Downlink Neighbor SQE >= Threshold + Hysteresis
OR
AND

A phrase typically applied to class 3 handovers is: always handover to this neighbor even if
neighbor isnt better.
June 19, 2006
Page 14 of 69
WP2003-007-2
FNE Initiated Handovers

FNE Initiated handovers are triggered by poor uplink SQE and are a combination of handover
classes 2 and 3. The following diagram provides summary of the handover criteria.
Downlink Neighbor SQE >= OB Threshold
OR

AND
Uplink Serving SQE < IB Threshold

AND
Uplink Neighbor C/(I+N) >= Serving SQE + IB Hysteresis
Figure 5: FNE-Initiated Handover Logic Diagram
NOTE:
The majority of FNE Initiated handovers are IntraCell handovers, if

enabled. However, RF Congestion Relief handovers, which are all
FNE-Initiated, are IntraCell ONLY if a secondary band is deployed
in the cell and there is capacity available, else an InterCell handover
will occur.
Handover Acknowledge Timer

Parameter
Name:
Occurrence:
Definition:
Range of
Values:
Step Size:
Default Value:
Units:
Comments:
June 19, 2006
Hdvr acknowledge timer

Once per ACG
The amount of time the CRM (Communications Resource Manager) will wait for
handover to be acknowledged.
0 ... 86400000
1
2000
Milliseconds
The target ACG must send a handover acknowledge message, indicating that the
resources are available, before a handover command message can sent to the SU.
This is shown in the following handover timing diagram.
Under normal conditions, it is not recommended to deviate from the default setting
of 2 seconds.
Page 15 of 69
WP2003-007-2
Initiating
MS
Serving
EBTS
Measurement
Report
Serving
BSC
MSC /
VLR
Handover
Required
Target
BSC
Target
EBTS
Handover
Request
Handover Request
Acknowledge Timer:
Start/Stop
Handover
Request
Acknowledge
Handover
Command
Figure 6: Handover Timing Diagram
Maximum Candidates for Handover

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Related
Parameters:
Comments:
Max candidates for handover

Once per cell
The maximum number of candidates (neighbor cells) that can be listed in the
Measurement Report (MR) transmitted by the MS.
1 ... 6
1
2
None
Max foreground neighbor cells
This parameter is broadcast on the BCCH. When a need for handover is detected,
the MS sends a Measurement Report (MR) message to the ACG via ACP (in-band
signaling). This parameter specifies the maximum number of neighbor cells that
can be included in the MR.
The neighbors cells reported within an MR are ordered by handover class (highest
first, i.e. 3) and by Pro (downlink RSSI).
Reducing the number of candidates limits the ability of the FNE to select suitable
handover targets with available resources that also meet predicted inbound C/(I+N)
threshold targets. Increasing the number of candidates in the list may provide more
alternatives but this parameter should not be greater than the number of max
foreground neighbor cells. Note that a larger number of reported candidates may
delay the handover, which may in turn result in degraded SQE..
June 19, 2006
Page 16 of 69
WP2003-007-2
Maximum Foreground Neighbor Cells: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
Maximum foreground neighbor cells

Once per cell
This parameter indicates the number of neighbor cells in the foreground list. The
foreground list contains those neighbors most acceptable for handover and the
background group contains those least acceptable.
0 ... 15
1
3
None
A neighbor cell is moved into the foreground list and will be considered for
handover based upon outbound C/I+N and the number of successful color code
detects. The cells with the best C/I+N will be moved to the foreground list only if a
valid color code is detected and the outbound C/I+N is greater than
foregroundCINROutboundThreshold. Using a sliding window, the MS counts the
number of successful color code detects within the last foreground window colorcode receptions. If this number is less than or equal to foreground fail threshold,
then foreground viability has failed; and the neighbor cell is moved into the
background list
Adjusting this parameter also affects how often foreground and background
neighbors are measured. More foreground neighbors equates to more the time
between measurements whereas fewer foreground neighbors shortens the time
between neighbor measurements.
This value should be at least equal to or greater than the number of max candidates
for handover.
NOTE:
Systems using HNNS (Home Network Neighbor Search) to

facilitate the recovery of dispatch services for radio units that have
left the coverage area of their home network, may increase this
parameter by 1-2
Handover C/I+N Inbound Intercell Floor: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
June 19, 2006
Handover C/I+N inbound intercell floor

Once per cell
This parameter was introduced in SR4 to stop inbound handover flurries, rapid
bouncing of the SU between two cells during a SU-initiated handover. It is used to
verify that the target cells C/(I+N) is greater than a given threshold. Note that if
this test fails, the handover request will be blocked and the Handover Failed
Threshold statistic will be incremented at the target cell.
Please refer to the WP2003-011 [1] for handover flow charts.
14 ... 29
1
Page 17 of 69
WP2003-007-2
Default Value:
Units:
Comments:
28
dB
This parameter equates to the target cell acceptable_CINRi for SU-Initiated
handovers. Reference the Radio Link Control manual.
The default value was originally calculated by adding the hdvr C/I+N inbound
threshold and hdvr C/I+N inbound hysteresis. Testing has shown that handover
delay, as defined by the number of consecutive Measurement Reports from the MS
to the FNE, can be reduced by dropping this parameter from the 26-28 dB range to
20-24 dB.
In some instances, for dense urban areas, it has been reported that an improvement
in LOT rate resulted from adjusting this parameter from 22 to 24dB. It is
recommended to proceed cautiously with such changes.
Handover C/I+N Inbound Hysteresis: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
Hdvr C/I+N inbound hysteresis

Once per cell
The inbound C/I+N hysteresis, in dB, for evaluating handover candidates.
0 ... 15
1
6
dB
For an FNE initiated handover, the serving cell recognizes the need for a handover
when the inbound C/(I+N) falls below the threshold set by hdvr C/I+N inbound
threshold. The serving cell calculates an acceptable inbound C/(I+N) value by
adding hdvr C/I+N inbound hysteresis to the current inbound C/(I+N), which is
then passed to all neighbor candidates. This is the acceptable_CINRo. If a
candidate neighbor cell calculates that it will have an inbound C/(I+N) higher than
the acceptable value, a handover occurs.
An increase in this parameter would delay the handover until the target cell's
C/(I+N) ratio was much better than the current cell's C/(I+N) ratio. This could
cause the MS to hang onto a call too long (degrading audio and disrupting traffic
patterns). A decrease in this parameter could cause increased handover ping-pong.
This parameter is usually set between 6-8.
June 19, 2006
Page 18 of 69
WP2003-007-2
Handover C/I+N Inbound Threshold: OL

The default and range of this parameter have been reduced based on WP2002-026 [8]. These
changes are summarized in the following table:
Release
Pre-SR10.5
SR10.5
Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Related
Parameters:
Comments:
Range
14 to 29 dB
22 dB
Default
14 to 20 dB
18 dB
Hdvr C/I+N inbound threshold

Once per cell
The Inbound C/(I+N) threshold, in dB, for triggering FNE-Initiated handovers and
for evaluating handover candidates.
14 ... 20
1
18
dB
Hdvr C/I+N inbound hysteresis
Handover C/I+N inbound intercell floor
For an FNE initiated handover, the serving cell recognizes the need for a handover
when the inbound C/(I+N) falls below the threshold set by hdvr C/I+N inbound
threshold. The serving cell calculates an acceptable inbound C/I+N by adding hdvr
C/I+N inbound hysteresis to the current inbound C/I+N, which is then passed to the
acceptable neighbor candidates. If a candidate neighbor cell calculates that it will
have an inbound C/(I+N) higher than the calculated acceptable value, a handover
occurs.
An increase in this parameter would cause the MS to initiate a handover request
sooner under conditions of degrading C/(I+N).
Lowering this parameter may reduce the number of Measurement Requests from
the FNE and corresponding Measurement Reports from the MS due to low inbound
signals causing FNE initiated handovers.
Please refer to WP2002-026-1 [7] for current recommendation on the configuration
of this parameter.
Handover C/I+N Outbound Hysteresis: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Related
June 19, 2006
Hdvr C/I+N outbound hysteresis

Once per cell
The Outbound C/(I+N) hysteresis, in dB, for evaluating handover candidates. This
parameter is used differently depending on the handover class of cell of the
neighbor being considered for handover. This value is broadcast on the BCCH.
0 ... 15
1
6
dB
Hdvr C/I+N outbound threshold
Page 19 of 69
WP2003-007-2
Parameters:
Comments:
Handover class of cell

This parameter is usually set between 6-8. The summation of hdvr C/I+N
hysteresis + hdvr C/I+N threshold should be no more than 28 and no less than 26
for normal operation.
An increase in this parameter typically delays a handover until the target cell
C/(I+N) was much better than the current cell's C/(I+N) ratio. This could cause the
MS to hang onto a call too long (degrading audio and disrupting traffic patterns).
A decrease in this parameter could cause increased handover ping-pong (flurries).
Simulations studying the sensitivity of this parameter to change suggest acceptable
performance is limited to a range of 6-10 dB, with 6-8 dB providing optimal
C/(I+N) performance.
Recommended values are:
5.5dB Lognormal Standard Deviation 6-8dB hysteresis
8dB Lognormal Standard Deviation 6-10dB hysteresis
10dB Lognormal Standard Deviation 8-12dB hysteresis
Figure 7: Handover C/(I+N) Outbound Hysteresis Simulation Results
June 19, 2006
Page 20 of 69
WP2003-007-2
Handover C/I+N Outbound Threshold: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
Hdvr C/I+N outbound threshold

Once per cell
The Outbound C/I+N threshold on the serving cell for handover and for evaluating
handover candidates. This parameter is used differently depending on the handover
class of cell of the neighbor being considered for handover. This value is broadcast
on the BCCH.
This parameter is equal to the actual threshold in dB minus 14dB.
0 ... 15
1
8
dB
This parameter is usually set between 6-8. The summation of hdvr C/I+N
outbound hysteresis + hdvr C/I+N outbound threshold should be no more than 28
and no less than 26 in normal circumstances.
An increase in this parameter would cause the MS to initiate a handover request
sooner under conditions of degrading C/(I+N). However, setting this parameter too
high may cause excessive handover requests and handover ping-pong for
conditions where the ratio degrades slowly or when going through a long shallow
fade. Reducing this parameter may cause conditions where the audio degrades
below the recommended minimum C/(I+N) ratio for a longer time before handover
is actually accomplished.
Simulations have shown that the optimal range for this parameter is 20-24 dB with
20 providing the least number of handovers with optimal dropped call and C/(I+N)
performance.
Handover Switches
The BSC controls many aspects of the handover process of which the following parameters
External Handover Allowed

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments
June 19, 2006
Extrl_handover_allowed
Once per Cell in the Call Processor BSC
This field defines whether a handover (InterBSC) is allowed between cells on
different BSCs
0 do not allow
1 - allow
1
1
None
Other than for specific applications, External handovers should always be allowed.
Page 21 of 69
WP2003-007-2
InterCell Handover Allowed

Parameter Name:
Occurrence:
Definition:
Note:
Range of Values:
Step Size:
Default Value:
Units:
Comments
Inter_cell_handover_allowed
Once per Call Processor
This parameter indicates whether inter cell handover is allowed or not. When inter
cell handover is allowed then subscriber units can pass from one cell to another cell
within the same CP BSC, as long as this parameter is enabled/allowed for each of
the cells.
It is also 1 of 14 fields that make up the Cell ID table. Of those 14 fields 9 of them
are set to a default value.
0 do not allow
1 - allow
1
1
None
Other than for specific applications, InterCell handovers should always be allowed.
IntraCell Handover Allowed

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments
Intra_cell_handover_allowed
Once per Call Processor
This parameter indicates whether handover between BRs within the same cell is
allowed.
0: Do not allow Intra cell handover
1: Allow Intra cell handover
1
1
None
Typically, IntraCell handovers, being FNE-Initiated, are enabled when uplink
interference is problematic on specific channels. Performing an IntraCell handover
will improve call quality in these cases.
IntraCell handovers must be enabled to allow RF Congestion Relief handovers to
occur between primary and secondary bands within the same cell.
Handover Required Reject Switch

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
June 19, 2006
Handover_required_reject_switch
Once per Cell in the Call Processor BSC
This parameter indicates if the handover reject message is required to be sent to the
MSC. This is specified for each cell in the Call Processor BSC.
0 Do not use handover required reject
1 - Use handover required reject
1
0
None
If left off, this could delay handovers as any rejected handover causes the system to
wait 10 seconds before allowing another attempt. Excessively delayed handovers
tend to degrade quality and hence increase the probability of dropped calls.
Page 22 of 69
WP2003-007-2
Handover Debugging
Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Comments:
Handover Debugging
If set to True, the EBTS will send handover reports to the BSC for debugging
purposes.
True or False
False
This feature may be used during system performance analysis and/or
troubleshooting of handover related issues. It is not recommended to leave this
parameter on (TRUE) for extended period of time.
An example of the data provided is as follows:
Handover Result (successful, blocked due to resource or uplink quality)
Target cell acceptable CINRi
Estimated target cell C/(I+N)
Target cell Power Control Constant
MS maximum transmit power (ms_pti_max)
Target cell maximum transmit power of MS (cell_pit_max)
Target cell Pto
Target cell RxTxGain
Target cell INI
Serving cell Pro
Enhancements to this feature are incorporated in the RF Interference Management
feature to be deployed with SR11.
June 19, 2006
Page 23 of 69
WP2003-007-2
Dispatch Reconnection
Reconnection is the term used to describe mobility management during a dispatch call.
Dispatch reconnections are always initiated by SU measurements and are relatively simplistic,
when compared to an interconnect handover.
The following flow chart highlights the basic process.
No
SU
FNE
Foreground
nbrs meet downlink
reconnect
requirement
Measure downlink SQE of

serving and neighbor cells
Yes
Change freq. to 1st nbr
cell
FNE processing based upon

call stage and call type
Group Calls Queue
Private Calls typically end!
No
Decode PCCH
Send in dispatch
service request
TCH available?
Yes
Reconnect
Complete
Decode TCCH or
TCH
Change freq, slot
Assign call to TCH

freq, slot
Figure 8: Reconnection Mechanism
The MS can be in one of three states, each of which uses different reconnection algorithms.
1. MS is on the PCCH
In this state, a dispatch call is in the process of being set-up but has not yet been assigned a
traffic channel. If the serving cell outbound C/(I+N) drops below recon C/I+N outbound
threshold, a reconnection to a neighbor cell will occur if the neighbor outbound C/(I+N) is
greater than the serving cell outbound C/(I+N) + recon C/I+N outbound hysteresis.
2. MS is on a traffic channel
While receiving a call, a reconnection will occur if the serving cell C/(I+N) drops below
recon C/I+N min and if a neighbors outbound C/(I+N) is greater than that of the serving
cells outbound C/(I+N).
3. MS is on a temporary control channel (TCCH)
In this state, the traffic channel has been converted to a temporary control channel (i.e.
during the hang time of the BR). This state is like when the MS is on the PCCH.
.
June 19, 2006
Page 24 of 69
WP2003-007-2
NOTE:
It should be recognized that dispatch reconnections do not verify

that the target cell has sufficient resources to accept the call.
The typical reconnection criteria is presented within the following logic diagram and discussed
within this section:
Class 1 on TCH
Downlink Serving SQE < Recon OB C/(I+N) Low
Downlink Neighbor SQE >= Serving SQE + Recon OB C/(I+N) Hysteresis
AND
OR
Class 1 on TCCH
Downlink Serving SQE < Recon OB C/(I+N) Threshold
Downlink Neighbor SQE >= Serving SQE + Recon OB C/(I+N) Hysteresis
AND
Figure 9: Dispatch Reconnection Logic Diagram
Reconnection C/I+N Min: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
Recon C/I+N min

Once per cell
Reconnection threshold whilst on TCH..
0 ... 15
1
0
dB
If the serving cell outbound C/(I+N) drops below recon C/I+N outbound threshold,
a reconnection to a neighbor cell will occur if the neighbor outbound C/(I+N) is
greater than the serving cell outbound C/(I+N) + recon C/I+N outbound hysteresis.
This value is broadcast on the BCCH of the cell. This parameter is equal to the
actual threshold in dB minus 14dB. Note that the value of 14dB is chosen to force
the reconnection to occur during gaps in conversations. The MS will not reconnect
during a conversation unless the server is much weaker than the reconnection
threshold while on a PCCH or temporary control channel. Thus, the instant an MS
transmission ends, the reconnect threshold jumps upward, increasing the
probability of a reconnection during the repeater hang time.
As an example:
Recon C/I+N outbound threshold = 8
Recon C/I+N outbound hysteresis = 3
Recon C/I+N min
=0
June 19, 2006
Page 25 of 69
WP2003-007-2
The outbound C/I+N threshold is set at 8 + 14 = 22dB and the recon C/I+N min is
set at 0 + 14 = 14dB. If the MS is on the PCCH or a TCCH, a reconnection to
another cell will occur if the serving cells C/(I+N) drops below 22dB and the
neighbors C/(I+N) is 3 dB stronger than that of the serving cell. If the MS is on a
traffic channel, i.e. during the talk phase of a call, a reconnection will occur if the
serving cells C/(I+N) drops to 14dB and a neighbors C/(I+N) is stronger than that
of the server.
Increasing this parameter above 0 (14) would increase the probability of
reconnection during RF fades. However, the list of potential neighbors is not
updated upon reconnect so only one reconnect during a call can be accomplished
reliably.
Lowering this parameter would increase the probability of dragging the dispatch
call into areas with low C/(I+N), resulting in degrading audio quality.
Reconnection C/I+N Outbound Hysteresis: OL

Parameter Name:
Occurrence:
Definition:
Example:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
Recon C/I+N outbound hysteresis

Once per cell
Reconnection hysteresis while on TCCH.
0 ... 15
1
3
dB
Based on simulations (reference section IMPORTANT:), the recommended
default range for this parameter is 6-8dB. A recommended default range for the
corresponding threshold parameter is 20-22 dB respectively is recommended that
the sum of the hysteresis and the threshold be no more than 28 dB due to nonlinearity in SQE above this level and limited tests in typical applications. (Use 20
and 8 or use 22 and 6 for threshold and hysteresis.) Other values may be beneficial
in unusual circumstances but careful consideration is advised before changing these
parameters significantly.
As an example:
Recon C/I+N outbound threshold = 8 (8 + 14 = 22dB)
Recon C/I+N outbound hysteresis = 3
Recon C/I+N min
= 0 (0 + 14 = 14dB)
The outbound C/(I+N) threshold is set at 22dB. If the MS is on the PCCH or a
TCCH, a reconnection to another cell will occur if the serving cells C/(I+N) drops
below 22dB and the neighbors C/(I+N) is 3 dB stronger than that of the serving
cell. If the MS is on a traffic channel, i.e. during the talk phase of a call, a
reconnection will occur if the serving cells C/(I+N) drops to 14dB and a
neighbors C/(I+N) is stronger than that of the server.
Lowering the hysteresis will increase the probability of reconnecting. However, the
list of potential neighbors is not updated upon reconnect so only one reconnect
during a call can be accomplished reliably.
June 19, 2006
Page 26 of 69
WP2003-007-2
Increasing the hysteresis substantially may cause the dispatch call to drag into
areas with lower C/(I+N), resulting in degraded audio quality. A reasonable
operational setting for this parameter is in the 3-6 dB area.
Reconnection C/I+N Outbound Threshold: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
Recon C/I+N outbound threshold

Once per cell
Threshold for private and group call reconnection while when not on TCH, i.e. on
the PCCH or TCCH between PTTs.
0 ... 15
1
8
dB
This parameter is equal to the actual threshold in dB minus 14 dB
Increase this value to cause the MS to reconnect to a new cell at a higher C/(I+N)
value while not in the talk phase of a dispatch call. Decrease this parameter to
cause the MS to initiate a reconnection at a lower C/(I+N) level.
The recommended default range for this parameter is 20-22 dB based on
simulations and on limited tests in typical scenarios. A recommended default range
for the corresponding hysteresis parameter is 8-6 dB respectively is recommended
that the sum of the hysteresis and the threshold be no more than 28 dB due to nonlinearity in SQE above this level and limited tests in typical applications. (Use 20
and 8 or use 22 and 6 for threshold and hysteresis.) Other values may be beneficial
in unusual circumstances but careful consideration is advised before changing these
parameters significantly.
Reconnection class
Parameter Name:
Occurrence:
Definition:
Range of Values:
Default Value:
Units:
Comments
June 19, 2006
Reconnection class
Once per neighbor
Indicates, for each neighbor cell, whether the cell should be considered for
reconnection. Reconnection is mobility management during a dispatch call.
Unlike handover class, a neighbor is either considered or not considered for
reconnection. There are not multiple levels of reconnection desirability.
0, 1, 2, 3
2
None
0
Don't consider for reconnection
1
Consider for reconnection
2
3
Page 27 of 69
WP2003-007-2
Packet Data Reconnection

The Packet Data (PD) reconnection process is a composite of Dispatch reconnection and
Interconnect handover class definitions. The various Packet Data reconnection conditions are
presented in the following logic diagram.
Class 1
Downlink Serving SQE <OB C/(I+N) Threshold
AND
AND
Class 2: RSSI Driven

Downlink Neighbor RSSI >= Serving RSSI + OB RSSI Hysteresis
Downlink Neighbor SQE >= OB Threshold + OB Hysteresis
OR
OR
Class 2: SQE Driven
OR
Downlink Neighbor RSSI < Serving RSSI + OB Hysteresis

Downlink Serving SQE <OB Threshold
AND
Downlink Neighbor SQE >= Serving SQE + OB C/(I+N) Hysteresis
Class 3
Downlink Neighbor SQE >= OB Threshold + OB C/(I+N) Hysteresis
OR
Class 1: Data Transfer in Progress

Downlink Serving SQE < OB C/(I+N) Low
Downlink Neighbor SQE >= Serving SQE + OB C/(I+N) Hysteresis
AND
Figure 10: Packet Data Reconnection Logic Diagram
PD Reconnect CINRo Hysteresis: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
June 19, 2006
PD Reconnect CINRo Hysteresis

Once per cell
Used for hysteresis in cell Packet Data reconnection.
0 ... 15
1
6
dB
Reference Handover C/I+N Outbound Hysteresis: OL
Page 28 of 69
WP2003-007-2
PD Reconnect CINRo Low: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
PD Reconnect CINRo Low

Once per cell
Defines a value used to trigger reselection during the talk phase of a PD call.
1 ... 15
1
14
dB
Reference Reconnection C/I+N Min: OL
PD Reconnect CINRo Threshold: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
PD Reconnect CINRo Threshold

Once per cell
Used to trigger reconnection while not in the talk phase of a Packet Data call.
0...30
1
22
dB
Reference Handover C/I+N Outbound Hysteresis: OL
PD Reconnect Pro Hysteresis: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
June 19, 2006
PD Reconnect Pro Hysteresis

Once per cell
Used for hysteresis in cell Packet Data reconnection.
0 ... 15
1
6
dB
This parameter is unique to Packet Data. For Interconnect Handovers a single
hysteresis parameter is used for C/(I+N) and RSSI (Class 2 HO).
Page 29 of 69
WP2003-007-2
PD Reconnection Class
Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
PD Reconnection Class
Once per cell
Indicates, for each cell and neighbor cell, whether the cell should be considered for
Packet Data reconnection.
0 = do not consider for reselection
1-3 = do consider for reselection where higher values indicate more desirability.
0...3
1
2
None
Reference Handover Class of Cell
Idle Mode Procedure (Cell Reselection)

Cell Reselection occurs when the SU is in idle mode, i.e. on the P/SCCH, and is based solely
on (downlink/outbound) measurements of serving and neighbor cell RSSI (Pro) and SQE
(CINRo). The FNE is not involved in this process hence success is dictated by the RF
conditions and parameters broadcast over the BCCH, as indicated in the following flow chart:
No
Foreground
nbrs meet downlink
reselect
requirements?
Measure downlink SQE, RSSI of

serving and neighbor cells
Yes
Change freq. to top
foreground target
Cell selection
(Rescan Bandmap)
red-light
Successfully
decode PCCH of
new cell?
No
No
Yes
Yes
New
cell characteristics
OK?
Read BCCH of new cell
Figure 11: Cell Reselection Mechanism
June 19, 2006
Page 30 of 69
WP2003-007-2
NOTE:
As can be seen, a failed reselection results in the SU entering cell

selection, which is a RED light condition. Please refer to the Radio
Link Control manual [3] for details on the Cell Selection algorithm.
Reselection C/I+N Outbound Threshold: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
Resel C/I+N outbound threshold

Once per cell
The Outbound C/I+N threshold on the serving cell for reselection and for
evaluating reselection candidates. This parameter is used differently depending on
the reselection class of the neighbor being considered for reselection. Please
reference Reselection Class.
This value is broadcast on the BCCH of the cell. This parameter is equal to the
actual threshold in dB minus 14dB, i.e. 8 22dB
1 ... 15
1
8
dB
An increase in this parameter would cause the MS to initiate a reselection request
sooner under conditions of degrading C/(I+N). However, setting this parameter too
high may cause excessive reselection requests and reselection ping-pong for
conditions where the ratio degrades slowly or when going through a long shallow
fade.
Reducing this parameter may cause conditions where a new message may degrade
below the recommended minimum in the C/(I+N) ratio for a longer time before
reselection is actually accomplished.
Reselection C/I+N Outbound Hysteresis: OL

Parameter Name:
Occurrence:
Definition:
Resel C/I+N outbound hysteresis

Once per cell
The Outbound C/I+N hysteresis, in dB, for evaluating reselection candidates.
Range of Values:
Step Size:
Default Value:
Units:
Related
This parameter is used differently depending on the reselection class of the

neighbor being considered for reselection. See the description of reselection class
or Appendix 1 for a detailed explanation. This value is broadcast on the BCCH of
the cell.
0 ... 15
1
6
dB
Reselection C/I+N outbound threshold
June 19, 2006
Page 31 of 69
WP2003-007-2
Parameters:
Comments:
Reselection class
An increase in this parameter would delay cell reselection until the target cell's
C/(I+N) ratio was much better than the current cell's C/(I+N) ratio. This may cause
the MS to camp onto a cell too long. A decrease in this parameter may cause
increased reselection ping-pong.
Reselection Class
Parameter Name:
Occurrence:
Definition:
Range of Values:
Default Value:
Units:
Comments:
Reselection Class
Once per neighbor
This parameter indicates for each neighbor cell, whether the neighbor cell should
be considered for reselection. Reselection is the mobility management function
that occurs when the MS is in the idle mode. Each neighbor is assigned a
reselection class based on desirability.
0, 1, 2, 3
2
None
Reference Handover Class of Cell
This parameter is transmitted on the BCCH of the cell and can be set to indicate
closer neighbors with higher desirability and further neighbors with lower
desirability. Traffic loading or coverage considerations may suggest a different
strategy for assigning this parameter. A neighbor cell with more traffic capacity
may be set with a higher desirability while a neighbor cell with fewer channels may
be set with lower desirability. Several low sites may be "covered" by one higher
site and the handover classes may be assigned such that the higher site is less
desirable to prevent all MS's from migrating to the single high site.
June 19, 2006
Page 32 of 69
WP2003-007-2
The following logic diagram presents the criteria for reselection for each of the four classes.
Class 1
AND
AND
Class 2: RSSI Driven

Downlink Neighbor RSSI >= Serving RSSI + OB Hysteresis
OR
OR
OR
Class 2: SQE Driven

Downlink Neighbor RSSI < Serving RSSI + OB Hysteresis
AND
Class 3
OR
Figure 12: Reselection Logic Diagram
Reselection Class 0:
This setting does not allow a reselection to this neighbor. Such classification occurs for Home
Network Neighbor Search (HNNS) neighbors and also in cases where extended neighbor lists
are implemented to minimize dispatch call dragging. In this case the Reconnect Class would
be 1 and the Handover and Reselection Classes set to 0.
Reselect this neighbor only if in trouble.
When the serving cells C/(I+N) falls below the threshold specified by the sum of reselection
C/I+N outbound threshold + rsel C/I+N outbound hysteresis, reselect whenever the neighbors
outbound C/(I+N) is better than the servers outbound C/(I+N). Otherwise, never reselect the
neighbor.
Always reselect this neighbor if neighbor is better.
If the signal strength (RSSI) of the neighbor is stronger than the serving cell by rsel C/I+N
outbound hysteresis dB, reselect the neighbor under two conditions:
When the server cells C/(I+N) falls below the threshold specified by the sum of
reselection C/I+N outbound threshold + rsel C/I+N outbound hysteresis, reselect whenever
the neighbors outbound C/I+N is better than the servers outbound C/(I+N).
June 19, 2006
Page 33 of 69
WP2003-007-2
When the servers C/(I+N) is better than the threshold specified by the sum of reselection
C/I+N outbound threshold + rsel C/I+N outbound hysteresis, reselect to the neighbor if the
neighbors outbound C/(I+N) is better than this threshold. If the signal strength of the
neighbor cell is lower than the sum of the server cell C/(I+N) + hdvr C/I+N outbound
hysteresis dB, reselect the neighbor only if the outbound C/(I+N) of the server cell falls
below reselection C/I+N outbound threshold and the neighbors outbound C/(I+N) is better
than the server cell by rsel C/I+N outbound hysteresis dB.
Class 3 equates to Always reselect this neighbor even if neighbor isnt better. Reselection
will occur under two conditions:
When the server cells C/(I+N) falls below the threshold specified by the sum of
reselection C/I+N outbound threshold + rsel C/I+N outbound hysteresis, reselect whenever
the neighbors outbound C/I+N is better than the servers outbound C/(I+N).
When the servers C/(I+N) is better than the threshold specified by the sum of reselection
C/I+N outbound threshold + rsel C/I+N outbound hysteresis, reselect the neighbor if the
neighbors outbound C/(I+N) is better than this threshold.
It can be seen that Class 2 is a combination of Class 1 and Class 3. Which algorithm is used is
dependent upon the signal strength (RSSI), not signal quality (SQE,) of the neighbor in
relation to that of the server.
Reselection Measurement Period: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Units:
Comments:
Resel measurement period

Once per cell
The number of PCCH slots between measurements on the serving or neighbor cell.
The value of this parameter depends on the setting of primary control channel
(PCCH) interleave.
1 ... 15
1
Integer
General recommendations are:
1
12:1 PCCH Interleave
2
6:1 PCCH Interleave
1 to 2 BRs
> 2BRS
180mS
360mS
Deviations may cause unusual and/or uneven distribution of server and neighbor
cell measurements.
June 19, 2006
Page 34 of 69
WP2003-007-2
Idle Mobility Timers
Timer for Location Updating

Parameter Name:
Occurrence:
Definition:
Timer for location updating

Once per cell
The time-out value (in segments of 10 hours) used for periodic interconnect
location area updating within the cell. Even if an MS hasnt crossed an
interconnect location area boundary, it can be told to periodically do a location
update.
Location updating is an interconnect process and is similar to a dispatch renewal.
However, a location update occurs on a DCCH channel and contributes to DCCH
loading. A dispatch renewal doesnt.
Range of Values:
Step Size:
Default Value:
Units:
Comments
This parameter is set to a value equal to 1/10 the required time interval in hours. A
value of 0 indicates that periodic updating is not enabled (infinite time-out) for
this cell. Lowering the value of this parameter will cause an increase in DCCH
traffic since interconnect location area updates will occur more frequently.
0 ... 255
1
2
Tens of Hours
This parameter will force a location update from a MS, in idle mode, which has
remained IDLE within the same ILA for greater than the value set.
Timer for Registration Renewal (Hours)

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
June 19, 2006
Timer for Registration Renewal (Hours)

The timeout value used for periodic registration renewal. The maximum elapsed
time between registrations or registration renewals is set through this parameter.
A value of 0 indicates that periodic registration renewal is not enabled.
0 thru 255 hours
1
10
Hours
This parameter will force a registration renewal from a MS, in IDLE mode, which
has remained within the same DLA for greater than the value set
Page 35 of 69
WP2003-007-2
Channel Quality Measurements

Handover INI Window
Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
Hdvr INI Window

Once per cell
The number of measurements, by the ACG on idle channels, which are used to
produce the measured inbound interference level of an idle server. The most recent
hdvr INI window measurements are used in calculating the interference level.
1 ... 60
1
3
Integer
If Hdvr INI window = 3, then the last most 3 inbound interference measurements
are used in calculating the interference level of the idle server.
A shorter measurement window would provide a more instantaneous value, which
may not accurately represent what an MS will experience if transferred to that cell
for a call.
A significantly longer window might average over too long a time and not reflect
temporary local interference levels that may exist at the time of a handover. Long
term averaging may also adversely impact the availability of AGC memory and
processing resources.
Handover Inquire Interval

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
June 19, 2006
Hdvr inquire interval

Once per ACG
The rate at which the ACG sends Measurement Inquire (MI) messages to the MS.
When a need for an FNE-Initiated handover is calculated determined, the ACG
sends a Measurement Inquire message to the MS. The MS responds with a
Measurement Report (MR) for each Measurement Inquire message received. The
repetition rate at which the ACG sends the Measurement Inquire message is
specified by hdvr inquire interval.
30 ... 2000
10
1000
milliseconds
iDEN mobility management relies on the measurement of uplink and downlink path
C/(I+N). When either path detects a C/(I+N) level, which does not meet defined
criteria, a request for information and handover is initiated. If the requested
handover meets established criteria, the handover occurs. If the requested handover
does not meet established criteria, then the handover is denied and the detecting
device must initiate another request. Please refer to WP2003-011 [1] for
information on the statistics pegged for these events.
Page 36 of 69
WP2003-007-2
Handover requests are not queued as conditions may change very quickly due to
RF fading. A momentary requirement for handover may disappear as the MS
moves from a fade back into coverage. By design, the device detecting low signal
level conditions must continue to request a handover if the initial request is denied
for one of several reasons.
This parameter can be used to moderate the frequency of Measurement Inquiry
(MI) messages from the FNE to the MS. A lower number might cause a large
number of MI requests that could not be fulfilled without overloading MS
resources. The MIs are sent using ACP, which steals bits from the message data
capacity (voice).
Too many MIs may degrade audio quality as the number of bits for voice is
decreased. The handover delay may become too great and the audio quality may
degrade if the time between MIs on a quickly degrading path is extended too long.
A system experiencing widespread consecutive MIs may reduce the bit stealing
impact of multiple consecutive MIs by increasing the interval slightly (~2 sec.,
parameter = 2000) interval. Caution is advised as the handover delay can increase
by increasing this parameter.
Handover Report Interval: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
Hdvr Report Interval

Once per cell
When a need for handover is calculated by the FNE, the ACG sends a
Measurement Inquire message to the MS. The MS responds with a Measurement
Report (MR) for each Measurement Inquire (MI) message received.
When the MS determines the need for a handover, a MR is sent to the FNE and the
Hdvr Report Interval specifies the repetition rate at which MRs are sent.
The actual value is 24 times the parameter setting. This parameter is broadcast on
the BCCH.
1 ... 15
1
3
None
If Hdvr Report Interval = 3, then the time between Measurement Report
messages is set at 3*24 or 72 timeslots
The default value is recommended unless cell configurations used to off load calls
to a sponge cell cause an excessive volume of MRs. In this instance, increasing
this value may be desirable to reduce the volume of MRs. However, caution is
advised when adjusting this parameter so as not to degrade quality due to delayed
handovers.
Note that MRs sent while the FNE is processing a previous MR will be ignored.
June 19, 2006
Page 37 of 69
WP2003-007-2
Handover Server Window: OL

Parameter Name:
Occurrence:
Definition:
Hdvr Server Window

Once per cell
The number of measurements made by the ACG on its active channels, which are
used to produce inbound C/I+N measurements.
Range of Values:
Step Size:
Default Value:
Units:
Comments:
1 ... 100
1
28
None
The measurement of the inbound C/(I+N) is valid only if a successful color code
detect also occurs for the timeslot being measured. An inbound measurement can
be made every 15ms, thus for the default value of 28, the measurement period is
.015x28= .42 seconds long.
The default value is recommended.
A lower value would produce a more instantaneous value that may reflect more
momentary RF fades. A larger value for this parameter may cause the FNE to react
too slowly to quickly changing RF conditions.
Because there must also be successful color code detection, some long interval
measurements may be unreliable in highly faded environments.
Foreground Fail Threshold: OL

Parameter Name:
Occurrence:
Definition:
Foreground Fail Threshold (slots)

Once per cell
Neighbor Cell foreground viability is based on successful color code detects and is
controlled by two BCCH parameters: foreground fail threshold and foreground
window.
Example:
Foreground fail threshold = 4

Foreground window = 7
5 or more of the last 7 color code receptions must be detected for the cell to
consider for foreground membership.
1 to 15
1
4
None
Using a sliding window, the MS counts the number of successful color code detects
within the last foreground window color-code receptions. If this number is less
than or equal to foreground fail threshold, then foreground viability has failed; and
the neighbor cell is moved into the background group. Only those cells in the
foreground group are considered as handover candidates. The Maximum
Candidates for Handover parameter sets how many cells can be in the foreground
group. Cells that are in the foreground list are sampled more frequently for C/I+N
measurements.
Range of Values:
Step Size:
Default Value:
Units:
Comments:
.
June 19, 2006
Page 38 of 69
WP2003-007-2
Reduce this parameter to allow more neighbor cells with less reliable signal levels
to populate the foreground list. For Example: There is a coverage gap to the nearest
neighbor cells in a given direction. Reducing this parameter would allow the MS to
identify the more remote neighbors as potential handover targets.
Increase this parameter to insure foreground neighbors are more reliable handover
targets.
Maximum Foreground Neighbor Cells: OL

Parameter Name:
Occurrence:
Definition
Range
Step
Default
Units
Comments:
Foreground Max
Once per cell
The number of cells allowed in the foreground list
1-15
1
3
Integer
Decreasing the maximum number of foreground candidates will reduce the time to
measure foreground cells and hence reduce the time between background cell
measurements.
Foreground Window (slots): OL

Parameter Name:
Occurrence:
Definition
Range of Values:
Step Size:
Default Value:
Units:
Comments:
Foreground window
Once per cell
Slot over which foreground neighbor RSSI and SQE is averaged.
1 to 15
1
7
None
Increasing the Foreground Window increases the number of samples taken for each
evaluation period. Thus, increasing in this parameter to reduce handover pingpong will increase the measurement period.
Simulations have shown that the optimal averaging length falls between 5-9 slots.
Lower values will increase total handovers and bad handover percentages while
larger values will increase dropped calls.
June 19, 2006
Page 39 of 69
WP2003-007-2
Foreground C/(I+N) Outbound Threshold: OL

Parameter Name:
Occurrence:
Definition:
Example:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
Foreground C/(I+N) Outbound Threshold

Once per cell
The foreground CINRo threshold determines whether the neighbor cell's outbound
C/I+N ratio is good enough for the cell to be in the MS foreground group. The
neighbor is only placed in the foreground list if the outbound C/I+N ratio equals or
exceeds Foreground CINRo Threshold and the number of successful color code
detects exceeds the threshold set by foreground fail window and foreground
window. Cells that are in the foreground list are sampled more frequently for
C/I+N measurements. This parameter is equal to the actual threshold in dB minus
14dB.
Threshold = 16 dB
Foreground C/(I+N) Outbound Threshold = 2
0 ... 15
1
2
None
Reduce this parameter to allow neighbor cells with lower C/(I+N) signal levels to
populate the foreground list. Fewer foreground neighbors are also sampled more
often.
Increase this parameter to insure foreground neighbors have higher C/(I+N) levels.
More foreground neighbors are sampled less frequently.
Serving Window: OL
Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
Serving Window
Once per cell
This parameter is broadcast on the BCCH of the cell.
The number of measurements made by the MS on the serving cell that are used to
produce outbound C/I+N measurements.
1 ... 15
1
7
None
The outbound C/I+N of the serving cell are obtained by averaging together the last
most serving window C/I+N measurements by the MS. The measurement of the
outbound C/I+N is valid only if a successful color code detect also occurs for the
timeslot being measured. An outbound measurement is made every 90ms, thus for
the default value of 28, the measurement period is 0.090 x 2 8 = 2.52 seconds long.
The actual number of measurements is 4 times the value of this parameter.
Decreasing this value will shorten the interval and make the measurement less
accurate. This is likely to cause more rapid switching between sites while on an
interconnect call. Lessening this value significantly will cause ping-pong between
sites.
June 19, 2006
Page 40 of 69
WP2003-007-2
Increasing this value will make it more difficult to handover quickly in situations
where the signal degrades quickly and the measurement may not accurately reflect
fast fading environments.
Simulations have shown that the optimal setting for this parameter is 20-36 slots.
Average lengths below this will increase dropped calls, total handovers, and bad
handover percentages. Larger average lengths will decrease C/(I+N)..
Channel Disconnect and Failure

These parameters are used by the FNE and SU to determine when the RF channel has been
lost. Adjusting these parameters impacts the Loss of Transmission (LOT) rate.
A channel disconnect, as logged by the SU, would be classed as an Uplink channel failure. A
channel failure, logged by the SU, would be classed as a Downlink channel failure.
NOTE:
Split 3:1 channel disconnects and failures will be detected

somewhat differently by the SU and FNE due to changes in the
channel format, however the same cell parameters as legacy
channels will apply.
FNE Fail Threshold: OL

Parameter Name:
Occurrence:
Definition:
FNE Fail Threshold

Once per BR
To determine an RF channel failure, the BR counts the number of valid SDBs
within the last FNE fail window received timeslots. A Slot Descriptor Block (SDB)
is a header on each timeslot that contains information about the slot. If the number
of valid SDBs is the same as or falls below FNE fail threshold, a failure is detected
and the ACG will disconnect the channel.
Note:
Range of Values:
Step size:
Default value:
Units:
Comment:
The recommended setting for this parameter is 0.

0 ... 6
1
None
If discontinuous transmission is used (DTX period set to 2 - 15), only those slots
requiring an MS transmission will be monitored.
Note that this parameter is tightly coupled to the FNE fail window parameter.
Increasing this parameter up from 0 allows the MS to detect a loss of FNE
communications more quickly but an increase would also makes it more difficult to
maintain the channel through RF fades and small coverage holes.
The FNE fail window parameter can be increased to require a longer period of time
before declaring a channel failure. Likewise the FNE fail window may be reduced
to allow a shorter period before detecting a channel failure.
June 19, 2006
Page 41 of 69
WP2003-007-2
FNE Fail Window: OL

Parameter Name:
Occurrence:
Definition:
Note:
Range of Values:
Step Size:
Default Value:
Units:
Comment:
FNE Fail Window

Once per BR
To determine an RF channel failure, the BR counts the number of valid SDBs
within the last FNE fail window received timeslots. A Slot Descriptor Block (SDB)
is a header on each timeslot that contains information about the slot. If the number
of valid SDBs is the same as or falls below FNE fail threshold, a failure is detected
and the ACG will disconnect the channel. If discontinuous transmission is used
(DTX period set to 2 - 15), only those slots requiring an MS transmission will be
monitor.
The recommended setting for this parameter is 12.
1 ... 24
1
None
Note that this parameter is tightly coupled to the FNE fail threshold parameter. The
FNE fail window parameter can be increased to require a longer period of time
before declaring a channel failure. Likewise the FNE fail window may be reduced
to allow a shorter period before detecting a channel failure.
MS Fail Threshold: OL
Parameter Name:
Occurrence:
Definition:
Example:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
June 19, 2006
MS Fail Threshold
Once per cell
The MS is constantly monitoring the Slot Descriptor Blocks (SDB) transmitted by
the BR. To determine an RF channel failure, the MS counts the number of valid
SDBs within the last ms fail window receptions. If the number of valid SDBs is the
same as or falls below ms fail threshold, a failure is detected and the MS will leave
the channel. This parameter is set to 1/2 the actual required value. MS fail window
is also set to 1/2 the actual required value and must always be greater than this
parameter. This parameter is broadcast on the BCCH.
MS fail window = 6
MS fail threshold = 1
An RF channel failure is detected if 2 or less SDBs are detected within the last 12
SDB receptions.
0 ... 15
1
0
None
Increasing this parameter requires more successful SDB decodes and increases the
probability that the MS will signal a channel failure. The MS would be less
tolerant to RF fades if this parameter were increased without a corresponding
increase in the ms fail window.
Page 42 of 69
WP2003-007-2
MS Fail Window: OL
Parameter Name:
Occurrence:
Definition:
Example:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
MS Fail Window
Once per cell
The MS is constantly monitoring the Slot Descriptor Blocks (SDB) transmitted by
the BR. To determine an RF channel failure, the MS counts the number of valid
SDBs within the last ms fail window receptions. If the number of valid SDBs is the
same as or falls below ms fail threshold, a failure is detected and the MS will leave
the channel. This parameter is set to 1/2 the actual required value. ms fail
threshold must always be less than this parameter. This parameter is broadcast on
the BCCH.
MS fail window = 6
MS fail threshold = 1 (Parameter setting is half of the actual value used.)
An RF channel failure is detected if 2 or less SDBs are detected within the last 12
SDB receptions.
1 ... 15
1
6
None
Reduce this parameter to cause the MS to signal a channel failure more quickly.
Reducing the number may cause the MS to signal failure even though the MS has
gone through a short RF fade. Increase this parameter to increase the time before
the MS signals a channel failure.
CHANNEL ALLOCATION
Optimization of the Dynamic Channel Algorithm (DCA) parameters depends on the
dispatch/telephone/DCCH traffic mix in each cell. The ACG will assign resources in the most
efficient manner, however this process can be influences by the parameters presented within
this section.
The grade of service must be monitored for each service and the DCA parameters must be
adjusted accordingly. The most productive way of balancing telephone and dispatch blocking
is by adjusting the min3 and min12 parameters. The exact value depends on the ratio of
telephone to dispatch traffic and relative blocking levels. Min6 is defaulted to zero since 6:1
channels are easier to allocate than 3:1 channels.
The introduction of Split 3:1 channels adds another set of rules to DCA, however since a full
3:1 must be available to allocated two Split 3:1 subslots no new DCA parameters have been
introduced. Note that the order of allocation for a Split 3:1 is as follows:
1. If MS is secondary band capable, allocate the unassigned subslot mate of an existing split
3:1 call on the secondary band.
2. Allocate the unassigned subslot mate of an existing split 3:1 call on the primary band.
3. If MS is secondary band capable, reserve a new I3 on secondary band and allocate a
subslot of that 3:1 for the split 3:1 call.
4. Reserve a new 3:1 on the primary band and allocate a subslot of that 3:1 for the split 3:1
call.
5. Queue the request (queuing a request may initiate a request to withdraw a full 3:1 channel
from the PCH)
June 19, 2006
Page 43 of 69
WP2003-007-2
The ACG selects the channel with the best quality (lowest I+N) within the highest class an
available split 3:1 subslot exists. In the cases of 3 and 4, the ACG looks for the lowest subslot
I+N within a full 3:1 channel. The full 3:1 channel is then split into 2 subslots and the best
quality channel is assigned to the call.
Dynamic Channel Allocation Procedure Frame Size (Slots)

Parameter Name:
Occurrence:
Definition:
Range of Values:
Default Value:
Comments:
Dynamic Channel Allocation Procedure Frame Size (Slots)

The frame size of the Dynamic Channel Allocation Procedure used to manage
channels.
A DCAP frame is a multiple of 24 slots where 1 slot = 15 ms. The valid DCAP
frame sizes are 24, 48, 72, and 96 slots. When sent over the air, a value of 1, 2, 3,
or 4 is sent to the MS, which it then multiplies by 24 to get the number of slots in
the DCAP frame.
24, 48, 72, or 96 (slots)
24
It is recommended that this parameter be left at the default setting on 24. Changes
will impact multiple Radio Link Control procedures as well as dynamic channel
allocation.
Primary Control Channel Interleave: OLL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments
NOTE:
June 19, 2006
Primary control channel interleave

Once per cell
This parameter defines how far apart the PCCH slots are spaced on the BR thats
designated as the control channel. Usually the first BR (BR #1, or the bottom BR in
the cabinet) is so assigned.
1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 14, 16, 18, 20, 24.
None
6
None
Currently only the following PCCH settings are supported by the SU:
12:1 PCCH
2:1 BCCH Interleave 1 2 BRs
6:1 PCCH
4:1 BCCH Interleave > 2 BRs
The product of BCCH Interleave and of primary control channel interleave must be
24. The value of primary control channel interleave is dependent on the number of
BRs in the cell.
The Primary Control Channel Offset is a time slot is uniquely

identified by two parameters, its interleave, which is the spacing
between sequential slots of the channel, and its offset, which is the
starting slot within the signaling frame. Thus to uniquely identify a
PCCH, both the interleave and offset must be given. The offset is
always in the range of 0 to one less than the interleave value of the
channel. Currently, 0 is the only valid value.
Page 44 of 69
WP2003-007-2
BCCH Interleave: OL
Parameter Name:
Occurrence:
Definition:
Range of Values:
Default Value:
Units:
Related
Parameters:
BCCH Interleave
Once per cell
This parameter defines how far apart the BCCH slots are spaced in the PCCH. A
BCCH interleave of 2 means that every second PCCH slot is a BCCH. A BCCH
interleave of 6 means that every sixth PCCH slot is a BCCH. The product of
BCCH Interleave and of primary control channel interleave must be 24. Thus, the
following table 2.3.1 is defined.
The value of BCCH Interleave is dependent upon that of primary control channel
interleave, which depends on the number of BRs. See the following table 2.3.2.
2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 14, 16, 18, 20. 24
4
None
Primary control channel interleave
Number of Secondary Control Channel: OLL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Comments:
Number of Secondary Control Channel: OLL

Once per cell
Specifies the number of SCCHs for this cell.
0 thru 4
1
0
This parameter should be set less than the number of BRs in the cell.
Secondary Control Channel Interleave: OLL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Default Value:
Comments:
Secondary Control Channel Interleave (SCCH)

Once per cell
Specifies the channel interleave of the SCCH.
6 or 12
6
It is not necessary set this to the same value as the PCCH Interleave, however the
limitations of a 12:1 SCCH may outweigh any desire to reduce the impact to the
TCH server pool.
Maximum Interleave
This parameter was introduced in the SR9.2 / SR9.5 release.
Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Comments:
June 19, 2006
Maximum Interleave
Once per ACG/EBTS
This parameter is used, by the ACG, to determine the largest allowed interleave.
AllowI6_I12 or AllowI3_I6_I12
AllowI3_I 6_I12
Caution: Setting this parameter to allow_I6_I12 prohibits 3:1 interconnect traffic
from the site.
Page 45 of 69
WP2003-007-2
Telephone Queuing Timer: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments
Telephone queuing timer

Once per ACG
This parameter specifies the length of time a queued interconnect call stays in the
busy queue. When this time expires, the call leaves the queue and the initiating MS
is returned to a Phone Ready state.
Setting this parameter to 0 disables telephone queuing.
0 ... 10000
1 (Odd for a 12/2 PCCH interleave, even for a 6/4 interleave)
10000
msec
While an MS is in queue, its assigned a DCCH and holds it for the duration of
the timer or until channel assignment, whichever is first. . Thus, the DCCH will be
quickly saturated if all the RF timeslots are in use and the dynamic channel
assignment algorithm cannot increase the number of DCCHs. Keep in mind that
interconnect location area updates, registrations, and SMS use the DCCH. If the
DCCH is reserved for an interconnect call, these other transactions cant take place.
At sites with just 1 DCCH (a 1or 2 BR site with a 12:1 PCCH interleave for
example), interconnect location area updates, registrations, and SMS will be
blocked for this length of time when an interconnect call is in queue.
The purpose of this timer is to give an interconnect service request a chance to
compete for an RF timeslot with dispatch service requests. Dispatch traffic is
typically characterized by short, rapid fire, transmissions. Interconnect is
characterized by longer, less bursty transmissions. Because of this, dispatch
channel requests will tend to get serviced more than interconnect (simply because
there are more of them). Allowing an interconnect service request to stay in queue
for a short time increases its success rate when competing for channel resources
against dispatch traffic.
Should DCCH blocking occur on busy sites, this timer may be lowered. However,
it is first recommended to optimize the minimum number of DCCH per cell.
Busy Queue Max Length

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Comments:
Busy Queue Max Length

Once per Cell
The number of subscribers allowed to be held in queue.
10 thru 255
1
35
A value of zero indicates that there will be no queuing on either dispatch or
interconnect calls.
Prior to SR9.2 this parameter was applied on a site basis. Please refer to iDEN
update iden_g_ebts_003 for details.
June 19, 2006
Page 46 of 69
WP2003-007-2
Optimal Number of BRs For a Given Cell

This parameter has been removed in SR10.5, however it is listed here for markets that have yet
to upgrade to this system release.
Parameter Name:
Occurrence:
Definition:
Example:
Optimal Num. of BRs For a Given Cell

Once per cell
This parameter specifies how many BRs should be in the cell. If the actual number
of BRs is different from Optimal Num. of BRs for a Given Cell channel scaling
occurs and the minimum and preferred settings are adjusted accordingly.
A site has 10 BRs, 5 of which are out of service.
Before Scaling:
Optimal Num. of BRs For a Given Cell
Minimum number of DCCH per cell =
Min. Num. of I-6 TCH Per Cell
=
=
Range of Values:
Step Size:
Default Value:
Comments
=10
4
0
4
After Scaling:
Optimal Num. of BRs For a Given Cell =10
Minimum number of DCCH per cell = 2
= 0
= 2
1 ... 10
1
5
This parameter has a default value, which may not be appropriate for the site
configuration being datafilled. It is important to review this parameter to ensure the
proper setting
Channel Minimums
This set of DCA parameters are used to reserve a specific number of 12:1, 6:1 or 3:1
interleaves to maintain a desired Grade of Service. These parameters should be adjusted based
on traffic load. Please refer to iDEN white paper WP2001-020 for more details on optimizing
these parameters.
June 19, 2006
Page 47 of 69
WP2003-007-2
Minimum Number of DCCH per cell: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
Minimum number of DCCH per cell

Once per cell
This parameter defines the minimum number of Dedicated Control Channels for
the given cell. The DCCH (Dedicated Control Channel) is used for interconnect
call set up, registrations; interconnect location area updates, and SMS (Short
Message Service) transmissions. Renewal (a dispatch location area update) does
not use the DCCH.
0 ... 119
1
2
None
If this parameter is set to a value greater than 30% of the total pool of timeslots,
the ACG will send a warning message saying this is inadvisable. This is not an
error, and the ACG will still operate, but the range of the dynamic assignment
algorithm will be reduced.
To handle the expected traffic loads, a certain number of DCCHs are required or
calls will be blocked. The number of DCCHs is dynamically assigned based on
traffic loading at the ACG. This parameter specifies a minimum number of
DCCHs that the ACG will not drop below. Each of the six timeslots on an RF
channel must be assigned one of four functions. A timeslot can be a PCCH slot
(Primary Control Channel), a DCCH slot (Dedicated Control Channel), an I-6
TCH slot (Traffic Channel), or an I-3 TCH slot (interconnect only).
Minimum number of DCCH per cell must be less than or equal to DCCH
preferred number per cell. The value of minimum number of DCCH per cell is
dependent upon the PCCH interleave and the number of BRs in the cell. Thus if
PCCH Interleave is changed, This parameter might also require changing.
Because interconnect location area updates, and registrations are performed on the
DCCH, those cells along interconnect location area boundaries will have higher
DCCH loading than other cells. Be aware of this and boost minimum number of
DCCH per cell when DCCH blocking begins to appear
The following tables present the basic DCCH requirements for different PCCH interleaves and
BR stacks:
PCCH Interleave
12
6
Number of BRs
1-2
>2
June 19, 2006

Odd number: 1, 3, 5, 7, ...
Even number: 2, 4, 6, 8, ...
1
2
Page 48 of 69
WP2003-007-2
Minimum Number of I-6 Traffic Channels: OL

Parameter Name:
Occurrence:
Definition:
Note:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
Min. num of I-6 traffic channels (formerly known as Minimum Number of Traffic
Channels)
Once per cell
Defines the minimum number of interleave 6 traffic channels (TCH) for the given
cell.
If this parameter is set to a value greater than 30% of the total pool of timeslots, the
ACG will send a warning message saying this is inadvisable. This is not an error,
and the ACG will still operate, but the range of the dynamic assignment algorithm
will be reduced.
0 ...119
1
0
None
An I-6 TCH can carry either dispatch or I-6 interconnect traffic. Each of the six
timeslots on an RF channel must be assigned one of four functions. A timeslot can
be a PCCH slot (Primary Control Channel), a DCCH slot (Dedicated Control
Channel), an I-6 TCH slot (Traffic Channel), or an I-3 TCH slot (interconnect
only). Out of the total pool of RF timeslots (number of BRs x 6), some are set
aside for the PCCH (primary control channel interleave), some are set aside for I-3
traffic channels (Num. Preferred I-3 TCH Per Cell), and the remaining are
dynamically assigned, depending on need, to be either DCCH or I-6 TCH slots.
The ACG will always keep min num of I-6 traffic channels timeslots as TCH. Min
num of I-6 traffic channels must be less than or equal to preferred num. of I-6 TCH
/ Cell.
Minimum Number of I-3 TCH Per Cell: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Comments:

Once per cell
Defines the minimum number of Interleave three traffic channels for the given cell.
0 ... 59
1
0
It is strongly recommended that this parameter be >0. Initially set to the same
value as the number of carriers equipped in the cell.
Having this parameter at 0 will tend to cause handover resource blocking on
neighbor cells, which tends to decrease call quality and increase the number of
LOTs. .
June 19, 2006
Page 49 of 69
WP2003-007-2
Channel Holdbacks
Added in SR 5.0 to control the dynamic assignment of traffic channel types. Holdback queues
are used to tell the EBTS to take channels out of the PCH for other services before they are
actually needed. This helps to prevent the non-PD services from queuing as their demand
grows by making the channels available before they are actually needed.
Holdback queues are merely equivalent or potential channels. Channels used to satisfy one
holdback queue can be used to satisfy another holdback queue if the channels are the proper
offset to be joined and they must be split or joined such that cell minimum values will not be
violated in the split or join.
Recommended Holdback Settings For Sites With One BR:
Definition
3:1 Holdback
6:1 Holdback
12:1 Holdback
Value
0
0
1
Recommended Holdback settings For Sites With More Than One BR:
To Favor 6:1
3:1 Holdback
6:1 Holdback
12:1 holdback
Total # 6:1 Held Back
Most Suggested - - - - > Least Suggested

0
0
0
0
0
1
2
3
4
5
2
8
12
12
12
1
2
3
4
5
To Favor 3:1
3:1 Holdback
6:1 Holdback
12:1 holdback
Total # 3:1 Held Back
Most Suggested - - - - > Least Suggested

1
1
2
3
3
2
0
4
0
6
4
4
8
8
12
1
1
2
2
3
0
6
12
6
Holdback I12 DCCH: OL

Parameter Name:
Occurrence:
Definition:
Recommendation:
Range of Values:
Step Size:
Default Value:
June 19, 2006
Holdback I12 DCCH

Holdback I12 TCH represents the equivalent number of I12 TCH logical channels
to always attempt to maintain as available.
Recommended Holdback Settings For Site With One BR:
3:1 Holdback = 0
6:1 Holdback= 0
12:1 Holdback= 1
Recommended Holdback settings For Site With More Than One BR..
0...12
1
0
Page 50 of 69
WP2003-007-2
Holdback I6 TCH: OL
Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Holdback I6 TCH
Once per cell
Holdback I6 TCH represents the equivalent number of I6 TCH logical channels to
always attempt to maintain as available
0...6
1
1
None
Holdback I3 TCH: OL
Parameter Name:
Occurrence:
Definition:
Holdback I3 TCH
Once per cell
Holdback I3 TCH represents the equivalent number of I3 TCH logical channels to
always attempt to maintain as available.
Range of Values:
Step Size:
Default Value:
Units:
0...3
1
0
None
Channel Preferred
The Preferred set of DCA parameters were made obsolete in SR9.2 but the parameter remained
in AIRGEN, where they were recommended to be set the same as the minimum parameter for
the given interleave. With SR10.5 these parameter have been removed from AIRGEN.
Preferred Number DCCH per Cell

This parameter has been removed in SR10.5.
Parameter Name:
Occurrence:
Definition:
Step Size:
Default Value:
Units:
Comments
June 19, 2006
Num. Preferred 12:1 (DCCH) Per Cell

Once per cell
Obsolete
For pre SR9.2 / SR9.5 systems this parameter was used to set the number of 12:1
channels the ACG tried to maintain.
1
6
None
Post SR9.2/SR9.5, this parameter should be set to the same value as the minimum
Page 51 of 69
WP2003-007-2
Preferred Number of I-6 TCHs per Cell

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments
Preferred num. of I-6 TCH / Cell

Once per cell
Obsolete
For pre SR9.2 / SR9.5 systems this parameter was used to set the number of I6
0 ... 59
1
2
None
number of I6 TCH
Preferred Number I-3 TCH per Cell

Parameter Name:
Occurrence:
Definition:
Step Size:
Default Value:
Units:
Comments
Num. Preferred I-3 TCH Per Cell

Once per cell
Obsolete
For pre SR9.2 / SR9.5 systems this parameter was used to set the number of I3
1
6
None
Number Of Interconnect Paging Sub-channels: OL

Parameter Name:
Occurrence:
Definition:
Note:
Range of Values:
Step Size:
Default Value:
Units:
June 19, 2006
Number of paging Sub-channels

Once per cell
The number of distinct paging Sub-channels on each common control channel.
The Primary Control Channel is comprised of two sub-control channels. The
Broadcast Control Channel (BCCH) broadcasts data of a general nature describing
the characteristics of the cell and system. The Common Control Channel (CCCH)
transmits data targeted for specific MS such as Registration, Location updates,
Interconnect call set-up, and SMS data.
The number of CCCH slots is dependent upon the values of primary control
channel interleave and BCCH interleave. The value of this parameter must be
reviewed each time a BR is added to the cell. This parameter is broadcast on the
BCCH of the cell.
1 ... 15
1
9
None
Page 52 of 69
WP2003-007-2
The following tables highlight the recommended number of paging sub-channels based on the
PCCH Interleave and/or the BR stack per cell.
PCCH Interleave
12
6
Number of BRs
1
2
3
4
5
6
7
8
9
10
Number of Paging Sub-Channels

3
9
Number of Paging Sub-Channels
3
3
9
9
9
9
9
9
9
9
Cell Access / Priority

Bar from Cell
Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Comments:
Bar from Cell

Indicates whether subscribers may camp on the cell. The value 1 indicates the
cell is barred (i.e., camping on the cell is forbidden). This is one of the cell
availability parameters sent on the BCCH.
0 or 1
0
A setting of 1 may be desired during initial testing of a new EBTS.
Access Class
Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Comments:
June 19, 2006
Access Class
This parameter contains the entire list of MS Access Classes (Class 0 to Class 15),
which may or may not be allowed to access the cell. It should be noted that Access
Class 10 does not exist as a normal class; it is used to restrict emergency calls.
0 thru 65,535
0
Page 53 of 69
WP2003-007-2
Interconnect Call Class

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments
Interconnect call class

Once per cell
This parameter defines the call class value field for all interconnect calls within the
cell.
The default value of 6 puts queued interconnect calls at the same priority as
queued dispatch calls. If dispatch calls need higher priority, set this parameter to a
higher value. Likewise, if interconnect is to be prioritized, set this parameter to a
lower value.
Within a call class, queued calls are also assigned a priority value. Thus two calls
of class 6 could be assigned different priorities so one will be processed before
the other. See interconnect priority value. Changing the priority will accomplish the
same goal as changing interconnect call class but with finer detail. Calls are
queued based on five categories. Interconnect call class is the second of these
categories.
1 ... 15
1
6
None
Priority
Category
1) Emergency
Highest importance
2) Class
3) Priority
4) Recent User
5) First in/First out (FIFO) Lowest Importance
Interconnect Priority Value

Parameter Name:
Occurrence:
Definition:
Interconnect priority value

Once per cell
Defines the priority value field for interconnect call/request priority
When calls of the same class are queued within a cell, they are assigned a priority
value to determine the order in which they are served. This parameter, assigns the
priority value for all interconnect calls placed at a cell. 0 is highest priority, 15
is lowest. Both dispatch talkgroup calls and dispatch private calls are assigned
priority values base upon a setting in the DAP HLR, determined at the time the
talkgroup/unit is entered into the DAP.
Range of Values:
Step Size:
Default Value:
Units:
June 19, 2006
Calls are queued based on five categories. Interconnect priority value is the third of
these categories.
0 ... 15
1
6
None
Page 54 of 69
WP2003-007-2
Comments:
Category
Priority
1) Emergency
Highest importance
2) Class
3) Priority
4) Recent User
5) First in/First out (FIFO) Lowest Importance

By changing interconnect priority value, queued interconnect calls can be given
priority over dispatch calls, or visa versa within the same class.
Queued talkgroup calls will be processed before interconnect calls which will be
processed before private calls.
Reference iDEN document iden_g_ebts_003 for information on how this parameter
is applied pre and post SR9.2.
Public Access
Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Related
Parameters:
Comments:
June 19, 2006
Public Access
Indicates if a cell is available for public access. Setting this to False indicates
the cell is part of a private network (not public); MSs of other Mobile Country
Codes, and Network Domain Codes will not lock onto the cell.
True or False
False
Page 55 of 69
WP2003-007-2
Multiple Packet Data Channels

This section presents the Multiple Packet (Data) Channel (MPCH) feature and associated
parameters. To aid the transition to the MPCH parameters, the following table may be used to
understand the relationship to pre-SR9.8 parameters:
Pre-SR9.8 minPCH
0
12
6
3
1
SR9.8 TPMS
0
2
2
4
12
Auto-Management Flag (AMF)

OFF
OFF
OFF
OFF
OFF
Cell PCH Auto Management: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Default Value:
Comments:
Cell PCH Auto Management

Once per Cell
This parameter indicates whether the number of packet channels in a cell is
statically set or dynamically adjusted by the EBTS. Setting the value to Yes or No
overrides the setting of the Packet Data Region.
Yes, No, or Same As Packet Data Region
Same As Packet Data Region
AMF is OFF:
The number of PCHs in the cell remains equal to the number of PCHs
derived from the TPMS
If the TPMS is less than or equal to twelve, then there will be a single
PCH in the cell. The behavior will be the same as pre-9.8.
If the TPMS is greater than twelve, then the individual PCH min sizes will
be equal to twelve regardless of traffic conditions
AMF is ON:
The ACG will automatically manage the number of PCHs in the cell and
the individual PCH minimum sizes
The current number of PCHs in the cell depends on the TPMS, number of
Resource Allocation Groups (RAGs), and voice traffic
o
June 19, 2006
RAGs are dynamically redistributed as packet channels are added

or removed
When voice traffic decreases for a certain amount of time, additional

PCHs can be added to the cell
When voice traffic increases for a certain amount of time, PCHs may be
removed. However, the number of PCHs and current TPMS will not be
smaller then the configured values under normal conditions
Page 56 of 69
WP2003-007-2
Maximum Number of Packet Channels: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Maximum Number of Packet Channels

Once per cell
This parameter indicates the maximum number of PCHs allowed for a cell.
Step Size:
Default Value:
Comments:
1
None
None
0 (No Packet Data Service)
1, 2, 3 (DEFAULT_3_SECTOR) or (DEFAULT_2_SECTOR)
5, 6, 7, 8, 9 (DEFAULT_OMNI_SECTOR)
Limits the number of PCH in the cell
The summation of the MaxPCHs for all cells in the site shall not exceed nine.
These may be split in any fashion.
If MaxPCHs is set to zero, then packet data service is not available in the cell
Minimum Total Packet Channel Bandwidth: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Comments:
Minimum Total Packet Channel Bandwidth (TPMS)

Once per cell
This parameter indicates the minimum value of the total bandwidth of all packet
channels in a cell. This parameter, known as TPMS, is specified in terms of
number of interleave 12:1 channels.
0 thru 108
1
0
Every time the number of PCHs in the cell changes to a value different than the
number initially configured, the ACG will calculate a new PCH Min Size value
based on the TPMS and the new number of the PCHs in the cell.
The MPCH feature allows up to 9 PCH per ACG, which is represented by the
maximum parameter value of 108 (12 * 9).
The minimum value of the total combined size of the bandwidth of all packet channels
in the cell. This value is guaranteed to be available for packet data service under
normal conditions. If minPCH = 1, then TPMS >=12.
The value is dependent on other ACG configurations parameters and the

configurations of the MDGs
The TPMS is distributed evenly across each individual packet channel in the
cell.
The valid values of totalPCHMinSize and the Minimum PCH configuration for Auto
Management ON are shown in the table below:
June 19, 2006
Page 57 of 69
WP2003-007-2
Total PCH Min Size (TPMS)

0
2
4
8
16
24
32
40
48
56
64
72
Number of PCHs
1
1
1
1
2
3
4
5
6
7
8
9
PCH Min Size (per PCH)

0
2 (2 x 12:1)
4 (4 x 12:1)
8 (8 x 12:1)
8 (8 x 12:1)
8 (8 x 12:1)
8 (8 x 12:1)
8 (8 x 12:1)
8 (8 x 12:1)
8 (8 x 12:1)
8 (8 x 12:1)
8 (8 x 12:1)
EBTS / RF PLANNING
This section presents parameters related to EBTS and RF planning. The following parameters,
relating to power control are discussed within the Radio Link Control section of this paper.
Transmit Power/Carrier: OL; OLL
Transmit Power (Pto): OL
Cell Maximum Transmit Power of MS: OL
Receiver/Transmitter Gain: OL
Power Control Constant: OL
Hardware Platform: OLL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Comments:
Hardware Platform: OLL

Once per BR
Indicates whether the BR is a single carrier BR, or a Quad (1, 2, 3 or 4 carrier) BR
Singer Carrier or Quad
Note that a Quad BR can have a single frequency. In this case, the hardware
platform is set to Quad and not to Single. Setting this parameter to Single indicates
that the BR hardware is only capable of accepting just 1 frequency.
Primary Control Channel: OLL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Default Value:
Comments:
June 19, 2006
Primary Control Channel: OLL

Once per Carrier
Indicates if the carrier is the PCCH. Any of the 4 carriers in a Quad BR can be
designated as a PCCH. One and only one carrier can be a PCCH.
Yes or No
No
The control channel is typically the first BR in the cell, which is the lowest
mounted BR in the cabinet. The frequency assigned to the PCCH must be a
suitable bandmap channel.
Page 58 of 69
WP2003-007-2
Broadcast Channel Carrier Number: OLL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Default Value:
Comments:
Broadcast Channel Carrier Number: OLL

Once per Cell
The carrier number of the primary control channel.
800 MHz Band: 1 thru 1,199
900 MHz Band: 1 thru 398
1.5 GHz Band: 1 thru 479
1
This parameter is the carrier number of the BR that is designated as the control
channel and is derived from transmit frequency by the following equation:
Carrier number of broadcast channel = carrier number (1st BR)
Transmit frequency in MHz (1st BR) - 851) / 0.0125
The control channel is typically the first BR in the cell, which is the lowest
mounted BR in the cabinet. This parameter must agree with the carrier number of
the neighbor cell in each cell that lists the cell being datafilled as a neighbor. It
must always be the same as carrier number that is in the BR designated as the
control channel.
Number Of Carriers: OL; OLL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Comments:
No. Of Carriers: OL; OLL

Once per Quad BR
If Hardware Platform is set to Quad, this parameter indicates how many carriers
are programmed.
1, 2, 3, or 4
1
1
This parameter is not valid for single BRs.
Transmit frequency, OL; OLL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments
Transmit frequency
Once per BR per cell
This parameter defines the transmit frequency of the BR in MHz.
851.0125 ... 865.9875
0.0125
MHz
Frequency assignments must follow accepted RF design fundamentals. Note that
the receive frequency is determined from this parameter, according to the operating
bands Tx/Rx Offset (duplex spacing).
Please refer to Figure 13, which is an extract from Appendix B: Frequency
Mapping of the iDEN Naming Specification manual (68P81129E11). This manual
should be referenced for further information on the relationship of frequencies to
carrier numbers.
June 19, 2006
Page 59 of 69
WP2003-007-2
Figure 13: Frequency Band Specifier
Color Code: OL, OLL

Parameter Name:
Occurrence:
Definition:
Color code
Once per cell
This parameter specifies the color code of the Cell. The color code is broadcast on
the control channel and is used by the MS to ensure that the proper cell is being
received. There are 16 possible color codes.
If a cell has multiple neighbors of the same frequency, then the neighbors must be
given different color codes to permit the MS to identify the proper neighbor.
Range of Values:
Step Size:
Default Value:
Comments:
June 19, 2006
This parameter must be the same as color code of neighbor cell in adjacent cells,
which list the cell being datafilled as a neighbor.
0 ... 15
1
0
Refer to the iDEN RF Planning Guide for additional information assigning color
codes.
Assigning color codes to the same frequency (co-channel co-dcc) must be avoided
whenever two sites may see a MS initiating a dispatch call. This can cause two
simultaneous requests for channels from the DAP. A Network Trouble message
at the MS is the usual result of this conflict. Color codes can be grouped and
assigned to cell clusters in large-scale reuse patterns similar to the way frequencies
can be assigned.
Page 60 of 69
WP2003-007-2
Color Code Extension:

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Comments:
Color Code Extension

Once per cell
Extends the color code on inbound split 3:1 and 12:1 dispatch traffic channels.
0 ... 5
1
0
Color Code Extension should be set differently in sites that use same color code
and frequency to avoid audio crosstalk and other issues.
Combiner Type
Parameter Name:
Occurrence:
Definition:
Range of Values:
Default Value:
Comments:
Combiner Type
Once per Cell
This parameter specifies the type of transmit combiner deployed and determines
the PCCH redundancy operation.
Hybrid (1)
Cavity (2)
Hybrid (1)
A hybrid combiner allows flexibility in the assignment of frequencies to a specific
base radio. However, this flexibility comes at a price; the hybrid combiner adds
loss to the signal path.
The cavity combiner introduces less loss than the hybrid combiner. However, it
removes the flexibility in frequency assignment.
PCCH Redundancy
If a redundant PCCH BR is specified, and the primary PCCH BR fails, a new PCCH BR is
selected based upon the setting of this combiner type parameter and configured redundant BR.
The redundant PCCH BR must be of the same type as the PCCH BR, i.e. a single BR cannot
PCCH rollover to a Quad BR.
If the combiner type is HYBRID, then the ACG considers the configured redundant PCCH BR
as preferred. This means that if this BR is not available the ACG can pick any other BR in
the cell. This decision is based upon the BR recovery time thus for a cell with mixed BR
types, GEN2 BRs will tend to be selected over legacy units. This functionality is due to that
fact that, in a hybrid-combined system, there are no frequency sensitive components, so any of
the available BRs can be reprogrammed to the PCCH frequency and power.
If combiner type is CAVITY, the ACG understands that the only choice is the BR indicated by
redundant BR. This is due to hardware limitations of standard cavity-combined systems. If
the redundant BR is not available, then the cell will be taken off the air because no BRs are
available to carry the control channel. The ACG will also activate the PCCH redundancy relay
to switch the proper cavity over to the new, redundant, BR.
If a cavity combined EBTS is inappropriately programmed as HYBRID, this relay will not be
activated. The anticipated result is reduced power out of the combiner from a wrongly tuned
cavity and increased heating of the combiner isolator load. Although the cavity input will have
high VSWR, the isolator will usually prevent the BR from knowing this.
June 19, 2006
Page 61 of 69
WP2003-007-2
If a hybrid combined EBTS is inappropriately programmed as having cavity combiners, the

selection of a redundant BR is severely limited. Instead of being able to select from any of the
functioning BRs the specified redundant BR is the only that can be picked.
In the case a site being equipped with mixed combiner types, such as auto-tune cavity
combiners (ATC) being used on the same cell as hybrid combiners, care must be taken to
ensure correct site operation upon PCCH rollover. An initial suggestion is for the combiner
type to be set to CAVITY. This ensures that the redundant PCCH BR is always as defined and
can be configured appropriately. As previously noted, the probability of the redundant BR
also failing is very low, however in this event the cell will go out of service until the PCCH
BR can be restored. If the combiner type is set to HYBRID then the PCCH BR must be
configured with sufficient frequency spacing, i.e. 250kHz, from the BRs connected through the
ATC. Consideration to the path balance must be made if the PCCH rolls over from a hybrid to
a cavity combined BR due to insertion loss differences.
IMPORTANT:
Motorola neither recommends or supports mixed

combiner types on a single site or cell. The above
guidance has been provided to assist customers
deploying such configurations.
Cavity Switch Type

Parameter Name:
Occurrence:
Definition:
Range of Values:
Comments:
Cavity Switch Type

Once per cell
The type of switch used in the EBTS for its cavity combiner.
Transfer or DPDT
If combiner type is CAVITY, the ACG will also activate the PCCH redundancy
relay to switch the proper cavity over to the defined redundant, BR.
If a cavity combined EBTS is inappropriately programmed as HYBRID, this relay
wont ever be activated. The anticipated result is reduced power out of the
combiner from a wrongly tuned cavity and increased heating of the combiner
isolator load. Although the cavity input will have high VSWR, the isolator will
usually prevent the BR from knowing this.
Redundant BR
Parameter Name:
Occurrence:
Definition:
Range of Values:
Default Value:
June 19, 2006
Redundant BR
Once per cell
Indicates that the BR is a redundant BR. There can be 0 or 1 redundant BRs in a
cell. The redundant BR must have the same number of carriers as the primary
PCCH BR.
Yes or No
No
Page 62 of 69
WP2003-007-2
Color Code of Neighbor Cell

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Comments
Color code of neighbor cell

Once per neighbor.
This parameter specifies the color code of a neighbor cell. It must be the same
value as color code specified in the neighbor. There are 16 valid color codes
0 ... 15
1
0
Special conditions may influence the exclusion of a close neighbor or the inclusion
of a far neighbor. Some close neighbors may be excluded if the system operator
does not want to direct additional traffic towards a new, off-line or otherwise
overloaded cell. A far neighbor may be included if it has a relatively large
coverage area (a high site providing coverage over one or more low sites) or has
excess capacity and covers the area reliably
Carrier Number of Neighbor Cell

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Related
Parameters::
Comments:
June 19, 2006
Carrier number of neighbor cell

Once per neighbor.
This parameter is the carrier number of broadcast channel for each neighbor listed
in the neighbor list of the cell being datafilled. If the broadcast channel of a
neighbor is changed, then the corresponding entry, carrier number of broadcast
channel must be changed in each and every neighbor of the cell that was changed.
1 ... 1199
1
None
Carrier number of broadcast channel
Transmit frequency
Receiver frequency
Special conditions may influence the exclusion of a close neighbor or the inclusion
of a far neighbor. Some close neighbors may be excluded if the system operator
does not want to direct additional traffic towards a new, off-line or overloaded cell.
A far neighbor may be included if it has a relatively large coverage area (a high site
providing coverage over one or more low sites) or has excess capacity and covers
the area reliably.
Page 63 of 69
WP2003-007-2
Slot Timing Error Threshold Mode: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
Slot Timing Error Threshold Mode: OL

Once per cell
This parameter is part of the Co-Channel Enahancement feature and determines the
mode for setting the slot timing error threshold.
0 thru 250
10.5
250
Microseconds
The slot timing error (STE) information is used to dynamically map out the
surrounding cells to set a threshold roughly at the distance to the first tier of cochannel MS radios. The further an MS is away from the site, the greater the timing
delay will typically be on the inbound slot. Inbound transmissions that have
excessive timing error (STE larger than STE Threshold) will be ignored by EBTS.
This minimizes blocked dispatch calls and audio crosstalk associated with the use
of co-channel, co-color code cells.
Automated mode is recommended for standard deployments.
A 0 indicates automated mode where the threshold is determined by the EBTS.
Any value greater than zero forces a manual mode, which overrides the automated
mode.
Using a step size of 10.5 microseconds, this is equivalent to 0.976 miles or 1.56 km
per step. A setting of 250 is equivalent to 0.976 x 250 = 244 miles or 392 km.
IMPORTANT:
Due to timing jitter, of existing MS radios, the STE

filtering approach should only be used when cochannel, co-color-code sites are separated by at
least 35 miles.
RF Congestion Relief
This feature, introduced in SR9.8, is designed to improve the Grade of Service for congested
cell by forcing FNE-Initiated handovers, for a specific number of interconnect calls in
progress, to allow call to exit the busy queue.
Capacity gains up to 30% have been simulated, however this assumed cells have overlapping
coverage and neighbor cells have sufficient instantaneous capacity to handle incoming RF
Congestion Relief handovers.
Please also refer the SR9.8 EBTS Release Notes and the SETS Formulas for Traffic Analysis
document for further information. These are available on the iDEN customer documentation
website (GTSS Online / Extranet).
June 19, 2006
Page 64 of 69
WP2003-007-2
Congestion Relief Trigger Threshold: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
Congestion Relief Trigger Threshold: OL

Congestion Relief is triggered in a cell if the number of available RF resources falls
below this threshold. Congestion Relief is disabled when this parameter is set to
zero.
0 thru 5
1
1
None
Increasing this value will force congestion relief handovers to be trigger earlier than
may be desired. The effect of this will be an increase in HO attempts and
subsequent failure/blocking.
It is recommended that the crThreshold be limited by the i3holdback size, as
follows:
1. PCH Auto-management = 1 (ON)
a. CrThreshold < i3holdback size.
Limiting the crThreshold by the i3holdback simplifies the interaction
between congestion relief and the multiple packet channel feature. By
limiting the crThreshold, premature congestion relief triggering is limited
by allowing the MPCH feature to remove packet channel carriers for
holdback violations (as designed)
2. PCH Auto-management = 2 (OFF)
a. TotalPCHMinSize < 12 then crThreshold < i3holdback size
Congestion relief should not be triggered before bandwidth can be removed
from the packet channel to serve voice traffic. Limiting the CrThreshold by
the I3 holdback limits the triggering of congestion relief by removing
bandwidth from the packet channel first.
b. TotalPCHMinSize >= 12 then no restrictions
In this case, holdbacks are not used by the ACG so there is no limit required
for the CrThreshold.
June 19, 2006
Page 65 of 69
WP2003-007-2
ProThreshold
Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Comments:
ProThreshold: OL
Once per Neighbor Cell
This parameter defines the minimum acceptable outbound RSSI (Pro), reported in a
Measurement Report, for a neighbor cell.
-120 thru -30
1
-110
dBm
The ProThreshold is applied to Measurement Reports for InterCell handover. If a
neighbor cell report in the MR is below its defined ProThreshold it will be stripped
from the MR and thus not considered as a viable handover candidate.
Setting this parameter too high will cause handovers to be rejected and potentially
degraded quality and cause dropped calls.
Congestion Relief Measurement Inquire Retry Timer: OL

Parameter Name:
Occurrence:
Definition:
Range of Values:
Step Size:
Default Value:
Units:
Related
Parameters:
Comments:
June 19, 2006
Congestion Relief Measurement Inquire Retry Timer: OL

Time, in centisec, that must elapse before a congestion relief handover is re-tried
for an existing call.
0 thru 3,000 centisecs
1,000 centisecs
Centisec (0.01 seconds)
Setting this parameter lower will increase the volume of congestion relief handover
attempts.
Page 66 of 69
WP2003-007-2
REFERENCES
The following documents were referenced during the creation of this white paper.
[1] WP2003-011:
RF Statistics and Solutions: RF Link Optimization Guide
[2] WP2003-010:
Link Budgets: RF Planning Guide
[3] 68P81127E91
Radio Link Control
[4] 68P81131E99: iDEN OMC-R System Configuration Reference Manual (Parameters)

[5] iden_g_ebts_003:Enhanced Call Processing for SR9.2 to SR9.5
[6] WP2002-026-1: Inbound Handover Threshold Optimization
[7] WP2001-020:
DCA Optimization
[8] WP2002-026:
Inbound Handover Threshold Optimization
IMPORTANT:
Some documents may not be currently available

under the names listed above.
Revision History
Version
Date
Author
Description
1.0
4/7/03
John Critchley
Original issue
1.1
08/04/03
John Critchley
Draft revision for

SR10.5
2.0
06/19/06
John Critchley
Periodic update
June 19, 2006
Page 67 of 69
WP2003-007-2
Contact Information
For assistance please contact your Motorola Regional Customer Network Resolution Center
(CNRC) at:
iDEN/Harmony Products:
US/Canada - +1-800-499-6477
International - +1-847-704-9800
World-wide Web
Additional information can be found at:
iDEN/Harmony:
https://mynetworksupport.motorola.com/
June 19, 2006
Page 68 of 69
WP2003-007-2
MOTOROLA and the Stylized M logo are registered in the U.S. Patent and Trademark Office. All other
product or service names are the property of their respective owners
Motorola, Inc. 2006.
June 19, 2006

Config RF Parameters

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Config RF Parameters

Uploaded by

Copyright:

Available Formats

CONFIGURABLE RF

iDEN Technical Publications White Paper

iDEN Technical Publications White Paper

CHANNEL DISCONNECT AND FAILURE ..................................................................................................41

iDEN Technical Publications White Paper

RF CONGESTION RELIEF .......................................................................................................................64

June 19, 2006

iDEN Technical Publications White Paper

SPECIFICATIONS SUBJECT TO CHANGE WITHOUT NOTICE

June 19, 2006

iDEN Technical Publications White Paper

RADIO LINK CONTROL

The acronyms SU and MS are used interchangeably to describe the

June 19, 2006

iDEN Technical Publications White Paper

Discontinuous Transmission (DTX) is also employed by the SU,

Transmit Power/Carrier: OL; OLL

Default Transmit Power Level

June 19, 2006

iDEN Technical Publications White Paper

Transmit Power (Pto): OL

Transmit Power (dBm): OL

Cell Maximum Transmit Power of MS: OL

Cell Maximum Transmit Power of MS

June 19, 2006

iDEN Technical Publications White Paper

Receiver/Transmitter Gain (dB): OL

Power Control Constant: OL

Power Control Constant (dBm): OL

June 19, 2006

iDEN Technical Publications White Paper

-128 to +127 dBm

Please refer to WP2003-010 for further comments on this parameter.

June 19, 2006

iDEN Technical Publications White Paper

FNE evaluates target

Figure 1: Handover Process Summary

June 19, 2006

iDEN Technical Publications White Paper

There are 3 types scenarios than may result, as follows:

IntraCell: Between BRs or slots on a BR within the same cell.

InterBSC: Between BRs on different cells on different BSCs.

The associated RF parameters are presented in the following sections.

Handover Class of Cell

Handover class of cell

Changing this parameter has a drastic effect on

June 19, 2006

iDEN Technical Publications White Paper

These rules are presented in the following logic diagram:

Downlink Serving SQE < OB Threshold

Figure 2: SU-Initiated Handover: Class 1 Logic Diagram

June 19, 2006

iDEN Technical Publications White Paper

These rules are presented in the following logic diagram:

Downlink Neighbor SQE >= Threshold + Hysteresis

Downlink Neighbor RSSI < Serving RSSI + Hysteresis

Downlink Neighbor SQE >= Serving SQE + OB Hysteresis

Figure 3: SU-Initiated Handover: Class 2 Logic Diagram

These conditions are presented in the following logic diagram:

Figure 4: SU-Initiated Handover: Class 3 Logic Diagram

June 19, 2006

iDEN Technical Publications White Paper

FNE Initiated Handovers

Downlink Neighbor SQE >= Serving SQE