Moby Dick Consolidated System Integration Plan
Moby Dick Consolidated System Integration Plan
Moby Dick Consolidated System Integration Plan
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 />
4.5.2.9 AAA message flow<br />
This section describes and specifies the message flows. The flows are divided in to request flow and reply<br />
flows. The request flow originate from MN and trans the AAA entities towards the AAA server. Whereas<br />
the reply flow is the response to the request flow and goes towards the MN.<br />
MN<br />
MNARq<br />
Attendant AAA.f AAA.h<br />
ARR.f<br />
ARR<br />
Request flow<br />
MNARp<br />
ARA.f<br />
ARA<br />
Reply flow<br />
Figure 84: AAA message flows<br />
Note, upon the reception of the ARA, the AAAC.f dumps the NVUP (part of user’s profile) to the<br />
QoSB.f. For more details see section: QoS Interface.<br />
4.5.2.9.1 MN to Attendant<br />
When the MN is switched on or after the expiration of the authorization lifetime, the MN communicates<br />
with the attendant to request an access. As Diameter is not used for communication between an MN and<br />
Attendant, the diameter AAA request from the MN must be sent using UDP to the Attendant.<br />
Message:<br />
MNARq (Mobile Node AAA Request)<br />
UDP packet containing an AAA message having the following structure:<br />
Parameters:<br />
Challenge<br />
User-Name<br />
MIPv6-Mobile-Node-Address<br />
MIPv6-Home -Agent-Address<br />
MIP-Binding-Update<br />
MN-DH-PV<br />
MN-MAC<br />
In the following sections the content of the AAA message is listed.<br />
Challenge<br />
The attendant broadcasts the challenge. The format of the Challenge has the following structure.<br />
AVP code: 0xfff00400<br />
Type: Unsigned32<br />
Length: 12 (16 if the 'V' bit is enabled)<br />
Value: The challenge MN has got from the Attendant<br />
User-Name<br />
D0103v1.doc 114 / 168
Change language