ETSI TS 129 594 V15.4.0 (2019-10)

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


3GPP TS 29.594 version 15.4.0 Release 15 1 ETSI TS 129 594 V15.4.0 (2019-10)

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

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

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

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

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

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3GPP TS 29.594 version 15.4.0 Release 15 2 ETSI TS 129 594 V15.4.0 (2019-10)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 29.594 version 15.4.0 Release 15 3 ETSI TS 129 594 V15.4.0 (2019-10)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Nchf_SpendingLimitControl Service . 7
4.1 Service Description . 7
4.1.1 Overview . 7
4.1.2 Service Architecture . 7
4.1.3 Network Functions . 8
4.1.3.1 Charging Function (CHF) . 8
4.1.3.2 NF Service Consumers . 8
4.2 Service Operations . 8
4.2.1 Introduction. 8
4.2.2 Nchf_SpendingLimitControl_Subscribe service operation . 9
4.2.2.1 General . 9
4.2.2.2 Initial spending limit retrieval . 9
4.2.2.3 Intermediate spending limit report retrieval . 10
4.2.3 Nchf_SpendingLimitControl_Unsubscribe service operation . 11
4.2.3.1 General . 11
4.2.3.2 Unsubscribe from spending limit reporting . 11
4.2.4 Nchf_SpendingLimitControl_Notify service operation . 12
4.2.4.1 General . 12
4.2.4.2 Spending limit report. 12
4.2.4.3 Subscription termination request by CHF . 13
5 Nchf_SpendingLimitControl Service API . 14
5.1 Introduction . 14
5.2 Usage of HTTP . 14
5.2.1 General . 14
5.2.2 HTTP standard headers . 14
5.2.2.1 General . 14
5.2.2.2 Content type . 14
5.2.3 HTTP custom headers . 15
5.2.3.1 General . 15
5.3 Resources . 15
5.3.1 Resource Structure . 15
5.3.2 Resource: Spending Limit Retrieval Subscriptions (Collection) . 15
5.3.2.1 Description . 15
5.3.2.2 Resource definition . 15
5.3.2.3 Resource Standard Methods . 16
5.3.2.3.1 POST . 16
5.3.2.4 Resource Custom Operations . 16
5.3.3 Resource: Individual Spending Limit Retrieval Subscription (Document) . 16
5.3.3.1 Description . 16
5.3.3.2 Resource definition . 16
5.3.3.3 Resource Standard Methods . 17
5.3.3.3.1 PUT . 17
5.3.3.3.2 DELETE . 17
5.4 Custom Operations without associated resources. 18
ETSI
3GPP TS 29.594 version 15.4.0 Release 15 4 ETSI TS 129 594 V15.4.0 (2019-10)
5.5 Notifications . 18
5.5.1 General . 18
5.5.2 Spending limit notification . 18
5.5.2.1 Description . 18
5.5.2.2 Target URI . 18
5.5.2.3 Standard Methods . 18
5.5.2.3.1 POST . 18
5.5.3 Subscription Termination . 19
5.5.3.1 Description . 19
5.5.3.2 Target URI . 19
5.5.3.3 Standard Methods . 19
5.5.3.3.1 POST . 19
5.6 Data Model . 20
5.6.1 General . 20
5.6.2 Structured data types . 20
5.6.2.1 Introduction . 20
5.6.2.2 Type SpendingLimitContext . 21
5.6.2.3 Type SpendingLimitStatus . 22
5.6.2.4 Type PolicyCounterInfo . 22
5.6.2.5 Type PendingPolicyCounterStatus . 22
5.6.2.6 Type SubscriptionTerminationInfo . 23
5.6.3 Simple data types and enumerations . 23
5.6.3.1 Introduction . 23
5.6.3.2 Simple data types . 23
5.6.3.3 Enumeration: TerminationCause . 23
5.7 Error handling . 23
5.7.1 General . 23
5.7.2 Protocol Errors . 23
5.7.3 Application Errors . 24
5.8 Feature negotiation . 24
5.9 Security . 24
Annex A (normative): OpenAPI specification . 25
A.1 General . 25
A.2 Nchf_SpendingLimitControl Service API . 25
Annex B (informative): Change history . 30
History . 33

