1x rtt traffic_management_part_ii

NORTEL NETWORKS CONFIDENTIAL

1xRTT TRAFFIC MANAGEMENT (Part 2)Multi-Carrier Traffic Allocation (MCTA)

Prepared by Quang D. PhamCDMA RF Engineering

Version 1.0April 2002

NORTEL NETWORKS CONFIDENTIAL Page 3

1xRTT TRAFFIC MANAGEMENT

MULTI-CARRIER TRAFFIC ALLOCATION

MCTA – NBSS 10.1


The Multi-Carrier Traffic Allocation (MCTA) feature can dynamically balance the traffic across multiple RF carriers served by the same system

MCTA operates at call setup and supports up to 3 RF carriers per sector

MCTA mechanism can be used for both IS95 and IS2000 systems

MCTA can be Co-Functional with Hashing or GSR.

MCTA works with:

a single Metro Cell BTS

Metro Cell – Metro Cell BTS combination

Multi-Carrier Traffic Allocation (MCTA) Overview


Capacity Estimate:

It is the estimated number of calls that can be carried on a specific sector. It can be calculated as follows:

— EFLC (Excess Forward Link Capacity): The total available power in the carrier.

— In 1xRTT network, The EFLC is adjusted according to the radio configuration of the BTS (i.e. Radio Configstate (CellCapability), CCEM or XCEM)

MCTA Definitions

____

___

____

:_

=

availableCodesWalshofnumber

availableCEofnumber

availablelinksRFofnumber

ofSmallesttimateCapacityEs


MCTA (Capacity) Threshold (Datafilled in the Advancedsector(PilotDatabase) MO)

It is the number that is being used to determine the “Relative Capacity” available in the sector in which a call will be setup. This parameter represents the minimum value in which Excess Forward Links Capacity (EFLC) in units of calls should drop below before selecting the next preferred frequency.

MCTA (Frequency) Priority (Datafilled in the Advancedsector(PilotDatabase) MO)

It is the factor that used to determine the order in which the carriers should be analyzed (A lower value means the carrier has a higher priority).

Relative Capacity:

It is used by the MCTA algorithm when selecting a carrier. It is calculated as follows:

Relative Capacity = Capacity Estimate - MCTA (Capacity)Threshold

MCTA Definitions (cont.)


MCTA Algorithm

During a new call or hard hand-off setup, the SBS Selector sends a ‘capacity request’ message to each BTS serving the sector on which the call attempt was made configured as a part of the MCTA cell site.

Each BTS responds back with its Capacity Estimate in the ‘Capacity Response’ message.

The SBS Controller uses the Carrier Determination Algorithm (CDA) to select the best carrier using a combination of Frequency Priority, Capacity Threshold and the Capacity Estimate response retrieved from the ‘Capacity Response’ Message.

MCTA Priority, MCTA Threshold and Frequency Priority, Capacity Threshold will determine how MCTA operates

Multi-Carrier Traffic Allocation (MCTA)


Multi-Carrier Traffic Allocation (MCTA)

A single Metro Cell with 1 DCG - the MCTA decision takes place at the BTS level

A single Metro Cell with 2 DCGs, the MCTA decision takes place at the SBS level.

A Metro Cell – Metro Cell System - the MCTA decision takes place at the SBS level.

Where does the MCTA decision take place?


Sector A: MCTA threshold MCTA priority

Sector B: MCTA threshold MCTA priority

Sector G: MCTA threshold MCTA priority




AdvancedFA1Frequency F1


BTSCall Processing

Report Capacity Estimate for F1 on Sector A


MCBTS CDA selects the best carrier per sector basis

SBS Pilot Data Base

Sector (n) Capacity ThresholdSector (n) Frequency Priority . . Sector (x) Capacity ThresholdSector (x) Frequency Priority

Report Capacity Estimate for the selected frequency on Sector A

SBS CDA makes a final decision, a frequency is selected

Assume that the mobile is in the idle mode on this sector and originates a call

Single Metro Cell with 1 DCG










