ETSI TS 132 255 V15.5.0 (2020-01)

TECHNICAL SPECIFICATION
5G;
Telecommunication management;
Charging management;
5G data connectivity domain charging;
Stage 2
(3GPP TS 32.255 version 15.5.0 Release 15)

3GPP TS 32.255 version 15.5.0 Release 15 1 ETSI TS 132 255 V15.5.0 (2020-01)

Reference
RTS/TSGS-0532255vF50
Keywords
5G
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2020.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3GPP TS 32.255 version 15.5.0 Release 15 2 ETSI TS 132 255 V15.5.0 (2020-01)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 32.255 version 15.5.0 Release 15 3 ETSI TS 132 255 V15.5.0 (2020-01)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope. . 7
2 References . 7
3 Definitions, symbols and abbreviations . 8
3.1 Definitions . 8
3.2 Symbols . 8
3.3 Abbreviations . 9
4 Architecture considerations . 9
4.1 High-level 5G System architecture . 9
4.1.1 Non-roaming reference architecture . 9
4.1.2 Roaming Home Routed reference architecture . 10
4.1.3 Interworking with EPC architecture . 10
4.1.4 Architecture reference for Non-3GPP Accesses . 11
4.2 5G data connectivity domain converged charging architecture . 12
5 5G data connectivity charging principles and scenarios . 12
5.1 5G data connectivity charging principles . 12
5.1.1 General . 12
5.1.2 Requirements . 13
5.1.3 Charging information . 13
5.1.4 Charging Identifier . 14
5.1.5 PCC rules and charging . 14
5.1.5.1 PCC rules and chargeable events . 14
5.1.5.2 Specific PCC rules scenarios. 15
5.1.6 Session and Service Continuity modes . 15
5.1.7 UE Presence in Presence Reporting Area (PRA) . 15
5.1.8 CHF selection . 15
5.1.9 Roaming . 16
5.1.9.1 General . 16
5.1.9.2 CHF selection . 16
5.1.10 Data Volume Reporting for Secondary RAT usage . 16
5.2 5G data connectivity converged online and offline charging scenarios . 17
5.2.1 Basic principles . 17
5.2.1.1 General . 17
5.2.1.2 Applicable Triggers in the SMF . 18
5.2.1.2.1 General . 18
5.2.1.2.2 Flow Based Charging (FBC) triggers . 18
5.2.1.2.2 QoS flow Based Charging (QBC) triggers . 18
5.2.1.3 PDU session charging . 19
5.2.1.4 Flow Based Charging (FBC) . 19
5.2.1.5 SSC Mode and Triggers . 25
5.2.1.6 QoS flow Based Charging . 27
5.2.1.7 Roaming QoS flow Based charging (QBC) . 30
5.2.1.8 Termination action . 30
5.2.1.9 Sponsored data connectivity charging . 31
5.2.2 Message flows . 31
5.2.2.1 General . 31
5.2.2.2 PDU session charging from SMF . 31
5.2.2.2.1 General . 31
5.2.2.2.2 PDU session establishment . 31
5.2.2.3 PDU session charging SSC Mode 1 from SMF . 33
ETSI
3GPP TS 32.255 version 15.5.0 Release 15 4 ETSI TS 132 255 V15.5.0 (2020-01)
5.2.2.3.1 General . 33
5.2.2.3.2 PDU session charging SSC Mode 1 . 33
5.2.2.4 PDU session Charging SSC Mode 2 from SMF . 34
5.2.2.4.1 General . 34
5.2.2.4.2 PDU session Charging SSC Mode 2 . 34
5.2.2.5 PDU session Charging SSC Mode 3 from SMF . 36
5.2.2.5.1 General . 36
5.2.2.5.2 PDU session Charging SSC Mode 3 . 36
5.2.2.6 PDU session Charging SSC Mode 3 IPv6 Multi Homed from SMF . 37
5.2.2.6.1 General . 37
5.2.2.6.2 PDU session Charging SSC Mode 3 IPv6 Multi Homed . 37
5.2.2.7 Addition of additional PDU Session Anchor and Branching Point or UL CL . 39
5.2.2.8 Removal of additional PDU Session Anchor and Branching Point or UL CL . 40
5.2.2.9 Change of additional PDU Session Anchor for IPv6 multi-homing or UL CL . 41
5.2.2.10 Simultaneous change of Branching Point or UL CL and additional PSA for a PDU Session. 42
5.2.2.11 PDU session charging for interworking with EPC . 44
5.2.2.11.1 General . 44
5.2.2.11.2 5GS to EPS handover using N26 interface . 44
5.2.2.11.3 EPS to 5GS handover using N26 interface . 46
5.2.2.12 PDU session charging for roaming in Home routed scenario . 47
5.2.2.12.1 General . 47
5.2.2.12.2 PDU session establishment . 47
5.2.2.12.3 PDU session modification . 49
5.2.2.12.4 PDU session release . 50
5.2.2.13 PDU session charging - non-3GPP access . 51
5.2.2.13.1 General . 51
5.2.2.13.2 PDU session establishment . 52
5.2.2.13.3 PDU session modification . 52
5.2.2.13.4 PDU session release . 53
5.2.3 CDR generation . 54
5.2.3.1 Introduction . 54
5.2.3.2 Triggers for CHF CDR . 54
5.2.3.2.1 General . 54
5.2.3.2.2 Triggers for CHF CDR charging information addition . 55
5.2.3.2.3 Triggers for CHF CDR partial record closure . 55
5.2.3.2.4 Triggers for CHF CDR closure . 56
5.2.3.3 Triggers for CHF CDR for roaming QBC. 56
5.2.3.3.1 General . 56
5.2.3.3.2 Triggers for CHF CDR charging information addition for roaming QBC . 56
5.2.3.3.3 Triggers for CHF CDR partial record closure for roaming QBC . 57
5.2.3.3.4 Triggers for roaming QBC CHF CDR closure . 57
5.2.4 Ga record transfer flows . 57
5.2.5 Bd CDR file transfer . 57
6. Definition of charging information . 57
6.1 Data description for 5G data connectivity charging . 57
6.1.1 Message contents . 57
6.1.1.1 General . 57
6.1.1.2 Charging Data Request message . 58
6.1.1.3 Charging data response message . 59
6.1.2 Ga message contents . 59
6.1.3 CDR description on the B interface . 59
d
6.1.3.1 General . 59
6.1.3.2 PDU session charging CHF CDR data . 59
6.1.3.3 Roaming QBC CHF CDR data . 62
6.2 5G data connectivity charging specific parameters . 62
6.2.1 Definition of 5G data connectivity charging information . 62
6.2.1.1 General . 62
6.2.1.2 Definition of PDU session charging information . 63
6.2.1.3 Definition of PDU Container information . 65
6.2.1.4 Definition of roaming QBC information . 66
6.2.1.5 Definition of QFI Container information . 66
ETSI
3GPP TS 32.255 version 15.5.0 Release 15 5 ETSI TS 132 255 V15.5.0 (2020-01)
6.2.2 Detailed message format for converged charging . 67
6.2.3 Formal 5G data connectivity charging parameter description . 70
6.2.3.1 5G data connectivity CHF CDR parameters . 70
6.2.3.2 5G data connectivity resources attributes . 70
Annex A (normative): Charging Characteristics . 71
A.1 General . 71
Annex B (informative): Change history . 72
History . 73

