Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 32.254  Word version:  17.3.0

Top   Top   None   None   Next
1…   4…

 

1  Scopep. 7

The present document is part of a series of documents that specify charging functionality and charging management in 3GPP networks. The 3GPP core network charging architecture and principles are specified in TS 32.240, which provides an umbrella for other charging management TSs that specify:
  • the content of the CDRs per domain / subsystem / service (offline charging);
  • the content of real-time charging messages per domain / subsystem / service (online charging);
  • the functionality of online and offline charging for those domains / subsystems / services;
  • the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events).
The complete document structure for these TSs is defined in TS 32.240.
The present document specifies the offline, online and converged charging description for Northbound Application Program Interfaces (API), based on the functional stage 2 description in TS 23.682 for transaction over T8 reference point between SCEF and SCS/AS and in TS 23.501 for Network Exposure Function (NEF). This charging description includes the offline, online and converged charging architecture and scenarios specific to Northbound Application Program Interfaces (API), as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 onto the Northbound Application Program Interfaces (API). It further specifies the structure and content of the CDRs for offline charging. The present document is related to other 3GPP charging TSs as follows:
  • The common 3GPP charging architecture is specified in TS 32.240.
  • The parameters, abstract syntax and encoding rules for the CDRs are specified in TS 32.298.
  • A transaction based mechanism for the transfer of CDRs within the network is specified in TS 32.295.
  • The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g. the billing system or a mediation device) is specified in TS 32.297.
  • The 3GPP Diameter application that is used for Northbound Application Program Interfaces (API) offline and online charging is specified in TS 32.299.
  • The services, operations and procedures of charging, using Service Based Interface are specified in TS 32.290.
  • The charging service of 5G system is specified in TS 32.291.
Up

2  Referencesp. 7

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles".
[2] - [49]  Void.
[50]
TS 32.299: "Telecommunication management; Charging management; Diameter charging application".
[51]
TS 32.298: "Telecommunication management; Charging management; Charging Data Record (CDR) parameter description".
[52]
TS 32.297: "Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer".
[53]
TS 32.296: "Telecommunication management; Charging management; Online Charging System (OCS): Applications and interfaces".
[54]
TS 32.295: "Telecommunication management; Charging management; Charging Data Record (CDR) transfer".
[55] - [56]  Void.
[57]
TS 32.290: "Telecommunication management; Charging management; 5G system; Services, operations and procedures of charging using Service Based Interface (SBI)".
[58]
TS 32.291: "Telecommunication management; Charging management; 5G system; Charging service, stage 3".
[59] - [99]  Void.
[100]
TR 21.905: "Vocabulary for 3GPP Specifications".
[101] - [199]  Void
[200]
TS 23.501: "System Architecture for the 5G System".
[201]
TS 23.502: "Procedures for the 5G System".
[202] - [229]  Void
[230]
TS 29.122: "T8 reference point for northbound Application Programming Interfaces (APIs)".
[231] - [242]  Void
[243]
TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[244] - [299]  Void
[300] - [399]  Void.
Up

3  Definitions, symbols and abbreviationsp. 8

3.1  Definitionsp. 8

For the purposes of the present document, the terms and definitions given in TR 21.905, TS 32.240 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in either TR 21.905 or TS 32.240.
Up

3.2  Symbolsp. 9

For the purposes of the present document, the following symbols apply:
Bea
Reference point for the CDR file transfer from the Exposure function API CGF to the BD.
Ga
Reference point for CDR transfer between a CDF and the CGF.
Nchf
Service based interface exhibited by CHF.
N44
Reference point between the NEF and the CHF
Rf
Offline charging reference point between a SCEF and the CDF.
Ro
Online charging reference point between a SCEF and the CDF.
T8
Reference point between the SCEF and SCS/AS.

3.3  Abbreviationsp. 9

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
AS
Application Server
BD
Billing Domain
CDF
Charging Data Function
CGF
Charging Gateway Function
CTF
Charging Trigger Function
ECUR
Event Charging with Unit Reservation
IE
Information Element
IEC
Immediate Event Charging
NEF
Network Exposure Function
PEC
Post Event Charging
SCEF
Service Capability Exposure Function
SCS
Services Capability Server
SGSN
Serving GPRS Support Node
RCAF
RAN Congestion Awareness Function
Up

Up   Top   ToC