BTSCall Processing


Reports Capacity Estimate for F2 on Sector A

MCBTS CDA selects the best carrier on a per sector basis









BTSCall Processing


MCBTS CDA selects the best carrier on a per sector basis

SBS Pilot Data Base


Reports Capacity Estimate for the selected frequency on Sector A


SBS CDA makes a final decision A frequency is selected

DCG1 (MC 1)

DCG2 (MC 1)

Single Metro Cell with 2 DCGs Assume that the mobile is in the idle mode on this sector and originates a call










BTSCall Processing



MCBTS CDA selected the best carrier on a per sector basis









BTSCall Processing


MCBTS CDA selected the best carrier on a per sector basis

SBS Pilot Data Base




SBS CDA makes a final MCTA decision,a frequency is selected

DCG1 (MC1)

DCG1 (MC2)

Metro Cell – Metro CellAssume that the mobile is in the idle mode on this sector and originates a call


Flow Chart of CDA Algorithm

Find the preferred frequency ( F ) using the frequency priority entries

Calculate Capacity Estimate for Each blossomed frequency in the sector

is Capacity Estimate of (F)

> MCTA threshold

of (F)

Select frequency ( F )

Find the next preferred frequency using the priority entries

Are there any more

frequencies available?

Select the frequency with the largest

Capacity Estimate

Y

N

Capacity Estimate Number of calls that can be carried on a specific sector

MCTA Threshold Minimum number of calls to admit to a high priority frequency before selecting the next priority frequency

Y

N

CDA Calculated Relative Capacity = Capacity Estimate – MCTA Threshold


Frequency F1 F2 F3

Frequency Priority (datafill) 0 0 0

Capacity Threshold (datafill) 64 64 64

Calculated Capacity Estimate 6 8 4

Capacity Estimate > Capacity Threshold No No No

Calculated Relative Capacity -58 -56 -60

�

MCTA algorithm

Example 1: Even Traffic Distribution


Frequency F1 F2 F3




Capacity Estimate > Capacity Threshold No Yes -

Calculated Relative Capacity -44 3 -

�

MCTA algorithm

Example 2: Sequential Traffic Distribution


Frequency F1 F2 F3




Capacity Estimate > Capacity Threshold No Yes -

Calculated Relative Capacity -44 -3 -5

�

MCTA algorithm

Example 3: Sequential Traffic Distribution (10.1 BTS CDA)


MCTA Requirement Settings

The Cell IDs for multiple carriers of the same site location need to be the same

All the Co-located MCTA BTS(s) must belong to the same BSC

Set the “MCTATimeout” parameter to a value that allows enough time for the “Capacity Response” message from all BTSs to be received at the SBS. Recommended value is 100 ms

The “frqvct” field (cdma_frequency_vector field) needs to be datafilled with the appropriate frequency in the CDMAPART table for each of the MCTA sectors. Once done, the MCTA OMs will be collected on per frequency basis


MCTA at Carrier Boundaries

F3F2F1

F2F1F1

Datafill: Even / Sequential

F1: FrequencyPriority = 0 CapacityThreshold = 3



Datafill: Sequential


F2: Frequency Priority = 1 CapacityThreshold = 64

Datafill: N/A

Datafill: Even




F3F2F1

Moving away from core of a network

Margin


1xRTT Multi-Carrier Traffic Allocation MCTA

The MCTA feature in 1xRTT works in the same way as in an IS95 system. It distributes CDMA traffic over the various carriers that have the same CELL ID in a given sector

MCTA can support up to 3 carriers

In a 1xRTT system, MCTA also considers the Radio Configuration (RC) and user type (voice and or data). In the other words, MCTA now evaluates its estimates for each carrier based on the desired RC and the call type

The RC for a voice and data user will affect the results for the number of total traffic channels, total forward power and the total available Walsh codes

Hardware RequirementMetro Cell BTS (CCEM, XCEM)

Software RequirementsNBSS10.X or greater Mobiles with MOB_P_REV >= 6


