Authentication Profile for UICC- less eHRPD Terminals QUALCOMM Incorporated Contact(s): Anand Palanigounder Jun Wang Notice ©2009. All rights reserved. The contributors grants 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 contributors are 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 contributors 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 contributors. The contributors specifically reserves the right to amend or modify the material contained herein and nothing herein shall be construed as conferring or offering licenses or rights with respect to any intellectual property of the contributors other than provided in the copyright statement above. 1 S xx X xx

Background/Issue eHRPD (X.S0057) uses EAP-AKA’ for authentication EAP-AKA’ relies on an AKA algorithm (consisting of a set of “f” functions, f1-f5) pre- agreed between the UE and the HSS – If the UE has UICC, then the USIM application on the UICC contains the needed AKA algorithm (in addition to the credentials) selected by the operator – UICC’s are operator-specific, so AKA can use any AKA algorithm selected by the operator (as long as the HSS supports it) – However, eHRPD-only terminals may not use UICC (e.g., no 3GPP access supported by the eHRPD-only terminal) – This means that the eHRPD only terminal has to be: – Either operator-specific (i.e., eHRPD-only UE can only be used with the operator to whom it was specifically customized) – Or we need to specify a mandatory AKA profile & AKA algorithm profile (to support) We propose that support for an AKA profile and an AKA algorithm is mandated for eHRPD-only terminals in X.S0057 NOTE: TSG-C WG1 has already agreed to support OTASP based provisioning of eHRPD credentials and algorithms in C.P0016-D (see next slide) 2

When the device is capable of cdma2000, then the OTASP (as specified in C.S0016-D) can be used to provision the 3GPP AKA profile and AKA algorithm profile AKA profile – 3GPP/eHRPD IMSI (i.e., eHRPD IMSI used to derive EAP-AKA’ identity in NAI format, see TS ) – 3GPP AKA authentication root key (K) – AKA authentication Algorithm to be used MILENAGE (as specified in TS & ) AKA Algorithm profile: MILENAGE Authentication algorithm customization parameters such as OP or OPc – 128-bit Operator Variant Algorithm configuration Field that is used to derive the OPc or provision OPc directly NOTE: It is assumed that only MILENAGE support, as specified in TS is needed for this release, but we may add support for other algorithms in the future if needed. OTASP Support for eHRPD Provisioning 3

The eHRPD IMSI, eHRPD AKA Root Key (K) and AKA algorithm may be either factory provisioned or (re)provisioned using OTASP as specified in C.P0016- D The AKA algorithm: MILENAGE as specified in TS & AKA SQN management scheme shall be as specified in section C.2.2 and C.3.2 of Annex C in TS Anonimity Key (AK) shall be used for SQN concealment (i.e., f5 & f5* shall be non-zero) – NOTE: This is required for schemes where the SQN generation is predictable AKA Profile for eHRPD UEs 4

The MILENAGE algorithm “f” functions (f1, …, f5, f1* & f5*) shall be as defined in TS bit Operator Variant Algorithm configuration Field may be either OP or OPc (see TS )and can be reprovisioned using OTASP (see C.S0016-D). – If OP is in use, then OPc shall be derived from OP – If OPc is in use, then OPc shall be used directly MILENAGE Profile 5

Currently, we haven’t specified AKA profile and algorithm profile in X.S for UICC- less eHRPD UEs. We propose to specify an AKA profile and an AKA algorithm profile as suggested in this contribution in X.S v2.0 – Mandate AKA Profile (SQN handling scheme) – Mandate MILENAGE algorithm Conclusion & Proposal 6