ETSI TS 129 217 V15.1.0 (2019-10)

TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
LTE;
Policy and Charging Control (PCC);
Congestion reporting over Np reference point
(3GPP TS 29.217 version 15.1.0 Release 15)

3GPP TS 29.217 version 15.1.0 Release 15 1 ETSI TS 129 217 V15.1.0 (2019-10)

Reference
RTS/TSGC-0329217vf10
Keywords
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.217 version 15.1.0 Release 15 2 ETSI TS 129 217 V15.1.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.217 version 15.1.0 Release 15 3 ETSI TS 129 217 V15.1.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 Np reference point . 7
4.1 Overview . 7
4.2 Np reference model . 8
4.3 Functional ele me nts . 8
4.3.1 RCAF . 8
4.3.2 PCRF . 9
4.3.3 H-PCRF . 9
4.3.4 V-PCRF . 9
4.4 Procedures over Np reference point . 9
4.4.1 RUCI Report . 9
4.4.1.1 General . 9
4.4.1.2 Non-aggregated RUCI report . 10
4.4.1.3 Aggregated RUCI report . 10
4.4.2 Reporting Restriction Provisioning . 10
4.4.3 UE mobility between RCAFs . 11
4.4.4 Removal of UE context . 11
4.4.5 Race condition handling . 12
5 Np protocol . 12
5.1 Protocol support . 12
5.2 Initialization, maintenance and termination of connection and session. 12
5.3 Np specific AVPs . 13
5.3.1 General . 13
5.3.2 Aggregated-Congestion-Info AVP . 13
5.3.3 Aggregated-RUCI-Report AVP . 13
5.3.4 Congestion-Level-Definition AVP . 14
5.3.5 Congestion-Level-Range AVP . 14
5.3.6 Congestion-Level-Set-Id AVP . 14
5.3.7 Congestion-Level-Value AVP . 14
5.3.8 Congestion-Location-Id AVP . 15
5.3.9 Conditional-Restriction AVP . 15
5.3.10 eNodeB-Id AVP . 15
5.3.11 IMSI-List AVP . 15
5.3.12 RCAF-Id AVP . 16
5.3.13 Reporting-Restriction AVP . 16
5.3.14 RUCI-Action AVP . 16
5.3.15 Extended-eNodeB-Id AVP . 17
5.4 Np re-used AVPs . 17
5.4.1 General . 17
5.4.2 Use of the Supported-Features AVP on the Np reference point . 18
5.5 Np specific Experimental-Result-Code AVP values . 19
5.5.1 General . 19
5.5.2 Success . 19
5.5.3 Permanent Failures . 19
5.5.4 Transient Failures . 19
ETSI
3GPP TS 29.217 version 15.1.0 Release 15 4 ETSI TS 129 217 V15.1.0 (2019-10)
5.6 Np messages . 19
5.6.0 Command-Code Values . 19
5.6.1 Non-Aggregated-RUCI-Report-Request (NRR) command . 20
5.6.2 Non-Aggregated-RUCI-Report-Answer (NRA) command . 20
5.6.3 Aggregated-RUCI-Report-Request (ARR) command . 21
5.6.4 Aggregated-RUCI-Report-Answer (ARA) command . 21
5.6.5 Modify-Uecontext-Request (MUR) command . 21
5.6.6 Modify-Uecontext-Answer (MUA) command . 22
Annex A (informative): Change history . 23
History . 24

