1. Impact Analysis for1xRevE Changes Vikram Gupta, Ravindra Patwardhan, Jen Chen R&D, Qualcomm Inc. 01/17/2010 1

2. Overview 2  Issue:  Prevent 1x-A MS from affecting certain legacy BS that cannot support extended RC bitmaps & capability information record  Proposed Solution  Add an indicator bit in 1x-Advanced BS SPM 1x-A BSLegacy BS1x-A Mobile Legacy Mobile ImpactAdd a bit in SPM nonechange behavior based on SPM bit none

3. Proposed Solution 3  1x-Advanced BS includes a bit Rev_E_Ext_Allowed in the SPM  Bit indicates BS is capable of processing  ORM/PRM/SRM with FOR_FCH_LEN field > 3  Capability Information Record as defined in Rev E  MS will set Rev_E_Ext_Allowed to ‘0’  by default or  At handoff to legacy RC

4. MS Impact 4  1x-A MS  MS will indicate support of new RCs in ORM/PRM only if the new SPM bit is set to ‘1’  MS will reset the indicator at handoff to legacy RC  Legacy MS  No impact (verified by multiple vendors)  Mandated by revision 0 standard on the MS  Tests for this behavior are included in test standard

5. Base Station Impact 5  1x-A base station  No IOS impact  No significant processing change from C.S0005-Ev1 include indicator bit and set it to ‘1’  Legacy BS  No Impact 1x-A MS will not include RC bitmap or capability record extensions