ETSI TS 129 219 V15.3.0 (2019-10)

TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Policy and charging control: Spending limit reporting over Sy
reference point
(3GPP TS 29.219 version 15.3.0 Release 15)

3GPP TS 29.219 version 15.3.0 Release 15 1 ETSI TS 129 219 V15.3.0 (2019-10)

Reference
RTS/TSGC-0329219vf30
Keywords
GSM,LTE,UMTS
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.219 version 15.3.0 Release 15 2 ETSI TS 129 219 V15.3.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.219 version 15.3.0 Release 15 3 ETSI TS 129 219 V15.3.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 Sy reference point . 7
4.1 Overview . 7
4.2 Sy Reference model. 8
4.3 Subscriber Spending Limits . 8
4.4 Functional ele me nts . 9
4.4.1 PCRF . 9
4.4.2 OCS . 9
4.5 Spending Limits procedures over Sy reference point . 9
4.5.1 Initial/Intermediate Spending Limit Report Request . 9
4.5.1.1 General . 9
4.5.1.2 Detailed behaviour of the PCRF . 10
4.5.1.3 The behaviour of the OCS . 10
4.5.2 Spending Limit Report. 11
4.5.2.1 General . 11
4.5.2.2 The behaviour of the OCS . 12
4.5.2.3 Detailed behaviour of the PCRF . 12
4.5.3 Final Spending Limit Report Request . 12
4.5.3.1 General . 12
4.5.3.2 Detailed behaviour of the PCRF . 13
4.5.3.3 The behaviour of the OCS . 13
4.5.4 Sy Session Termination by the OCS . 13
5 Sy protocol . 13
5.1 Protocol support . 13
5.1.1 Use of Diameter base protocol . 13
5.1.2 Void . 14
5.1.3 Accounting functionality . 14
5.1.4 Transport protocol . 14
5.1.5 Advertising Application Support . 14
5.1.6 Use of the Supported-Features AVP . 14
5.2 Initialization and maintenance of connection and session . 15
5.3 Sy specific AVPs . 15
5.3.0 General . 15
5.3.1 Policy-Counter-Identifier AVP . 16
5.3.2 Policy-Counter-Status AVP . 16
5.3.3 Policy-Counter-Status-Report AVP . 16
5.3.4 SL-Request-Type AVP . 16
5.3.5 Pending-Policy-Counter-Information AVP . 17
5.3.6 Pending-Policy-Counter-Change-Time AVP . 17
5.3.7 SN-Request-Type AVP . 17
5.4 Sy re-used AVPs . 17
5.5 Sy specific Experimental-Result-Code AVP values . 18
5.5.1 General . 18
5.5.2 Permanent Failures . 18
5.5.3 Transient Failures . 19
ETSI
3GPP TS 29.219 version 15.3.0 Release 15 4 ETSI TS 129 219 V15.3.0 (2019-10)
5.6 Sy Messages . 19
5.6.1 Command-Code Values . 19
5.6.2 Spending-Limit-Request (SLR) command . 19
5.6.3 Spending-Limit-Answer (SLA) command . 20
5.6.4 Spending-Status-Notification-Request (SNR) command. 20
5.6.5 Spending-Status-Notification-Answer (SNA) command . 20
5.6.6 Session-Termination-Request (STR) command . 21
5.6.7 Session-Termination-Answer (STA) command . 21
Annex A (normative): User Identity for Fixed Broadband Access network convergence . 22
Annex B (informative): Change history . 23
History . 24

