Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
7 BU
8 BACK
9 Accounting Data SrcIP, HoAd?, DesIP, DSCP, In/Out
Byte/Packet Counter
10 Accounting Data SrcIP, HoAd?, DesIP, DSCP, In/Out
Byte/Packet Counter
T1 Timer for AAA Attendant
to forward data to AAAC.f
T2 Re-registration interval
Table 46: Registration Step 1 messages and Parameters
The destination address
may also be required in
many network-level
services (free numbers,
e.g.)
The setting of the timer T1 has not been studies profoundly. However, in first discussions about the
involved partners for the time being a 3 minute interval is foreseen. The timer T2 for the re -registration
interval is proposed to be at the range of about 10 minutes, but also here some further discussions are
required and this value might change significantly. Possible the measurements of the trials will provide
here further input in order to come to an optimal solution.
The key between Mobile Node and Access Router is send twice, due to the encryption requirement: the
first key is encrypted for the AR, the second is encrypted for the MN. (However, it is the same key).
Messages between the MN and AR are URP messages. Messages between AR, AAAC.f and AAAC.h are
Diameter messages containing the appropriate AVPs already defined. BU and BACK are standard MIP
messages. Step 2 is shown in Figure 2. In the step 2 the initial BU is piggybacked on the AA request. This
figure does not contain the re-registration interval and the interval for the transfer of the accounting data
since this procedure is identical to step1.
MN AR AAAC. QoS.f QoS.h AAAC. HA
Figure 97: Registration Scenario Step 2
The following table specifies the messages, describes parameters and content and allows remarks.
No. Message Content / Parameters Remarks
1 AA request usr:pwd@domain; BU
2 AA request usr:pwd@domain; BU
D0103v1.doc 150 / 168