Microsoft Word Master master doc

3.2.6
 
Charging of Service Usage 
There are two main design choices available for charging a service. Either by developing 
a CAMEL application which supports the service or to let the service itself do the 
charging. Same as with registration/un-registration of clients a solution with CAMEL is 
avoided here, for the same reason. 
As noted in [33] it is important for the consumer to get one bill for all services 
consumed, through its network operator. OMA is developing a specification for such a 
system [xx], but this work is not completed. Instead we have reused the logical design of 
OMA Wireless Application Protocol (WAP) Billing Framework v1.0 (WBF) [34] The 
reason for not implementing the complete specification is that it is very tightly bound to 
WAP, which makes it hard. However, to make it easier to interoperate in a network with 
WBF support the CDR used is designed to be easy to transform into a WBF CDR if 
needed. 
The service will act as a Content Provider entity in WBF. The Charging Control and 
Business Support entities are also needed, which ideally are available from the network 
operator or another party. For example, they could be provided by a company 
specializing in billing customers. Otherwise the service provider must provide its own 
entities. 
In contrast to the original WBF specification there is only one chargeable operation 
defined here. The chargeable operation is 
message sending
. To support commercial use of 
the messaging service, e.g. selling multimedia, the sender may request that the receiver is 
charged instead. 
First the charging model is described in detail. Next the eXtensible Markup Language 
(XML) Schema[35] for the CDR is described. 
3.2.6.1
 
Charging Model 
The charging model can be seen in the state machines depicted in Figure 3-10 and Figure 
3-11 below. 

---

3.2 TMMS Service based on GPRS: : Design 
Page 38 of 93