1xRTT Multi-Carrier Traffic Allocation (MCTA) (Cont)

Datafill RequirementsMTX CDMAPART TABLE (Cont) In order to activate MCTA, the Cell IDs for multiple carriers of the same

site need to be the same. So, in MTX CDMAPART table, the CELL ID (SUBCELL) in the MTX CDMACELL table needs to be modified accordingly

The FRQVCT field contains two sub-fields, Band Class and Channel Number, that need to be datafilled

ExampleSUBCELL PILOTPN XLANUM TLDNPNUM CNIPBLK TRANSL FRQVCT SIDNID

1X 138 1 1 N NAXL 214 NPRT (1 425) (1 675) $ N


1xRTT Multi-Carrier Traffic Allocation (MCTA)

Datafill Requirements (Cont)

MTX CDMAPART TABLE

Subcell: Uniquely identifies a sector• Range: Word32 Recommend Value: User Specific

Pilotpn: Pilot Pn for the MCTA sector• Range: 0..512 Recommend Value: User Specific

Freqvct: CDMA Frequency Vector

Band Class Number: Band Class – Sub-field of Frqvct• Range: 0, 1 Recommend Value: 0 – 800MHz; 1- 1900MHz

Channel Number: Channel Number – Sub-field of Frqvct• Range: 0..1199 Recommend Value: User Specific




AdvancedSector MO Sector Cell ID: Uniquely identifies a BTS

• Range: 0..65523 Recommend Value: User Specific

MCTA Threshold: The minimum value in which Excess Forward Links Capacity (EFCL) in units of calls should drop below before selecting the next preferred frequency.

• Range: 0..64 (NBSS10.x) Recommend Value: User Specific

MCTA Priority: It is the factor that used to determine the order in which the carriers should be analyzed (A lower value means the carrier has a higher preference).


MaxVoiceResources: defines upper limit of percentage of BTS resources (forward link power and Walsh codes) used on voice calls


MaxDataResources: defines upper limit of percentage of BTS resources (forward link power and Walsh codes) used on 3G data calls





AdvancedSector MO (Cont) MaxDataFchResources: controls number of 3G data resources on fundamental

traffic channel vs. supplemental channel• Range: 0..100 Recommend Value: User Specific

AdvancedFA MO RadioConfigState: Identifies radio configuration and calls supported by the

carrier - Voice (2G and 3G) and Data (data only or mixed)• Range: Voice_2G; Voice 2G/3G; Data_3G; Mixed; Mixed and RRM

Recommend Value: User Specific

PilotDataBase MO ExtendedBaseID: Uniquely identifies a sector

• Range: Word32 Recommend Value: User Specific

Capacity Threshold: The minimum value in which Excess Forward Links Capacity (EFCL) in units of calls should drop below before selecting the next preferred frequency.





PilotDatabase MO (Cont) Frequency Priority: It is the factor that used to determine the order in which

the carriers should be analyzed (A lower value means the carrier has a higher priority).


CellCapability: Define the sector service capability • Range: Voice_2G; Voice 2G/3G; Data_3G; Mixed; Mixed and RRM

Recommend Value: User Specific

Note: The CellCapability (datafilled in PDB) and the RadioConfigState (datafilled in AdvancedFA MO) are being used to define the sector capability of handling various types of call services, so they should match in the datafill.


BSMCI Table – Metro Subsystem


BSMCI Table – PDB SUBSYSTEM


CDF Editor


RFO – Drive test data


RFO – Drive test data



Limitation on resources that can be considered by MCTA based on desired RC for the call and user typeNote: MCTA is configurable on a per-sector basis

RCData User

FCHPhysical

resources FCH Forward Power Walsh Codes

1 or 2 FALSECCEM or

XCEM

Portion of FCH forward power allocatedfor voice only which is controlled by theparameter MaxVoiceResources

Portion of Walsh codes allocated for voice only which is controlled by theparameter MaxVoiceResources

3+ FALSE XCEM only

Portion of FCH forward power allocatedfor voice only which is controlled by theparameter MaxVoiceResources

