80-VXXX-X A July 2008 Page 1 QUALCOMM Confidential and Proprietary PCC Support for cdma2000 QUALCOMM Inc. Jun Wang, George Cherian, Masa Shirota June 15, 2009 Notice © 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.

80-VXXX-X A July 2008 Page 2 QUALCOMM Confidential and Proprietary Background eHRPD uses Gx interface and Gxa interface to support PCC PMIP is used We also need PCC support in cdma2000 (HRPD and 1x Packet): We agreed stage 3 text for NW initiated QoS in HRPD/cdma1xpacket Both UE initiated QoS and NW initiated QoS in HRPD/cdma1xpacket with PCC using Gx/Gxa interface is not clearly specified Problems with Ty interface: No BCM Selection Lack of NW initiated QoS support in 3GPP2 eHRPD PCC Structure

80-VXXX-X A July 2008 Page 3 QUALCOMM Confidential and Proprietary Overview of HRPD/1xpacket PCC Architecture (1) Policy and Charging Control (PCC) functionality includes two main functions: Flow Based Charging, including charging control and online credit control; Policy control (e.g. gating control, QoS control, QoS signalling, etc.). Gx Interface is the interface between PCRF and PCEF (PDN-GW): Gx is super set of Gxx interface Request for PCC decision from PCEF to PCRF; Provision of PCC decision from PCRF to PCEF; Delivery of IP ‑ CAN-specific parameters from PCRF to PCEF or from PCEF to PCRF - This applies only when Gxx interface is deployed Negotiation of IP ‑ CAN bearer establishment mode (i.e., BCM mode) (UE-only or UE/NW); Termination of Gx session (corresponding to an IP ‑ CAN session) by PCEF or PCRF. Gxa is used for non-3GPP trusted access: Provisioning, update, and removal of QoS rules from the PCRF to the BBERF Transmission of traffic plane events from the BBERF to the PCRF. Transmission of events reported by the PCEF to the BBERF via the PCRF. (What events are reported?)

80-VXXX-X A July 2008 Page 4 QUALCOMM Confidential and Proprietary Overview of HRPD/1xpacket PCC Architecture (2) BBERF Functions in PDSN: Packet Filter Establishment Mapping between QCI/MBR/GBR and FlowProfileID Bearer Binding (Binding flow to A10 connection) Event Reporting PCEF Functions in the PDN-GW/PDSN: Policy Enforcement – Gating ON and OFF – APN-AMBR enforcement Flow Based Accounting Bearer binding, event reporting, QoS control when Gxx interface is not used See 3GPP TS and

80-VXXX-X A July 2008 Page 5 QUALCOMM Confidential and Proprietary HRPD/1x packet PCC Architecture Simple IP

80-VXXX-X A July 2008 Page 6 QUALCOMM Confidential and Proprietary HRPD/1x packet PCC Architecture PMIP/CMIP CCoA/CMIP FA with reverse tunneling Open issue: How to handle charging at PDSN? Option 1: no change to Gx/Gxa but move all charging function to HA/LMA Option 2: use Gx interface to PDSN also Option 3: enhance Gxa to add charging related information (Is this a partial PCEF function?)

80-VXXX-X A July 2008 Page 7 QUALCOMM Confidential and Proprietary HRPD/1x packet PCC Architecture CMIP FA without reverse tunneling Open issue: How to handle charging at PDSN? Open issue: as reverse tunneling is not used, the traffic can also break out at PDSN, how to handle this using either Gx or Gxa?

80-VXXX-X A July 2008 Page 8 QUALCOMM Confidential and Proprietary UE Initiated QoS with PCC Interaction (CMIP and Simple IP)

80-VXXX-X A July 2008 Page 9 QUALCOMM Confidential and Proprietary NW-init QoS with PCC Interaction (CMIP and Simple IP)

80-VXXX-X A July 2008 Page 10 QUALCOMM Confidential and Proprietary HRPD/1x packet PCC Architecture Options MIP4 FA, CMIP and Simple IP PCC (Option B) MIP4 FA, CMIP and Simple IP PCC (Option A) PCRF need to push PCC Rules to both HA and PDSN PDSN needs support Gx for Simple IP and support Gxa for PMIP/CMIP

80-VXXX-X A July 2008 Page 11 QUALCOMM Confidential and Proprietary Proposals MIPv4 FA Mode needs to be studied further If reverse tunneling is enabled: – PCEF can be located in the HA If reverse tunneling is disabled: – PCEF must be located in the PDSN Option A (Option 1 in slide 6): For simple IP session, PCEF is located in the PDSN with Gx interface For PMIP IP session and CMIP session, PCEF is located in the HA and BBERF is located in the PDSN (reverse tunneling is always enabled). – Any issue without S2a interface supported? (We do not think so.) 3GPP needs to allow CCoA of CMIP session to be same as Simple IP address of Simple IP session For each MS, the PDSN needs to support Gx session for Simple IP and Gxa session for PMIP and CMIP Option B: For simple IP session, PCEF is located in the PDSN with Gx interface Same Gx session can be used for the Gxa session for PMIP and CMIP – Need 3GPP to support it. PCEF for CMIP with reverse tunneling and PMIP is located in the HA/LMA For each MS, the PDSN needs to support one Gx session for Simple IP, PMIP and CMIP Gx interface could be renamed with a different interface

80-VXXX-X A July 2008 Page 12 QUALCOMM Confidential and Proprietary Recommendations Need to have end to end support for PCC in cdma2000 packet data network PCC interaction should be worked jointly by the PDS and MMD Can be either specified in X.S0011-E or in a separate document Need to make 3GPP PCC specifications change if needed