Wireless Business Group subject: CDMA 1xEV Translation Application Note #1 Timing, Delay, and Access Parameters Version

12.0 date: December 5, 2007

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 1.0 2.0 3.0 3.1 4.0 5.0 6.0 7.0 8.0 Changes Updated document for CDMA 1xEV Cell Release 1.0 Updated document for CDMA 1xEV Cell Release 2.0 Updated document for CDMA 1xEV Cell Release 20.0 Updated document for CDMA 1xEV Cell Release 20.1 Updated document for CDMA 1xEV Cell Release 21.0 Updated document for CDMA 1xEV Cell Release 22.01/22.02 Updated document for CDMA 1xEV Cell Release 23.0 Updated document for CDMA 1xEV Cell Release 24.0 Updated document for CDMA 1xEV Cell Release 25.0
-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

9.0

Updated document for CDMA 1xEV Cell Release 26.0
-Updated Section 2.1 – Transmission/Receive Antenna Propagation Delay, Open Loop Adjustment
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 © 2007 Alcatel-Lucent Unpublished and Not for Publication All rights reserved

CDMA 1xEV RF Translation Application Note #1

Version 12.0

-Updated Section 5 – Test Carrier -Updated Section 7 – Multiple Carriers: Hashing and Traffic Load Balancing -Updated Section 8 – Session Close feature

10.0

Updated document for CDMA 1xEV Cell Release 27.0
-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 – Transmission/Receive Antenna Propagation Delay -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

12.0

Updated document for CDMA 1xEV Cell Release 29.0 (RNC Release R29 SU2)
-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

Alcatel-Lucent – Proprietary See notice on first page

2

In general. and maximize access success rate. The reverse link of a CDMA 1xEV system. the demodulator must exactly match the path delay such that the PN code can be in phase with the transmitted sequence.CDMA 1xEV RF Translation Application Note #1 Version 12. minimize delay perceived by the end user. 2. delay. especially when many mobile stations are at a similar range from the base station. there are three goals in optimizing the access translation parameters: minimize interference to the existing traffic users. To this end. It accommodates the maximum possible air propagation delay (one way). allows multiple users to simultaneously share the same frequency band. there is no PN randomization in 1xEV. 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. Sector size (sectorsize): The maximum range of a cell’s desired coverage. The purpose of this document is to explain the functions of these translation parameters and to provide their recommended values. Their definition and recommended values are included below. A correct set of values of these translation parameters is required for the proper operation of a system. and access. The recommended value is 10 miles. The information on the access channel (Rev0 and Default Access Channel in RevA) is transmitted at a fixed rate of 9. The access channel consists of a pilot channel and a data channel. and Delay There are several access. 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. Unlike 3G1x. Alcatel-Lucent – Proprietary See notice on first page 3 . The demodulator needs to test many path delay hypotheses to find the best match of the path delay. and delay related translation parameters that are fundamental to the operation of a CDMA 1xEV system. Timing. which uses the CDMA scheme.1 Basic Translation Parameters that Impact Access. timing.0 1 Introduction There are several CDMA 1xEV translation parameters that impact timing. The search window (both in the base station and AT) specifies the range for the path delay hypotheses. The demodulator extracts the desired user’s signal by matching the modulated user-specific PN code.6 kbps.

1xEV Access Channel Structure Access channel probe backoff (probebackoff): If the maximum allowable number of access probes has not been reached. This is to reduce call setup latency for Push-toTalk (PTT) service and also to increase access channel capacity. The recommended value for DBEVM is still 64 slots. that is. access probe can be transmitted at a time T such that T modulo access cycle duration equals 0. DBEVM supports only one access channel element. The access cycle duration can only take on the following values: 16. This setting is supported for SBEVM only.02. either AT initiated or AN initiated. 1 frame. 64. when probe search period is shorter than the probe transmission period. It indicates how often base station needs to start a new probe search and when mobile can transmit a probe. and 128 slots. The SBEVM (CSM6800) supports multiple access channel elements (at least 8). Number of access probes (probenumstep): Maximum number of access probes an AT is allowed to transmit in a single access probe sequence.0 Maximum number for an access probe sequence (maxprobesequence): Maximum allowable number of access probe sequences for a single access attempt. Access cycle duration (accesscycleduration): It is the basic time unit of all access channel activities. SBEVM implementation allows setting of access cycle duration such that the search period is less than the probe transmission period (Preamble + Message Capsule). The recommendation was changed from 64 slots to 16 slots starting with R28. This is shown in Figure 1. On the other hand.376 ms) whereas RT is an Alcatel-Lucent – Proprietary See notice on first page 4 .CDMA 1xEV RF Translation Application Note #1 Version 12. allows access cycle duration to be shorter than access probe duration. Therefore. unlike 3G1x. access probe must be transmitted at the access probe boundary (equal to access channel slot boundary). The recommended value is 16 slots (26. the search period must be greater than or equal to transmission period.67 ms). The recommended value is 5. Hence. The recommended value is 2. The 1xEV standard. In 1xEV. 32. base station requires multiple access channel elements. Figure 1. In 3G1x. However. 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.

