May, 2009 C2 – Company Confidential SOURCE: David Rossetti and Jialin Zou CONTACT: ABSTRACT: This is a stage 2 proposal on 1x parameters required for CSFB. It is for C.S v2.0. TITLE: 1X Parameters for CSFB TSG-C RECOMMENDATION: Discuss and adopt. The source companies of this contribution grant a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner's name any Organizational Partner's standards publication even though it may include all or portions of this contribution; and at the Organizational Partner's sole discretion to permit others to reproduce in whole or in part such contribution or the resulting Organizational Partner's standards publication. The source companies of this contribution is also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partner’s standard which incorporates this contribution. This document has been prepared by The source companies of this contribution to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on The source companies of this contribution. The source companies of this contribution specifically reserves the right to amend or modify the material contained herein and to any intellectual property of The source companies of this contribution other than provided in the copyright statement above.

C2 – Company Confidential 2 | CSFB | May, X Parameters for CSFB A few tunneled uplink 1x messages are required to support Circuit-Switched FallBack operation.  E.g. 1X Registration Message, or Databurst Message for SMS.  In order for the UE to know how to format the tunneled encapsulated LAC PDU, the UE needs to know the value of certain 1x parameters. These parameters are sent to the UE using the MobilityParametersCDMA2000 Information Element. 3GPP TS v8.5.0 defines the MobilityParametersCDMA2000 IE, referencing C.S However, this IE is not currently defined in C.S  This IE can either be sent in CSFBParametersResponseCDMA2000 (for CSFB) or HandoverFromEUTRAPreparationRequest (for SRVCC) messages. Assumption has been that the format of this IE will be identical to the portion of the CSNA 3G1XParameters message that follows the 3G1XParametersSignature field, as defined in C.S v

C2 – Company Confidential 3 | CSFB | May, 2009 Issues  However, there are several issues with this approach that need to be clarified:  Certain 1x parameters are essentially mandatory, but this is not defined.  Default values for optional parameters that are mandatory on the 1X air interface.  Interaction with LTE SIB8 broadcast csfb-RegistrationParam1XRTT IE  Extensibility. Define how any additions will be implemented.  Interaction with LTE “rand” IE, equivalent to 1X RAND used for CDMA authentication.

C2 – Company Confidential 4 | CSFB | May, 2009 Mandatory Parameters for CSFB Although the 3G1XParameters message in C.S0082 has include bits for each 1x parameter, in practice the following parameters are mandatory for the AN to provide in order to support defined CSFB scenarios:  PREF_MSID_TYPE: So the UE knows the MSID format to use  IMSI_T_SUPPORTED: So the UE knows whether to send MIN-based or True IMSI If the P_REV in the 3G1xParameters is > 9, then the following parameters are conditionally mandatory:  MEID_REQD  EXT_PREF_MSID_TYPE

C2 – Company Confidential 5 | CSFB | May, 2009 Mandatory Parameters for 1xRTT SRVCC The following parameters are additionally necessary to be included during SRVCC:  FPC_FCH_INIT_SETPT_RC3, _RC4, & _RC5.  T_ADD  PILOT_INC

C2 – Company Confidential 6 | CSFB | May, 2009 Default values for non-mandatory parameters If a non-mandatory parameter is not included in the MobilityParametersCDMA2000, then the UE shall use the following default values. References to SIB8 are to TS v  SID: Use “sid” from CSFB-RegistrationParam1XRTT in LTE SIB8.  NID: Use “nid” from SIB8.  REG_ZONE: Use “registrationZone” from SIB8.  TOTAL_ZONES: Use “totalZone” from SIB8.  ZONE_TIMER: Use “zoneTimer” from SIB8.  PACKET_ZONE_ID: 0  PZ_HYST_ENABLED: 0  PZ_HYST_INFO_INCL: 0  P_REV: 6 (TIA/EIA/IS )

C2 – Company Confidential 7 | CSFB | May, 2009 Additional Defaults  NEG_SLOT_CYCLE_INDEX_SUPPORTED: 0  ENCRYPT_MODE: 0  ENC_SUPPORTED: 0  SIG_ENCRYPT_SUP: 0  MSG_INTEGRITY_SUP: 0  SIG_INTEGRITY_SUP_INCL: 0  SIG_INTEGRITY_SUP: 0  AUTH: 0  MAX_NUM_ALT_SO: 0  USE_SYNC_ID: 0  MS_INIT_POS_LOC_SUP_IND: 0

C2 – Company Confidential 8 | CSFB | May, 2009 Default Values (Page 3)  MOB_QOS: 0  BAND_CLASS_INFO_REQ: 0  ALT_BAND_CLASS: 0  MAX_ADD_SERV_INSTANCE: 0  HOME_REG: Use “homeReg” from SIB8.  FOR_SID_REG: Use “foreignSIDReg” from SIB8.  FOR_NID_REG: Use “foreightNIDReg” from SIB8.  POWER_UP_REG: Use “powerUpReg” from SIB8.  POWER_DOWN_REG: 0  PARAMETER_REG: Use “parameterReg” from SIB8.  REG_PRD: Use “registrationPeriod” from SIB8.

C2 – Company Confidential 9 | CSFB | May, 2009 Default Values (Page 4)  REG_DIST: 0  EXT_PREF_MSID_TYPE: 0  MEID_REQD: 0  MCC: 0 (Note that MCC 0 is reserved per ITU; this means that the UE would always use IMSI Class 0 Subtype 3).  IMSI_11_12: 0  RECONNECT_MSG_IND: 0  RER_MODE_SUPPORTED: 0  TKZ_MODE_SUPPORTED: 0  TKZ_ID: 0

C2 – Company Confidential 10 | CSFB | May, 2009 Default values  PILOT_REPORT: 0  SDB_SUPPORTED: 0  AUTO_FSCO_ALLOWED: 0  SDB_IN_RCNM_IND: 0

C2 – Company Confidential 11 | CSFB | May, 2009 Extensibility For forward compatibility, we should explicitly specify that the MS should ignore any unknown parameters at the end of the 3G1XParameters message.  Any future additions to the format will be added at the end of the message.

C2 – Company Confidential 12 | CSFB | May, 2009 RAND TS provides the ability of the eNB to signal the “RAND-CDMA2000” information element to the UE (equivalent to 1x RAND).  In CSFBParametersResponse for CSFB  In HandoverFromEUTRAPreparationRequest for SRVCC TS and TS provide the ability to signal the RAND from the eNB back to the 1xRTT IWS. There is currently no standardized mechanism for the IWS to generate the RAND and send across S102 and S1 to the eNB. Therefore we don’t need RAND to be added to the MobilityParametersCDMA2000.