ETSI
3GPP TS 29.219 version 15.3.0 Release 15 5 ETSI TS 129 219 V15.3.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.219 version 15.3.0 Release 15 6 ETSI TS 129 219 V15.3.0 (2019-10)
1 Scope
The present document provides the stage 3 specification of the Sy reference point for the present release. The functional
requirements and the stage 2 specifications of the Sy reference point are contained in TS 23.203 [2]. The Sy reference
point lies between the Policy and Charging Rule Function (PCRF) and the Online Charging System (OCS). The internal
OCS functionality for policy counter provision management pertaining to Sy is specified in TS 32.296 [16].
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.203: "Policy Control and Charging architecture".
[3] Void.
[4] IETF RFC 4005: "Diameter Network Access Server Application"
[5] IETF RFC 4006: "Diameter Credit Control Application".
[6] IETF RFC 5719: "Updated IANA Considerations for Diameter Command Code Allocations”
[7] IETF RFC 2234: "Augmented BNF for syntax specifications".
[8] 3GPP TS 29.213:"Policy and charging control signalling flows and Quality of Service (QoS)
parameter mapping".
[9] Void.
[10] Void.
[11] Void.
[12] Void.
[13] IETF RFC 791:"Transmission Control Protocol".
[14] IETF RFC 4960:"Stream Control Transmission Protocol".
[15] 3GPP TS 29.229:"Cx and Dx interfaces based on the Diameter protocol".
[16] 3GPP TS 32.296:"Telecommunication management; charging management; Online Charging
System (OCS) applications and interfaces".
[17] ETSI TS 283 034 v2.2.0:"Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e4 interface based
on the DIAMETER protocol".
[18] IETF RFC 3046:"DHCP Relay Agent Information Option".
[19] 3GPP TS 29.212:"Policy and Charging Control (PCC); Reference points".
[20] IETF RFC 7683:"Diameter Overload Indication Conveyance".
ETSI
3GPP TS 29.219 version 15.3.0 Release 15 7 ETSI TS 129 219 V15.3.0 (2019-10)
[21] IETF RFC 7944: "Diameter Routing Message Priority".
[22] IETF RFC 8583: "Diameter Load Information Conveyance".
[23] IETF RFC 6733: "Diameter Base Protocol".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 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 TR 21.905 [1].
policy counter: A mechanism within the OCS to track spending applicable for a subscriber.
policy counter identifier: A reference to a policy counter in the OCS 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 OCS to PCRF. Specific
labels are configured jointly in OCS and PCRF.
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 OCS to the PCRF
via the Sy reference point.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 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
TR 21.905 [1].
DRMP Diameter Routing Message Priority
OCS Online charging system
OFCS Offline charging system
PCEF Policy and Charging Enforcement Function
PCRF Policy and Charging Rule Function
RCAF RAN Congestion Awareness Function
SLA Spending-Limit-Answer (SL-Answer)
SLR Spending-Limit-Request (SL- Request)
SNA Spending-Status-Notification-Answer (SN-Answer)
SNR Spending-Status-Notification-Request (SN- Request)
STA Session-Termination-Answer (ST-Answer)
STR Session-Termination-Request (ST- Request)
4 Sy reference point
4.1 Overview
The Sy reference point is located between the Policy and Charging Rules Function (PCRF) and the Online Charging
System (OCS). The Sy reference point enables transfer of policy counter status information relating to subscriber
spending from OCS to PCRF and supports the following functions:
ETSI
3GPP TS 29.219 version 15.3.0 Release 15 8 ETSI TS 129 219 V15.3.0 (2019-10)
- Request of policy counter status reporting from PCRF to OCS and subscribe to or unsubscribe from spending
limit reports (i.e. notifications of policy counter status changes).
- Notification of spending limit reports from OCS to PCRF.
- Cancellation of spending limit reporting from PCRF to OCS.
Since the Sy reference point resides between the PCRF and OCS in the HPLMN, roaming with home routed or visited
access as well as non-roaming scenarios are supported in the same manner.
The stage 2 level requirements for the Sy reference point are defined in 3GPP TS 23.203 [2].
Signalling flows related to the Sy interface are specified in 3GPP TS 29.213 [8].
Refer to Annex G of 3GPP TS 29.213 [8] for Diameter overload control procedures over the Sy interface.
Refer to Annex J of 3GPP TS 29.213 [8] for Diameter message priority mechanism procedures over the Sy interface.
Refer to Annex K of 3GPP TS 29.213 [8] for Diameter load control procedures over the Sy interface.
4.2 Sy Reference model
The Sy reference point is defined between the PCRF and the OCS. The relationships between the involved functional
entities are depicted in figure 4.2.1. The overall PCC architecture is depicted in clause 3a of 3GPP TS 29.213 [8]
Sy
OCS
PCRF
Figure 4.2.1: Sy reference model
.Figure 4.2.2: Void
4.3 Subscriber Spending Limits
Policy decisions based on spending limits is a function that allows the PCRF to make policy decisions based on the
status of policy counters that are maintained in the OCS. The PCRF uses the policy counter statuses received from the
OCS as input to its policy decisions, e.g. downgrade the QoS (e.g. APN-AMBR) or modify the PCC/QoS/ADC Rules.
When the status of policy counters is first required to make a policy decision for a subscriber, the PCRF uses the Initial
Spending Limit Report Request procedure. The PCRF may request specific or all policy counter statuses to be reported
by the OCS for the user. The OCS provides the status to the PCRF of the requested policy counters, and will notify the
PCRF of any changes in the status of those policy counters. Optionally, the OCS can provide one or more pending
statuses for a requested policy counter with the times that have to be applied. The pending status of a policy counter
shall autonomously become the current status of a policy counter at the PCRF when the indicated corresponding time is
reached. Subsequently, the provided information for pending statuses of a policy counter shall overwrite the previously
received information.
NOTE 1: The mechanism for provisioning the policy counters in the OCS is out of scope of this document.
NOTE 2: A policy counter in the OCS can represent the spending for one or more services, one or more devices,
one or more subscribers, etc. The representation is operator dependent. There is no explicit relationship
between Charging-Key and policy counter.
The PCRF may request reporting for specific policy counter(s) that it is not currently subscribed and/or cancel reporting
for specific policy counter status(es) using the Intermediate Spending Limit Report Request. The PCRF may cancel
spending limit reporting for all policy counter(s) using the Final Spending Limit Report Request.
ETSI
3GPP TS 29.219 version 15.3.0 Release 15 9 ETSI TS 129 219 V15.3.0 (2019-10)
The updated subscriber profile may also trigger the PCRF sending the Initial/Intermediate/Final Spending Limit Report
Request to the OCS to subscribed and/or cancel reporting for policy counter status(es). If spending limit reporting for a
policy counter is enabled, the OCS shall notify the PCRF of changes in the status of this policy counter (e.g. daily
spending limit of $2 reached) and optionally pending statuses of this policy counter with the activation time (e.g. due to
a billing period that will expire at midnight).
4.4 Functional elements
4.4.1 PCRF
The Policy Control and Charging Rules Function (PCRF) is a functional element that encompasses policy control
decision and flow based charging control functionalities.
The PCRF may take information on the subscriber's spending status into account in its policy decisions. The PCRF may
request spending limit reporting for policy counters from the OCS using the Initial or Intermediate Spending Limit
Report Request procedure as specified in clause 4.5.1. The PCRF may cancel spending limit reporting for specific
policy counter(s) using the Intermediate Spending Limit Report Request procedure, or for all policy counter(s) using the
Final Spending Limit Report Request procedure as specified in clause 4.5.3.
The PCRF shall have at least one active IP-CAN session to be able to initiate an Sy session to be used when required for
spending limit reporting for that subscriber. The PCRF shall terminate the Sy session when the last IP-CAN session for
that subscriber is terminated or no IP-CAN session for the same user depends on the spending status information
provided over Sy reference point.
The PCRF may use the status of each relevant policy counter as input to its policy decision as required by the decision
logic.
4.4.2 OCS
The Online Charging System (OCS), for the purpose of policy decisions based on the subscriber's spending, shall:
- maintain the policy counter statuses applicable for a subscriber.
- report the policy counter status values for the subscriber when requested to the PCRF.
- when a policy counter status changes, report the change to the PCRF.
4.5 Spending Limits procedures over Sy reference point
4.5.1 Initial/Intermediate Spending Limit Report Request
4.5.1.1 General
This procedure shall be used by the PCRF to request the status of policy counters available at the OCS, and to subscribe
or unsubscribe to updates of policy counters by the OCS.
This procedure is mapped to the Spending-Limit-Request/Answer commands specified in section 5.6.
ETSI
3GPP TS 29.219 version 15.3.0 Release 15 10 ETSI TS 129 219 V15.3.0 (2019-10)
Table 4.5.1.1/1: Initial/Intermediate Spending Limit Report Request
Information element Mapping to Cat. Description
name Diameter AVP
User Identity Subscription-Id, C This IE shall contain the identity of the user. It shall be present in
Logical-Access- the initial request when the SL-Request-Type=INITIAL_REQUEST.
ID AVP, Physical-
Access-ID
(NOTE 1)
Request Type SL-Request-Type M This IE shall indicate whether this is the initial or a subsequent
request for the user.
Subscribed Policy Policy-Counter- O This IE shall indicate the list of policy counter identifiers to be
Counter Identifier List Identifier subscribed to. In the intermediate spending limit report request
procedure, this list overrides a previously provisioned list. If omitted
in either the Initial or Intermediate Spending Limit Report Request
procedures the PCRF requests subscription to all available policy
counters.
NOTE 1: The Logical-Access-ID AVP and Physical-Access-ID AVP are only applicable to Fixed Broadband Access
network convergence as defined in annex A.

