ETSI TS 129 594 V18.4.0 (2024-07)

5G; 5G System; Spending Limit Control Service; Stage 3 (3GPP TS 29.594 version 18.4.0 Release 18)

RTS/TSGC-0329594vi40

General Information

• Status: Not Published
• Technical Committee: 3GPP CT 3 - Interworking with external networks (formely CN3)
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Completion Date: 26-Jul-2024

Standards Content (Sample)

TECHNICAL SPECIFICATION
5G;
5G System;
Spending Limit Control Service;
Stage 3
(3GPP TS 29.594 version 18.4.0 Release 18)


3GPP TS 29.594 version 18.4.0 Release 18 1 ETSI TS 129 594 V18.4.0 (2024-07)

Reference
RTS/TSGC-0329594vi40
Keywords
5G
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2024.
All rights reserved.
ETSI
3GPP TS 29.594 version 18.4.0 Release 18 2 ETSI TS 129 594 V18.4.0 (2024-07)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (https://ipr.etsi.org/).
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its

Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the ®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under https://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 29.594 version 18.4.0 Release 18 3 ETSI TS 129 594 V18.4.0 (2024-07)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
2 References . 7
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Nchf_SpendingLimitControl Service . 8
4.1 Service Description . 8
4.1.1 Overview . 8
4.1.2 Service Architecture . 9
4.1.3 Network Functions . 9
4.1.3.1 Charging Function (CHF) . 9
4.1.3.2 NF Service Consumers . 9
4.2 Service Operations . 10
4.2.1 Introduction. 10
4.2.2 Nchf_SpendingLimitControl_Subscribe service operation . 10
4.2.2.1 General . 10
4.2.2.2 Initial spending limit retrieval . 10
4.2.2.3 Intermediate spending limit report retrieval . 12
4.2.3 Nchf_SpendingLimitControl_Unsubscribe service operation . 14
4.2.3.1 General . 14
4.2.3.2 Unsubscribe from spending limit reporting . 14
4.2.4 Nchf_SpendingLimitControl_Notify service operation . 15
4.2.4.1 General . 15
4.2.4.2 Spending limit report. 15
4.2.4.3 Subscription termination request by CHF . 17
5 Nchf_SpendingLimitControl Service API . 18
5.1 Introduction . 18
5.2 Usage of HTTP . 18
5.2.1 General . 18
5.2.2 HTTP standard headers . 18
5.2.2.1 General . 18
5.2.2.2 Content type . 18
5.2.3 HTTP custom headers . 19
5.2.3.1 General . 19
5.3 Resources . 19
5.3.1 Resource Structure . 19
5.3.2 Resource: Spending Limit Retrieval Subscriptions (Collection) . 19
5.3.2.1 Description . 19
5.3.2.2 Resource definition . 19
5.3.2.3 Resource Standard Methods . 20
5.3.2.3.1 POST . 20
5.3.2.4 Resource Custom Operations . 20
5.3.3 Resource: Individual Spending Limit Retrieval Subscription (Document) . 20
5.3.3.1 Description . 20
5.3.3.2 Resource definition . 21
5.3.3.3 Resource Standard Methods . 21
5.3.3.3.1 PUT . 21
5.3.3.3.2 DELETE . 22
5.4 Custom Operations without associated resources. 23
ETSI
3GPP TS 29.594 version 18.4.0 Release 18 4 ETSI TS 129 594 V18.4.0 (2024-07)
5.5 Notifications . 23
5.5.1 General . 23
5.5.2 Spending limit notification . 24
5.5.2.1 Description . 24
5.5.2.2 Target URI . 24
5.5.2.3 Standard Methods . 24
5.5.2.3.1 POST . 24
5.5.3 Subscription Termination . 25
5.5.3.1 Description . 25
5.5.3.2 Target URI . 25
5.5.3.3 Standard Methods . 26
5.5.3.3.1 POST . 26
5.6 Data Model . 27
5.6.1 General . 27
5.6.2 Structured data types . 28
5.6.2.1 Introduction . 28
5.6.2.2 Type SpendingLimitContext . 29
5.6.2.3 Type SpendingLimitStatus . 31
5.6.2.4 Type PolicyCounterInfo . 32
5.6.2.5 Type PendingPolicyCounterStatus . 32
5.6.2.6 Type SubscriptionTerminationInfo . 32
5.6.3 Simple data types and enumerations . 33
5.6.3.1 Introduction . 33
5.6.3.2 Simple data types . 33
5.6.3.3 Enumeration: TerminationCause . 33
5.7 Error handling . 33
5.7.1 General . 33
5.7.2 Protocol Errors . 33
5.7.3 Application Errors . 33
5.8 Feature negotiation . 34
5.9 Security . 34
Annex A (normative): OpenAPI specification . 35
A.1 General . 35
A.2 Nchf_SpendingLimitControl Service API . 35
Annex B (normative): 5GC and EPC interworking scenario support . 41
B.1 Scope . 41
B.2 Nchf_SpendingLimitControl Service . 41
B.2.1 Service Description . 41
B.2.1.1 Overview . 41
B.2.1.2 Service Architecture . 41
B.3 Service Operation . 41
B.3.1 Introduction . 41
B.3.2 Nchf_SpendingLimitControl_Subscribe Service Operation . 41
B.3.3 Nchf_SpendingLimitControl_Unsubscribe Service Operation . 41
B.3.4 Nchf_SpendingLimitControl_Notify Service Operation . 41
Annex C (normative): Wireless and wireline convergence access support . 42
C.1 Scope . 42
C.2 Nchf_SpendingLimitControl Service . 42
C.2.1 Service Description . 42
C.2.1.1 Overview . 42
C.2.1.2 Service Architecture . 42
C.3 Service Operation . 42
C.3.1 Introduction . 42
C.3.2 Nchf_SpendingLimitControl_Subscribe Service Operation . 42
ETSI
3GPP TS 29.594 version 18.4.0 Release 18 5 ETSI TS 129 594 V18.4.0 (2024-07)
C.3.2.1 General . 42
C.3.3 Nchf_SpendingLimitControl_Unsubscribe Service Operation . 42
C.3.4 Nchf_SpendingLimitControl_Notify Service Operation . 43
Annex D (informative): Change history . 44
History . 47

ETSI
3GPP TS 29.594 version 18.4.0 Release 18 6 ETSI TS 129 594 V18.4.0 (2024-07)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
3GPP TS 29.594 version 18.4.0 Release 18 7 ETSI TS 129 594 V18.4.0 (2024-07)
1 Scope
The present specification provides the stage 3 definition of the Spending Limit Control Service of the 5G System.
The 5G System Architecture is defined in 3GPP TS 23.501 [2]. The stage 2 definition and related procedures for the
Spending Limit Control Service are specified in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [6].
The 5G System stage 3 call flows are provided in 3GPP TS 29.513 [12].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition
are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
The Spending Limit Control Service is provided by the Charging Function (CHF) and enables the NF service consumer
to retrieve policy counter status information. The internal CHF functionality for policy counter management
provisioning is specified in 3GPP TS 32.240 [7].
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 TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[6] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2".
[7] 3GPP TS 32.240: "Charging architecture and principles; Stage 2".
[8] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)".
[9] OpenAPI: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0.
[10] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
[11] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces".
[12] 3GPP TS 29.513: "5G System; Policy and Charging Control signalling flows and QoS parameter
mapping; Stage 3".
[13] IETF RFC 9457: "Problem Details for HTTP APIs".
[14] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
[15] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
[16] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3".
[17] 3GPP TR 21.900: "Technical Specification Group working methods".
ETSI
3GPP TS 29.594 version 18.4.0 Release 18 8 ETSI TS 129 594 V18.4.0 (2024-07)
[18] 3GPP TS 29.512: "5G System; Session Management Policy Control Service; Stage 3".
[19] 3GPP TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)".
3 Definitions 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 [1].
Nchf: Service-based interface exhibited by Charging Function.
Policy counter: A mechanism within the CHF to track spending applicable to a subscriber.
Policy counter identifier: A reference to a policy counter in the CHF for a subscriber.
Policy counter status: A label whose values are not standardized and that is associated with a policy counter's value
relative to the spending limit(s) (the number of possible policy counter status values for a policy counter is one greater
than the number of thresholds associated with that policy counter, i.e. policy counter status values describe the status
around the thresholds). This is used to convey information relating to subscriber spending from CHF to PCF. Specific
labels are configured jointly in CHF and PCF.
Spending limit: A spending limit is the usage limit of a policy counter (e.g. monetary, volume, duration) that a
subscriber is allowed to consume.
Spending limit report: A notification, containing the current policy counter status generated from the CHF to the PCF.
3.2 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].
5G-RG 5G Residential Gateway
CCS Converged Charging System
CHF Charging Function
CTS Charging Trigger Function
FN-RG Fixed Network Residential Gateway
GCI Global Cable Identifier
GLI Global Line Identifier
GPSI Generic Public Subscription Identifier
NF Network Function
NRF Network Repository Function
PCF Policy Control Function
SUPI Subscription Permanent Identifier
W-AGF Wireline Access Gateway Function
4 Nchf_SpendingLimitControl Service
4.1 Service Description
4.1.1 Overview
The Nchf_SpendingLimitControl service, as defined in 3GPP TS23.502 [3] and 3GPP TS23.503 [6], is provided by the
Charging Function (CHF).
ETSI
3GPP TS 29.594 version 18.4.0 Release 18 9 ETSI TS 129 594 V18.4.0 (2024-07)
The Nchf_SpendingLimitControl service enables the NF service consumer (e.g. PCF) to retrieve policy counter status
information and spending limit reporting per UE from the CHF.
If the spending limit reporting is no more required, the Nchf_SpendingLimitControl service enables the NF service
consumer to unsubscribe from the reporting.
Nchf_SpendingLimitControl Service applies to the cases where the PCF interacts with the CHF in the non-roaming
scenario, and for roaming scenario the H-PCF for the PDU session interacts with the H-CHF in the home-routed
scenario. Roaming scenarios are not supported for the PCF for the UE in this release of the specification.
4.1.2 Service Architecture
The Nchf_SpendingLimitControl service is provided by the CHF and consumed by the NF service consumer (e.g. PCF),
as shown in figure 4.1.2-1 for the SBI representation model and in figure 4.1.2-2 for the reference point representation
model.
CHF
Nchf
Nchf_SpendingLimitControl
PCF
Figure 4.1.2-1: Nchf_SpendingLimitControl service architecture, SBI representation
CHF
N28
PCF
Figure 4.1.2-2: Nchf_SpendingLimitControl service architecture, reference point representation
4.1.3 Network Functions
4.1.3.1 Charging Function (CHF)
The Charging Function (CHF) is part of the Converged Charging System (CCS). The CHF provides the
Nchf_SpendingLimitControl service and is specified in 3GPP TS 32.240 [7].
4.1.3.2 NF Service Consumers
The PCF is the known NF service consumer, as defined in 3GPP TS 23.502 [3]. The NF service consumer accesses
policy counter status information relating to the subscriber spending from the CHF and uses the status of each relevant
policy counter as input to its policy decision as required by the decision logic.
ETSI
3GPP TS 29.594 version 18.4.0 Release 18 10 ETSI TS 129 594 V18.4.0 (2024-07)
4.2 Service Operations
4.2.1 Introduction
The service operations defined for the Nchf_SpendingLimitControl service are shown in table 4.2.1-1.
Table 4.2.1-1: Nchf_SpendingLimitControl Service Operations
Service operation name Description Initiated by
Nchf_SpendingLimitControl_Subscribe This service operation is used by NF service NF service consumer
consumers to subscribe to notification of (e.g. PCF)
changes in the status of the policy counters
available and retrieval of the status of the policy
counters for which subscription is accepted.
Nchf_SpendingLimitControl_Unsubscribe This service operation is used by NF service NF service consumer
consumers to unsubscribe from notification of (e.g. PCF)
changes in the status of all policy counters.
Nchf_SpendingLimitControl_Notify This service operation is used by the CHF to CHF
notify the NF service consumers about the
change of the status of the subscribed policy
counters. Alternatively, it can be used by the
CHF to notify that the status for one or multiple
subscribed policy counter will change in the
future, indicating the time when this change
shall be applied. Alternatively, it is also used to
notify the NF service consumer of the removal
of a subscriber from the CHF system for the
purpose that the NF service consumer can
terminate the subscriptions of all policy counters
of the subscriber.
4.2.2 Nchf_SpendingLimitControl_Subscribe service operation
4.2.2.1 General
The Nchf_SpendingLimitControl_Subscribe service operation is used by the NF service consumer to subscribe to
notification of changes in the status of the policy counters available and to retrieve the status of the policy counters for
which the subscription is accepted. The following procedures are related to the subscribe service operation:
- initial spending limit retrieval; and
- intermediate spending limit report retrieval.
4.2.2.2 Initial spending limit retrieval
Figure 4.2.2.2-1 shows the scenario where the NF service consumer sends a request to the CHF to retrieve the status of
policy counters available at the CHF and to subscribe to spending limit reporting (see also 3GPP TS 23.502 [3],
figure 4.16.8.2.1).
ETSI
3GPP TS 29.594 version 18.4.0 Release 18 11 ETSI TS 129 594 V18.4.0 (2024-07)
NF service
CHF
consumer
1. POST…/subscriptions
2. 201 Created
Figure 4.2.2.2-1: NF service consumer subscribes to retrieve policy counter status and spending limit
reporting
The NF service consumer shall send an HTTP POST request to the resource "{apiRoot}/nchf-
spendinglimitcontrol/v1/subscriptions" representing the "Spending Limit Retrieval Subscriptions", as shown in
figure 4.2.2.2-1, step 1, to create a subscription for retrieval of the policy counter status and spending limit reporting.
The "SpendingLimitContext" data structure provided in the request body shall include:
- the Subscription Permanent Identifier (SUPI) encoded in the "supi" attribute;
- the notification correlation target address encoded in the "notifUri" attribute; and
- If the feature "NotificationCorrelation" is supported, a Notification Correlation Identifier assigned by the NF
service consumer for the requested notifications encoded in the "notifId" attribute, if the "notifUri" does not
encode within the provided URI the notification correlation Id.
NOTE: NF service consumer (e.g. PCF) ensures the combination of notifUri and notifId is unique per
subscription in the whole network, including multiple network slices scenario.
The "SpendingLimitContext" data structure provided in the request body may include:
- the General Public Subscription Identifier (GPSI) encoded in the "gpsi" attribute;
- Event Filter information "list of policy counter identifier(s)" encoded in the "policyCounterIds" attribute. The
"policyCounterIds" attribute shall contain the list of policy counter identifiers to be subscribed to. If the
"policyCounterIds" attribute is omitted, the subscription is to all available policy counters; and
- when the feature "SubscriptionExpirationTimeControl" is supported by the NF service consumer, the NF service
consumer may include an expiry time encoded in the "expiry" attribute, representing the time up to which the
subscription is desired to be kept active. When the "expiry" attribute is omitted in the request, it represents the
NF service consumer does not have any time constraint in the duration of the subscription.
If the CHF cannot successfully fulfil the received HTTP POST request due to an internal CHF error or due to the error
in the HTTP POST request, the CHF shall send the HTTP error response as specified in clause 5.7.
If the subscriber specified in the request is unknown to the CHF, the CHF shall indicate in an HTTP "400 Bad Request"
response the cause for the rejection with the "cause" attribute set to "USER_UNKNOWN".
If the CHF has no available policy counters specified for the subscriber, the CHF shall indicate in an HTTP "400 Bad
Request" response the cause for the rejection with the "cause" attribute set to
"NO_AVAILABLE_POLICY_COUNTERS ".
If one or more policy counters specified in the request in the "policyCounterIds" attribute are unknown to the CHF, and
the CHF is configured to reject request, the CHF shall indicate in an HTTP "400 Bad Request" response the cause for
the rejection with the "cause" attribute set to "UNKNOWN_POLICY_COUNTERS" and the unknown policy counter
identifiers within the "invalidParams" attribute.
Otherwise, upon the reception of an HTTP POST request the CHF shall:
ETSI
3GPP TS 29.594 version 18.4.0 Release 18 12 ETSI TS 129 594 V18.4.0 (2024-07)
- create a new subscription resource, which contains the list of the policy counters included in the
"policyCounterIds" attribute, or if the "policyCounterIds" attribute is omitted, all the policy counters of the
subscriber;
- assign a subscriptionId; and
- store the subscription resource.
After the CHF created an "Individual Spending Limit Retrieval Subscription" resource, the CHF shall respond with
"201 Created" response with a Location header field containing the URI of the created subscription resource and the
message body containing a representation of the created subscription, as shown in figure 4.2.2.2-1, step 2.
The SpendingLimitStatus data structure provided in the response body shall include the status of the requested
subscribed policy counters in the "statusInfos" map, where every PolicyCounterInfo entry shall contain:
- the policy counter identifier in the "policyCounterId" attribute; and
- the policy counter status in the "currentStatus" attribute.
When a requested policy counter identifier is known by the CHF, but it is not applicable to the subscriber (e.g. not
provisioned), the CHF may include it in the "statusInfos" map, and set the "currentStatus" attribute to an operator
configured policy counter status to indicate this to the NF service consumer.
When one or more policy counters specified in the request in the "policyCounterIds" attribute are unknown to the CHF,
and the CHF is configured to accept the request, the CHF may include the unknown policy counters in the "statusInfos"
map, and set the "currentStatus" attribute to an operator configured policy counter status to indicate this to the NF
service consumer.
A PolicyCounterInfo data structure may include the list of the pending policy counter statuses and their activation times
within the attribute "penPolCounterStatuses".
When the feature "SubscriptionExpirationTimeControl" is supported, the CHF may include the "expiry" attribute,
representing the time up to which the subscription shall be kept active. If an expiry time was included in the
subscription request, then the expiry time shall be returned in the response, and the value shall be less than or equal to
the requested value. When the "expiry" attribute is omitted in the request and in the response, it represents neither the
CHF or the NF service consumer have time constrains in the duration of the subscription and shall be kept active till the
explicit subscription termination as described in clause 4.2.3.2 and clause 4.2.4.3.
NOTE 1: If the NF Service Consumer does not include a expiry time in the request, the CHF can include a expiry
time in the response that represents the time after which the subscription becomes invalid.
NOTE 2: Once the subscription expires, if the NF service consumer wants to keep receiving notifications, it needs
to create a new subscription in the CHF, as specified in this clause.
4.2.2.3 Intermediate spending limit report retrieval
Figure 4.2.2.3-1 shows the scenario where the NF service consumer sends a request to the CHF to modify the existing
subscription to the retrieval of spending limit reports (see also 3GPP TS 23.502 [3], figure 4.16.8.3.1). The NF service
consumer can add or remove policy counters to retrieve the status of the counters.
ETSI
3GPP TS 29.594 version 18.4.0 Release 18 13 ETSI TS 129 594 V18.4.0 (2024-07)
NF service
CHF
consumer
1. PUT…/subscriptions/
{subscriptionId}
2. 200 OK
Figure 4.2.2.3-1: NF service consumer modifies the subscription to retrieve policy counter status and
spending limit reporting
The NF service consumer shall send an HTTP PUT request to the resource "{apiRoot}/nchf-
spendinglimitcontrol/v1/subscriptions/{subscriptionId}" representing an existing "Individual Spending Limit
Subscription" resource, as shown in figure 4.2.2.3-1, step 1, to modify the subscription for retrieval of the policy
counter status and spending limit reporting.
The "SpendingLimitContext" data structure provided in the request body:
- shall include the Subscription Permanent Identifier (SUPI) encoded in the "supi" attribute;
- shall include the notification correlation target address encoded in the "notifUri" attribute;
- if the feature "NotificationCorrelation" is supported, a Notification Correlation Identifier assigned by the NF
service consumer for the requested notifications encoded in the "notifId" attribute, if the "notifUri" does not
encode within the provided URI the notification correlation Id.
NOTE 1: If the notification correlation target address is not changed the previously provided notification
correlation target address is included in the "notifUri" attribute. If the Notification Correlation Id is not
changed the previously provided Notification Correlation Id is included in the "notifId" attribute.
- if the General Public Subscription Identifier (GPSI) was provided within the initial spending limit retrieval
procedure, described in clause 4.2.2.2, shall include the GPSI encoded in the "gpsi" attribute; and
- may include Event Filter information as a "list of policy counter identifier(s)" encoded in the "policyCounterIds"
attribute. The "policyCounterIds" attribute shall contain the updated list of policy counter identifiers to be
subscribed to. If the "policyCounterIds" attribute is omitted, the subscription is updated to all available policy
counters; and
- when the feature "SubscriptionExpirationTimeControl" is supported, may include an updated expiry time
encoded in the "expiry" attribute to update the duration of the subscription, representing the updated time up to
which the subscription is desired to be kept active. When the "expiry" attribute is omitted in the request, it
represents the NF service consumer update does not have any time constraint from this moment on in the
duration of the subscription.
NOTE 2: The "notifUri" attribute within the SpendingLimitContext data structure can be modified to request that
subsequent notifications are sent to a new NF service consumer.
When the "policyCounterIds" attribute is present in the subscription request, this list of policy counters overrides a
previously provisioned list.
After the CHF modified an "Individual Spending Limit Retriev
...