Microsoft Word Master master doc

Figure 4-14: TMMS Client unregistration 
4.2.6
 
Charging of Service Usage 
The only chargeable operation is if the client responds with 200 (OK) or 202 (Accepted) 
to a NOTIFY request. If a P-Charging-Vector header is included in the MESSAGE 
request then the TMMS PR will honor that when issuing charging. This can be used by 
the sender to indicate that the recipient shall be charged for the message.
Similar to the GPRS charging model, see 3.2.6.1, the NOTIFY request will include the 
CDR if available. 
4.2.6.1
 
Online Charging 
After the client receives the NOTIFY request it can either respond with a success 
response, such as 200 (OK) or 202 (Accepted), or with an error response. If the error 
response is 606 (Not Acceptable) that means the client is not willing to be charged for 
the message. 
The success scenario is depicted in below and the error scenario in Figure 4-15. 

---

4.2 TMMS Service based on IMS: : Design 
Page 59 of 93 
Figure 4-15: IMS online charging, client accepts to be charged 
TMMS PR uses Immediate Event Charging (IEC) to do charge the client. In the CCR it 
will have the CC-Request-Type AVP set to EVENT_REQUEST and the Requested-
Action AVP set to DIRECT_DEBITING. The TMMS PR will then wait until OCS 
answers the request. The client can now retrieve the message from the TMMS Message 
Store using the URI provided in the NOTIFY request message. 
4.2.6.2
 
Offline Charging 
For offline charging the TMMS PR sends an Accounting-Request, with the Accounting-
Record-Type AVP set to EVENT_RECORD, to the CDF after each scenario has 
finished. 
Figure 4-16: Offline charging in IMS 

---

4.2 TMMS Service based on IMS: : Design 
Page 60 of 93