Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
given application
with a given DSCP
not yet in use
2 QoS Broker query
for
QoS
instructions
3 AR QoS
Configuration
4 1 st packet,
retransmitted by
the MN
5 QoS Broker query
for
QoS
instructions
6 AR2 QoS
Configuration
7, 8 1 st packet,
retransmitted by
the MN and reply
from the CN.
its information (CoA, Destination, DSCP)
will be used to query the QoS Broker.
CoA, Destination, DSCP The QoS Broker will consult the NVUP
information for that user, and if the DSCP is
allowed by the SLA, the QoS Broker
configures the AR to allow forwarding of
the next matching packets (DSCP, Dest,
CoA).
BW, priority, DSCP, CoA If there are not enough resources available in
that AR, nothing will be done.
CoA, DSCP, CN Address This packet will initiate the resource
reservation on the CN access network.
DSCP, CN Address
DSCP, CN Address
DSCP is the DSCP of the packets sent by the MT.
5.2.3 Intra-domain handover
Table 48: Message Specification for Session Setup
Every packet coming from the CORE is
trusted. No authorization or authentication
information needed at this point.
The QoS Broker will configure the AR to
allow the packets coming and going to the
CN Address with that specific DSCP.
“Session Start”
Within the Moby Dick mobility framework two different handover scenarios are considered. These are
from an administrative point of view inter-domain handover scenarios and inter-domain handover
scenarios. In order to fasten up the scenarios to minimize the timely effort for the mobility management
procedure, an intra-domain handover involves no AAA entity. Here AAA mechanisms are included as
attributes into the FAST handover specific communication between the oAR and the nAR. So, the focus
of the Moby Dick project with respect to an integration of AAA and mobility is on intra-domain
handover, mainly due to the following aspects:
• Majority of handovers will occur within an administrative domain
• Provisioning of seamless handover can be guaranteed (while inter-domain handover requires
time consuming signalling to the home domain, which might cause interruptions)
At this point of time there seems to be no need to distinguish between specification and implementation.
Therefore, the following diagram represents the fast handover signalling specification. The
implementation may depend on existing code capabilities.
The deployment of context transfer in combination with the fast handover messages prior to the handover
allow to carry the IPsec related data as e.g. a key, meter configuration information and the (sub-) profile
to the new AR and thus, e.g., allow network configuration before handover execution. It is required that
the whole active user configuration on the oAR is transmitted to the nAR. However, the acceptance of
these new flows may imply changes on current configuration of the nAR. The QoSB is aware of all these
aspects, and thus will be signalled by the oAR that a movement is desired. The QoSB does make the
adequate configuration changes and sends these commands to the nAR. After being properly configured,
the nAR confirms the configuration to the oAR, and the MN then proceeds with the handover. The a-
priory transferred information (i.e., meter configuration information and key) allow the AR to match the
authorization, to start the accounting appropriately and if necessary cancel the connection. It is not
necessary for advising the AAAC.f of the new location of the MN, to start a new AAA session between
nAR and AAAC.f, to configure the accounting on nAR etc. The AAAC only needs to receive the overall
accounting information, offline, and does not need to be informed real-time of these movements. The
parameters concerned with metering can be exchanged via a CT-alike information at the Handover
Initiate. Regardless of the result of the handover, the handover request will be then automatically
registered in the metering unit.
With respect to Context Transfer provision in combination with Fast-HO, the HI message conveys AAA
related data as a byte-stream from the oAR to the nAR. There is no need to transfer context or related
D0103v1.doc 153 / 168