Imer 2

Wireless Business Group
subject: CDMA 1xEV Translation Application Note #1 date: February 12, 2012
Timing, Delay, and Access Parameters
Version 20.0
Abstract
There are several CDMA 1xEV translation parameters that involve timing, delay, and access.
The values of these translation parameters must be set correctly for proper operation of a CDMA
1xEV system. The purpose of this translation application note is to explain the functions of these
important translation parameters, the relationship among them, and to provide their
recommended values.
Version History
Version Changes
1.0 Updated document for CDMA 1xEV Cell Release 1.0
5.0 Updated document for CDMA 1xEV Cell Release 22.01/22.02
-Updated Section 2.1 – Access Cycle Duration, Transmission Antenna Propagation Delay
-Updated Section 2.3 – Access Preamble Length, Access Capsule Max Length
-Updated Section 3.3.1 – Normal Paging Method
-Updated Section 2.1 – Transmission/Receive Antenna Propagation Delay, Open Loop Adjustment
-Updated Section 5 – Test Carrier
Alcatel-Lucent - Proprietary
This document contains proprietary information of
Alcatel-Lucent and is not to be disclosed or used
except in accordance with applicable agreements.
Copyright © 2012 Alcatel-Lucent

Unpublished and Not for Publication
All rights reserved
CDMA 1xEV RF Translation Application Note #1 Version 20.0
-Updated Section 7 – Multiple Carriers: Hashing and Traffic Load Balancing

-Updated Section 8 – Session Close feature
-Updated Section 2.1 – Transmission/Receive Antenna Propagation Delay
-Updated Section 5 – Test Carrier
-Updated Section 8 – Session Close feature
11.0 Updated document for CDMA 1xEV Cell Release 28.0 (RNC Release R28 SU1)
-Updated Section 2.1 – Access Cycle Duration, Open Loop Adjust
- Updated Section 2.3 – Access Capsule Max Length
- Updated Section 3.2.2 – Distance based Registration
- Updated Section 3.3.1 – Normal Paging method
-Update Sections 7.3,7.4, 7.5 – Traffic Channel Load Balancing Algorithm and Border Carrier
-Updated Section 2.1 – TxDelay / RxDelay per Sector-Carrier capability and increase in range of
TxDelay; new recommendation for Open Loop Power Adjust and Access Cycle Duration parameters
- Updated Section 2.3 – New recommendation for Access Capsule Max Length parameter
- Updated Section 3, 3.2.1, 3.3.1 – Default Best-Effort Paging, Subnet based Registration, Default
Best Effort Normal Paging method
-Updated Section 5 – New implementation of Test Carrier with RNC R29
-Update Sections 7.4, 7.5 – Traffic Channel Load Balancing Algorithm with QoS enabled; Traffic
Channel Load Balancing between Border and Non-Border carriers; Important Notes
Update Sections 8 – Session Close Feature
-Updated section 3.3 – Comment on Repage Timer (Minimum Time to wait for a Page or DoS
response)
-Update sections 7.4 and 7.5 – Comment on Load Differential translation parameter; Updated section
on Important Notes
-Update sections 8 – Comment on disabling Session Close Feature
-Updated Section 2.1 – Per Sector-Carrier view for TxDelay and RxDelay parameters
-Updated Section 7.5 – New Translation Parameter to control traffic load balancing between Border
and Non-Border Carriers
-Updated Section 2.1 – Tx/Rx delay parameters for BTS 9234 with RRH
-Updated Section 2.1 – Dynamic Open Loop Power Adjustment
-Updated Section 2.3 – Recommendation change for Access Preamble Length
-Updated Sections 7.2, 7.3, 7.4, 7.6 – RSSI Rise based traffic load balancing for Rev0 mobiles for
both Non-Border/Non-Border carriers and Non-Border/Border carriers
-Updated Section 2.1 – Tx/Rx delay parameters for BTS 9234, 9228, 9222 with RRH
-Updated Section 5 – Test Carrier feature and new translation parameter SID Override
-Updated Section 7.4 – Per Sector view of translation parameter RF Load Differential
-Updated Section 2.1 – Dynamic OpenLoopAdjust recommendation changed to Enable
-Updated Section 2.1 – New translation parameter for Dynamic OLA
-Updated Section 2.2 – Impact of Access Search Window size inequality violation
-Updated Section 7.4 – New translation parameter for RF Loading Differential at the sector level
Alcatel-Lucent – Proprietary 2
See notice on first page
-Updated Section 2.1 – Updated RxDelay for RRH (850 band class) in Table 1, added clarification
regarding OpenLoopAdjust parameter
-Updated Section 2.1 on OpenLoopAdjust parameter. Maximum correction applied to
OpenLoopAdjust increased from 15dB to 27dB
-Updated Section 7.0 on traffic load balancing. A new traffic load balancing algorithm introduced via
FID 8219.26 in R37 is documented in Translation Application Note #12
1 Introduction
There are several CDMA 1xEV translation parameters that impact timing, delay, and access. A
correct set of values of these translation parameters is required for the proper operation of a
system. The purpose of this document is to explain the functions of these translation parameters
and to provide their recommended values.
2 Access Channel
Access channel is used by an access terminal (AT) to initiate communication with the access
network (AN) or to respond to the AT directed message when AT does not have a traffic channel
assigned. The access channel consists of a pilot channel and a data channel. The information on
the access channel (Rev0 and Default Access Channel in RevA) is transmitted at a fixed rate of
9.6 kbps.
The reverse link of a CDMA 1xEV system, which uses the CDMA scheme, allows multiple users
to simultaneously share the same frequency band. The demodulator extracts the desired user’s
signal by matching the modulated user-specific PN code. To this end, the demodulator must
exactly match the path delay such that the PN code can be in phase with the transmitted
sequence. The demodulator needs to test many path delay hypotheses to find the best match of
the path delay. The search window (both in the base station and AT) specifies the range for the
path delay hypotheses.
Unlike 3G1x, there is no PN randomization in 1xEV. PN randomization increases the probability

that the base station will be able to separately demodulate transmissions from multiple mobile
stations in the same access channel slot, especially when many mobile stations are at a similar
range from the base station.
In general, there are three goals in optimizing the access translation parameters: minimize
interference to the existing traffic users, minimize delay perceived by the end user, and maximize
access success rate.
2.1 Basic Translation Parameters that Impact Access, Timing, and Delay
There are several access, timing, and delay related translation parameters that are fundamental to
the operation of a CDMA 1xEV system. Their definition and recommended values are included
below.
Sector size (sectorsize): The maximum range of a cell’s desired coverage. It accommodates the
maximum possible air propagation delay (one way). The recommended value is 10 miles.
Maximum number for an access probe sequence (maxprobesequence): Maximum allowable

number of access probe sequences for a single access attempt, either AT initiated or AN initiated.
The recommended value is 2.
Number of access probes (probenumstep): Maximum number of access probes an AT is

allowed to transmit in a single access probe sequence. The recommended value is 5.
Access cycle duration (accesscycleduration): It is the basic time unit of all access channel
activities. It indicates how often base station needs to start a new probe search and when mobile
can transmit a probe. In 3G1x, access probe must be transmitted at the access probe boundary
(equal to access channel slot boundary). In 1xEV, access probe can be transmitted at a time T
such that T modulo access cycle duration equals 0. The 1xEV standard, unlike 3G1x, allows
access cycle duration to be shorter than access probe duration. This is shown in Figure 1.
However, when probe search period is shorter than the probe transmission period, base station
requires multiple access channel elements. The SBEVM (CSM6800) supports multiple access
channel elements (at least 8). Hence, SBEVM implementation allows setting of access cycle
duration such that the search period is less than the probe transmission period (Preamble +
Message Capsule). On the other hand, DBEVM supports only one access channel element.
Therefore, the search period must be greater than or equal to transmission period. The access
cycle duration can only take on the following values: 16, 32, 64, and 128 slots. The
recommended value is 16 slots (26.67 ms), that is, 1 frame. The recommendation was changed
from 64 slots to 16 slots starting with R28.02. This is to reduce call setup latency for Push-to-
Talk (PTT) service and also to increase access channel capacity. This setting is supported for
SBEVM only. The recommended value for DBEVM is still 64 slots.
Figure 1. 1xEV Access Channel Structure
Access channel probe backoff (probebackoff): If the maximum allowable number of access
probes has not been reached, the next access probe is transmitted after TA + RT time. TA is a
fixed waiting time defined by the IS-856 standard as 128 slots (213.376 ms) whereas RT is an
additional random delay, which ranges from 0 to probebackoff in the units of access cycle
duration. The recommended value is 4 (106.67 ms) for SBEVM and 4 (426.67ms) for DBEVM.
Access channel probe sequence backoff (probesequencebackoff): If the maximum allowable

