1 / 9

Support for PDSN handoffs in SBBC

Both Simple IP and Mobile IP supports AGW ↔ AGW (PDSN) fast handoffs Mobile IP supports Dormant Handoffs Bearer connections (A10, A11) moved between AGWs during handoff This capability is not required for GGSNs What about cross technology handoffs? e.g. (HRPD ↔ 1X and Rev A ↔ Rel 0).

malana
Download Presentation

Support for PDSN handoffs in SBBC

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Both Simple IP and Mobile IP supports AGW ↔ AGW (PDSN) fast handoffs Mobile IP supports Dormant Handoffs Bearer connections (A10, A11) moved between AGWs during handoff This capability is not required for GGSNs What about cross technology handoffs? e.g. (HRPD ↔ 1X and Rev A ↔ Rel 0) Support for PDSN handoffs in SBBC

  2. Typical Handoff Signaling (Inter PCF- Different PDSN) Inter-PCF Handoff (Dormant or Active) - Different PDSN This kind of handoff is indicated to the PDSN by receipt of an A11 Registration Request containing the PANID and CANID. It also includes the Mobility Event Indicator and Accounting Data (R-P Session Setup Air-link Record). From the perspective of High Availability, this looks like a new session establishment on the newly active PDSN and a 'regular' session termination on the old PDSN. Background info

  3. Background info

  4. Background info

  5. Background info

  6. How does the PCRF know that a giver bearer creation needs authorization from the PCRF How can the PCRF know that authorization requres information from the af How does the PCRF know that subsequent bearers will be requested. Does this mean that PCRF is not applicable on RAT without supplementaty bearers This implies that Bearer only (no AF required) is permitted. Even if the Bearer never comes, new charging rules can be pushed

  7. PreviousPCF NewPCF PreviousAGW New AGW MS PCRF AF A11 Registration Request SBBC Authorization Query * Not all A11 signalling messages shown PCRF Sees Duplicate Authorization and implements handoff Bearer Authorization and charging rules A11 Registration Reply PCRF Loads IP QoS and Charging Rules A11 Registration Update SBBC Terminate Bearer SBBC Terminate Charging Rules SBBC Authorization Query A11 Registration Request Bearer Authorization and charging rules Re-negoitiate PPP and Mobile IP R-P Session Expires Terminate Remaining Bearers and Charging rules. Terminate IP Charging Rules New Bearers should be authorized (e.g. admitted) and new charging rules may apply Delete MS Session and all Subsessions

  8. AF AF PCRF PCRF AGW AGW Handoffs Where Each AGW is Attached to a Different PCRF • There is no assurance that an MS cannot handoff to an AGW/PCRF that is not attached to the MS’s AF • There is no way to ensure that MS/AGW is on the same PCRF as the AF • When an AF is attached to multiple PCRFs there is no way for the AF to determine the current AGW/PCRF for the MS • PCRF/AGW may need to transfer gate information to new PCRF/AGW in handoff situation • Recommend contribution for Service PCRF (S-PCRF) and Access PCRF (A-PCRF) similar to TISPAN model • Provides Scalability • Support Fixed Mobile Convergence • Resolve inter PCRF handoff problems • Can be implemented as a Redirect server for scalability and performance AF AF S- PCRF A-PCRF A-PCRF A-PCRF AGW AGW Cable/DSL

More Related