Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
4.5.2.3 Registration Protocol Handler
The Registration Protocol Handler (RPH) is triggered on receiving an MNARq or on receiving an
MNARp.
The MNARq message is sent when the MN is switched on or the authorization lifetime expires. After
such an event the MN communicates with the attendant to request an access. As Diameter is not used for
communication between a MN and an Attendant, the AAA request from the MN must be sent using UDP
to the Attendant.
Message:
Parameters:
MNARq (Mobile Node AAA Request)
Challenge
User-Name (AVP name which can generate lots of confusion)
MIPv6-Mobile-Node-Address
MIPv6-Home -Agent-Address
MIP-Binding-Update (Home Registration)
MN-DH-PV (MN's Diffie-Hellman public value)
The RPH is also triggered at receiving a response message from the AAAC infrastructure. This is the
response sent by the AAA-h to the MNARq
Message: MNARp.
Message:
Parameters:
MNARp
Session-Id
Result-Code
AAAC.h-MN-AVPs
4.5.2.4 AAAC Protocol Handler
Once the Attendant has received the UDP packets containing the AAA messages, it will send all the
upstream messages using Diameter
ARR.f ::= < Diameter-Header: 0xfff00fff, 0, REQ, PXY >
{ Session-Id }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Auth-Application-Id }
{ MN-AAAC.h-AVPs } /* An AVP of type Grouped */
{ Att-DH-PV }
* [ AVP ]
The answer to the above request looks as follows
ARA.f ::= < Diameter-Header: 0xfff00fff, 0, REP, PXY >
{ Session-Id }
{ Result-Code }
{ AAAC.h-MN-AVPs } /* An AVP of type Grouped */
* [ AVP ]
4.5.2.5 Fast handover
The attendant also has an interface to the Fast Handover (FHO) module, which is a kernel space module.
These modules interact with each other to transfer the context from the old access router to the new
access router.
D0103v1.doc 112 / 168