number of access probe sequences has not been reached, the next access probe in the next access
probe sequence is transmitted after TA + RS time. TA is a fixed waiting time defined by the IS-
856 standard as 128 slots (213.376 ms) whereas RS is an additional random delay, which ranges
from 0 to probesequencebackoff in the units of access cycle duration. The recommended value is
8 (213.38ms) for SBEVM and 8 (853.44 ms) for DBEVM.
Transmit antenna propagation delay (txdelay): The delay observed in the forward transmit
path between forward link modem (FLM, DBEVM) or SBEVM and the antenna connector.
Receive antenna propagation delay (rxdelay): The delay observed in the receive path between
the antenna connector and the reverse link modem (RLM, DBEVM) or SBEVM. Starting with
Cell/RNC Release R24, this translation parameter is used by the 1xEV system for both access
and handoff.
The recommended values of Txdelay and Rxdelay are shown in Table 1. The Txdelay is
independent of the controller (CRC versus URCm for legacy Mod cells) used.
Starting with RNC R31 SU1 and Cell R31.00, translation parameters Transmit Antenna
Propagation Delay (TxDelay) and Receive Antenna Propagation Delay (RxDelay) will have both
the per sector view and per sector carrier view. Cell R31.00 is required for the per sector carrier
view. The range of these translation parameters is 0 to 400us for both sector and sector carrier
views. If the cell release is either R29 or R30, then continue to use spare sector-carrier translation
parameters, Auxiliary Per-Sector-Carrier Control – 1 and Auxiliary Per-Sector-Carrier
Control – 2, to allow provisioning of TxDelay and RxDelay, respectively, on a per sector-carrier
basis. The unit of TxDelay and RxDelay at both sector and sector carrier levels is in us. However,
the unit of Auxiliary Per-Sector-Carrier Control – 1 and Auxiliary Per-Sector-Carrier
Control – 2 is 1/10th us. For example, if TxDelay of 139.5us is required, then set Auxiliary Per-
Sector-Carrier Control – 1 to 1395. If Auxiliary Per-Sector-Carrier Control – 1 and Auxiliary
Per-Sector-Carrier Control – 2 are set to 0, then they are not used and the current per-sector
translation parameters are used. EVM needs to be restored / rebooted for changes in
TxDelay/RxDelay parameters to take effect either at sector or sector-carrier level. The R31 OSR
implemented the following:
If auxSectorCarrierCtrl1 = 0; set scTxdelay to -1 (blank)

If auxSectorCarrierCtrl1 > 4000; set scTxdelay to 400us.
Otherwise set scTxdelay to (auxSectorCarrierCtrl1/10).
If auxSectorCarrierCtrl2 = 0; set scRxdelay to -1 (blank)

If auxSectorCarrierCtrl2 > 4000; set scRxdelay to 400us.
Otherwise set scRxdelay to (auxSectorCarrierCtrl2/10).
Parameter Recommended Value
450 700 Cellular PCS Korea

MCR MCR A or MCR B MHz MHz band band band IMT-2000
Tx_delay (Flexent Mod Cell) 27.7 us 27.7 us 19.9 us
Rx_delay (Flexent Micro/Mod Cell) 14 us 14 us 14 us
Tx_delay (Flexent Mod Cell, SBCBR) 27.7 us 27.7 us 20 us
Rx_delay (Flexent Micro/Mod Cell, SBCBR) 14 us 14 us 14 us
Tx_delay (Flexent OneBTS) 38 us 23.1 us 23.1 us
Rx_delay (Flexent OneBTS) 46 us 19.6 us 19.6 us
Tx_delay (Flexent OneBTS HD) 22.5 us 22.5us
Rx_delay (Flexent OneBTS HD) 19.6 us 19.6 us
Tx_delay (Flexent OneBTS HD MCR) 32.5 us 32.5 us
Rx_delay (Flexent OneBTS HD MCR) 19.6 us 19.6 us
Tx_delay (Flexent OneBTS Compact) 23.1us 23.1us
Rx_delay (Flexent OneBTS Compact) 19.6 us 19.6 us
Tx_delay (Flexent Korea OneBTS) 23.1 us
Rx_delay (Flexent Korea OneBTS) 19.6 us
Tx_delay (Flexent OneBTS MCR) 32.5 us 32.5 us
Rx_delay (Flexent OneBTS MCR) 19.6 us 19.6 us
Tx_delay (Flexent OneBTS Compact MCR) 32.5 us 32.5 us 32.5 us
Rx_delay (Flexent OneBTS Compact MCR) 19.6 us 19.6 us 19.6 us
Tx_delay BS2400 (OneBTS, MCR, SBEVM) 32.5 us 32.5us
Rx_delay BS2400 (OneBTS, MCR, SBEVM) 22.7 us 22.7 us
Tx_delay (OneBTS, UCR) 23.1 us
Rx_delay (OneBTS, UCR) 17.3us
Tx_delay BS4400, TTLNA (OneBTS, MCR) 32.5 us 32.5 us
Rx_delay BS4400, TTLNA (OneBTS, MCR) 19.6 us 19.6 us
Tx_delay BS4400, TTLNA (OneBTS, UCR) 23.1 us 23.1 us
Rx_delay BS4400, TTLNA (OneBTS, UCR) 19.6 us 19.6 us
Tx_delay (OneBTS, MCR, MCPA) 32.5 us 32.5us
Rx_delay (OneBTS, MCR, MCPA) 19.6 us 19.6us
Tx_delay (OneBTS, UCR, MCPA) 23.1 us
Rx_delay (OneBTS, UCR, MCPA) 19.6 us
Tx_delay PCS IA Frame (OneBTS 4.0B, MCR) 32.5 us
Rx_delay PCS IA Frame (OneBTS 4.0B, MCR) 19.6 us
Tx_delay (BTS 9234, 9228, 9222 with RRH) 0+ 0+
TICLI_Tx = op:cell X, asmb Y, rrh Z TICLI_Tx TICLI_Tx
Rx_delay (BTS 9234, 9228, 9222 with RRH) PCS
and AWS band classes have same values 0.7 + 2.4 +
TICLI_Rx = op:cell X, asmb Y, rrh Z TICLI_Rx TICLI_Rx
Table 1. Recommended values of TxDelay and RxDelay
Notes:
a) AWS band uses same Tx/Rx delay values as PCS band
b) 4400/4401 use the same Tx/Rx delay values as Mod4.0
c) Tx/Rx delay for BS2400 for 2100 MHz is the same as the one listed in the table above
Open loop power adjustment (openloopadjust): The nominal power used by an AT in the
open loop power estimate. The value used by the AT is (–1) times the value of openloopadjust.
The recommended values of this parameter are shown in Table 2. The AT transmits the ith probe
in the probe sequence at a power level given by X0+(i-1)*powerstep, where X0 represents the
AT’s open loop power of the pilot channel and is given by X0 = - rx power (dBm) +
openloopadjust + probeinitialadjust . The mean rx power is estimated throughout the
transmission of each probe. The probeinitialadjust parameter is defined later in this section.
The value of this translation parameter was changed starting with R24 due to increasing number
of deployed access terminals based on MSM6500 chipset. Access terminals based on MSM5500
chipset use Probe Power that is 6 dB below the expected value. This was corrected for the
MSM6500 chipset mobiles. The pre-R24 value of this translation parameter accounted for this 6
dB shortfall.
The recommended value of this parameter is updated starting with R28.02. The updated value
can be used for previous releases. The new recommended value assumes that the majority of the
mobiles in the market are MSM6500 and beyond. If there are still a large number of MSM5500
mobiles in the market, then this parameter can be set 6dB lower (to correct for AT’s probe power
issue) for all band classes.
Parameter Recommended Value
450 MHz 700 MHz Cellular band PCS band Korea band 2 GHz
Open Loop Power Adjustment 80 dB 81 dB 81 dB 82 dB 81 dB 82 dB
Table 2. Recommended Values of Open Loop Power Adjustment
It is possible that the starting power for the access probe may not be sufficient to overcome the
rise even after exhausting all 10 probes, especially on cells with heavy loading on the reverse
link. This calls for evaluating higher starting power for the probe. One way to adjust this is by
setting the Open Loop Power Adjustment parameter to a lower value (such as 76 dB instead of
recommended value of 82 dB for PCS band). Higher probe transmit power will improve the
chances of probe reception at the AN. This will also improve the first probe success rate, an
important metric for delay sensitive applications, such as PTT, as well as the mean/median
number of probes per attempt. However, when increasing the initial probe power, there is a
balance that needs to be maintained between better probe detection rate and interference caused
by unnecessarily high probe power. To overcome this limitation of the static Open Loop Power
Adjustment, starting with cell R32.0, Alcatel-Lucent has implemented dynamic Open Loop
Power Adjustment value which will be adjusted based on the average RSSI Rise. When there is
no significant RSSI Rise, the default (translation) value will be used for Open Loop Power
Adjustment. The following table shows the mapping between corrected Open Loop Power
Adjustment value and corresponding RSSI Rise for PCS band. However, the same change in
Open Loop Power Adjustment value applies for any other band classes.
RSSI Rise Translation Value (PCS band) of Corrected Value of

