Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
Now we will list all the components with a small description of each one:
4.4.2.1 WebGUI
WebGUI is the module that enables the contact with the human operator. It was developed with two
purposes:
• It enables the QoS Broker configuration with the data edition in the NetworkDB database;
• It shows the network use status, showing the active reservations and the profiles authorized;
4.4.2.2 NetProbe
NetProbe is the entity that monitors the network status. The collected information is inserted in a database
named NetStatus. This information and the information given by the NMSInterface represent the network
status, at every instant. QBrokerEngine will user this information to decide if it should or should not
allow a new access to the network resources.
4.4.2.3 QBrokerEngine
QBrokerEngine is a process that manages several threads, one for each interface. Those threads should
wait for requests from the outside world. We will have:
• AAACAttendant – AAACAttendant will receive and answer the AAAC requests
• InterBrokerAttendant – InterBrokerAttendant receives external FHO-related data needed by the
nQoSBroker to configure the mobile terminal's nAR.
• RouterAttendant – RouterAttendant will receive router requests after processing the QoSBroker
answers. Those requests can to be summarized as follows:
o Data flow authorizing requests: AR requests QoSBroker to accept some data flow, and
QoSBroker after analysing network resource state answers accepting or rejecting that
flow;
o FHO requests: oAR contacts QoSBroker requesting the FHO process sending oCoA,
nCoA and nAR addresses. QoSBroker looks for nAR address
QBrokerEngine is responsible to launch, stop and manage those threads.
4.4.2.4 QoS Broker Interfaces
QoS Broker has several interfaces, one for each Moby Dick architecture component. Figure 72 shows a
picture of this aspect of the architecture.
AAACInterf
RGWClient
QoSBroker
NMSInterf
RouterInterface
WebServer
BrokerInterface
Attendant
BrokerClient
Now we will describe those interfaces:
4.4.2.4.1 BrokerInterface
Figure 72 – QoS Broker interfaces
BrokerInterface is the module that interfaces with neighbouring Brokers. This interface is used to change
external handover information between oQosBroker and nQoSBroker. As soon as oQoSBroker realises
that nAR belongs to other QoSBroker it collects NVUP information and reservation information about
this oCoA and sends it to the nQoSBroker. The communication between QoSBroker is made using COPS
protocol and the COPSApi developed to the communication between the AAAC, the AR and the
QoSBroker is utilised.
4.4.2.4.2 NMSInterface
That’s the interface with NMS (Network Management System) entity that allows the NMS entity to
define the network resources that can be used by this broker. It should also allow access to policy, alarm
processing and service translation functions. This interface should also to be connected to the database
D0103v1.doc 97 / 168