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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

D0103v1.doc Version 1 6.7.2003<br />

QoS broker<br />

QoS manager<br />

FastHandover<br />

module<br />

QoS<br />

Attendant<br />

PEP<br />

DSCP table<br />

Enhanced IPv6 stack<br />

Standard IPv6 stack<br />

Local Log<br />

Management<br />

Local<br />

Log<br />

IPSec<br />

Diffserv<br />

logic<br />

Internalinterface<br />

Protocol communication<br />

Kernel space<br />

User space<br />

Figure 37: QoSManager and its relationship with other modules<br />

4.2.2.5.1 Communication with other AR elements and within the modules of the QoS Manager<br />

Communication between the QoS Attendant and the FHM is for the following purposes:<br />

• See corresponding paragraph in Fast Handover Module / MIPL section<br />

Communication between the PEP and the DiffServ logic is for the following purposes:<br />

• Once the PEP has queried the BB how to configure the DiffServ Logic, PEP will configure<br />

queues in the DiffServ logic.<br />

• Periodically, the PEP queries the DiffServ Logic about its queues’ state.<br />

• When a new entry is added in the DSCP table, the PEP creates a filter in the DiffServ logic so<br />

that the packets whose parameters match this entry are no longer blocked but given the<br />

appropriated<br />

• When a entry is removed in the DSCP table, the PEP removes the above mentioned filter in the<br />

DiffServ logic.<br />

• When a packet is blocked the DiffServ logic, communicates packet’s parameters to the PEP so<br />

that it can initiate an authorization procedure (i.e. queering the BB).<br />

Communication between the internal elements of the QoS Manager<br />

Three elements constitute the QoS Manager, the PEP module, the QoS Attendant Module and the DSCP<br />

table. PEP communicates with both QoS Attendant and DSCP table. No communication exists between<br />

DSCP table and the QoS Attendant.<br />

Communication between the PEP and the DSCP table is for the following purposes.<br />

• Periodically the PEP checks the table for flows (CoA+DSCP) whose authorization live time is<br />

about to expire. In that case, the PEP queries the BB for a reauthorisation.<br />

• DSCP table contains the QoS treatment to apply to flows and, knowing this, the PEP can<br />

configure accordingly the DiffServ Logic.<br />

Communication between the PEP and the QoSAttendant is for the following purposes.<br />

• The QoSAttendant tells the PEP to:<br />

o ask the QoSBroker for a context transfer (in the oAR)<br />

o start listening for the Context transfer message coming form the QoSBroker (in the<br />

nAR)<br />

• When the PEP in the nAR receives this context transfer it tells the QoSAttendant if there are or<br />

not enough available QoS resources.<br />

D0103v1.doc 52 / 168

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

Saved successfully!

Ooh no, something went wrong!