Policybased QoS Network Management

1
Policy-based QoS Network Management

• Yi Pan Ariffin Datuk Yahaya
• Professor Tatsuya Sudas NetGroup
• University of California, Irvine
• ypan_at_uci.edu, ariffin_at_uci.edu

2
Outline

• Existing QoS frameworks
• Policy-based Network Management (PBNM)
• Basic Concept
• Components and Architecture
• Deploying PBNM in the Internet
• Flat vs hierarchical Architecture

3
Existing QoS Frameworks

• Proposed frameworks to provide QoS services in
  the literatures
• IntServ and RSVP
• A per-flow resource reservation based approach to
  enable end-to-end QoS guarantee
• DiffServ
• A scalable provision scheme to provide hop-by-hop
  differentiated service for aggregated flows
• IntServ over DiffServ
• A hybrid framework to provide IntServ-like QoS
  service to users on top of the underlying
  DiffServ core network
• Policy-based Network Management (PBNM)
• Using policies and policy servers to provide QoS
  services based on the contract between the
  service provider and the users

4
Outline

• Existing QoS frameworks
• Policy-based Network Management (PBNM)
• Basic Concept
• Components and Architecture
• Deploying PBNM in the Internet
• Flat vs hierarchical Architecture

5
Policy-based Network Management (PBNM)

• Policy-based network management (PBNM) - Basic
  Concept
• QoS service is provided through policy server
• The edge routers consult the policy server to
  perform admission control
• The core routers accept resource configurations
  from policy server to implement certain QoS
  service requirements

6
Policy-based Network Management (PBNM)

• Components and Architecture

7
Policy-based Network Management (PBNM)

• Functions of Components
• Policy Repository
• A database storing all policy rules
• Describing the agreed level of QoS services to
  the users
• Policy Management Tools
• An administrative tool to monitor, edit, and
  debug the policies in the Policy Repository

8
Policy-based Network Management (PBNM)

• PDP (Policy Decision Point)
• Performs the admission and configuration
  decisions
• Decisions are made by consulting the policies in
  the Policy Repository
• Configurations are deployed to PEPs
• PIB (Policy Information Base) and device MIB
• Keep records of all instances of enforced policy
  rules on the network devices
• PEP (Policy Enforcement Point)
• Intelligent network device such as routers
• Forward user request
• Execute configuration defined by the policy rules
• Control the resource for each user flow

9
Policy-based Network Management (PBNM)

• Summary
• Advantages of deploying PBNM
• Provides a flexible interface to define and
  deploy QoS services without depending on the
  hardware
• Can be applied together with IntServ, DiffServ,
  or IntServ over DiffServ frameworks, providing a
  flexible granularity of QoS services guarantee to
  the users
• Automate network resource management by
  dynamically reconfigure the network devices based
  on the policies

10
Outline

• Existing QoS frameworks
• Policy-based Network Management (PBNM)
• Basic Concept
• Components and Architecture
• Deploying PBNM in the Internet
• Flat vs hierarchical Architecture

11
Deploying PBNM in the Internet

• Providing QoS in the Internet requires
  multi-domain operations
• A multi-domain PBNM system can have
• Flat architecture
• All policy servers are peers to each other
• Only one type of relationship between policy
  servers neighboring
• Hierarchical architecture
• Policy servers are grouped together in
  hierarchies
• Two different types of relationship between the
  policy servers
• Siblings policy servers who are subordinates of
  the same master-server
• Master policy servers that dominates several
  other sub-servers

12
Flat Architecture
13
Hierarchical Architecture
14
Deploying PBNM in Internet

• Conclusion
• For a small topology (that we simulated), flat is
  better
• Hierarchical architecture is better with large
  topology