Content for TS 32.240 Word version: 19.0.0

1… 3… 4… 4.2.3 4.2.4 4.3… 4.4… 4.5… 5… 5.3… A… C… D… E… F… G…

4.4 Reference points 4.4.1 Offline charging reference points 4.4.1.1 Rf 4.4.1.2 Gz 4.4.1.3 Ga 4.4.1.4 Bx 4.4.1.6 Gzn 4.4.2 Online charging reference points 4.4.2.1 Ro 4.4.2.2 CAP 4.4.2.3 Gy 4.4.2.4 Re 4.4.2.5 Rc 4.4.2.7 Gyn 4.4.3 Charging services Reference point
...

4.4 Reference points p. 38

4.4.1 Offline charging reference points p. 38

4.4.1.1 Rf p. 38

The Rf reference point supports interaction between a CTF and a CDF. The following information may flow across this reference point in real-time:

Charging events for offline charging from the CTF to the CDF;
Acknowledgements for these events from the CDF to the CTF.

The protocol(s) crossing this reference point shall support the following capabilities:

Real-time transactions;
Stateless mode ("event based charging") and statefull mode ("session based charging") of operation;
Provide its own reliability mechanisms, e.g. retransmission of charging events, to run also on unreliable transport.

In addition, the protocol should support changeover to a secondary destination (alternate CDF(s)) in case of the primary CDF not being reachable.

This interface application is defined in TS 32.299. The information contained in the charging events and the relevant chargeable events are specific to the domain / subsystem / service and are detailed in the respective middle tier TSs.

4.4.1.2 Gz p. 38

The Gz reference point is functionally equivalent to Ga for Legacy PS domain and to Ga or Rf for Evolved PS domain, and hence is replaced by Ga or Rf within the common charging architecture. See also clause 4.2.

4.4.1.3 Ga p. 38

The Ga reference point supports interaction between a CDF and a CGF. The following information may flow across this reference point:

CDRs are sent from the CDF to the CGF;
Acknowledgements for these CDRs are returned from the CGF to the CDF.

The protocol(s) crossing this reference point shall support the following capabilities:

Near real-time transactions;
Send one or more CDRs in a single request message;
Changeover to secondary destinations (alternate CGFs) in case of the primary CGF not being reachable;
Provide its own reliability mechanisms, e.g. retransmission of charging events, to run also on unreliable transport.

This interface application is defined in TS 32.295. The content of the CDRs, and the CDR trigger conditions, are specific to the domain / subsystem / service and are detailed in the middle tier TSs.

4.4.1.4 Bx p. 38

The Bx reference point supports interaction between a CGF and the BD. The information crossing this reference point is comprised of CDR files. A common, standard file transfer protocol (e.g. FTAM, FTP) shall be used, including the transport mechanisms specified for the selected protocol.

This interface application is defined in TS 32.297. The information contained in the files corresponds to the CDRs defined per domain/subsystem/service, as stated in clause 4.4.1.3.

4.4.1.5 Void

4.4.1.6 Gzn |R12| p. 39

The Gzn reference point is functionally equivalent to Ga or Rf in PS domain, and hence is replaced by Ga or Rf within the common charging architecture. See also clause 4.2.

4.4.2 Online charging reference points p. 39

4.4.2.1 Ro p. 39

The Ro reference point supports interaction between a CTF and an OCF. The following information may flow across this reference point:

Charging events for online charging from the CTF to the OCF.
Receive Acknowledgements for these charging events from the OCF to the CTF. The acknowledgement grants or rejects the network resource usage requested in the charging event, according to the decision taken by the OCS.

The protocol(s) crossing this reference point shall support the following capabilities:

Real-time transactions;
Stateless mode ("event based charging") and statefull mode ("session based charging") of operation;

NOTE:
For "event based charging", the protocol may be stateless, however Internal implementation of the CTF and OCF may be stateful across the different charging events.
Provide its own reliability mechanisms, e.g. retransmission of charging events, to run also on unreliable transport.

In addition, the protocol should support changeover to a secondary destination (alternate OCF(s)) in case of the primary OCF not being reachable.

4.4.2.2 CAP p. 39

The CAP reference point provides similar functionality for online charging as Ro, however, it is based on CAMEL techniques. It is kept within the overall charging architecture as CAMEL may be used in the CS and PS domains. See TS 23.078 for details on CAMEL.

4.4.2.3 Gy p. 39

The Gy reference point is functionally equivalent to Ro, and hence is replaced by Ro within the common charging architecture. See also clause 4.2.

4.4.2.4 Re p. 39

The Re reference point supports interaction between the OCF and a Rating Function (RF) in order to determine the value of chargeable events in terms of monetary or non-monetary units. This interface application is defined in TS 32.296.

4.4.2.5 Rc p. 39

The Rc reference point allows the interaction between the OCF and an Account Balance Management Function (ABMF) in order to access the account of the subscriber on the OCS. See TS 32.296 for further information.

4.4.2.6 Void

4.4.2.7 Gyn |R12| p. 40

The Gyn reference point is functionally equivalent to Ro, and hence is replaced by Ro within the common charging architecture. See also clause 4.2.

4.4.3 Charging services Reference point |R17| p. 40

The common charging architectures are mapped into the specific domain/subsystem/service charging architectures in the respective middle tier TSs, which contain in their reference point representation, the following reference points:

N28:

Reference point between PCF and CHF defined in TS 23.501.

N40:

Reference point between SMF and the CHF in the same PLMN defined in clause 4.2 of TS 32.255.

N41:

Reference point between AMF and CHF in different PLMNs defined in clause 4.2 of TS 32.256.

N42:

Reference point between AMF and CHF in the same PLMN defined in clause 4.2 of TS 32.256.

N44:

Reference point between NEF and CHF defined in clause 4.4 of TS 32.254.

N45:

Reference point between IMS Node and CHF defined in clause 4.4 of TS 32.260.

N46:

Reference point between SMSF and CHF defined in clause 4.4 of TS 32.274.

N47:

Reference point between SMF and the CHF in different PLMNs defined in clause 4.2 of TS 32.255.

N48:

Reference point between 5G DDNMF and the CHF in different PLMNs defined in clause 4.4 of TS 32.277.

N49:

Reference point between EES and CHF defined in clause 4.2.3 of TS 32.257.

N100:

Reference point between MMS node and CHF defined in clause 4.4 of TS 32.270.

N101:

Reference point between MB-SMF and the CHF in the same PLMN defined in clause 4.2 of TS 32.279.

N102:

Reference point between NSACF and the CHF defined in clause 4.2.1 of TS 28.203.

N103:

Reference point between NSSAAF and the CHF defined in clause 4.2.1 of TS 28.204.

N104:

Reference point between TSN AF and CHF defined in clause 4.2 of TS 32.282.

N105:

Reference point between TSCTSF and CHF defined in clause 4.2 of TS 32.282.

N106:

Reference point between GMLC and CHF defined in clause 4.4 of TS 32.271.

N107:

Reference point between two CHFs (V-CHF and H-CHF) defined in clause 4.2 of TS 32.255 and clause 4.2 of TS 32.256.

N108:

Reference point between two CHFs (C-CHF to B-CHF) defined in clause 4.3 of TS 32.255 and clause 4.3 of TS 32.256.