1x rtt traffic_management_part_i

NORTEL NETWORKS CONFIDENTIAL
1xRTT TRAFFIC MANAGEMENT
Prepared by Quang D. Pham
CDMA RF Engineering
Version 1.0
April 2002

NORTEL NETWORKS CONFIDENTIAL Page 3
• PART 1
Introduction IS95 vs 1xRTT Traffic Management
1xRTT Traffic management during System Acquisition/Initialization stage using
the Sync Channel Message
1xRTT Traffic Management in Idle Mode
Using Channel List Message (CLM) and Extend Channel List Message
(ECLM) in conjunction with Hashing function
Using Global Services Redirection Message (GSR) and Extend Global
Services Redirection Message (EGSR)
• PART 2 (will be covered at a later date)
1xRTT Traffic Management during the Access State using Multi-Carrier Traffic
Allocation (MCTA)
1xRTT Traffic Management during the Access State using Retain Loading
Multi-Carrier Traffic Allocation (MCTA Retain Loading – 10.3 Load)
1xRTT Traffic Management Agenda

IS95 & 1xRTT Traffic Management Overview
In a IS95 network, traffic can be
balanced across the carriers when
the mobiles are either in the idle
mode or during call set up
Idle mode traffic balance can be
achieved either using IS95 CDMA
Channel List in conjunction with
Hashing function or Global Service
Redirection
The balancing traffic during call
setup can be done using Multi-
carrier Traffic Allocation (MCTA
feature)
In a IS2000 network, traffic
management supports 2G and 3G
mobile distribution among the 2G
and/or 3G capable carriers either in
the idle mode or during call set up
System Acquisition/Initialization
stage using Sync Channel Message
Idle mode traffic balance can be
achieved either using IS2000 CDMA
Channel List/Extend CDMA Channel
List in conjunction with Hashing
function or Global Service
Redirection/Extend Global Service
Redirection
The balancing of traffic during call
setup can be done using Multi-
carrier Traffic Allocation (MCTA
feature)

1xRTT Traffic Management
The goal of 1xRTT Idle mode traffic management is to make efficient use of 1xRTT
resources
The capabilities of a carrier are determined by datafill, software and hardware
resources
Supports the following types of carriers:
IS-95 Voice only
1xRTT Voice only
1xRTT Voice/Data
1xRTT Data only
IS-95/1xRTT Voice/Data
1xRTT CDMA products support three types of Idle mode traffic management
mechanisms. In compliance with IS-95/IS2000 standard each traffic management
mechanism works at different stages, such as system acquisition, idle state and
access state

1xRTT TRAFFIC MANAGEMENT AT THE IDLE MODE

1xRTT Traffic Management During The Initial Systems
Acquisition Stage Using Sync Channel Message
At the initial system acquisition stage, 2G and 3G mobiles can be directed to their
extendedtworks/Carriers by using IS-2000 “Sync Channel Message” in conjunction
with existing datafill MOB_P_REV at Mobile stations and MIN_REV/P_REV at the base
stations
Interaction with mobile stations
• Mobiles with MOB_P_REV >= 6 read and tune to EXT_CDMA_FREQ
• Mobiles with MOB_P_REV < 6 read and tune to CDMA_FREQ
Datafilling 2G (using CDMA_FREQ) and 3G (using EXT_CDMA_FREQ) BTS’s
• 2G Only BTS:
- CDMA_FREQ=2G only CH; EXT_CDMA_FREQ=3G only CH
• 3G Only BTS:
- CDMA_FREQ=2G only CH; EXT_CDMA_FREQ=3G only CH
• 2G/3G BTS:
- CDMA_FREQ=2G/3G CH; EXT_CDMA_FREQ=2G/3G CH

1xRTT Traffic Management During The Initial Systems
Acquisition Stage Using Sync Channel Message (Cont)
Hardware Requirement
Metrocell BTS (Legacy BTS(s) are not capable of supporting IS-2000
messaging)
Mobile’s with MOB_P_REV >= 6
Software Requirement
NBSS10.X or greater

1xRTT Traffic Management During The Initial System
Datafill Requirement
AdvancedSector MO
 CDMA_FREQ: Broadcasted on the SYNC channel message that indicates the