Portion of Walsh codes allocated for voice only which is controlled by theparameter MaxVoiceResources

3+ TRUE XCEM only

Portion of FCH forward power allocatedfor FCH data only which is controlled by the parameters MaxDataResources and MaxDataFCHResources

Portion of Walsh codes allocated for FCH data only which is controlled by theparameters MaxVoiceResources andMaxDataFCHResources


IS95AB/IS2000 Messaging

There is no messaging directly involved with this functionality. The MCTA functionality is implemented through Carrier Determination Algorithm (CDA) at both the BTS and SBS level. The call origination message on the access channel and the channel assignment message on the paging channel are the messages that are related to MCTA

Procedure to turn this function ON/OFF

If the Multi-Carrier site has the same CELL ID among all carriers and all carriers of this site are on the same BSC, the MCTA functionality is automatically ON for this site.

By properly datafilling the MCTA (Capacity) Threshold and MCTA (Frequency) Priority at the AdvancedSector MO (Pilot Database table), MCTA is able to distribute calls among the carriers during the access state

In addition to 1xRTT voice and data service distribution, the following attributes need to be datafilled accomplish this task.

“RadioConfigState” datafilled at the AdvanceFA MO, “MaxVoiceResources”, MaxDataResources and MaxDataFCHResources datafilled at the AdvanceSector MO and CellCapability at Pilot Database MO



Message Logging

The following attributes need to be checked at the mobile log mask

Access Channel Message

Paging Channel Message

Fwd Traffic Channel Message

Rev Traffic Channel Message

How to verify this functionality:

In order to verify that the calls are directed to their correct carrier according to their RC types, mobile logging is needed for this verification

Users can verify the CDMA channel that has been assigned for this call from the channel assignment message

1xRTT Multi-Carrier Traffic Allocation (Cont)



Multi-Carrier Traffic Allocation

MCTA – NBSS 10.1

Deployment Considerations


1xRTT Multi-Carrier Traffic Allocation (MCTA)1. Radio Configuration Downgrades

Radio configuration downgrades happen when there are no RC3+ physical resource to support the call on all carriers in the Metrocell. The capacity estimate will be based on resources for an RC1/2 voice call, and the capacity estimate is marked as a downgrade.

In the capacity response message, going back to the SBS controller, the downgrade field must be set to true when the capacity estimate has been downgraded

The resource requests for the FCH(s) can have downgrades in the radio configurations

A downgrade in the RC can occur for one of the following reasons:

The operations, administration, and maintenance (OAM) attribute RC4_Preferred is set to true indicating that RC4 is preferred over RC3 (RC3 redirected to RC4)

There are no physical resources for the specified RC. If there is no forward power or Walsh codes available, the FCH RC will not be downgraded since any attempt will result in failure

The RadioConfigState CFDS attribute is set to Voice_2G



1. Radio Configuration Downgrades (Cont)



2. Multi-Carrier Configuration



3. Carrier Configurations impact on MCTA

Case 1: Radio Configuration State for F1 : Voice_2G Radio Configuration State for F2 : Voice_2G

Having MCTA functionality turned on between these two carriers will not have any impact:

2G Voice calls can be placed by MCTA on either F1 or F2 as long resources are available



3. Carrier Configurations impact on MCTA (Cont)

Case 2: Radio Configuration State for F1 : Voice_2G Radio Configuration State for F2 : Data_3G

Having MCTA functionality turned on between these two carriers will have the following Impact:

It will not provide any capacity gain because RC3+ data calls are only placed by MCTA on F2 if resources are available

The RC1/2 voice calls are only placed on F1 if resources are available

If a 3G mobile latched onto the paging channel of F2 and attempts to make a voice call, MCTA would setup the voice call attempt on F1.

The RC3+ voice call attempt will be downgraded to RC1/2 voice call if resources are available




Case 3: Radio Configuration State for F1 : Voice_2G Radio Configuration State for F2 : Voice_2G_3G