ETSI
3GPP TS 32.255 version 15.5.0 Release 15 6 ETSI TS 132 255 V15.5.0 (2020-01)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
3GPP TS 32.255 version 15.5.0 Release 15 7 ETSI TS 132 255 V15.5.0 (2020-01)
1 Scope.
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 [1], 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 [1].
The present document specifies the converged offline and online charging description for the 5G Data Connectivity
domain based on the functional stage 2 description in TS 23.501 [200], TS 23.502 [201] and TS 23.503 [202].
This charging description includes the converged offline and online charging architecture and scenarios specific to the
5G Data Connectivity domain, as well as the mapping of the common 3GPP charging architecture specified in
TS 32.240 [1] onto the 5G Data Connectivity domain.
It further specifies the structure and content of the CDRs for offline charging, and the charging events for converged
online and 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 [1].
- The parameters, abstract syntax and encoding rules for the CDRs are specified in TS 32.298 [51].
- A transaction based mechanism for the transfer of CDRs within the network is specified in TS 32.295 [54].
- 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 [52].
- The services, operations and procedures of charging, using Service Based Interface are specified in TS 32.290
[57].
- The charging service of 5G system is specified in TS 32.291 [58].
All references, abbreviations, definitions, descriptions, principles and requirements, used in the present document, that
are common across 3GPP TSs, are defined in TR 21.905 [100]. Those that are common across charging management in
3GPP networks/domains, services or subsystems are provided in the umbrella TS 32.240 [1] 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.
2 References
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] 3GPP TS 32.240: "Telecommunication management; Charging management; Charging
architecture and principles".
ETSI
3GPP TS 32.255 version 15.5.0 Release 15 8 ETSI TS 132 255 V15.5.0 (2020-01)
[2] - [50] Void.
[51] 3GPP TS 32.298: "Telecommunication management; Charging management; Charging Data
Record (CDR) parameter description".
[52] 3GPP TS 32.297: "Telecommunication management; Charging management; Charging Data
Record (CDR) file format and transfer".
[53] Void.
[54] 3GPP TS 32.295: "Telecommunication management; Charging management; Charging Data
Record (CDR) transfer".
[55-56] Void.
[57] 3GPP TS 32.290: "Telecommunication management; Charging management; 5G system; Services,
operations and procedures of charging using Service Based Interface (SBI)".
[58] 3GPP TS 32.291: " Telecommunication management; Charging management; 5G system;
Charging service, stage 3".
[59] - [99] Void.
[100] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[101] 3GPP TS 22.115: "Service aspects; Charging and billing".
[102] 3GPP TS 22.261: "Service requirements for next generation new services and markets".
[103] - [199] Void
[200] 3GPP TS 23.501:"System Architecture for the 5G System".
[201] 3GPP TS 23.502:"Procedures for the 5G System".
[202] 3GPP TS 23.503:"Policy and Charging Control Framework for the 5G System; Stage 2".
[203] - [299] Void
[300] - [399] Void.
[400] - [499] Void.
[500] - [599] Void.
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [100] and the following
apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP
TR 21.905 [100].
3.2 Symbols
For the purposes of the present document, the following symbols apply:
Bd Reference point for the CDR file transfer from the 5G Data connectivity CGF to the BD.
Ga Reference point for CDR transfer between a CDF and the CGF.
Nchf Service based interface exhibited by CHF.
ETSI
3GPP TS 32.255 version 15.5.0 Release 15 9 ETSI TS 132 255 V15.5.0 (2020-01)
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [100] and the following apply.
An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any,
in 3GPP TR 21.905 [100].
5GC 5G Core Network
5GS 5G System
ABMF Account Balance Management Function
AF Application Function
AMF Access and Mobility Management Function
AUSF Authentication Server Function
BD Billing Domain
CCS Converged Charging System
CDF Charging Data Function
CGF Charging Gateway Function
CHF Charging Function
CP Control Plane
CTF Charging Trigger Function
DNN Data Network Name
FBC Flow Based Charging
GPSI Generic Public Subscription Identifier
GUAMI Globally Unique AMF Identifier
N3IWF Non-3GPP InterWorking Function
NE Network Element
NEF Network Exposure Function
NF Network Function
NRF Network Repository Function
NSSF Network Slice Selection Function
OCF Online Charging Function
OCS Online Charging System
PCC Policy and Charging Control
PCF Policy Control Function
PEI Permanent Equipment Identifier
QBC Qos flow Based Charging
QFI QoS Flow Identifier
SMF Session Management Function
SSC Session and Service Continuity
SUPI Subscription Permanent Identifier
UDM Unified Data Management
UDR Unified Data Repository
UPF User Plane Function
4 Architecture considerations
4.1 High-level 5G System architecture
4.1.1 Non-roaming reference architecture
Figure 4.1.1.1 shows the 5G System high level architecture as defined in TS 23.501 [200] for 5G data connectivity, in
the service-based representation for Control Plane (CP) Network Functions.
ETSI
3GPP TS 32.255 version 15.5.0 Release 15 10 ETSI TS 132 255 V15.5.0 (2020-01)
NSSF NEF NRF PCF UDM AF
Npcf Nudm
Nnef Nnrf
Nnssf Naf
Nausf
Nsmf
Namf
AUSF SMF
AMF
N4
N2
UE N3
(R)AN UPF N6 DN
Figure 4.1.1.1: 5G System architecture
4.1.2 Roaming Home Routed reference architecture
Figure 4.1.2.1 shows the 5G System high level Roaming Home Routed architecture as defined in TS 23.501 [200] for
5G data connectivity, in the service-based representation for Control Plane (CP) Network Functions.
NEF NRF PCF UDM NRF
NEF NSSF
NSSF
Nnrf
Npcf
Nudm
Nnef Nnrf Nnef
Nnssf
Nnssf
N32
vSEPP
hSEPP
Nsmf
Namf Nsmf Nausf
Npcf
Naf
AMF SMF
SMF AUSF
AF
PCF
N
DN
N3 N9 UPF N6
UE (R)AN UPF
VPLMN HPLMN
Figure 4.1.2.1: Roaming 5G System architecture - home routed scenario in service-based interface
representation
4.1.3 Interworking with EPC architecture
Figure 4.1.3.1 shows the non-roaming architecture for interworking between 5GS and EPC/E-UTRAN as defined in
TS 23.501 [200] for 5G data connectivity.
ETSI
3GPP TS 32.255 version 15.5.0 Release 15 11 ETSI TS 132 255 V15.5.0 (2020-01)