CDMA channel that contains the primary paging channel for 2G or 2G/3G
combined carriers
• Range: 0-2047 Recommend Value: Customer Specific
 EXT _CDMA_FREQ: Broadcasted on the SYNC channel message that indicates
the CDMA channel that contains the primary paging channel for 3G or 2G/3G
combined carriers
• Range: 0-2047 Recommend Value: Customer Specific
BTSCallProcessing MO
 P_REV: BTS protocol revision
• Range: 1..6 Recommend Value: 1-1900 MHz; 3-800 MHz
5-IS95B; 6- 1xRTT
 MIN_P_REV: Minimum BTS protocol revision
• Range: 1..6 Recommend Value: 1-1900 MHz; 3-800 MHz
5-IS95B; 6- 1xRTT

BSMCI Tables – Metro Subsystem

1xRTT Sync Channel Message Summary
SYNC
All 3G mobiles
(MOB_P_REV>= 6)
All 3G mobiles
(MOB_P_REV>= 6)
if CDMA_FREQ is datafilled the same
Frequency as EXT_CDMA_FREQ
All 2G mobiles
(MOB_P_REV< 6)
CDMA_FREQ
EXT_CDMA_FREQ

IS95-IS2000 Messages involved
IS95: CDMA Sync Channel Messages (SCHM) on the sync channel
IS2000: CDMA Sync Channel Message (SCHM) on the sync channel
Procedure to turn ON/OFF
There is no ON/OFF switch for this functionality
By properly datafilling the CDMA_FREQ and EXT_CDMA_FREQ, the Sync
channel message will broadcast the corresponding attributes on its message
and the functionality will automatically be activated

How to Verify this functionality
Case 1: Direct Mobile to acquire 2G or 3G segregated carriers
1. Quick Verification
Assume the testing area has 2G or 3G supported segregated carrier BTS(s)
Power down the 2G or 3G mobiles
When powering up, the 2G mobiles will read the “CDMA_FREQ” that
contains the 2G primary paging channel broadcasted on the Sync channel
message and the 3G mobiles will read the “EXT_CDMA_FREQ” that contains
the 3G primary paging channel broadcasted on the Sync channel message
2. Diagnostic Verification
Perform mobile logging and capture the sync channel message by powering
down/up the mobile during logging or during the origination/termination of the
call
Check “CDMA_FREQ” (2G carrier that contain the 2G primary paging
channel) and “EXT_CDMA_FREQ” (3G carrier that contains the 3G primary
paging channel) in the Sync channel message and make sure that the CDMA
channel in these attributes contains the correct value

Case 2: Direct the Mobile to acquire 2G/3G combined carrier
Assume the testing area has 2G/3G combined carrier BTS(s)
Power down the 2G and 3G mobiles
When the 2G and 3G mobiles power up, both the 2G and 3G mobiles
will read and tune to the 2G/3G combined carrier that contains the
common primary paging channel broadcasted on the Sync channel
message
Perform mobile logging and capture the sync channel message by
powering down/up the mobile during logging or during the
origination/termination of the call
Check “CDMA_FREQ” and “EXT_CDMA_FREQ” in the Sync channel
message and make sure that these attributes contain the correct value
(The 2G/3G combined carrier that contains the common primary paging
channel)

TRAFFIC MANAGEMENT IN THE IDLE MODE
CHANNEL LIST (HASHING)

Mobile is turned on or Enters the region where more than one Paging
Channel is configured.
A Channel List message with available channels is continuously
broadcasted on the Paging Channel.
Mobile Chooses the desired channel by means of its IS95/IS2000 HASHING
Function while in the Idle Mode.
Mobile remains on that channel until it leaves the area where the additional
channels are available or gets directed to the underlying channel using
GSR (Step Down).
Channel List/Extended Channel List (HASHING) Overview

1xRTT Traffic Management in the Idle Mode Using
Channel List/Extended Channel List Messages
(Hashing Algorithm)
The Channel List and/or Extended Channel List messages are periodically
transmitted through the Paging Channel. Upon receiving the channel list
information embedded in the CLM and/or ECLM, the mobiles will use the
hashing function defined in the IS-95 and/or IS-2000 to determine the
carrier(s) frequency
CLM can be used to distribute 2G and/or 3G mobiles among multiple carriers
The ECLM introduced in IS-2000 can be used to distribute 3G mobiles only
Metrocell BTS
Mobiles with MOB_P_REV >= 6
NBSS10.X or greater