RC3+ voice calls are placed only on carrier F2 as long as XCEM resources are available on F2 and F2 is not running out of forward power and Walsh codes

When carrier F2 runs out of XCEM resources but not out of forward power and Walsh codes, RC3+ voice calls are downgraded to RC1/2 and can be placed by MCTA on either F1 or F2 (It’s recommended to have only XCEMs for F2 to avoid needless RC downgrades)

When carrier F2 runs out of forward power and Walsh codes, RC3+ voice calls are downgraded to RC1/2 and can be placed by MCTA only on F1 if the resources are available

RC1/2 calls can be placed by MCTA on either F1 or F2 as long as resources are available


1xRTT Multi-Carrier Traffic Allocation (MCTA)3. Carrier Configurations impact on MCTA (Cont)

Case 4: Radio Configuration State for F1 : Voice_2G Radio Configuration State for F2 : Mixed or Mixed_and_RRM


RC3+ voice calls are placed only on carrier F2 as long as XCEM resources, forward power and Walsh code portions are available for voice

When carrier F2 runs out of XCEM resources but not out of forward power and Walsh codes, RC3+ voice calls are downgraded to RC1/2 and can be placed by MCTA on either F1 or F2 (It’s recommended to have only XCEM for F2 to avoid needless RC downgrades)

When carrier F2 runs out of forward power and Walsh codes portion allocated for voice, RC3+ voice calls are downgraded to RC1/2 and can be placed by MCTA only if F1 resources are available

RC1/2 calls can be placed by MCTA on either F1 or F2 as long as resources are available

Note: It is recommend to datafill F1 with a higher Frequency Priority than F2




Case 5: Radio Configuration State for F1 : Voice_2G_3G Radio Configuration State for F2 : Voice_2G_3G


2G and 3G voice calls can be placed by MCTA on either F1 or F2 as long asresources are available

When one carrier runs out of XCEM resources before it runs out of forwardpower and Walsh codes, that carrier can no longer be considered by MCTAfor RC3+ voice calls until the same happens with the other carrier

When both carriers run out of XCEM resources, RC3+ voice calls get downgraded to RC1/2, and get placed on either F1 or F2

Note: It is recommended to have only XCEM for F1 and F2 to avoid RC downgrades




Case 6: Radio Configuration State for F1 : Voice_2G_3G Radio Configuration State for F2 : Data_3G

Having MCTA functionality turned on between these two carriers will have the following impact:

MCTA will not provide any capacity gain because RC3+ data calls are only placed on F2 if resources are available, and voice calls are only placed

on F1 if resources are available

When these 2 carriers are co-located, they should be assigned the same CELL ID due to the following reasons:

A 3G mobile which gets on the paging channel of F2 and attempts to make a voice call, will be redirected by MCTA resources to set up the voice call attempt on F1 A 3G mobile which gets on the paging channel of F1 and attemptsto make a data call, will be redirected by MCTA resources to set up thedata call attempt on F2




Case 7: Radio Configuration State for F1 : Voice_2G_3G Radio Configuration State for F2 : Mixed or Mixed_and_RRM


RC3+ data calls are placed only on carrier F2 as long as XCEM resources, forward power and Walsh code portions are available for data

RC3+ voice calls can be placed by MCTA on either carrier F1 or F2 as long as XCEM resources are available and both carriers are not running out of forward power and Walsh codes portions allocated for voice

RC1/2 calls can be placed by MCTA on either F1 or F2 as long as resources (XCEM, CCEM) are available and both carriers are not running out of forward power and Walsh codes portion allocated for voice

Note: It is recommended to have only XCEM cards for F1 and F2 to avoid RC downgrades for 3G voice calls and needless blocks of 3G data calls on F2 due to the lack of XCEM. It is also recommended to datafill F1 with higher Frequency Priority than F2




Case 8: Radio Configuration State for F1 : Data_3G Radio Configuration State for F2 : Data_3G


3G data calls can be placed by MCTA on either F1 or F2 as long asresources are available


1xRTT Multi-Carrier Traffic Allocation (MCTA)3. Carrier Configurations impact on MCTA (Cont)

