Resource Control in Access Networks Bert Winkelman, Sven Ooghe, Fred Willems September 2008

Agenda 1.Introduction 2.The impact of QoS on quality of end-user services  Why resource control 3.Resource control  Architecture – ITU and ETSI  Proposed RAC architecture  RAC in the first mile  Resource request flow in proposed design 4.Conclusion

All Rights Reserved © Alcatel-Lucent 2008, September 23 3 | Resource Control in Access networks | September 2008 Connection types and Service types - Diversity of Requirements

All Rights Reserved © Alcatel-Lucent 2008, September 23 4 | Resource Control in Access networks | September 2008 The impact of QoS on quality of end-user services - Test Configuration

All Rights Reserved © Alcatel-Lucent 2008, September 23 5 | Resource Control in Access networks | September 2008 The impact of QoS on quality of end-user services – Test Results

All Rights Reserved © Alcatel-Lucent 2008, September 23 6 | Resource Control in Access networks | September 2008 Why resource control?  Bandwidth limitations in first mile, aggregation and core network  Protect quality of established sessions that require QoS treatment  Condition for a satisfactory customer experience for high-bandwidth services on first mile in lower bandwidth bracket ( 5, 10, 20 Mbit/s).

All Rights Reserved © Alcatel-Lucent 2008, September 23 7 | Resource Control in Access networks | September 2008 Resource Admission Control – ITU and ETSI architecture

All Rights Reserved © Alcatel-Lucent 2008, September 23 8 | Resource Control in Access networks | September 2008 Proposed RAC architecture

All Rights Reserved © Alcatel-Lucent 2008, September 23 9 | Resource Control in Access networks | September 2008 RAC Function in the Access Network Connection types to be supported:  Unicast between access node and service node  Multicast between access node and service node Unicast – Client interacts with Server Multicast – Client interacts with Access node using IGMP

All Rights Reserved © Alcatel-Lucent 2008, September | Resource Control in Access networks | September 2008 RAC architecture in the first mile Central:  Every client must support interaction with RACF  No standards available for session signalling Central or Local? Local in Access Node:  Access node performs RAC for unicast and multicast connections  Central RAC passes unicast connection requests to Access node through interface with central RAC  No impact on client

All Rights Reserved © Alcatel-Lucent 2008, September | Resource Control in Access networks | September 2008 Resource Request Flow with Local RAC in the first mile (unicast service)

All Rights Reserved © Alcatel-Lucent 2008, September | Resource Control in Access networks | September 2008 Conclusion  Resource control is necessary to protect established sessions against service quality degradation  Local RAC in the access node is the recommended solution because:  It is a logical extension of the IGMP based multicast admission control function used in access node today,  Channel zapping delay does not increase,  No impact on customer premises equipment (set-top box, IP phone)

All Rights Reserved © Alcatel-Lucent 2008, September | Resource Control in Access networks | September