Policy-based QoS Network Management Yi Pan & Ariffin Datuk Yahaya Professor Tatsuya Suda’s NetGroup University of Californ...
Outline <ul><li>Existing QoS frameworks </li></ul><ul><li>Policy-based Network Management (PBNM) </li></ul><ul><ul><li>Bas...
Existing QoS Frameworks <ul><li>Proposed frameworks to provide QoS services in the literatures </li></ul><ul><ul><li>IntSe...
Outline <ul><li>Existing QoS frameworks </li></ul><ul><li>Policy-based Network Management (PBNM) </li></ul><ul><ul><li>Bas...
Policy-based Network Management (PBNM) <ul><li>Policy-based network management (PBNM) - Basic Concept </li></ul><ul><ul><l...
Policy-based Network Management (PBNM) <ul><li>Components and Architecture </li></ul>
Policy-based Network Management (PBNM) <ul><li>Functions of Components: </li></ul><ul><ul><li>Policy Repository </li></ul>...
Policy-based Network Management (PBNM) <ul><ul><li>PDP (Policy Decision Point) </li></ul></ul><ul><ul><ul><li>Performs the...
Policy-based Network Management (PBNM) <ul><li>Summary: </li></ul><ul><ul><li>Advantages of deploying PBNM </li></ul></ul>...
Outline <ul><li>Existing QoS frameworks </li></ul><ul><li>Policy-based Network Management (PBNM) </li></ul><ul><ul><li>Bas...
Deploying PBNM in the Internet <ul><li>Providing QoS in the Internet requires multi-domain operations </li></ul><ul><li>A ...
Flat Architecture Ha1 wants to send Data to Hd1 and sends a Request to the Router This Request is sent to the Policy Serve...
Hierarchical Architecture Ha1 wants to send Data to Hd1 and sends Request to the Router This Request is sent to the Policy...
Deploying PBNM in Internet <ul><li>Conclusion: </li></ul><ul><ul><li>For a small topology (that we simulated), flat is bet...
Upcoming SlideShare
Loading in …5
×

bolero.ics.uci.edu/ypan/MPATH_strm/Hitachi-slides/...

327 views

Published on

  • Be the first to comment

  • Be the first to like this

