3GPP TS 32.291

3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;

3GPP TS 32.291
Telecommunication management;
V15.5.0 (2019-12)
Charging management;
Technical Specification
5G system, charging service;
Stage 3
(Release 15)
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP..
The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this
Specification.
Specifications and Reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.
Release 15 2 3GPP TS 32.291 V15.45.0 (2019-0912)
Keywords
charging, service based interface
3GPP
Postal address
3GPP support office address

650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org
Copyright Notification
No part may be reproduced except as authorized by written permission.

The copyright and the foregoing restriction extend to reproduction in all media.
© 2019, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.
UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
GSM® and the GSM logo are registered and owned by the GSM Association
3GPP
Release 15 3 3GPP TS 32.291 V15.45.0 (2019-0912)
Contents
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..............................................................................................................................................8
4 Overview........................................................................................................................................9
4.1 Service architecture.....................................................................................................................................9
4.2 Network functions.......................................................................................................................................9
4.2.1 Charging Function (CHF)......................................................................................................................9
4.2.2 NF Service Consumers..........................................................................................................................9
5 Services offered by the CHF.........................................................................................................10
5.1 Introduction...............................................................................................................................................10
5.2 Nchf_ConvergedCharging service............................................................................................................10
5.2.1 Service description..............................................................................................................................10
5.2.2 Service operations...............................................................................................................................10
5.2.2.1 Introduction....................................................................................................................................10
5.2.2.2 Nchf_ConvergedCharging_Create Operation................................................................................11
5.2.2.3 Nchf_ConvergedCharging_Update Operation..............................................................................12
5.2.2.4 Nchf_ConvergedCharging_Release Operation..............................................................................12
5.2.2.5 Nchf_ConvergedCharging_Notify Operation................................................................................13
6 API definitions..............................................................................................................................14
6.1 Nchf_ ConvergedCharging Service API...................................................................................................14
6.1.1 Introduction.........................................................................................................................................14
6.1.2 Usage of HTTP....................................................................................................................................14
6.1.2.1 General...........................................................................................................................................14
6.1.2.2 HTTP standard headers..................................................................................................................14
6.1.2.2.1 General.....................................................................................................................................14
6.1.2.2.2 Content type.............................................................................................................................14
6.1.2.3 HTTP custom headers....................................................................................................................14
6.1.2.3.1 General.....................................................................................................................................14
6.1.3 Resources.............................................................................................................................................15
6.1.3.1 Overview........................................................................................................................................15
6.1.3.2 Resource: Charging Data...............................................................................................................16
6.1.3.2.1 Description...............................................................................................................................16
6.1.3.2.2 Resource Definition.................................................................................................................16
6.1.3.2.3 Resource Standard Methods.....................................................................................................16
6.1.3.2.3.1 POST..................................................................................................................................16
6.1.3.2.4 Resource Custom Operations...................................................................................................17
6.1.3.3 Resource: Individual Charging Data..............................................................................................17
6.1.3.3.1 Description...............................................................................................................................17
6.1.3.3.2 Resource Definition.................................................................................................................17
6.1.3.3.3 Resource Standard Methods.....................................................................................................18
6.1.3.3.4 Resource Custom Operations...................................................................................................18
6.1.3.3.4.1 Overview............................................................................................................................18
6.1.3.3.4.2 Operation: update...............................................................................................................18
6.1.3.3.4.2.1 Description....................................................................................................................18
6.1.3.3.4.2.2 Operation Definition.....................................................................................................18
6.1.3.3.4.3 Operation: release...............................................................................................................19
6.1.3.3.4.3.1 Description....................................................................................................................19
6.1.3.3.4.3.2 Operation Definition.....................................................................................................19
6.1.4 Custom Operations without associated resources...............................................................................20
3GPP
Release 15 4 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.5 Notifications........................................................................................................................................20
6.1.5.1 General...........................................................................................................................................20
6.1.5.2 Event Notification..........................................................................................................................20
6.1.5.2.1 Description...............................................................................................................................20
6.1.5.2.2 Target URI...............................................................................................................................20
6.1.5.2.3 Standard Methods.....................................................................................................................20
6.1.5.2.3.1 POST..................................................................................................................................20
6.1.6 Data Model..........................................................................................................................................21
6.1.6.1 General...........................................................................................................................................21
6.1.6.2 Structured data types......................................................................................................................24
6.1.6.2.1 Common Data Type.................................................................................................................24
6.1.6.2.1.1 Type ChargingDataRequest................................................................................................24
6.1.6.2.1.2 Type ChargingDataResponse.............................................................................................25
6.1.6.2.1.3 Type ChargingNotifyRequest.............................................................................................25
6.1.6.2.1.4 Type NFIdentification........................................................................................................26
6.1.6.2.1.5 Type MultipleUnitUsage....................................................................................................27
6.1.6.2.1.6 Type InvocationResult........................................................................................................27
6.1.6.2.1.7 Type Trigger.......................................................................................................................28
6.1.6.2.1.8 Type MultipleUnitInformation...........................................................................................29
6.1.6.2.1.9 Type RequestedUnit...........................................................................................................29
6.1.6.2.1.10 Type UsedUnitContainer....................................................................................................30
6.1.6.2.1.11 Type GrantedUnit...............................................................................................................31
6.1.6.2.1.12 Type FinalUnitIndication...................................................................................................31
6.1.6.2.1.13 Type RedirectServer...........................................................................................................31
6.1.6.2.1.14 Type ReauthorizationDetails..............................................................................................32
6.1.6.2.1.15 Void....................................................................................................................................32
6.1.6.2.1.16 Type ChargingNotifyResponse..........................................................................................32
6.1.6.2.2 5G Data Connectivity Specified Data Type.............................................................................32
6.1.6.2.2.2 Type ChargingDataResponse.............................................................................................32
6.1.6.2.2.3 Type MultipleUnitUsage....................................................................................................33
6.1.6.2.2.4 Type MultipleUnitInformation...........................................................................................33
6.1.6.2.2.5 Type UsedUnitContainer....................................................................................................33
6.1.6.2.2.6 Type PDUSessionChargingInformation.............................................................................34
6.1.6.2.2.7 Type UserInformation........................................................................................................35
6.1.6.2.2.8 Type PDUSessionInformation............................................................................................36
6.1.6.2.2.9 Type PDUContainerInformation........................................................................................37
6.1.6.2.2.10 Type NetworkSlicingInfo...................................................................................................37
6.1.6.2.2.11 Type PDUAddress..............................................................................................................38
6.1.6.2.2.12 Type ServingNetworkFunctionID......................................................................................38
6.1.6.2.2.13 Type RoamingQBCInformation.........................................................................................38
6.1.6.2.2.14 Type MultipleQFIcontainer................................................................................................39
6.1.6.2.2.15 Type RoamingChargingProfile..........................................................................................39
6.1.6.2.2.16 Type QFIContainerInformation..........................................................................................40
6.1.6.2.2.17 Type RANSecondaryRATUsageReport.............................................................................40
6.1.6.2.2.18 Type QosFlowsUsageReport..............................................................................................41
6.1.6.2.3 SMS Specified Data Type........................................................................................................41
6.1.6.2.3.2 Type SMSChargingInformation.........................................................................................42
6.1.6.2.3.3 Type OriginatorInfo............................................................................................................43
6.1.6.2.3.4 Type RecipientInfo.............................................................................................................44
6.1.6.2.3.5 Type SMAddressInfo.........................................................................................................44
6.1.6.2.3.6 Type RecipientAddress......................................................................................................44
6.1.6.2.3.7 Type MessageClass............................................................................................................45
6.1.6.2.3.8 Type SMAddressDomain...................................................................................................45
6.1.6.2.3.9 Type SMInterface...............................................................................................................45
6.1.6.3 Simple data types and enumerations..............................................................................................45
6.1.6.3.1 Introduction..............................................................................................................................45
6.1.6.3.2 Simple data types.....................................................................................................................45
6.1.6.3.3 Enumeration: NotificationType...............................................................................................46
6.1.6.3.4 Enumeration: NodeFunctionality.............................................................................................46
3GPP
Release 15 5 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.3.5 Enumeration: ChargingCharacteristicsSelectionMode............................................................46

6.1.6.3.6 Enumeration: TriggerType.......................................................................................................47
6.1.6.3.7 Enumeration: FinalUnitAction.................................................................................................48
6.1.6.3.8 Enumeration: RedirectAddressType........................................................................................48
6.1.6.3.9 Enumeration: TriggerCategory................................................................................................49
6.1.6.3.10 Enumeration: QuotaManagementIndicator..............................................................................49
6.1.6.3.11 Enumeration: FailureHandling.................................................................................................49
6.1.6.3.12 Enumeration: SessionFailover.................................................................................................50
6.1.6.3.13 Enumeration: 3GPPPSDataOffStatus......................................................................................50
6.1.6.3.14 Enumeration: ResultCode........................................................................................................51
6.1.6.3.15 Enumeration: PartialRecordMethod.........................................................................................52
6.1.6.3.16 Enumeration: RoamerInOut.....................................................................................................52
6.1.6.3.17 Void..........................................................................................................................................52
6.1.6.3.18 Enumeration: SMMessageType...............................................................................................52
6.1.6.3.19 Enumeration: SMPriority.........................................................................................................52
6.1.6.3.20 Enumeration: DeliveryReportRequested.................................................................................52
6.1.6.3.21 Enumeration: InterfaceType.....................................................................................................53
6.1.6.3.22 Enumeration: ClassIdentifier...................................................................................................53
6.1.6.3.23 Enumeration: SMAddressType................................................................................................53
6.1.6.3.24 Enumeration: SMAddresseeType............................................................................................53
6.1.6.3.25 Enumeration: SMServiceType.................................................................................................54
6.1.6.3.26 Enumeration: ReplyPathRequested..........................................................................................54
6.1.6.3.27 Enumeration: DnnSelectionMode............................................................................................54
6.1.6.3.28 Enumeration: EventType.........................................................................................................54
6.1.6.4 Data types describing alternative data types or combinations of data types.................................54
6.1.6.5 Binary data.....................................................................................................................................55
6.1.7 Error handling......................................................................................................................................55
6.1.7.1 General...........................................................................................................................................55
6.1.7.2 Protocol Errors...............................................................................................................................55
6.1.7.3 Application errors..........................................................................................................................55
6.1.8 Feature negotiation..............................................................................................................................56
7 Bindings of CDR field, Information Element and Resource Attribute..........................................57
7.0 General......................................................................................................................................................57
7.1 Bindings of common CDR field, Information Element and Resource Attribute......................................58
7.2 Bindings for 5G data connectivity............................................................................................................60
7.3 Bindings for SMS charging.......................................................................................................................63
8 Security.........................................................................................................................................64
Annex A (normative): OpenAPI specification..........................................................................64
A.1 General......................................................................................................................................................64
A.2 Nchf_ ConvergedCharging API................................................................................................................64
Annex B (informative):Change history...................................................................................................79
3GPP
Release 15 6 3GPP TS 32.291 V15.45.0 (2019-0912)
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.
3GPP
Release 15 7 3GPP TS 32.291 V15.45.0 (2019-0912)
1 Scope
The present document specifies the protocol that is used for service based interface. The API definitions and data type
definitions are aligned with 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 5G data connectivity is specified in TS 32.255[30].
- The service, operations and procedures of 5G charging for service based interface is specified in TS 32.290 [58].
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] - [28] Void.
[29] 3GPP TS 32.274: "Telecommunication management; Charging management;Short Message

Service (SMS) charging".
[30] 3GPP TS 32.255: "Telecommunication management; Charging management; 5G Data

connectivity domain charging; stage 2".
[31] - [49] Void.
[50] - [57] Void.
[58] 3GPP TS 32.290: "Telecommunication management; Charging management; 5G system; Services,

operations and procedures of charging using Service Based Interface (SBI).
[59] - [99] Void.
[100] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[101] - [199] Void
[200] - [203] Void
[204] - [298] Void
[299] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[300] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[301] 3GPP TS 29.594: "5G System; Spending Limit Control Service; Stage 3".
[302] 3GPP TS 29.512: "5G System; Session Management Policy Control Service; Stage 3".
3GPP
Release 15 8 3GPP TS 32.291 V15.45.0 (2019-0912)
[303] - [370] Void
[371] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[372] - [389] Void
[390] 3GPP TS 33.501: "Security architecture and procedures for 5G System".
[391] - [399] Void
[400] Void.
[401] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2) ".
[402] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format ".
[403] - [499] Void.
[500] OpenAPI: "OpenAPI 3.0.0 Specification",

https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md.
[501] - [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 [1] 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:
Nchf Service based interface exhibited by CHF.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] 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 [1].
AF Application Function
AMF Access and Mobility Management Function
CHF Charging Function
CTF Charging Trigger Function
GPSI Generic Public Subscription Identifier
GUAMI Globally Unique AMF Identifier
NF Network Function
PEI Permanent Equipment Identifier
QBC QoS flow Based Charging
QFI QoS Flow Identifier
SMSF Short Message Service Function
SMF Session Management Function
SSC Session and Service Continuity
SUPI Subscription Permanent Identifier
3GPP
Release 15 9 3GPP TS 32.291 V15.45.0 (2019-0912)
4 Overview
4.1 Service architecture

The Converged Charging Service is provided by the CHF to the consumer and shown in the SBI representation model
in figure 4. 1.1. The 5G Data connectivity domain charging is depicted in 3GPP TS 32.255 [30].
The ConvergedCharging Service (Nchf_ ConvergedCharging) is part of the Nchf service-based interface exhibited by
the Charging Function (CHF) , with SMF and SMSF as the NF Service Consumer.
Figure 4. 1.1: Reference Architecture for the Nchf_ConvergedCharging Service; SBI representation
4.2 Network functions

4.2.1 Charging Function (CHF)
The CHF is responsible for converged online charging and offline charging functionalities. The CHF provides the
following:
- Quota;
- Re-authorisation triggers;
- Notification when Charging Domain determines rating conditions is affected or when CHF determines to
terminate the charging service;
- Receiving service usage reports from NF Service Consumer; and
- CDRs generation.
4.2.2 NF Service Consumers

The NF Service Consumers shall support:
- Requesting and receiving the quota(s);
- Sending service usage reports; and
- Handling quota re-authorisation or abort notifications.
3GPP
Release 15 10 3GPP TS 32.291 V15.45.0 (2019-0912)
5 Services offered by the CHF
5.1 Introduction
The following services are provided by the CHF.
Table 5.1-1: NF Services provided by CHF
Service Name Description Consumer

Nchf_ConvergedCharging This service provides a converged charging for SMF, SMSF
service session and event based NF services, with and
without quota management, as well as charging
information record generation
Nchf_SpendingLimitControl This service enables the PCF to retrieve policy PCF
counter status information per UE from the CHF by
subscribing to spending limit reporting (i.e.
notifications of policy counter status changes).
The "Nchf_SpendingLimitControl" service is defined in 29.594 [301].
5.2 Nchf_ConvergedCharging service

5.2.1 Service description
This service provides charging in converged charging scenario by the CHF to the NF service consumer as defined in
subclause 6.2 in 3GPP TS 32.290[58].
It includes the following functionalities:
- Create resource at service establishment or no existing ChargingData resource, and may allocate quotas based on
the request from NF consumer;
- During the service consumption lifecycle, update resource upon receiving the quota usage or service usage report
under a number of circumstances and allocate subsequent quotas based on the request from NF consumer;
- Release upon service termination, Unit Count Inactivity Timer expiry or error response; and
- Notify NF Service Consumer of the re-authorisation triggers when CHF determines rating conditions is affected,
or the abort triggers when CHF determines to terminate the charging service.
- Charging information record generation
5.2.2 Service operations
5.2.2.1 Introduction
The service operations defined for Nchf_ ConvergedCharging are shown in table 5.2.2.1-1.
3GPP
Release 15 11 3GPP TS 32.291 V15.45.0 (2019-0912)
Table 5.2.2.1-2: Nchf_ ConvergedCharging Operations
Service Operation Name Description Initiated by Corresponding

Converged
charging
messages in
3GPP TS
32.290[58]
Nchf_ ConvergedCharging_Create First Interrogation of unit NF consumer Charging Data
reservation; Request/Respons
And/or initial report of service e [Initial]
usage.
One Time request for the service. Charging Data
Request/Respons
e [Event]
Nchf_ ConvergedCharging_Update Intermediate Interrogation for NF consumer Charging Data
subsequent units reservation Request/Respons
when: e [Update]
- the granted service
unitfor one rating group
are spent
- expiry of granted service
units validity time
- service events occur,
which might affect the
rating of the current
service
And/or Intermediate report of
service usage.
Nchf_ ConvergedCharging_Release Final Interrogation without any NF consumer Charging Data
unit reservation Request/Respons
And/or last report of service e [Termination]
usage.
Nchf_ ConvergedCharging_Notify Request that the user be re- CHF Charging Notify
authorized or the charging Request/Respons
session context be terminated. e
5.2.2.2 Nchf_ConvergedCharging_Create Operation

The Nchf_ConvergedCharging_Create service operation provides means for NF (CTF) to request quotas for service
delivery or initial report of service usage.
The following procedures using the Nchf_ConvergedCharging_Create service operation are supported:
- No existing charging data resource.
Figure 5.2.2.2-1: Nchf_ ConvergedCharging_Create Service Operation
3GPP
Release 15 12 3GPP TS 32.291 V15.45.0 (2019-0912)
1. NF (CTF) sends a Nchf_ConvergedCharging_Create request to the CHF to create resource for charging.
Requested quota and notification URI for Nchf_ConvergedCharging_Notify service operation are included in the
request body.
2a. At successful operation, "201 Created" response is returned. In the "201 Created" response, the CHF includes a
Location header field and the allocated quota in the body. The Location header field shall contain the URI of the
created resource. The NF (CTF) shall use the URI received in the Location header in subsequent requests to the
CHF for the same PDU session.
2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.3.2.3.1-3 shall be returned. For a
4xx/5xx response, the message body shall contain a ProblemDetails structure with the "cause" attribute set to one
of the application error listed in Table 6.1.7.3-1.
5.2.2.3 Nchf_ConvergedCharging_Update Operation