(dB) Open Loop Power Adjustment Open Loop Power Adjustment Change
0 82 82 0
3 82 79 3
6 82 76 6
9 82 73 9
12 82 70 12
15 82 67 15
18 82 64 18
21 82 61 21
24 82 58 24
>= 27 82 55 27
It is important to note that the above table is implemented via a RSSI Rise bin size of 3 dB as
identified in the table along with 2 dB of hysteresis. This is to avoid frequent changes in Open
Loop Power Adjustment which can impact latency and battery life since Open Loop Power
Adjustment is part of overhead Access Parameters. For example, if RSSI Rise is less than 3 dB,
then there is no correction in the value of Open Loop Power Adjustment. The correction factor
is 3 dB when the RSSI Rise is between 3 dB and 6 dB. The correction factor goes back to 0 when
the RSSI Rise falls below 1dB (3 – 2 dB hysteresis). The correction factor is 6 dB when the RSSI
Rise is between 6 dB and 9 dB. The correction factor goes back to 3 dB when the RSSI Rise falls
below 5dB (but greater than 3 dB). Prior to R37, the maximum correction applied to the Open
Loop Power Adjustment value was 15 dB. Starting with R37, the maximum correction applied
to the Open Loop Power Adjustment value is 27 dB
The dynamic Open Loop Power Adjustment algorithm will help reduce the number of probes
per access attempt which will thereby reduce the number of access collisions (less access channel
congestion). Prior to R35, the temporary translation parameter Auxiliary Per Sector Control – 2
controlled the dynamic Open Loop Power Adjustment algorithm. Starting with R35, the
translation parameter Dynamic Open Loop Power Adjustment Algorithm Enabled is used for
this functionality. During R35 retrofit, the OSR will carry forward the value of the parameter
Auxiliary Per Sector Control – 2 to the new translation parameter Dynamic Open Loop
Power Adjustment Algorithm Enabled. The value of the parameter Auxiliary Per Sector
Control – 2 is then reset to 0. The recommended value of the new parameter is Yes (enabled).
Initial probe power correction factor (probeinitialadjust): Correction factor to be used by an

AT for open loop transmit power estimation for initial transmission on the access channel. The
recommended value is 0 dB. The allowed values are -16 to 15 dB in steps of 1 dB.
Power increment step (powerstep): Power increment between two consecutive access probes
within one access probe sequence. The recommended value is 8 (4 dB). The allowed values are 0
to 15. The AT uses 0.5 dB times the value set in the database.
2.2 Access Search Window Size
The access search window size should be such that all possible users located in the covered areas
can access the system. Note that the upper limit on air delay is the sector size, and therefore the
translation, sectorsize, must be greater than the actual air delay at any point in the coverage area.
The optimal access search window width is
Access search window width (in PN chips)
= 2 * sectorsize (in miles) * 6.6 (chips/miles) + RxDelay (in us) * 1.23 (chips/us) (1)
The access search window width should ensure that all possible path delays in the coverage areas
are included in the path delay hypotheses tests. For convenience, Table 3 shows the conversion
formula between units. A velocity factor of 0.6 has been assumed for the cable.
Miles in air PN chips Microseconds Miles in cable

Miles in air 1 6.55 5.33 0.6663
PN chips 0.1527 1 0.814 0.1017
Microseconds 0.1876 1.2288 1 0.125
Miles in cable 1.5 9.83 8 1
Table 3. Conversion between different units
Note that there is an upper bound associated with the cell access search window. The maximal
cell access search window size is restricted by hardware. Therefore under any circumstances, the
following inequality for delay budget must be satisfied:
2 * sectorsize (in miles) * 6.6 (chips/miles) + RxDelay (in us) * 1.23 (chips/us) <= 512 chips (2)
It is very important to note that inequality in (2) holds true for any combination of sector
size and RxDelay values. If the inequality is violated, access probe may not be detected and
it may also impact forward link throughput due to lack of D-ARQ. Please refer to ALU
alert 10-1308 for more info.
2.3 Access Channel Slot Setup
The access channel slot structure for CDMA 1xEV is similar to that of CDMA IS-95A/B/2000.
The access channel probe consists of two parts: access channel preamble and access channel
message capsule. The access channel structure is shown in Figure 1. The access channel cycle is
the basic time unit of all access channel activities. If the access channel cycle duration can be
minimized, then all access channel activities will speed up proportionally. This can result in
improvement on access delay (probe delay and sequence delay etc.). The sizes of access
preamble and message capsule are controlled by the following two translation parameters.
Access preamble length (preamblelength): The access channel preamble is a series of known
symbols transmitted in the beginning portion of each access channel probe to assist the base
station in detecting AT’s signal through the whole range of delay hypotheses tests.
The access preamble size depends on the access search window width in Equation (1) because
the purpose of this preamble is to allow the base station to detect an AT. Therefore, for each
access channel slot, the preamble must be greater than the time that the base station needs to do
all the hypotheses tests in the access search window. Table 4 shows the relationship between
access search window size and access preamble. For normal operation (sector size of 10 miles or
less), the recommended value of this parameter is 1 frame.
Access preamble length (frames) Access search window size (PN chips)
1 width < 158 PN chips
2 158 PN chips <= width < 391 PN chips
3 391 PN chips <= width
Table 4. Optimal Access Channel Preamble Length
The recommendation for Access preamble length is changed from 2 frames to 1frame to reduce
the probe transmission time thereby reducing the overall reverse link interference. This will
ultimately help with better probe detection success rate.
Access capsule max length (capsulelengthmax): The maximum access message capsule length
that will be used for the access message. The capsule length should be large enough to contain at
least two access channel messages because, for any access channel message, the route update
message is always included.
Starting with R28.02 cell, recommendation of Access Capsule Max Length is changed from 2
frames to 4 frames for SBEVM to support Data-Over-Signaling. For existing Rev0 and RevA
mobiles, there shouldn’t be any impact since they will mostly use up to 2 frames. The
recommended value for DBEVM is 2 frames.
It is important to note that ALPHA sector values of Access Channel Parameters (Access
Preamble Length, Access Cycle Duration, and Access Capsule Max Length) dictate the values of
these parameters for BETA and GAMMA sectors. Ensure that these 3 parameters are set the
same across all 3 sectors of the cell. Even though this holds true only for DBEVM, these
parameters should be set the same across all 3 sectors for SBEVM unless needed to address
market specific circumstances.
2.4 Access Probe Power
During system access, closed-loop power control (feedback from the base station) is not possible
since the communication link is not yet set up. Open-loop estimation is used to determine the
power needed by the AT. A higher AT transmit power will allow easier access, but will create
interference to existing users. A lower transmit power will lengthen the duration of the access
process.
An access probe consists of preamble followed by message. During the preamble transmission,
only the pilot channel is transmitted. During the message transmission, both the pilot and the data
channel are transmitted. However, the total power transmitted by the AT during access preamble
transmission and access message transmission is same.
The initial access probe power IP of the AT is defined as

IP = - mean received power (dBm) + openloopadjust + probeinitialadjust, (3)
where openloopadjust and probeinitialadjust are defined in Section 2.1. The power of the
subsequent probe is powerstep dB higher than the previous probe within an access probe
sequence. The initial access probe power should be set high enough such that the first access
probe can be detected at the base station with high probability. On the other hand, usage of
excessive initial access probe power does not improve the access success rate significantly, but
instead creates more interference to the existing traffic users.
2.5 Access Delay Perceived by the End User
The net delay for a user to successfully access the system is governed by the required number of
access probes and sequences. The delay between access probes and between access sequences are
the primary contributing factors to the net delay perceived by the end user. The number of probes
and sequences needed for a successful access attempt is determined by the probe power, the
instantaneous reverse link power level at the base station, the number of simultaneous access
users (or indirectly the access arrival rate), and even the dynamics of pilot change (i.e., fast
shadow fading plus user mobility), etc.
The delay between probes and between sequences is basically a trade-off. A short delay between
probes and between sequences will in general yield shorter user-perceived delay and also will be
more immune to the dynamics of pilot change (i.e., less chance for change in the dominant pilot
between probes and sequences). On the other hand, if a sudden burst arrival of access occurs
(e.g., traffic events, sports events, disaster, etc.), this instantaneous increase in arrival rate will
create large interference to the whole system. Usage of a longer delay between probes and
between sequences will somewhat reduce the interference in such a situation. Since the chance of
this sudden burst arrival is rare compared to the chance of dynamics of pilot change, the idea is to
use shorter delay between access probes and access sequences.
3 1xEV Default Best-Effort Paging
Paging is the mechanism used to inform a dormant access terminal about access network’s
request for a connection when there is pending data. This section only covers the default best-
effort (DBE) paging strategy. In addition to DBE paging, there are several new paging strategies
supported with introduction of RNC Grouping, QoS Paging, and Distance based Paging. Paging
strategy with RNC Grouping enabled is discussed in translation application note #13. QoS
paging including Distance based paging is documented in translation application note #12.
The DBE paging uses synchronous control channel to transmit page messages. The access
network uses two distinct methods of DBE paging when it has pending data to transfer to a
dormant AT:
1) Normal DBE paging method which, conceptually, is very similar to the paging
method used in 3G1x HSPD network
2) Fast connect DBE paging method which is unique to 1xEV
Selection of a paging method depends on whether dormant AT is in suspended mode or slotted

