Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
3. Deregistration time: DeAuthorizeProfile(NVUP) – AAAC signal QoSBroker to cancel resource
usage by that user;
Communication between AAAC and the QoSBroker is made using a COPS API, that implement COPSprotocol
as messages aren't answered by the QoSBroker because of scalability reasons it was decided that
the AAAC server shouldn't wait for the QoSBroker answer each time it sends a message.
4.4.3.1.2 RouterInterface
As was stated before RouterInterface is the interface to the routers. Figure 73 shows its internal
composition.
QBroker
QBrokerEngine
NetProbe
VirtualRouter
CLIDriver
COPSDriver
Linux Router
Figure 73 - RouterInterface internals
Here is the list of those components :
• VirtualRouter: It chooses the driver that should to be used to communicate with some
specific router;
• CLIDriver: CLIDriver is the driver used to communicate with routers that we should
communicate by Command Line Interface;
• COPSDriver: COPSDriver is the driver used to communicate through COPS.
The incoming messages from the routers that request some network resource are mapped from the
COPSDriver directly to the QBrokerEngine. The outgoing messages, from the QBrokerEngine to the
routers, messages to make some configuration, or simply to analyse the network status are passed to the
VirtualRouter. Now we will describe in more detail these components and their implementation.
4.4.3.1.2.1 VirtualRouter
VirtualRouter, in Figure 74, is a kind of virtual driver that will interface the Router Interface and the
router drivers that broker use to configure the routers. It will have a database that keeps information about
the routers, its vendors, its models, and its communication format.
When the Virtual router receives a message that it should send to a router, it should verify the routers
communication format and use the correct driver to send that message. Like that we are able to have
different protocols to be used to “talk” with different routers. Such an architecture was chosen because of
the following reasons:
• The program uses the drivers as an abstraction to communicate with all the routers without
taking care about specific router communication details, making development easier;
• Makes the program evolution easier, when a new router arise the only thing needed is to add a
new entry in the database and add the specific router commands in the database.
D0103v1.doc 99 / 168