50 likes | 181 Views
Network Evolution Network-Initiated Auxiliary RLP Link Flows. Bruce Perlmutter Camiant Inc February, 2006 Jeju Korea. Why Network Initiated Auxiliary RLP Link Flow?.
E N D
Network Evolution Network-Initiated Auxiliary RLP Link Flows Bruce Perlmutter Camiant Inc February, 2006 Jeju Korea
Why Network Initiated Auxiliary RLP Link Flow? • Goal: Make the Introduction of QoS-Enabled Packet Data Services Rapid, Secure, Easy to Manage and Therefore More Likely to Proliferate • What is Network Initiated RLP Link Flows? • User initiates application request on primary link flow • Application function notifies PCRF of request • PCRF performs policy logic • If policy is approved, PCRF signals RAN to initiate new Auxiliary RLP Link Flow with specified RAN QoS via PDSN
Why Network Initiated Auxiliary RLP Link Flow ? • Potential Issues with Client Initiated Auxiliary RLP Link Flow Model • Complicated application / client requirements • Operator cannot modify application bearer characteristics based on capacity or policy • No centralized point for QoS definition • QoS definitions distributed between RAN, PDSN, AAA, PCRF, MS • New application behavior dependant on behavior of multiple handset/clients types • Camiant’s Cable Experience Has Shown Network Initiated Model is More Commonly Adopted • CableLabs PCMM spec allows both models, but virtually all deployments & trials have all been Network Initiated • DOCSIS 1.1 Cable RF environment is very similar to emerging mobile multi-flow RF environment
Proposed Network Initiated Auxiliary PDSI HRPD Rev A Signaling MAY BE DIFFERENOther Approaches maybe possible
Comparison with MS Initiated Auxiliary PDSI HRPD Rev A Signaling MAY BE DIFFERENT