mode when AN has data to transmit.
3.1 Slotted Mode Operation
The 1xEV idle state protocol supports periodic network monitoring by the access terminal. This
results in less processing at access terminal, which reduces power consumption thereby,
increasing battery life. In slotted mode operation, AT monitors only selected synchronous control
channel cycle (Sync CCC), which is transmitted every 426.67ms. The access terminal transitions
to monitor state from sleep state once every 5.12s (one Sync CCC out of every 12 Sync CCC).
Hence, the 1xEV sleep period duration is 5.12, which is defined by the standard and is not
configurable. The access terminal transitions to slotted mode from suspended mode after
expiration of suspend timer. In suspended mode, AT monitors Sync CCC continuously for a
period of time defined by suspend timer at the access terminal.
3.1.1 Paging Slot Determination for EVDO only Mode
The default best-effort paging mechanism in slotted mode requires access network know which
Sync CCC access terminal will transition from sleep state to monitor state. Both AN and AT
determine this Sync CCC using a hash function defined by 1xEV standard. Random Access
Terminal Identifier (RATI), also known as Session Seed, is used as an input to this hash function.
RATI is a 32-bit pseudo-random number which is communicated to the AN by the AT during
initial setup of 1xEV session.
3.1.2 Paging Slot Determination for Hybrid Mode
Hybrid AT in slotted mode is required to periodically monitor both 3G1x paging channel and
1xEV Sync CCC. Hybrid AT knows its 3G1x sleep cycle based on IMSI, maximum slot cycle
index value transmitted OTA, and its own programmed slot cycle value. Hybrid AT will always
negotiate its 1xEV sleep cycle using Preferred Control Channel Cycle (PCCC) attribute. The
access terminal proposes PCCC value such that it will not conflict with its 3G1x tune away.
3.2 Location of Dormant Access Terminal
In 1xEV, there is no centralized database such as HLR/VLR as in 3G1x to keep track of the
access terminal whereabouts. Knowledge at the 1xEV Radio Network Controller (RNC) of
dormant AT’s location will reduce the probability of RNC wide paging. The current
implementation uses two forms of registration to keep track of dormant AT’s location:
1) Subnet based registration
2) Distance based registration
3.2.1 Subnet based Registration
A subnet can be viewed as geographic coverage area spanned by a group of cells that use same
color code. Color code is associated with the subnet to which Unicast Access Terminal Identifier
(UATI) belongs. For example, all cells on a single RNC will have same color code. The subnet
area is restricted to coverage area spanned by cells on a single RNC and is not currently
configurable. The access terminal re-registers with access network (after crossing RNC
boundaries) when it notices change in color code. After AT registration, information including
Pilots reported in RouteUpdate message and new controlling RNC is stored at access network
and is used for future paging purpose. This process is also called Inter-RNC Idle/Dormant
Handoff.
The above original definition of subnet has changed with introduction of RNC Grouping feature.
With RNC Grouping enabled and subnet mask of 64, AT will not re-register even when it crosses
RNC boundaries within the RNC Group. Please refer to translation application note #13 for more
information.
3.2.2 Distance based Registration
A dormant access terminal re-registers with access network when it is at a distance greater than
the threshold RouteUpdateRadius field in the SectorParameters message from the last accessed
base station. Distance is computed using fields Latitude and Longitude of the SectorParameters
message from last accessed base station and the one AT is currently monitoring. It is important to
note that the distance (angular distance) computed is between two base stations and not between
the last accessed base station and the AT. After registration, information including pilots reported
in RouteUpdate message is stored at access network and is used for future paging purpose. This
form of registration can be used if a RNC coverage area is quite large. To enable distance based
registration, set the translation parameter Radius for Registration Update (angular distance) to
a non-zero value. The current recommendation is 0 (turn off distance based registration).
Additionally, the translation parameters Base Station Antenna Latitude and Base Station
Antenna Longitude need to be appropriately populated in the database.
Below is the information on how to populate Latitude and Longitude information in the database.
Starting with R28, Latitudes have values from -90 to 90 with -90 corresponding to 90-degree
South Latitude (South Pole), and 90 corresponding to 90-degree North Latitude (North Pole).
The equator is 0 degree Latitude.
Starting with R28, Longitudes have values from -180 to 180 with -180 corresponding to 180-
degree West Longitude and 180 corresponding to 180-degree East Longitude. The Prime
Meridian (Greenwich, England) is 0 degree Longitude.
For example, North Latitude of 40:43:28N would be entered as 40 degrees, 43 minutes, 2800
seconds. Please note that seconds are multiplied by 100 when entered in the GUI. Hence, for 28
seconds, enter 2800. For South Latitude of 65:45:36S, enter it as -65 for degrees, 45 minutes,
3600 seconds in the GUI database.
For example, East Longitude of 74:24:58E would be entered as 74 degrees, 24 minutes, 5800
seconds. For West Longitude of 65:45:36W, enter it as -65 for degrees, 45 minutes, 3600 seconds
in the GUI database.
The current recommendation is to enable distance based registration with RNC R28 SU2 and
beyond. Given a RNC of geographic area A, set the Radius for Registration Update such that it
covers a circle of one quarter of the area A. That is, 0.25 * A.
3.3 1xEV Default Best-Effort Paging Methods
There are two different types of DBE paging methods.
3.3.1 Normal DBE Paging Method
Normal paging method is invoked by access network when suspend timer at dormant access
terminal has expired and access terminal has entered slotted mode operation. This paging method
is implemented via a two-step process:
1) Access network sends page message on all sectors last accessed by access terminal. That
is, page the last known active set
2) If there is no response from the access terminal after executing step 1), page all cells
within the same RNC
Starting with R28, there are two translation parameters associated with normal paging method.
The translation parameter Number of Times to Page the Last Active Set (name change with
R28) governs the number of page attempts for step 1. The translation parameter Number of
Times to Page the Last Seen RNC (name change with R28) governs the number of page
attempts for step 2. The recommended values for both of these parameters are 2. With the above
recommendations, there are a total of 4 page attempts for each page request. The translation
parameter Paging Strategy is obsolete starting with R28.
Prior to RNC R28, RNC sends a page as soon as it receives data from the PDSN. RNC then starts
a repage timer. When the timer expires RNC sends another page attempt and restart the timer.
This process continues till all the page attempts are exhausted. Prior to R28, the repage timer was
hard coded to 5 seconds from the time RNC sends the message to the cell. For example, if the
AT doesn't wake up for next 4 seconds, RNC will only give AT 1s to respond to the page before
the repage timer expires. Starting with RNC R28, the repage timer implementation has changed.
The repage timer starts from the time the page message is sent over the air. In other words in R28
RNC estimates AT’s next wake up time and starts the repage timer accordingly. Additionally, the
repage timer is governed by the translation parameter Minimum Time to wait for a Page or
DoS response (also called Repage Timer under Profile ID). The recommended value for this
translation is 2s. It can be set as high as 5s for default page cycle of 5.12s without negative
tradeoff. This parameter governs the tradeoff between page success rate and page response time.
If it is set to a higher value (> 5), it will give AT more time to respond by extending the paging
cycle time. However, this will slow down the page response time. The new repage timer
mechanism may change the page attempt distribution (compared to pre-R28) depending on the
repage timer value.
Parameter Recommended value

Paging Strategy Obsolete Starting with R28
Number of Times to Page the Last Active Set 2
Number of Times to Page the Last Seen RNC 2
It is important to note that if the last known active set contained Pilots from different RNCs, only
cells under the RNC governing the AT session (UATI) will be paged when the second step is
executed. If all the page attempts fail, the data packets that generated the page request are
discarded. However, the R-P connection remains intact. If AN receives the page response from
AT (AN-Initiated Connection Request), but the call setup fails, AN will keep paging the mobile.
If AN receives new data from PDSN while it is already in the paging process, the new data will
be buffered but it will not trigger a start of new paging sequence. If AN receives page response
all the buffered data (initial and new) will be sent to the AT. If all the page attempts fail, all the
data packets (initial and new) will be discarded.
3.3.2 Fast Connect DBE Paging Method
This form of paging method is used by 1xEV access network to establish traffic channel with
access terminal using fewer signaling messages. It is invoked (as oppose to Normal Paging
method) when AN has data to send while the suspend timer is running at the access terminal.
When Dormancy timer expires, AT may include suspend timer in the ConnectionClose message.
If the AT included suspend timer in the ConnectionClose message then it is running in suspended
mode and is monitoring all Sync CCCs.
If the AN has data to send to a dormant AT while suspend timer is running, it will initiate fast
connect procedure using AT’s last known active set. Access network directly sends
TrafficChannelAssignment message thereby eliminating the need to exchange page and
ConnectionRequest messages. The suspend timer is set to 5s at AT. The access terminal cannot
move a significant distance within 5s (suspend timer) and hence, it is very unlikely that AT’s last
active set will change. There are no translation parameters associated with this paging method.
Mobiles based on MSM5500 chipset support non-zero suspend timer. Mobiles based on
MSM6500 and MSM6800 chipsets, in most cases, do not support non-zero suspend timer.
Hence, Fast Connect method is never invoked for these mobiles.
4 Dormancy State
In CDMA 1xEV packet switched data, when the traffic channel is idle during a data call for time
defined by a translation parameter, Dormancy Timer, the call enters a dormancy state. That is,
the physical channel is teared down. This would help reduce overall call blocking due to system
resources. When the user requests additional data transfer, the physical channel goes through the
routine setup procedure (without the end user knowledge). The end-to-end channel is still active,
that is, the mobile IP address is still the same. The recommended value of this parameter is 10
seconds.
5 Test Carrier Feature
The Test Carrier feature is introduced in 1xEV R23. This feature enables a 1xEV carrier access
to be restricted to a special class of mobiles. In 1xEV, there are up to four mobile classes.
Currently, all ATs are using the default class of '0'. The test mobiles can be programmed to use
any other class while the system is being integrated and optimized. With only test mobiles
allowed, the optimization process can be carried out in a well-controlled manner and service will
not be provided to the end-users prematurely.
The test carrier feature uses persistence parameter, APersistence field in the
AccessParameterMessage, to restrict 1xEV access. When test carrier feature is ON, the first
occurrence of APersistence field is set to 0x3F. It is set to 0x00 when the test carrier feature is
OFF. AT uses this persistence parameter to compute persistence probability P in the following
manner:
P = 2 ^ (-N/4), where N is the value of the APersistence field