Table 4.5.1.1/2: Initial/Intermediate Spending Limit Report Response
Information element Mapping to Cat. Description
name Diameter AVP
Policy Counter Status Policy-Counter- O If present, this information element shall contain a policy counter
Report Status-Report identifier, the current status value and if applicable pending policy
counter statuses with the activation times.
Result Result-Code or
M This IE shall contain the result of the operation.
Experimental-
Result
4.5.1.2 Detailed behaviour of the PCRF
The PCRF shall make use of this procedure when it determines for a subscriber that
- The status of policy counter(s) to which the PCRF does not have an existing subscription for status change
notifications is/are required.
- The status of one or more, but not all, policy counter(s) to which the PCRF has an existing subscription for status
change notifications are no longer required.
NOTE: The Final Spending Limit Request procedure in clause 4.5.3 is used to remove all subscriptions.
In the initial request, i.e. when the request is sent for the first time for the Subscriber, the PCRF shall set the SL-
Request-Type AVP to the value INITIAL_REQUEST (0). For subsequent requests for the same Subscriber, the PCRF
shall set the SL-Request-Type AVP to INTERMEDIATE_REQUEST (1).
For each policy counter that the PCRF requires the current status and notifications of future status changes, the PCRF
shall indicate the concerned policy counter identifiers in the request. Alternatively, the policy counter identifiers may be
omitted if the PCRF requires the current status and notifications of future status changes of all available policy counters.
4.5.1.3 The behaviour of the OCS
Upon reception of the request from the PCRF, the OCS shall check if there is an ongoing Sy session associated with the
received Session-Id AVP. If there is no Sy session and the SL-Request-Type AVP is set to INITIAL_REQUEST (0), an
Sy session is created on the OCS. If there is an Sy session and the SL-Request-Type AVP is not set to
INTERMEDIATE_REQUEST (1), the OCS shall return a response with the Result-Code set to
DIAMETER_INVALID_AVP_VALUE and with the Failed-AVP AVP containing the SL-Request-Type AVP. If there
is no Sy session and the SL-Request-Type AVP is not set to INITIAL_REQUEST (0), the OCS shall return a response
with the Result-Code AVP set to DIAMETER_UNKNOWN_SESSION_ID.
Upon reception of the request from the PCRF provided with explicit Policy Counter Identifier(s):
ETSI
3GPP TS 29.219 version 15.3.0 Release 15 11 ETSI TS 129 219 V15.3.0 (2019-10)
If all the policy counter identifiers are known to the OCS, the OCS shall be able to subsequently notify the PCRF of any
policy counter state changes and/or additions, removal or changes of pending policy counter statuses along with their
activation time.
If a policy counter identifier is known by the OCS, but is not applicable to the subscriber (e.g. not provisioned), the
OCS may use an operator configured policy counter status to indicate this to the PCRF.
If the OCS is configured to accept the request provided with unknown policy counter identifier(s) , and if the OCS
determines that one or more policy counter identifiers are unknown, an operator configured policy counter status may
be used to indicate the policy counter identifier(s) determined as unknown by OCS. The status of known policy counter
identifier(s) shall be returned to the PCRF in the same procedure in this case.
Alternatively, if the OCS is configured to reject the request provided with unknown policy counter identifier(s), and if
the OCS determines that one or more policy counter identifiers are unknown, the OCS shall return a response with the
Experimental-Result-Code AVP set to DIAMETER_ERROR_UNKNOWN POLICY_COUNTERS and with the
Failed-AVP AVP indicating the unknown policy counter identifiers. When this failure occurs, if the SL-Request-Type
AVP is set to:
- INITIAL_REQUEST (0), then the Sy session is not created.
- INTERMEDIATE_REQUEST (1), then none of the changes in the request take effect but the Sy session is
maintained.
NOTE 1: In order to avoid misbehaviors due to the policy counters maintained in the Sy session, the PCRF can
terminate the Sy session invoking the Final Spending Limit Request procedure in clause 4.5.3.
When the PCRF provides a new subscribed policy counter identifier list, the OCS shall remove any policy counter
identifiers no longer in the list from association with the Sy session such that the OCS will no longer notify the PCRF of
those policy counter state changes.
If an initial or intermediate request contains no policy counter identifiers, the OCS shall subsequently notify the PCRF
of all available policy counter state changes and optionally the pending policy counter statuses with the activation times.
If the OCS has no available policy counters for that subscriber during the Initial Spending Limit Report Request
procedure, it sets the Experimental-Result-Code to DIAMETER_ERROR_NO_AVAILABLE_POLICY_COUNTERS.
When this failure occurs, if the SL-Request-Type AVP is set to:
- INITIAL_REQUEST (0), then the Sy session is not created.
- INTERMEDIATE_REQUEST (1), then none of the changes in the request take effect but the Sy session is
maintained.
NOTE 2: The PCRF can terminate the Sy session invoking the Final Spending Limit Request procedure in
clause 4.5.3, or maintain the Sy session assuming that further available policy counters will be notified.
If the user identified in an initial request is not known to the OCS, the OCS shall reject the Spending Limit Report
Request by including the result code of DIAMETER_USER_UNKNOWN in the Spending Limit Report Answer. In
this case, the Sy session is not created.
Upon successful creation of an Sy session, the OCS shall include the current status of all subscribed policy counters (if
any) in the response and set the Result-Code to DIAMETER_SUCCESS.
4.5.2 Spending Limit Report
4.5.2.1 General
This procedure shall be used by the OCS to notify the PCRF of changes in the status of subscribed policy counter(s).
This procedure is mapped to the Spending-Status-Notification-Request /Answer commands specified commands
specified in section 5.6.
ETSI
3GPP TS 29.219 version 15.3.0 Release 15 12 ETSI TS 129 219 V15.3.0 (2019-10)
Table 4.5.2.1/1: Spending Limit Report Request
Information element Mapping to Cat. Description
name Diameter AVP
Policy Counter Status Policy-Counter- M If present, this information element shall contain a policy counter
Report Status-Report identifier, the current status value and if applicable pending policy
counter statuses with the activation times.