ETSI
3GPP TS 29.217 version 15.1.0 Release 15 5 ETSI TS 129 217 V15.1.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.217 version 15.1.0 Release 15 6 ETSI TS 129 217 V15.1.0 (2019-10)
1 Scope
The present document provides the stage 3 specification of the Np reference point. The functional requirements and the
stage 2 specifications of the Np reference point are contained in 3GPP TS 23.203 [2]. The Np reference point lies
between the RAN Congestion Awareness Function (RCAF) and the Policy and Charging Rules Function (PCRF) for the
non-roaming case, between the RCAF and the H-PCRF for the home-routed scenario and between the RCAF and the V-
PCRF for the visited access scenario.
NOTE: If not specified explicitly, the PCRF also means H-PCRF for the home-routed scenario or V-PCRF in the
visited access scenario in the specification.
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 and charging control architecture".
[3] 3GPP TS 29.213: "Policy and Charging Control signalling flows and QoS parameter mapping".
[4] IETF RFC 4005: "Diameter Network Access Server Application".
[5] IETF RFC 4006: "Diameter Credit Control Application".
[6] 3GPP TS 29.229: "Cx and Dx interfaces based on Diameter protocol; Protocol details".
[7] IETF RFC 3588: "Diameter Base Protocol".
[8] 3GPP TS 23.401: "GPRS enhancements for E-UTRAN access".
[9] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[10] 3GPP TS 29.215: "Policy and Charging Control (PCC) over S9 reference point; Stage 3".
[11] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting
packet based services and Packet Data Networks (PDN)".
[12] 3GPP TS 29.274: "3GPP Evolved Packet System. Evolved GPRS Tunnelling Protocol for EPS
(GTPv2)".
[13] ITU-T Recommendation E.212: "The international identification plan for mobile terminals and
mobile users".
[14] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points".
[15] IETF RFC 7683: "Diameter Overload Indication Conveyance".
[16] IETF RFC 7944: "Diameter Routing Message Priority".
[17] IETF RFC 8583: "Diameter Load Information Conveyance".
[18] IETF RFC 6733: "Diameter Base Protocol".
ETSI
3GPP TS 29.217 version 15.1.0 Release 15 7 ETSI TS 129 217 V15.1.0 (2019-10)
[19] IETF RFC 5719: "Updated IANA Considerations for Diameter Command Code Allocations".
[20] IETF RFC 2234: "Augmented BNF for syntax specifications".
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].
Home Routed Access: Roaming scenario where the PCEF is located in the HPLMN. In a Home Routed roaming
scenario, the UE obtains access to the packet data network from the HPLMN.
RAN user plane congestion: RAN user plane congestion occurs when the demand for RAN resources exceeds the
available RAN capacity to deliver the user data for a prolonged period of time.
NOTE: Short-duration traffic bursts is a normal condition at any traffic load level, and is not considered to be
RAN user plane congestion. Likewise, a high-level of utilization of RAN resources (based on operator
configuration) is considered a normal mode of operation and might not be RAN user plane congestion.
Visited Access (also known as local breakout): Roaming scenario where the PCEF is located in the VPLMN. In a
Visited Access Roaming scenario, the UE obtains access to the packet data network from the VPLMN.
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].
AF Application Function
ARR Aggregated RUCI Report Request
ARA Aggregated RUCI Report Answer
DRMP Diameter Routing Message Priority
H-PCRF Home PCRF
MUR Modify Uecontext Request
MUA Modify Uecontext Answer
NRR Non-Aggregated RUCI Report Request
NRA Non-Aggregated RUCI Report Answer
PCC Policy and Charging Control
PCRF Policy and Charging Rule Function
RCAF RAN Congestion Awareness Function
RUCI RAN User Plane Congestion Information
V-PCRF Visited PCRF
4 Np reference point
4.1 Overview
The Np reference point is located between the RCAF and the PCRF for the non-roaming scenario, between the RCAF
and the H-PCRF for the home-routed scenario and between the RCAF and the V-PCRF for the visited access scenario.
The Np reference point is used for:
- Reporting the RUCI from the RCAF to the PCRF;
- Provisioning the Reporting Restriction from the PCRF to the RCAF;
ETSI
3GPP TS 29.217 version 15.1.0 Release 15 8 ETSI TS 129 217 V15.1.0 (2019-10)
- The User Equipment (UE) mobility between RCAFs;
- The removal of the UE context in the RCAF.
The stage 2 level requirements for the Np reference point are defined in 3GPP TS 23.203 [2].
Signalling flows related to Np interface are specified in 3GPP TS 29.213 [3].
Refer to Annex G of 3GPP TS 29.213 [3] for Diameter overload control procedures over the Np interface.
Refer to Annex J of 3GPP TS 29.213 [3] for Diameter message priority mechanism procedures over the Np interface.
Refer to Annex K of 3GPP TS 29.213 [3] for Diameter load control procedures over the Np interface.
4.2 Np reference model
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 [3] .
Np
RCAF PCRF
Figure 4.2.1: Np reference model
NOTE: For the home-routed access scenario, the RCAF interacts with the H-PCRF. For the visited access
scenario, the RCAF interacts with the V-PCRF.
Figure 4.2.2: Void
Figure 4.2.3: Void
4.3 Functional elements
4.3.1 RCAF
The RCAF is a functional element which reports RAN User Plane Congestion Information (RUCI) via the Np interface
to the PCRF to enable the PCRF to take the RAN user plane congestion status into account for policy decisions. RUCI
includes the following information:
- The user id (e.g. IMSI) identifying the UE impacted by congestion;
- PDN ID for which congestion information is reported;
- Congestion level information (either congestion level value or congestion level set id) of the UE impacted by
congestion;
- eNodeB identifier, ECGI or SAI identifying the eNodeB, E-UTRAN cell or Service Area respectively, serving
the UE if a conditional restriction to restrict location reporting is not enabled.
NOTE 1: In case of E-UTRAN, whether the eNodeB identifier or the ECGI are included in the RUCI is up to
operator configuration in the RCAF.
The RCAF sends the RUCI to the PCRFs serving the UEs' PDN connections as follows:
- For a PDN connection in a non-roaming scenario the RCAF reports the RUCI to the PCRF;
- For a PDN connection in a local breakout scenario, based on operator configuration, the RCAF reports the RUCI
to the V-PCRF;
ETSI
3GPP TS 29.217 version 15.1.0 Release 15 9 ETSI TS 129 217 V15.1.0 (2019-10)
- For a PDN connection in a home routed scenario, based on the roaming agreement with the HPLMN and
operator configuration, the RCAF reports the RUCI to the H-PCRF
NOTE 2: Reporting of congestion information to the HPLMN may be used e.g. in case of a group of PLMNs which
belong to a single business entity.
The RCAF determines whether a given PDN connection is served in a local breakout or a home routed roaming
scenario based on the APN operator identifier received as part of the APN information from the MME or the SGSN as
documented in 3GPP TS 23.401 [8] and 3GPP TS 23.060 [9], respectively.
NOTE 3: Operator configuration can be used to limit RUCI reporting on the Np interface to certain APNs only.
The RCAF maintains a context per user id and APN. The context is identified by the IMSI and the APN. It contains the
following information:
- The previously reported congestion level over the Np reference point;
- The reporting restrictions received from the PCRF. The reporting restrictions are stored by the RCAF until the
PCRF explicitly signals to remove the reporting restrictions.
- The logical PCRF id received from the PCRF to identify the PCRF that is the Np destination for the RCAF when
sending aggregate messages.
4.3.2 PCRF
The PCRF is a functional element that encompasses policy control decision and flow based charging control
functionalities.
The PCRF may receive RUCI from the RCAF as input for policy decisions of congestion mitigation. The PCRF may
provide, update or remove the reporting restrictions of RUCI, or stop or enable RUCI reporting for a given user id and
PDN ID. The PCRF may enable or disable the reporting of congestion location identifier as part of RUCI. The PCRF
may also remove the context at the RCAF for a given user id and PDN ID.
NOTE: Depending on the RUCI reporting interval configured in the RCAF, a UE can move outside the area
indicated without the RCAF immediately notifying the PCRF. In case the PCRF receives information
about the cell currently serving a UE via Np and Gx when the location change reporting is enabled, then
the information received via Gx is expected to take precedence.
4.3.3 H-PCRF
Functionality defined in clause 4.3.2 shall apply if UE is roaming with home-routed access scenario.
NOTE: Reporting of congestion information to the HPLMN can be used e.g. in case of a group of PLMNs which
belong to a single business entity.
4.3.4 V-PCRF
Functionality defined in clause 4.3.2 shall apply if UE is roaming with visited access scenario.
4.4 Procedures over Np reference point
4.4.1 RUCI Report
4.4.1.1 General
The RCAF shall perform the RUCI reporting to the PCRF when at least one of the following conditions applies:
- the RCAF detects a UE in the congestion area for the first time;
- a reporting restriction is enabled and the congestion level set id is changed;
ETSI
3GPP TS 29.217 version 15.1.0 Release 15 10 ETSI TS 129 217 V15.1.0 (2019-10)
- a reporting restriction is not enabled and the congestion level value is changed;
- a conditional restriction to restrict location reporting is not enabled and the UE is in a congested area and the
location is changed; or
- the RCAF detects that the UE is no longer experiencing congestion (i.e. the UE is no longer detected in any of
the congested cells that the RCAF is monitoring).
The RCAF shall report the RUCI to the PCRF unless the RUCI reporting is disabled for the PDN ID or for the user id
and the PDN ID.
Two types of RUCI reports may be used on Np for transfer of congestion information from RCAF to PCRF: Non-
aggregated RUCI report and Aggregated RUCI report. If the RCAF does not know the destination PCRF for the user id
and PDN ID, the Non-aggregated RUCI report shall be used; otherwise the RCAF may use either the Non-aggregate
RUCI report or Aggregated RUCI report for the user id and PDN ID.
4.4.1.2 Non-aggregated RUCI report
For a Non-aggregated RUCI report, the RCAF shall send an NRR command to the PCRF by including the user id
within the Subscription-Id AVP, PDN ID within the Called-Station-Id AVP and a congestion level set id within the
Congestion-Level-Set-Id AVP if the reporting restriction was provided earlier or a congestion level value within the
Congestion-Level-Value AVP if the reporting restriction was not provided earlier at the command level. The RCAF
may also provide congestion location identifier of the UE within the Congestion-Location-Id AVP in the NRR
command. The RCAF shall also include the RCAF Identity within the RCAF-Id AVP in every NRR command for a
specific user id and PDN ID.
Once the PCRF receives the NRR command, the PCRF shall store the related info and respond with an NRA command
including the PCRF id within the PCRF-Address AVP. The PCRF may use the RUCI received from the RCAF as input
for policy decisions. When the RCAF receives the NRA command, the RCAF may store the PCRF id in the UE context
for this specific user id together with PDN ID for further aggregated RUCI report.
If the ReportRestriction feature is supported by both the RCAF and the PCRF, the PCRF may provide reporting
restrictions in the NRA command according to clause 4.4.2.
4.4.1.3 Aggregated RUCI report
For an Aggregated RUCI report, the RCAF shall aggregate the RUCIs of different user ids and PDN IDs that have the
same destination PCRF. The RCAF shall send an ARR command to the destination PCRF by including the PCRF id
within the Destination-Host AVP, one or more Aggregated-RUCI-Report AVP with a congestion level set id within the
Congestion-Level-Set-Id AVP if the reporting restriction was provided earlier or a congestion level value within the
Congestion-Level-Value AVP if the reporting restriction was not provided earlier, the PDN ID within the Called-
Station-ID AVP and a list of aggregated congestion information within the Aggregated-Congestion-Info AVP.
NOTE 1: Each instance of Aggregated-RUCI-Report AVP aggregates the user id list of the subscribers that share
the same level of congestion or share the same congestion level set id.
NOTE 2: When the RCAF assembles a Diameter ARR command, if the message length of ARR command has
exceeded the maximum length of Diameter message which can be configurable, the RCAF can divide the
original ARR command into multiple aggregated RUCI messages for the delivery over Np reference
point.
Once the PCRF receives the ARR command, the PCRF shall store the related info and respond with an ARA command.
The PCRF may use the RUCI received from the RCAF as input for policy decisions.
4.4.2 Reporting Restriction Provisioning
If the ReportRestriction feature is supported by both the RCAF and the PCRF, the PCRF may provide the reporting
restrictions for a specific user id and PDN ID in the initial NRA command. The PCRF may also provide, modify or
disable restrictions for RUCI reporting or stop or enable RUCI reporting for the specific user id and PDN ID at any later
time. The PCRF may also use this procedure to enable or disable the reporting of congestion location identifier as part
of RUCI.
ETSI
3GPP TS 29.217 version 15.1.0 Release 15 11 ETSI TS 129 217 V15.1.0 (2019-10)
In order to initially provide the reporting restrictions, the PCRF shall send a Modify-Uecontext-Request (MUR)
command including the targeted Subscription-Id AVP indicating the user id, the Called-Station-Id AVP indicating the
targeted PDN ID and one or more Congestion-Level-Definition AVP(s) including the defined congestion level set
within the Congestion-Level-Set-Id AVP and corresponding congestion level(s) within the Congestion-Level-Range
AVP or reply with an NRA command including one or more Congestion-Level-Definition AVP(s) including the defined
congestion level set within the Congestion-Level-Set-Id AVP and corresponding congestion level(s) within the
Congestion-Level-Range AVP . The PCRF may also include the Reporting-Restriction AVP and Conditional-
Restriction AVP to indicate when conditional reporting restrictions apply.
The PCRF may modify already provided reporting restrictions. To do so the PCRF shall provide the complete list of
congestion level sets and corresponding congestion levels to be used in the same manner as when initially providing
reporting restrictions. This complete list shall replace any previously provided list. The absence of Reporting-
Restriction AVP and Conditional-Restriction AVP indicates that previous state of reporting restrictions remains valid.
If reporting restrictions has been provided for a specific user id and PDN ID, the PCRF may remove the reporting
restrictions by, in the MUR command, including the Reporting-Restriction AVP set to 0 (No reporting restriction),
together with Subscription-Id AVP indicating the user id and the Called-Station-Id AVP indicating the targeted PDN ID
or reply with an NRA command including the Reporting-Restriction AVP set to 0 (No reporting restriction).
The PCRF may disable RUCI reporting by, in the MUR command, including the RUCI-Action AVP set to 0 (Disable
RUCI Reporting), together with Subscription-Id AVP indicating the user id and the Called-Station-Id AVP indicating
the targeted PDN ID or reply with an NRA command including the RUCI-Action AVP set to 0 (Disable RUCI
Reporting).
To enable RUCI Reporting if previously disabled, the PCRF in the MUR command shall include the RUCI-Action AVP
set to1 (Enable RUCI Reporting), together with Subscription-Id AVP indicating the user id and the Called-Station-Id
AVP indicating the targeted PDN ID or reply with an NRA command including the RUCI-Action AVP set to 1 (Enable
RUCI Reporting).
If reporting restrictions also applies, the PCRF shall include one or more Congestion-Level-Definition AVP(s)
including the defined congestion level set with the Congestion-Level-Set-Id AVP and corresponding congestion level(s)
within the Congestion-Level-Range AVP, within the same command.
To provision the reporting restriction which disables the reporting of congestion location identifier of the UE as part of
RUCI, the PCRF shall include Reporting-Restriction AVP set to 1 (Conditional reporting restriction) and Conditional-
Restriction AVP with the bit 0 be set. To enable a previously disabled reporting of the congestion location identifier of
the UE as part of RUCI, the PCRF shall include Reporting-Restriction AVP set to 2 (Unconditional reporting
restriction).
The PCRF shall include the value of the RCAF-Id AVP received in the NRR command for the specific user id and PDN
ID in the Destination-Host AVP of the MUR command.
The RCAF acknowledges the received MUR command by sending a Modify-Uecontext-Answer (MUA) command in
all cases above.
4.4.3 UE mobility between RCAFs
If RUCI reporting is used for a specific user id and PDN ID and the PCRF receives a new non-aggregated RUCI report
for the same user id and PDN ID but with a different RCAF id included in the RCAF-Id AVP, the PCRF shall update
the related information and respond with an NRA command according to clause 4.4.1.1.
The PCRF shall also initiate a removal of the UE context to the old RCAF according to clause 4.4.4.
4.4.4 Removal of UE context
This procedure is initiated when the PCRF needs to remove a UE context from the RCAF, e.g. at UE mobility between
RCAFs.
If the PCRF due to an event determines that a UE context needs to be removed from the RCAF, the PCRF shall send an
MUR command to the targeted RCAF to explicitly release the context related to the user id and PDN ID by including
the Subscription-Id AVP indicating the user id, the Called-Station-Id AVP indicating the PDN ID, the Destination-Host
AVP indicating the targeted RCAF id and the RUCI-Action AVP set to 2 (Release Context).
ETSI
3GPP TS 29.217 version 15.1.0 Release 15 12 ETSI TS 129 217 V15.1.0 (2019-10)
The RCAF when receiving the MUR command from the PCRF shall release the context related to the user id and PDN
ID. If this is the last PDN ID stored for this user id the RCAF shall release the complete context.
The RCAF shall acknowledge the received MUR command by sending an MUA command.
4.4.5 Race condition handling
If the RCAF receives an MUR command to remove a context for a specific user id and PDN ID, the request shall be
handled immediately, regardless of whether there are any ongoing RUCI report transactions for that user id and PDN
ID.
If the PCRF receives an NRR command for a specific user id and PDN ID, and if there is an ongoing MUR command to
remove the context for that user id and PDN ID, the PCRF shall reject the incoming request with a Diameter
experimental result code of DIAMETER_PENDING_TRANSACTION.
If the PCRF receives an ARR command for specific user id and PDN ID combinations for which there is at least one
ongoing MUR command to remove the context, the PCRF shall accept the request and only update the context(s) that
are not in the process of being removed.
5 Np protocol
5.1 Protocol support
The Np application is defined as a vendor specific Diameter application, where the vendor is 3GPP and the Application-
ID for the Np Application in the present release is 16777342. The vendor identifier assigned by IANA to 3GPP
(http://www.iana.org/assignments/enterprise-numbers) is 10415.
NOTE: A route entry can have a different destination based on the application identification AVP of the message.
Therefore, Diameter agents (relay, proxy, redirection, translation agents) must be configured
appropriately to identify the 3GPP Np application within the Auth-Application-Id AVP in order to create
suitable routeing tables.
With regard to the Diameter protocol defined over the Np interface, the PCRF acts as a Diameter server, in the sense
that it is the network element that handles the RUCI reporting for a particular realm. The RCAF acts as the Diameter
client, in the sense that it is the network element reporting the RUCI.
5.2 Initialization, maintenance and termination of connection
and session
The initialization and maintenance of the connection between the RCAF and PCRF are defined by the underlying
protocol. Establishment and maintenance of connections between Diameter nodes are described in
IETF RFC 6733 [18].
After establishing the transport connection, the RCAF and the PCRF shall advertise the support of the Np specific
Application by including the value of the application identifier in the Auth-Application-Id AVP and the value of the
3GPP (10415) in the Vendor-Id AVP of the Vendor-Specific-Application-Id AVP contained in the
Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. The Capabilities-Exchange-Request
and Capabilities-Exchange-Answer commands are specified in the Diameter Base Protocol (IETF RFC 6733 [18]).
The Np Diameter session shall be terminated after each request and answer pair interaction.
In order to indicate that the session state is not to be maintained, the Diameter client and server shall include the Auth-
Session-State AVP with the value set to NO_STATE_MAINTAINED (1), in the request and in the answer messages
(see IETF RFC 6733 [18]).
ETSI
3GPP TS 29.217 version 15.1.0 Release 15 13 ETSI TS 129 217 V15.1.0 (2019-10)
5.3 Np specific AVPs
5.3.1 General
Table 5.3.1.1 describes the Diameter AVPs defined for the Np reference point, their AVP Code values, types, possible
flag values, whether or not the AVP may be encrypted and which supported features the AVP is applicable to. The
Vendor-Id header of all AVPs defined in the present document shall be set to 3GPP (10415).
Table 5.3.1.1: Np specific Diameter AVPs
AVP Flag rules
(NOTE 1)
Attribute Name AVP Clause Value Type Mus May Should Must May Applicability
Code defined (NOTE 2) t not not Encr. (NOTE 3)
Aggregated-Congestion-Info 4000 5.3.2 Grouped V, P  Y
M
Aggregated-RUCI-Report 4001 5.3.3 Grouped V, P  Y
M
Congestion-Level-Definition 4002 5.3.4 Grouped V P M Y ReportRestriction
Congestion-Level-Range 4003 5.3.5 Unsigned32 V P M Y ReportRestriction
Congestion-Level-Set-Id 4004 5.3.6 Unsigned32 V P M Y ReportRestriction
Congestion-Level-Value 4005 5.3.7 Unsigned32 V, P  Y
M
Congestion-Location-Id 4006 5.3.8 Grouped V P M Y ReportRestriction
Conditional-Restriction 4007 5.3.9 Unsigned32 V P M Y ReportRestriction
eNodeB-Id 4008 5.3.10 OctetString V, P  Y
M
IMSI-List 4009 5.3.11 OctetString V, P  Y
M
RCAF-Id 4010 5.3.12 DiameterIdentity V, P  Y
M
Reporting-Restriction 4011 5.3.13 Unsigned32 V P M Y ReportRestriction
RUCI-Action 4012 5.3.14 Unsigned32 V P M Y ReportRestriction
Extended-eNodeB-Id 4013 5.3.15 OctetString V, P M Y
NOTE 1: The AVP header bit denoted as 'M', indicates whether support of the AVP is required. The AVP header bit
denoted as 'V', indicates whether the optional Vendor-ID field is present in the AVP header. For further
details, see IETF RFC 6733 [18].
NOTE 2: The value types are defined in IETF RFC 6733 [18].
NOTE 3: AVPs marked with a supported feature (e.g. "ReportRestriction") are applicable as described in
clause 5.4.2.
5.3.2 Aggregated-Congestion-Info AVP
The Aggregated-Congestion-Info AVP (AVP code 4000) is of type Grouped. It contains a list of user ids identified by
IMSI and optionally the congestion location id in which the list of user ids are located.
Aggregated-Congestion-Info ::= < AVP Header: 4000 >
[ Congestion-Location-Id ]
[ IMSI-List ]
*[ AVP ]
5.3.3 Aggregated-RUCI-Report AVP
The Aggregated-RUCI-Report AVP (AVP code 4001) is of type Grouped, and it is used to contain the congestion level
value or congestion level set id for a set of users which have the same PCRF for the same PDN ID.
The congestion-Level-Value AVP contains the congestion level value if the PCRF did not provide the reporting
restriction earlier for the user id and PDN ID.
The Congestion-Level-Set-Id AVP contains the congestion level set identifier between the PCRF and the RCAF if the
PCRF provided the reporting restriction earlier for the user id and PDN ID.
ETSI
3GPP TS 29.217 version 15.1.0 Release 15 14 ETSI TS 129 217 V15.1.0 (2019-10)
The Called-Station-Id AVP contains the PDN ID.
The Aggregated-Congestion-Info AVP shall indicate the list of users included in the IMSI-List AVP and the congested
location included in the Congestion-Location-Id AVP (if applicable), where a congestion level included in the
Congestion-Level-Value AVP or congestion level set included in the Congestion-Level-Set-Id AVP shall apply.
Aggregated-RUCI-Report ::= < AVP Header: 4001 >
1*{ Aggregated-Congestion-Info }
[ Called-Station-Id ]
[ Congestion-Level-Value ]
[ Congestion-Level-Set-Id ]
*[ AVP ]
5.3.4 Congestion-Level-Definition AVP
The Congestion-Level-Definition AVP (AVP code 4002) is of type Grouped, and it is used to define a congestion level
set and corresponding congestion level(s) to be used by the RCAF for a specific user id and PDN ID at congestion
reporting. When this AVP is present in the MUR command reporting restrictions apply, when this AVP is absent there
are no reporting restriction for the specific user id and PDN ID.
Congestion-Level-Definition ::= < AVP Header: 4002 >
{ Congestion-Level-Set-Id }
{ Congestion-Level-Range }
*[ AVP ]
5.3.5 Congestion-Level-Range AVP
The Congestion-Level-Range AVP (AVP code 4003) is of type Unsigned32, and it is used to indicate the list of
congestion level(s) bound to a certain congestion level set, between the PCRF and the RCAF. The Congestion-Level-
Range AVP shall contain a bit mask. The bit 0 shall be the least significant bit. For example, to get the value of bit 0, a
bit mask of 0x0001 should be used. The meaning of the bits shall be as defined below:
Table 5.3.5.1: Congestion Level Range
Bit Name Description
0 No congestion This bit, when set, indicates that the RCAF shall report the
corresponding congestion level set id to the PCRF when there is
no congestion for a certain user id and PDN ID.

1 Congestion level 1 This bit, when set, indicates that the RCAF shall report the
corresponding congestion level set id to the PCRF when
congestion level 1 is reached for a certain user id and PDN ID.
1+n Congestion level This bit, when set, indicates that the RCAF shall report the
1+n corresponding congestion level set id to the PCRF when
congestion level 1+n is reached
...