For DBEVM. if TxDelay of 139. then set Auxiliary Per-Sector-Carrier Control – 1 to 1395. TA is a fixed waiting time defined by the IS856 standard as 128 slots (213.0 additional random delay. Additionally. then they are not used and the current per-sector translation parameters are used. the next access probe in the next access probe sequence is transmitted after TA + RS time.67 ms) for SBEVM and 4 (426. This was corrected for the Alcatel-Lucent – Proprietary See notice on first page 5 .67ms) for DBEVM. Transmit antenna propagation delay (txdelay): The delay observed in the forward transmit path between forward link modem (FLM.44 ms) for DBEVM. Receive antenna propagation delay (rxdelay): The delay observed in the receive path between the antenna connector and the reverse link modem (RLM. Open loop power adjustment (openloopadjust): The nominal power used by an AT for initial transmission on the access channel. on a per sector-carrier basis. Auxiliary Per-Sector-Carrier Control – 1 and Auxiliary Per-Sector-Carrier Control – 2. respectively.CDMA 1xEV RF Translation Application Note #1 Version 12. The recommended values of Txdelay and Rxdelay are shown in Table 1. Access channel probe sequence backoff (probesequencebackoff): If the maximum allowable number of access probe sequences has not been reached.376 ms) whereas RS is an additional random delay. Access terminals based on MSM5500 chipset use Probe Power that is 6 dB below the expected value. this translation parameter is used by the 1xEV system for both access and handoff. RxDelay supported range up to 400us. the range of TxDelay was restricted to 62us. DBEVM) or SBEVM and the antenna connector. which ranges from 0 to probebackoff in the units of access cycle duration. EVM needs to be restored / rebooted for changes in TxDelay/RxDelay parameters to take effect either at sector or sectorcarrier level. translation parameters Transmit Antenna Propagation Delay (TxDelay) and Receive Antenna Propagation Delay (RxDelay) parameters were per sector. The value used by the AT is (–1) times the value of openloopadjust. RNC R30 will have new permanent per-sector carrier translations for TxDelay and RxDelay and will discontinue the use of these spare sector-carrier translation parameters for TxDelay and RxDelay. For example.1us. Prior to RNC R29 SU1. RNC R29 SU1 uses spare sector-carrier translation parameters. Also.5us is required. This increase in TxDelay range is only for SBEVM. to allow provisioning of TxDelay and RxDelay. it is still restricted to 62us even if the per sector-carrier translation is set to a higher value. The recommended values of this parameter are shown in Table 2. the spare sector-carrier translation also supports the increase in range of TxDelay from 62us to 400us.38ms) for SBEVM and 8 (853. Starting with Cell/RNC Release R24. The units of Auxiliary Per-Sector-Carrier Control – 1 and Auxiliary Per-Sector-Carrier Control – 2 are 0. DBEVM) or SBEVM. If Auxiliary Per-SectorCarrier Control – 1 and Auxiliary Per-Sector-Carrier Control – 2 are set to 0. which ranges from 0 to probesequencebackoff in the units of access cycle duration. The recommended value is 4 (106. The recommended value is 8 (213. The value of this translation parameter was changed starting with R24 due to increasing number of deployed access terminals based on MSM6500 chipset. The Txdelay is independent of the controller (CRC versus URCm for legacy Mod cells) used.

The new recommended value assumes that the majority of the mobiles in the market are MSM6500 and beyond.5 us 19.1us 19.7 us 14 us 38 us 46 us 700 MHz Recommended Value Cellular band 27.1 us 19. MCPA) 450 MHz 27. UCR) Rx_delay BS4400. The updated value can be used for previous releases.6 us 23. If there are still a large number of MSM5500 mobiles in the market.5us 19.5 us 22.6 us 32. MCR. SBCBR) Rx_delay (Flexent Micro/Mod Cell.6 us 35 us 22 us 32.3us 32.6 us 22. MCR. TTLNA (OneBTS.7 us 14 us 23.5 us 19. TTLNA (OneBTS.1 us 19.5 us 19.CDMA 1xEV RF Translation Application Note #1 Version 12. MCPA) Rx_delay (OneBTS.6 us 32.6 us 23.6 us PCS band 19.0 MSM6500 chipset mobiles. UCR) Tx_delay BS4400.5 us 19.7 us 14 us 27.6 us 22.6 us 32. UCR) Tx_delay (OneBTS. MCR) Rx_delay BS4400.5 us 19. MCR. The recommended value of this parameter is updated starting with R28. then this parameter can be set 6dB lower (to correct for AT’s probe power issue) for all band classes. MCR) Tx_delay BS4400.5 us 19.5 us 19. TTLNA (OneBTS. Recommended values of TxDelay and RxDelay Alcatel-Lucent – Proprietary See notice on first page 6 .5 us 19.5us 22.6 us 32.6 us Table 1. MCR. SBEVM) Tx_delay (OneBTS.6 us 32.6 us 32.9 us 14 us 20 us 14 us 23. The pre-R24 value of this translation parameter accounted for this 6 dB shortfall.1 us 17.7 us Korea band IMT-2000 32.6 us 23.1 us 19.5 us 19.5 us 19.5 us 19.6 us 32.7 us 14 us 27.5 us 19.7 us 23. UCR) Rx_delay (OneBTS. TTLNA (OneBTS.02. Parameter MCR MCR A or MCR B Tx_delay (Flexent Mod Cell) Rx_delay (Flexent Micro/Mod Cell) Tx_delay (Flexent Mod Cell.6 us 32.6 us 32. SBCBR) Tx_delay (Flexent OneBTS) Rx_delay (Flexent OneBTS) Tx_delay (Flexent OneBTS HD) Rx_delay (Flexent OneBTS HD) Tx_delay (Flexent OneBTS HD MCR) Rx_delay (Flexent OneBTS HD MCR) Tx_delay (Flexent OneBTS Compact) Rx_delay (Flexent OneBTS Compact) Tx_delay (Flexent Korea OneBTS) Rx_delay (Flexent Korea OneBTS) Tx_delay (Flexent OneBTS MCR) Rx_delay (Flexent OneBTS MCR) Tx_delay (Flexent OneBTS Compact MCR) Rx_delay (Flexent OneBTS Compact MCR) Tx_delay BS2400 (OneBTS.6 us 32.1us 19. SBEVM) Rx_delay BS2400 (OneBTS.

814 1 8 Miles in cable 0. and therefore the translation.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. The maximal cell access search window size is restricted by hardware. The recommended value is 0 dB. the following inequality for delay budget must be satisfied: 2 * sectorsize * 6.125 1 Miles in air PN chips Microseconds Miles in cable Table 3.6 (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. Note that the upper limit on air delay is the sector size. must be greater than the actual air delay at any point in the coverage area.6 has been assumed for the cable.5 PN chips 6. Miles in air 1 0. The AT uses 0. sectorsize.2288 9. The allowed values are 0 to 15.0 Parameter Recommended Value 450 MHz 700 MHz Cellular band PCS band Korea band 2 GHz Open Loop Power Adjustment 80 dB 81 dB 82 dB 81 dB 81 dB 82 dB Table 2.83 Microseconds 5.CDMA 1xEV RF Translation Application Note #1 Version 12.33 0.6663 0. A velocity factor of 0. Power increment step (powerstep): Power increment between two consecutive access probes within one access probe sequence. Table 3 shows the conversion formula between units. The optimal access search window width is Access search window width (in PN chips) = 2 * sectorsize (in miles) * 6. The recommended value is 8 (4 dB). The allowed values are -16 to 15 dB in steps of 1 dB. Therefore under any circumstances. Recommended Values of Open Loop Power Adjustment 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.1017 0. 2.5 dB times the value set in the database.55 1 1. Conversion between different units Note that there is an upper bound associated with the cell access search window.1876 1.6 < 512 chips Alcatel-Lucent – Proprietary See notice on first page (2) 7 . For convenience.1527 0.

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. the route update message is always included. The recommended value for DBEVM is 2 frames. Therefore. Table 4 shows the relationship between access search window size and access preamble.3 Access Channel Slot Setup The access channel slot structure for CDMA 1xEV is similar to that of CDMA IS-95A/B/2000. Starting with R28. The sizes of access preamble and message capsule are controlled by the following two translation parameters. The access channel structure is shown in Figure 1. This can result in improvement on access delay (probe delay and sequence delay etc. It is important to note that ALPHA sector values of Access Channel Parameters (Access Preamble Length. the preamble must be greater than the time that the base station needs to do all the hypotheses tests in the access search window. these parameters should be set the same across all 3 sectors for SBEVM unless needed to address market specific circumstances. For existing Rev0 and RevA mobiles. The capsule length should be large enough to contain at least two access channel messages because. then all access channel activities will speed up proportionally. Optimal Access Channel Preamble Length Access capsule max length (capsulelengthmax): The maximum access message capsule length that will be used for the access message. The access channel cycle is the basic time unit of all access channel activities.).0 2. the recommended value of this parameter is 2 frames. 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. for any access channel message. for each access channel slot. Ensure that these 3 parameters are set the same across all 3 sectors of the cell. there shouldn’t be any impact since they will mostly use up to 2 frames. 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. The access channel probe consists of two parts: access channel preamble and access channel message capsule. For normal operation (sector size of 10 miles or less).02 cell. recommendation of Access Capsule Max Length is changed from 2 frames to 4 frames for SBEVM to support Data-Over-Signaling. and Access Capsule Max Length) dictate the values of these parameters for BETA and GAMMA sectors. Alcatel-Lucent – Proprietary See notice on first page 8 . If the access channel cycle duration can be minimized. Access Cycle Duration.CDMA 1xEV RF Translation Application Note #1 Version 12. Even though this holds true only for DBEVM.

and even the dynamics of pilot change (i.e..0 2. (3) where openloopadjust and probeinitialadjust are defined in Section 2. usage of excessive initial access probe power does not improve the access success rate significantly.. On the other hand. if a sudden burst arrival of access occurs (e. 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. etc.e.1. 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. but instead creates more interference to the existing traffic users. only the pilot channel is transmitted. Since the chance of this sudden burst arrival is rare compared to the chance of dynamics of pilot change. During the preamble transmission. Alcatel-Lucent – Proprietary See notice on first page 9 .g. sports events. the total power transmitted by the AT during access preamble transmission and access message transmission is same. etc.CDMA 1xEV RF Translation Application Note #1 Version 12. The initial access probe power IP of the AT is defined as IP = .). Open-loop estimation is used to determine the power needed by the AT. traffic events. The delay between access probes and between access sequences are the primary contributing factors to the net delay perceived by the end user. disaster. 2.mean received power (dBm) + openloopadjust + probeinitialadjust. the number of simultaneous access users (or indirectly the access arrival rate). this instantaneous increase in arrival rate will create large interference to the whole system. The delay between probes and between sequences is basically a trade-off. less chance for change in the dominant pilot between probes and sequences). A higher AT transmit power will allow easier access. but will create interference to existing users. An access probe consists of preamble followed by message.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. On the other hand. both the pilot and the data channel are transmitted.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. the instantaneous reverse link power level at the base station. During the message transmission.. The power of the subsequent probe is powerstep dB higher than the previous probe within an access probe sequence. the idea is to use shorter delay between access probes and access sequences. A lower transmit power will lengthen the duration of the access process. fast shadow fading plus user mobility). The number of probes and sequences needed for a successful access attempt is determined by the probe power. Usage of a longer delay between probes and between sequences will somewhat reduce the interference in such a situation. However.

12. This results in less processing at access terminal. Alcatel-Lucent – Proprietary See notice on first page 10 . 3.CDMA 1xEV RF Translation Application Note #1 Version 12. The access terminal transitions to slotted mode from suspended mode after expiration of suspend timer. 3. Both AN and AT determine this Sync CCC using a hash function defined by 1xEV standard. Hence. there are several new paging strategies supported with introduction of RNC Grouping. AT monitors Sync CCC continuously for a period of time defined by suspend timer at the access terminal. the 1xEV sleep period duration is 5. which is transmitted every 426.0 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. The DBE paging uses synchronous control channel to transmit page messages. This section only covers the default besteffort (DBE) paging strategy. Paging strategy with RNC Grouping enabled is discussed in translation application note #13. AT monitors only selected synchronous control channel cycle (Sync CCC).67ms. also known as Session Seed. QoS paging including Distance based paging is documented in translation application note #12.1. RATI is a 32-bit pseudo-random number which is communicated to the AN by the AT during initial setup of 1xEV session. In suspended mode. In slotted mode operation. and Distance based Paging. QoS Paging. In addition to DBE paging. which is defined by the standard and is not configurable. 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. The access terminal transitions to monitor state from sleep state once every 5. 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. is used as an input to this hash function.12s (one Sync CCC out of every 12 Sync CCC). Random Access Terminal Identifier (RATI). conceptually.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. which reduces power consumption thereby.1 Slotted Mode Operation The 1xEV idle state protocol supports periodic network monitoring by the access terminal. increasing battery life.

3. information including pilots reported Alcatel-Lucent – Proprietary 11 See notice on first page . all cells on a single RNC will have same color code.2 Location of Dormant Access Terminal In 1xEV.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. The above original definition of subnet has changed with introduction of RNC Grouping feature. Hybrid AT knows its 3G1x sleep cycle based on IMSI.0 3.1. and its own programmed slot cycle value.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. 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. Knowledge at the 1xEV Radio Network Controller (RNC) of dormant AT’s location will reduce the probability of RNC wide paging. Color code is associated with the subnet to which Unicast Access Terminal Identifier (UATI) belongs. The subnet area is restricted to coverage area spanned by cells on a single RNC and is not currently configurable. This process is also called Inter-RNC Idle/Dormant Handoff. After AT registration. With RNC Grouping enabled and subnet mask of 64. After registration.2. Hybrid AT will always negotiate its 1xEV sleep cycle using Preferred Control Channel Cycle (PCCC) attribute. maximum slot cycle index value transmitted OTA.2. For example. AT will not re-register even when it crosses RNC boundaries within the RNC Group. 3. The access terminal re-registers with access network (after crossing RNC boundaries) when it notices change in color code.1 Subnet based Registration A subnet can be viewed as geographic coverage area spanned by a group of cells that use same color code. information including Pilots reported in RouteUpdate message and new controlling RNC is stored at access network and is used for future paging purpose. there is no centralized database such as HLR/VLR as in 3G1x to keep track of the access terminal whereabouts. 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. Please refer to translation application note #13 for more information.CDMA 1xEV RF Translation Application Note #1 Version 12. The access terminal proposes PCCC value such that it will not conflict with its 3G1x tune away. Distance is computed using fields Latitude and Longitude of the SectorParameters message from last accessed base station and the one AT is currently monitoring.

The current recommendation is 0 (turn off distance based registration). England) is 0 degree Longitude. For South Latitude of 65:45:36S. the translation parameters Base Station Antenna Latitude and Base Station Antenna Longitude need to be appropriately populated in the database. Additionally. The Prime Meridian (Greenwich. Longitudes have values from -180 to 180 with -180 corresponding to 180degree West Longitude and 180 corresponding to 180-degree East Longitude. That is.3. North Latitude of 40:43:28N would be entered as 40 degrees. for 28 seconds. 45 minutes. 3600 seconds in the EMS GUI database. This form of registration can be used if a RNC coverage area is quite large. 3. For example. enter it as -65 for degrees. set the translation parameter Radius for Registration Update (angular distance) to a non-zero value. enter it as -65 for degrees. To enable distance based registration.CDMA 1xEV RF Translation Application Note #1 Version 12. This paging method is implemented via a two-step process: 1) Access network sends page message on all sectors last accessed by access terminal. 3. 5800 seconds. East Longitude of 74:24:58E would be entered as 74 degrees. 43 minutes. The current recommendation is to enable distance based registration with RNC R28 SU2 and beyond. Starting with R28. 24 minutes. 2800 seconds. The equator is 0 degree Latitude. For example.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. 45 minutes. Starting with R28.3 1xEV Default Best-Effort Paging Methods There are two different types of DBE paging methods. enter 2800. and 90 corresponding to 90-degree North Latitude (North Pole). 3600 seconds in the EMS GUI database. Below is the information on how to populate Latitude and Longitude information in the database. Hence.0 in RouteUpdate message is stored at access network and is used for future paging purpose. Latitudes have values from -90 to 90 with -90 corresponding to 90-degree South Latitude (South Pole). Please note that seconds are multiplied by 100 when entered in the EMS GUI. page all cells within the same RNC Alcatel-Lucent – Proprietary See notice on first page 12 . page the last known active set 2) If there is no response from the access terminal after executing step 1). For West Longitude of 65:45:36W.

Starting with RNC R28. However. 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). RNC will only give AT 1s to respond to the page before the repage timer expires. AN will keep paging the mobile. When the timer expires RNC sends another page attempt and restart the timer. the repage timer implementation has changed. this will slow down the page response time. When Dormancy timer expires. there are two translation parameters associated with normal paging method.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. In other words in R28 RNC estimates AT’s next wake up time and starts the repage timer accordingly. Prior to R28.0 Starting with R28. The new repage timer mechanism may change the page attempt distribution (compared to pre-R28) depending on the repage timer value. RNC then starts a repage timer. If AN receives the page response from AT (AN-Initiated Connection Request). 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 AT doesn't wake up for next 4 seconds. The recommended values for both of these parameters are 2. the R-P connection remains intact. If it is set to a higher value (> 5). This process continues till all the page attempts are exhausted. 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. the repage timer was hard coded to 5 seconds from the time RNC sends the message to the cell. The repage timer starts from the time the page message is sent over the air. 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. only cells under the RNC governing the AT session (UATI) will be paged when the second step is executed. Alcatel-Lucent – Proprietary See notice on first page 13 .3. Prior to RNC R28. there are a total of 4 page attempts for each page request. RNC sends a page as soon as it receives data from the PDSN. For example. but the call setup fails. AT may include suspend timer in the ConnectionClose message. However. With the above recommendations. Additionally.CDMA 1xEV RF Translation Application Note #1 Version 12. If all the page attempts fail. 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 translation parameter Paging Strategy is obsolete starting with R28. Parameter Paging Strategy Number of Times to Page the Last Active Set Number of Times to Page the Last Seen RNC Recommended value Obsolete Starting with R28 2 2 It is important to note that if the last known active set contained Pilots from different RNCs. it will give AT more time to respond by extending the paging cycle time. the data packets that generated the page request are discarded. This parameter governs the tradeoff between page success rate and page response time. 3. The recommended value for this translation is 2s.

That is. to restrict 1xEV access. With only test mobiles allowed. the mobile IP address is still the same. Mobiles based on MSM6500 and MSM6800 chipsets. AT uses this persistence parameter to compute persistence probability P in the following manner: P = 2 ^ (-N/4). If X < P. Alcatel-Lucent – Proprietary See notice on first page 14 . The recommended value of this parameter is 10 seconds. It is set to 0x00 when the test carrier feature is OFF. In 1xEV. Mobiles based on MSM5500 chipset support non-zero suspend timer. Dormancy Timer. AT will not be able to send access probes on 1xEV system. The access terminal cannot move a significant distance within 5s (suspend timer) and hence.CDMA 1xEV RF Translation Application Note #1 Version 12. it is very unlikely that AT’s last active set will change. do not support non-zero suspend timer. the physical channel is teared down. there are up to four mobile classes. the optimization process can be carried out in a well-controlled manner and service will not be provided to the end-users prematurely. 5 Test Carrier Feature The Test Carrier feature is introduced in 1xEV R23.0 If the AN has data to send to a dormant AT while suspend timer is running. the persistence test will be considered successful and AT will be able to send the access probes. Hybrid ATs will access 3G1x system subsequently. The end-to-end channel is still active. 4 Dormancy State In CDMA 1xEV packet switched data. Fast Connect method is never invoked for these mobiles. in most cases. Hence. where N is the value of the APersistence field =0 if N = 0x3F AT generates a random number X between 0 and 1. the first occurrence of APersistence field is set to 0x3F. The test mobiles can be programmed to use any other class while the system is being integrated and optimized. APersistence field in the AccessParameterMessage. A non-test mode AT will be able to perform active mode handoff to a test carrier enabled sector. The test carrier feature uses persistence parameter. that is. There are no translation parameters associated with this paging method. Currently. all ATs are using the default class of '0'. the physical channel goes through the routine setup procedure (without the end user knowledge). When the user requests additional data transfer. when the traffic channel is idle during a data call for time defined by a translation parameter. it will initiate fast connect procedure using AT’s last known active set. the call enters a dormancy state. This would help reduce overall call blocking due to system resources. Access network directly sends TrafficChannelAssignment message thereby eliminating the need to exchange page and ConnectionRequest messages. This feature enables a 1xEV carrier access to be restricted to a special class of mobiles. Otherwise. When test carrier feature is ON. The suspend timer is set to 5s at AT.

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. the network will send the SID as zero over the air only for the sectors that are in test-carrier mode. 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 R26. Starting with RNC R27 SU2 and Cell R27. 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). 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). This SID is same for both the test-carrier and the commercial carrier. If a non-test carrier is not provisioned in the PRL. which wakes up once a minute and attempt to access the network but fails. In a multi-carrier cell with test carrier enabled. Active handoffs from test carrier cells to non-test carrier cells are allowed. These mobiles have a built-in algorithm. access network knows that this is a test mobile and will allow handoffs in to a test carrier cell. When the SID is set to 0. With this change. AlcatelLucent has updated the test carrier implementation to confirm to this new standard change. If this flag is enabled. The workaround solution is for the network to set the SID to 0 for test-carrier. AT will access 3G1x instead. when test carrier feature is ON. It is important to note that this feature only works when both RNC and Cell loads are at least running R23 loads. This is to alleviate the rapid mobile battery drain issue when mobiles are trying to acquire 1xEV system on a test carrier enabled cell. The default value of this parameter is No. It is set to 0x00 when the test carrier feature is OFF. A new flag (SID override) has been added to the Service Node configuration database.01. 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 a non-test AT is idling on a sector-carrier. which is later on marked as test carrier. the third occurrence of APersistence field is set to 0x3F. 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. access network will allow the handoffs to a test carrier enabled cell. Starting with R29. The test carrier feature is controlled via the translation parameter Test Carrier. there is an enhancement to the test carrier feature implementation. AT uses this Apersistence parameter Alcatel-Lucent – Proprietary See notice on first page 15 . (This enhancement is also supported for RNC R26 SU3 CFT H and Cell R26. If a call originated on a test carrier cell. If the call originated on a test carrier. These continuous periodic attempts to access the network in test carrier mode are causing these mobiles to lose its power rapidly.CDMA 1xEV RF Translation Application Note #1 Version 12. IS-856 RevA standard defines APersistence index 2 for test mobile.0 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.02). RNC will block all handoffs to a test carrier enabled cell if the call originated on a non-test carrier cell.

In this case. For IMSI based algorithm. 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. 15 Apersistence index -----------------------0 1 2 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. RNC uses either RATI based algorithm or IMSI based algorithm to select one of the PDSNs. 1xEV system will select the same PDSN as underlying 3G1x system. Alcatel-Lucent – Proprietary See notice on first page 16 . 6 PDSN Selection Algorithm Lucent 1xEV system allows provisioning of multiple PDSNs at the RNC. Currently. traffic load balancing between carriers. N is the number of PDSNs provisioned in the database. MNID is input to the standard defined PDSN selection algorithm. MNID = 999999 + last 9 digits of RATI.0. Following sections discuss the basic concepts of hashing across carriers. Lucent 1xEV system supports cells with multiple carriers. Access overload class (ACCOLC) is a 4-bit value which is translated to APersistence index according to the following: ACCOLC -----------0–9 10.CDMA 1xEV RF Translation Application Note #1 Version 12. 11 12. MNID = IMSI. If RAN is OFF. If RAN authentication is disabled. which is used for access. 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. 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. 7 Multiple Carriers: Hashing and Traffic Load Balancing Starting with cell release R26. where (truncated MNID) is defined to be the least significant 4 digits of the MNID taken as a decimal value. A mobile with access overload class set to 10 will not be able to access test carrier with the new implementation. the PCF shall determine which PDSN to use for a particular MS by the following: PDSN No. If IMSI is available. The standard defined PDSN selection algorithm is: For initial PDSN assignment and for PDSN reselection. 13 14. RAN authentication needs to be enabled. MNID is 15 digits in decimal value. If the RAN authentication is ON. = (truncated MNID) modulo N. border carrier and related translation parameters.0 to compute persistence probability P.

Load Balancing Method. Whenever the number of channels listed within the SectorParameters message changes.4 of IS-856. Additionally. 2) Non-test mobiles should be prevented from attempting to access the test carrier. This parameter allows service providers to select a particular traffic channel selection algorithm. depending on the number of carriers available in each sector. it also helps balance Control Channel and Access Channel occupancy among carriers which leads to better overall access performance.2 Traffic Channel Selection Algorithm for Call Setup The main purpose of this algorithm is to try to balance traffic load across multiple carriers. we ensure that once the mobile tunes to a non-test carrier it will not attempt to access a test carrier 7. 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. As idle mobile moves around the network from sector to sector. If the connection request is received on a test carrier then AT will only be assigned to a test carrier. Call processing maintains two separate channel lists for each sector: non-test carrier channel list and test carrier channel list. Similarly if the connection request is received on a non-test carrier then AT will only be assigned to a non-test carrier.CDMA 1xEV RF Translation Application Note #1 Version 12. This helps balance traffic load across carriers reducing the number of cross-carrier traffic channel assignments. Unlike CDMA. the AT selects a channel to monitor based on the hash algorithm defined in section 10. and the test carrier channel list will not contain any non-test carriers. The non-test carrier channel list will not contain any test carriers.0 7. If the channel list for the test carrier contains non-test carriers. 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. the idle AT will re-execute the hash algorithm. it may monitor different channels in each sector. Originating Carrier and Number of Active Users. When multiple carriers are present in a sector. The inputs to hash algorithm are Random Access Terminal Identifier (RATI) and number of channels listed in SectorParameters message. By not listing any of the test carriers in the channel list of a non-test carrier. Alcatel-Lucent – Proprietary See notice on first page 17 .1 1xEV Mobile Hashing Mobile hashing distributes mobiles uniformly across multi-carriers. The traffic channel selection algorithms based on Originating Carrier and Number of Active Users and are described below. There is a per sector translation parameter. which has two allowable values. the mobile could hash to a non-test carrier.

Alcatel-Lucent – Proprietary See notice on first page 18 . Otherwise. The translation parameter.. If all of the differences are less than the value of this translation parameter. Load Differential.4 Traffic Channel Selection Algorithm based on Number of Active Users This algorithm balances number of users across carriers based on the number of active users on each carrier. This algorithm is applied to both session setup connection requests and user initiated connection requests. Otherwise. Otherwise. If all fails. If another carrier couldn’t be selected. If another carrier couldn’t be selected. then the originating carrier is selected. For each carrier in the sector. the call will be assigned carrier F1 for traffic. then after Tforcerelease timer has expired. This algorithm is applied to both session setup connection requests and user initiated connection requests.3 Traffic Channel Selection Algorithm based on Originating Carrier With this algorithm. if a mobile originate on carrier F1. the connection request will be denied. This is useful for a multi-carrier system when each carrier may have different RF coverage footprint. the recommended value of Load Differential is changed from 10 to 20 to minimize cross-carrier assignments thereby reducing call setup failure rate due to RF mismatch between carriers. a mobile will be assigned a carrier based on the origination carrier. Starting with R28.CDMA 1xEV RF Translation Application Note #1 Version 12. and the number of active users on the originating sector carrier minus the Load Differential is less than the number of active users on each of the other carriers in that sector. Call Processing computes the difference between the number of active users on the originating sector carrier and the other carriers in that sector. Maximum Number of Users Supported Rev0/RevA. AT is assigned to another (least loaded) sector carrier. then after Tforcerelease timer has expired. i. if all the active users are carrying out data transfer. AT is assigned resources on the originating carrier. call processing will select another (least loaded) carrier if possible. is used in the traffic channel selection algorithm and the preference is given to the carrier that the AT originally accessed. and if there are active users that are idling (not carrying out data transfer and dormancy timer hasn’t expired yet). the call is assigned to the least loaded carrier. This traffic channel selection algorithm is supported for following configurations and scenarios: 1) All carriers are only Rev0 capable. the connection request will be denied. the longest idle user on the originating carrier will be forced into dormancy and the new call will be assigned to the originating carrier. and if there are active users that are idling (not carrying out data transfer and dormancy timer hasn’t expired yet). Call processing will select the originating carrier for traffic channel assignment if the number of active users does not exceed the value of the translation parameter Maximum Number of Users Supported for Rev0.0 7. If the number of active users on the originating sector carrier is less than the translation parameter.e. the longest idle user on the originating carrier will be forced into dormancy and the new call will be assigned to the originating carrier. 7. This traffic channel selection algorithm is only supported when all carriers are only Rev0 capable. If all fails.

0 2) All carriers are RevA capable. 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 connection request will be denied. Rev0 calls are assigned to the Rev0 carrier and RevA calls are assigned to the Rev A carrier. The tunable parameter can be updated via an OMP script. AT’s personality is known. If all the carriers are RevA capable. if there are active users that are idling (not carrying out data transfer and dormancy timer hasn’t expired yet). Load Balancing Method. 3) A mix of Rev0 and RevA carriers. An idle mobile will hash to one of carriers based on its RATI. this results in significant number of cross-carrier assignments. The same holds true if Rev0 carrier reached Maximum Number of Users Supported for Rev0 limit. the longest idle user on the RevA carrier will be forced into dormancy and the new call will be assigned to the originating carrier. 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. Starting with R29. then this algorithm is used regardless of the translation parameter. Additionally. traffic channel load balancing algorithm for RevA calls is based on reverse link RSSI Rise. Cross-carrier assignments may lead to a high call setup failure rate due to RF mismatch between the carriers. this is controlled via a tunable parameter called Rel0RevAloadDifferential threshold. A Rev0 mobile may hash to a RevA carrier. The current recommended value for this parameter is 15. the traffic channel selection algorithm is implemented as follows: During session setup phase. Alcatel-Lucent – Proprietary See notice on first page 19 . then after Tforcerelease timer has expired. The negative value for this threshold implies carrier selection preference is given to Rev0 carrier for Rev0 mobiles originating on RevA carrier. Refer to the R28 SU1 release letter on the use of this script. This algorithm is applied to both session setup connection requests and user initiated connection requests. If all fails. This load balancing algorithm allows RevA carrier to carry Rev0 traffic. 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. then the Rev0 calls originating on RevA carrier will be cross-assigned to the Rev0 carrier. Once this threshold is exceeded. Pre-RNC R29. till the maximum number of users limit is reached. both Rev0 and RevA calls will be assigned to Rev 0 carrier if possible (Rev0 carrier has resources). 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. Rev0 or RevA. This algorithm is documented in translation application note #12. that is. Prior to R28 SU1. The valid range of this parameter is -59 to 59. Alcatel-Lucent doesn’t recommend a mix of Rev0/RevA carrier configuration. In presence of current limited RevA mobile population. setting. Otherwise. and then will be assigned to the Rev0 carrier based on this implementation during user initiated connection request.CDMA 1xEV RF Translation Application Note #1 Version 12. Call processing uses both Number of Active Users and Load Differential to assign connection request to either one of the carriers. When QoS is enabled. Starting with R28 SU1. this is controlled via a new translation parameter called Rel0 RevA Loading Differential. the AT’s personality (capability) is not known. Once the session is configured. this implementation leads to in-efficient use of RevA carrier capacity. This is only true when QoS is not enabled.

the tunable parameter essentially defines percentage of maximum allowed users active on non-border carrier after which the border and non-border carriers will start sharing equal traffic. The traffic channel load balancing algorithm is enhanced starting with R28 SU2 where calls are assigned to border carrier based on tunable parameter hdrSNSpare6. via IFHO. the area where 1xEV is no longer supported as AT moves further from the cells. The script should work for R28. The first N connections will be served on the continuing carrier F1. There will be a translation parameter in R31 that will control this algorithm. unless there are no other carriers available in that sector. embedded within a larger 1xEV coverage area with different frequencies (continuing/common carriers). The translation parameter. Also. The subsequent connections will be alternatively assigned between border (F2) and non-border carrier (F1). calls will not be assigned to border carrier till non-border carrier reaches Maximum Number of Users Supported for Rev0/RevA limit. The recommended value for this parameter is 20. also known as discontinuing carrier. The number N is defined by two parameters: Maximum number of Users Supported for Rev A and tunable parameter hdrSNSpare6. there is no advantage in marking these sectors as border sector carriers. This is to fully utilize the air interface resources within those sectors as efficiently as possible. it prevents access attempts on that carrier. Border Carrier. N = (Maximum number of Users Supported for Rev A) * (hdrSNSpare6 / 100) Based on the above. The border sector carrier designation should only be used within the boundaries of 1xEV coverage area. Since there is no Inter-Frequency Handoff (IFHO) at the 1xEV coverage boundary. but where other 1xEV carriers are available.0 7. is defined as a sector carrier where the frequency of that carrier is no longer supported as AT moves away from that sector. Carriers that are marked as a border sector carrier are excluded from the channel lists that are calculated. should not be marked as border sector carriers. That is. Field data shows that access attempts are more susceptible to failures on the border carrier. By excluding the border sector carrier from the channel list. This parameter can be updated via OMP script named borderNonBorderRatioSetup. If a carrier is marked as border carrier. and not along the edge of the 1xEV coverage. designates whether a sector carrier is a border sector carrier or not. immediately following call setup. Alcatel-Lucent – Proprietary See notice on first page 20 .CDMA 1xEV RF Translation Application Note #1 Version 12. R29 and R30.5 Border Carrier A border sector carrier. current implementation (up to R28 SU1) of traffic channel load balancing algorithm doesn’t assign any calls to the border carrier until resources on all nonborder carriers are exhausted. calls may be handed down to another carrier. The cells along the edge of the 1xEV coverage area.

8 Session Close: Critical System Edge Metric Preservation Feature Session Close feature. It monitors only 3G1x during this time. also known as Critical System Edge Metric Preservation feature. The software issue will be addressed in R29 RNC SU2 CFT C and beyond. allows service providers an option to deny Session Setup requests from mobiles in poor RF / nondesignated 1xEV coverage areas. Users. AT will monitor 3G1x for about 11 minutes. It only impacts ATs that are undergoing session setup in poor RF conditions at the edge of the service area. are not impacted. traffic channel load balancing algorithm between Border and Non-Border carriers is not working for QoS (ReservationOnRequest bundled with RouteUpdate and ConnectionRequest messages) calls. either Best-Effort (Default Flow Packet Application or MultiFlow Packet Application) or QoS (ReservationOnRequest bundled with RouteUpdate and ConnectionRequest messages) will use traffic load balancing based on RSSI Rise. RevA calls are assigned only to the Originating carrier. 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. AT will avoid the carrier it acquired 1xEV and not the hashed carrier where it received SessionClose message. hybrid AT avoids monitoring 1xEV system for a period of about11 minutes. Mobiles are very persistent in trying to establish 1xEV session since that’s what they are designed for. In case of multiple 1xEVcarriers. These attempts use up Reverse Link resources often taking them away from other ATs that have a better chance of establishing a data connection. with valid 1xEV session. This will be addressed in a future release. RevA calls may not be balanced between carriers. This load balancing algorithm is described in translation application note #12. That is. Battery life of these ATs is also most often needlessly diminished. the RSSI Rise based traffic load balancing algorithm is not working due to software issue. QoS calls will be assigned only to the continuing Non-Border carrier. Many ATs are autonomously attempting to start up new sessions in extremely poor RF conditions outside of the nominal service area. 2) When multiple carriers are RevA QoS enabled. When the network denies several successive 3 to 4 session setup attempts. when QoS is enabled on both carriers. However. Table 5 summarizes both hashing and traffic channel load balancing algorithms for different configurations and scenarios. After all 1xEV carriers are avoided. traffic load balancing for both Rev0 and RevA calls is based on Number of Active Users. 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). This implies that if QoS is enabled either in R28 or R29. Alcatel-Lucent – Proprietary 21 See notice on first page .0 Important Notes: 1) When multiple carriers are RevA enabled but QoS is not supported. RevA calls. Currently. then Rev0 calls use traffic load balancing based on Number of Active Users.CDMA 1xEV RF Translation Application Note #1 Version 12. 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.

will activate the feature. used by the feature.CDMA 1xEV RF Translation Application Note #1 Version 12.0 There are three parameters associated with this feature. Scenario Idle mode hashing (Default Idle State Protocol) Traffic Channel Load Balancing Algorithm F1. respectively. respectively. Setting the translation parameter. The recommended values of these parameters are –9 dB and 2. are defined by the translation parameters. The RF and Distance thresholds. 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). RF-Border Session Setup Deny ( pre-R27 RF-Border Session Setup Connection Deny) to Deny Connections in Poor Conditions (recommended value). Summary of Hashing and Traffic Channel Load Balancing Algorithms Alcatel-Lucent – Proprietary See notice on first page 22 . RevA carrier allowed to carry Rev0 traffic via tunable parameter (R28) Rel0RevAloadDifferential and translation parameter (R29) Rel0 RevA Loading Differential RevA calls assigned to RevA carrier Mixed Rev0/RevA carriers Number of Active Users R28 SU1 Table 5.5 miles. F2 is Border carrier Session Setup Connection Setup Originating Carrier or Number of Active Users Number of Active Users Based on RATI Always to the NonBorder carrier (F1) Number of Active Users Rev0 – Number of Active Users RevA – RSSI Rise (described in translation application note # 12) Pre R28 SU1 Rev0 AT assigned to Rev0 carrier. The names of these translation parameters were changed starting with R27. F2 are NonBorder carriers Two Rev 0 carriers Two Rev A carriers QoS disabled Two RevA carriers QoS enabled F1 is NonBorder carrier. RevA AT assigned to RevA carrier.

General section 2 Sectors .Access Control / Service Node .Access Control / Service Node .7 us (450 MHz) 23.Configuration / Service Access Probe Sequence Node .CDMA 1xEV RF Translation Application Note #1 Version 12.1 us (cellular.Access Control / Service Node .General section 2 Sectors . OneBTS.Configuration / Service Node .General section 2 Sectors .General section 2 2 82 dB (PCS) Max Tx Pwr per Carrier 81 dB (Cellular) PCS – 16W Cellular – 20W 81 dB (Korea) Korea – 20W 80 dB (450 MHz) 450 MHz – 26W 81 dB (700 MHz) 700 MHz – 20W 82 dB (2 GHz) 2 GHz – 16W 0 dB Initial Probe Power Correction Factor Power Increment Step Transmit Antenna Propagation Delay**** Sectors . *** Access Preamble Length** Access Channel Probe Backoff Access Channel Probe Sequence Backoff Number of Access Probes EMS GUI Page Sectors .General section 2 Recommended Note Values 10 miles 16 slots 4 frames 2 frames 4 Units of Access Cycle Duration 8 Units of Access Cycle Duration 5 Maximum Number for an Sectors .Configuration / Service Node .5us (cellular.1 us (pcs. MCR) 23.5us (pcs.Configuration / Service Node .Access Control / Service Node .General section 2 Open Loop Power Adjustment* Sectors .General section 2 Sectors .General / Service Node .General section 2 Sectors .0 9 Summary of Translation Parameters EMS Field Label Sector Size Access Cycle Duration**.1 us (Korea. OneBTS.General section 2 Sectors .9 us (pcs) MCR MCR-A or MCR-B 27. MCR) 23.Configuration / Service Node .*** Access Capsule Max Length**. OneBTS) Alcatel-Lucent – Proprietary See notice on first page 23 .General section 2 Sectors .General section 2 Sectors – General 8 (4 dB) 19. OneBTS) 32.Access Control / Service Node .7 us (cellular) 27. OneBTS) 32.

cellular) Receive Antenna Propagation Delay**** Sectors . HD) 38us (450 MHz. with RNC/Cell R24.5us BS2400 (MCR. cellular) 23.0us (OneBTS.7us BS2400 (MCR. SBEVM. OneBTS HD) 23. OneBTS Compact) 32.5us BS4400. 450.1 us (pcs.5us (pcs. pcs.0 22. pcs. SBCBR) 27. OneBTS Compact) 32.5 us (cellular. UCR.5us (IMT-2000. MCR. OneBTS Compact) 32.5us (pcs. MCR.5us (cellular. OneBTS) 20us (pcs. 19. pcs.1us 700MHz (OneBTS. TTLNA (OneBTS. OneBTS Compact) 23. OneBTS. SBCBR) 32.CDMA 1xEV RF Translation Application Note #1 Version 12.1us (cellular. MCR MCR-A or 46us (OneBTS. TTLNA (OneBTS.5us (cellular. cellular) 17. cellular) 23. OneBTS.0us (OneBTS. MCPA. MCR. MCR. cellular) 14us (Legacy RxDelay is used starting Modcell). 450 MCR-B MHz) 22. MCR. UCR) 22. SBEVM.7us (cellular.6 us (OneBTS). MCR. pcs.General Alcatel-Lucent – Proprietary See notice on first page 24 . UCR) 35.5 us (pcs. OneBTS HD) 22. MCPA.3us 700MHz (OneBTS. MCR OneBTS Compact) 32.1us BS4400. cellular) 32. HD) 32. MCR.

Alcatel-Lucent – Proprietary See notice on first page 25 .General section 3 Load Differential Sectors – Configuration / Service Node .General / Service Node . New in R29.CDMA 1xEV RF Translation Application Note #1 Version 12.General section 2 Service Node – Paging Parameters 10s 1 Starting with R28. No. Default value is No.Base Station Antenna Longitude Sector Carriers . 3.General Radius for Registration Update Service Node . To disable RNC wide paging. Default value is No. set Number of Times to Page the Last seen RNC to 0. 20 New in R26. Applies only when Number of Active Users based Load Balancing algorithm is used 15 Used for traffic load balancing between Rev0 and RevA carriers.General section 3 Rel0 RevA Loading Differential Service Node II-QoS/Sector Carrier – General Border Carrier Sector Carriers .Base Station Antenna Latitude Sectors . 2 Parameter name change in R28 2 Parameter name change in R28 2.1 seconds) Load Balancing Method Sectors – Configuration / Service Node . 1.General section 1 N/A Yes.0 Dormancy Timer Paging Strategy Sectors . Recommendation is to enable Distance based Registration. this parameter is not used. Set it to Yes if there No is a need to block nontest mobiles from accessing the network. are different carriers Needed for Distance based Paging. 0 means distance based N/A registration is OFF.0s Number of Times to Page Service Node – Paging the Last Active set Parameters Number of Times to Page Service Node – Paging the Last seen RNC Parameters Minimum Time to wait for Service Node – Paging a Page or DoS response Parameters (in steps of 0. N/A Base Station Antenna Latitude Base Station Antenna Longitude Test Carrier***** Sectors .General section 1 Number of Active Only method of choice Users for Traffic Load Balancing across Multiple Carriers when both carriers are RevA capable.General / Service Node . Set it to Yes if it is a Border N/A Carrier. 2.

1us. there shouldn’t be any impact since they will mostly use up to 2 frames.5 miles in R27. If there are still a large number of MSM5500 mobiles in the market. Auxiliary Per-Sector-Carrier Control – 1 and Auxiliary Per-Sector-Carrier Control – 2. ** . * . if TxDelay of 139.The recommended value of this parameter is updated starting with R28. Even though this holds true only for DBEVM. it is still restricted to 62us even if the per sector-carrier translation is set to a higher value. If Auxiliary Per-SectorCarrier Control – 1 and Auxiliary Per-Sector-Carrier Control – 2 are set to 0. This increase in TxDelay range is only for SBEVM. Parameter name change 2.0. Alcatel-Lucent – Proprietary See notice on first page 26 . Also. the spare sector-carrier translation also supports the increase in range of TxDelay from 62us to 400us. RNC R29 SU1 uses spare sector-carrier translation parameters.0 RF-Border Session Setup Sectors – Access Control / Deny Service Node – Pilot Values Signal Strength Threshold Sectors – Pilot Values / Service Node – Pilot Values for Session Setup Request Denial Minimum Distance Threshold for Session Setup Request Denial Sectors – Pilot Values / Service Node – Pilot Values Session Close Deny Connections in Implementation. then they are not used and the current per-sector translation parameters are used. respectively even with these settings enabled in the database.Need to set these 3 parameters the same across all 3 sectors. Parameter name change 18 (-9.02. DBEVM will still use the default settings of 2 frames and 64 slots. For existing Rev0 and RevA mobiles. For example. to allow provisioning of TxDelay and RxDelay. For DBEVM. The updated value can be used for previous releases.CDMA 1xEV RF Translation Application Note #1 Version 12. RNC R30 will have new permanent per-sector carrier translations for TxDelay and RxDelay and will discontinue the use of these spare sector-carrier translation parameters for TxDelay and RxDelay. The units of Auxiliary Per-Sector-Carrier Control – 1 and Auxiliary Per-Sector-Carrier Control – 2 are 0. these parameters should be set the same across all 3 sectors for SBEVM unless needed to address market specific circumstances. **** . EVM needs to be restored / rebooted for changes in TxDelay/RxDelay parameters to take effect either at sector or sectorcarrier level.Prior to RNC R29 SU1.0 dB) in R27. Refer to Lucent Alert 05-0518. the range of TxDelay was restricted to 62us. RxDelay supported range up to 400us. The new recommended value assumes that the majority of the mobiles in the market are MSM6500 and beyond.0. 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. Poor Conditions Parameter name change in R27. respectively. Additionally.5us is required.0. These settings are supported for SBEVM only. translation parameters Transmit Antenna Propagation Delay (TxDelay) and Receive Antenna Propagation Delay (RxDelay) parameters were per sector. then set Auxiliary Per-Sector-Carrier Control – 1 to 1395. then this parameter can be set 6dB lower for all band classes.02 to support Data-Over-Signaling. *** .Recommendation of Access Capsule Max Length is changed from 2 frames to 4 frames starting with R28. on a per sector-carrier basis.

11 12. the third occurrence of APersistence field is set to 0x3F. which is used for access. Starting with R29. Access overload class (ACCOLC) is a 4-bit value which is translated to APersistence index according to the following: ACCOLC -----------0–9 10. 13 14. 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. With this change. Alcatel-Lucent has updated the test carrier implementation to confirm to this new standard change.CDMA 1xEV RF Translation Application Note #1 Version 12.IS-856 RevA standard defines APersistence index 2 for test mobile. It is set to 0x00 when the test carrier feature is OFF. when test carrier feature is ON. 15 Apersistence index -----------------------0 1 2 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. A mobile with access overload class set to 10 will not be able to access test carrier with the new implementation.0 ***** . AT uses this Apersistence parameter to compute persistence probability P. Alcatel-Lucent – Proprietary See notice on first page 27 .