1. TSG-X Title: Network Initiated Bearer Setup in eHRPD ____________________________________________________________________________________________________________________ Source: MOTOROLA Steve Magee Javed Khan steve.magee@motorola.com Javed.Khan@motorola.com +1-480-732-3990+1-480-732-4864 _____________________________________________________________________________________________________________________ Abstract: The contribution proposes a mechanism for setting up network initiated bearers in eHRPD ____________________________________________________________________________________________________________________ Recommendation: Discussion steve.magee@motorola.com ©2007 Motorola, Inc. Motorola Incorporated grants a free, irrevocable license to 3GPP2 and its Organization 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 portions of the contribution; and at the Organization Partner’s sole discretion to permit others to reproduce in whole or in part such contributions or the resulting Organizational Partner’s standards publication. Motorola Incorporated 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 Motorola Incorporated 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 Motorola Incorporated. Motorola Incorporated 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 Motorola Incorporated other than provided in the copyright statement above.

2. 2 Introduction Legacy HRPD does not support Network initiated bearer setup. Existing HRPD based applications use UE/AT initiated bearer setup. However, LTE/SAE supports both network initiated and UE initiated dedicated bearer setup Goal: –Evaluate eHRPD based network initiated bearer setup Coexist with UE initiated bearer setup Reuse UE Initiated bearer setup procedures for NW initiated procedure –Scenarios shown UE in HRPD  NW initiated bearer setup  NW initiated bearer teardown UE in LTE  Pre-registration – bearer setup initiated from eHRPD

3. 3 UEeANHSGW P-GW (PDN-1) HUSP: Setup Flow Response (Flow=0x02, TFT, ReqID=x) HUSP: Setup Flow Acknowledge (ReqID=x) AF / IMS H-PCRF HSS / AAA SPR Setup Resv=0x02 ProfileID=0x0100 A11’ (Flow=0x02, Setup,QoS,SO67) UE in HRPD – NW initiated dedicated bearer setup IMS/SIP signaling to setup VoIP call Application/ServiceInfo (EventRep) Ack GW and Qos Policy Rules Provision PCC Rules Provision PCC Rules Provision Ack GW and QoS Policy Rules Ack NW initiated dedicated bearer Setup e.g. VoIP bearer creation HUSP: Setup Flow Request (ProfileID=0x0100, PDN-1, UL Packet Filter, ReqID=x) HSGW maps QCI_BW => HRPD ProfileID VoIP – call setup Reservation ON Resv=0x02 A11’ (Flow=0x02, Active Start) VoIP data Default Bearer to PDN-1 already established If the UE identifies an existing reservation (Resv=0x02) which matches Profile ID, and has sufficient BW to carry IP Flow, then step may not be needed HSGW requests addition of SDF

4. 4 UEeANHSGWP-GW AF / IMS H-PCRF HSS / AAA SPROCS Release Resv=0x02 A11’ (drop Flow=0x02) UE in HRPD – NW initiated dedicated bearer deletion IMS/SIP signaling to end VoIP call Application/ServiceInfo (EventRep) Ack GW and Qos Policy Rules Provision PCC Rules Provision PCC Rules Ack GW and QoS Policy Rules Ack NW initiated dedicated bearer Release e.g. VoIP bearer release HUSP: Release Flow Request (FlowID=0x02, PDN-1, UL PacketFilter, ReqID=y) VoIP – call ends HUSP: Release Flow Response (ReqID=y, FlowID=0x02, TFT) Reservation OFF Resv=0x02 A11’ (Flow=0x02, Active Stop) HSGW requests removal of SDF If this is removal of last SDF on reservation, UE may opt to either turn reservation OFF and keep reservation for later use or it may simply release the reservation (with/without first turning OFF reservation) if it is not needed anymore

5. 5 UE eAN HSGWP-GW AF / IMS H-PCRF HSS / AAA SPR UE in LTE – Pre-registration dedicated bearer addition HUSP: PDN Connect Request (Flow=0x00, APN, AttachType) PDN1 default flow Setup HUSP Main signaling connection + Auth HRPD Session setup A11’ (Flow=0xFF Setup, SOxx) EAP Authentication Setup Resv=0x00 ProfileID=BE (0x00) A11’ (Flow=0x00, Setup,QoS,SO67) GW Ctrl Sess Est (APN, UE NAI) PCC Rules Provision PCC Rules Ack GW Ctrl Sess Est Ack (QoS Rules, Events) HSGW caches UE Sub + QoS profile, default APN, NAI, PDN GW IP Addresses etc. MME EUTRAN HUSP: Setup Flow Response (Flow=0x02, TFT, ReqID=x) HUSP: Setup Flow Acknowledge (ReqID=x) Setup Resv=0x02 ProfileID=0x0100 A11’ (Flow=0x02, Setup,QoS,SO67) HUSP: Setup Flow Request (ProfileID=0x0100, PDN-1, UL Pkt Filter, ReqID=x) HSGW initiates setup for ALL bearers already created (including bearers setup using UE initiated and NW initiated LTE procedures) – this is based upon GW info retrieved from GW Ctrl Sess Est Ack during PDN GW setup procedure Also contains info about ALL dedicated bearers currently active. NW initiated dedicated bearer Setup e.g. IMS Signaling Existing bearer GAUP to update flows A11: Session Update (QoS Profile) A11: Session Update Ack HUSP: PDN Connect Response (PDN-1) Default bearer mapping to P- GW complete

6. 6 eHRPD Bearer Mapping  IP Flow  Identified minimally by a IP 5 tuple  [src addr, dest addr, src port, dest port, protocol ID,...]  Also refered to as Packet Flow in TS23.203  Service Data Flow (SDF)  Aggregate set of IP flows which match a service data flow packet filter  SDF  aggregate of (1..n) IP flows  Packet Filter (PF)  A set of IP header values/ranges used to identify one or more of the IP flows constituting a SDF  Traffic Flow Template (TFT)  Associated with an IP address of the UE  TFT  aggregate of (1..n) Packet Filters  We assume IS835D definition of TFT will be reused in eHRPD  TFT is equivalent to a SDF template in TS23.203  UE maps a TFT PF to a Reservation Label (KK) / FlowID (KK)  eHRPD AN may map multiple reservations to single RLP / A8 / A10 tunnel  UE creates TFT (consisting of UL/DL Packet filters)  For network initiated bearer setup, TFT is created using packet filter received from HSGW  TFT binds UL SDF IP Flows to a reservation which is in turn bound to a RLP Flow  UE sends TFT to HSGW which binds DL SDF IP Flows to an Flow ID, which is in turn mapped to A10 tunnel based upon A11 signaling from RAN  HSGW provides PDNID to UE via HUSP signaling when a default bearer and dedicated bearer to a PDN is created  eHRPD AN provides 1-to-1 mapping between a single RLP flow, A8 tunnel and A10 tunnel

7. 7 Bearer Mapping in eHRPD