The Nchf_ConvergedCharging_Update service operation provides means for NF (CTF) to update the charging data.
The following procedures using the Nchf_ConvergedCharging_Update service operation are supported:
- the granted service units for one rating group are spent
- expiry of granted service units' validity time
- charging events occur, which might affect the rating of the current service
- receiving re-authorization notification from CHF
Figure 5.2.2.3-1: Nchf_ConvergedCharging_Update Service Operation
1. NF (CTF) sends a Nchf_ConvergedCharging_Update request to the CHF. The {ChargingDataRef } in the URI
identifies the "Charging Data" to be updated. The requested service unit and previous used service unit is
included in the request body.
2a. At successful operation, "200 OK" response is returned. The CHF includes the granted service unit in the "200
OK" response.
2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.3.3.4.2.2-2 shall be returned. For a
5.2.2.4 Nchf_ConvergedCharging_Release Operation

The Nchf_ConvergedCharging_Release service operation provides means for NF (CTF) to terminate charging Session.
The following procedures using the Nchf_ConvergedCharging_Release service operation are supported:
- Expiry of unit count inactivity timer.in NF Consumer
3GPP
Release 15 13 3GPP TS 32.291 V15.45.0 (2019-0912)
- Abort notification is received from CHF.- Service termination in NF Consumer
Figure 5.2.2.4-1: Nchf_ConvergedCharging_Release Service Operation
1. NF(CTF) sends a Nchf_ConvergedCharging_Release request to the CHF. The {ChargingDataRef } in the URI
identifies the "Charging Data" to be updated and then released. The final used service unit is included in the
request body.
2a. At successful operation, "204 No Content" response is returned.
2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.3.3.4.3.2-2 shall be returned. For a
5.2.2.5 Nchf_ConvergedCharging_Notify Operation

The Nchf_ConvergedCharging_Notify service operation provides means for CHF to notify the NF(CTF) to update or
terminate charging of the PDU Session.
The following procedures using the Nchf_ConvergedCharging_Notify service operation are supported:
- CHF determines re-authorization.
- CHF determines abort of charging.
Figure 5.2.2.5-1: Nchf_ConvergedCharging_Notify Service Operation
1. The CHF sends a Nchf_ConvergedCharging_Notify request to the NF (CTF). The {notifyUri} identifies the
notification URI which is sent in the Nchf_ConvergedCharging_Create request. The notification type is included
in the request body.
2a. At successful operation, "204 No Content" response is returned.
2b. On failure, one of the HTTP status code listed in Table 6.1.5.2.3.1-2 shall be returned. For a 4xx/5xx response,
the message body shall contain a ProblemDetails structure with the "cause" attribute set to one of the application
error listed in Table 6.1.7.3-1.
3GPP
Release 15 14 3GPP TS 32.291 V15.45.0 (2019-0912)
After successful operation, when the NF Service Consumer receives a Charging Notify Request while not waiting for
any Charging Data Response from the CHF, CTF can send a new Charging Data Request.
6 API definitions
6.1 Nchf_ ConvergedCharging Service API

6.1.1 Introduction
The APIs defined in this subclause implement the service operation defined in subclause 5.2.2.
The Nchf_ConvergedCharging service shall use the Nchf_ConvergedCharging API.
The request URI used in each HTTP request from the NF service consumer towards the CHF shall have the structure
defined in subclause 4.4.1 of 3GPP TS 29.501 [5], i.e.:
{apiRoot}/{apiName}/{apiVersion}/{apiSpecificResourceUriPart}
with the following components:
- The {apiRoot} shall be set as described in 3GPP TS 29.501 [5].
- The {apiName} shall be "nchf-convergedcharging".
- The {apiVersion} shall be "v2".
- The {apiSpecificResourceUriPart} shall be set as described in subclause 6.1.3.
6.1.2 Usage of HTTP
6.1.2.1 General
HTTP/2 as described in IETF RFC 7540 [401] shall be used as specified in subclause 5.2 of 3GPP TS 29.500 [299].
6.1.2.2 HTTP standard headers
6.1.2.2.1 General
See subclause 5.2.2 of 3GPP TS 29.500 [299] for the usage of HTTP standard headers.
HTTP/2, shall be transported as specified in subclause 5.3 of 3GPP TS 29.500 [299].
6.1.2.2.2 Content type

JSON, IETF RFC 8259 [402], shall be used as content type of the HTTP bodies specified in the present specification, as
specified in subclause 5.4 of 3GPP TS 29.500 [299].
6.1.2.3 HTTP custom headers
6.1.2.3.1 General
HTTP custom header fields shall be supported as specified in subclause 5.2.3.2 of 3GPP TS 29.500 [299].
In this Release of the specification, no specific custom headers are defined.
3GPP
Release 15 15 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.3 Resources
6.1.3.1 Overview
Figure 6.1.3.1-1: Resource URI structure of the Nchf_ConvergedCharging API
Charging Data Ref is a unique identifier for a charging data resource in a PLMN. It’s created in CHF when CHF
receives a Nchf_ ConvergedCharging_Create request and provided to NF (CTF) in the Location header field in the
Nchf_ ConvergedCharging_Create response. The NF (CTF) shall use the Charging Data Ref received in subsequent
requests to the CHF for the same charging data resource.
Table 6.1.3.1-1 provides an overview of the resources and applicable HTTP methods.
Table 6.1.3.1-1: Resources and methods overview
HTTP Corresponding service

method operation
or Descriptio
Resource name Resource URI
custom n
operatio
n
POST Create a Nchf_
{apiRoot}/ new ConvergedCharging_Create
Charging Data nchf-convergedcharging/ Charging
{apiVersion}/chargingdata/ Data
resource
update Update an Nchf_
{apiRoot}/ (POST) existing ConvergedCharging_Update
nchf-convergedcharging/{apiVersion}/ Charging
chargingdata/{ChargingDataRef }/update Data
resource.
Individual Charging
release Update and Nchf_
Data
(POST) release an ConvergedCharging_Releas
{apiRoot}/
existing e
nchf-convergedcharging/{apiVersion}/
Charging
chargingdata /{ChargingDataRef}/release
Data
resource.
3GPP
Release 15 16 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.3.2 Resource: Charging Data
6.1.3.2.1 Description
Charging Data resource represents a collection of the different charging data resources created by the CHF for
converged charging as defined in 3GPP TS 32.290 [58].
6.1.3.2.2 Resource Definition

Resource URI: {apiRoot}/nchf-convergedcharging/{apiVersion}/chargingData
This resource shall support the resource URI variables defined in table 6.1.3.2.2-1.
Table 6.1.3.2.2-1: Resource URI variables for this resource
Name Definition
apiRoot See subclause 6.1.1
6.1.3.2.3 Resource Standard Methods
6.1.3.2.3.1 POST
This method shall support the URI query parameters specified in table 6.1.3.2.3.1-1.
Table 6.1.3.2.3.1-1: URI query parameters supported by the POST method on this resource
Name Data type P Cardinality Description

n/a
This method shall support the request data structures specified in table 6.1.3.2.3.1-2 and the response data structures and
response codes specified in table 6.1.3.2.3.1-3.
Table 6.1.3.2.3.1-2: Data structures supported by the POST Request Body on this resource
Data type P Cardinality Description

ChargingDataRequest M 1 Parameters to create a new Charging Data resource.
3GPP
Release 15 17 3GPP TS 32.291 V15.45.0 (2019-0912)
Table 6.1.3.2.3.1-3: Data structures supported by the POST Response Body on this resource
Data type P Cardinality Response Description

codes
ChargingDataRespons M 1 201 The creation of a Charging Data resource is confirmed and a
e Created representation of that resource is returned.
The Charging Data resource which is created and returned
successfully. The representation of created resource is
identified via Location header field in the 201 response.
n/a 307 (NOTE 2)
Temporary
Redirect
ChargingDataRespons M 1 400 (NOTE 2)
e Bad
Request
e Forbidden

e Not Found
n/a 405 (NOTE 2)

Method
Not
Allowed
n/a 408 (NOTE 2)

Request
Timeout
n/a 410 Gone (NOTE 2)

NOTE 1: In addition, the HTTP status codes which are specified as mandatory in table 5.2.7.1-1 of
3GPP TS 29.500 [299] for the POST method also apply.
NOTE 2: Failure cases are described in subclause 6.1.7.
6.1.3.2.4 Resource Custom Operations

None.
6.1.3.3 Resource: Individual Charging Data
Individual Charging Data resource represents a Charging data resource created in the CHF.
6.1.3.3.2 Resource Definition

Resource URI: {apiRoot}/nchf-convergedcharging/{apiVersion}/chargingdata/{ChargingDataRef}
This resource shall support the resource URI variables defined in table 6.1.3.3.2-1.
Name Definition
apiRoot See subclause 6.1.1
ChargingDataRef Charging data resource reference assigned by the CHF during the Nchf_
ConvergedCharging_Create operation,
3GPP
Release 15 18 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.3.3.3 Resource Standard Methods

None.
6.1.3.3.4 Resource Custom Operations
6.1.3.3.4.1 Overview
Table 6.1.3.3.4.1-1: Custom operations
Mapped
Custom operation URI HTTP Description
method
{apiRoot}/ POST Update an existing Charging Data resource.
nchf-convergedcharging/{apiVersion}/
chargingdata/{ChargingDataRef }/update
{apiRoot}/ POST Update and release an existing Charging Data
nchf-convergedcharging/{apiVersion}/ resource.
chargingdata /{ChargingDataRef}/release
6.1.3.3.4.2 Operation: update
6.1.3.3.4.2.1 Description
This operation updates an existing Charging Data resource.
6.1.3.3.4.2.2 Operation Definition
This operation shall support the request data structures specified in table 6.1.3.3.4.2.2-1 and the response data structures
and response codes specified in table 6.1.3.3.4.2.2-2.
Table 6.1.3.3.4.2.2-1: Data structures supported by the POST Request Body on this resource

ChargingDataRequest M 1 Parameters to modify an existing Charging Data resource matching the
ChargingDataRef according to the representation in the ChargingData.
The request URI is the representation in the Location header field in the
201 response of resource creation.
3GPP
Release 15 19 3GPP TS 32.291 V15.45.0 (2019-0912)
Table 6.1.3.3.4.2.2-2: Data structures supported by the POST Response Body on this resource
Data type P Cardinality Response Description

codes
ChargingDataRespons M 1 200 OK The modification of a Charging Data resource is confirmed
e and a representation of that resource is returned.
The Charging Data resource which is modified and returned
successfully.
n/a 307 (NOTE 2)
Temporary
Redirect
e Bad
Request
e Forbidden

e Not Found
n/a 405 (NOTE 2)

Method
Not
Allowed
n/a 408 (NOTE 2)

Request
Timeout

6.1.3.3.4.3 Operation: release
6.1.3.3.4.3.1 Description
This operation update and release an existing Charging session
6.1.3.3.4.3.2 Operation Definition
This operation shall support the request data structures specified in table 6.1.3.3.4.3.2-1 and the response data structures
and response codes specified in table 6.1.3.3.4.3.2-2.
Table 6.1.3.3.4.3.2-1: Data structures supported by the POST Request Body on this resource

ChargingDataRequest M 1 Parameters to modify and then release the Charging Data resource
matching the ChargingDataRef according to the representation in the
ChargingData.
The request URI is the representation in the Location header field in the
201 response of resource creation.
3GPP
Release 15 20 3GPP TS 32.291 V15.45.0 (2019-0912)
Table 6.1.3.3.4.3.2-2: Data structures supported by the POST Response Body on this resource
Data type P
Cardinality Response Description
codes
n/a 204 No Successful case: The Charging Data resource matching the
Content ChargingDataRef is modified and then released.
ChargingDataRespons M 1 404 Not (NOTE 2)
e Found
NOTE 1: The mandatory HTTP error status codes for the POST method listed in table 5.2.7.1-1 of 3GPP TS 29.500
[4] also apply.
6.1.4 Custom Operations without associated resources

None.
6.1.5 Notifications
6.1.5.1 General
Notifications shall comply to subclause 6.2 of 3GPP TS 29.500 [299] and subclause 4.6.2.3 of 3GPP TS 29.501 [300].
6.1.5.2 Event Notification
The Notification is used by the CHF to notify NF consumers of the subscribed events is occurs , which implements the
Nchf_ ConvergedCharging_Notify operation defined in 3GPP TS 32.290 [58].
6.1.5.2.2 Target URI

The Notification URI "{notifyUri}" shall be used with the resource URI variables defined in table 6.1.5.2.2-1.
Name Definition
notifyUri String formatted as URI with the Notification URI is provided by the SMF during the creation of
the Charging Data resource and within the ChargingData type, as defined in subclause 6.1.6.
6.1.5.2.3 Standard Methods
6.1.5.2.3.1 POST
This method shall support the request data structures specified in table 6.1.5.2.3.1-1 and the response data structures and
response codes specified in table 6.1.5.2.3.1-2.
Table 6.1.5.2.3.1-1: Data structures supported by the POST Request Body on this resource

ChargingNotifyRequest M 1 Provides Information about active Charging events.
ChargingNotifyRequest data type is defined in subclause
6.1.6.
3GPP
Release 15 21 3GPP TS 32.291 V15.45.0 (2019-0912)
Table 6.1.5.2.3.1-2: Data structures supported by the POST Response Body on this resource
Data type P CardinalitResponse Description

y codes
n/a 204 No The receipt of the Notification is acknowledged.
Content
ChargingNotifyResponse M 1 400 Bad (NOTE 2)
Request
6.1.6 Data Model
6.1.6.1 General
This subclause specifies the application data model supported by the API.
The Nchf_ConvergedCharging Service API allows the NF consumer to consume the converged charging service from
the CHF as defined in 3GPP TS 32.290 [58].
Table 6.1.6.1-1 specifies the data types defined for the ConvergedCharging service based interface protocol.
Table 6.1.6.1-1: Nchf_ ConvergedCharging specific Data Types
Data type Section defined Description Applicability

ChargingDataRequest 6.1.6.2.1.1 Describes the attributes of Charging
6.1.6.2.2.1 Data Request to CHF for initial,
update and termination of the
charging session.
ChargingDataResponse 6.1.6.2.1.2 Describes the attributes of Charging
6.1.6.2.2.2 Data Response from CHF on
charging session initial, update and
termination.
ChargingNotifyRequest 6.1.6.2.1.3 Describes Notifications about events
that occurred in request message.
ChargingNotifyResponse 6.1.6.2.1.16 Describes the response of
notification.
Table 6.1.6.1-2 specifies data types re-used by the Nchf_ConvergedCharging service based interface protocol from
other specifications, including a reference to their respective specifications and when needed, a short description of their
use within the Nchf_ConvergedCharging service based interface.
3GPP
Release 15 22 3GPP TS 32.291 V15.45.0 (2019-0912)
Table 6.1.6.1-2: Nchf_ConvergedCharging re-used Data Types
Data type Reference Comments Applicability

Supi 3GPP TS 29.571 [371] The identification of
the user (i.e. IMSI,
NAI).
Uint32 3GPP TS 29.571 [371] Unsigned 32-bit
integers
Uint64 3GPP TS 29.571 [371] Unsigned 64-bit
integers
PduSessionId 3GPP TS 29.571 [371] The identification of
the PDU session.
PduSessionType 3GPP TS 29.571 [371] the type of a PDU
session
Uri 3GPP TS 29.571 [371] String providing an
URI
AccessType 3GPP TS 29.571 [371] The identification of
the type of access
network.
DateTime 3GPP TS 29.571 [371] The time.
ChargingId 3GPP TS 29.571 [371] Charging identifier
allowing correlation
of charging
information
RatType 3GPP TS 29.571 [371] The identification of
the RAT type.
RatingGroup 3GPP TS 29.571 [371] The identification of
the rating group
Ipv4Addr 3GPP TS 29.571 [371] Ipv4 address.
Ipv6Prefix 3GPP TS 29.571 [371] The Ipv6 prefix
allocated for the user.
Ipv6Addr 3GPP TS 29.571 [371] Ipv6 Address.
Pei 3GPP TS 29.571 [371] The Identification of a
Permanent
Equipment.
TimeZone 3GPP TS 29.571 [371] Time zone
information
NfInstanceId 3GPP TS 29.571 [371] String uniquely
identifying a NF
instance.
Gpsi 3GPP TS 29.571 [371] String identifying a
Gpsi
DefaultQosInformatio 3GPP TS 29.571 [371] Identifies the
n information of the
default QoS.
SubscribedDefaultQo 3GPP TS 29.571 [371] subscribed default
s QoS.
AuthorizedDefaultQos 3GPP TS 29.512 [302] Authorized default
QoS.
Ambr 3GPP TS 29.571 [371] Aggregate Maximum
Bit rate
QosData 3GPP TS 29.512 [302] Contains QoS
parameters
UserLocation 3GPP TS 29.571 [371] User location
information
PlmnId 3GPP TS 29.571 [371] PLMN id
Guami 3GPP TS 29.571 [371] Globally Unique AMF
Identifier
DurationSec 3GPP TS 29.571 [371] Identifies a period of
time in units of
seconds.
Snssai 3GPP TS 29.571 [371] SNSSAI
ProblemDetails 3GPP TS 29.571 [371] additional details of

