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

Message:<br />

Parameters:<br />

StartInterdomainHO<br />

MesgType<br />

MesgLen<br />

MN-info - stream of bytes of variable length<br />

The structure of MN-info is as follows:<br />

MN-info<br />

in6_addr MIPv6-Mobile-Node-Address (home address of the MT)<br />

in6_addr MIPv6-Home-Agent-Address<br />

in6_addr CoA-MN<br />

in6_addr AR-Addr<br />

MN-AAACh-Secret-Key<br />

Current Interface Name<br />

User-Name<br />

Step2<br />

In order to get authenticated from the AAAC server this message is sent out<br />

Message:<br />

MNA_Rq<br />

This message is not relevant for the URP-MTNM interface<br />

Step3<br />

The response the URP gets from the attendant<br />

Message:<br />

MNA_Rsp<br />

This message is not relevant for the URP-MTNM interface<br />

Step4<br />

Upon receiving a MNA_Rp from the AAAC-Attendant, the URP sends this message to MTMN)<br />

Message: SendRegResponse {<br />

Parameters: MesgType<br />

MesgLen<br />

RespCode (states whether the AAAC reg. was successful or not)<br />

Mobile Terminal<br />

Access Router<br />

User Space<br />

URP Module<br />

4. SendRegResp<br />

2. MNA_Rq<br />

3. MNA_Rp<br />

User Space<br />

AAA Att.<br />

1.<br />

Trigger<br />

StartIntDomHO<br />

NTNM Module<br />

Kernel<br />

Kernel<br />

Figure 23: Registration messages<br />

Also the following message is sent from MTNM to URP, after a successful Fast Handover:<br />

Message:<br />

StartFHO_REG<br />

D0103v1.doc 38 / 168

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

Saved successfully!

Ooh no, something went wrong!