Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
missing in the accounting database. It is important to note that the accounting data has to be consistent
and complete. Completer in the sense that all open session are eventually closed. The accounting
components are responsible for a consistent and complete accounting database.
Basically, information 5 is lost only when n consecutive “interim” accounting messages are lost until and
including the “end” message of the session. If only “interim” messages are lost, but the “end” message is
correct, then accounting is correct as well. This is because the counters produced from one session at one
AR are absolute—i.e. the lost of DIAMETER “interim” messages is not a problem as long as the
DIAMETER “end” message is correctly written to the accounting database.
4.5.4.11 Implementation of the Charging Component
The charging component is realized by using a web server and JSP’s. The main calculation is done in a
small java module located at the web server. The next figure depicts the overall architecture as well as the
message flows.
The users can login and view their charges that have been accumulated so far. The user communicates
through a web-browser with the web server; this connection can be IPv6, if the user is running an IPv6
capable browser.
The “Moby Dick”-operator on the other can also login via a web-browser, but has more and advanced
possibilities, for instance it can trigger manually the “accounting to charging” process.
Accounting DB
Datawarehouse
Customer DB
Charging DB
New
Accounting
Data
copying of processed data
Datawarehouse
Customer
profile
Charging
Data
Addi ng chargi ng data
Readi ng new accounting Data
Webserver
Accounting to charging
Checking consistency of all
databases
Reading customer profile
Looking up customer data
Looking up charging data of customer
Star ting
Triggering; either
manualy or automatically
Accounting2charging.jsp
cal li ng
Charging report
(JSP)
Charge Servlet, calculates
volume based charges.
Figure 87. Implementation Overview
4.5.5 QoS Interface
4.5.5.1 Purpose and architecture
The QoS Interface is used by the AAAC.f to dump, upon the arrival of a positive ARA, part of the user
profile, the NVUP, to the QoSB.f. The NVUP has a TTL equal to Authorization Life time of the
DIAMETER Session.
Upon its initialization, the AAAC.f provides the QoSB.f with a description of the NetServices within this
domain. To do so, the AAAC.f also uses the QoS Interface.
5 Information is seen here from point of view of the charging component.
D0103v1.doc 131 / 168