Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
4.2.2.6.1 Metering
The core component of the metering software is the IETF RTFM NeTraMet implementation as
documented in RFC 2063, RFC 2064 and its successor RFCs.
The NeTraMet implementation was enhanced with the following new features:
A Meter was modifies in the sense that dynamically CoAs can be assigned to User_Class_IDs. This user
class Ids will be used to link CoAs with a predefined user group reflecting a certain SLA.
A Meter Manager and Meter reader was modified in the sense that the flow data is stored into a mySQL
database. The communication between the Meter Reader and the database is done via ODBC.
Figure 44 depicts the components of the meter block located at the Access Router. NeTraMet meters the
data according the above mentioned RFCs. NeMaCDB reads the data from the meter, opens at each
reading cycle the database and stores the raw data into this database. All this modules are installed at the
same machine. The interval between two consecutive meter reading cycles is expected to be in the rage 1
s – 5 s.
NeTraMet
SNMP
NeMaCDB
SNMP
ODBC
Metering
Attendant
Accounting
Interface
AAA Attendant
Figure 44: Metering Module Architecture
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 45: Meter Attendant API – data format
D0103v1.doc 57 / 168