ETSI
3GPP TS 29.594 version 15.4.0 Release 15 5 ETSI TS 129 594 V15.4.0 (2019-10)
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 15.4.0 Release 15 6 ETSI TS 129 594 V15.4.0 (2019-10)
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 3.0.0 Specification", https://github.com/OAI/OpenAPI-
Specification/blob/master/versions/3.0.0.md.
[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 7807: "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".
ETSI
3GPP TS 29.594 version 15.4.0 Release 15 7 ETSI TS 129 594 V15.4.0 (2019-10)
[17] 3GPP TR 21.900: "Technical Specification Group working methods".
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.
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].
CCS Converged Charging System
CHF Charging Function
CTS Charging Trigger Function
GPSI Generic Public Subscription Identifier
NF Network Function
NRF Network Repository Function
PCF Policy Control Function
SUPI Subscription Permanent Identifier
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).
The Nchf_SpendingLimitControl service enables the NF service consumer to retrieve policy counter status information
per UE from the CHF by subscribing to spending limit reporting (i.e. notifications of policy counter status changes).
If the spending limit reporting is no more required the Nchf_SpendingLimitControl service enables the NF service
consumer to unsubscribe from the reporting.
4.1.2 Service Architecture
The Nchf_SpendingLimitControl service is provided by the CHF and consumed by the 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.
ETSI
3GPP TS 29.594 version 15.4.0 Release 15 8 ETSI TS 129 594 V15.4.0 (2019-10)
CHF
Nchf
Nchf_SpendingLimitControl
PCF
Figure 4.1.2-1: Nchf_SpendingLimitContol service architecture, SBI representation
CHF
N28
PCF
Figure 4.1.2-2: Nchf_SpendingLimitContol 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.
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.
ETSI
3GPP TS 29.594 version 15.4.0 Release 15 9 ETSI TS 129 594 V15.4.0 (2019-10)
Table 4.2.1-1: Nchf_SpendingLimitControl Service Operations
Service operation name Description Initiated by
Nchf_SpendingLimitControl_Subscribe This service operation is used by an NF NF service
service consumer to subscribe to notification consumer (PCF)
of 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 an NF NF service
service consumer to unsubscribe from consumer (PCF)
notification of 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).
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
ETSI
3GPP TS 29.594 version 15.4.0 Release 15 10 ETSI TS 129 594 V15.4.0 (2019-10)
The NF service consumer shall send an HTTP POST request to the resource "{apiRoot}/nchf-
spendinglimitcontrol/v1/subscriptions" representing the "CHF 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 data structure provided in the request body shall include:
- the Subscription Permanent Identifier (SUPI); and
- the notification correlation target address.
The data structure provided in the request body may include:
- the General Public Subscription Identifier (GPSI); and
- Event Filter information "list of policy counter identifier(s)".
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 subclause 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 ".
Otherwise, upon the reception of an HTTP POST request the CHF shall:
- create a new subscription;
- assign a subscriptionCorrelationId; and
- store the subscription.
After the CHF created an "Individual CHF Subscription" resource, the CHF shall respond with "201 Created" with the
message body containing a representation of the created subscription, as shown in figure 4.2.2.2-1, step 2.
The data structure provided in the response body shall include:
- the status of the requested subscribed policy counters to the subscriber in the event information.
The data structure provided in the response body may include:
- pending policy counter statuses and their activation times for all policy counter(s) available for the subscriber;
- if a list of policy counter identifier(s) was provided, the CHF returns only the pending policy counter statuses
and their activation times, per required policy counter identifier in the event Information
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 15.4.0 Release 15 11 ETSI TS 129 594 V15.4.0 (2019-10)
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 "CHF Subscriptions", 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 data structure provided in the request body may include:
- Event Filter information "list of policy counter identifier(s)"; and
- a new notification correlation target address.
After the CHF modified an "Individual CHF Subscription" resource, the CHF shall respond with "200 OK" with the
message body containing a representation of the modified subscription, as shown in figure 4.2.2.3-1, step 2.
The data structure provided in the response body shall include:
- the status of the requested subscribed policy counters to the subscriber in the event information.
The data structure provided in the response body may include:
- pending policy counter statuses and their activation times for all policy counter(s) available for the subscriber;
- if a list of policy counter identifier(s) was provided, the CHF returns only the pending policy counter statuses
and their activation times, per required policy counter identifier in the event Information
If the HTTP PUT request is not accepted by the CHF, it shall indicate the appropriate cause for the rejection in the
HTTP response code to the NF service consumer. 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 ".
4.2.3 Nchf_SpendingLimitControl_Unsubscribe service operation
4.2.3.1 General
The Nchf_SpendingLimitControl_Unsubscribe service operation is used by the NF service consumer to cancel the
subscription of status changes for all the policy counters available at the CHF. That means the complete cancellation of
the spending limit reporting procedure.
4.2.3.2 Unsubscribe from spending limit reporting
Figure 4.2.3.2-1 shows the scenario where the NF service consumer sends a request to the CHF to unsubscribe from
spending limit reporting (see also 3GPP TS 23.502 [3] figure 4.16.8.4.1).
ETSI
3GPP TS 29.594 version 15.4.0 Release 15 12 ETSI TS 129 594 V15.4.0 (2019-10)
NF service
CHF
consumer
1. DELETE…/subscriptions/
{subscriptionId}
2. 204 No Content
Figure 4.2.3.2-1: NF service consumer unsubscribes from spending limit reporting
The NF service consumer shall invoke the Nchf_SpendingLimitControl_Unsubscribe service operation to unsubscribe
from the spending limit reporting (status change for all policy counters available is no more required). The NF service
consumer shall send an HTTP DELETE request to the resource "{apiRoot}/nchf-spendinglimitcontrol/v1/subscriptions
/{subscriptionId}", whereby the "{subscriptionId}" is the identification of the existing subscription to be deleted. Upon
the reception of an HTTP DELETE request the CHF removes the corresponding subscription.
If the HTTP DELETE request is accepted by the CHF, it shall respond with "204 No Content" as shown in
figure 4.2.3.2-1, step 2.
If the HTTP DELETE request is not accepted by the CHF, it shall indicate the appropriate cause for the rejection in the
HTTP response code to the NF service consumer.
4.2.4 Nchf_SpendingLimitControl_Notify service operation
4.2.4.1 General
The Nchf_SpendingLimitControl_Notify service operation is used by the CHF:
- to notify the change of the status of the subscribed policy counters available at the CHF for that subscriber;
and/or
- to provide one or more pending statuses for a subscribed policy counter together with the time they shall be
applied; and/or
- to request the termination of the subscription of status changes for all policy counters for a subscriber (e.g. the
subscriber is removed from the CHF system).
NOTE: The SUPI represents the subscription Id.
4.2.4.2 Spending limit report
Figure 4.2.4.2-1 shows the scenario where the CHF sends a notification to the NF service consumer, when it detects that
the status of a policy counter(s) has changed and the NF service consumer has subscribed to notifications of changes in
the status of this policy counter(s). The CHF can also notify the NF service consumer that the status for one or multiple
subscribed policy counter will change and indicate this by providing the time when this change shall be applied (see
also 3GPP TS 23.502 [3], figure 4.16.8.5.1).
ETSI
3GPP TS 29.594 version 15.4.0 Release 15 13 ETSI TS 129 594 V15.4.0 (2019-10)