1xRTT Traffic Management in the Idle Mode Using Channel
List/Extended Channel List Messages (Hashing Algorithm)
(Cont)
AdvancedSector: ChannelList MO
 Channel: CDMA Carrier that contains an active paging Channel (One or more
channels)
• Range: 0..10 Recommend Value: User Specific
Note: The above attributes in the ChannelList MO are read by 2G mobiles and 3G
mobiles if the ExtChannelList MO does not exist
AdvancedSector: ExtChannelList MO
 RC_QPCH_Indicator: Use to turn on/off the RC>2/QPCH capability for the channels
in the Extended Channel list
• Range: TRUE/FALSE Recommend Value: User Specific
 ExtChannels: Channel list array will be used by MOB_P_REV >= 6 mobiles
Note: The above attributes in the ExtChannelList MO are used by mobiles with
MOB_P_REV >= 6

List/Extended Channel List Messages (Hashing Algorithm)
(Cont)
Datafill Requirement (Cont)
AdvancedSector MO: ExtChannelList MO: ExtChannel
 CDMA_FREQ: CDMA Frequency Number (One or more channels)
 RC_QPCH_CAP_IND: Indicates whether the above channel supports RC>2/QPCH
or not (Multiple instances as above)

BSMCI Tables – Metro Subsystem

Channel List and Extend Channel List in BSM GUI

1xRTT CCLM/ECLM (HASHING) SUMMARY
ECCL
bit
SPM
True
False All Channels
in CCLM
2G mobile with MOB_P_REV < 6
use channels in CCLM for hashing
3G mobile with MOB_P_REV >= 6
ECCLM
All Channels
in CCLM
2G mobile with MOB_P_REV < 6
RC_QPCH
_INDICATOR bit
True
False
All CHs in
ECCLM
All 3G mobiles use channels
in ECCLM for hashing
All CHs in
ECCLM
True
False
RC_QPCH
CAP_IND bits
CHs in
ECCLM
CHs in
ECCLM
All 3G mobiles use these
CHs in ECCLM for hashing
No mobiles will use these
CHs in ECCLM for hashing
Selective Hashing

IS95-IS2000 Messages
IS95: CDMA Channel List Message (CCLM) on the paging channel
IS2000: CDMA Channel List Message (CCLM) and Extend CDMA
Channel List Message (ECCLM) on the paging channel
IS95/IS2000: System Parameter Message (SPM) over the paging channel
There is an indicator bit (EXT_CHAN_LIST) in the SPM to indicate that the
3G mobiles need to read the ECCLM instead of the CCLM
Procedure to turn this function ON/OFF
There is no on/off switch for this functionality.
The Extend Channel List Message will not be broadcasted over the paging
channel when the ExtChannelList MO has no entry
Channel List/Extended Channel List Messages
(Hashing Algorithm) (Cont)

Case 1: Direct both 2G and 3G mobiles using CCLM only (no ECCLM available)
Assume the testing area has 2G/3G combined carrier BTS(s)
When powered up, the 2G and 3G mobiles should hash among 2G/3G
combined carriers and then idle on a particular 2G/3G combined carrier
according to the datafill in the AdvancedSector:ChannelList
Perform mobile logging and capture the paging channel message
The System Parameter Message (SPM) and (CDMA Channel List Message)
CCLM need to be checked.
In the SPM message, the “EXT_CHAN_LIST” should be set to “FALSE”.
In the CCLM, users should expect to see multiple CDMA channels (Datafilled
in the “ChannelList MO”) that are used for the mobiles to hash among.
List/Extended Channel List Messages(Hashing Algorithm) (Cont)

