Tech-invite   3GPPspecs   RFCs   SIP   Search in Tech-invite

21222324252627282931323334353637384142434445464849515255IntroTBsRELsFeaturesNEFsRef‑PointsSBIsIDsInfo
Top   in Index   Prev   Next

TR 23.800 (SA2)
Study on
Application Based Charging (ABC)

use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V12.0.0 (Wzip)  2013/03  60 p.

Rapporteur:  Mrs. Goldner, Alla

This Technical Report defines key issues and studies PCEF/TDF charging solutions for the network usage of services and applications when TDF performs application detection and control. Both online and offline charging aspects will be considered.

full Table of Contents for  TR 23.800  Word version:   12.0.0

 

Here   Top

 

1  ScopeWord-p. 8
2  ReferencesWord-p. 9
3  Definitions and abbreviationsWord-p. 10
4  Architectural Requirements
5  Key IssuesWord-p. 11
6  SolutionsWord-p. 13
6.1  Solutions for Scenario 1: application usage charging only per IP-CAN session
6.1.1  Alternative solution 1: sdf transferUp
6.1.2  Alternative solution 2: Sy extension
6.1.3  Alternative solution 3: TDF marking and PCEF based application charging
6.1.4  Alternative solution 4: Bi-Directional Marking of Charged Packets
6.1.5  Alternative solution 5: TDF TFT analysisWord-p. 23
6.1.6  Alternative solution 6: Returning the dropped packet
6.1.7  Alternative solution 7: Simplified solution for Application Based ChargingUp
6.2  Solutions for Scenario 2: sdf usage charging only per IP-CAN session
6.2.1  Alternative solution 1: sdf transfer
6.2.2  Alternative solution 2: Sy extensionWord-p. 28
6.2.3  Alternative solution 3: TDF marking and PCEF based application chargingWord-p. 29
6.2.4  Alternative solution 4: Bi-Directional Marking of Charged Packets
6.2.5  Alternative solution 5: TDF TFT analysis
6.2.6  Alternative solution 6: Returning the dropped packet
6.3  Solutions for Scenario 3: Both service data flow charging and application usage charging is required per IP-CAN session
6.3.1  Alternative solution 1: sdf transfer
6.3.2  Alternative solution 2: Sy extensionWord-p. 37
6.3.3  Alternative solution 3: Correlation by OCS
6.3.4  Alternative solution 4: TDF marking and PCEF based application charging
6.3.5  Alternative solution 5: Bi-Directional Marking of Charged Packets
6.3.6  Alternative solution 6: TDF TFT analysis
6.3.7  Alternative solution 7: Returning the dropped packet
7  EvaluationWord-p. 51
8  ConclusionsWord-p. 52
A  Application Based Charging for the applications with deducible service data flows (as supported in Rel-11)Word-p. 54
B  Packet Marking MechanismsWord-p. 55
C  Change historyWord-p. 60

Up   Top