NF service
CHF
consumer
1. POST…/{notifUri}/notify
2. 204 No Content
Figure 4.2.4.2-1: Spending limit reporting
The CHF shall send an HTTP POST request to the resource notification target address (notifUri) of the NF service
consumer received in the subscription creation or modification, and shall append the "notify" segment path at the end of
the URI, to indicate the NF service consumer the notification of a policy counter status change.
The data structure provided in the request body shall include:
- Subscriber Id; and
- Policy counter status as event information.
The data structure provided in the request body may include:
- Pending policy counter statuses and their activation times as event information.
If the HTTP POST notification request message is accepted by the NF service consumer, it shall acknowledge the
receipt of the event notification with a "204 No Content" response, as shown in figure 4.2.4.2-1, step 2.
If the HTTP POST request is not accepted and the information received is not considered by the NF service consumer,
the NF service consumer shall indicate the appropriate cause for the rejection in the HTTP response code to the CHF.
4.2.4.3 Subscription termination request by CHF
Figure 4.2.4.3-1 shows the scenario where the CHF sends a notification to the NF service consumer, when it requests
the termination of the subscription of status changes for all policy counters for a subscriber.

NF service
CHF
consumer
1. POST…/{notifUri}/terminate
2. 204 No Content
Figure 4.2.4.3-1: Subscription termination request by CHF
The CHF shall send an HTTP POST request to the resource notification target address (notifUri) of the NF service
consumer received in the subscription creation or modification and shall append the "terminate" segment path at the end
of the URI, to indicate the subscription termination to the NF service consumer.
ETSI
3GPP TS 29.594 version 15.4.0 Release 15 14 ETSI TS 129 594 V15.4.0 (2019-10)
The data structure provided in the request body shall include:
- Subscriber Id; and
- subscription termination information.
If the HTTP POST notification request message is accepted by the NF service consumer, it shall remove the
subscription to notifications of all policy counters for a subscriber and shall acknowledge the receipt of the event
notification with a "204 No Content" response, as shown in figure 4.2.4.3-1, step 2.
If the HTTP POST request is not accepted and the information received is not considered by the NF service consumer,
the NF service consumer shall indicate the appropriate cause for the rejection in the HTTP response code to the CHF.
5 Nchf_SpendingLimitControl Service API
5.1 Introduction
The Nchf_SpendingLimitControl service shall use the Nchf_SpendingLimitControl 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 TS29.501 [5].
- The {apiName} shall be "nchf-spendinglimitcontrol".
- The {apiVersion} shall be "v1".
- The {apiSpecificResourceUriPart} shall be set as described in subclause 5.3.
5.2 Usage of HTTP
5.2.1 General
HTTP/2, IETF RFC 7540 [8], shall be used as specified in subclause 5.2 of 3GPP TS 29.500 [4].
HTTP/2 shall be transported as specified in subclause 5.3 of 3GPP TS 29.500 [4].
The OpenAPI [9] specification of HTTP messages and content bodies for the Nchf_SpendingLimitControl service is
contained in Annex A.
5.2.2 HTTP standard headers
5.2.2.1 General
See subclause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers.
5.2.2.2 Content type
JSON, IETF RFC 8259 [10], 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 [4]. The use of the JSON format shall be signalled by the content type
"application/json".
"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and
shall be signalled by the content type "application/problem+json", as defined in IETF RFC 7807 [13].
ETSI
3GPP TS 29.594 version 15.4.0 Release 15 15 ETSI TS 129 594 V15.4.0 (2019-10)
5.2.3 HTTP custom headers
5.2.3.1 General
The Nchf_SpendingLimitControl API shall support HTTP custom header fields specified in subclause 5.2.3.2 of
3GPP TS 29.500 [4].
In this Release of the specification, no specific custom headers are defined for the Nchf_SpendingLimitControl API.
5.3 Resources
5.3.1 Resource Structure
Figure 5.3.1-1 shows the resource structure of the Nchf_SpendingLimitControl API.

