 |
 |
 |
 |
|
 |
 |
|
 |
of service level requirements to network QoS is done by resouce control agent.
[Cor]discusses the QoS contol architecture for DiffServ over MPLS.
[Cam] suggests that work on QoS-driven end-system architecture must be
integrated with network configurable QoS services and protocols to meet application-to-
application requirements.
In recognition of this, researchers have recently proposed new communication
architectures which are broader in scope and cover both network and end-system
domains. The [JN] does an extensive survey on the state-of-art of the QoS
architectures and mentions following projects:
_ Extended Integrated Reference Model (XRM), which is
being developed at
Columbia University;
_ OSI QoS Framework, which is being developed by the
ISO SC21 QoS Working
Group;
_ OMEGA Architecture, which is being developed at theUniversity of Pennsylvania;
_ Heidelberg QoS Model, which is being developed at IBMs European Networking
Center;
_ Tenet Architecture, which is being developed at theUniversity of California at
Berkeley
_ End System QoS Framework, which is being developed at Washington University;
_ IETF QoS Manager (QM), which is being developed by
the int-serv group as part of
its strategy for an integrated services Internet;
_ TINA QoS Framework, which is being developed by the TINA Consortium; and
_ MASI End-to-End Architecture, which is being developed at Universit Pierre et
Marie Curie.
We now discuss Aquila architecture in detail here.
1) Aquila Architecture: The general AQUILA network architecture is based on the
DiffServ network concept.
The objective of the project is to provide dynamic control
to QoS based traffic.
This is done by creating an architecture with a layer resource control layer forcontrolling
network resources above the DiffServ network. It maintains the distribution of network
resources between different network entities, especially the network access points. So it
 |
|
 |
|