Case 2: Direct 2G and 3G mobiles using CCLM and ECCLM
Assume the testing area has 2G and 3G segregated carrier BTS(s)
When powered up, the 2G mobiles should hash among 2G carrier and then idle on
the 2G carrier (2G Channel datafilled in the AdvanceSector MO:ChannelList)
3G mobiles should hash among 3G supported carrier and idle on the 3G carrier (3G
Channel datafilled in the AdvancedSector MO:ExtChannelList)
The SPM, CCLM and ECCLM need to be checked.
In the SPM message, the “EXT_CHAN_LIST” field should be set to “TRUE”.
In the CCLM, users should expect to see multiple CDMA Channels (Datafilled in the
“ChannelList MO” that’s being used for 2G mobiles to hash among.
In the ECCLM message, users should expect to see one or more “CDMA_FREQ”
(Datafilled in the “ExtChannelList MO”) that contain only the 3G channel number for the
3G mobiles to hash among.
List/Extended Channel List Messages(Hashing Algorithm) (Cont)

TRAFFIC MANAGEMENT IN THE IDLE MODE
GLOBAL SERVICE REDIRECTION/EXTEND GLOBAL SERVICE REDIRECTION

Mobile is turned on or Enters the region where GSR and/or EGSR is active
GSR and/or EGSR directs mobiles based on the Access Overload Class set within the
GSR and/or EGSR Message(s) (a bit mapping Long Word (16 bits 0 - F)).
GSR and/or EGSR Message(s) can be broadcasted on the Paging Channel.
Mobiles remain on that channel until they leave the area where the additional
channel(s) are available or get directed to the underlying channel.
Border sectors provide GSR and/or EGSR message(s) sending all mobiles to the
underlying frequency.
Global Service Redirection/Extend Global Service Redirection Overview

Global Service Redirection/Extended Global Service
Redirection Messages (GSR Algorithm)
Global Service Redirection (GSR) and Extended Global Service Redirection
(EGSR) messages are another mechanism offered by IS95 and IS2000 to
perform idle mode traffic management among multi-carrier bands as well as
multi-generation technologies
Metro Cell BTS
Mobiles with MOB_P_REV <6 are only able to process GSRM
Mobiles with MOB_P_REV >= 6 are able to process both GSRM and EGSRM
NBSS10.X or greater

1xRTT Traffic Management in the Idle Mode Using Global
Service Redirection/Extended Global Service Redirection
Messages (GSR Algorithm) (Cont)
AdvancedSector MO: GlobalServiceRedirection MO
 Transmit: Used to turn the GSR message on/off (If set to TRUE the redirection
message will be transmitted)
Range: FALSE or TRUE Recommend Value: User Specific
 ExcludeRedirection: Excludes the MOB_P_REV >=6 mobiles from redirection
Range: FALSE or TRUE Recommend Value: User Specific (Set to
TRUE – if EGSRM is to be broadcasted
 RedirectAccessOverLoadClasses: Composed of 16 bits, represents 16 states
of access overload class
Range: 0..65535 Recommend Value: User Specific
 ReturnIfFail: Indicates that mobiles will return to their system upon failure to
obtain the service using the redirection criteria in this message
Range: FALSE or TRUE Recommend Value: TRUE

Service Redirection/Extend Global Service Redirection
AdvancedSector MO: GlobalServiceRedirection MO (Cont)
 Delete TMSI: This field should be set to TRUE if redirected mobiles are
required to delete the TMSI assigned to mobiles
 RecordType: Specify the redirected system type
Range: 1 or 2 Recommend Value: 2 – CDMA system
AdvancedSector MO: CDMASystemRedirectionRecord
 Band_Class: Redirected target system band class
 Expected_SID: Redirected target system ID
Range: 0..32,767 Recommend Value: User Specific
 Expected_NID: Redirected target system NID
Range: 0..65,535 Recommend Value: User Specific
 CDMA_ChannelList: List of channel number
 Range: 0..2047 Recommend Value: User Specific

AdvancedSector: ExtendedGlobalServiceRedirection MO
 Transmit: Used to turn this message on/off (If set to TRUE, the redirection
message will be transmitted)
 RedirectAccessOverLoadClasses: Composed of 16 bits, represent 16 states of
access overload class
 ReturnIfFail: Indicates that mobiles are to return to this system upon failure to
obtain the service using the redirection criteria in this message
 Delete TMSI: This field should be set to TRUE if redirected mobiles are
required to delete the TMSI assigned to the mobile

AdvancedSector: ExtendedGlobalServiceRedirection MO (Cont)
 RedirectedPRevIncluded: If this field is set to TRUE, then only mobiles with
MOB_P_REV defined in following three fields are redirected
 ExcludingPRevIndicator: If this field is set to TRUE mobiles with MOB_P_REV
defined by PMin and PMax are excluded from redirection. Once this field is set to
FALSE, only mobiles with MOB_P_REV defined by PMin and PMax are redirected
 RedirectPMin: Lower Bound of MOB_P_REV
 RedirectPMax: Upper Bound of MOB_P_REV
 RecordType: Specifies the redirected system type
• Range: 1 or 2 Recommend Value: 2 – CDMA System

AdvancedSector MO: ExtentedGlobalServiceRedirection:
CDMASystemRedirectionRecord (Cont)
 Band_Class: Redirected target system band class
 Expected_SID: Redirected target system SID
• Range: 0..32,767 Recommend Value: User Specific
 Expected_NID: Redirected target system NID
• Range: 0..65,535 Recommend Value: User Specific
 CDMA_Channel_List: List of channel number

1xRTT GSR AND EGSR SUMMARY
2G mobiles with MOB_P_REV < 6
Are subject to be redirected
according to their Access Over
Load Class
All Mobiles are subject to be redirect
according to their Access Overload
Class
Exclude
Redirection
Indicator bitGSRM
Present
False
EGSRM
Present
All mobiles with MOB_P_REV >= 6
are subject to be redirected according to their
Access Overload Class
Excluding protocol
revision indicator. - bit
True
False
All mobiles with MOB_P_REV in range defined by
{REDIRECT_P_MIN, REDIRECT_P_MAX} are subject to be
redirected according to their Access Overload Class
RedirectPRecInclp
ded - bit
False
True
All mobiles with MOB_P_REV in range defined by
{REDIRECT_P_MIN, REDIRECT_P_MAX} are excluded from
redirection
True
All mobiles with MOB_P_REV >= 6
Used EGSRM

Example of GSR in the CLI Script
• bsm1a% cliapp
• # Hello. Welcome to the BSM Command Line Interface (CLI).
• # For on-line cli documentation type: help;
•
• 1>cd cells1:mc800BTS1516:MCBTSSubsystem1:root1:bTSCallProcessing1:AdvancedFA1:$
• # "O
%:CBS1:cells1:mc800BTS1516:MCBTSSubsystem1:root1:bTSCallProcessing1:Advanced
• FA1:AdvancedSector1"
• 2>ls -af;
• # GlobalServiceRedirection =
• # (
• # Transmit = true,
• # RedirectedAccessOverloadClasses = 0x07CO,
• # ReturnIfFail = true,
• # DeleteTMSI = false,
• # ExcludeRedirection = false,
• # RecordType = AnalogSystemRedirection,
• # AnalogRedirectionRecord =
• # (
• # EXPECTED_SID = 0,
• # IGNORE_CDMA = 0,
• # SYS_ORDERING = ObtainEitherSystemViaCustom
• # ),
• # CDMASystemRedirectionRecord =
• # (
• # BAND_CLASS = 1900MHz,
• # EXPECTED_NID = 1,
• # CDMA_CHAN_List =
• # (
• # (1,0=25)
• # )
• # )
• # ),
ACCOLC = 0x07CO
0 7 C 0
0 0 0 0 | 0 1 1 1 | 1 1 0 0 | 0 0 0 0 |
0 1 2 3 4 5 6 7 8 9 A B C D E F
Mobile with ACCOLC (5 – 9) will be
redirected to Channel 25
How to Calculate AccessOverLoadClass

Example of GSR through BSM GUI and CLI Tools
•
• # "O
%:CBS1:cells1:mc800BTS1516:MCBTSSubsystem1:root1:bTSCallProcessing1:Advanced
• 2>ls -af;
• # GlobalServiceRedirection =
• # (
• # Transmit = True,
• # ExcludeRedirection =false,
• # RecordType = AnalogSystemRedirection,
• # (
• # ),
• # (
• # (
• # (1,0=25)
• # )
• # )
• # ),

Example of EGSR through BSM GUI and CLI Tools
• bsm1a% cliapp
•
• # "O%:CBS1:cells1:mc800BTS1516:MCBTSSubsystem1:root1:bTSCallProcessing1:Advanced
• 2>ls -af;
• # ExtendedGlobalServiceRedirection =
• # (
• # Transmit = True,
• # RedirectPRevIncluded = True,
• # ExcludingPRevIndicator = false,
• # RedirectPMin = 6,
• # RedirectPMax = 6,
• # RecordType = CDMASystemRedirection,
• # (
• # ),
• # (
• # (
• # (2,0=350,1=375)
• # )
• # )
• # ),
• #

IS95-IS2000 Messages
IS95: CDMA Global Service Redirection Message (GSRM) on the paging
channel
IS95 and IS2000: System Parameter Message (SPM) on the paging
channel
IS2000: GSRM and EGSRM on the paging channel
Procedure to turn this function ON/OFF
There is an on-off “transmit” bit in both GSRM and EGSRM to turn this
functionality on/off.
By properly datafilling several fields of the IS95 Global Services
Redirection Message (GSRM), certain levels of 2G idle mode traffic
management can be achieved
By properly datafilling several fields of the IS2000 Global Services
Redirection Message (GSRM) and/or Extend GSR (EGSRM), certain levels of
3G idle mode traffic management can be achieved
GSR/EGSR Messages (Cont)

Case 1: Direct 2G and 3G mobiles using GSRM only
Assume the testing area has 2G/3G combine carriers
When powered up, the 2G and 3G mobiles should acquire the system,
redirect and then idle on a 2G/3G carrier according to their
ACCESSOVERLOAD Class and redirection bits in the GSR message
In the System Parameter Message, users should expect to see the
“GLOBAL_REDIRECT” bit set to “TRUE” and the “EXT_GLOBAL_REDIRECT”
bit set to “FALSE”.

Case 1: Direct 2G and 3G mobiles using GSRM only (Cont)
2. Diagnostic Verification (Cont)
For the IS95 GSR message, users should verify the 16 bit “REDIRECT_ACCOLC”
and compare it with the mobile’s ACCESSOVERLOAD Class.
For the IS2000 GSR message, users should verify the 16 bit
“REDIRECT_ACCOLC” and compare it with the mobile’s ACCESSOVERLOAD
Class. Also, make sure that the “EXCL_P_REV” (or ExcludeRedirection) bit is set to
”FALSE”,

Case 2: Direct 2G and 3G mobiles using GSRM and EGSRM, respectively
Assume the testing area has 2G and 3G segregated carrier BTS(s)
When the 2G mobiles power up, the mobiles should acquire the system, redirect
and then idle on the 2G carrier according to their “ACCESSOVERLOAD” class
and its “GLOBAL_REDIRECT” bit in the GSR message
When the 3G mobiles power up, the mobiles should acquire the system, redirect
and then idle on the 3G carrier according to their “ACCESSOVERLOAD” class and
its “EXT_GLOBAL_REDIRECT” bit in the EGSR message
Perform mobile logging and capture the paging channel message.
In the System Parameter Message, users should expect to see the
“GLOBAL_REDIRECT” bit set to “TRUE”. For IS2000, the
“EXT_GLOBAL_REDIRECT” bit should be set to “TRUE”.

Case 2: Direct 2G and 3G mobiles using GSRM and EGSR, respectively (Cont)
2. Diagnostic Verification (Cont)
• For IS95 GSR message
• Verify that the 16 bit “REDIRECT_ACCOLC” and compare it with the mobile’s
ACCESSOVERLOAD class.
• For IS2000 GSR Message
• Verify that the 16 bit “REDIRECT_ACCOLC” and compare it with the mobile’s
ACCESSOVERLOAD class.
• Verify that the “EXCL_P_REV” (or ExcludeRedirection) bit is set to ”FALSE”
• For IS2000 EGSR message
• Verify the 16 bit “REDIRECT_ACCOLC” and compare it with the mobile’s
ACCESSOVERLOAD class
• Verify the “REDIRECT_P_REV_INCL” bit. If this bit is set to ”TRUE”, all 3G mobiles
with “MOB_P_REV” defined in the range of “REDIRECT_P_MIN” and
“REDIRECT_P_MAX” should either be redirected if “EXCL_P_REV_IND” bit equals
“FALSE” or excluded from being redirected if the “EXCL_P_REV_IND” bit is set to
“TRUE”

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. RF Datafill Spreadsheet – “CDMARF_NBSS10_V24a1”, Martin
Kendall, Sep 19, 2001

1x rtt traffic_management_part_i

1x rtt traffic_management_part_i

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to 1x rtt traffic_management_part_i

Similar to 1x rtt traffic_management_part_i (20)

More from Phuoc Phuoc

More from Phuoc Phuoc (8)

1x rtt traffic_management_part_i