Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
is to be passed to the AAAC attendant module, providing also the nCoA as identifier for the new binding.
The following figure repeats the fast handover message flow, whereas the important messages for the
AAAC context transfer are numbered 3 and 5 and the colored messages, marked with A,B,C and X, are
not considered in the following description.
After the Mobile Terminal initialized the handover via the Proxy Router Advertisement (msg. 2), the
FHO module should:
• Get the WP4 context from the AAAC on the oAR before Msg 3 (fig. above)
• Include the WP4 context in the Handover initiate (msg. 3) and sent it to the nAR
• Give the WP4 context to the AAAC attendant on the nAR (fig above)
The context will consist of a Type Length Value TLV structure that is opaque to the FHO module. The
parameters passed from the AAAC attendant to the MT registration module are also passed in a TLV
structure.
Old AR
New AR
User Space
AAA Att.
User Space
AAA Att.
1.
Trigger
ctxTran
FHO Mod.
Kernel
2.
CtxtoFHO
3. Handover Initiate
FHO Mod.
Kernel
4.
CtxtoAtt
Figure 54: FHO module and Attendant interaction during FHO
4.2.3.8.2 Interface mechanisms
After the handover is initiated via the Proxy Router Advertisement (msg. 2) by the Mobile Node, the oAR
needs the AAAC context before contacting the nAR and triggers the ATT to relay the AAAC context to
the FHO module (see figure below: step 1), which is performed in step 2 (figure below). The context is
included in the Handover initiate message to the nAR (step 3, figure below) where it is given to the
respective AAAC attendant in step4. The figure below shows the interaction between the different entities
involved in detail.
On receiving a “Router Solicitation for Proxy” message form the MN, the FHO module at the old access
router requests the AAAC Attendant for the context associated with the MN. The FHOmodule executes
the function “StartCtxTransfer” which contains identification of the message (MesgType) e.g.
StartCtxTransfer, SendctxToAtt or SendctxToFHO and the length of this message. The parameters of the
respective messages will be presented in detail below.
4.2.3.8.3 Interface contents
The contents of the context are as follows
Context
{ Auth-Lifetime };
{ Session-Timeout }; /* what's left of it */
{ ATT-MN-SPI };
{ MIPv6-Mobile-Node-Address };
{ MIPv6-CO-Address };
{ AR-Address };
D0103v1.doc 71 / 168