the error
3GPP
Release 15 23 3GPP TS 32.291 V15.45.0 (2019-0912)
ServiceId 3GPP TS 29.571 [371] Identifier of service
SscMode 3GPP TS 29.571 [371] SSC Mode type
PresenceInfo 3GPP TS 29.571 [371] PRA information

including PRAId,
PRA element list and
PRA status
Qfi 3GPP TS 29.571 [371] QoS flow identifier

designated as "Qfi".
AmfId 3GPP TS 29.571 [371] AMF identifier
Dnn 3GPP TS 29.571 [371] Data Network Name
3GPP
Release 15 24 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2 Structured data types
6.1.6.2.1 Common Data Type
6.1.6.2.1.1 Type ChargingDataRequest
Table 6.1.6.2.1.1-1: Definition of type ChargingDataRequest
Attribute name Data type P Cardinality Description Applicability

subscriberIdentifi Supi OM 0..1 Identifier of the subscriber
er that uses the requested
service.
nfConsumerIdent NFIdentification M 1 This is a grouped field which
ification contains a set of information
identifying the NF consumer
of the charging service.
invocationTimeSt DateTime M 1 The time at which the request
amp is send
invocationSeque Uint32 M 1 This field contains the
nceNumber sequence number of the
charging service invocation
by the NF consumer.
oneTimeEvent boolean OC 0..1 Indicates, if included, that this
is event based charging and
whether this is a one-time
event. If true, this is a one-
time event that there will be
no update or release.
oneTimeEventTy EventType OC 0..1 indicates the type of the one
pe time event, i.e. Immediate or
Post event charging.
notifyUri Uri OC 0..1 Identifies the recipient of
Notifications sent by the CHF.
In case of session based
charging it shall be present in
create request message, and
may be present in update.
service String OC 0..1 Identifies service specific
SpecificationInfor document that applies to the
mation request, e.g. the service
specific document ('middle
tier' TS) and 3GPP release
the service specific document
is based upon.
multipleUnitUsag array(MultipleUnitUs OC 0..N This field contains the
e age) parameters for the quota
management request and/or
usage reporting.
triggers array(Trigger) OC 0..N This field identifies the
event(s) triggering the
request.
3GPP
Release 15 25 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.1.2 Type ChargingDataResponse
Table 6.1.6.2.1.2-1: Definition of type ChargingDataResponse

invocationTimest DateTime M 1 This field holds the timestamp
amp of the charging service
response from the CHF.
invocationResult InvocationResult OC 0..1 This field holds the result of
by the NF consumer
invocationSeque Uint32 M 1 This field contains the
nceNumber sequence number of the
by the NF consumer.
sessionFailover SessionFailover OC 0..1 This field indicates whether
alternative CHF is supported
for ongoing charging service
failover handling by NF
consumer.
multipleUnitInfor array(MultipleUnitInf OC 0..N This field holds the
mation ormation) parameters for the quota
management and/or usage
reporting information. It may
have multiple occurrences.
triggers array(Trigger) OC 0..N This field identifies the
chargeable event(s) supplied
by CHF to override/activate
the existing chargeable
event(s) in NF consumer.
The presence of the triggers
attribute without any
triggerType is used by CHF to
disable all the triggers except
rating group level triggers.
6.1.6.2.1.3 Type ChargingNotifyRequest
Table 6.1.6.2.1.3-1: Definition of type ChargingNotifyRequest
Attribute name Data type P Cardinalit Description Applicability

y
notificationType NotificationType M 1 Type of notification to indicate
re-authorization or termination.
reauthorizationD array(Reauthorizatio OC 0..N descriptors for re-authorization
etails nDetails) to determine which quota or
usage reporting is updated.
3GPP
Release 15 26 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.1.4 Type NFIdentification
Table 6.1.6.2.1.4-1: Definition of type NFIdentification

y
nodeFunctionality NodeFunctionality M 1 This field contains the function
of the node.
nFName NfInstanceId OC 0..1 Identifier of NF instance. At
least one of the nFName or
nFIPv4Address or
nFIPv6Address shall be
present.
nFIPv4Address Ipv4Addr OC 0..1 The IPv4 address of the NF. At
nFIPv4Address or
present.
nFIPv6Address Ipv6Addr OC 0..1 The IPv6 address of the NF. At
nFIPv4Address or
present.
nFFqdn string OC 0..1 FQDN of the NF
nFPLMNID PlmnId OC 0..1 This field holds the PLMN ID of
the network the NF belongs to.
6.1.6.2.1.5 Type MultipleUnitUsage
Table 6.1.6.2.1.5-1: Definition of type MultipleUnitUsage

y
ratingGroup RatingGroup M 1 The identifier of a rating group.
requestedUnit RequestedUnit OC 0..1 This field indicates, if included,
that quota management is
required. It may additionally
contain the amount of
requested service units for a
particular category.
usedUnitContain array(UsedUnitCont OC 0..N This field contains the amount
er ainer) of used non-monetary service
units measured.
3GPP
Release 15 27 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.1.6 Type InvocationResult
Table 6.1.6.2.1.6-1: Definition of type InvocationResult

y
error ProblemDetails OC 0..1 More information on the error
shall be provided in the "cause"
attribute of the "ProblemDetails"
structure in case of
unsuccessful charging service
invocation by the NF consumer.
The "invalidParams" attribute of
the "ProblemDetails" structure
shall contain the invalid
parameters which caused the
rejection.
failureHandling FailureHandling OC 0..1 This field holds the failure
handling to be performed by the
NF consumer when charging
service invocation is temporarily
prevented. The provided value
shall always override any
already existing value in NF
consumer.
In case of failure, it indicates
which action to be performed by
the NF consumer.
In case of success, it indicates
which action to be performed by
the NF consumer in case
subsequent charging service
invocation are temporarily
prevented.
3GPP
Release 15 28 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.1.7 Type Trigger
Table 6.1.6.2.1.7-1: Definition of type Trigger

y
triggerType TriggerType Oc 0..1 the events whose occurrence
lead to charging event is issued
towards the CHF
triggerCategory TriggerCategory M 1 This field indicates whether the
charging data generated by the
NF consumer for the trigger
lead to a Charging Event
towards the CHF immediately
or not.
timeLimit DurationSec OC 0..1 Time limit if trigger type is
"Expiry of data time limit"
volumeLimit Uint32 OC 0..1 Volume limit if trigger type is
"Expiry of data volume limit".
This attribute is not valid from
Nchf_ ConvergedCharging API
version v2.0.0
volumeLimit64 Uint64 OC 0..1 Volume limit if trigger type is
"Expiry of data volume limit".
This attribute replaces the
volumeLimit attribute from
Nchf_ ConvergedCharging API
v2.0.0
maxNumberOfcc Uint32 OC 0..1 Maximum number if trigger type
c is "Max nb of number of
charging condition changes"
3GPP
Release 15 29 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.1.8 Type MultipleUnitInformation
Table 6.1.6.2.1.8-1: Definition of type MultipleUnitInformation

y
resultCode ResultCode OC 0..1 This field contains the result of
the Rating group quota
allocation.
ratingGroup RatingGroup M 1 The identifier of a rating group.
grantedUnit GrantedUnit OC 0..1 This field holds the granted
quota.
triggers array(Trigger) OC 0..N This field holds triggers for
usage reporting associated to
the rating group, which is
supplied from the CHF.
The presence of the triggers

attribute without any
triggerType is used by CHF to
disable all the triggers to the
associated rating group.
validityTime DurationSec OC 0..1 This field defines the time in
order to limit the validity of the
granted quota for a given
category instance.
quotaHoldingTim DurationSec OC 0..1 This field holds the quota
e holding time in seconds. It
applies equally to the granted
time quota and to the granted
volume quota.
The NF Consumer shall deem a
quota to have expired when no
traffic associated with the quota
is observed for the value
indicated by this attribute. A
quotaHoldingTime value of zero
indicates that this mechanism
shall not be used. If the
quotaHoldingTime attribute is
not present, then a locally
configurable default value in the
NF Consumer shall be used.
finalUnitIndicatio FinalUnitIndication OC 0..1 This field indicates the granted
n final units for the service.
timeQuotaThresh integer OC 0..1 indicates the threshold in
old seconds for the granted time
quota.
volumeQuotaThr Uint64 OC 0..1 indicates the threshold in octets
eshold when the granted quota is
volume
unitQuotaThresh integer OC 0..1 indicates the threshold in
old service specific units, that are
defined in the service specific
documents, when the granted
quota is service specific
3GPP
Release 15 30 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.1.9 Type RequestedUnit
Table 6.1.6.2.1.9-1: Definition of type RequestedUnit

y
time Uint32 OC 0..1 This field holds the amount of
requested time.
totalVolume Uint64 OC 0..1 This field holds the amount of
requested volume in both uplink
and downlink directions.
uplinkVolume Uint64 OC 0..1 This field holds the amount of
requested volume in uplink
direction.
downlinkVolume Uint64 OC 0..1 This field holds the amount of
requested volume in downlink
direction.
serviceSpecificU Uint64 OC 0..1 This field holds the amount of
nits requested service specific units.
NOTE 1: If none is included the category and amount is determined by CHF.
6.1.6.2.1.10 Type UsedUnitContainer
Table 6.1.6.2.1.10-1: Definition of type UsedUnitContainer

y
serviceId ServiceId OC 0..1 This field identity of the used
service
quotaManageme QuotaManagementI OC 0..1 an indicator on whether the
ntIndicator ndicator reported used units are with or
without quota management
control. If the attribute is not
present, it indicates the used
unit is without quota
management applied.
triggers array (Trigger) OC 0..N This field specifies the reason
for usage reporting for one or
more types of unit associated to
the rating group.
triggerTimestamp DateTime Oc 0..1 This field holds the timestamp
when the reporting trigger
occur.
used time.
used volume in both uplink and
downlink directions.
used volume in uplink direction.
used volume in downlink
direction.
serviceSpecific Uint64 OC 0..1 This field holds the amount of
Units used service specific units.
eventTimeStamp DateTime OC 0..1 This field holds the timestamps
s of the event reported in the
Service Specific Unit s, if the
reported units are event based
localSequenceNu integer M 1 holds the Used Unit sequence
mber number, i.e. the order when
charging event occurs. It starts
from 1 and increased by 1 for
each Used Unit generation.
3GPP
Release 15 31 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.1.11 Type GrantedUnit
Table 6.1.6.2.1.11-1: Definition of type GrantedUnit

y
tariffTimeChange DateTime OC 0..1 This field contains the switch
time when the tariff will be
changed.
granted time.
granted volume in both uplink
and downlink directions.
granted volume in uplink
direction.
granted volume in downlink
direction.
serviceSpecificU Uint64 OC 0..1 This field holds the amount of
nits granted requested service
specific units.
6.1.6.2.1.12 Type FinalUnitIndication
Table 6.1.6.2.1.12-1: Definition of type FinalUnitIndication

y
finalUnitAction FinalUnitAction M 1 indicates to the service
consumer the action to be
taken when the user's account
cannot cover the service cost
restrictionFilterRu IPFilterRule OC 0..1 filter rules corresponding to
le services that are to remain
accessible even if there are no
more service units granted.
filterId string OC 0..1 the IP packet filters
corresponding to services that
are to remain accessible even if
there are no more service units
granted.
redirectServer RedirectServer OC 0..1 the address information of the
redirect server with which the
end user is to be connected
when the account cannot cover
the service cost.
6.1.6.2.1.13 Type RedirectServer
Table 6.1.6.2.1.13-1: Definition of type RedirectServer

y
redirectAddressT RedirectAddressTyp M 1 The type of redirect server
ype e address
redirectServerAd string M 1 the address of redirect server
dress
3GPP
Release 15 32 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.1.14 Type ReauthorizationDetails
Table 6.1.6.2.1.14-1: Definition of type ReauthorizationDetails

y
service ServiceId OC 0..1 identifier for a service
RatingGroup OC 0..1 identifier of a rating group.
This attribute shall be present if
ratingGroup
serviceIdentifier attribute is
present.
QuotaManagementI OC 0..1 an indicator on whether the re-
quotaManageme ndicator authorization notification is for
ntIndicator quota management control or
not.
6.1.6.2.1.16 Type ChargingNotifyResponse
Table 6.1.6.2.1.16-1: Definition of type ChargingNotifyResponse

invocationResult InvocationResult OC 0..1 This field holds the result of
notification.
6.1.6.2.2 5G Data Connectivity Specified Data Type
This clause is additional attributes of the type ChargingDataRequest defined in clause 6.1.6.2.1.1 for 5G data
connectivity charging described in 3GPP TS 32.255[30].
Table 6.1.6.2.2.1-1: 5G Data Connectivity Specified attribute of type ChargingDataRequest

pDUSessionChar PDUSessionChargin OM 0..1 This field holds the 5G data
gingInformation gInformation connectivity specific
information.
roamingQBCInfor RoamingQBCInform OM 0..1 This field holds the 5G data
mation ation connectivity specific
information roaming QBC.
6.1.6.2.2.2 Type ChargingDataResponse
This clause is additional attributes of the type ChargingDataResponse defined in clause 6.1.6.2.1.2 for 5G data
Table 6.1.6.2.2.2-1: 5G Data Connectivity Specified attribute of type ChargingDataResponse

pDUSessionChar PDUSessionChargin OM 0..1 This field holds the 5G data
gingInformation gInformation connectivity specific
information.
roamingQBCInfor RoamingQBCInform OM 0..1 This field holds the 5G data
mation ation connectivity specific
information roaming QBC.
3GPP
Release 15 33 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.2.3 Type MultipleUnitUsage
This clause is additional attributes of the type MultipleUnitUsage defined in clause 6.1.6.2.1.5 for 5G data connectivity
charging described in 3GPP TS 32.255[30].
Table 6.1.6.2.2.3-1: 5G Data Connectivity Specified attribute of type MultipleUnitUsage

y
uPFID NfInstanceId OC 0..1 identifier of UPF
6.1.6.2.2.4 Type MultipleUnitInformation
This clause is additional attributes of the type MultipleUnitInformationdefined in clause 6.1.6.2.1.8 for 5G data
Table 6.1.6.2.2.4-1: 5G Data Connectivity Specified attribute of type MultipleUnitInformation

y
uPFID NfInstanceId Oc 0..1 UPF id
6.1.6.2.2.5 Type UsedUnitContainer
This clause is additional portion of the type UsedUnitContainer defined in clause 6.1.6.2.1.10 for 5G data connectivity
charging described in 3GPP TS 32.255[30].
Table 6.1.6.2.2.5-1: 5G Data Connectivity Specified portion of type UsedUnitContainer

y
pDUContainerInf PDUContainerInfor OC 0..1 the 5G data connectivity
ormation mation specific information
3GPP
Release 15 34 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.2.6 Type PDUSessionChargingInformation
Table 6.1.6.2.2.6-1: Definition of type PDUSessionChargingInformation

y
chargingId ChargingId OM 0..1 Charging identifier for
correlation between different
records of a single PDU
session
userInformation UserInformation OM 0..1 including information of user
and user equipment,
userLocationinfo UserLocation OC 0..1 provides information on the
location
userLocationTim DateTime OC 0..1 the time at which the UE was
e last known to be in the location.
presenceReporti map(PresenceInfo) OC 0..N When the data type is present
ngAreaInformatio in response message, it
n includes the PRA information
provisioned by the CHF, in
which case the "presenceState"
attribute within the
PresenceInfo data type shall
not be supplied. When the data
type is present in request
message, it’s used to report
user presence reporting area
status.
The praId attribute within the
PresenceInfo data type shall be
the key of the map.
uetimeZone TimeZone OC 0..1 the UE Timezone the UE is
currently located
pduSessionInfor PDUSessionInforma M 1 PDU session level information,
mation tion including PDU session ID, PDU
type, SSC Mode, QoS, network
slicing etc.
unitCountInactivit DurationSec OC 0..1 threshold for the time period
yTimer resource idle
Upon the initial interaction with
the CHF, the SMF use this
attribute to provide pre-
configured threshold to CHF.
when present in response
message, it contains the
threshold supplied by CHF in
response of initial request to
override existing threshold in
SMF.
It’s only present when unit
count inactivity timer trigger is
active.
rANSecondaryR RANSecondaryRAT OC 0..1 Secondary RAT usage reported
ATUsageReport UsageReport from RAN.
3GPP
Release 15 35 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.2.7 Type UserInformation
Table 6.1.6.2.2.7-1: Definition of type UserInformation

y
servedGPSI Gpsi OC 0..1 the Generic Public Subscription
Identifier (GPSI) of the served
party, if available.
servedPEI Pei OC 0..1 the identification of Permanent
Equipment Identifier.
unauthenticatedF boolean OC 0..1 indicates the served SUPI is not
lag authenticated
roamerInOut RoamerInOut OC 0..1 In-bound or Out-bound roamer
3GPP
Release 15 36 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.2.8 Type PDUSessionInformation
Table 6.1.6.2.2.8-1: Definition of type PDUSessionInformation

y
networkSlicingInf NetworkSlicingInfo OM 0..1 information of network slice
o serving the PDU session
pduSessionID PduSessionId M 1
pduType PduSessionType OM 0..1 type of the PDU session
sscMode SscMode OC 0..1 information of SSC Mode type.
hPlmnId PlmnId OC 0..1 PLMN identifier of the home
network
servingNetworkF ServingNetworkFun Oc 0..1 This field holds serving Network
unctionID ctionID Function identifier.
servingCNPlmnId PlmnId Oc 0..1 Serving Core Network Operator
PLMN ID selected by the UE in
shared networks.
ratType RatType OC 0..1 the RAT Type of the PDU
session
dnnId Dnn M 1 a Data Network Name
dnnSelectionMod DnnSelectionMode OC 0..1 This field indicates how the
e DNN was selected.
chargingCharact string OC 0..1 the Charging Characteristics for
eristics this PDU session.
chargingCharact ChargingCharacteris OC 0..1 information about how the
eristicsSelection ticsSelectionMode "Charging Characteristics" was
Mode selected.
startTime DateTime OC 0..1 the time in UTC format which
represents the start of a PDU
session at the SMF
stopTime DateTime OC 0..1 the time in UTC format which
represents the stop of a PDU
session at the SMF
3gppPSDataOffS 3GPPPSDataOffSta OC 0..1 This field holds the 3GPP Data
tatus tus off Status when UE’s 3GPP
Data Off status is Activated or
Deactivated.
sessionStopIndic boolean OC 0..1 This field indicates to the CHF
ator that the PDU session has been
terminated.
pduAddress PDUAddress OC 0..1 Group of user ip address/prefix
diagnostics Diagnostics OC 0..1 provides a more detailed cause
value from SMF.
authorizedQoSInf AuthorizedDefaultQ OC 0..1 This field holds the authorized
ormation os QoS applied to PDU session.
subscribedQoSIn SubscribedDefaultQ OC 0..1 This field holds the subscribed
formation os Default QoS
authorizedSessio Ambr OC 0..1 This field holds the authorized
nAMBR session-AMBR.
subscribedSessio Ambr OC 0..1 This field holds the subscribed
nAMBR session-AMBR.
3GPP
Release 15 37 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.2.9 Type PDUContainerInformation
Table 6.1.6.2.2.9-1: Definition of type PDUContainerInformation

y
timeofFirstUsage DateTime OC 0..1 the time stamp for the first IP
packet to be transmitted and
mapped to the reporting used
unit.
timeofLastUsage DateTime OC 0..1 the time stamp for the last IP
mapped to the reporting used
unit.
qoSInformation QoSData OC 0..1 the QoS applied for the
reporting used unit.
In case gbrUl or gbrDl are
present for GBR flow, the GBR
targets are "GUARANTEED",
otherwise, are "
NOT_GUARANTEED".
aFCorrelationInfo string OC 0..1 An identifier, provided from the
rmation AF, correlating the
measurement for the Charging
key/Service identifier values in
this PCC rule with application
level reports.
userLocationInfor UserLocation OC 0..1 provides information on the
mation location
uetimeZone TimeZone OC 0..1 the UE Time Zone during the
used unit container interval.
rATType RatType OC 0..1 the RAT Type of the used unit
servingNodeID array(ServingNetwor OC 0..N the list of serving node
kFunctionID) identifiers during the used unit
container interval.
presenceReporti map(PresenceInfo) OC 0..N the Presence Reporting Area
ngAreaInformatio status of UE during the used
n unit container interval.
3gppPSDataOffS 3GPPPSDataOffSta OC 0..1 the 3GPP Data off Status
tatus tus during the used unit container
interval.
sponsorIdentity string OC 0..1 an identifier of the sponsor.
applicationservic string OC 0..1 an identifier of the application
eProviderIdentity service provider
chargingRuleBas string OC 0..1 the reference to group of PCC
eName rules predefined at the SMF.
6.1.6.2.2.10 Type NetworkSlicingInfo
Table 6.1.6.2.2.10-1: Definition of type NetworkSlicingInfo

y
sNSSAI Snssai M 1 Single Network Slice Selection
Assistance Information
3GPP
Release 15 38 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.2.11 Type PDUAddress
Table 6.1.6.2.2.11-1: Definition of type PDUAddress

y
pduIPv4Address Ipv4Addr OC 0..1 the IPv4 address of the served
SUPI allocated for the PDU
session
pduIPv6Address Ipv6Addr OC 0..1 the IPv6 address with prefix of
withPrefix the served SUPI allocated for
the PDU session
pduAddressprefix integer OC 0..1 PDU Address prefix length of
length an IPv6 typed Served PDU
Address. The field needs not
available for prefix length of 64
bits.
iPv4dynamicAddr boolean OC 0..1 This field indicates whether
essFlag served IPv4 address is
dynamically allocated. This field
is missing if address is static.
iPv6dynamicPrefi boolean OC 0..1 This field indicates whether
xFlag served IPv6 address prefix is
dynamically allocated. This field
is missing if address is static.
6.1.6.2.2.12 Type ServingNetworkFunctionID
Table 6.1.6.2.2.12-1: Definition of type ServingNetworkFunctionID

y
servingNetworkF NFIdentification M 0..1 Serving Network Function
unctionInformatio information: i.e. AMF or V-SMF.
n
aMFId AmfId OC 0..1 AMF identifier
6.1.6.2.2.13 Type RoamingQBCInformation
Table 6.1.6.2.1.13-1: Definition of type RoamingQBCInformation

y
multipleQFIcontai array(MultipleQFIcon Oc 0..N list of QFI containers
ner tainer)
uPFID NfInstanceId OC 0..1 identifer of UPF
roamingCharging RoamingChargingPr OC 0..1 Roaming Charging Profile
Profile ofile associated to the PDU session
for roaming QBC.
3GPP
Release 15 39 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.2.14 Type MultipleQFIcontainer
Table 6.1.6.2.1.14-1: Definition of type MultipleQFIcontainer
Attribute name Data type PCardinalit Description Applicability

y
triggers array (Trigger) Oc 0..N This field holds reason for
closing the QFI unit container.
triggerTimestamp DateTime Oc 0..1 This field holds the timestamp
when the reporting trigger
occur.
time.
volume in both uplink and
downlink directions.
volume in uplink direction.
volume in downlink direction.
localSequenceNu integer M 1 QFI data container sequence
mber number. It starts from 1 and
increased by 1 for each
container generation
qFIContainerInfor QFIContainerInforma OC 0..1 This field holds the QFI data
mation tion container information
6.1.6.2.2.15 Type RoamingChargingProfile
Table 6.1.6.2.1.15-1: Definition of type RoamingChargingProfile

y
triggers array(Trigger) OC 0..N Trigger for roaming QBC
partialRecordMet PartialRecordMetho Oc 0..1 method uses for partial record
hod d closure
3GPP
Release 15 40 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.2.16 Type QFIContainerInformation
Table 6.1.6.2.1.16-1: Definition of type QFIContainerInformation

y
qFI Qfi OM 0..1 QoS Flow Identifier (QFI)
reportTime DateTime OC 0..1 the time stamp when the QFI
data container was closed
timeofFirstUsage DateTime OC 0..1 the time stamp for the first IP
mapped to the QFI container
timeofLastUsage DateTime OC 0..1 the time stamp for the last IP
mapped to the QFI container.
qoSInformation QoSData OC 0..1 the QoS applied to QFI
container. In case gbrUl or
gbrDl are present for GBR QoS
flow, the GBR targets are
"GUARANTEED", otherwise,
are " NOT_GUARANTEED".
userLocationInfor UserLocation OC 0..1 provides information on the
mation location
uetimeZone TimeZone OC 0..1 UE Time Zone the UE is
currently located
presenceReporti map(PresenceInfo) OC 0..N the Presence Reporting Area
ngAreaInformatio status of UE during the used
n unit container interval.
rATType RatType OC 0..1 the RAT Type of the used unit
servingNetworkF array(ServingNetwor OC 0..N the list of serving Node
unctionID kFunctionI) Identifiers during the used unit
container interval.
3gppPSDataOffS 3GPPPSDataOffSta OC 0..1 the 3GPP Data off Status
tatus tus during the used unit container
interval.
6.1.6.2.2.17 Type RANSecondaryRATUsageReport
Table 6.1.6.2.2.17-1: Definition of type RANSecondaryRATUsageReport

rANSecondaryR RatType OM 0..1 RAT type associated to the
ATType reported usage on secondary
RAT.
The following values are
applicable:
- "NR"
- "EUTRA"
qosFlowsUsage Array(QosFlowsUsa OM 0..N list of containers per QFI with

Reports geReport) volumes reported.
3GPP
Release 15 41 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.2.18 Type QosFlowsUsageReport
Table 6.1.6.2.2.18-1: Definition of type QosFlowsUsageReport

qFI Qfi OM 0..1 QoS Flow Identifier (QFI)
startTimestamp DateTime OC 0..1 Start time of the reported

usage
endTimestamp DateTime OC 0..1 End time of the reported
usage
downlinkVolume Uint64 OC 0..1 Amount of volume in downlink
direction.
uplinkVolume Uint64 OC 0..1 Amount of volume in uplink
direction.
6.1.6.2.3 SMS Specified Data Type
This clause is additional attributes of the type ChargingDataRequest defined in clause 6.1.6.2.3.1 for SMS charging
described in 3GPP TS 32.274[28].
Table 6.1.6.2.3.1-1: SMS Specified attribute of type ChargingDataRequest

sMSCharging SMSChargingInform OM 0..1 This field holds the
Information ation SMSspecific information.
3GPP
Release 15 42 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.3.2 Type SMSChargingInformation
Table 6.1.6.2.2.3-2: Definition of type SMSChargingInformation
3GPP
Release 15 43 3GPP TS 32.291 V15.45.0 (2019-0912)

originatorInfo OriginatorInfo OM 0..1 originator of the SM
recipientInfo Array(RecipientInfo) OC 0..N recipient information for the
SM
userEquipment Pei OC 0..1 the identification of the
Info terminal
userLocationInfo UserLocation OC 0..1 provides information on the
location
uetimeZone TimeZone OC 0..1 the UE Time Zone the UE is
currently located
rATType RatType OC 0..1 The identification of the RAT
type.
sMSCAddress string OM 0..1 the address (e.g. E.164) of
the SMS-service centre
sending the Charging Data
Request used for producing
the record. (SMSC Address)
sMDataCodingSc integer OM 0..1 the data coding scheme used
heme within the SM. The
information to populate this
field is obtained from TP-DCS
header.
sMMessageType SMmessageType OM 0..1 identifies the message that
triggered the generation of
charging information.
sMReplyPathReq ReplyPathRequeste OC 0..1 an indication of whether a
uested d reply SM to an original SM
was requested to follow the
same path as identified by the
TP-Reply-Path (TP-RP) flag.
sMUserDataHea string OC 0..1 carries the user data header
der extracted from the user data
of the SM. The user data
header (TP-UDH) is specified
in TS 23.040 [x].
sMStatus string OC 0..1 the information from the TP-
Status field in a Status-Report
TPDU
sMDischargeTim DateTime OC 0..1 the time associated with the
e event being reported in the
SM Status field. This
information is only applicable
to delivery report charging
procedures.
numberofMessag Uint32 OC 0..1 the number of SMSs sent by
esSent the IMS application or the
total number of short
messages when this SM is
part of concatenated short
message, if applicable.
sMServiceType SMServiceType OC 0..1 the type of SM service that
caused the charging
interaction. It is only
applicable for SM
supplementary service
procedures.
sMSequenceNu Uint32 OC 0..1 the sequence number of this
mber SM within the concatenated
short message
sMSresult Uint32 C 0..1 the result of the attempted
SM transaction, if
unsuccessful.
This field is only for offline
charging.
submissionTime DateTime OC 0..1 the timestamp of when the
submitted SM arrived at the
originating SMS Node
sMpriority SMPriority OC 0..1 any priority information
3GPP
Release 15 44 3GPP TS 32.291 V15.45.0 (2019-0912)
associated with an SM
messageReferen string OM 0..1 the identity used to identify an
ce SM in the SMS node
associated with entity that
submitted it
messageSize Uint32 OM 0..1 the total number of short
messages when this SM is
part of concatenated short
message
messageClass MessageClass OM 0..1 implementation dependent
the value selected for a
specific transaction.
deliveryReportRe DeliveryReportRequ OC 0..1 indicates whether a delivery
quested ested report is requested by the SM
originator
6.1.6.2.3.3 Type OriginatorInfo
Table 6.1.6.2.3.3-1: Definition of type OriginatorInfo

originatorSUPI supi 0..1 SUPI of the originator of the
OM
SMS
originatorGPSI gpsi 0..1 GPSI of the originator of the
OC
SMS
originatorOtherA SMAddressInfo 0..1 the address of the recipient of
ddress OM the SM, when different from
SUPI and GPSI
originatorReceive SMAddressInfo 0..1 original, unmodified address
dAddress of the originator of the SM, as
received by the SMS node, in
OC case address manipulation
(such as number plan
corrections) have been
applied in the SMS node.
originatorSCCP string 0..1 SCCP calling address used to
Address OC receive the SM at the SMS
node
sMOriginatorInter Interface 0..1 Provide the information
face describing the interface on
OM
which the SM was received
by the SMS node.
sMOriginatorProt string 0..1 the protocol used for the SM
OC
ocolId by originator
3GPP
Release 15 45 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.3.4 Type RecipientInfo
Table 6.1.6.2.3.4-1: Definition of type RecipientInfo

recipientSUPI supi 0..1 SUPI of the recipient of the
OM SM, as received by the SMS
Node
recipientGPSI gpsi 0..1 GPSI of the recipient of the
OC SM, as received by the SMS
Node
recipientOtherAd Array(recipientAddre OC 0..N the address of the recipient of
dress ss) the SM, as received by the
SMS Node, when different
from SUPI and GPSI
recipientReceive Array(SMAddressInf OC 0..N original, unmodified address
dAddress o) of the recipient of the SM, as
received by the SMS node, in
case address manipulation
(such as number plan
corrections) have been
applied in the SMS node.
recipientSCCPAd string OC 0..1 SCCP called address used by
dress the SMS node to onward
deliver the SM
sMDestinationInt SMInterface OM 0..1 containing information
erface describing the interface on
which the SM was requested
to be delivered
sMRecipientProt string OC 0..1 holds the TP-PROTOCOL-ID
ocolId (TP-PID)
6.1.6.2.3.5 Type SMAddressInfo
Table 6.1.6.2.3.5-1: Definition of type SMAddressInfo

sMaddressType SMAddressType OC 0..1 the type of address carried
sMaddressData string 0..1 the address information and
OC formatted according type of
address
sMaddressDomai SMAddressDomain OC 0..1 the domain/network to which
n the associated address
resides
6.1.6.2.3.6 Type RecipientAddress
Table 6.1.6.2.3.6-1: Definition of type RecipientAddress

recipientAddressI SMAddressInfo 0..1 indicates the type of address
OC
nfo carried
sMaddresseeTyp SMAddresseeType 0..1 identifies the how the
e OC recipient is addressed in the
header of an MM
3GPP
Release 15 46 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.2.3.7 Type MessageClass
Table 6.1.6.2.3.7-1: Definition of type MessageClass

classIdentifier ClassIdentifier OC 0..1 indicate the class identifier
tokenText string 0..1 contains extension
OC
information
6.1.6.2.3.8 Type SMAddressDomain
Table 6.1.6.2.3.8-1: Definition of type SMAddressDomain

domainName string 0..1 represents a fully qualified
OC
domain name (FQDN).
3GPPIMSIMCCM string 0..1 MCC and MNC extracted
NC from the user’s IMSI (first 5 or
OC
6 digits, as applicable from
the presented IMSI.
6.1.6.2.3.9 Type SMInterface
Table 6.1.6.2.3.9-1: Definition of type SMInterface

interfaceId string 0..1 the interface identification
OC provided by the messaging
node (originator/destination).
interfaceText string 0..1 It is the consolidation
information about the
OC
application associated with
the charging event
interfacePort string OC 0..1 the port-identification or
contains information about
the transport layer port used
by the application associated
with the charging event
interfaceType InterfaceType 0..1 type of interface / nature of
the transaction in the
OC
messaging node for which the
charging event occurs
6.1.6.3 Simple data types and enumerations
6.1.6.3.1 Introduction
This subclause defines simple data types and enumerations that can be referenced from data structures defined in the
previous subclauses.
6.1.6.3.2 Simple data types

The simple data types defined in table 6.1.6.3.2-1 shall be supported.
Table 6.1.6.3.2-1: Simple data types
Type Name Type Definition Description Applicability

Diagnostics integer a more detailed cause value from SMF
IPFilterRule string filter rules corresponding to services
3GPP
Release 15 47 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.3.3 Enumeration: NotificationType
Table 6.1.6.3.3-1: Enumeration NotificationType
Enumeration value Description Applicability

REAUTHORIZATION This value is used to indicate re-
authorization.
ABORT_CHARGING This value is used to indicate termination of
charging for PDU session.
6.1.6.3.4 Enumeration: NodeFunctionality
Table 6.1.6.3.4-1: Enumeration NodeFunctionality

SMF This field identifies that NF is a SMF.
AMF This field identifies that NF is a AMF.
SMSF This field identifies that NF service
consumer is a SMSF.
6.1.6.3.5 Enumeration: ChargingCharacteristicsSelectionMode
Table 6.1.6.3.5-1: Enumeration ChargingCharacteristicsSelectionMode

HOME_DEFAULT the subscriber belongs to the same PLMN
as the SMF
ROAMING_DEFAULT the subscriber belongs to same PLMN and
the AMF belongs to a different PLMN
VISITING_DEFAULT the subscriber belongs to a different PLMN
3GPP
Release 15 48 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.3.6 Enumeration: TriggerType
Table 6.1.6.3.6-1: Enumeration TriggerType
3GPP
Release 15 49 3GPP TS 32.291 V15.45.0 (2019-0912)
Enumeration value Description Applicabilit

y
QUOTA_THRESHOLD the quota threshold has been reached
QHT the quota holding time specified in a
previous response has been hit (i.e. the
quota has been unused for that period of
time)
FINAL a service termination has happened
QUOTA_EXHAUSTED the quota has been exhausted
VALIDITY_TIME the credit authorization lifetime provided from
CHF has expired
OTHER_QUOTA_TYPE usage reporting of the particular quota type
indicated in the used unit container where it
appears is that, for a multi-dimensional
quota, one reached a trigger condition and
the other quota is being reported.
FORCED_REAUTHORISATION a Server initiated re-authorization procedure,
i.e. receipt of notify service operation
UNIT_COUNT_INACTIVITY_TIMER the unit count inactivity timer has expired
ABNORMAL_RELEASE PDU session has abnormal released.
QOS_CHANGE In request message, this value is used to
indicate that QoS change has happened.
Any of elements of QoSData may result in
QoS change.
In response message, this value is used to
indicate that a change of authorized QoS
shall cause the service consumer to ask for
a re-authorization of the associated quota
VOLUME_LIMIT Volume limit has been reached.
TIME_LIMIT Time limit has been reached
EVENT_LIMIT Event limit has been reached
PLMN_CHANGE PLMN has been changed.
USER_LOCATION_CHANGE In request message, this value is used to
indicate that User location has been
changed.
indicate that a change in the end user
location shall cause the service consumer to
ask for a re-authorization of the associated
quota
RAT_CHANGE In request message, this value is used to
indicate that RAT type has been changed.
indicate that a change in the radio access
technology shall cause the service consumer
to ask for a re-authorization of the
associated quota
SESSION_AMBR_CHANGE In request message, this value is used to
indicate that Session AMBR has been
changed.
indicate that a change in the session AMBR
shall cause the service consumer to ask for
a re-authorization of the associated quota.
GFBR_GUARANTEED_STATUS_CHAN this value is used to indicate that GBR
GE targets for the indicated SDFs are changed
("NOT_GUARANTEED" or "GUARANTEED"
again).
UE_TIMEZONE_CHANGE In request message, this value is used to
indicate that UE timezone has been
changed.
indicate that a change in the time zone
where the end user is located shall cause
the service consumer to ask for a re-
authorization of the associated quota.
TARIFF_TIME_CHANGE Tariff time change has happened.
3GPP
Release 15 50 3GPP TS 32.291 V15.45.0 (2019-0912)
MAX_NUMBER_OF_CHANGES_IN Max number of change has been reached

CHARGING_CONDITIONS
MANAGEMENT_INTERVENTION Management intervention
CHANGE_OF_UE_PRESENCE_IN In request message, this value is used to
PRESENCE_REPORTING_AREA indicate that Change of UE presence in PRA
has happened.
indicate a request of reporting the event that
the user enters/leaves the area(s) as
indicated in the presenceReportingArea
Attribute
CHANGE_OF_3GPP_PS_DATA_OFF_S In request message, this value is used to
TATUS indicate that Change of 3GPP PS Data off
status has happened.
indicate that a change in the 3GPP PS Data
off status shall cause the service consumer
to ask for a re-authorization of the
associated quota
SERVING_NODE_CHANGE A serving node (e.g., AMF) change in the NF
Consumer
REMOVAL_OF_UPF A used UPF is removed
ADDITION_OF_UPF A new UPF is added.
START_OF_SERVICE_DATA_FLOW A Service Data Flow has started
6.1.6.3.7 Enumeration: FinalUnitAction
Table 6.1.6.3.7-1: Enumeration FinalUnitAction

TERMINATE The service consumer should terminate the
service session.
REDIRECT The service consumer should redirect the
user to the address specified in the
redirectServerAddress attribute.
RESTRICT_ACCESS The service consumer should restrict the
user access according to the IP packet
filters defined in the restrictionFilterRule
attribute or
according to the IP packet filters identified
by the filterId attribute.
6.1.6.3.8 Enumeration: RedirectAddressType
Table 6.1.6.3.8-1: Enumeration RedirectAddressType

IPV4 the redirect server address is IPV4.
IPV6 the redirect server address is IPV6.
URL the redirect server address is URL.
3GPP
Release 15 51 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.3.9 Enumeration: TriggerCategory
Table 6.1.6.3.9-1: Enumeration TriggerCategory

y
IMMEDIATE_REPORT chargeable events for which, when occurring,
the charging data generated by the NF
Consumer triggers a Charging Event towards
the CHF.
DEFERRED_REPORT chargeable events for which, when occurring,
the charging data generated by the NF
Consumer, does not trigger a Charging Event
towards the CHF .
6.1.6.3.10 Enumeration: QuotaManagementIndicator
Table 6.1.6.3.10-1: Enumeration QuotaManagementIndicator

ONLINE_CHARGING quota management control
OFFLINE_CHARGING without quota management control
6.1.6.3.11 Enumeration: FailureHandling
Table 6.1.6.3.11-1: Enumeration FailureHandling

TERMINATE the service shall only be granted for as
long as there is a connection between NF
consumer and the CHF.
CONTINUE the NF consumer should re-send and
continue the request to an alternative
server in the case of transport temporary
failures, provided that a failover procedure
is supported in the CHF and the NF
consumer, and that an alternative server is
available. Otherwise, the service SHOULD
be granted, even if charging data request
can't be delivered.
RETRY_AND_TERMINATE the NF consumer should re-send the
request to an alternative server in the case
of transport temporary failures, provided
that a failover procedure is supported in the
CHF and NF consumer, and that an
alternative server is available. Otherwise,
the service should not be granted when the
charging data request can't be delivered.
3GPP
Release 15 52 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.3.12 Enumeration: SessionFailover
Table 6.1.6.3.12-1: Enumeration SessionFailover

FAILOVER_NOT_SUPPORTED The Nchf_ConvergedCharging messages
could not be moved to an alternative
destination in the case of communication
failure.
This is the default behaviour if the attribute
is not present in the response.
FAILOVER_SUPPORTED The Nchf_ ConvergedCharging messages
should be moved to an alternative
destination in the case of communication
failure.
6.1.6.3.13 Enumeration: 3GPPPSDataOffStatus
Table 6.1.6.3.13-1: Enumeration 3GPPPSDataOffStatus

ACTIVE 3GPP PS data off status is active.
INACTIVE 3GPP PS data off status is inactive.
3GPP
Release 15 53 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.3.14 Enumeration: ResultCode
Table 6.1.6.3.14-1: Enumeration ResultCode

y
SUCCESS The CHF grants the
service to the end-
user.
This applies to the
rating group.
END_USER_SERVICE_DENIED The CHF denies the
service request due
to end-user service
restrictions or
limitations related to
the end-user. If the
request contained
used units they shall
be deducted, if
applicable.
This applies to the
rating group.
QUOTA_MANAGEMENT_NOT_APPLICABLE The CHF determines
that the service can
be granted to the end
user without quota
management, and
used units shall be
reported.
This applies to the
rating group.
QUOTA_LIMIT_REACHED The CHF denies the
service request since
the end user's
account could not
cover the requested
service. If the request
contained used units
they shall be
deducted, if
applicable.
This applies to the
rating group.
END_USER_SERVICE_REJECTED The CHF denies the
service request in
order to terminate the
service for which
credit is requested.
This applies to the
rating group.
RATING_FAILED The CHF determines
that the service
cannot be rated due
to insufficient rating
input, incorrect
parameter
combination or
unrecognized
parameter, or
parameter value.
This applies to the
rating group.
3GPP
Release 15 54 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.3.15 Enumeration: PartialRecordMethod
Table 6.1.6.3.15-1: Enumeration PartialRecordMethod
DEFAULT Default method used for partial records

INDIVIDUAL Individual methods used for partial records
6.1.6.3.16 Enumeration: RoamerInOut

The enumeration RoamerInOut indicates whether the user is an in-bound or out-bound roamer.
Table 6.1.6.3.16-1: Enumeration RoamerInOut
Enumeration Description Applicability

value
IN_BOUND In-bound roamer.
OUT_BOUN Out-bound roamer.
D
6.1.6.3.17 Void
6.1.6.3.18 Enumeration: SMMessageType
Table 6.1.6.3.18-1: Enumeration SMMessageType

y
SUBMISSION The SMS message type is submission.
DELIVERY_REPORT The SMS message type is delivery report.
SM_SERVICE_REQUEST The SMS message type is SMS service request.
6.1.6.3.19 Enumeration: SMPriority
Table 6.1.6.3.19-1: Enumeration SMPriority

y
LOW low priority
NORMAL normal priority
HIGH high priority
6.1.6.3.20 Enumeration: DeliveryReportRequested
Table 6.1.6.3.20-1: Enumeration DeliveryReportRequested

y
YES Delivey report is requested.
NO The delivery report is not requested.
3GPP
Release 15 55 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.3.21 Enumeration: InterfaceType
Table 6.1.6.3.21-1: Enumeration InterfaceType

y
UNKNOWN Interface type is unknown,
MOBILE_ORIGINATING Interface type is mobile originated.
MOBILE_TERMINATING Interface type is mobile terminated.
APPLICATION_ORIGINATING Interface type is application originated.
APPLICATION_TERMINATION Interface type is application terminated.
6.1.6.3.22 Enumeration: ClassIdentifier
Table 6.1.6.3.22-1: Enumeration ClassIdentifier

y
PERSONAL The class identifier is personal.
ADVERTISEMENT The class identifier is advertisement.
INFORMATIONAL The class identifier is informational.
AUTO The class identifier is auto.
6.1.6.3.23 Enumeration: SMAddressType
Table 6.1.6.3.23-1: Enumeration SMAddressType

y
EMAIL_ADDRESS The carried address type is EMAIL.
MSISDN The carried address type is MSISDN.
IPV4_ ADDRESS The carried address type is IPv4.
IPV6_ ADDRESS The carried address type is IPv6.
NUMERIC_SHORTCODE The carried address type is numeric shortcode.
ALPHANUMERIC_SHORTCODE The carried address type is alphanumeric
shortcode.
OTHER The carried address type is other.
IMSI The carried address type is IMSI
6.1.6.3.24 Enumeration: SMAddresseeType
Table 6.1.6.3.24-1: Enumeration SMAddresseeType

y
TO The addressee type is TO.
CC The addressee type is CC.
BCC The addressee type is BCC.
3GPP
Release 15 56 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.3.25 Enumeration: SMServiceType
Table 6.1.6.3.25-1: Enumeration SMServiceType

y
VAS4SMS_SHORT_MESSAGE_CONTENT The type of SM service is VAS4SMS short
_PROCESSING message content processing.
VAS4SMS_SHORT_MESSAGE_FORWAR The type of SM service is VAS4SMS short
DING message forwarding.
VAS4SMS_SHORT_MESSAGE_FORWAR The type of SM service is VAS4SMS short
DING _MULTIPLE_SUBSCRIPTIONS message forwarding multiple
subscriptions.
VAS4SMS_SHORT_MESSAGE_FILTERIN The type of SM service is VAS4SMS short
G message filtering.
VAS4SMS_SHORT_MESSAGE_RECEIPT The type of SM service is VAS4SMS short
message receipt.
VAS4SMS_SHORT_MESSAGE_NETWOR The type of SM service is VAS4SMS short
K_STORAGE message network storage.
VAS4SMS_SHORT_MESSAGE_TO_MULT The type of SM service is VAS4SMS short
IPLE_DESTINATIONS message to multiple destinations.
VAS4SMS_SHORT_MESSAGE_VIRTUAL_ The type of SM service is VAS4SMS short
PRIVATE_NETWORK(VPN) message virtual private network.
VAS4SMS_SHORT_MESSAGE_AUTO_RE The type of SM service is VAS4SMS short
PLY message auto reply.
VAS4SMS_SHORT_MESSAGE_PERSONA The type of SM service is VAS4SMS short
L_SIGNATURE message personal signature.
VAS4SMS_SHORT_MESSAGE_DEFERRE The type of SM service is VAS4SMS short
D_DELIVERY message deferred delivery.
6.1.6.3.26 Enumeration: ReplyPathRequested
Table 6.1.6.3.26.1: Enumeration ReplyPathRequested

y
NO_REPLY_PATH_SET The reply SM to an original SM was requested
to follow the same path.
REPLY_PATH_SET The reply SM to an original SM was not
requested to follow the same path.
6.1.6.3.27 Enumeration: DnnSelectionMode
Table 6.1.6.3.27.1: Enumeration DnnSelectionMode
Enumeration value Description

"VERIFIED" UE or network provided DNN, subscription verified
"UE_DNN_NOT_VERIFIED" UE provided DNN, subscription not verified
"NW_DNN_NOT_VERIFIED" Network provided DNN, subscription not verified
6.1.6.3.28 Enumeration: EventType
Table 6.1.6.3.28.1: Enumeration EventType

IEC This value is used to indicate immediate event
charging.
PEC This value is used to indicate post event charging.
3GPP
Release 15 57 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.6.4 Data types describing alternative data types or combinations of data types
None.
6.1.6.5 Binary data

None.
6.1.7 Error handling
6.1.7.1 General
HTTP error handling shall be supported as specified in subclause 5.2.4 of 3GPP TS 29.500 [4].
For the Nchf_ConvergedCharging API, HTTP error responses shall be supported as specified in subclause 4.8 of
3GPP TS 29.501 [2]. Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [4] shall be
supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP
method in table 5.2.7.1-1 of 3GPP TS 29.500 [4]. In addition, the requirements in the following subclauses shall apply.
6.1.7.2 Protocol Errors

In this Release of the specification, there are no additional protocol errors applicable for the Nchf_ConvergedCharging
API compared to the Protocol Error Handling specified in subclause 5.2.7.2 of 3GPP TS 29.500 [7].
6.1.7.3 Application errors

The application errors defined for the Nchf_ConvergedCharging API are listed in table 6.1.7.3-1. The CHF shall
include in the HTTP status code a "ProblemDetails" data structure with the "cause" attribute indicating the application
error as listed in table 6.1.7.3-1. The common application errors defined in the Table 5.2.7.2-1 in 3GPP TS 29.500 [7]
may also be used for the Npcf_ConvergedCharging service.
Table 6.1.7.3-1: Application errors
Application Error HTTP status code Description

CHARGING_FAILED 400 Bad Request The HTTP request is rejected because the set
of session or subscriber information needed
by the CHF for charging or CDR creation is
incomplete or erroneous or not available. (E.g.
Rating Group, subscriber information)
RE_AUTHORIZATION_FAILED 400 Bad Request The HTTP request is rejected because the set
of information needed by the NF Consumer
(CTF) to report the usage is incomplete or
erroneous or not available.
CHARGING_NOT_APPLICABLE 403 Forbidden The HTTP request is rejected by the CHF
since it has been determined that the service
can be allowed to the end user without any
charging or CDR creation.
USER_UNKNOWN 404 Not Found The HTTP request is rejected because the
end user specified in the request cannot be
served by the CHF.
END_USER REQUEST_DENIED 403 Forbidden The HTTP request denied by the CHF due to
restrictions or limitations related to the end-
user.
QUOTA_LIMIT_REACHED 403 Forbidden The HTTP request denied by the CHF
because the end user's account could not
cover the requested service. If the request
contained used units they are deducted, if
applicable.
END_USER_REQUEST_REJECTED 403 Forbidden The HTTP request rejected by the CHF due to
end-user restrictions or limitations.
3GPP
Release 15 58 3GPP TS 32.291 V15.45.0 (2019-0912)
6.1.8 Feature negotiation

The optional features in table 6.1.8-1 are defined for the Nchf_ConvergedCharging API. They shall be negotiated using
the extensibility mechanism defined in subclause 6.6 of 3GPP TS 29.500 [299].
Table 6.1.8-1: Supported Features
Feature number Feature Name Description
3GPP
Release 15 59 3GPP TS 32.291 V15.45.0 (2019-0912)
7 Bindings of CDR field, Information Element and

Resource Attribute
7.0 General
This clause aims to describe the mapping between the Service Charging Information element, Resource Attribute and
CDR field for 5G charging.
Table 7.1-1 and 7.2-1 describes the mapping of the Information Element, Resource Attribute and CDR field of CHF-
CDR for 5G charging.
3GPP
Release 15 60 3GPP TS 32.291 V15.45.0 (2019-0912)
7.1 Bindings of common CDR field, Information Element and

Resource Attribute
Table 7.1-1: Bindings of common CDR field, Information Element and Resource Attribute
3GPP
Release 15 61 3GPP TS 32.291 V15.45.0 (2019-0912)
Information Element CDR Field Resource Attribute

Session Identifier Charging Session Identifier /{ ChargingDataRef }/
ChargingDataRequest
Subscriber Identifier Subscriber Identifier /subscriberIdentifier
Invocation Timestamp - /invocationTimeStamp
Invocation Sequence Number - /invocationSequenceNumber
One-time Event - /oneTimeEvent
NF Consumer Identification NF Information /nfConsumerIdentification
NF Name NF Name /nfConsumerIdentification/nFName
NF Address NF Address /nfConsumerIdentification/nFIPv4Address
/nfConsumerIdentification/nFIPv6Address
/nfConsumerIdentification/nFFqdn
NF PLMN ID NF PLMN ID /nfConsumerIdentification/nFPLMNID
NF Functionality Record Type /nfConsumerIdentification/nodeFunctionality
Notify URI /notifyUri
Service Specification Information Service Specification Information /serviceSpecificationInfo
Multiple Unit Usage List of Multiple Unit Usage /multipleUnitUsage
Rating Group Rating Group /multipleUnitUsage/ratingGroup
Requested Unit - /multipleUnitUsage/requestedUnit
Time - /multipleUnitUsage/requestedUnit/time
Total Volume - /multipleUnitUsage/requestedUnit/totalVolume
Uplink Volume - /multipleUnitUsage/requestedUnit/uplinkVolume
Downlink Volume - /multipleUnitUsage/requestedUnit/
downlinkVolume
Service Specific Units - /multipleUnitUsage/requestedUnit/
serviceSpecificUnits
Used Unit Container Used Unit Container
/multipleUnitUsage/usedUnitContainer
Service Identifier Service Identifier /multipleUnitUsage/usedUnitContainer/
serviceId
Quota management Indicator Quota management Indicator /multipleUnitUsage/usedUnitContainer/
quotaManagementIndicator
Triggers Triggers /multipleUnitUsage/usedUnitContainer/triggers
Trigger Timestamp Trigger Timestamp /multipleUnitUsage/usedUnitContainer/
triggerTimestamp
Time Time /multipleUnitUsage/usedUnitContainer/time
Total Volume Total Volume /multipleUnitUsage/usedUnitContainer/
totalVolume
Uplink Volume Uplink Volume /multipleUnitUsage/usedUnitContainer/
uplinkVolume
Downlink Volume Downlink Volume /multipleUnitUsage/usedUnitContainer/
downlinkVolume
Service Specific Unit Service Specific Unit /multipleUnitUsage/usedUnitContainer/
Event Time Stamps Event Time Stamps /multipleUnitUsage/usedUnitContainer/
eventTimeStamps
Local Sequence Number Local Sequence Number /multipleUnitUsage/usedUnitContainer/
localSequenceNumber
Triggers Triggers /triggers
ChargingDataResponse
Invocation Timestamp /invocationTimeStamp
Invocation Sequence Number /invocationSequenceNumber
Session Failover - /sessionFailover
Triggers - /triggers
Multiple Unit Information - /multipleUnitInformation
Result Code - /multipleUnitInformation/resultCode
Rating Group - /multipleUnitInformation/ratingGroup
Granted Unit - /multipleUnitInformation/grantedUnit
Tariff Time Change - /multipleUnitInformation/
grantedUnit/tariffTimeChange
Time - /multipleUnitInformation/grantedUnit/time
Total Volume - /multipleUnitInformation/grantedUnit/
totalVolume
Uplink Volume - /multipleUnitInformation/grantedUnit/
uplinkVolume
3GPP
Release 15 62 3GPP TS 32.291 V15.45.0 (2019-0912)

Downlink Volume - /multipleUnitInformation/grantedUnit/
downlinkVolume
Service Specific Units - /multipleUnitInformation/grantedUnit/
Triggers - /multipleUnitInformation/triggers
Validity Time - /multipleUnitInformation/validityTime
Quota Holding Time - /multipleUnitInformation/quotaHoldingTime
Final Unit Indication - /multipleUnitInformation/finalUnitIndication
Time Quota Threshold - /multipleUnitInformation/timeQuotaThreshold
Volume Quota Threshold - /multipleUnitInformation/volumeQuotaThreshold
Unit Quota Threshold - /multipleUnitInformation/unitQuotaThreshold
Invocation Result - /invocationResult
Invocation Result code - /invocationResult/error/cause
Failed parameter - /invocationResult/error/invalidParams
Failure Handling - /invocationResult/failureHandling
3GPP
Release 15 63 3GPP TS 32.291 V15.45.0 (2019-0912)
7.2 Bindings for 5G data connectivity

Table 7.2-1: Bindings of 5G data connectivity CDR field, Information Element and Resource Attribute
3GPP
Release 15 64 3GPP TS 32.291 V15.45.0 (2019-0912)

ChargingDataRequest
Multiple Unit Usage List of Multiple Unit Usage /multipleUnitUsage
UPF ID UPF ID /multipleUnitUsage/uPFID
Used Unit Container Used Unit Container
/multipleUnitUsage/usedUnitContainer
PDU Container Information PDU Container Information /multipleUnitUsage/
usedUnitContainer/pDUContainerInformation
Time of First Usage Time of First Usage /multipleUnitUsage/
usedUnitContainer/
pDUContainerInformation/timeofFirstUsage
Time of Last Usage Time of Last Usage /multipleUnitUsage/
usedUnitContainer/
pDUContainerInformation/timeofLastUsage
QoS Information QoS Information /multipleUnitUsage/
usedUnitContainer/pDUContainerInformation/
qoSInformation
AF Correlation AF Correlation Information /multipleUnitUsage/
Information usedUnitContainer/
pDUContainerInformation/
aFCorrelationInformation
User Location User Location Information /multipleUnitUsage/
Information usedUnitContainer/
userLocationInformation
UE Time Zone UE Time Zone /multipleUnitUsage/
uetimeZone
RAT Type RAT Type /multipleUnitUsage/
rATType
Serving Network Serving Network Function /multipleUnitUsage/
Function ID ID usedUnitContainer/pDUContainerInformation/
servingNodeID
Presence Reporting Presence Reporting Area /multipleUnitUsage/
Area Information Information usedUnitContainer/pDUContainerInformation/
presenceReportingAreaInformation
3GPP PS Data Off 3GPP PS Data Off Status /multipleUnitUsage/
Status usedUnitContainer/pDUContainerInformation/
3gppPSDataOffStatus
Sponsor Identity Sponsor Identity /multipleUnitUsage/
usedUnitContainer/
pDUContainerInformation/sponsorIdentity
Application Service Application Service /multipleUnitUsage/
Provider Identity Provider Identity usedUnitContainer/
applicationserviceProviderIdentity
Charging Rule Base Charging Rule Base Name /multipleUnitUsage/
Name usedUnitContainer/pDUContainerInformation/
chargingRuleBaseName
PDU Session Charging PDU Session Charging Information /pDUSessionChargingInformation
Information
Charging Id Charging Id /pDUSessionChargingInformation/chargingId
User Information User Information /pDUSessionChargingInformation/
userInformation
User Identifier User Identifier /pDUSessionChargingInformation/
userInformation/servedGPSI
User Equipment Info User Equipment Info /pDUSessionChargingInformation/
userInformation/ servedPEI
Unauthenticated Flag Unauthenticated Flag /pDUSessionChargingInformation/
userInformation/unauthenticatedFlag
Roamer In Out Roamer In Out /pDUSessionChargingInformation/
userInformation/roamerInOut
User Location Info User Location Info /pDUSessionChargingInformation/
userLocationinfo
User Location Time User Location Time /pDUSessionChargingInformation/
userLocationTime
3GPP
Release 15 65 3GPP TS 32.291 V15.45.0 (2019-0912)

UE Time Zone UE Time Zone /pDUSessionChargingInformation/uEtimeZone
Presence Reporting Area Presence Reporting Area /pDUSessionChargingInformation/
Information Information presenceReportingAreaInformation
PDU Session Information PDU Session Information /pDUSessionChargingInformation/
pduSessionInformation
PDU Session ID PDU Session ID /pDUSessionChargingInformation/
pduSessionInformation/pduSessionID
Network Slice Instance Network Slice Instance /pDUSessionChargingInformation/
Identifier Identifier pduSessionInformation/networkSlicingInfo
PDU Type PDU Type /pDUSessionChargingInformation/
pduSessionInformation/pduType
PDU Address PDU Address /pDUSessionChargingInformation/
pduSessionInformation/pduAddress
PDU IP Address PDU IP Address /pDUSessionChargingInformation/
pduSessionInformation/pduAddress/
pduIPv4Address
/pDUSessionChargingInformation/
pduIPv6Addresswithprefix
PDU Address prefix PDU Address prefix length /pDUSessionChargingInformation/
length pduSessionInformation/pduAddress/
pduAddressprefixlength
Dynamic Address Flag Dynamic Address Flag /pDUSessionChargingInformation/
iPv4dynamicAddressFlag
pDUSessionChargingInformation/
iPv6dynamicAddressFlag
SSC Mode SSC Mode /pDUSessionChargingInformation/
pduSessionInformation/sscMode
SUPI PLMN ID SUPI PLMN ID /pDUSessionChargingInformation/
pduSessionInformation/hPlmnId
Serving Network Function Serving Network Function ID /pDUSessionChargingInformation/
ID pduSessionInformation/
servingNetworkFunctionID
Serving CN PLMN ID Serving CN PLMN ID /pDUSessionChargingInformation/
pduSessionInformation/servingCNPlmnId
RAT Type RAT Type /pDUSessionChargingInformation/
pduSessionInformation/ratType
Data Network Name Data Network Name Identifier /pDUSessionChargingInformation/
Identifier pduSessionInformation/dnnid
DNN Selection Mode DNN Selection Mode /pDUSessionChargingInformation/
pduSessionInformation/dnnselectionMode
Authorized QoS Authorized Qos Information /pDUSessionChargingInformation/
information pduSessionInformation/
authorizedqoSInformation
Subscribed QoS Subscribed QoS Information /pDUSessionChargingInformation/
Information pduSessionInformation/
subscribedQoSInformation
Authorized Session-AMBR Authorized Session-AMBR /pDUSessionChargingInformation/
pduSessionInformation/
authorizedSessionAMBR
Subscribed Session-AMBR Subscribed Session-AMBR /pDUSessionChargingInformation/
pduSessionInformation/
subscribedSessionAMBR
Charging Characteristics Charging Characteristics /pDUSessionChargingInformation/
pduSessionInformation/chargingCharacteristics
Charging Characteristics Charging Characteristics /pDUSessionChargingInformation/
Selection Mode Selection Mode pduSessionInformation/
chargingCharacteristicsSelectionMode
PDU session start Time PDU session start Time /pDUSessionChargingInformation/
pduSessionInformation/startTime
PDU session stop Time PDU session stop Time /pDUSessionChargingInformation/
pduSessionInformation/stopTime
Diagnostics Diagnostics /pDUSessionChargingInformation/
pduSessionInformation/diagnostics
3GPP
Release 15 66 3GPP TS 32.291 V15.45.0 (2019-0912)

3GPP PS Data Off Status 3GPP PS Data Off Status /pDUSessionChargingInformation/
pduSessionInformation/3gppPSDataOffStatus
Session Stop Indicator Session Stop Indictor /pDUSessionChargingInformation/
pduSessionInformation/sessionStopIndicator
Unit Count Inactivity Timer - /pDUSessionChargingInformation/
unitCountInactivityTimer
RAN Secondary RAT Usage RAN Secondary RAT Usage /
Report Report pDUSessionChargingInformation/
rANSecondaryRATUsageReport
NG RAN Secondary RAT NG RAN Secondary RAT Type /
Type pDUSessionChargingInformation/
rANSecondaryRATUsageReport/
rANSecondaryRATType
Qos Flows Usage Reports Qos Flows Usage Reports /
pDUSessionChargingInformation/
rANSecondaryRATUsageReport/
qosFlowsUsageReports
Roaming QBC information Roaming QBC information /roamingQBCInformation
Multiple QFI container Multiple QFI container /roamingQBCInformation/multipleQFIcontainer
Triggers Triggers /roamingQBCInformation/multipleQFIcontainer/
triggers
Trigger Timestamp Trigger Timestamp /roamingQBCInformation/multipleQFIcontainer/
triggerTimestamp
Time Time /roamingQBCInformation/multipleQFIcontainer/
time
Total Volume Total Volume /roamingQBCInformation/multipleQFIcontainer/
totalVolume
Uplink Volume Uplink Volume /roamingQBCInformation/
multipleQFIcontainer/uplinkVolume
Downlink Volume Downlink Volume /roamingQBCInformation/
multipleQFIcontainer/downlinkVolume
Local Sequence Number Local Sequence Number /roamingQBCInformation/
multipleQFIcontainer/localSequenceNumber
QFI Container information QFI Container information /roamingQBCInformation/
multipleQFIcontainer/qFIContainerInformation
QoS Flow Id QoS Flow Id /roamingQBCInformation/
multipleQFIcontainer/qFIContainerInformation/
qFI
Time of First Usage Time of First Usage /roamingQBCInformation/
multipleQFIcontainer/
qFIContainerInformation/timeofFirstUsage
Time of Last Usage Time of Last Usage /roamingQBCInformation/
qFIContainerInformation/timeofLastUsage
QoS Information QoS Information /roamingQBCInformation/
qoSInformation
User Location Information User Location Information /roamingQBCInformation/
qFIContainerInformation/
userLocationInformation
UE Time Zone UE Time Zone /roamingQBCInformation/
uetimeZone
Presence Reporting Area Presence Reporting Area /roamingQBCInformation/
Information Information multipleQFIcontainer/qFIContainerInformation/
presenceReportingAreaInformation
RAT Type RAT Type /roamingQBCInformation/
rATType
Report Time Report Time /roamingQBCInformation/
reportTime
Serving Network Function Serving Network Function ID /roamingQBCInformation/
ID multipleQFIcontainer/
qFIContainerInformation/
3GPP
Release 15 67 3GPP TS 32.291 V15.45.0 (2019-0912)

servingNetworkFunctionID
3GPP PS Data Off Status 3GPP PS Data Off Status /roamingQBCInformation/
3gppPSDataOffStatus
UPF ID UPF ID /roamingQBCInformation/uPFID
Roaming Charging Profile Roaming Charging Profile /roamingQBCInformation/
roamingChargingProfile
Trigger Trigger /roamingQBCInformation/
roamingChargingProfile/trigger
Partial record method Partial record method /roamingQBCInformation/
roamingChargingProfile/partialRecordMethod
Multiple Unit information - /multipleUnitInformation
UPF ID - /multipleUnitInformation/uPFID
3GPP
Release 15 68 3GPP TS 32.291 V15.45.0 (2019-0912)
7.3 Bindings for SMS charging

Table 7.3-1: Bindings of CDR field, Information Element and Resource Attribute for SMS charging
3GPP
Release 15 69 3GPP TS 32.291 V15.45.0 (2019-0912)

ChargingDataRequest
SMS Charging Information SMS Charging Information /sMSChargingInformation
Originator Info Originator Info /sMSChargingInformation/originatorInfo
Originator SUPI Originator SUPI /sMSChargingInformation/originatorInfo/
originatorSUPI
Originator GPSI Originator GPSI /sMSChargingInformation/originatorInfo/
originatorGPSI
Originator Other Address Originator Other Address /sMSChargingInformation/originatorInfo/
originatorOtherAddress
Originator Received Originator Received Address /sMSChargingInformation/originatorInfo/
Address originatorReceivedAddress
Originator SCCP Address Originator SCCP Address /sMSChargingInformation/originatorInfo/
originatorSCCPAddress
SM Originator Interface SM Originator Interface /sMSChargingInformation/originatorInfo/
sMOriginatorInterface
SM Originator Protocol Id SM Originator Protocol Id /sMSChargingInformation/originatorInfo/
sMOriginatorProtocolId
Recipient Info Recipient Info /sMSChargingInformation/recipientInfo
Recipient SUPI Recipient SUPI /sMSChargingInformation/recipientInfo/
recipientSUPI
Recipient GPSI Recipient GPSI /sMSChargingInformation/recipientInfo/
recipientGPSI
Recipient Other Address Recipient Other Address /sMSChargingInformation/recipientInfo/
recipientOtherAddress
Recipient Received Recipient Received Address /sMSChargingInformation/recipientInfo/
Address recipientReceivedAddress
Recipient SCCP Address Recipient SCCP Address /sMSChargingInformation/recipientInfo/
recipientSCCPAddress
SM Destination Interface SM Destination Interface /sMSChargingInformation/recipientInfo/
sMDestinationInterface
SM Recipient Protocol Id SM Recipient Protocol Id /sMSChargingInformation/recipientInfo/
sMrecipientProtocolId
User Equipment Info User Equipment Info /sMSChargingInformation/userEquipmentInfo
User Location Info User Location Info /sMSChargingInformation/userLocationinfo
UE Time Zone UE Time Zone /sMSChargingInformation/uetimeZone
RAT Type RAT Type /sMSChargingInformation/rATType
SMSC Address SMSC Address /sMSChargingInformation/sMSCAddress
SM Data Coding Scheme SM Data Coding Scheme /sMSChargingInformation/
sMDataCodingScheme
SM Message Type SM Message Type /sMSChargingInformation/sMMessageType
SM Reply Path Requested SM Reply Path Requested /sMSChargingInformation/
sMReplyPathRequested
SM User Data Header SM User Data Header /sMSChargingInformation/sMUserDataHeader
SM Status SM Status /sMSChargingInformation/sMStatus
SM Discharge Time SM Discharge Time /sMSChargingInformation/sMDischargeTime
Number of Messages Sent Number of Messages Sent /sMSChargingInformation/
numberofMessagesSent
SM Service Type SM Service Type /sMSChargingInformation/sMServiceType
SM Sequence Number SM Sequence Number /sMSChargingInformation/sMSequenceNumber
SMS result SMS result /sMSChargingInformation/sMSresult
Submission Time Submission Time /sMSChargingInformation/submissionTime
SM Priority SM Priority /sMSChargingInformation/sMPriority
Message Reference Message Reference /sMSChargingInformation/messageReference
Message Size Message Size /sMSChargingInformation/messageSize
Message Class Message Class /sMSChargingInformation/messageClass
Delivery Report Requested Delivery Report Requested /sMSChargingInformation/
deliveryReportRequested
- - -
3GPP
Release 15 70 3GPP TS 32.291 V15.45.0 (2019-0912)
8 Security
Security aspects for service based interface shall be supported as specified in subclause 13 of 3GPP TS 33.501 [390].
Annex A (normative):
OpenAPI specification
A.1 General
The present Annex contains an OpenAPI [500] specification of HTTP messages and content bodies used by the
Nchf_ConvergedCharging API.
This Annex takes precedence when being discrepant to other parts of the specification with respect to the encoding of
information elements and methods within the API(s).
NOTE 1: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations
of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the
specification also apply.
Informative copies of the OpenAPI specification files contained in this 3GPP Technical Specification are available on
the public 3GPP file server in the following locations (see clause 5B of the 3GPP TR 21.900 [7] for further
information):
- https://www.3gpp.org/ftp/Specs/archive/OpenAPI/<Release>/, and
- https://www.3gpp.org/ftp/Specs/<Plenary>/<Release>/OpenAPI/.
A.2 Nchf_ ConvergedCharging API

openapi: 3.0.0
info:
title: Nchf_ConvergedCharging
version: 2.0.3
description: ConvergedCharging Service
© 2019, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.
externalDocs:
description: >
3GPP TS 32.291 V15.5.0: Telecommunication management; Charging management;
5G system, charging service; Stage 3.
url: 'http://www.3gpp.org/ftp/Specs/archive/32_series/32.291/'
servers:
- url: '{apiRoot}/nchf-convergedcharging/v2'
variables:
apiRoot:
default: https://example.com
description: apiRoot as defined in subclause 4.4 of 3GPP TS 29.501.
paths:
/chargingdata:
post:
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/ChargingDataRequest'
responses:
'201':
description: Created
content:
application/json:
schema:
3GPP
Release 15 71 3GPP TS 32.291 V15.45.0 (2019-0912)
$ref: '#/components/schemas/ChargingDataResponse'
'400':
description: Bad request
content:
application/json:
schema:
$ref: 'TS29571_CommonData.yaml#/components/schemas/ProblemDetails'
'403':
description: Forbidden
content:
application/json:
schema:
'404':
description: Not Found
content:
application/json:
schema:
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'410':
'411':
'413':
'500':
'503':
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
callbacks:
myNotification:
'{$request.body#/notifyUri}':
post:
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/ChargingNotifyRequest'
responses:
'204':
description: 'No Content, Notification was succesfull'
'400':
content:
application/json:
schema:
$ref: >-
TS29571_CommonData.yaml#/components/schemas/ProblemDetails
default:
'/chargingdata/{ChargingDataRef}/update':
post:
requestBody:
required: true
content:
application/json:
schema:
parameters:
- name: ChargingDataRef
in: path
description: a unique identifier for a charging data resource in a PLMN
required: true
schema:
type: string
responses:
'200':
description: OK. Updated Charging Data resource is returned
content:
application/json:
schema:
$ref: '#/components/schemas/ChargingDataResponse'
'400':
3GPP
Release 15 72 3GPP TS 32.291 V15.45.0 (2019-0912)

content:
application/json:
schema:
'403':
description: Forbidden
content:
application/json:
schema:
'404':
content:
application/json:
schema:
'401':
'410':
'411':
'413':
'500':
'503':
default:
'/chargingdata/{ChargingDataRef}/release':
post:
requestBody:
required: true
content:
application/json:
schema:
parameters:
- name: ChargingDataRef
in: path
description: a unique identifier for a charging data resource in a PLMN
required: true
schema:
type: string
responses:
'204':
description: No Content.
'404':
content:
application/json:
schema:
'401':
'410':
'411':
'413':
'500':
'503':
default:
components:
schemas:
ChargingDataRequest:
type: object
properties:
subscriberIdentifier:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Supi'
nfConsumerIdentification:
$ref: '#/components/schemas/NFIdentification'
3GPP
Release 15 73 3GPP TS 32.291 V15.45.0 (2019-0912)
invocationTimeStamp:
$ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime'
invocationSequenceNumber:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Uint32'
oneTimeEvent:
type: boolean
oneTimeEventType:
$ref: '#/components/schemas/oneTimeEventType'
notifyUri:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
serviceSpecificationInfo:
type: string
multipleUnitUsage:
type: array
items:
$ref: '#/components/schemas/MultipleUnitUsage'
minItems: 0
triggers:
type: array
items:
$ref: '#/components/schemas/Trigger'
minItems: 0
pDUSessionChargingInformation:
$ref: '#/components/schemas/PDUSessionChargingInformation'
roamingQBCInformation:
$ref: '#/components/schemas/RoamingQBCInformation'
sMSChargingInformation:
$ref: '#/components/schemas/SMSChargingInformation'
required:
- nfConsumerIdentification
- invocationTimeStamp
- invocationSequenceNumber
ChargingDataResponse:
type: object
properties:
invocationTimeStamp:
invocationSequenceNumber:
invocationResult:
$ref: '#/components/schemas/InvocationResult'
sessionFailover:
$ref: '#/components/schemas/SessionFailover'
multipleUnitInformation:
type: array
items:
$ref: '#/components/schemas/MultipleUnitInformation'
minItems: 0
triggers:
type: array
items:
minItems: 0
pDUSessionChargingInformation:
$ref: '#/components/schemas/PDUSessionChargingInformation'
roamingQBCInformation:
$ref: '#/components/schemas/RoamingQBCInformation'
required:
- nfConsumerIdentification
- invocationSequenceNumber
ChargingNotifyRequest:
type: object
properties:
notificationType:
$ref: '#/components/schemas/NotificationType'
reauthorizationDetails:
type: array
items:
$ref: '#/components/schemas/ReauthorizationDetails'
minItems: 0
required:
- notificationType
ChargingNotifyResponse:
type: object
properties:
invocationResult:
$ref: '#/components/schemas/InvocationResult'
NFIdentification:
3GPP
Release 15 74 3GPP TS 32.291 V15.45.0 (2019-0912)
type: object
properties:
nFName:
$ref: 'TS29571_CommonData.yaml#/components/schemas/NfInstanceId'
nFIPv4Address:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4Addr'
nFIPv6Address:
nFPLMNID:
$ref: 'TS29571_CommonData.yaml#/components/schemas/PlmnId'
nodeFunctionality:
$ref: '#/components/schemas/NodeFunctionality'
nFFqdn:
type: string
required:
- nodeFunctionality
MultipleUnitUsage:
type: object
properties:
ratingGroup:
$ref: 'TS29571_CommonData.yaml#/components/schemas/RatingGroup'
requestedUnit:
$ref: '#/components/schemas/RequestedUnit'
usedUnitContainer:
type: array
items:
$ref: '#/components/schemas/UsedUnitContainer'
minItems: 0
uPFID:
required:
- ratingGroup
InvocationResult:
type: object
properties:
error:
failureHandling:
$ref: '#/components/schemas/FailureHandling'
Trigger:
type: object
properties:
triggerType:
$ref: '#/components/schemas/TriggerType'
triggerCategory:
$ref: '#/components/schemas/TriggerCategory'
timeLimit:
$ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec'
volumeLimit:
volumeLimit64:
maxNumberOfccc:
required:
- triggerType
- triggerCategory
MultipleUnitInformation:
type: object
properties:
resultCode:
$ref: '#/components/schemas/ResultCode'
ratingGroup:
grantedUnit:
$ref: '#/components/schemas/GrantedUnit'
triggers:
type: array
items:
minItems: 0
validityTime:
quotaHoldingTime:
finalUnitIndication:
$ref: '#/components/schemas/FinalUnitIndication'
timeQuotaThreshold:
3GPP
Release 15 75 3GPP TS 32.291 V15.45.0 (2019-0912)
type: integer
volumeQuotaThreshold:
unitQuotaThreshold:
type: integer
uPFID:
required:
- ratingGroup
RequestedUnit:
type: object
properties:
time:
totalVolume:
uplinkVolume:
downlinkVolume:
serviceSpecificUnits:
UsedUnitContainer:
type: object
properties:
serviceId:
$ref: 'TS29571_CommonData.yaml#/components/schemas/ServiceId'
quotaManagementIndicator:
$ref: '#/components/schemas/QuotaManagementIndicator'
triggers:
type: array
items:
minItems: 0
triggerTimestamp:
time:
totalVolume:
uplinkVolume:
downlinkVolume:
eventTimeStamps:
localSequenceNumber:
type: integer
pDUContainerInformation:
$ref: '#/components/schemas/PDUContainerInformation'
required:
- localSequenceNumber
GrantedUnit:
type: object
properties:
tariffTimeChange:
time:
totalVolume:
uplinkVolume:
downlinkVolume:
FinalUnitIndication:
type: object
properties:
finalUnitAction:
$ref: '#/components/schemas/FinalUnitAction'
restrictionFilterRule:
$ref: '#/components/schemas/IPFilterRule'
filterId:
type: string
3GPP
Release 15 76 3GPP TS 32.291 V15.45.0 (2019-0912)
redirectServer:
$ref: '#/components/schemas/RedirectServer'
required:
- finalUnitAction
RedirectServer:
type: object
properties:
redirectAddressType:
$ref: '#/components/schemas/RedirectAddressType'
redirectServerAddress:
type: string
required:
- redirectAddressType
- redirectServerAddress
ReauthorizationDetails:
type: object
properties:
serviceId:
$ref: 'TS29571_CommonData.yaml#/components/schemas/ServiceId'
ratingGroup:
quotaManagementIndicator:
$ref: '#/components/schemas/QuotaManagementIndicator'
PDUSessionChargingInformation:
type: object
properties:
chargingId:
$ref: 'TS29571_CommonData.yaml#/components/schemas/ChargingId'
userInformation:
$ref: '#/components/schemas/UserInformation'
userLocationinfo:
$ref: 'TS29571_CommonData.yaml#/components/schemas/UserLocation'
userLocationTime:
presenceReportingAreaInformation:
type: object
additionalProperties:
$ref: 'TS29571_CommonData.yaml#/components/schemas/PresenceInfo'
minProperties: 0
uetimeZone:
$ref: 'TS29571_CommonData.yaml#/components/schemas/TimeZone'
pduSessionInformation:
$ref: '#/components/schemas/PDUSessionInformation'
unitCountInactivityTimer:
rANSecondaryRATUsageReport:
$ref: '#/components/schemas/RANSecondaryRATUsageReport'
required:
- pduSessionInformation
UserInformation:
type: object
properties:
servedGPSI:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi'
servedPEI:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Pei'
unauthenticatedFlag:
type: boolean
roamerInOut:
$ref: '#/components/schemas/RoamerInOut'
PDUSessionInformation:
type: object
properties:
networkSlicingInfo:
$ref: '#/components/schemas/NetworkSlicingInfo'
pduSessionID:
$ref: 'TS29571_CommonData.yaml#/components/schemas/PduSessionId'
pduType:
$ref: 'TS29571_CommonData.yaml#/components/schemas/PduSessionType'
sscMode:
$ref: 'TS29571_CommonData.yaml#/components/schemas/SscMode'
hPlmnId:
servingNetworkFunctionID:
$ref: '#/components/schemas/ServingNetworkFunctionID'
ratType:
$ref: 'TS29571_CommonData.yaml#/components/schemas/RatType'
dnnId:
3GPP
Release 15 77 3GPP TS 32.291 V15.45.0 (2019-0912)
$ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn'
dnnSelectionMode:
$ref: '#/components/schemas/dnnSelectionMode'
chargingCharacteristics:
type: string
chargingCharacteristicsSelectionMode:
$ref: '#/components/schemas/ChargingCharacteristicsSelectionMode'
startTime:
stopTime:
3gppPSDataOffStatus:
$ref: '#/components/schemas/3GPPPSDataOffStatus'
sessionStopIndicator:
type: boolean
pduAddress:
$ref: '#/components/schemas/PDUAddress'
diagnostics:
$ref: '#/components/schemas/Diagnostics'
authorizedQoSInformation:
$ref: 'TS29512_Npcf_SMPolicyControl.yaml#/components/schemas/AuthorizedDefaultQos'
subscribedQoSInformation:
$ref: 'TS29571_CommonData.yaml#/components/schemas/SubscribedDefaultQos'
authorizedSessionAMBR:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Ambr'
subscribedSessionAMBR:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Ambr'
servingCNPlmnId:
required:
- pduSessionID
- dnnId
PDUContainerInformation:
type: object
properties:
timeofFirstUsage:
timeofLastUsage:
qoSInformation:
$ref: 'TS29512_Npcf_SMPolicyControl.yaml#/components/schemas/QosData'
aFCorrelationInformation:
type: string
userLocationInformation:
uetimeZone:
rATType:
servingNodeID:
type: array
items:
minItems: 0
type: object
minProperties: 0
sponsorIdentity:
type: string
applicationserviceProviderIdentity:
type: string
chargingRuleBaseName:
type: string
NetworkSlicingInfo:
type: object
properties:
sNSSAI:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Snssai'
required:
- sNSSAI
PDUAddress:
type: object
properties:
pduIPv4Address:
3GPP
Release 15 78 3GPP TS 32.291 V15.45.0 (2019-0912)
pduIPv6AddresswithPrefix:
pduAddressprefixlength:
type: integer
iPv4dynamicAddressFlag:
type: boolean
iPv6dynamicPrefixFlag:
type: boolean
ServingNetworkFunctionID:
type: object
properties:
servingNetworkFunctionInformation:
$ref: '#/components/schemas/NFIdentification'
aMFId:
$ref: 'TS29571_CommonData.yaml#/components/schemas/AmfId'
required:
- servingNetworkFunctionInformation
RoamingQBCInformation:
type: object
properties:
multipleQFIcontainer:
type: array
items:
$ref: '#/components/schemas/MultipleQFIcontainer'
minItems: 0
uPFID:
roamingChargingProfile:
$ref: '#/components/schemas/RoamingChargingProfile'
MultipleQFIcontainer:
type: object
properties:
triggers:
type: array
items:
minItems: 0
triggerTimestamp:
time:
totalVolume:
uplinkVolume:
localSequenceNumber:
type: integer
qFIContainerInformation:
$ref: '#/components/schemas/QFIContainerInformation'
required:
- localSequenceNumber
QFIContainerInformation:
type: object
properties:
qFI:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Qfi'
reportTime:
timeofFirstUsage:
timeofLastUsage:
qoSInformation:
$ref: 'TS29512_Npcf_SMPolicyControl.yaml#/components/schemas/QosData'
userLocationInformation:
uetimeZone:
type: object
minProperties: 0
rATType:
servingNetworkFunctionID:
3GPP
Release 15 79 3GPP TS 32.291 V15.45.0 (2019-0912)
type: array
items:
minItems: 0
RoamingChargingProfile:
type: object
properties:
triggers:
type: array
items:
minItems: 0
partialRecordMethod:
$ref: '#/components/schemas/PartialRecordMethod'
SMSChargingInformation:
type: object
properties:
originatorInfo:
$ref: '#/components/schemas/OriginatorInfo'
recipientInfo:
type: array
items:
$ref: '#/components/schemas/RecipientInfo'
minItems: 0
userEquipmentInfo:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Pei'
userLocationinfo:
uetimeZone:
rATType:
sMSCAddress:
type: string
sMDataCodingScheme:
type: integer
sMMessageType:
$ref: '#/components/schemas/SMMessageType'
sMReplyPathRequested:
$ref: '#/components/schemas/ReplyPathRequested'
sMUserDataHeader:
type: string
sMStatus:
type: string
sMDischargeTime:
numberofMessagesSent:
sMServiceType:
$ref: '#/components/schemas/SMServiceType'
sMSequenceNumber:
sMSresult:
submissionTime:
sMPriority:
$ref: '#/components/schemas/SMPriority'
messageReference:
type: string
messageSize:
messageClass:
$ref: '#/components/schemas/MessageClass'
deliveryReportRequested:
$ref: '#/components/schemas/DeliveryReportRequested'
OriginatorInfo:
type: object
properties:
originatorSUPI:
originatorGPSI:
originatorOtherAddress:
$ref: '#/components/schemas/SMAddressInfo'
originatorReceivedAddress:
3GPP
Release 15 80 3GPP TS 32.291 V15.45.0 (2019-0912)
originatorSCCPAddress:
type: string
sMOriginatorInterface:
$ref: '#/components/schemas/SMInterface'
sMOriginatorProtocolId:
type: string
RecipientInfo:
type: object
properties:
recipientSUPI:
recipientGPSI:
recipientOtherAddress:
recipientReceivedAddress:
recipientSCCPAddress:
type: string
sMDestinationInterface:
$ref: '#/components/schemas/SMInterface'
sMrecipientProtocolId:
type: string
SMAddressInfo:
type: object
properties:
sMaddressType:
$ref: '#/components/schemas/SMAddressType'
sMaddressData:
type: string
sMaddressDomain:
$ref: '#/components/schemas/SMAddressDomain'
RecipientAddress:
type: object
properties:
recipientAddressInfo:
sMaddresseeType:
$ref: '#/components/schemas/SMAddresseeType'
MessageClass:
type: object
properties:
classIdentifier:
$ref: '#/components/schemas/ClassIdentifier'
tokenText:
type: string
SMAddressDomain:
type: object
properties:
domainName:
type: string
3GPPIMSIMCCMNC:
type: string
SMInterface:
type: object
properties:
interfaceId:
type: string
interfaceText:
type: string
interfacePort:
type: string
interfaceType:
$ref: '#/components/schemas/InterfaceType'
RANSecondaryRATUsageReport:
type: object
properties:
rANSecondaryRATType:
qosFlowsUsageReports:
type: array
items:
$ref: '#/components/schemas/QosFlowsUsageReport'
Diagnostics:
type: integer
IPFilterRule:
type: string
3GPP
Release 15 81 3GPP TS 32.291 V15.45.0 (2019-0912)
QosFlowsUsageReport:
type: object
properties:
qFI:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Qfi'
startTimestamp:
endTimestamp:
uplinkVolume:
downlinkVolume:
NotificationType:
anyOf:
- type: string
enum:
- REAUTHORIZATION
- ABORT_CHARGING
- type: string
NodeFunctionality:
anyOf:
- type: string
enum:
- SMF
- SMSF
- type: string
ChargingCharacteristicsSelectionMode:
anyOf:
- type: string
enum:
- HOME_DEFAULT
- ROAMING_DEFAULT
- VISITING_DEFAULT
- type: string
TriggerType:
anyOf:
- type: string
enum:
- QUOTA_THRESHOLD
- QHT
- FINAL
- QUOTA_EXHAUSTED
- VALIDITY_TIME
- OTHER_QUOTA_TYPE
- FORCED_REAUTHORISATION
- UNUSED_QUOTA_TIMER # Included for backwards compatibility, shall not be used
- UNIT_COUNT_INACTIVITY_TIMER
- ABNORMAL_RELEASE
- QOS_CHANGE
- VOLUME_LIMIT
- TIME_LIMIT
- PLMN_CHANGE
- USER_LOCATION_CHANGE
- RAT_CHANGE
- SESSION_AMBR_CHANGE
- UE_TIMEZONE_CHANGE
- TARIFF_TIME_CHANGE
- MAX_NUMBER_OF_CHANGES_IN_CHARGING_CONDITIONS
- MANAGEMENT_INTERVENTION
- CHANGE_OF_UE_PRESENCE_IN_PRESENCE_REPORTING_AREA
- CHANGE_OF_3GPP_PS_DATA_OFF_STATUS
- SERVING_NODE_CHANGE
- REMOVAL_OF_UPF
- ADDITION_OF_UPF
- START_OF_SERVICE_DATA_FLOW
- GFBR_GUARANTEED_STATUS_CHANGE
- type: string
FinalUnitAction:
anyOf:
- type: string
enum:
- TERMINATE
- REDIRECT
- RESTRICT_ACCESS
- type: string
RedirectAddressType:
anyOf:
3GPP
Release 15 82 3GPP TS 32.291 V15.45.0 (2019-0912)
- type: string
enum:
- IPV4
- IPV6
- URL
- type: string
TriggerCategory:
anyOf:
- type: string
enum:
- IMMEDIATE_REPORT
- DEFERRED_REPORT
- type: string
QuotaManagementIndicator:
anyOf:
- type: string
enum:
- ONLINE_CHARGING
- OFFLINE_CHARGING
- type: string
FailureHandling:
anyOf:
- type: string
enum:
- TERMINATE
- CONTINUE
- RETRY_AND_TERMINATE
- type: string
SessionFailover:
anyOf:
- type: string
enum:
- FAILOVER_NOT_SUPPORTED
- FAILOVER_SUPPORTED
- type: string
3GPPPSDataOffStatus:
anyOf:
- type: string
enum:
- ACTIVE
- INACTIVE
- type: string
ResultCode:
anyOf:
- type: string
enum:
- SUCCESS
- END_USER_SERVICE_DENIED
- QUOTA_MANAGEMENT_NOT_APPLICABLE
- QUOTA_LIMIT_REACHED
- END_USER_SERVICE_REJECTED
- USER_UNKNOWN
- RATING_FAILED
- type: string
PartialRecordMethod:
anyOf:
- type: string
enum:
- DEFAULT
- INDIVIDUAL
- type: string
RoamerInOut:
anyOf:
- type: string
enum:
- IN_BOUND
- OUT_BOUND
- type: string
SMMessageType:
anyOf:
- type: string
enum:
- SUBMISSION
- DELIVERY_REPORT
- SM_SERVICE_REQUEST
- type: string
SMPriority:
anyOf:
3GPP
Release 15 83 3GPP TS 32.291 V15.45.0 (2019-0912)
- type: string
enum:
- LOW
- NORMAL
- HIGH
- type: string
DeliveryReportRequested:
anyOf:
- type: string
enum:
- YES
- NO
- type: string
InterfaceType:
anyOf:
- type: string
enum:
- UNKNOWN
- MOBILE_ORIGINATING
- MOBILE_TERMINATING
- APPLICATION_ORIGINATING
- APPLICATION_TERMINATING
- type: string
ClassIdentifier:
anyOf:
- type: string
enum:
- PERSONAL
- ADVERTISEMENT
- INFORMATIONAL
- AUTO
- type: string
SMAddressType:
anyOf:
- type: string
enum:
- EMAIL_ADDRESS
- MSISDN
- IPV4_ADDRESS
- IPV6_ADDRESS
- NUMERIC_SHORTCODE
- ALPHANUMERIC_SHORTCODE
- OTHER
- IMSI
- type: string
SMAddresseeType:
anyOf:
- type: string
enum:
- TO
- CC
- BCC
- type: string
SMServiceType:
anyOf:
- type: string
enum:
- VAS4SMS_SHORT_MESSAGE_CONTENT_PROCESSING
- VAS4SMS_SHORT_MESSAGE_FORWARDING
- VAS4SMS_SHORT_MESSAGE_FORWARDING_MULTIPLE_SUBSCRIPTIONS
- VAS4SMS_SHORT_MESSAGE_FILTERING
- VAS4SMS_SHORT_MESSAGE_RECEIPT
- VAS4SMS_SHORT_MESSAGE_NETWORK_STORAGE
- VAS4SMS_SHORT_MESSAGE_TO_MULTIPLE_DESTINATIONS
- VAS4SMS_SHORT_MESSAGE_VIRTUAL_PRIVATE_NETWORK(VPN)
- VAS4SMS_SHORT_MESSAGE_AUTO_REPLY
- VAS4SMS_SHORT_MESSAGE_PERSONAL_SIGNATURE
- VAS4SMS_SHORT_MESSAGE_DEFERRED_DELIVERY
- type: string
ReplyPathRequested:
anyOf:
- type: string
enum:
- NO_REPLY_PATH_SET
- REPLY_PATH_SET
- type: string
oneTimeEventType:
anyOf:
3GPP
Release 15 84 3GPP TS 32.291 V15.45.0 (2019-0912)
- type: string
enum:
- IEC
- PEC
- type: string
dnnSelectionMode:
anyOf:
- type: string
enum:
- VERIFIED
- UE_DNN_NOT_VERIFIED
- NW_DNN_NOT_VERIFIED
- type: string
3GPP
Release 15 85 3GPP TS 32.291 V15.45.0 (2019-0912)
Annex B (informative):Change history
3GPP
Release 15 86 3GPP TS 32.291 V15.45.0 (2019-0912)
Change history
Date Meeting TDoc CR Rev Cat Subject/Comment New
version
2018-09 SA#81 Upgrade to change control version 15.0.0
2018-12 SA#82 SP-181157 0001 1 F Correction on the Reference and Resource name 15.1.0
2018-12 SA#82 SP-181157 0002 1 F Editorial Correction 15.1.0
2018-12 SA#82 SP-181157 0003 1 F Data Type Applicability Correction 15.1.0
2018-12 SA#82 SP-181059 0004 1 F Serving Node ID Correction 15.1.0
2018-12 SA#82 SP-181059 0006 1 F Correction of Common Data reference in 15.1.0

Nchf_ConvergedCharging API
2018-12 SA#82 SP-181059 0007 1 F Correction of references to TS 29.512, TS 29.514 and data types 15.1.0
2018-12 SA#82 SP-181059 0008 1 F Clarification of requested units handling 15.1.0
2018-12 SA#82 SP-181059 0009 1 F Remove of underscore in the API name 15.1.0
2018-12 SA#82 SP-181059 0010 1 F Correction of data type for subscriber identifier 15.1.0
2018-12 SA#82 SP-181059 0011 - F Correction of response code in flow for Notify 15.1.0
2018-12 SA#82 SP-181059 0012 1 F Allow updating of Notify URI 15.1.0
2018-12 SA#82 SP-181059 0013 1 F Correction of overlapping results between Invocation result and 15.1.0
Result code
2018-12 SA#82 SP-181059 0014 1 F Correction of Invocation result at http ok 15.1.0
2018-12 SA#82 SP-181059 0015 1 F Correction of Rating Group Id and Service Id to Uint32 15.1.0
2018-12 SA#82 SP-181059 0016 1 F Correction of name for Multiple Unit Information 15.1.0
2018-12 SA#82 SP-181059 0018 1 F Correction of name for Multiple Unit Information 15.1.0
2018-12 SA#82 SP-181059 0019 1 F Correction of missing http status code 15.1.0
2018-12 SA#82 SP-181052 0020 1 B Addition of event based charging 15.1.0
2018-12 SA#82 SP-181057 0021 1 B Introduction Data Volume Reporting for Option 4&7 15.1.0
2018-12 SA#82 SP-181059 0022 1 F Alignment for session identifier 15.1.0
2018-12 SA#82 SP-181059 0023 1 F Correction on Charging Notification message 15.1.0
2018-12 SA#82 SP-181059 0024 1 F Correction on Charging ID data type 15.1.0
2018-12 SA#82 SP-181059 0025 1 F Correction on Reauthorizationdetails 15.1.0
2018-12 SA#82 SP-181052 0026 2 B Data Type for SMS 15.1.0
2018-12 SA#82 SP-181052 0027 1 B Introduce Binding for SMS charging 15.1.0
2018-12 SA#82 SP-181052 0028 1 B Introduce OpenAPI extension for SMS charging 15.1.0
2018-12 SA#82 SP-181059 0029 - F Failure Handling Mechanism Clarification 15.1.0
2018-12 SA#82 SP-181059 0030 - F Correction of Serving Network Function ID definition 15.1.0
2019-03 SA#83 SP-190116 0031 1 F Correction of create operation description for event 15.2.0
2019-03 SA#83 SP-190115 0032 1 F Correction of data type associated to volume 15.2.0
2019-03 SA#83 SP-190214 0033 3 F Correction on reference for common data types 15.2.0
2019-03 SA#83 SP-190116 0034 1 F Correction of inconsistencies in data types 15.2.0
2019-03 SA#83 SP-190116 0035 1 F Correction of NF Consumer Information 15.2.0
2019-03 SA#83 SP-190117 0036 - F Correction of SMSF as NF Consumer 15.2.0
3GPP
Release 15 87 3GPP TS 32.291 V15.45.0 (2019-0912)
2019-03 SA#83 SP-190116 0037 - F Correction of validityTime data type 15.2.0
2019-03 SA#83 SP-190116 0038 1 F Correction of API versioning and externalDocs field 15.2.0
2019-03 SA#83 SP-190212 0039 4 F Correction of Qos Information 15.2.0
2019-03 SA#83 SP-190116 0040 1 F Correct missing Session Identifier 15.2.0
2019-03 SA#83 SP-190116 0041 1 F Correct faults in yaml part 15.2.0
2019-03 SA#83 SP-190115 0042 1 F Correction of User Information 15.2.0
2019-03 SA#83 SP-190115 0043 - F Correction of dnn data type 15.2.0
2019-03 SA#83 SP-190213 0044 3 F Correction of serving Network Function 15.2.0
2019-03 SA#83 SP-190116 0045 1 F Correction of Multiple Unit Information in ChargingDataResponse 15.2.0
2019-03 SA#83 SP-190116 0046 1 F Correction of trigger in ChargingDataResponse 15.2.0
2019-03 SA#83 SP-190116 0048 1 F Correction of RANSecondaryRATUsageReport occurrence 15.2.0
2019-03 SA#83 SP-190116 0052 - F Correcting of table for bindings 15.2.0
2019-03 SA#83 SP-190115 0054 1 F Correction of UE IP Addresses 15.2.0
2019-03 SA#83 SP-190116 0055 - F Correction on local sequence nb 15.2.0
2019-03 SA#83 Editorial corrections in the OPENAPI (MCC) 15.2.1
2019-06 SA#84 SP-190384 0057 - F Add the reference for SMS charging 15.3.0
2019-06 SA#84 SP-190384 0058 1 F Correct the failure handling 15.3.0
2019-06 SA#84 SP-190384 0063 1 F Correction on errors description 15.3.0
2019-06 SA#84 SP-190384 0064 - F Correction on Gateway timeout code 15.3.0
2019-06 SA#84 SP-190384 0065 - F Correction of used unit container attributes 15.3.0
2019-06 SA#84 SP-190383 0066 1 F Correction on binding 15.3.0
2019-06 SA#84 SP-190383 0067 - F Correction of trigger type for start of service data flow 15.3.0
2019-06 SA#84 SP-190383 0068 1 F Correction of trigger type unit count inactivity timer 15.3.0
2019-06 SA#84 SP-190383 0069 1 F Correction of Nchf_ConvergedCharging release usage 15.3.0
2019-06 SA#84 SP-190383 0070 1 F Correction of missing http status codes 15.3.0
2019-06 SA#84 SP-190522 0072 - F Correction on the OpenAPI version 15.3.0
2019-09 SA#85 SP-190761 0081 1 F Correction of nfConsumerIdentification and usedUnitContainer 15.4.0
2019-09 SA#85 SP-190762 0083 - F Correction of TriggerCategory and Triggers 15.4.0
2019-09 SA#85 SP-190762 0085 1 F Correction of Report Time in QFI Container Information 15.4.0
2019-09 SA#85 SP-190762 0087 1 F Correction of SubscriptionIdentificationType 15.4.0
2019-09 SA#85 SP-190762 0091 1 F Correction of multipleQuotaInformation 15.4.0
2019-09 SA#85 SP-190762 0093 1 F Correction of HTTP Status Codes 15.4.0
2019-09 SA#85 SP-190762 0097 1 F Correction of version numbering 15.4.0
2019-09 SA#85 SP-190762 0098 - F Correct the QoS change trigger 15.4.0
2019-09 SA#85 SP-190762 0099 1 F Add the selection mode in PDU session information 15.4.0
2019-09 SA#85 SP-190762 0102 1 F Event based charging mechanism 15.4.0
2019-09 SA#85 SP-190840 0103 1 F Bindings of common field correction 15.4.0
3GPP
Release 15 88 3GPP TS 32.291 V15.45.0 (2019-0912)
2019-09 SA#85 SP-190840 0104 1 F Coordination of attribute Presence condition 15.4.0
2019-09 SA#85 SP-190840 0105 1 F Bindings for 5G data connectivity correction 15.4.0
2019-09 SA#85 SP-190840 0106 1 F Correction of data structure of response body 15.4.0
2019-09 SA#85 SP-190840 0107 - F Correction of serving Network Function identifier 15.4.0
2019-09 SA#85 SP-190840 0123 - F Corrections on OpenAPI 15.4.0
2019-09 SA#85 SP-190752 0125 - F Correction on OpenAPI version 15.4.0
2019-12 SA#86 SP-191160 0128 1 F Add the Service Specification Information 15.5.0
2019-12 SA#86 SP-191160 0130 1 F Add the QNC support 15.5.0
2019-12 SA#86 SP-191160 0131 3 F Clarify the QoS change trigger 15.5.0
2019-12 SA#86 SP-191160 0134 1 F Correction of Nchf_ConvergedCharging_Release operation 15.5.0
2019-12 SA#86 SP-191161 0142 - F Correction of subscriberIdentifier 15.5.0
2019-12 SA#86 SP-191161 0155 1 F Correction InvocationResult description and binding 15.5.0
2019-12 SA#86 SP-191161 0161 1 F Correction of nfIdentification in yaml 15.5.0
2019-12 SA#86 SP-191161 0162 1 F Alignment with TS 29.501 template 15.5.0
2019-12 SA#86 SP-191161 0165 1 F Correction of Notify Response 15.5.0
2019-12 SA#86 SP-191204 0167 2 F Correction of ChargingNotifyResponse description 15.5.0
2019-12 SA#86 SP-191161 0169 1 F Correction on the Resource URI 15.5.0
2019-12 SA#86 SP-191202 0182 2 F Add Session-AMBR change trigger 15.5.0
2019-12 SA#86 SP-191161 0188 - F Correction to NF consumer identification 15.5.0
2019-12 SA#86 SP-191161 0190 1 F Correction of binding for 5G data connectivity 15.5.0
2019-12 SA#86 SP-191206 0197 - F Update OpenAPI version 15.5.0
3GPP

3GPP TS 32.291

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

3GPP TS 32.291

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3GPP TS 32.291

Uploaded by

Copyright:

Available Formats

3rd Generation Partnership Project;

Technical Specification Group Services and System Aspects;

3GPP support office address

No part may be reproduced except as authorized by written permission.

6.1.6.3.5 Enumeration: ChargingCharacteristicsSelectionMode............................................................46

Annex B (informative):Change history...................................................................................................79

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.

- The common 3GPP charging architecture is specified in TS 32.240 [1].

- The 5G data connectivity is specified in TS 32.255[30].

- For a specific reference, subsequent revisions do not apply.

[1] 3GPP TS 32.240: "Telecommunication management; Charging management; Charging

[2] - [28] Void.

[29] 3GPP TS 32.274: "Telecommunication management; Charging management;Short Message

[30] 3GPP TS 32.255: "Telecommunication management; Charging management; 5G Data

[31] - [49] Void.

[50] - [57] Void.

[58] 3GPP TS 32.290: "Telecommunication management; Charging management; 5G system; Services,

[59] - [99] Void.

[100] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".

[101] - [199] Void

[200] - [203] Void

[204] - [298] Void

[303] - [370] Void

[372] - [389] Void

[390] 3GPP TS 33.501: "Security architecture and procedures for 5G System".

[391] - [399] Void

[401] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2) ".

[403] - [499] Void.

[500] OpenAPI: "OpenAPI 3.0.0 Specification",

[501] - [599] Void.

3 Definitions, symbols and abbreviations

Nchf Service based interface exhibited by CHF.

4.1 Service architecture

4.2 Network functions

- Receiving service usage reports from NF Service Consumer; and

4.2.2 NF Service Consumers

- Requesting and receiving the quota(s);

- Sending service usage reports; and

- Handling quota re-authorisation or abort notifications.

5 Services offered by the CHF

Table 5.1-1: NF Services provided by CHF

Service Name Description Consumer

The "Nchf_SpendingLimitControl" service is defined in 29.594 [301].

5.2 Nchf_ConvergedCharging service

It includes the following functionalities:

- Charging information record generation

5.2.2 Service operations

Table 5.2.2.1-2: Nchf_ ConvergedCharging Operations

Service Operation Name Description Initiated by Corresponding

5.2.2.2 Nchf_ConvergedCharging_Create Operation

- No existing charging data resource.

Figure 5.2.2.2-1: Nchf_ ConvergedCharging_Create Service Operation

5.2.2.3 Nchf_ConvergedCharging_Update Operation

- expiry of granted service units' validity time