|
TECHNICAL SPECIFICATION
5G;
Telecommunication management;
Charging management;
5G system;
Services, operations and procedures of charging using
Service Based Interface (SBI)
(3GPP TS 32.290 version 15.3.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 32.290 version 15.3.0 Release 15 1 ETSI TS 132 290 V15.3.0 (2019-05)
Reference
RTS/TSGS-0532290vf30
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:
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
If you find errors in the present document, please send your comment to one of the following services:
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 2019.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
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
---------------------- Page: 2 ----------------------
3GPP TS 32.290 version 15.3.0 Release 15 2 ETSI TS 132 290 V15.3.0 (2019-05)
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.
Foreword
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, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
.
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
---------------------- Page: 3 ----------------------
3GPP TS 32.290 version 15.3.0 Release 15 3 ETSI TS 132 290 V15.3.0 (2019-05)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions, symbols and abbreviations . 7
3.1 Definitions . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 Architecture reference model . 7
4.1 General . 7
4.2 Reference architecture . 7
5 Charging function requirement . 8
5.1 Offline charging scenario . 8
5.1.1 Basic principles . 8
5.1.2 Charging scenarios . 8
5.1.2.1 Introduction . 8
5.1.2.2 Scenarios . 8
5.2 Online charging scenario . 8
5.2.1 Basic principles . 8
5.2.2 Charging scenarios . 8
5.2.2.1 Introduction . 8
5.2.2.2 Scenarios . 9
5.2.3 Void . 9
5.3 Converged Charging scenario . 9
5.3.1 Basic principles . 9
5.3.2 Charging scenarios . 9
5.3.2.1 Introduction . 9
5.3.2.2 Event based charging . 9
5.3.2.3 Session based charging . 10
5.4 Other functionalities . 19
5.4.1 Re-authorization . 19
5.4.2 Threshold based re-authorization triggers . 19
5.4.3 Termination action . 19
5.4.4 Service termination . 19
5.4.5 Trigger Mechanism . 19
5.5 Error handling . 20
5.5.1 Failure handling . 20
5.5.1.1 CTF detected failure . 20
5.5.1.2 CHF detected failure . 20
5.5.2 Retry handling . 20
6 Service Definition . 20
6.1 NF Service Framework . 20
6.2 Nchf_ConvergedCharging service . 21
6.2.1 General . 21
6.2.2 Nchf_ConvergedCharging_Create service operation. 21
6.2.3 Nchf_ConvergedCharging_Update service operation . 21
6.2.4 Nchf_ConvergedCharging_Release service operation. 22
6.2.5 Nchf_ConvergedCharging_Notify service operation . 22
6.3 Nchf_SpendingLimitControl service . 22
6.3.1 Overview . 22
6.4 Void . 23
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 32.290 version 15.3.0 Release 15 4 ETSI TS 132 290 V15.3.0 (2019-05)
7 Message contents . 23
Annex A (informative): Change history . 27
History . 28
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 32.290 version 15.3.0 Release 15 5 ETSI TS 132 290 V15.3.0 (2019-05)
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
---------------------- Page: 6 ----------------------
3GPP TS 32.290 version 15.3.0 Release 15 6 ETSI TS 132 290 V15.3.0 (2019-05)
1 Scope
The present document specifies service, operations and procedures of 5G charging for service based interface. This
charging description includes the charging architecture and scenarios as well as the mapping of the common charging
architecture specified in TS 32.240 [1]. 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 protocol that are used for service based interface is specified in TS 32.291 [58].
The description is following the same methodology as used in TS 23.501 [201] and TS 23.502 [202] for the 5G system.
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".
[2] - [49] Void.
[50] 3GPP TS 32.299: "Telecommunication management; Charging management; Diameter charging
application".
[51] - [54] Void.
[55] - [57] Void.
[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] - [200] Void.
[201] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[202] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[203] - [206] Void.
[207] - [299] Void.
[300] 3GPP TS 29.510: " 5G System; Network function repository services; Stage 3".
[301] - [370] Void.
[371] - [399] Void.
[400] - [499] Void.
[500] - [599] Void.
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 32.290 version 15.3.0 Release 15 7 ETSI TS 132 290 V15.3.0 (2019-05)
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], TS 32.240 [1] and
the following apply. A term defined in the present document takes precedence over the definition of the same term, if
any, in either 3GPP TR 21.905 [100] or TS 32.240 [1].
5G Access Network: An access network comprising a NG-RAN and/or non-3GPP AN connecting to a 5G Core
Network.
5G Core Network: The core network specified in the present document. It connects to a 5G Access Network.
NF service: a functionality exposed by a NF through a service based interface and consumed by other authorized NFs.
NF service operation: An elementary unit a NF service is composed of.
service based interface: It represents how a set of services is provided/exposed by a given NF.
charging session: The association between the CHF (NF Service Producer) that provides the charging service and NF
service consumer.
3.2 Symbols
For the purposes of the present document, the following symbols apply:
Nchf Service-based interface exhibited by Charging Function.
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
CCS Converged Charging System
CHF Charging Function
IEC Immediate Event Charging
NF Network Function
PCF Policy Control Function
SBI Service based Interface
SMSF Short Message Service Function
SMF Session Management Function
4 Architecture reference model
4.1 General
The present document describes the service based architecture for 5G Charging.
4.2 Reference architecture
The NFs with CTF interact with CHF using Nchf interface for converged online and offline charging. The NF PCF
interacts with CHF using Nchf interface for Spending Limit Control. The Nchf is a service based interface for NF and
CHF.
Figure 4.2.1 depicts the reference architecture for the Nchf Interface.
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 32.290 version 15.3.0 Release 15 8 ETSI TS 132 290 V15.3.0 (2019-05)
Figure 4.2.1: Reference Architecture for the Nchf Interface; SBI representation
5 Charging function requirement
5.1 Offline charging scenario
5.1.1 Basic principles
Basic principles for offline charging are defined in TS 32.240 [1].
5.1.2 Charging scenarios
5.1.2.1 Introduction
Offline charging for both events and sessions based charging as defined in TS 32.240 [1].
Two basic scenarios are used:
- Event based charging;
- Session based charging.
Both these scenarios may generate CDR files, which may then be transferred to the network operator's BD for the
purpose of subscriber billing and/or inter-operator accounting.
5.1.2.2 Scenarios
The scenarios described in TS 32.299 [50] clauses 5.1.1.1 and 5.1.1.2 apply with the CHF acting as a CDF.
5.2 Online charging scenario
5.2.1 Basic principles
Basic principles for online charging are defined in TS 32.240 [1].
5.2.2 Charging scenarios
5.2.2.1 Introduction
The following basic scenarios are used:
1 Immediate Event Charging
a) Decentralized Unit Determination and Centralized Rating
b) Centralized Unit Determination and Centralized Rating
c) Decentralized Unit Determination and Decentralized Rating
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 32.290 version 15.3.0 Release 15 9 ETSI TS 132 290 V15.3.0 (2019-05)
2 Event charging with Unit Reservation
a) Decentralized Unit Determination and Centralized Rating
b) Centralized Unit Determination and Centralized Rating
c) Decentralized Unit Determination and Decentralized Rating
3 Session charging with Unit Reservation
a) Decentralized Unit Determination and Centralized Rating
b) Centralized Unit Determination and Centralized Rating
c) Decentralized Unit Determination and Decentralized Rating
The combination of Centralized Unit Determination with Decentralized Rating is not possible.
5.2.2.2 Scenarios
The scenarios described in TS 32.299 [50], clauses 5.2.2.1, 5.2.2.2 and 5.2.2.3, apply with the CHF acting as an OCF.
5.2.3 Void
5.3 Converged Charging scenario
5.3.1 Basic principles
When offline charging and online charging are both applicable to a service delivery, the charging information of both
offline charging and online charging can be provided in a single command, upon any triggers of the offline charging or
online charging is occur.
5.3.2 Charging scenarios
5.3.2.1 Introduction
Converged charging for both events and sessions between CTF and the CHF is performed as defined in TS 32.240 [1].
Two basic scenarios are used:
- Converged Event based charging;
- Converged Session based charging.
5.3.2.2 Event based charging
For Converged Event based Charging, Immediate Event Charging (IEC) is supported .
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 32.290 version 15.3.0 Release 15 10 ETSI TS 132 290 V15.3.0 (2019-05)
Figure 5.3.2.2.1 shows a scenario for Event based charging with: Decentralized and Centralized Unit Determination,
Centralized Rating configurationand user's account balance deduction before service delivery, where the NF (CTF)
may invoke converged charging service towards the CHF, prior to service delivery if needed.
NF
CHF
(CTF)
1. Request for resource usage
Delivery procedure
2. Units Determination
3. Charging Data Request [ Event, Units ]
4. Account,Rating
Control
5. Create CDR
6. Charging Data Response [ Event, Units ]
7. Granted Units
Supervision
8 Content/Service Delivery
Figure 5.3.2.2.1: IEC- Event based charging with Decentralized and Centralized Unit Determination,
Centralized Rating
1) Request for resource usage: A request for session establishment is received in the NF (CTF). The service is
configured to be authorized by the CHF to start.
2) Units Determination: the NF (CTF) determines the number of units depending on the service requested by the
UE in "Decentralized Units determination" scenario.
3) Charging Data Request [Event, Units]: The NF (CTF) sends the request to the CHF for the service to be
granted authorization, and to allow the number of units, if determined in item 2, to be rated and accounted.
4) Account, Rating Control: The CHF calculates the number of monetary units that represents the price and
makes deduction of the calculated amount from user's account balance based on the number of units requested or
on internal unit determination, if the user's credit balance is sufficient.
5) Create CDR: based on policies, the CHF creates a CDR related to the service.
6) Charging Data Response [Event, Units]: The CHF grants authorization to NF (CTF) for the service to start,
with a number of granted units.
7) Granted Units Supervision: The service starts and the NF (CTF) monitors the consumption of the granted
units.
8) Content/Service Delivery: the NF (CTF) delivers the content/service based on the number of units.
5.3.2.3 Session based charging
For Converged Session based Charging, the following cases are supported:
- SCUR
- ECUR
ETSI
---------------------- Page: 11 ----------------------
3GPP TS 32.290 version 15.3.0 Release 15 11 ETSI TS 132 290 V15.3.0 (2019-05)
Figure 5.3.2.3.1 shows a scenario for Session based charging (SCUR) with: Unit Reservation, Decentralized and
Centralized Unit Determination, Centralized Rating configuration, user’s account deduction, where the NF (CTF)
invokes a converged charging service towards the CHF.
NF
CHF
(CTF)
1. Request for resource usage
Pre-delivery procedure
2. Units Determination
3. Charging Data Request [Initial, Quota Requested]
4. Account,Rating,
Reservation Control
5. Open CDR
6. Charging Data Response [Initial, Quota Granted]
7. Granted Units
Supervision
8 Content/Service Delivery
Usage Reporting procedure
9. Usage Reporting
Trigger
10. Charging Data Request [Update]
11. Account,
Rating Control
12. Update CDR
13. Charging Data Response [Update]
Quota management and Usage Reporting procedure
14. quota management
trigger
15. Charging Data Request [Update, Quota Requested]
16. Account,Rating,
Reservation Control
17. Update CDR
18. Charging Data Response [Update, Quota Granted ]
19.Content/Service Delivery
20. Session released
Post-delivery procedure
21. Charging data
generation
22. Charging Data Request [Termination]
23. Account,Rating
Control
24. Close CDR
25. Charging Data Request [Termination]
Figure 5.3.2.3.1: SCUR - Session based charging withDecentralized and Centralized Unit
Determination, Centralized Rating
ETSI
---------------------- Page: 12 ----------------------
3GPP TS 32.290 version 15.3.0 Release 15 12 ETSI TS 132 290 V15.3.0 (2019-05)
1) Request for resource usage: A request for session establishment is received in the NF (CTF). The service is
configured to be authorized by the CHF to start.
2) Units Determination: the NF (CTF)) determines the number of units depending on the service requested by the
UE in "Decentralized Units determination" scenario.
3) Charging Data Request [Initial, Quota Requested]: The NF (CTF) sends the request to the CHF for the
service to be granted authorization to start, and to reserve the number of units if determined in item 2.
4) Account, Rating, Reservation Control: the CHF rates the requests either based on the number of units
requested or on internal unit determination, checks if corresponding funds can be reserved on the user's account
balance. If the account has sufficient funds, the CHF performs the corresponding reservations.
5) Open CDR: based on policies, the CHF opens a CDR related to the service.
6) Charging Data Response [Initial, Quota Granted]: The CHF grants authorization to NF (CTF) for the service
to start, with the reserved number of units.
7) Granted Units Supervision: The service starts and the NF (CTF) monitors the consumption of the granted
units.
8) Content/Service Delivery: the NF (CTF) delivers the content/service based on the reserved number of units.
9) Usage Reporting Trigger: the NF (CTF) generates charging data related to service delivered, based on a
trigger for usage reporting is met.
10) Charging Data Request [Update]: the NF (CTF) sends the request for reporting the related charging data to
the CHF.
11) Account, Rating Control: The CHF performs the reported usage process involving rating entity and user's
account balance.
12) Update CDR: based on policies, the CHF updates the CDR with charging data related to the service.
13) Charging Data Response [Update]: The CHF informs the NF (CTF) on the result of the request.
14) Quota management Trigger: A Trigger associated to Quota management is met. Units determination is
performed when applicable.
15) Charging Data Request [Update, Quota Requested]: the NF (CTF) sends the request to the CHF, to be
granted with more unit for the service to continue, and also for reporting the used units.
16) Account, Rating, Reservation Control: The CHF performs the process related to the reported usage and the
requested reservation, involving rating entity and user's account balance.
17) Update CDR: based on policies, the CHF updates the CDR with charging data related to the service.
18) Charging Data Response [Update, Quota Granted]: The CHF grants quota to NF (CTF) for the service to
continue, with the reserved number of units.
19) Content/Service Delivery: the NF (CTF) delivers the content/service based on the granted quota.
20) Session released: the session is released.
21) Charging Data Generation: the NF (CTF) generates charging data related to service released.
22) Charging Data Request [Termination]: the NF (CTF) sends the request to the CHF, for charging data related
to the service termination with the final consumed units.
23) Account, Rating Control: The CHF performs the service termination process involving rating entity and user's
account balance.
24) Close CDR: based on policies, the CHF closes the CDR with charging data related to the service termination
and the last reported units.
25) Charging Data Response [Termination]: The CHF informs the NF (CTF) on the result of the request.
ETSI
---------------------- P
...