27.03.2014 Views

Moby Dick Consolidated System Integration Plan

Moby Dick Consolidated System Integration Plan

Moby Dick Consolidated System Integration Plan

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

D0103v1.doc Version 1 6.7.2003<br />

User<br />

Profile<br />

Data<br />

QBroker<br />

QBrokerEngine<br />

NetStatus<br />

RouterInterface<br />

COPSDriver<br />

Linux Router<br />

Figure 76 – COPSDriver as a PDP interface<br />

COPS communication between AR and QoSBroker is made by the COPSApi referred before. The Api<br />

implements a COPS-RSVP-like protocol, with the exception in the FHO message that is the only<br />

unsolicited message the Api supports. This interface uses the change of Keep-Alive messages in order to<br />

the network components to announce its running state to the network elements that they are connected.<br />

4.4.3.1.2.4 Data format interchanged between AR and QoSBroker<br />

BehaviourData: It describes the QoSManager queues parameters. This structure can be described:<br />

- dscp_b;<br />

- dest_addr;<br />

- queue_type;<br />

- behaviuor;<br />

- borrow_flag;<br />

- min_gred_queue;<br />

- max_gred_queue;<br />

- prob_gred_queue;<br />

At QoSManager start-up time, the QoSManager requests the configuration from the QoSBroker. The<br />

QoSBroker collects an array of BehaviourData from describing QoSManager queues information and<br />

send them to QoSManager.<br />

RD (Resource Description). It describes the resource that is being requested to the AR by a host. Such a<br />

description has:<br />

-Source address;<br />

-Destination address;<br />

-DSCP signalling code;<br />

DSCP is the reference to the QoS profile wanted. With this information QoSBroker will analyse network<br />

conditions and decide about accepting or rejecting that flow.<br />

FHOData(Fast Handover data). It describes the FHO process being requested to the QoSBroker. This<br />

structure has:<br />

- oCoA ( the old CoA): the address in use by the MN that is making a FHO;<br />

- nCoA ( the new CoA): the address that will be used by the MN after the FHO process;<br />

- nAR ( new AR): the address of the router that will connect the MN after the FHO.<br />

FHOServReserv (Fast Handover Service Reservation): is the fast handover registered service<br />

description sent by the QoSBroker to the nAR after a FHO decision was taken. This data structures has:<br />

- SourceAddress (Source address): is the source address of the registered service for the MN;<br />

- DestAddress (Destination address): is the destiny address of the service registered to that MN;<br />

- DSCP: is the DSCP of the regis tered service;<br />

- PolicyBW (Policy Bandwidth): is bandwidth values send to nAR that is used for the data rate<br />

parameter of the queue that is created to keep this service packets;<br />

- PolicyBurst (Policy Burst): is the burst rate value that defines the burst rate of the queue that<br />

AR will create in it interface to keep this service packets;<br />

D0103v1.doc 101 / 168

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!