Content for TS 23.125 Word version: 6.8.0
4 General Requirements
5 Flow Based Charging Concepts
6 Architectural concepts
7 Message Flows
A Overall architectural impacts of IP flow based charging
B IMS and Flow based charging
C WLAN and flow based charging
D Policy functions provided by FBC architecture
$ Change history
4 General Requirements p. 8
5 Flow Based Charging Concepts p. 10
5.1 Overview p. 10
5.2 Charging rules p. 11
5.3 Service data flow detection and counting p. 13
5.4 Reporting p. 14
5.5 Credit management p. 14
5.6 Termination Action p. 15
5.7 Re-authorisation and Event Triggers p. 16
5.8 Policy functions provided by FBC architecture p. 16
5.8.1 General p. 16
5.8.2 Charging correlation p. 16
5.8.3 Gating p. 17
5.8.4 QoS control p. 17
5.8.5 Bearer events p. 17
5.8.6 Session events p. 17
5.9 Bearer Relation p. 18
6 Architectural concepts p. 18
6.1 Architecture p. 18
6.1.1 Online service data flow based bearer charging architecture p. 18
6.1.2 Offline service data flow based bearer charging architecture p. 19
6.2 Functional Entities p. 19
6.2.1 Charging Rules Function p. 19
6.2.2 Service Data Flow Based Credit Control Function p. 19
6.2.3 Offline Charging System p. 20
6.2.4 Traffic Plane Function p. 20
6.2.5 Application Function p. 21
6.2.6 Relationship between functional entities p. 22
6.3 Reference points p. 22
6.3.1 Gx reference point p. 22
6.3.1.1 Initialisation and Maintenance of Gx Connection p. 23
6.3.1.2 Request for Charging Rules (from TPF to CRF) p. 23
6.3.1.3 Provision of Charging Rules (from CRF to TPF) p. 23
6.3.1.4 Indication of Bearer Termination (from TPF to CRF) p. 24
6.3.2 Gy reference point p. 24
6.3.3 Gz reference point p. 24
6.3.4 Rx reference point p. 24
6.3.5 Void
7 Message Flows p. 24
7.1 AF input to provision of charging rules p. 24
7.2 Bearer events p. 26
7.2.1 Bearer Service Establishment p. 26
7.2.2 Bearer Service Modification p. 28
7.2.2.1 General p. 28
7.2.2.2 Bearer Service Modification in case of offline charging p. 28
7.2.2.3 Void
7.2.2.4 Bearer Service Modification in case of online charging p. 29
7.2.3 Bearer Service Termination p. 30
7.2.4 Notification of AF on bearer events p. 32
7.3 Provision of Charging Rules triggered by other event to the CRF p. 33
7.4 TPF initiated Bearer Service Termination p. 34
A Overall architectural impacts of IP flow based charging p. 36
A.1 GGSN in HPLMN p. 36
A.2 Comparison of S-CDR and G-CDR fields p. 36
A.2.1 S-CDR information missing from G-CDR p. 36
A.2.2 Served IMEI p. 36
A.2.3 MS Network Capability p. 37
A.2.4 LAC/RAC/CI at "record opening" p. 37
A.2.5 Access Point Name Operator Identifier p. 37
A.2.6 System Type p. 37
A.2.7 CAMEL information p. 38
A.2.8 RNC unsent data volume p. 38
A.2.9 Time zone of the user's location p. 38
A.3 RADIUS attributes p. 39
B IMS and Flow based charging p. 40
B.1 IMS SIP signalling p. 40
B.2 IMS media p. 40
B.3 FBC with IMS compared to release 5 IMS charging correlation p. 42
B.4 Rx/Gx functions and SBLP usage p. 42
C WLAN and flow based charging p. 43
C.1 TPF usage for WLAN p. 43
D Policy functions provided by FBC architecture p. 44
D.1 General p. 44
D.2 General architectural considerations p. 44
D.2.1 Charging correlation p. 44
D.2.2 Gating p. 45
D.2.3 QoS control p. 45
D.2.4 Bearer events p. 45
D.2.5 Session events p. 46
D.3 Summary and comparison p. 47
$ Change history p. 48
