Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
MySQL data type:
INT UNSIGNED
(32 Bit Unsigned)
4.5.4.5.2 EventTime
0 1.
Session time at the time the 2. – n.
record was generated in
seconds
Table 30: Session Time Details
In order to support “a time of the day” tariff scheme, each record contains the timestamp of its generation.
Thus the first record contains the start time of the session and the last record contains the end time of the
session. Within the Moby Dick project the time base will be CET.
Details:
MySQL data type:
DATETIME
4.5.4.5.2.1 BytesToUser
Value
Rows (in the same session)
Start time of session and date 1.
Time of interim record 2. – n-1
End time of session n.
Table 31: Event Time
This parameter measures the number of bytes sent to the user (i.e. downstream) from the user’s point of
view. The first row of a session in the accounting DB (“start” row), will contain only “null” values. The
counter is an absolute number from the start of the session. Thus the final amount will be in the n. row
which is the row generated by the DIAMETER “end” message.
Details:
MySQL data type:
INT UNSIGNED
(32 Bit Unsigned)
4.5.4.5.2.2 PacketsToUser
Value
Rows (in the same session)
BytesToUser 1. – n.
Table 32: Bytes To User
This parameter measures the number of packets sent to the user (i.e. downstream) from the user’s point of
view. The first row of a session in the accounting DB (“start” row), will contain only “null” values. The
counter is an absolute number from the start of the session. Thus the final amount will be in the n. row
which is the row generated by the DIAMET ER “end” message.
Details:
MySQL data type:
INT UNSIGNED
(32 Bit Unsigned)
Value
Rows (in the same session)
PacketsToUser 1. – n.
Table 33: Packets To User
D0103v1.doc 128 / 168