Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
that keeps the network information, named NetStatus. It will receive a message SendQoSBConfigData
with parameter QOSB_CONFIGDATA.
4.4.2.4.3 AAACInterface
AAACInterface interfaces with the AAAC server. It defines the service QoS parameters at QoSBroker
start-up time, and dumps NVUP information to QoSBroker when any user registers in AAAC system.
Once the AAAC server starts running, it connects with the QoSBroker and sends a message defining QoS
parameters used in the available services and the corresponding DSCP codes. Those parameters are used
in the network QoS management that QoSBroker does during its operation.
After user registration in the AAAC system has been performed, the AAAC server dumps NVUP
information into the QoSBroker defining the list of services that the user will be able to use. The NVUP
information contains information such as CoA, authorisation timeout, and a list of services described by a
source address, destination address and a DSCP. It is also possible to have different timeouts for different
services, because each service has its own timeout.
4.4.2.4.4 RouterInterface
RouterInterface is the entity that will interface with the routers. It will have two modes of operation:
• receives the router request reservations: when a host starts sending a packet flow, the
Access Router (AR) will send a request to the QoSBroker through COPSDriver making a
resource reservation. QoSBroker analyses network usage state and sends an answer
accepting the new flow, or denying it.
• sends router configuration information: during AR startup, and when AR requests for a
configuration, the QoSBroker sends a set of parameters configuring the AR Queues;
4.4.3 Software Implementation
Now we will describe the implementation that has been done of the software components. We will start
with the interface description, and then we will analyze the databases used by the broker, and this
structure.
4.4.3.1 Interfaces
4.4.3.1.1 AAACInterface
AAACInterface interfaces with the AAAC server.
4.4.3.1.1.1 Data format interchanged between QoSBroker and AAAC
NVUP (Network View of User Profile). It represents the subset of the user profile that the network needs
to know. Such subset includes:
-User ID / NAI;
-Home Domain / Home service provider;
-Source address;
-N services: number of services that a user subscribed;
-Array of N elements with:
-Destination address;
-Authorisation timeout;
-DSCP signalling code;
DSCP signalling code can be very useful in a situation of a foreign domain access with different QoS
signalization. For each user is defined a set of N services that can be used by him. Each service has an
authorisation timeout, a destination address, a QoS Profile describing this service QoS parameters, and a
DSCP signalling code. Matching user profiles in different domains is a task to AAAC.
QoSProfile – QosProfile represents the QoS conditions of some profile. This profile defines some
parameters as:
-DSCP;
-Bandwidth;
-Priority;
-Minimum Delay;
4.4.3.1.1.2 Messages changed between AAAC and QoSBroker
It will allow several messages in several different moments:
1. Before Operation: SendQoSProfile(QoSProfile) – Used by the AAAC to define to the
QoSBroker the QoS Profiles, and its QoS parameters;
2. Registration time: AuthorizeProfile(NVUP) - AAAC signals QoSBroker to allow resource
usage (for a user). Resources are not yet reserved, this is done at session setup time;
D0103v1.doc 98 / 168