E-UTRAN - HRPD rev B Interworking KDDI – Tomoyuki Tamura (tom-tamura@kddi.com) Hitachi – Shiro Mazawa (shiro.mazawa.qg@hitachi.com) Qualcomm - Peerapol Tinnakornsrisuphap (peerapol@qualcomm.com) Samsung – Jungsoo Jung (jungsoo@samsung.com) February 2009 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.

Overview Current E-UTRAN-HRPD rev A Interworking E-UTRAN-HRPD rev B Interworking Multiple PDN Connections EAP-AKA Support Network Initiated QoS Handoff from E-UTRAN to HRPD rev B Idle Optimized handoff Conclusion & Recommendation 2 2

E-UTRAN-HRPD rev A Interworking E-UTRAN-HRPD rev A Interworking scope consists of the following: eHRPD Multiple PDN connectivity EAP-AKA Support Network Initiated QoS E-UTRAN-HRPD rev A Idle Handoff E-UTRAN-HRPD rev A Optimized Handoff for Active Call This contribution explores additional efforts required to support E-UTRAN-HRPD rev B interworking of these features 3 3

eHRPD : Multiple PDN connections Requirements for HRPD rev A: Support of ProtocolID 0x07 (Octet based HDLC like framing supporting multiple PDNs) in Packet Application Support of ProtocolID 0x08 (One octet PDN-ID prefix) in Packet Application Support Service Option 72 in A8/A9/A10/A11 Support of VSNCP and VSNP in PPP Requirements 1&2 in C.S0087 already apply to both EMFPA and Multi-Link Multi-Flow Packet App Requirements 3&4 are transparent to the air-interface and are identical between HRPD rev A & B 4 4

eHRPD : EAP-AKA Support Requirements for HRPD rev A: Use PPP extension to support EAP-AKA authentication Requirement 1 is transparent to the air-interface and is common between HRPD rev A & B 5 5

eHRPD : Network Initiated QoS Requirements for HRPD rev A: Use RSVP message to trigger AT to initiate QoS Requirement 1 is transparent to the air-interface and is common between HRPD rev A & B 6 6

E-UTRAN to HRPD Idle Handoff Requirements: Either the AT needs to open HRPD connection when performing idle handoff from E-UTRAN to HRPD to trigger PMIP binding above HSGW, Or the AT can send InterRAT Mobility Indication message (in Default Address Management Protocol) to AN on Access Channel to trigger PMIP binding Requirement 1&2 are common between HRPD rev A & B No change on E-UTRAN is needed 7 7

E-UTRAN to HRPD Optimized Handoff Requirements for HRPD rev A: Support of Signaling Adaptation Protocol and various InterRAT subtypes of HRPD protocols The InterRAT subtypes of various HRPD protocols are actually identical to existing HRPD protocols, they just have additional “tunnel” state which is used to facilitate session negotiation and traffic channel assignment while the AT is active on E-UTRAN Protocols in Requirement 1 do not include some HRPD rev B protocols No change on E-UTRAN is needed 8 8

New Subtypes If Multicarrier TCA is required at the time of handoff, then multicarrier RouteUpdate is needed in the tunnel Inter-RAT RouteUpdate protocol needs to be enhanced to support multicarrier functionalities, Or new subtype of Inter-RAT RouteUpdate protocol is needed based on multicarrier RouteUpdate protocol Also, if Quick Idle State protocol is used, then we need Inter-RAT Quick Idle State protocol also 9 9

New Subtypes for C.S0087-A Example: Personality 1- HRPD rev B “Pre-Registration” Personality Use when AT pre-negotiates session over E-UTRAN and also when connects over-the-air Note that Inter-RAT multicarrier RUP can be used for single carrier AT as well 10 10

Call Flow

Conclusion & Recommendation Almost all necessary procedures for E-UTRAN – HRPD rev B interworking are already defined in C.S0087-0, X.S0057-0, and A.S0022-0 C.S0087-A can focus on active handoff for E-UTRAN-HRPD rev B Minor changes may include: Inter-RAT subtype for Quick Idle State and Multicarrier RUP Updated Rev B overhead messages Procedure for determining initial RTC transmission power (similar to C.S0087-0 for RTCMAC subtype 3) 12 12