Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
MN
Meter
Attendant/
AAAC client
AAAC.
1
2
3
4a
4 5
6
7
8
9
10
Figure 85: Accounting MSC
The following table specifies the messages, describes parameters and content and allows remarks.
No.
Message Content / Parameters Remarks
1
AA request
usr:pwd@domain; BU
2 AA reques t usr:pwd@domain; BU
3 AA response 2x key(MN, AR), Profile SubSet, BACK
4 Start_Meter CoA, accounting type e.g. [bytes] per DSCP
service class
4a Allow_User_Access
5 ACR 4.5.3.2.1 The Accounting-Request (ACR)
6 ACA 4.5.3.2.2 The Accounting-Answer (ACA)
7 Get_Meter_Value volume, DSCP
8 Send_Meter_Value volume, DSCP
9 ACR 4.5.3.2.1 The Accounting-Request (ACR)
10
ACA
4.5.3.2.2 The Accounting-Answer (ACA)
Table 22: Accounting Messages and their content
4.5.4 Charging Module
Charging calculates the price for a given service consumption based on session and accounting
information. It maps technical values into monetary units, and therefore applies a given contractual
agreed upon tariff. The tariff applied might depend on QoS parameters as well as timely dependent
parameters, e.g. time of the days, days of the week a service is invoked. The tariff for a particular session
is assumed to be static during that session.
If the user stays in a foreign domain (i.e. roaming) then the accounting data could basically be stored in an
accounting database located in AAAC.f or AAAC.h. Furthermore the charging could be done either in
AAAC.f or AAAC.h. Within Moby Dick, all accounting data is stored in an accounting database located
at the AAAC.h only (home domain). This implies that the charging component is located in the home
domain, too. In the case of roaming, accounting data is flowing from the foreign to the home domain. Of
D0103v1.doc 121 / 168