Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
parameters for re -establishment of QoS functions on the nAR. Re-establishment of the security
association on the nAR is done by conveying the respective key. Additionally, since each AR generates a
new SPI, this index is not to be conveyed from oAR to nAR, but the nAR generates a new SPI. This SPI
is to be transferred from the nAR to the mobile terminal.
The Accounting Start indication is sent to the AAAC.f from the mobility manager of the nAR on
reception of the 1 st PDU at the nAR.
In case of a inter-domain handover it is expected that no communication between the two provider (of the
oAR and the nAR) takes place for sure and so no direct context transfer is possible. In this case a standard
registration process is triggered. The de-registration of a user/MT in the oAR domain is done exclusively
by either a missing re-registration message, or a registration message of a new user using the same CoA.
MN oAR nAR oQoS.f nQoS.f AAAC.f HA
2
1
3
Is delay an issue? If yes,
consider to not wait for C.
A
C
B
5
6
7
9
8
10
11 12
13
14
X
15
Figure 99: Fast Handover Signalling Flow
The following table describes the messages and parameters for the Fast Handover Signalling:
No. Message Content / Parameters Remarks
1 Router Advertisement Network prefix + x Indicates HO type - see below
2 Router Solicitation for Proxy NARaddr, new CoA
3 Handover Initiate SubSubProfile, key, new
CoA
CT info for AAA as bytestream
conveyed
A QoS message (COPS?) NAR, oCoA Indication of nAR ID, oCoA
B QoS message (COPS?) HoA, nCoA, DSCP in use carry NVUP (HoA, nCoA,
DSCP in use)
C QoS message (COPS?) Configuration data, result
info (command and DAD
check result)
5 Handover Acknowledge SPI
6 Proxy Router Advertisement SPI
7 Handover Execute (FBU)
8 Start Bicasting (& Timer)
carries configuration data for
nAR or info on ResReserv
failure, indication on DAD
result
D0103v1.doc 154 / 168