Case 9: Radio Configuration State for F1 : Data_3G Radio Configuration State for F2 : Mixed or Mixed_and_RRM


2G voice calls can only be placed by MCTA on carrier F2 as long as XCEM or CCEM resources are available and F2 is not running out of forward power and Walsh codes portions allocated for voice

3G voice calls can only be placed by MCTA on carrier F2 as long as XCEM resources are available and F2 is not running out of forward power and Walsh codes portions allocated for voice

RC3+ data calls can be placed by MCTA on either F1 or F2 as long as resources are available

Note: It is recommend to datafill F1 with a higher Frequency Priority than F2 so that all 3G data calls go to F1 first until F1 is fully loaded. This way 2G and 3G voice calls are not blocked unnecessarily




Case 10: Radio Configuration State for F1 : Mixed or Mixed_and_RRM Radio Configuration State for F2 : Mixed or Mixed_and_RRM


2G and 3G voice calls as well as 3G data calls can be placed by MCTA on either F1 or F2 as long as resources are available

Note: It is recommend to have only XCEM for F1 and F2 to avoid RC downgrades for 3G voicecalls and needless blocks of 3G data calls due to the lack of XCEM



Multi-Carrier Traffic Allocation

(MCTA Retain Loading – NBSS 10.3)


Prior to 10.3 Load - MCTA AlgorithmSBS CDA

Responsible for choosing between different carriers on a BTS sector basis when allocating resources for a call

For equal high priority carriers, the SBS CDA carrier selection is based on the first response received with positive relative capacity that supports the radio configuration requested by the mobiles

When all the carriers have a negative or zero Relative Capacity, the SBS CDA selects the carrier with the largest Capacity Estimate

10.3 Load - MCTA Algorithm

SBS CDA Enhancement Responsible for choosing between different carriers on a BTS sector basis when allocating resources for a call

For equal high priority carriers, the SBS CDA is enhanced to wait for all the BTSs to respond before making a decision within the predefined CDA timer “MCTA time out” in SBSC MO (Default value is 100 msec). After responses from all equal priority carriers are received, the enhanced CDA algorithm at SBS processes the carriers based on priority, capacity and type of radio resources available for the call. If 2 or more carriers have equal priority, the CDA selects the carrier with the highest positive Relative Capacity that supports the Radio Configuration requested by the mobile.

When all the carriers have a negative or zero Relative Capacity, the SBS CDA selects the carrier with the largest Capacity Estimate

NBSS 10.3 – SBS CDA vs SBS CDA Enhancement


Prior to 10.3 Load - MCTA AlgorithmMCBTS CDA

Responsible for choosing between different Carriers on a per sector basis

For equal high priority carriers, the last carrier initialized is the first carrier to be used if it has positive Relative Capacity, that supports the Radio Configuration requested by mobiles. If not, the MCBTS CDA continues with the next carrier in the order of last initialized until it finds a carrier with positive Relative Capacity

When all the carriers have a negative Relative Capacity, the MCBTS CDA selects the carrier with the least negative Relative Capacity

10.3 Load - MCTA Algorithm

MCBTS CDA Enhancement Responsible for choosing between different Carriers on a per sector basis

For equal high priority carriers, the MCBTS CDA calculates Relative Capacity from all the carriers with the same Cell ID and will select the carrier with the highest positive Relative Capacity that supports the Radio Configuration requested by mobile

When all the carriers have a negative or zero Relative Capacity, the MCBTS CDA selects the carrier with the the largest Capacity Estimate

NBSS 10.3 – MCBTS CDA vs MCBTS CDA Enhancement


CDA With Retain Loading (NBSS 10.3)

CDA with Retain Loading

With Retain Loading turned on, the CDA will retain the call setup (Origination, Termination, or Hard Handoff) on the same carrier until this carrier’s Relative Capacity is less than or equal to zero

