Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
PacketsFromUser BIGINT UNSIGNED
(64 Bit Unsigned)
Table 28. Second MySQL table “flows” for detailed information on flows.
4.5.4.5.1 Detailed Descriptions of Parameters
4.5.4.5.1.1 UserID
For the UserID the NAI format is used. The UserID has the following structure:
@
An example UserID is “fred@bco.com”.
The FQDN contained in the UserID can be compared with the FQDN contained in the sessionID to find
out whether the user is roaming or not. The UserID will be used as a key to select data from the database,
therefore each row in the table must contain the UserID.
MySQL data type
VARCHAR (255)
(Max. 2^8 – 1 Characters)
4.5.4.5.1.2 SessionID
As described in section 4.5.4.1, the accounting components will generate n rows of accounting data for
each session. If the session duration is shorter than the “interim” interval, then a completely accounted
session will consist only of two rows. Otherwise there will be several “interim” rows between the “start”
and “end” row.
Therefore a complete accounting for one session, consists of n rows, where n is greater or equal to two.
Details:
The exact structure of the sessionID is the following:
;
An example is: “access-router1.ethz.ch;1234”
Value
Rows (in the same session)
SessionID 1. – n.
Table 29: Session ID
The 64bit numeric ID uniquely identifies the session at the AAA client. The AAA client can generate it
by just monotonically increase a session counter. The 64bit ID should be spitted into lower and higher
32bit for transfer encoding:
:;