Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
4.5.4.7 Charging Database
The charging DB consists of two MySQL tables, cf. Table 37 and Table 38. The first one consists of
charging information for one session, i.e. each session of an user will is represented by one row in this
table. The second MySQL table holds additional information of each session, e.g. it contains information
about the DSCP (i.e. the service) the customer was using.
MySQL
MySQL
Example
Remarks
Column Name Data Type
ChargingID INT UNSIGNED Primary key,
auto_increment
UserID VARCHAR (255) hans.muster@bco.com Must be globally unique
(Max. 2^8 – 1
Characters)
SessionID VARCHAR (255) Exact structure see
Must be globally unique
(Max. 2^8 – 1
Characters)
4.5.4.5.1.2
Charge FLOAT Charge in Euros for this
Domain VARCHAR (50)
(Max. 50
Characters)
SessionTime
INT UNSIGNED
(32 Bit Unsigned)
“foreign”
session.
Indicate the domain where
the services were
consumed: “home” or
“foreign”. Note: It does
not contain the domain
name!
1350 Duration of this session,
measured in seconds.
Table 37: First MySQL table “chargingrecords” containing charge-information for a Session.
MySQL MySQL
Remarks
Column Name Data Type
ID INT UNSIGNED Primary key, auto_increment
ChargingID INT UNSIGNED Foreign key from table
“chargingrecords”
BytesToUser BIGINT UNSIGNED (64 Bit Unsigned)
DSCP TINYINT UNSIGNED (Value 0 to 255)
BytesFromUser BIGINT UNSIGNED (64 Bit Unsigned)
Charge FLOAT Charge in Euros for consuming
services with this DSCP value.
Table 38: Second MySQL table “chargingrecordsdetails” containing detailed charge-information of a
Session.
4.5.4.8 User-profiles Database
The User-profile with its databases is described in section 4.5.1.
4.5.4.9 Accounting Data Warehouse
The table definitions and exactly the same as for the accounting DB, cf. section 4.5.4.5.
4.5.4.10 Error Handling and Failure
After the accounting for one session is finished, there must be the following rows in the accounting
database:
The first row that was created with “DIAMETER start message”
(One or more rows that were generated with “DIAMETER interim messages”) 4
The last row that was created with “DIAMETER end message”
The charging component will only use closed sessions, i.e. sessions containing the last message, cf.
section 4.5.4.2.5. Due to failure of one or several components, it might happen that one or more rows are
4 Only present, if the duration of the session is longer than the „interim“ interval.
D0103v1.doc 130 / 168