Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
static int PFKey::get_spi()
static void PFKey::free_spi(int spi)
static int URPFWMgr::init()
static int URPFWMgr::allow6(const char *in_dev,
struct in6_addr *v6addr)
static int URPFWMgr::forbid6(struct in6_addr *v6addr)
4.2.3.7 Interface between AAAC Attendant and metering
The metering attendant can read out the data from the Accounting database on request coming from the
AAAC Attendant. It is expected that data of the accounting database is red out in permanent intervals
(about 3 minutes). The data red out will be deleted at the accounting database in order to keep the size of
this database small and the whole system scalable. This reading intervals will be triggered by the AAAC
Attendant via a C API which is described in the following:
AAAC client can get accounting data through a function call (Get_Meter_Data). Additionally, the C Lib
can also give AAAC client two functions as required in [1]: Meter_Start() and Meter_Stop().
struct st_accdata
{
char *date;
char *time;
char *sourcepeeraddress;
char *destpeeraddress;
unsigned int inputOctets; //fromoctets
unsigned int outputOctets; //tooctets
unsigned int inputPackets; //frompdus
unsigned int outputPackets; //fromoctets
unsigned int destPort;
unsigned int dscp;
struct st_acctdata *next
}
Figure 53: Meter Attendant API – data format
Parameters of the Meter_Start message are Session_ID and CoA. Para meters of the get_Meter are the
Session_ID. The Meter_Stop parameter is the Session_ID only.
The Session_ID will be created and maintained by the AAAC Attendant. This session_ID will be
combined with a CoA after Meter_Start is called. AAAC client can use it to get Accounting data from
meter and inform meter to stop counting for this CoA.
Get_Meter_Data return a pointer to the structure. The accounting data are stored in this structure list. The
list end with a null point in next.
4.2.3.8 Interface between AAAC attendant and Fast Handover module
4.2.3.8.1 Description
The AAAC attendant module 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
(oAR) to the new access router (nAR). This is illustrated in the figure below.
On receiving a “Router Solicitation for Proxy” message form the MN, the FHO module at the old access
router requests the AAAC Attendant for the context associated with the MN. The FHOmodule executes
the function “StartCtxTransfer” which contains identification of the message (MesgType) e.g.
StartCtxTransfer, SendctxToAtt or SendctxToFHO and the length of this message
In case of an intra-domain fast handover, which is the only kind of FAST Handover to be considered
within Moby Dick, transferring the related context between the oAR and the nAR performs reestablishment
of related AAAC context on the nAR. This requires control primitives to be exchanged
locally between the old and new Air’s HO module and the AAAC attendant. Context has to be requested
from the AAAC attendant on the oAR on reception of the Router Solicitation for Proxy. To identify the
respective mobile terminal, the old CoA is used as an identifier on the oAR. The context is to be attached
to the Fast-HO CT extension and conveyed to the nAR through the HI message. On the nAR, the context
D0103v1.doc 70 / 168