The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS/LTE networks. The GSM/UMTS/LTE 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 Charging description for Monitoring Events, based on the functional stage 2 description in TS 23.682. This charging description includes the offline charging architecture and scenarios specific to Monitoring Events, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 onto the 3GPP Architecture for Service Capability Exposure. 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 Monitoring Event offline charging is specified in TS 32.299.
The online charging functionality for Monitoring Events is outside the scope of 3GPP standardisation.
All references, abbreviations, definitions, descriptions, principles and requirements, used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905. Those that are common across charging management in GSM/UMTS/LTE domains, services or subsystems are provided in the umbrella document TS 32.240 and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
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.
Recommendation ITU-T X.25: "Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit".
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
2G / 3G:
prefixes 2G and 3G refer to functionality that supports only GSM or UMTS, respectively, e.g. 2G SGSN refers only to the GSM functionality of an SGSN.
process of apportioning charges between the Home Environment, Serving Network and Subscriber.
information / data specific to an application other than the MMS User Agent / VASP which is intended to be transported without alteration by using MMS.
function whereby CDRs generated by the charging function(s) are transformed into bills requiring payment.
part of the operator network, which is outside the telecommunication network, that receives and processes CDR files from the core network charging functions.
CDR field categories:
the CDR fields are defined in the present document. CDR fields may be operator provisionable and are divided into the following categories:
Mandatory (M): field that shall always be present in the CDR.
Conditional (C): field that shall be present in a CDR if certain conditions are met.
Operator Provisionable: Mandatory (OM): field that, if provisioned by the operator, shall always be present in the CDR.
Operator Provisionable: Conditional (OC): field that, if provisioned by the operator, shall be present in a CDR if certain conditions are met.
activity utilizing telecommunication network resources and related services for:
user to user communication (e.g. a single call, a data communication session or a short message); or
user to network communication (e.g. service profile administration); or
inter-network communication (e.g. transferring calls, signalling, or short messages); or
mobility (e.g. roaming or inter-system handover); and
that the network operator may want to charge for.
user involved in a chargeable event who has to pay parts or the whole charges of the chargeable event, or a third party paying the charges caused by one or all users involved in the chargeable event, or a network operator.
function within the telecommunications network and the associated OCS/BD components whereby information related to a chargeable event is collected, formatted, transferred and evaluated in order to make it possible to determine usage for which the charged party may be billed (offline charging) or the subscriber's account balance may be debited (online charging).
Charging Data Record (CDR):
formatted collection of information about one or more chargeable event(s) (e.g. time of call set-up, duration of the call, amount of data transferred, etc) for use in billing and accounting.
set of charging information forwarded by the CTF towards the CDF (offline charging) or towards the OCS (online charging).
entity inside the core network domain, subsystem or service that is involved in charging for that domain, subsystem or service.
feedback information provided to an originator MMS User Agent by an MMS Relay/Server about the status of the delivery of an MM.
part of a communication network that provides network resources using a certain bearer technology.
qualifier indicating that this clause or paragraph applies only to a GSM system.
qualifier indicating that this paragraph applies only to GSM System.
qualifier indicating that this paragraph applies only to UMTS System.
change of radio access between different radio access technologies such as GSM, UMTS and LTE.
"middle tier" (charging) TS:
term used for the 3GPP charging TSs that specify the domain / subsystem / service specific, online and offline, charging functionality.
charging mechanism where charging information does not affect, in real-time, the service rendered.
charging mechanism where charging information can affect, in real-time, the service rendered and therefore a direct interaction of the charging mechanism with bearer/session/service control is required.
online charging system:
the entity that performs real-time credit control. Its functionality includes transaction handling, rating, online correlation and management of subscriber account balances.
packet switched domain:
domain within GSM/UMTS/LTE in which data is transferred in packet switched mode. Corresponds to the term "GPRS".
CDR that provides charging information on part of a subscriber session. A long session may be covered by several partial CDRs.
payment of amounts resulting from the accounting process.
entity (associated with one or more users) that is engaged in a subscription with a service provider.
connection that reaches the communication or data transfer phase e.g. the "answered" state for speech connections.
UE being positioned.
part of one (calendar) day during which a particular tariff is applied. Defined by the time at which the period commences (the switch-over time) and the tariff to be applied after switch-over.
set of parameters defining the network utilisation charges for the use of a particular bearer / session / service.
qualifier indicating that this clause or paragraph applies only to a UMTS system.
entity, not part of the 3GPP System, that uses network resources by means of a subscription.
User Equipment (UE):
device allowing a user access to network services.
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.
3rd Generation Partnership Project
Account Balance Management Function
Access Point Name
Attribute Value Pair
Charging Collection Function
Charging Data Function
Charging Data Record
Charging Gateway Function
Charging Rules Function
Charging Trigger Function
Diameter Credit Control Application
Event Based Charging Function
Event Charging with Unit Reservation
Furnish Charging Information
Fully Qualified Partial CDR
File Transfer, Access and Management
GGSN (PDP context) generated - CDR
Gateway GPRS Support Node
General Packet Radio Service
Global System for Mobile communication
Home Location Register
Home Subscriber Server
Immediate Event Charging
Internet Engineering Task Force
International Mobile Equipment Identity
International Mobile Subscriber Identity
Internet Protocol version 4
Internet Protocol version 6
Integrated Services Digital Network
Mobility management generated - Charging Data Record
Figure 4.1.1 shows the overall architecture for Service Capability Exposure which enables the 3GPP network to securely expose its services and capabilities provided by 3GPP network interfaces to external 3rd party service provider applications, which includes Monitoring Event functionality, as described in TS 23.682.
[not reproduced yet]
Figure 4.1.1: 3GPP Architecture for Service Capability Exposure
For roaming case, the Interworking SCEF (IWK-SCEF) is optionally deployed and located in the VPLMN, as described in figure 4.1.2.
[not reproduced yet]
Figure 4.1.2: 3GPP roaming Architecture for Service Capability Exposure
As described in TS 32.240, the CTF (an integrated component in each charging relevant NE) generates charging events and forwards them to the CDF. The CDF, in turn, generates CDRs which are then transferred to the CGF.
Finally, the CGF creates CDR files and forwards them to the BD.
For offline charging the following Monitoring Event Charging Nodes (MECN), functioning as the CTF, may generate accounting metrics sets for Monitoring Event CDRs:
the MME, to record Monitoring Events;
the SGSN, to record Monitoring Events;
the IWK-SCEF, to record Monitoring Events.
If the MECN generating the charging information has an integrated CDF, then the MECN can produce CDRs. The CGF may also be integrated in the MECN, or it may exist as a physically separate entity.
If the CGF is external to the MECN/CDF, then the MECN/CDF forwards the CDRs to the CGF across the Ga interface. In this case, the relationship between MECN/CDF and CGF is m:1.
If the CGF is integrated in the MECN/CDF, then there is only an internal interface between the CDF and the CGF. In this case, the relationship between MECN/CDF and CGF is 1:1. An integrated CGF may support the Ga interface from other MECN/CDFs.
If the CDF is external to the MECN, the charging events are transferred from the MECN to the CDF via the Rf interface specified in TS 32.299. In this case, the relationship between MECN and CDF is m:1.
When an external CGF is used, this CGF may also be used by other, i.e. non-Monitoring Event, network elements, according to network design and operator decision. It should be noted that the CGF may also be an integrated component of the BD - in this case, the Bmn interface does not exist and is replaced by a proprietary solution internal to the BD.
Figure 4.2.1 depicts the architectural options described above.