300 likes | 403 Views
Enabling Autonomic Access Network QoE Management through TCP Connection Monitoring. Bart De Vleeschauwer , W. Van de Meerssche, P. Simoens, F. De Turck, B. Dhoedt, P. Demeester K. Struyve, T. Van Caenegem, E. Gilon, H. Dequeker, E. Six Munich, 25/05/2007. Topic.
E N D
Enabling Autonomic Access Network QoE Management through TCP Connection Monitoring Bart De Vleeschauwer, W. Van de Meerssche, P. Simoens, F. De Turck, B. Dhoedt, P. Demeester K. Struyve, T. Van Caenegem, E. Gilon, H. Dequeker, E. Six Munich, 25/05/2007
Topic “Enabling Autonomic Access Network QoE Management through TCP Connection Monitoring” • “Recent evolution towards the delivery of multimedia services to residential users and the corresponding sensitivity of these services for QoS problems have triggered the need for an autonomic access network QoE management framework” • “TCP monitoring probes can perform an essential function in this broader framework as they allow to monitor packet loss, RTT and jitter”
IBBTInriaTU EindhovenBudapest UniversityICCS/NTUAHHILund Institute of TechnologyACREAUniv. Carlos III de MadridUniversity of Essex Multi-service Access Anywhere operators system vendors academical component vendors SME
Multi-service Access Anywhere • Future, low-cost multi-service access network • Broadband access for residential subscribers WP: Multimedia Enabled Access Platforms
Outline • Autonomic framework for QoS/QoE management • Access network services • The Kplane/Mplane concept • A distributed autonomic framework • TCP monitor probe in an autonomic framework • Conclusion
Services & Challenges • New services: VoIP, Broadcast IPTV, Video on Demand, Gaming • Higher Requirements: interactivity, quality, Zapping Time, Artifact-free Video • Quality of the service is greatly impacted by: • RTT • Packet loss • Jitter Need for QoS/QoE management
QoS Management complexity QoS/QoE management is a complex task: • Objective QoS vs subjective QoE • Wide range of applicable techniques • Not all information can be obtained (firewall/NAT) • Management on a per-user/application basis • Many simultaneous connections Autonomic QoS/QoE management: • Detect QoS/QoE problems • Determine the cause of the problems • Find and enable QoS restorative action • Need to do this reactively and proactively
Trigger alerts Summarize monitor data Monitor Plane Restorative action Determine solution Root cause analysis QoE decrease detection Store monitor data deviceparameters router queue filling wireless linkstatistics noisemargin Double-layered architecture Knowledge Plane reroutingBW reservation gateway reconfiguration DSL gatewaymodem accessnode home network aggregationnetwork service edge router end devices
Distributed architecture • Aggregation network has tree-like topology • Some problems can be solved locally • e.g. home network misconfiguration • Others need central coordination • e.g. clients behind different access nodes suffering from QoE degradation
The access node • An important component in the end-to-end architecture • Fully under control of the access network provider • Boundary • User specific part (access line and home network) • Common part (aggregation network and beyond) • Interesting location • Monitoring (all packets are seen) • Enabling user/service specific actions
The Service Plane What is the Service Plane? The Service Plane is a SW platform which allows easy & fast deployment of service logic inside an Access Node. This SW platform will be able to run on a modular HW add-on with additional Processing Power Network Service & Applications building blocks Service Plane Platform
Outline • Autonomic framework for QoS/QoE management • TCP monitor probe in an autonomic framework • Motivation of TCP monitoring • ANTMA algorithm • Evaluation results • Conclusion
Monitoring on the Access Node • QoS problems are often located between access node and end-device • Determine values of QoE related parameters between AN and end-device Knowledge Plane Monitor Plane
Packet sniffing on the access node • Deduce QoS information by sniffing packets for protocols with two-way traffic • TCP (High Speed Internet, VoD) ANTMA algorithm • RTP • Important parameters: • Roundtrip-time • Jitter • Packet loss • Many services use TCP • Web browsing, email, ftp,… • Massively Multiplayer Online Games (e.g. Anarchy online) • Video on demand application • Information on TCP connections applicable for: • Connection itself • General “Quality” of other services that share the same path
ANTMA • Access Network TCP Monitoring Algorithm • Monitor TCP connections on intermediate monitoring point • Monitor QoS between this point and end-device • Deduce information by pairing Data and Acknowledgement packets • Assumptions: • No reordering between intermediate node and end-device • All packet (both directions) seen at monitoring point • Mainly downstream traffic
DP 1 ACK 1 TCP flight Monitoring Point Receiver Sender A1 1
DP 1 DP 1 ACK 1 TCP packet loss flight Monitoring Point Receiver Sender Time-out! 1 A1 1
ANTMA algorithm overview • Algorithm keeps a stack of packets • Stack grows and shrinks • Stack size is smaller than TCP window • Rules process stack after a packet is received • Determine which data packets can cause an ACK • Packets are removed when there is a unique match • Lost & received packets are detected • Min and max loss is derived • Determines • Packet loss (Min, Max, Avg) • RTT • Jitter
ANTMA: Example Rule • Rule M1: • A data packet cannot cause an acknowledgment with an acknowledgment number one lower than its own sequence number (by definition of acknowledgement number in TCP RFC). Example: 1 2 3A1 Rule M1: A1 cannot have been caused by packet 2
DP 1 DP 2 DP 3 DP 4 DP 5 DP 6 ACK 2 ACK 1 ACK 3 ACK 3 ACK 3 TCP Loss Monitoring: Example 1 2 3 A1 A2 A3 4 5 6 A3 A3 MP LOST History: 1 2 3 A1 A2 A3 4 5 6 A3 A3 Can match: 1,3 2 3 5,6 6
Test Set-up Overview Emulates aggregation network Emulates access + home network Emulates access node
Packet loss measurement methods • Real packet loss • Counting TCP Retransmissions: • Problem: not all retransmissions are due to loss • Benko-Veres algorithm [1]: “Smart” counting retransmissions: 3 successive retransmissions are ignored (jitter) • ANTMA: • Min: minimum loss reported by ANTMA algorithm • Max: maximum loss reported by ANTMA algorithm • Avg: Average of minimum and maximum [1] P. Benko and A. Veres, "A Passive Method for Estimating End-to-End TCP Packet Loss", In Proceedings of IEEE Globecom, 2002
ANTMA Result 3: Jitter results No packets lost !
Conclusion & future work • Autonomic framework for QoS management • Two layers: Monitor Plane - Knowledge Plane • Distributed across the network • ANTMA: • Component of Monitor plane • Algorithm for monitoring TCP services on an intermediate node • Accurate detection of QoS • Future work • Connection management • QoS/QoE restorative action for video services
Thank you for your attention Further questions?