Once the originating carrier (with retain loading on) has its Relative Capacity less than or equal to 0, the next carrier is considered based on Frequency Priority/MCTA Priority and Capacity Threshold/MCTA Threshold for a call setup


CDA With Retain Loading – NBSS 10.3 (Cont)

CDA with Retain Loading (Cont)

With CDA retain loading turned on, the call type (2G, 3G voice and/or data), resources available (XCEM/CCEM, forward power, Walsh codes) and datafill (CellCapability and RadioConfigState) are also taken into consideration for the determination on which carrier is selected


MCTA Retain Loading Datafill parameters (NBSS 10.3)

MCTAAlgorithm is a new parameter introduced to the existing PDBRecord of the PilotDataBase and SystemPilotDataBase MO for controlling the Retain Loading ON/OFF capability. This attribute can have 2 values:

MCTA_ONLY

MCTA_WITH_RETAIN_LOAD

When the MCTAAlgorithm parameter is datafilled with the value “MCTA_ONLY”, only the Enhanced CDA algorithm functionality is active (No Retain Loading)

When the MCTAAlgorithm parameter is datafilled with the value “MCTA_WITH_RETAIN_LOAD”, the CDA with retain loading is active and the Enhanced CDA is also on

MCTAAlgorithm can be updated via the NCF file with the corresponding parameter MCTA_ALGORITHM. The valid enumerations for this parameter are “mcta_only” and “mcta_with_retain_loading”. CDF Editor can also be used to turn this function ON/OFF

The MCTAAlgorithm parameter field will display in each PDBRecord in the BSM GUI, CLI, and BSMCI User Interfaces after migration to the 10.3 release


MCTA Retain Loading (NBSS 10.3) – Rules for Deploying with Retain Loading ON

The MCTA Threshold in Advanced Sector MO and the Capacity Threshold in PDB Record of the Pilot Data Base should be set between 0 and 5

It is suggested that MCTA with Retain Loading on should be deployed across a cluster or a network that has a BSC with all ESEL cards.

Each carrier should have a paging channel in order to get the benefit of this feature (MCTA with retain loading on)


MCTA Retain Loading - (NBSS 10.3): ExampleMCTA with Retain Loading on versus Priority Setting

• Assume that mobile is idle on F1 and originates Call

• Call will be set up on F1 even though the MCTAPriority and Frequency Priority of F1 are set to 1and MCTA Priority and Frequency Priority of F2 is set to 0

• This call is only route to F2 only if Relative Capacity of F1 is less than or equal 0 or F1’s MCTA Algorithm is set to MCTA_ONLY


MCTA Retain Loading – Feature Restrictions and Limitations (NBSS 10.3)

The Retain Loading and Enhanced CDA functionality is only supported on the ESEL card

Retain Loading functionality is settable. It can be ON or OFF on per carrier-sector basis

The Enhanced CDA is automatically employed upon Subsystem (SBS and MCBTS) Upgrade. The Enhanced CDA functionality is not optional (i.e. MCTA_ONLY is a default value for the MCTAAlgorithm)

The Retain Loading functionality deployment across the customer’s network relies on the existing NCF and BSMCI User interfaces to turn ON/OFF of the Retain Loading functionality

This feature introduces no new OM and no changes to logging


References

1. Document - 1xRTT Traffic Management, Core RF Engineering, September 26, 2001.

2. TIA/EIA– “IS2000.5-A”, Chapter 5, Version 1.0, 2001

3. TIA/EIA– “IS95-B”, Version 1.0, 2000

4. PowerPoint – “CDMA Traffic Allocation”, John Alomari, September, 2000.

5. NTP – “CDMA 3G Data and Capacity Solutions – RF Optimization Guideline”, NBSS10.1, April 2001 (NTP 411-2133-004).

6. NTP - 3G Data and Capacity Solutions Planning Guide, NBSS10.1 (NTP 411-2133- 117).

7. NTP - CDMA MTX Planning Guide, (NTP 411-2133-130).

Date post:	16-Jul-2015
Category:	Engineering
Upload:	phuoc-phuoc
View:	109 times
Download:	3 times