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

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

RTS/TSGC-0329594vf50

General Information

• Status: Published
• Publication Date: 13-Oct-2019
• Technical Committee: 3GPP CT 3 - Interworking with external networks (formely CN3)
• Current Stage: 12 - Completion
• Completion Date: 14-Oct-2019

Standards Content (Sample)

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






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



---------------------- Page: 1 ----------------------
3GPP TS 29.594 version 15.5.0 Release 15 1 ETSI TS 129 594 V15.5.0 (2019-10)



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

Tel.: [phone]  Fax: [phone]

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

---------------------- Page: 2 ----------------------
3GPP TS 29.594 version 15.5.0 Release 15 2 ETSI TS 129 594 V15.5.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

---------------------- Page: 3 ----------------------
3GPP TS 29.594 version 15.5.0 Release 15 3 ETSI TS 129 594 V15.5.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 . 11
4.2.3 Nchf_SpendingLimitControl_Unsubscribe service operation . 12
4.2.3.1 General . 12
4.2.3.2 Unsubscribe from spending limit reporting . 12
4.2.4 Nchf_SpendingLimitControl_Notify service operation . 13
4.2.4.1 General . 13
4.2.4.2 Spending limit report. 13
4.2.4.3 Subscription termination request by CHF . 14
5 Nchf_SpendingLimitControl Service API . 15
5.1 Introduction . 15
5.2 Usage of HTTP . 15
5.2.1 General . 15
5.2.2 HTTP standard headers . 15
5.2.2.1 General . 15
5.2.2.2 Content type . 15
5.2.3 HTTP custom headers . 15
5.2.3.1 General . 15
5.3 Resources . 16
5.3.1 Resource Structure . 16
5.3.2 Resource: Spending Limit Retrieval Subscriptions (Collection) . 16
5.3.2.1 Description . 16
5.3.2.2 Resource definition . 16
5.3.2.3 Resource Standard Methods . 17
5.3.2.3.1 POST . 17
5.3.2.4 Resource Custom Operations . 17
5.3.3 Resource: Individual Spending Limit Retrieval Subscription (Document) . 17
5.3.3.1 Description . 17
5.3.3.2 Resource definition . 17
5.3.3.3 Resource Standard Methods . 18
5.3.3.3.1 PUT . 18
5.3.3.3.2 DELETE . 18
5.4 Custom Operations without associated resources. 19
ETSI

---------------------- Page: 4 ----------------------
3GPP TS 29.594 version 15.5.0 Release 15 4 ETSI TS 129 594 V15.5.0 (2019-10)
5.5 Notifications . 19
5.5.1 General . 19
5.5.2 Spending limit notification . 19
5.5.2.1 Description . 19
5.5.2.2 Target URI . 19
5.5.2.3 Standard Methods . 19
5.5.2.3.1 POST . 19
5.5.3 Subscription Termination . 20
5.5.3.1 Description . 20
5.5.3.2 Target URI . 20
5.5.3.3 Standard Methods . 20
5.5.3.3.1 POST . 20
5.6 Data Model . 21
5.6.1 General . 21
5.6.2 Structured data types . 21
5.6.2.1 Introduction . 21
5.6.2.2 Type SpendingLimitContext . 22
5.6.2.3 Type SpendingLimitStatus . 23
5.6.2.4 Type PolicyCounterInfo . 23
5.6.2.5 Type PendingPolicyCounterStatus . 23
5.6.2.6 Type SubscriptionTerminationInfo . 24
5.6.3 Simple data types and enumerations . 24
5.6.3.1 Introduction . 24
5.6.3.2 Simple data types . 24
5.6.3.3 Enumeration: TerminationCause . 24
5.7 Error handling . 24
5.7.1 General . 24
5.7.2 Protocol Errors . 24
5.7.3 Application Errors . 25
5.8 Feature negotiation . 25
5.9 Security . 25
Annex A (normative): OpenAPI specification . 26
A.1 General . 26
A.2 Nchf_SpendingLimitControl Service API . 26
Annex B (informative): Change history . 31
History . 34

ETSI

---------------------- Page: 5 ----------------------
3GPP TS 29.594 version 15.5.0 Release 15 5 ETSI TS 129 594 V15.5.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

---------------------- Page: 6 ----------------------
3GPP TS 29.594 version 15.5.0 Release 15 6 ETSI TS 129 594 V15.5.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

---------------------- Page: 7 ----------------------
3GPP TS 29.594 version 15.5.0 Release 15 7 ETSI TS 129 594 V15.5.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

---------------------- Page: 8 ----------------------
3GPP TS 29.594 version 15.5.0 Release 15 8 ETSI TS 129 594 V15.5.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

---------------------- Page: 9 ----------------------
3GPP TS 29.594 version 15.5.0 Release 15 9 ETSI TS 129 594 V15.5.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

---------------------- Page: 10 ----------------------
3GPP TS 29.594 version 15.5.0 Release 15 10 ETSI TS 129 594 V15.5.0 (2019-10)
The NF service consumer shall send an HTTP POST request to the resource "{apiRoot}/nchf-
spendinglimitcontrol/v1/subscriptions" representing the "Spending Limit RetrievalSubscriptions", 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; and
- the notification correlation target address encoded in the "notifUri" attribute.
The "SpendingLimitContext" data structure provided in the request body may include:
- the General Public Subscription Identifier (GPSI) encoded in the "gpsi" attribute; and
- 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.
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 i
...