1 / 301

Budget-Based QoS Management Architecture

Budget-Based QoS Management Architecture. 指導老師 連耀南 教授 學生 陳建同 學生 李宗勳 學生 陳明志 學生 陳逸民. 論文題目. Session 1. Introduction. Introduction. Network convergence All-IP Network Quality of Service UMTS Application Classes QoS Architecture for IP-Based Network Integrated Service

dino
Download Presentation

Budget-Based QoS Management Architecture

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. Budget-Based QoS Management Architecture 指導老師 連耀南 教授 學生 陳建同 學生 李宗勳 學生 陳明志 學生 陳逸民

  2. 論文題目

  3. Session 1

  4. Introduction

  5. Introduction • Network convergence • All-IP Network • Quality of Service • UMTS Application Classes • QoS Architecture for IP-Based Network • Integrated Service • Differentiated Service

  6. Network Convergence • Packet switching & circuit switching. • All-IP Networks.

  7. Network Convergence &All-IP Network

  8. All-IP Network • A globally integrated network based on IP technology • Strength • Low construction & management cost. • A platform for cross-network applications. • Problem • Heterogeneous networks (Impedance Mismatch) • Complicated quality of service

  9. Heterogeneous Networks

  10. Impedance Mismatch • Horizontal impedance mismatch • e.g. 3G – IP Core Network – WLAN • Vertical impedance mismatch • e.g. DiffServ – ATM

  11. Quality of Service • QoS aspects • Long delay time • Jitter • Packet loss • More complicated QoS management • Diversified QoS Expectations

  12. Diversified QoS Expectations • User • Lowest price, best service • Lowest price, accommodative service • Acceptable price, best service • Lowest price, tolerable service • System Provider • Acceptable price, best service • Highest price, acceptable service • Lowest price, tolerable service

  13. QoS Flexibility • System providers can adjust QoS management depending on different policies.

  14. UMTS Application Classes • Conversational class • Streaming class • Interactive class • Background class

  15. QoS Sensitivity of UMTS classes

  16. QoS Architecture for IP-Based Networks • IETF working group • Integrated Service • Differentiated Service

  17. Challenges • Network convergence brings new QoS problems. • How to provide per-flow end-to-end QoS with limited resource and maximum satisfaction level?

  18. Session 2

  19. Related Work

  20. Related Work • Related Technology • Trunk • MPLS (Multi-Protocol Label Switching) • IP Network QoS architecture • IntServ • DiffServ • QoS Management Architecture • TEQUILA • Victor O.K. Li’s System • AQUILA (Adaptive Resource Control for QoS Using an IP-Based Layered Architecture) • Summary

  21. Related Work Related Technology

  22. Trunk • A trunk is defined as a unit consisting of a number of flows. • A link is a unit consisting of a number of trunks. • Intermediate routers recognize only trunks.

  23. Trunk (2) • Available bandwidth is fixed. • Suffering high blocking rate comparing to per-flow management.

  24. MPLS (1) • The use of labels is to explicitly identify a common group of packets rather than to match variable parts of the packet header. • MPLS is to enable fast switching, by replacing route lookup for a variable length IP destination address, with an exact match of a fixed, predefined number of bits.

  25. MPLS (2) • MPLS provides the ability to forward packets over arbitrary non-shortest paths • For non-IP based networks such as ATM or frame relay, it provides a IP-based control plane(routing, path selection, reservation)

  26. Integrated Service • IntServ Architecture • Virtual circuit • Long-lived unicast or multicast flows • RSVP (Resource Reservation Protocol) • PATH. • RESV.

  27. IntServ Strength & Weakness • Strength • Absolute service guarantees • Traffic flows can be monitored • Using existing routing protocols • Weakness • Enormous processing overhead & state • Scalability problem

  28. Differentiated Service • DiffServ • Providing service by classes • DSCP (DiffServ Code Point) & PHB (Per-Hop Behavior)

  29. DiffServ PHBs • Expedited Forwarding (EF) - to minimize any delays that may occur when congestion exists • Assured Forwarding (AF) –to clarify whether a packet can be dropped • Best Effort (BE) –for traffic having no special forwarding requirement, for backward compatibility

  30. PHB Examples BE E-mail, FTP EF Voice over IP(VOIP), Video on Demand(VOD) AF Web Browsing, Telnet DiffServ PHBs Application Examples

  31. DiffServ Domain (1) • Different DiffServ domain • DSCP is not compatible • Hosts that arbitrarily mark DSCP • Non-DiffServ host can be part of DiffServ domain

  32. DiffServ Domain (2)

  33. DiffServ Management Function • Classifying–based on IP, port # and network protocol • Policing • Metering– flow rate, burst size (not only for keeping the quality, but also for billing) • Shaping– holding bursts and pacing the traffic • Dropping

  34. Distinction between Edge & Core • Edge Router • Ingress Router • Classifying • Policing • Egress Router • Shaping • Core Router • Forwarding

  35. DiffServ Strength & Weakness • Strength • Low overhead • No scalability problem & easy to implement • Weakness • DiffServ does not provide per-flow end-to-end QoS .

  36. Related Work QoS Management Architecture

  37. TEQUILA • The Traffic Engineering for Quality of Service in the Internet at Large Scale (TEQUILA) • TEQUILA Architecture • Service Level Specifications Management (SLS Management) • Traffic Engineering • Data plane

  38. TEQUILA Architecture

  39. TEQUILA System Components • SLS • Subscription • Invocation • Forecast • Inter-domain SLS • Traffic Engineering • Network dimensioning • Dynamic route management • Dynamic resource management

  40. TEQUILA System • Dynamic algorithms • Route Management • Load balance • Resource Management • Link bandwidth • Buffer

  41. Victor O.K. Li’s Architecture • Efficient Resource Management for End-to-End QoS Guarantees in DiffServ Networks

  42. Admission Control • RSVP-like • Inter-domain • Intra-domain

  43. Victor O.K. Li’s System • Centralized Routing & Resource Allocation • Pre-calculated paths • Periodically Reallocation • Distributed Admission Control

  44. Summary • Scalability problem (IntServ) • Providing per-flow end-to-end QoS (DiffServ) • Too many real-time processes (TEQUILA) • Low performance to deal with bulky burst traffic (Victor O.K Li’s System)

  45. Research Objective • Propose a flexible QoS management system and associated tools for All-IP Networks.

  46. QoS Management for large-scale networks • Simple QoS management architecture • Less real-time computation • Capability of providing per-flow end-to-end QoS • Flexibility for operators’ different expectation • Adaptability for different network technologies.

  47. Budget-Based QoSSystem Features • BBQ system is one pre-planning, distributed system. • A simplified architecture for providing per-flow end-to-end QoS with high processing efficiency low management complexity. • The proposed architecture is easy to deploy. • Flexibility for operators to adjust their QoS policy. • Adaptability for different layer-2 or layer-3 technologies.

  48. Session 3

  49. Budget-Based End-to-End QoS Management for All-IP Networks全IP網路中以預算為基礎之端對端服務品質管理 Student: Chen, Chien-Tung Advisor: Lien, Yao-Nan Lab. of Mobile Communication, Dept. of Computer Science, National ChengChi Univ. September, 2003

More Related