=0 if N = 0x3F
AT generates a random number X between 0 and 1. If X < P, the persistence test will be
considered successful and AT will be able to send the access probes. Otherwise, AT will not be
able to send access probes on 1xEV system. Hybrid ATs will access 3G1x system subsequently.
A non-test mode AT will be able to perform active mode handoff to a test carrier enabled sector.
Programming of the mobile (for test mode) can be done via Qualcomm CDMA Air Interface
Tester (CAIT) as well as Engineering Menu of the Connection Manager. The test carrier feature
is controlled via the translation parameter Test Carrier. The default value of this parameter is
No.
It is important to note that this feature only works when both RNC and Cell loads are at least
running R23 loads.
Starting with R26, RNC will block all handoffs to a test carrier enabled cell if the call originated
on a non-test carrier cell. If the call originated on a test carrier, access network will allow the
handoffs to a test carrier enabled cell. If a call originated on a test carrier cell, access network
knows that this is a test mobile and will allow handoffs in to a test carrier cell. Active handoffs
from test carrier cells to non-test carrier cells are allowed.
In a multi-carrier cell with test carrier enabled, there are two distinct channel lists: one list
includes channel information for all non-test carrier sector-carriers and the other list only
includes channel information for test carrier enabled sector-carriers. If non-test AT enters the
coverage of this cell either via acquiring 1xEV system (on a non-test carrier sector-carrier) or idle
handoff in to a non-test carrier sector-carrier, AT will be able to access 1xEV system on this cell
(AT will not hash to test carrier enabled sector-carrier since the channel information is not
included in the channel list). If a non-test AT is idling on a sector-carrier, which is later on
marked as test carrier, AT will try to access 1xEV on a non-test carrier sector-carrier if this
carrier channel info is provisioned in Preferred Roaming List (PRL). If a non-test carrier is not
provisioned in the PRL, AT will access 3G1x instead.
Starting with RNC R27 SU2 and Cell R27.01, there is an enhancement to the test carrier feature
implementation. This is to alleviate the rapid mobile battery drain issue when mobiles are trying
to acquire 1xEV system on a test carrier enabled cell. These mobiles try un-successfully to access
the EVDO test carrier because they are programmed to see the System ID (SID) that is being
transmitted over the air by the network. This SID is same for both the test-carrier and the
commercial carrier. These mobiles have a built-in algorithm, which wakes up once a minute and
attempt to access the network but fails. These continuous periodic attempts to access the network
in test carrier mode are causing these mobiles to lose its power rapidly. The workaround solution
is for the network to set the SID to 0 for test-carrier. When the SID is set to 0, the expected
behavior of these handsets is that they do not acquire the EVDO carrier and will not attempt to
access the network frequently. Starting with R33, a new translation parameter SID Override is
introduced to govern the SID value that is transmitted over the air. A value of 1 means SID
override is enabled and the access network will transmit SID=0 over the air only for the sector
carriers that are in test-carrier mode. A value of 0 means SID override is disabled. The
recommended value of the this translation parameter is 1.
IS-856 RevA standard defines APersistence index 2 for test mobile. Starting with R29, Alcatel-
Lucent has updated the test carrier implementation to confirm to this new standard change. With
this change, when test carrier feature is ON, the third occurrence of APersistence field is set to
0x3F. It is set to 0x00 when the test carrier feature is OFF. AT uses this Apersistence parameter
to compute persistence probability P, which is used for access. The test mobiles now need to be
programmed with access overload class of either 12 or 13 so that they can access the test carrier.
A mobile with access overload class set to 10 will not be able to access test carrier with the new
implementation. Access overload class (ACCOLC) is a 4-bit value which is translated to
APersistence index according to the following:
ACCOLC APersistence index

------------ ------------------------
0–9 0
10, 11 1
12, 13 2
14, 15 3
It is important to note that system id (SID) change is accounted for test ATs via Preferred
Roaming List (PRL) if SID is set to 0 when test carrier feature is enabled.
6 PDSN Selection Algorithm
Lucent 1xEV system allows provisioning of multiple PDSNs at the RNC. Currently, RNC uses
either RATI based algorithm or IMSI based algorithm to select one of the PDSNs. For IMSI
based algorithm, RAN authentication needs to be enabled. If IMSI is available, 1xEV system will
select the same PDSN as underlying 3G1x system.
If RAN authentication is disabled, the MNID (Mobile Mode Identifier) is computed based on
RATI instead of IMSI. It is ensured that this number is unique from a valid IMSI. In this case, a
preferred PDSN can be selected for data transfer by repeatedly releasing AT’s UATI (essentially
forcing AT to setup new 1xEV session using RATI) till RNC selects desired PDSN.
If the RAN authentication is ON, MNID = IMSI. MNID is input to the standard defined PDSN
selection algorithm. If RAN is OFF, MNID = 999999 + last 9 digits of RATI. MNID is 15 digits
in decimal value. The standard defined PDSN selection algorithm is:
For initial PDSN assignment and for PDSN reselection, the PCF shall determine which
PDSN to use for a particular MS by the following:
PDSN No. = (truncated MNID) modulo N,
where (truncated MNID) is defined to be the least significant 4 digits of the MNID taken as a
decimal value. N is the number of PDSNs provisioned in the database.
7 Multiple Carriers: Hashing and Traffic Load Balancing
Starting with cell release R26.0, Lucent 1xEV system supports cells with multiple carriers.
Following sections discuss the basic concepts of hashing across carriers, traffic load balancing
between carriers, border carrier and related translation parameters. A new traffic loading
balancing algorithm (FID 8219.26) introduced in R37 is documented in application note #12.
7.1 1xEV Mobile Hashing
Mobile hashing distributes mobiles uniformly across multi-carriers. This helps balance traffic
load across carriers reducing the number of cross-carrier traffic channel assignments.
Additionally, it also helps balance Control Channel and Access Channel occupancy among
carriers which leads to better overall access performance.
When multiple carriers are present in a sector, the AT selects a channel to monitor based on the
hash algorithm defined in section 10.4 of IS-856. The inputs to hash algorithm are Random
Access Terminal Identifier (RATI) and number of channels listed in SectorParameters message.
Whenever the number of channels listed within the SectorParameters message changes, the idle
AT will re-execute the hash algorithm. As idle mobile moves around the network from sector to
sector, it may monitor different channels in each sector, depending on the number of carriers
available in each sector.
Call processing maintains two separate channel lists for each sector: non-test carrier channel list
and test carrier channel list. The non-test carrier channel list will not contain any test carriers, and
the test carrier channel list will not contain any non-test carriers. This is due to:
1) Once a test mobile is on a test carrier we want that test mobile to remain on a test carrier.
If the channel list for the test carrier contains non-test carriers, the mobile could hash to a
non-test carrier.
2) Non-test mobiles should be prevented from attempting to access the test carrier. By not
listing any of the test carriers in the channel list of a non-test carrier, we ensure that once
the mobile tunes to a non-test carrier it will not attempt to access a test carrier
7.2 Traffic Channel Selection Algorithm for Call Setup
The main purpose of this algorithm is to try to balance traffic load across multiple carriers.
Starting with RNC R32, both Rev0 and RevA mobiles use the traffic channel selection
algorithms based on RSSI Rise if all carriers are RevA enabled. For Rev0 mobiles, the algorithm
applies to both session setup connection requests and user connection requests. The translation
parameters Load Balancing Method and Load Differential are not used starting with RNC R32
if the carriers are all RevA capable. Unlike CDMA, there is no algorithm based on forward RF
loading since in 1xEV forward link is always transmitting at full power.
Traffic load balancing is not performed between test carriers and non-test carriers. If the
connection request is received on a test carrier then AT will only be assigned to a test carrier.
Similarly if the connection request is received on a non-test carrier then AT will only be assigned
to a non-test carrier.
7.3 Traffic Channel Selection Algorithm based on Originating Carrier
With this algorithm, a mobile will be assigned a carrier based on the origination carrier, i.e., if a
mobile originate on carrier F1, the call will be assigned carrier F1 for traffic. This is useful for a
multi-carrier system when each carrier may have different RF coverage footprint.
Call processing will select the originating carrier for traffic channel assignment if the translation
parameter RF Load Differential is set to 1 and the number of active users does not exceed the
value of the translation parameter Maximum Number of Users Supported for RevA.
Otherwise, if all the active users are carrying out data transfer, call processing will select another
(least loaded) carrier if possible. If another carrier couldn’t be selected, and if there are active
users that are idling (not carrying out data transfer and dormancy timer hasn’t expired yet), then
after Tforcerelease timer has expired, the longest idle user on the originating carrier will be
forced into dormancy and the new call will be assigned to the originating carrier. If all fails, the
connection request will be denied.
7.4 Traffic Channel Selection Algorithm based on RSSI Rise
Starting with R32, both Rev0 and RevA mobiles use traffic load balancing algorithm based on
RSSI Rise. The algorithm based on number of active users is not used if all carriers are RevA
capable. It is important to note that RevA mobiles (QoS enabled in the system) were already
using this algorithm for traffic load balancing since R29. This algorithm is based on loading
(RSSI Rise) instead of Number of Active Users. The translation parameter, RF Load
Differential, is used in the traffic channel selection algorithm and the preference is given to the
carrier that the AT originally accessed. For each carrier in the sector, Call Processing computes
the difference between the loading of the originating sector carrier and the other carriers in that
sector. If all of the differences are less than the value of this translation parameter, AT is assigned
resources on the originating carrier. Otherwise, AT is assigned to another (least loaded) sector
carrier. The loading L is defined as
L = 1 - (1/RoT),
where RoT is RSSI rise in linear scale. If L_Orig - L_Target (least loaded carrier) < RF Load
Differential then select Originating carrier. Otherwise, select the least loaded Target carrier.
When RoT is 6 dB, the loading L approaches 75% (0.75). The mapping between RSSI Rise and
Loading is shown in the following table.
If the number of active users on the originating sector carrier is less than the translation
parameter, Maximum Number of Users Supported Rev0/RevA, and the loading on the
originating sector carrier minus the RF Load Differential is less than the loading on each of the
other carriers in that sector, then the originating carrier is selected. Otherwise, the call is assigned
to the least loaded carrier. If another carrier couldn’t be selected, and if there are active users that
are idling (not carrying out data transfer and dormancy timer hasn’t expired yet), then after
Tforcerelease timer has expired, the longest idle user on the originating carrier will be forced into
dormancy and the new call will be assigned to the originating carrier. If all fails, the connection
request will be denied.
Starting with RNC R32, the recommended value of the translation parameter, RF Load
Differential, is changed to 0.2 from 0.1. This is to reduce the number of overall cross carrier
assignments and thereby reduce the number of cross carrier failed call attempts (FCA). There is a
tradeoff between load balancing and cross carrier FCA rate. In general, lower RF Load
Differential leads to very effective load balancing between carriers but higher cross carrier
FCAs. There is no one value of RF Load Differential that works for all markets. Hence,
individual markets need to fine tweak the value of this translation parameter for effective load
balancing and FCA performance. The recommended value provides a good starting reference
point. Field data has shown that cross carrier FCA rate for Rev0 mobiles is higher than that of
RevA mobiles. This is expected and can be attributed to the level of RF sensitivity (RevA mobile
usually reports better SINR than Rev0 mobiles) and other AT fixes/enhancements. With this R32
change, there is a significant increase in number of cross carrier attempts for Rev0 mobiles. Since
Rev0 mobiles have higher cross carrier FCA rate, this increase in Rev0 cross carrier attempts will
increase the overall cross carrier FCA rate. It is important to note that there is no increase in
either Rev0 cross carrier FCA rate or RevA cross carrier FCA rate. Distance based
origination/termination should also be used to minimize cross carrier assignments and at the
same time not significantly sacrificing load balancing.
RSSI Rise (dB) Translation Parameter RF Load Differential

