Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
Interface Timing Message Send data
AAAC
QoSBroker SendQoSProfile Services Description
start-up
User
AuthoriseProfile NVUP
registration
time
User
registration
removal
DeAutorizeProfile
AR
Before runtime
ConfigRequest RouterConfig
ChangeConfig
Run-time ResourceRequest Resource
ResourceRelease
In a handover HandoverRequest HandoverResource
HandoverDec
NMS Any time SendQoSConfig QoSResourceData
QoSBrokerInterface External RequestHandover HandoverResource
Hanover
process
Radio Gateway In a new Radio
Gateway flow
OpenChannel
radio_access_allocation_msg_t
Table 17: RG to QoS Broker data
4.4.3.3 Databases
QoS Broker will have several databases. Depending on the size of them, the number of necessary queries
they should have, these databases will be present in memory or in a file. We will analyse each situation in
the following lines.
4.4.3.3.1 NetworkDB
NetworkDBs is the database that keeps the information about the network topology. It will keep
information about each router that the broker manages, its load information, the queues defined to each of
its interfaces, the scheduling algorithm applied to each interface, the occupation of each queue and the
resources that the NMS assigned in this broker. The database, as can be seen in the Figure 77, will have 5
tables:
• Router. Router table keep information such as router memory, processing capacity, router
load, and its state;
• Interface. Represents the router interfaces. It will keep information such as the Interface
address, the scheduling discipline used by the interface, and interface state;
• Queue. Represents the interface queues. It will keep the queue memory, queue occupation,
queue priority;
• QueueConf: Describes the AR queues parameters;
• RadioGW: Lists the radio gateways that belong to QoSBroker network. I has the radio
network address, as well as its network address and network mask;
• NetService: It describes the QoSBroker network services, as well as the correspondence
existing between services and radio classes;
D0103v1.doc 103 / 168