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 />

Old AR<br />

New AR<br />

User Space<br />

AAA Att.<br />

User Space<br />

AAA Att.<br />

1.<br />

Trigger<br />

ctxTran<br />

FHO Mod.<br />

Kernel<br />

2.<br />

CtxtoFHO<br />

3. Handover Initiate<br />

FHO Mod.<br />

Kernel<br />

4.<br />

CtxtoAtt<br />

Figure 83: FHO module and Attendant interaction during FHO<br />

On receiving a “Router Solicitation for Proxy” message form the MN, the FHO module at the old access<br />

router requests the AAA Attendant for the context associated with the MN. The FHOmodule executes the<br />

function “StartCtxTransfer” which contains identification of the message (MesgType) e.g.<br />

StartCtxTransfer, SendctxToAtt or SendctxToFHO and the length of this message<br />

4.5.2.6 Diameter / foreign server<br />

The main functions of a foreign server are to support the mobile users to be able to access the network<br />

from outside their home network. For this purpose the AAAC.f must also support MIP.<br />

Upon receiving an AA Registration Request (ARR.f) message, the AAAC.f: The foreign server then<br />

routes the ARR.f message to the AAAC.h (using proxies or not). The AAA core executes routing using<br />

Realm Routing Table (RRT). The AAAC.f then keeps the info related to this message into the list of<br />

pending requests<br />

The response to ARR is AA Registration Reply (ARA). Upon receiving an ARA message from the<br />

AAAC.h, the AAAC.f: checks / processes the AAA Result-Code and then route it back to the Attendant.<br />

After receiving an answer from the AAAC.h the AAAC.f calls the QoS ASM, that communicates with a<br />

QoS broker.<br />

4.5.2.7 AAAC.h<br />

The AAAC.h supports MIP (as developed for the <strong>Moby</strong> <strong>Dick</strong> project) with help of ASM (application<br />

specific module)<br />

After receiving an ARR.f message the mobility ASM checks the MN's NAI, MN's Home IP Addr., Home<br />

Ag. Addr. It further checks the authentication of the AVPs record from the MN. Based on this info, it<br />

decides whether it should allow the MN to use mobile-ipv6 or not. It also selects the SA to be used for<br />

authentication.<br />

4.5.2.8 Home Agent-AAA-Enabler<br />

This is a User-space application implementing an AAA-client. Main functions of this entity are that it<br />

enables the AAAC.h to dynamically allocate HAs (load balancing) and enforce mipv6 policies at the HA.<br />

After receiving HOR (Home Agent Request),: the AAA_HA module checks whether it is good or not;<br />

respond with an appropriate Result-Code AVP and create a DH key and send the public part to the MN as<br />

an AVP in the HOA message. This then sends the reply to the requesting AAAC.h server by using the<br />

HOA (Home Agent Answer) message:<br />

D0103v1.doc 113 / 168

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

Saved successfully!

Ooh no, something went wrong!