bolero.ics.uci.edu/ypan/MPATH_strm/Hitachi-slides/...

  1. 1. Policy-based QoS Network Management Yi Pan & Ariffin Datuk Yahaya Professor Tatsuya Suda’s NetGroup University of California, Irvine ypan@uci.edu, ariffin@uci.edu
  2. 2. Outline <ul><li>Existing QoS frameworks </li></ul><ul><li>Policy-based Network Management (PBNM) </li></ul><ul><ul><li>Basic Concept </li></ul></ul><ul><ul><li>Components and Architecture </li></ul></ul><ul><li>Deploying PBNM in the Internet </li></ul><ul><ul><li>Flat vs hierarchical Architecture </li></ul></ul>
  3. 3. Existing QoS Frameworks <ul><li>Proposed frameworks to provide QoS services in the literatures </li></ul><ul><ul><li>IntServ and RSVP </li></ul></ul><ul><ul><ul><li>A per-flow resource reservation based approach to enable end-to-end QoS guarantee </li></ul></ul></ul><ul><ul><li>DiffServ </li></ul></ul><ul><ul><ul><li>A scalable provision scheme to provide hop-by-hop differentiated service for aggregated flows </li></ul></ul></ul><ul><ul><li>IntServ over DiffServ </li></ul></ul><ul><ul><ul><li>A hybrid framework to provide IntServ-like QoS service to users on top of the underlying DiffServ core network </li></ul></ul></ul><ul><ul><li>Policy-based Network Management (PBNM) </li></ul></ul><ul><ul><ul><li>Using policies and policy servers to provide QoS services based on the contract between the service provider and the users </li></ul></ul></ul>
  4. 4. Outline <ul><li>Existing QoS frameworks </li></ul><ul><li>Policy-based Network Management (PBNM) </li></ul><ul><ul><li>Basic Concept </li></ul></ul><ul><ul><li>Components and Architecture </li></ul></ul><ul><li>Deploying PBNM in the Internet </li></ul><ul><ul><li>Flat vs hierarchical Architecture </li></ul></ul>
  5. 5. Policy-based Network Management (PBNM) <ul><li>Policy-based network management (PBNM) - Basic Concept </li></ul><ul><ul><li>QoS service is provided through policy server </li></ul></ul><ul><ul><ul><li>The edge routers consult the policy server to perform admission control </li></ul></ul></ul><ul><ul><ul><li>The core routers accept resource configurations from policy server to implement certain QoS service requirements </li></ul></ul></ul>
  6. 6. Policy-based Network Management (PBNM) <ul><li>Components and Architecture </li></ul>
  7. 7. Policy-based Network Management (PBNM) <ul><li>Functions of Components: </li></ul><ul><ul><li>Policy Repository </li></ul></ul><ul><ul><ul><li>A database storing all policy rules </li></ul></ul></ul><ul><ul><ul><li>Describing the agreed level of QoS services to the users </li></ul></ul></ul><ul><ul><li>Policy Management Tools </li></ul></ul><ul><ul><ul><li>An administrative tool to monitor, edit, and debug the policies in the Policy Repository </li></ul></ul></ul>
  8. 8. Policy-based Network Management (PBNM) <ul><ul><li>PDP (Policy Decision Point) </li></ul></ul><ul><ul><ul><li>Performs the admission and configuration decisions </li></ul></ul></ul><ul><ul><ul><ul><li>Decisions are made by consulting the policies in the Policy Repository </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Configurations are deployed to PEPs </li></ul></ul></ul></ul><ul><ul><ul><li>PIB (Policy Information Base) and device MIB </li></ul></ul></ul><ul><ul><ul><ul><li>Keep records of all instances of enforced policy rules on the network devices </li></ul></ul></ul></ul><ul><ul><li>PEP (Policy Enforcement Point) </li></ul></ul><ul><ul><ul><li>Intelligent network device such as routers </li></ul></ul></ul><ul><ul><ul><li>Forward user request </li></ul></ul></ul><ul><ul><ul><li>Execute configuration defined by the policy rules </li></ul></ul></ul><ul><ul><ul><li>Control the resource for each user flow </li></ul></ul></ul>
  9. 9. Policy-based Network Management (PBNM) <ul><li>Summary: </li></ul><ul><ul><li>Advantages of deploying PBNM </li></ul></ul><ul><ul><ul><li>Provides a flexible interface to define and deploy QoS services without depending on the hardware </li></ul></ul></ul><ul><ul><ul><li>Can be applied together with IntServ, DiffServ, or IntServ over DiffServ frameworks, providing a flexible granularity of QoS services guarantee to the users </li></ul></ul></ul><ul><ul><ul><li>Automate network resource management by dynamically reconfigure the network devices based on the policies </li></ul></ul></ul>
  10. 10. Outline <ul><li>Existing QoS frameworks </li></ul><ul><li>Policy-based Network Management (PBNM) </li></ul><ul><ul><li>Basic Concept </li></ul></ul><ul><ul><li>Components and Architecture </li></ul></ul><ul><li>Deploying PBNM in the Internet </li></ul><ul><ul><li>Flat vs hierarchical Architecture </li></ul></ul>
  11. 11. Deploying PBNM in the Internet <ul><li>Providing QoS in the Internet requires multi-domain operations </li></ul><ul><li>A multi-domain PBNM system can have </li></ul><ul><ul><li>Flat architecture </li></ul></ul><ul><ul><ul><li>All policy servers are peers to each other </li></ul></ul></ul><ul><ul><ul><li>Only one type of relationship between policy servers: neighboring </li></ul></ul></ul><ul><ul><li>Hierarchical architecture </li></ul></ul><ul><ul><ul><li>Policy servers are grouped together in hierarchies </li></ul></ul></ul><ul><ul><ul><li>Two different types of relationship between the policy servers: </li></ul></ul></ul><ul><ul><ul><ul><li>Siblings: policy servers who are subordinates of the same master-server </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Master: policy servers that dominates several other sub-servers </li></ul></ul></ul></ul>
  12. 12. Flat Architecture Ha1 wants to send Data to Hd1 and sends a Request to the Router This Request is sent to the Policy Server for Processing PSa Decides to Allow the Flow and Chooses an Intradomain Path PSa Sends an Interdomain Request to Next Hop Domain Border Router Forwards Interdomain Request to it’s Policy Server PSc Decides to allow the flow and chooses a path PSc Sends an Interdomain Request to Next Hop Domain Border Router Forwards Request to it’s Policy Server PSd Decides to allow the Flow and Chooses a Path Since this is the Destination, PSd Configures all the Components Components Acknowledges to Policy Server PSd sends an Interdomain Reservation to the Return Route Border Router Forwards Reservation to it’s Policy Server PSc Configures all the Components Components Acknowledges to Policy Server PSc send an Interdomain Reservation to the Return Route Border Router Forwards Reservation to it’s Policy Server PSa Configures all the Components Components Acknowledges to Policy Server PSa sends a Reservation to the Requesting User Requesting User uses the Reservation to Send Data (Ha1 to Hd1)
  13. 13. Hierarchical Architecture Ha1 wants to send Data to Hd1 and sends Request to the Router This Request is sent to the Policy Server for Processing PSa Decides to allow the flow and chooses an Intradomain Path PSa Forwards the Request to it’s Parent SMPS 1 Forwards the Request to it’s Parent ? SMPS 1 ’s Extended Domain MPS Decides to allow the flow and chooses Inter Domain Path MPS’s Extended Domain MPS Sends Request to Destination Domain through SMPS 2 SMPS 2 Forwards Request to Destination Domain SMPS 2 ’s Extended Domain PSd Chooses an Intradomain Path PSd Configures All Components Components Acknowledge Configuration PSd Informs Parent that the Domain is Configured SMPS 2 Informs Parent that the Domain is Configured MPS Configures All Other Components (Abbreviated) Components Acknowledge the Configuration (Abbreviated) MPS Sends Reservation to the Source (Abbreviated) Requesting User uses the Reservation to Send data out to Hd1
  14. 14. Deploying PBNM in Internet <ul><li>Conclusion: </li></ul><ul><ul><li>For a small topology (that we simulated), flat is better </li></ul></ul><ul><ul><li>Hierarchical architecture is better with large topology </li></ul></ul>

×