0.46 0.1
0.97 0.2
1.55 0.3
2.22 0.4
3.01 0.5
3.98 0.6
5.23 0.7
6.99 0.8
10.00 0.9
Prior to R35, the temporary translation parameter Auxiliary Per Sector Control – 1 was used to
set RF load differential at the sector level. Starting with R35, the translation parameter RF
Loading Differential is used at the sector level. During R35 retrofit, the OSR will carry forward
the value of the parameter Auxiliary Per Sector Control – 1 to the new translation parameter
RF Loading Differential. The value of Auxiliary Per Sector Control – 1 is then reset to
default value of 0. The recommended value of this parameter is 20 (20 means 0.2 in terms of RF
load differential). A value of 0 means blank. A value greater than 100 (1 in terms of RF Load
Differential) also implies blank.
7.5 Traffic Channel Selection Algorithm for a Mix of Rev0 and RevA Carriers
Prior to R28 SU1, the traffic channel selection algorithm is implemented as follows: During
session setup phase, the AT’s personality (capability) is not known. Call processing uses both
Number of Active Users and Load Differential to assign connection request to either one of the
carriers, Rev0 or RevA. Once the session is configured, that is, AT’s personality is known, Rev0
calls are assigned to the Rev0 carrier and RevA calls are assigned to the Rev A carrier, till the
maximum number of users limit is reached. In presence of current limited RevA mobile
population, this implementation leads to in-efficient use of RevA carrier capacity. Additionally,
this results in significant number of cross-carrier assignments. An idle mobile will hash to one of
carriers based on its RATI. A Rev0 mobile may hash to a RevA carrier, and then will be assigned
to the Rev0 carrier based on this implementation during user initiated connection request. Cross-
carrier assignments may lead to a high call setup failure rate due to RF mismatch between the
carriers.
Starting with R28 SU1, the load balancing algorithm in case of mix Rev0/RevA carriers is
enhanced to mitigate both in-efficient use of RevA carrier as well as possible high call setup
failure rate due to excessive cross carrier assignments. This load balancing algorithm allows
RevA carrier to carry Rev0 traffic. Pre-RNC R29, this is controlled via a tunable parameter
called Rel0RevAloadDifferential threshold. Starting with R29, this is controlled via a new
translation parameter called Rel0 RevA Loading Differential. Rev0 calls originating on a RevA
carrier are assigned to the originating RevA carrier till the number of active users on RevA
carrier exceeds the number of active users on Rev0 carrier by this threshold. Once this threshold
is exceeded, then the Rev0 calls originating on RevA carrier will be cross-assigned to the Rev0
carrier. The current recommended value for this parameter is 15. The valid range of this
parameter is -59 to 59. The tunable parameter can be updated via an OMP script. Refer to the
R28 SU1 release letter on the use of this script. Setting this field either higher or lower than this
range will turn OFF this enhancement and revert back to pre-R28 SU1 load balancing algorithm.
The negative value for this threshold implies carrier selection preference is given to Rev0 carrier
for Rev0 mobiles originating on RevA carrier. If this threshold is set higher than the translation
Maximum Number of Users Supported for RevA and the RevA carrier reaches this maximum
number of users limit, both Rev0 and RevA calls will be assigned to Rev 0 carrier if possible
(Rev0 carrier has resources). Otherwise, if there are active users that are idling (not carrying out
data transfer and dormancy timer hasn’t expired yet), then after Tforcerelease timer has expired,
the longest idle user on the RevA carrier will be forced into dormancy and the new call will be
assigned to the originating carrier. If all fails, the connection request will be denied. The same
holds true if Rev0 carrier reached Maximum Number of Users Supported for Rev0 limit.
Alcatel-Lucent doesn’t recommend a mix of Rev0/RevA carrier configuration.
7.6 Border Carrier
A border sector carrier, also known as discontinuing carrier, is defined as a sector carrier where
the frequency of that carrier is no longer supported as AT moves away from that sector, but
where other 1xEV carriers are available. The border sector carrier designation should only be
used within the boundaries of 1xEV coverage area, embedded within a larger 1xEV coverage
area with different frequencies (continuing/common carriers), and not along the edge of the
1xEV coverage. The cells along the edge of the 1xEV coverage area, the area where 1xEV is no
longer supported as AT moves further from the cells, should not be marked as border sector
carriers. This is to fully utilize the air interface resources within those sectors as efficiently as
possible. Since there is no Inter-Frequency Handoff (IFHO) at the 1xEV coverage boundary,
there is no advantage in marking these sectors as border sector carriers.
The translation parameter, Border Carrier, designates whether a sector carrier is a border sector
carrier or not. Carriers that are marked as a border sector carrier are excluded from the channel
lists that are calculated, unless there are no other carriers available in that sector. By excluding
the border sector carrier from the channel list, it prevents access attempts on that carrier. Field
data shows that access attempts are more susceptible to failures on the border carrier. Also, calls
may be handed down to another carrier, via IFHO, immediately following call setup.
8 Session Close: Critical System Edge Metric Preservation Feature
Session Close feature, also known as Critical System Edge Metric Preservation feature, allows
service providers an option to deny Session Setup requests from mobiles in poor RF / non-
designated 1xEV coverage areas. Mobiles are very persistent in trying to establish 1xEV session
since that’s what they are designed for. Many ATs are autonomously attempting to start up new
sessions in extremely poor RF conditions outside of the nominal service area. These attempts use
up Reverse Link resources often taking them away from other ATs that have a better chance of
establishing a data connection. Battery life of these ATs is also most often needlessly diminished.
These persistent session setup requests also impacts 3G1x termination performance of these
hybrid mobiles since these ATs do not tune to 3G1x while trying to establish 1xEV session. The
number of such session setup requests is sufficient to skew Service Measurements so that they no
longer provide an accurate account of the service in the valid coverage area.
This feature provides operators with the choice to deny session setup attempts that are in poor RF
conditions and too far away from serving sector (those having a negligible chance of successfully
establishing a data connection). It only impacts ATs that are undergoing session setup in poor RF
conditions at the edge of the service area. Users, with valid 1xEV session, are not impacted.
When the network denies several successive 3 to 4 session setup attempts, hybrid AT avoids
monitoring 1xEV system for a period of about11 minutes. It monitors only 3G1x during this
time. In case of multiple 1xEVcarriers, AT will avoid the carrier it acquired 1xEV and not the
hashed carrier where it received SessionClose message. After all 1xEV carriers are avoided, AT
will monitor 3G1x for about 11 minutes.
There are three parameters associated with this feature. The names of these translation
parameters were changed starting with R27. Setting the translation parameter, RF-Border
Session Setup Deny ( pre-R27 RF-Border Session Setup Connection Deny) to Deny
Connections in Poor Conditions (recommended value), will activate the feature. The RF and
Distance thresholds, used by the feature, are defined by the translation parameters, Signal
Strength Threshold for Session Setup Request Denial (pre-R27 Minimum Initial Signal
Strength Threshold) and Minimum Distance Threshold for Session Setup Request Denial
(pre-R27 Minimum Distance Threshold for Initial Connection Denial), respectively. The
recommended values of these parameters are –9 dB and 2.5 miles, respectively.
In general, this feature can be disabled if there are no EVDO coverage gaps. With the advent of
real time application such as PTT, this feature can be disabled to minimize impact to PTT
mobiles. It is important to note that when the feature is disabled there could be an increase in
session setup requests, increase in session setup failed connection attempts, increase in
configuration negotiation failure rate, increase in access channel occupancy, increase in RSSI
Rise, etc.
Scenario Idle mode hashing Traffic Channel Load Balancing Algorithm

