Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
No. Message Parameters Remarks
1 RtAdv or L2 beacon …, paging area ID Paging area info
advertisement
2 Dormant Mode Request …, sequence #, paging area ID, Includes AH for PA
reg. lifetime
3 Dormant Mode Reply …, status code, sequence #,
lifetime
authentication at ARs.
Status code to be checked,
paging key is the same. Not
included unless requested.
1a L2 control msg. [technology specific] L2 interaction, AR generated
IP Dormant Mode Request
message (paging area update).
1b L2 control msg. [technology specific] Arrival of IP Dormant Mode
Reply at AR triggers L2
interaction.
Table 53: Messages for Paging Area Updates signalling
5.2.6 Charging
5.2.6.1 Signalling Flow
Basically post-paid and prepaid business models are possible, however only the post-paid scenario will be
implemented. Prepaid scenario will need further investigations. In the ongoing text we will therefore
focus only on the post-paid scenario.
5.2.6.1.1 Post-paid Scenario
In the post-paid scenario, the AAAC.h server stores the accounting data in the accounting database. This
database in conjunction with the customer database will contain all necessary information needed to
perform charging by applying tariffs. The detailed structure of the accounting database is described in
section 4.5.4.4. Section 4.5.4.5 contains details about the charging database, section 0 contains details
about the customer database and section 4.5.4.9 describes the data warehouse, i.e. the used accounting
data.
Cf. Figure 105 for a graphical representation of the signalling: Accounting data is added to the database
after starting a session, during a session and after the session was closed (message 1). The charging
component (CC) will periodically contact the accounting database and extract new records that have not
been yet used for charge calculation purposes (messages 2, 3). For the post-paid scenario it is sufficient
that the CC will contact the database only once a day, typically during a period of low accounting
activities. The CC uses other database—the charging and customer database—to manage the charges. The
tariff definitions will be stored either in CC itself, since they will not change during the Moby Dick trials.
On the basis of the accounting data and the entries in the customer database, the appropriate tariff will be
applied (messages 4 and 5). After the charge calculation is finished the result (i.e. the charge) is written
back in the charging database (messages 6,7). The used rows from the accounting database for the current
charge calculation, will be marked (messages 7) and then copied to another database (not drawn in the
figure).
D0103v1.doc 161 / 168