Table 4.5.2.1/2: Spending Limit Report Response
Information element Mapping to Cat. Description
name Diameter AVP
Result Result-Code or M This IE shall contain the result of the operation.
Experimental-
Result
4.5.2.2 The behaviour of the OCS
When the status of a specific policy counter changes or when pending statuses associated with the policy counter are
added, removed or changed, the OCS shall determine the Sy sessions impacted by the change (i.e. those Sy sessions that
have subscribed to status change notifications for the changed policy counter) and send a Spending-Status-Notification-
Request command including the current policy counter status, and if applicable pending policy counter statuses with the
activation times to the PCRF associated with each affected Sy session. The OCS shall not send the policy counter status
for the same policy counter until it received the response of the previous status report of the policy counter.
If several policy counters change status at the same time, the OCS may group the status change notifications into a
single Spending-Status-Notification-Request command to the PCRF by sending multiple Policy-Counter-Status-Report
AVPs in the request.
4.5.2.3 Detailed behaviour of the PCRF
The PCRF shall acknowledge the request by sending a response with a Result-Code AVP set to
DIAMETER_SUCCESS and use the status of the received policy counter(s) as input to its policy decision to apply
operator defined actions, e.g. downgrade the QoS.
NOTE: The values related to the status of a policy counter (e.g. valid, invalid or any other status) are not
specified. The interpretation and actions related to the values are out of scope of 3GPP.
The PCRF shall ignore an unknown policy counter status report for all unknown policy counter identifiers in an SLA or
in an SNR from the OCS.
If the PCRF receives an SNR command while it has an ongoing SLR transaction with the OCS, the PCRF shall update
the policy counter information based on the SNR command. When the corresponding SLA command for the ongoing
SLR transaction is eventually received, the PCRF shall only update policy counter information for counters that were
not provided in the previously received SNR command.
If the PCRF receives a Policy-Counter-Status-Report with one or more Pending-Policy-Counter-Information AVPs,
then at the time defined by the Pending-Policy-Counter-Change-Time AVP, the pending Policy-Counter-Status shall
autonomously become the current status of a policy counter. Subsequently provided information for pending statuses of
a policy counter shall overwrite the previously received information. If the pending policy counter statuses are
applicable to a policy counter identifier but the Pending-Policy-Counter-Information AVPs are omitted in the new
policy counter status report, the PCRF shall remove all the pending policy counter statuses.
4.5.3 Final Spending Limit Report Request
4.5.3.1 General
This procedure shall be used by the PCRF to unsubscribe to any future updates of policy counters for a given subscriber
by the OCS.
ETSI
3GPP TS 29.219 version 15.3.0 Release 15 13 ETSI TS 129 219 V15.3.0 (2019-10)
This procedure is mapped to the Session-Termination-Request/Answer commands specified in IETF RFC 6733 [23].
Table 4.5.3.1/1: Final Spending Limit Report Request
Information element Mapping to Cat. Description
name Diameter AVP
Termination Cause Termination- M This IE shall contain the reason why the session was terminated. It
Cause shall be set to "DIAMETER_LOGOUT".