(Default Idle State Protocol)
F1 is Non-
F1, F2
Border
are Non-
carrier, F2 Session Setup Connection Setup
Border
is Border
carriers
carrier
Two Rev 0
carriers Originating Carrier or Number of Active Users
Two Rev A
carriers RSSI Rise
QoS
disabled
Two RevA
carriers
RSSI Rise RSSI Rise
QoS
Always to
enabled Based
the Non-
on RATI Pre Rev0 AT assigned to Rev0
Border
carrier (F1) R28 carrier, RevA AT assigned to
SU1 RevA carrier,
RevA carrier allowed to carry
Mixed Number of Rev0 traffic via tunable
Rev0/RevA Active Users parameter (R28)
carriers Rel0RevAloadDifferential and
R28
translation parameter (R29)
SU1
Rel0 RevA Loading
Differential
RevA calls assigned to RevA
carrier
Table 5. Summary of Hashing and Traffic Channel Load Balancing Algorithms
Starting with R32, the above traffic channel load balancing algorithm based on RSSI Rise is also
used for Rev0 mobiles for load balancing between Border and Non-Border carriers. RevA
mobiles were already using this algorithm. The translation parameter, Border and Non-border
Loading Ratio, governs the traffic load balancing between Border and Non-Border carriers. This
is true for both RevA and Rev0 mobiles. For both Rev0 and RevA users, the translation
parameter only reflects On/Off switch. A value in the range [1,100] indicates that the traffic load
balancing algorithm between Border and Non-Border carriers is enabled. If it is set to 0, the
traffic load balancing between Border and Non-Border carriers is disabled for both Rev0 and
RevA users.
Table 5 summarizes both hashing and traffic channel load balancing algorithms for different
configurations and scenarios.
9 Summary of Translation Parameters
OMC-RAN Field Label OMC-RAN GUI Page Recommended Note

Values
Sector Size Sector - General / FxAPx - SN 10 miles
General - General 2
Access Cycle Duration**,*** Sector Carrier – Access 16 slots
Control / Sector - Access
Control / FxAPx - SN General -
General 2
Access Capsule Max Sector Carrier – Configuration / 4 frames
Length**, *** Sector - Configuration / FxAPx
- SN General - General 2
Access Preamble Length** Sector Carrier – Access 1 frame Recommendation
Control / Sector - Access changed starting with
Control / FxAPx - SN General - R32. Can be applied to
General 2 pre-R32 release. This
applies to both Rev0
and RevA (without
EAC).
Access Channel Probe Sector - Configuration / FxAPx 4 Units of Access Cycle
Backoff - SN General - General 2 Duration
Access Channel Probe Sector - Configuration / FxAPx 8 Units of Access Cycle
Sequence Backoff - SN General - General 2 Duration
Number of Access Probes Sector - Access Control / 5
FxAPx - SN General - General
2
Maximum Number for an Sector - Configuration / FxAPx 2
Access Probe Sequence - SN General - General 2
Open Loop Power Sector Carrier – Access 82 dB (PCS) Max Tx Pwr per
Adjustment* Control / Sector - Access 81 dB (Cellular) Carrier PCS – 16W
Control / FxAPx - SN General - Cellular – 20W
81 dB (Korea)
General 2 Korea – 20W
80 dB (450 MHz) 450 MHz – 26W
81 dB (700 MHz) 700 MHz – 20W
82 dB (2 GHz) 2 GHz – 16W
Lower value can be
used on high traffic
cells to compensate for
high RoT
Dynamic Open Loop Power Sector – Access Control Yes (enabled) Prior to R35, Auxiliary
Adjustment Algorithm Enabled Per Sector Control – 2
controlled this
functionality.
Antenna Propagation Delay: Sector – General / 19.9 us (pcs) MCR MCR-A or

Transmission Delay**** SectorCarrier - General 27.7 us (cellular) MCR-B
27.7 us (450 MHz)
AWS band uses same
23.1 us (pcs, Tx/Rx delay values as
OneBTS) PCS band.
32.5us (pcs,
OneBTS, MCR) 4400/4401 use the
23.1 us (cellular, same Tx/Rx delay

OneBTS) values as Mod4.0
32.5us (cellular,
OneBTS, MCR) Tx/Rx delay for BS2400
for 2100 MHz is the
23.1 us (Korea, same as the one listed
OneBTS) here
22.5 us (cellular,
OneBTS HD) Per Sector-Carrier view
allowed starting with
22.5 us (pcs, RNC and Cell R31.0
OneBTS HD)
23.1 us (pcs, TICLI_Tx can be
OneBTS Compact) obtained via TICLI
command op:cell X,
32.5us (pcs, MCR,
asmb Y, rrh Z
OneBTS Compact)
23.1us (cellular,
OneBTS Compact)
32.5us (cellular,
MCR OneBTS
Compact)
32.5us (cellular,
MCR, OneBTS, HD)
32.5us (IMT-2000,
MCR, OneBTS
Compact)
32.5us (pcs, MCR,
OneBTS, HD)
38us (450 MHz,
OneBTS)
20us (pcs, SBCBR)
27.7us (cellular, 450,

SBCBR)
32.5us BS2400
(MCR, SBEVM, pcs,
cellular)
23.1us 700MHz
(OneBTS, UCR)
23.1us (OneBTS,
MCPA, UCR,
cellular)
32.5us (OneBTS,
MCPA, MCR, pcs,
cellular)
32.5us BS4400,
TTLNA (OneBTS,
MCR, pcs, cellular)
23.1us BS4400,
TTLNA (OneBTS,
UCR, pcs, cellular)
32.5us PCS IA
Frame (4.0B, MCR,
pcs)
0 + TICLI_Tx BTS
9234, 9228, 9222
with RRH (Cellular,
PCS, AWS)
Antenna Propagation Delay: Sector - General / 14us (Legacy RxDelay is used
Receive Delay**** SectorCarrier - General Modcell), starting with RNC/Cell
19.6 us (OneBTS), R24.
46us (OneBTS, 450 MCR MCR-A or
MHz) MCR-B
22.7us BS2400
(MCR, SBEVM, pcs, AWS band uses same
cellular) Tx/Rx delay values as
17.3us 700MHz PCS band.
(OneBTS, UCR)
19.6us (OneBTS, 4400/4401 use the
MCPA, MCR, UCR, same Tx/Rx delay
pcs, cellular) values as Mod4.0
19.6us PCS IA
Frame (4.0B, MCR, Tx/Rx delay for BS2400
pcs) for 2100 MHz is the
same as the one listed
0.7 + TICLI_Rx BTS here
9234, 9228, 9222
with RRH (Cellular) Per Sector-Carrier view
allowed starting with
2.4 + TICLI_Rx BTS RNC and Cell R31.0
9234, 9228, 9222
with RRH (PCS, TICLI_Rx can be
AWS) obtained via TICLI
command op:cell X,
asmb Y, rrh Z
Initial Probe Power Correction Sector Carrier – Access 0 dB
Factor Control / Sector - Access
Control / FxAPx - SN General -
General 2
Power Increment Step Sector - Configuration / FxAPx 8 (4 dB)
- SN General - General 2
Dormancy Timer Sector - General / FxApx – SN 10s
General - General 2
Paging Strategy Obsolete 1 Starting with R28, this
parameter is not used.
To disable RNC wide
paging, set Number of
Times to Page the Last
seen RNC to 0.
Number of Times to Page: FxApx – SN Page 2 Parameter name
The Last Active set change in R28
Number of Times to Page: FxApx – SN Page 2 Parameter name
The Last seen RNC change in R28
TM_Page_Response FxApx – SN Page 2.0s Can be increased to 5s
for default paging wake
up cycle of 5.12s
RF Load Differential (in steps FxApx – SN General – General 0.2 Starting with R32, both
of 0.01) 2 Rev0 and RevA
mobiles use traffic load
balancing algorithm
based on RSSI Rise.
Load Differential
parameter is not used
anymore. Change in
recommendation
starting with RNC R32.
This is to minimize
number of cross carrier
assignments and
thereby reduce cross
carrier FCAs.
Load Balancing Method Sector – Configuration / FxApx Number of Active Both Rev0 and RevA
– SN General – General 3 Users mobiles use RSSI Rise
based traffic load
balancing algorithm
Load Differential Sector – Configuration / FxApx 20 New in R26. Applies
– SN General – General 3 only when Number of
Active Users based
Load Balancing
algorithm is used
Rel0 RevA Loading Sector Carrier – General / 15 Used for traffic load
Differential FxApx – SN General – General balancing between
4 Rev0 and RevA
carriers. New in R29.
Border Carrier Sector Carrier - General Default value is No. Set
it to Yes if it is a Border
N/A
Carrier. 1, 2, 3, are
different carriers
Border and Non-border CellSite Configuration / FxApx Starting with R31 this
Loading Ratio – SN General – General 4 parameter governs
traffic load balancing
between border and
10
non-border carriers for
both RevA and Rev0.
See App notes 1 and
12 for more info.
Radius for Registration Sector – General / FxApx – SN Needed for Distance
Update General – General 1 based Paging. 0 means
distance based
0.25 * Area of RNC registration is OFF.
Recommendation is to
enable Distance based
Registration.
Base Station Antenna Latitude Sector - Sector
N/A
Base Station Antenna Sector - Sector

