Tech-invite   3GPPspecs   Glossaries   IETFRFCs   Groups   SIP   ABNFs   Ti+   Search in Tech-invite

Top   in Index   Prev   Next

TS 23.125 (SA2)
Flow based Charging

3GPP‑Page   ETSI‑search    
use "3GPP‑Page" to get the Word version
use "ETSI‑search" to get the PDF version
V6.8.0 (PDF)  2006/03  50 p.


Rapporteur:  Mr. Boman, Krister
Descendant:

The current level of traffic differentiation and traffic-type awareness of the GPRS architecture shall be extended beyond APN and PDP Context level. It shall be possible to apply differentiated charging for the traffic flows belonging to different services (a.k.a. different service data flows) even if they use the same PDP Context.
In addition, it shall be possible to apply differentiated charging for the traffic flows belonging to different services carried by other IP Connectivity Access Networks (IP-CANs).
Charging and tariffing models described in this Technical Specification shall be possible to be applied to both prepaid and postpaid subscribers, i.e. to both online and offline charging.
Online and offline are not the same as prepaid and postpaid (see TS 32.240). For example it is worth highlighting that the operator can have postpaid subscribers on credit control by using online charging mechanisms.
The GPRS online charging solutions up to release 5 are built around CAMEL mechanisms that provide online accessand charging-control for GPRS - pertaining to PDP Contexts of an APN.
The flow based charging architecture developed in this Technical Specification shall use generic native IP charging mechanisms to the extent possible in order to enable the reuse of the same charging solution and infrastructure for different type of IP-Connectivity Networks.
NOTE: Providing differentiated service data flow based charging is a different function from providing differentiated traffic treatment on the IP-flow level. The operation of service data flow based charging shall not mandate the operation of service based local policy.
In addition charging based on specific application services or protocols shall be supported.