Table 4.5.3.1/2: Final Spending Limit Report Response
Information element Mapping to Cat. Description
name Diameter AVP
Result Result-Code M This IE shall contain the result of the operation.

4.5.3.2 Detailed behaviour of the PCRF
When the PCRF decides that policy decisions for a given user no longer depend on policy counter(s) to which the PCRF
has existing subscriptions for status change notifications, the PCRF shall send the Final Spending Limit Report Request
to the OCS.
4.5.3.3 The behaviour of the OCS
Upon reception of the request from the PCRF, the OCS shall check that there is an ongoing Sy session associated with
the received Session-Id AVP. If there is no Sy session, the OCS shall return a response with the Result-Code AVP set to
DIAMETER_UNKNOWN_SESSION_ID.
The OCS shall remove all policy counter subscriptions associated with the Sy session such that the OCS will no longer
notify the PCRF of policy counter state changes and close the session by returning a response with the Result-Code
AVP set to DIAMETER_SUCCESS.
4.5.4 Sy Session Termination by the OCS
If the ASR feature is supported, and the OCS decides that the Sy session for a subscriber needs to be terminated (e.g.
because subscriber is removed from an OCS system), the OCS shall send the Spending-Status-Notification-Request
(SNR) conaining the SN-Request-Type AVP with bit 1 (Abort Session Request) set to the PCRF.
Upon receipt of the SNR containing the SN-Request-Type AVP with bit 1 set, the PCRF shall acknowledge the receipt
of the SNR by sending the Spending-Status-Notification-Answer (SNA) and shall then send a Final Spending Limit
Report Request as specified in subclause 4.5.3.
NOTE: The termination of the Sy session causes the H-PCRF to make the applicable policy decision and act
accordingly, i.e. sessions on other interfaces such as the Rx or Gx interface will remain established,
unless the policy decision causes their termination.
5 Sy protocol
5.1 Protocol support
5.1.1 Use of Diameter base protocol
The Diameter Base Protocol as specified in IETF RFC 6733 [23] shall apply except as modified by the defined support
of the methods and the defined support of the commands and AVPs, result and error codes as specified in this
specification. Unless otherwise specified, the procedures (including error handling and unrecognised information
handling) shall be used unmodified.
ETSI
3GPP TS 29.219 version 15.3.0 Release 15 14 ETSI TS 129 219 V15.3.0 (2019-10)
With regard to the Diameter protocol defined over the Sy interface, the OCS acts as a Diameter server, in the sense that
it is the network element that handles policy counter status requests for a particular realm. The PCRF acts as the
Diameter client, in the sense that is the network element requesting policy counter status to the OCS.
A Diameter routing table entry can have a different destination based on the application identifier of the command. The
application identifier stored in the command header must match the value of any application identifier AVPs in the
command body. Diameter agents (relay, proxy, redirection, translation agents) should use the application identifier in
the command header to route to a suitable destination.
5.1.2 Void
5.1.3 Accounting functionality
Accounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on
the Sy interface.
5.1.4 Transport protocol
Diameter messages over the Sy interface shall make use of TCP IETF RFC 791 [13] or SCTP IETF RFC 4960 [14].
5.1.5 Advertising Application Support
The Diameter application identifier assigned to the Sy interface application is 16777302.
The PCRF and OCS shall advertise support of the Diameter Sy Application by including the value of the Sy application
identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-
Exchange-Request and Capabilities-Exchange-Answer commands.
The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the Capabilities-
Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-
Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer
commands.
The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is
not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the
Diameter node as per IETF RFC 6733 [23].
5.1.6 Use of the Supported-Features AVP
The Supported-Features AVP is used during session establishment to inform the destination host about the required and
optional features that the origin host supports. The client shall, in the first request in a Diameter session indicate the set
of supported features. The server shall, in the first answer within the Diameter session indicate the set of features that it
has in common with the client and that the server shall support within the same Diameter session. Any further command
messages shall always be compliant with the list of supported features indicated in the Supported-Features AVPs during
session establishment. Features that are not advertised as supported shall not be used to construct the command
messages for that Diameter session. Unless otherwise stated, the use of the Supported-Features AVP on the Sy reference
point shall be compliant with the requirements for dynamic discovery of supported features and associated error
handling on the Cx reference point as defined in clause 7.2.1 of TS 29.229 [15].
The base functionality for the Sy reference p
...