Longitude N/A
Test Carrier***** Sector Carrier - General / Yes, No. Default value

FxApx – SN General – General is No. Set it to Yes if
1 No there is a need to block
non-test mobiles from
accessing the network.
RF-Border Session Setup Sector – Access Control / Session Close

Deny FxApx – SN Sector Implementation.
Parameter name
change in R27.0.
Deny Connections in
The feature can be
Poor Conditions
disabled if EVDO
coverage is adequate
and also to minimize
impact to PTT mobiles
Session Setup Request Sector – Access Control / Parameter name
Denial: Signal Strength FxApx – SN Sector 18 (-9.0 dB) change in R27.0.
Threshold
Session Setup Request Sector – Access Control / Parameter name
Denial: Minimum Distance FxApx – SN Sector 2.5 miles change in R27.0.
Threshold
RF Loading Differential Sector – Configuration Prior to R35, Auxiliary
20 (0.2 in terms of Per Sector Control – 1
RF Loading) was used for this
functionality.
* - The recommended value of this parameter is updated starting with R28.02. The updated value
can be used for previous releases. The new recommended value assumes that the majority of the
mobiles in the market are MSM6500 and beyond. If there are still a large number of MSM5500
mobiles in the market, then this parameter can be set 6dB lower for all band classes.
** - Need to set these 3 parameters the same across all 3 sectors. Refer to Lucent Alert 05-0518.
Even though this holds true only for DBEVM, these parameters should be set the same across all
3 sectors for SBEVM unless needed to address market specific circumstances.
*** - Recommendation of Access Capsule Max Length is changed from 2 frames to 4 frames
starting with R28.02 to support Data-Over-Signaling. For existing Rev0 and RevA mobiles, there
shouldn’t be any impact since they will mostly use up to 2 frames. Recommendation of Access
Cycle Duration is changed from 64 slots to 16 slots to reduce call setup latency for Push-to-Talk
(PTT) service and also to increase access channel capacity. These settings are supported for
SBEVM only. DBEVM will still use the default settings of 2 frames and 64 slots, respectively
even with these settings enabled in the database.
**** - Starting with RNC R31 SU1 and Cell R31.00, translation parameters Transmit Antenna
Propagation Delay (TxDelay) and Receive Antenna Propagation Delay (RxDelay) will have both
the per sector view and per sector carrier view. Cell R31.00 is required for the per sector carrier
view. The range of these translation parameters is 0 to 400us for both sector and sector carrier
views. If the cell release is either R29 or R30, then continue to use spare sector-carrier translation
parameters, Auxiliary Per-Sector-Carrier Control – 1 and Auxiliary Per-Sector-Carrier
Control – 2, to allow provisioning of TxDelay and RxDelay, respectively, on a per sector-carrier

basis. The unit of TxDelay and RxDelay at both sector and sector carrier levels is in us. However,
the unit of Auxiliary Per-Sector-Carrier Control – 1 and Auxiliary Per-Sector-Carrier
Control – 2 is 1/10th us. For example, if TxDelay of 139.5us is required, then set Auxiliary Per-
Sector-Carrier Control – 1 to 1395. If Auxiliary Per-Sector-Carrier Control – 1 and
Auxiliary Per-Sector-Carrier Control – 2 are set to 0, then they are not used and the current
per-sector translation parameters are used. EVM needs to be restored / rebooted for changes in
TxDelay/RxDelay parameters to take effect either at sector or sector-carrier level. The R31 OSR
implemented the following:
If auxSectorCarrierCtrl1 = 0; set scTxdelay to -1 (blank)

If auxSectorCarrierCtrl1 > 4000; set scTxdelay to 400us.
Otherwise set scTxdelay to (auxSectorCarrierCtrl1/10).
If auxSectorCarrierCtrl2 = 0; set scRxdelay to -1 (blank)

If auxSectorCarrierCtrl2 > 4000; set scRxdelay to 400us.
Otherwise set scRxdelay to (auxSectorCarrierCtrl2/10).
***** - IS-856 RevA standard defines APersistence index 2 for test mobile. Starting with R29,
Alcatel-Lucent has updated the test carrier implementation to confirm to this new standard
change. With this change, when test carrier feature is ON, the third occurrence of APersistence
field is set to 0x3F. It is set to 0x00 when the test carrier feature is OFF. AT uses this
Apersistence parameter to compute persistence probability P, which is used for access. The test
mobiles now need to be programmed with access overload class to either 12 or 13 so that they
can access the test carrier. A mobile with access overload class set to 10 will not be able to
access test carrier with the new implementation. Access overload class (ACCOLC) is a 4-bit
value which is translated to APersistence index according to the following:
ACCOLC Apersistence index

------------ ------------------------
0–9 0
10, 11 1
12, 13 2
14, 15 3
It is important to note that system id (SID) change is accounted for test ATs via Preferred
Roaming List (PRL) if SID is set to 0 when test carrier feature is enabled.

Imer 2

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Imer 2

Încărcat de

Drepturi de autor:

Formate disponibile

Wireless Business Group

Timing, Delay, and Access Parameters

Copyright © 2012 Alcatel-Lucent

-Updated Section 7 – Multiple Carriers: Hashing and Traffic Load Balancing

Unlike 3G1x, there is no PN randomization in 1xEV. PN randomization increases the probability

Maximum number for an access probe sequence (maxprobesequence): Maximum allowable

Number of access probes (probenumstep): Maximum number of access probes an AT is

Figure 1. 1xEV Access Channel Structure

Access channel probe sequence backoff (probesequencebackoff): If the maximum allowable

If auxSectorCarrierCtrl1 = 0; set scTxdelay to -1 (blank)

If auxSectorCarrierCtrl2 = 0; set scRxdelay to -1 (blank)

Parameter Recommended Value

450 700 Cellular PCS Korea

Table 1. Recommended values of TxDelay and RxDelay

Parameter Recommended Value

Table 2. Recommended Values of Open Loop Power Adjustment

RSSI Rise Translation Value (PCS band) of Corrected Value of

Initial probe power correction factor (probeinitialadjust): Correction factor to be used by an

2.2 Access Search Window Size

Miles in air PN chips Microseconds Miles in cable

Table 3. Conversion between different units

2.3 Access Channel Slot Setup

2.4 Access Probe Power

The initial access probe power IP of the AT is defined as

2.5 Access Delay Perceived by the End User

3 1xEV Default Best-Effort Paging

Selection of a paging method depends on whether dormant AT is in suspended mode or slotted

3.1 Slotted Mode Operation

3.1.1 Paging Slot Determination for EVDO only Mode

3.1.2 Paging Slot Determination for Hybrid Mode

3.2 Location of Dormant Access Terminal

3.2.1 Subnet based Registration

3.2.2 Distance based Registration

3.3 1xEV Default Best-Effort Paging Methods

There are two different types of DBE paging methods.

3.3.1 Normal DBE Paging Method

Parameter Recommended value

3.3.2 Fast Connect DBE Paging Method

5 Test Carrier Feature

P = 2 ^ (-N/4), where N is the value of the APersistence field

ACCOLC APersistence index

6 PDSN Selection Algorithm

PDSN No. = (truncated MNID) modulo N,

7 Multiple Carriers: Hashing and Traffic Load Balancing

7.1 1xEV Mobile Hashing

7.2 Traffic Channel Selection Algorithm for Call Setup

7.3 Traffic Channel Selection Algorithm based on Originating Carrier

7.4 Traffic Channel Selection Algorithm based on RSSI Rise

RSSI Rise (dB) Translation Parameter RF Load Differential

Alcatel-Lucent doesn’t recommend a mix of Rev0/RevA carrier configuration.

7.6 Border Carrier

8 Session Close: Critical System Edge Metric Preservation Feature

Scenario Idle mode hashing Traffic Channel Load Balancing Algorithm

Table 5. Summary of Hashing and Traffic Channel Load Balancing Algorithms

9 Summary of Translation Parameters

OMC-RAN Field Label OMC-RAN GUI Page Recommended Note

Antenna Propagation Delay: Sector – General / 19.9 us (pcs) MCR MCR-A or

23.1 us (cellular, same Tx/Rx delay

27.7us (cellular, 450,

Base Station Antenna Sector - Sector

Test Carrier***** Sector Carrier - General / Yes, No. Default value

RF-Border Session Setup Sector – Access Control / Session Close

Control – 2, to allow provisioning of TxDelay and RxDelay, respectively, on a per sector-carrier