{apiRoot}/nchf-spendinglimitcontrol/v1
/subscriptions
/{subscriptionId}
Figure 5.3.1-1: Resource URI structure of the Nchf_SpendingLimitControl API
Table 5.3.1-1 provides an overview of the resources and applicable HTTP methods.
Table 5.3.1-1: Resources and methods overview
HTTP method
Resource name Resource URI or custom Description
operation
Spending Limit Retrieval {apiRoot}/ POST Creates a new individual spending
Subscriptions nchf-spendinglimitcontrol/v1 limit retrieval subscription.
/subscriptions
Individual Spending Limit {apiRoot}/ PUT Modifies an existing subscription
Retrieval Subscription nchf-spendinglimitcontrol/v1 (e.g. addition of additional policy
/subscriptions/{subscriptionId} counters).

DELETE Deletes an individual subscription.

5.3.2 Resource: Spending Limit Retrieval Subscriptions (Collection)
5.3.2.1 Description
This resource represents the collection of Nchf_SpendingLimitControl service subscriptions at a given CHF.
5.3.2.2 Resource definition
Resource URI: {apiRoot}/nchf-spendinglimitcontrol/v1/subscriptions
ETSI
3GPP TS 29.594 version 15.4.0 Release 15 16 ETSI TS 129 594 V15.4.0 (2019-10)
This resource shall support the resource URI variables defined in table 5.3.2.2-1.
Table 5.3.2.2-1: Resource URI variables for this resource
Name Definition
apiRoot See subclause 5.1
5.3.2.3 Resource Standard Methods
5.3.2.3.1 POST
This method shall support the URI query parameters specified in table 5.3.2.3.1-1.
Table 5.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 5.3.2.3.1-2 and the response data structures and
response codes specified in table 5.3.2.3.1-3.
Table 5.3.2.3.1-2: Data structures supported by the POST Request Body on this resource
Data type P Cardinality Description
SpendingLimitContext M 1 Contains the information for the creation of a new individual spending
limit retrieval subscription.
Table 5.3.2.3.1-3: Data structures supported by the POST Response Body on this resource
Data type P Cardinality Response codes Description
SpendingLimitStatus M 1 201 Created The spending limit subscription was created and
spending limit reports are provided.
ProblemDetails M 1 400 Bad Request (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 [4] for the POST method shall also apply.
NOTE 2: In addition to protocol and application errors which are specified in subclause 5.2.7.2 of
3GPP TS 29.500 [4], specific errors are described in subclause 5.7.

5.3.2.4 Resource Custom Operations
None.
5.3.3 Resource: Individual Spending Limit Retrieval Subscription
(Document)
5.3.3.1 Description
This resource represents an individual Nchf_SpendingLimitControl service subscription at a given CHF.
5.3.3.2 Resource definition
Resource URI: {apiRoot}/nchf-spendinglimitcontrol/v1/subscriptions/{subscriptionId}
This resource shall support the resource URI variables defined in table 5.3.3.2-1.
ETSI
3GPP TS 29.594 version 15.4.0 Release 15 17 ETSI TS 129 594 V15.4.0 (2019-10)
Table 5.3.3.2-1: Resource URI variables for this resource
Name Definition
apiRoot See subclause 5.1
subscriptionId String identifying a subscription to the CHF spending limit control retrieval service.

5.3.3.3 Resource Standard Methods
5.3.3.3.1 PUT
This method shall support the URI query parameters specified in table 5.3.3.3.1-1.
Table 5.3.3.3.1-1
...