HSS +
UDM
N10
PCF +
S6a
PCRF
N8
N7
SMF +
N15
PGW-C
S5-C
N4
UPF +
N11
PGW-U
S5-U
SGW
S11
N26
MME AMF
N3 N2
S1-U U
S1-MME
N1
E-UTRAN
NG-RAN
UE
UE
Figure 4.1.3.1: Non-roaming architecture for interworking between 5GS and EPC/E-UTRAN
4.1.4 Architecture reference for Non-3GPP Accesses
Figure 4.1.4.1 shows the non-roaming architecture for Non-3GPP Accesses as defined in TS 23.501 [200] for 5G data
connectivity.
N2
N11
3GPP
AMF SMF
Access
N3
N2
N4
N1
Data Network
N3IWF UPF
N3 N6
HPLMN
NWu
Y2
N1
Non-3GPP
Networks
Untrusted Non-
UE
3GPP Access
Y1
Figure 4.1.4.1: Non-roaming architecture for Non-3GPP Accesses
This reference architecture supports service based interfaces for AMF, SMF and other NFs not represented in the figure.

ETSI
3GPP TS 32.255 version 15.5.0 Release 15 12 ETSI TS 132 255 V15.5.0 (2020-01)
4.2 5G data connectivity domain converged charging
architecture
The SMF embedding the CTF, generates charging events towards the CHF for PDU connectivity converged online and
offline charging.
As described in TS 32.240 [1], the CTF generates charging events towards to the CHF for converged online and offline
charging processing. The CDRs generation is performed by the CHF acting as a CDF, which transfers them to the CGF.
Finally, the CGF creates CDR files and forwards them to the BD.
If the CGF is external, the CHF acting as a CDF, forwards the CDRs to the CGF across the Ga interface.
If the CGF is integrated, there is only one internal interface between the CHF and the CGF. In this case, the relationship
between CHF and CGF is 1:1. An integrated CGF may support the Ga interface from other CDFs.
When an external CGF is used, this CGF may also be used by other, i.e. non-5GCS, 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 Bd interface does not exist and is replaced by a proprietary solution internal to the BD.
Figure 4.2.1 depicts the architectural options for converged charging.
Billing Domain
SMF
Nchf
Bd
CGF
CTF
Billing Domain
SMF
Bd
Nchf Ga
CGF
CTF
Billing Domain
SMF
Nchf
Ga
CGF
CTF
Figure 4.2.1: 5G data connectivity converged charging architecture
Nchf is described in clauses 5.2.1 and 5.2.2, Ga in clause 5.2.4 and Bd in clause 5.2.5.
5 5G data connectivity charging principles and
scenarios
5.1 5G data connectivity charging principles
5.1.1 General
The charging functions specified for the 5G data connectivity charging:
- PDU session in SMF, refer to TS 23.501 [200];
ETSI
3GPP TS 32.255 version 15.5.0 Release 15 13 ETSI TS 132 255 V15.5.0 (2020-01)
- service data flows, within PDU session, refer to TS 23.503 [202].
- QoS flows within PDU session refer to TS 23.501 [200] and TS 23.503 [202].
5.1.2 Requirements
The following are high-level charging requirements specific to the packet domain, derived from the requirements in
TS 22.115 [101], TS 22.261 [102], TS 23.501 [200], TS 23.502 [201] and TS 23.503 [202].
- The SMF shall support converged online and offline charging.
- The SMF shall support PDU session charging using service based interface.
- The SMF shall support network slice instance charging.
- The SMF shall collect charging information per PDU session for UEs served under 3GPP access and non-3GPP
access.
- Every PDU session shall be assigned a unique identity number for billing purposes per PLMN. (i.e. the Charging
Id).
- Data volumes on both the uplink and downlink directions shall be counted separately. The data volumes shall
reflect the data as delivered to and forwarded from the user.
- The charging mechanisms shall provide the date and time information when the PDU session starts.
- The SMF shall be capable of handling the Charging Characteristics. Charging Characteristics can be specific to a
subscription or subscribed DNN.
- The SMF may be capable of identifying data volumes, elapsed time or events for individual service data flows
(flow based charging). One PCC rule identifies one service data flow.
- SMF shall allow reporting of the service or the detected application usage per rating group or per combination of
the rating group and service id. This reporting level can be activated per PCC rule.
- The quota management shall be per rating group per PDU session.
- If there are multiple UPFs for one PDU session, the quota management may be one for all UPFs or separate per
UPF and the usage and charging information reporting per UPF.
- The SMF shall support charging for PDU Session types of IP, Ethernet and Unstructured.
- In Home Routed scenario, the SMF shall collect charging information per PDU session and, based on Home
Operator policy and agreement between Home and Visit Operators, shall be able to collect charging information
per Qos Flow for in-bound and out-bound roamers in Home Routed scenario.
- For interworking between 5GS and EPC, the dedicated PGW-C + SMF shall collect charging information using
the same mechanisms as the SMF.
5.1.3 Charging information
Charging information in the 5GC domain network is collected for each UE by the SMFs. PDU session charging allows
the SMF to collect and categorize per UE per UPF per PDU session, charging information related to data volumes.
The SMF shall collect the following charging information for converged online and offline charging:
- usage of the access and core network resources: the charging information shall describe the amount of data
delivered to and forwarded from the UE;
- usage duration: duration of PDU session is counted as the time interval from PDU session establishment to PDU
session release;
- user: the charging information shall provide the actual UE addresses used by the user for the PDU session;
ETSI
3GPP TS 32.255 version 15.5.0 Release 15 14 ETSI TS 132 255 V15.5.0 (2020-01)
- data network: the charging information shall describe the data network addresses with a level of accuracy as
determined by the DNN;
- usage of the external data networks: the charging information shall describe the amount of data sent and received
to and from the external data network. External networks can be identified by the DNN;
- start time: identifying the time when the PDU session was started;
- user location: HPLMN, VPLMN, inside/outside presence reporting area, plus optional higher-accuracy location
information.
The service data flows categorization is achieved by rating group or combination of the rating group and service id: i.e.
based on the level of reporting defined per PCC rule, counting per rating group or combination of the rating group and
service id. According to TS 23.503 [202], flow based charging shall support different charging models per PCC rule.
These charging models may be based on volume, time and/or on number of events matching a specific service data flow
template in PCC rule.
For service data flows defined for FBC, the SMF shall collect the following charging information:
- the information described above for PDU session;
- the amount of data transmitted in uplink and downlink directions categorized by rating group or combination of
the rating group and service id when volume based charging applies;
- the duration of service data flows is counted and categorized by rating group or combination of the rating group
and service id when time based charging applies;
- the number of events and corresponding time stamps categorized by rating group or combination of the rating
group and service id when event based charging applies.
Within the PDU session the SMF shall collect the charging information for service data flows per UPF, categorized
with rating group or combination of the rating group and service id.
The user can be identified by a Generic Public Subscription Identifier (GPSI) and/or a 5G Subscription Permanent
Identifier (SUPI).
5.1.4 Charging Identifier
Charging identifier is created to allow correlation of charging information.
For the SMF the charging identifier is assigned per PDU session. At each PDU session establishment a new, i.e.
assignment of a new PDU session id, PDU session specific SMF Charging Identifier is generated at the first SMF that
processes the PDU session initiating request. This SMF Charging Identifier shall be unique within the SMF and is then
used in all subsequent messages for that PDU session. The Charging Identifier shall be used throughout the PDU
session’s lifetime once assigned. In case of inter-system changes or handovers of PDU session, the Charging Identifier
is preserved as long as the PDU session Identifier is preserved.
5.1.5 PCC rules and charging
5.1.5.1 PCC rules and chargeable events
PCC rules can be activated, deactivated and modified at any time during the PDU session lifetime. The following
attribute can be modified by the PCF in a dynamic PCC rule active in the SMF: Charging key, Service identifier,
Sponsor Identifier, Application Service Provider Identifier, Measurement method and reporting level. The QoS Flow
binding mechanism employed by the SMF upon operations on PCC rules, may result in QoS Flows establishment,
modification, or release. This is specified in TS 23.503 [202].
Activities on PCC rules are not chargeable events. However, change of charging rule in PCC rules will lead to
chargeable events "start of service data flow" and when this is the last service data flow for the original PCC rule,
"termination of service data flow".
The charging key (i.e. Rating group) is a piece of information used to request online charging quotas as defined in
TS 23.503 [202].
ETSI
3GPP TS 32.255 version 15.5.0 Release 15 15 ETSI TS 132 255 V15.5.0 (2020-01)
5.1.5.2 Specific PCC rules scenarios
The capability of SMF to support Application Based Charging is achieved with appropriate PCC rules activation in the
SMF. Such PCC Rule shall be defined with service data flow template including an Application Identifier for the
application which needs to be detected, enforced and charged. The application detection mechanism in SMF is defined
in TS 23.503 [202].
5.1.6 Session and Service Continuity modes
For any scenario of SSC modes specified in TS 23.501 [200], one charging Id shall correspond to a single PDU session
ID.
As a result from such SSC mode, a new charging Id is generated by the SMF for the new PDU session Id, and the
charging session associated to the old PDU session Id is released.
This behaviour applies to the following scenario:
- PDU session anchor UPF relocation, in SSC mode 2;
- PDU session anchor UPF relocation in SSC mode 3 with multiple PDU Sessions.
5.1.7 UE Presence in Presence Reporting Area (PRA)
During charging session lifetime , the CHF may provide the Presence Reporting Area identifier to be activated for Core
Network pre-configured Presence Reporting Area(s) and additionally all of PRA Identifier(s) and list(s) of its elements
for UE-dedicated Presence Reporting Area(s) and provision the "Change of UE presence in Presence Reporting
Area(s)" re-authorization trigger to the SMF to request the reporting of Change of UE presence in Presence Reporting
Area. After such trigger is enabled, SMF shall close the current count, open a new count with the initial status of UE
presence in the PRA(s). In case of quota management is required, a Charging Data Response [Update] including the
initial status is sent. UE presence status in the PRA(s) describes whether the UE is entering or leaving Presence
...