|
TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
LTE;
Policy and charging control over Rx reference point
(3GPP TS 29.214 version 8.19.0 Release 8)
---------------------- Page: 1 ----------------------
3GPP TS 29.214 version 8.19.0 Release 8 1 ETSI TS 129 214 V8.19.0 (2019-01)
Reference
RTS/TSGC-0329214v8j0
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:
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 only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
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
If you find errors in the present document, please send your comment to one of the following services:
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.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
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.214 version 8.19.0 Release 8 2 ETSI TS 129 214 V8.19.0 (2019-01)
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.
Foreword
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, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
.
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.214 version 8.19.0 Release 8 3 ETSI TS 129 214 V8.19.0 (2019-01)
Contents
Intellectual Property Rights . 2
Foreword . 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 . 8
4 Rx reference point . 8
4.1 Overview . 8
4.2 Rx reference model . 8
4.3 Functional ele me nts . 9
4.3.1 AF . 9
4.3.2 PCRF . 9
4.4 PCC procedures over Rx reference point . 10
4.4.1 Initial Provisioning of Session Information . 10
4.4.2 Modification of Session Information . 12
4.4.3 Gate Related Procedures . 12
4.4.4 AF Session Termination . 13
4.4.5 Subscription to Notification of Signalling Path Status . 13
4.4.6 Traffic Plane Events. 13
4.4.6.1 IP-CAN Session Termination. 13
4.4.6.2 Service Data Flow Deactivation . 14
4.4.6.3 Notification of Signalling Path Status . 14
4.4.6.4 IP-CAN type change Notification . 14
4.4.6.5 Access Network Charging Information Notification. 14
5 Rx protocol . 15
5.1 Protocol support . 15
5.2 Initialization, maintenance and termination of connection and session. 15
5.3 Rx specific AVPs . 15
5.3.1 Abort-Cause AVP . 16
5.3.2 Access-Network-Charging-Address AVP . 16
5.3.3 Access-Network-Charging-Identifier AVP . 17
5.3.4 Access-Network-Charging-Identifier-Value AVP . 17
5.3.5 AF-Application-Identifier AVP . 17
5.3.6 AF-Charging-Identifier AVP . 17
5.3.7 Codec-Data AVP . 17
5.3.8 Flow-Description AVP . 18
5.3.9 Flow-Number AVP . 18
5.3.10 Flows AVP. 18
5.3.11 Flow-Status AVP . 19
5.3.12 Flow-Usage AVP . 19
5.3.13 Specific-Action AVP . 19
5.3.14 Max-Requested-Bandwidth-DL AVP . 21
5.3.15 Max-Requested-Bandwidth-UL AVP . 21
5.3.16 Media-Component-Description AVP . 21
5.3.17 Media-Component-Number AVP . 22
5.3.18 Media-Sub-Component AVP . 22
5.3.19 Media-Type AVP . 23
5.3.20 RR-Bandwidth AVP . 23
5.3.21 RS-Bandwidth AVP . 23
5.3.22 SIP-Forking-Indication AVP . 23
5.3.23 Service-URN AVP . 24
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 29.214 version 8.19.0 Release 8 4 ETSI TS 129 214 V8.19.0 (2019-01)
5.3.24 Acceptable-Service-Info AVP . 24
5.3.25 Service-Info-Status-AVP . 24
5.4 Rx re-used AVPs . 24
5.4.1 Use of the Supported-Features AVP on the Rx reference point . 25
5.5 Rx specific Experimental-Result-Code AVP values . 26
5.6 Rx messages . 27
5.6.1 AA-Request (AAR) command . 27
5.6.2 AA-Answer (AAA) command . 27
5.6.3 Re-Auth-Request (RAR) command . 28
5.6.4 Re-Auth-Answer (RAA) command . 28
5.6.5 Session-Termination-Request (STR) command . 29
5.6.6 Session-Termination-Answer (STA) command . 29
5.6.7 Abort-Session-Request (ASR) command . 29
5.6.8 Abort-Session-Answer (ASA) command . 29
Annex A (normative): IMS Related P-CSCF Procedures over Rx . 31
A.1 Provision of Service Information at P-CSCF . 31
A.2 Enabling of IP Flows . 32
A.3 Support for SIP forking . 32
A.3.1 PCC rule provisioning for early media for forked responses . 32
A.3.2 Updating the provisioned PCC rules at the final answer . 33
A.4 Notification of AF Signalling Transmission Path Status . 33
A.5 Indication of Emergency Session . 33
A.6 Notification IP-CAN Type Change . 33
Annex B (normative): Flow identifiers: Format definition and examples . 35
B.1 Format of a flow identifier . 35
B.2 Example 1 . 36
B.3 Example 2 . 37
B.4 Example 3 without media components. 38
B.5 Example 4 . 38
Annex C : Void . 40
Annex D (informative): Change history . 41
History . 43
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 29.214 version 8.19.0 Release 8 5 ETSI TS 129 214 V8.19.0 (2019-01)
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.214 version 8.19.0 Release 8 6 ETSI TS 129 214 V8.19.0 (2019-01)
1 Scope
The present document provides the stage 3 specification of the Rx reference point for the present release. The functional
requirements and the stage 2 specifications of the Rx reference point are contained in 3GPP TS 23.203 [7]. The Rx
reference point lies between the Application Function and the Policy and Charging Rule Function.
Whenever it is possible the present document specifies the requirements for the protocol by reference to specifications
produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined
within the present document.
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 and/or edition number or version number) 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] void
[4] void
[5] 3GPP TS 29.209: "Policy control over Gq interface", latest Rel-6 version.
[6] void
[7] 3GPP TS 29.211: "Rx Interface and Rx/Gx signalling flows", latest Rel-6 version.
[8] 3GPP TS 29.212: "Policy and Charging Control over Gx reference point".
[9] 3GPP TS 29.213: "Policy and Charging Control signalling flows and QoS parameter mapping".
[10] IETF RFC 3588: "Diameter Base Protocol".
[11] IETF RFC 3556: "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control
Protocol (RTCP) Bandwidth".
[12] IETF RFC 4005: "Diameter Network Access Server Application".
[13] IETF RFC 4566: "SDP: Session Description Protocol".
[14] IETF RFC 4006: "Diameter Credit Control Application".
[15] ETSI TS 183 017 v3.2.1: "Telecommunications and Internet Converged Services and Protocols for
Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER protocol for
session based policy set-up information exchange between the Application Function (AF) and the
Service Policy Decision Function (SPDF); Protocol specification".
[16] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[17] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3".
[18] IETF RFC 3264: "An Offer/Answer Model with the Session Description Protocol (SDP)".
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 29.214 version 8.19.0 Release 8 7 ETSI TS 129 214 V8.19.0 (2019-01)
[19] IETF RFC 4566: "SDP: Session Description Protocol".
[20] IETF RFC 3162: "Radius and IPv6".
[21] IETF RFC 5031: "A Uniform Resource Name (URN) for Emergency and Other Well-Known
Services".
[22] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting
packet based services and Packet Data Networks (PDN)".
[23] 3GPP TS 32.240: "Telecommunication management; Charging management; Charging
architecture and principles".
[24] 3GPP TS 32.299: "Telecommunication management; Charging management; Diameter charging
applications".
[25] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol; Protocol details"
[26] 3GPP TS 24.292: "IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS);
Stage 3".
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:
Application Function (AF): element offering application(s) that use IP bearer resources
NOTE: One example of an AF is the P-CSCF of the IM CN subsystem.
AF Session: application level session established by an application level signalling protocol offered by the AF that
requires a session set-up with explicit session description before the use of the service.
NOTE: One example of an application session is an IMS session.
Attribute-Value Pair (AVP): See RFC 3588 [5], corresponds to an Information Element in a Diameter message.
binding: PCRF process of associating IP flows described in AF Service Information with IP-CAN bearers.
IP-CAN bearer: IP transmission path of defined capacity, delay and bit error rate, etc.
See 3GPP TS 21.905 [1] for the definition of bearer.
IP-CAN session: association between a UE and an IP network (for GPRS, APN).
The association is identified by one UE IPv4 address and/or one IPv6 prefix together with a UE identity information, if
available, and a PDN represented by a PDN ID (e.g. an APN). An IP-CAN session incorporates one or more IP-CAN
bearers. Support for multiple IP-CAN bearers per IP-CAN session is IP-CAN specific. An IP-CAN session exists as
long as the related UE IPv4 address and/or IPv6 prefix are assigned and announced to the IP network.
IP flow: unidirectional flow of IP packets with the same source IP address and port number and the same destination IP
address and port number and the same transport protocol
Port numbers are only applicable if used by the transport protocol.
packet flow: A specific user data flow carried through the PCEF. A packet flow can be an IP flow.
PCC rule: set of information enabling the detection of a service data flow and providing parameters for policy control
and/or charging control
service information: set of information conveyed from the AF to the PCRF over the Rx interface to be used as a basis
for PCC decisions at the PCRF, including information about the AF session (e.g. application identifier, type of media,
bandwidth, IP address and port number)
service data flow: An aggregate set of packet flows.
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 29.214 version 8.19.0 Release 8 8 ETSI TS 129 214 V8.19.0 (2019-01)
3.2 Abbreviations
For the purpose of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply:
AF Application Function
AVP Attribute Value Pair
CRF Charging Rules Function
IP-CAN IP Connectivity Access Network
PCC Policy and Charging Control
PCEF Policy and Charging Enforcement Function
PCRF Policy and Charging Rule Function
PDF Policy Decision Function
P-CSCF Proxy-Call Session Control Function
QoS Quality of Service
SDF Service Data Flow
SPR Subscriber Profile Repository
UE User Equipment
4 Rx reference point
4.1 Overview
The Rx reference point is used to exchange application level session information between the Policy and Charging
Rules Function (PCRF) and the Application Function (AF). As defined in the stage 2 specifications
(3GPP TS 23.203 [2]), this information is part of the input used by the PCRF for the Policy and Charging Control
(PCC) decisions. The PCRF exchanges the PCC rules with the Policy and Charging Enforcement Function (PCEF) and
QoS rules with the Bearer Binding and Event Reporting Function (BBERF) as specified in 3GPP TS 29.212 [8].
Signalling flows related to the both Rx and Gx interfaces are specified in 3GPP TS 29.213 [9].
4.2 Rx reference model
The Rx reference point is defined between the PCRF and the AF. The relationships between the different functional
entities involved are depicted in figure 4.1.
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 29.214 version 8.19.0 Release 8 9 ETSI TS 129 214 V8.19.0 (2019-01)
Application
Function
(AF)
Rx
Subscription Sp Policy and
Profile Charging Rules
Repository Function
(SPR)
(PCRF)
Online Charging
Gxx System
Gx
(OCS)
Gy
Service Data Flow
Bearer Binding Policy and
Based Credit
and Event
Charging
Control
Reporting Enforcement
Function Function
(BBERF)
(PCEF)
Offline
Charging
AN-Gateway Gateway
System
(OFCS)
Gz
Figure 4.1: Rx reference point at the Policy and Charging Control (PCC) architecture
NOTE 1: The details associated with the Sp reference point are not specified in this Release. The SPR's relation to
existing subscriber databases is not specified in this Release.
NOTE 2: PCEF is located in the Gateway node implementing the IP access to the PDN. Refer to Annexes of 3GPP
TS 23.203 [2] for application to specific IP-CAN types.
NOTE 3: Refer to Annexes A.5 and H.2 of 3GPP TS 23.203 [2] for application of AN-Gateways.
4.3 Functional elements
4.3.1 AF
The AF is an element offering applications that require the Policy and Charging Control of traffic plane resources
(e.g. UMTS PS domain/GPRS domain resources). One example of an application function is the P-CSCF. The AF shall
use the Rx reference point to provide session information to the PCRF.
NOTE: The AFs may be deployed by the same operator offering the IP-CAN or may be provided by external
third party service provider .
4.3.2 PCRF
The PCRF (Policy Control and Charging Rules Function) is a functional element that encompasses policy control
decision and flow based charging control functionalities. These 2 functionalities are the heritage of the release 6 logical
entities PDF and CRF respectively. The PCRF provides network control regarding the service data flow detection,
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 29.214 version 8.19.0 Release 8 10 ETSI TS 129 214 V8.19.0 (2019-01)
gating, QoS and flow based charging (except credit management) towards the PCEF. The PCRF receives session and
media related information from the AF and informs AF of traffic plane events.
The PCRF may check that the service information provided by the AF is consistent with the operator defined policy
rules before storing the service information. The service information shall be used to derive the QoS for the service. The
PCRF may reject the request received from the AF and as a result the PCRF shall indicate, in the response to the AF,
the service information that can be accepted by the PCRF.
The PCRF may use the subscription information as basis for the policy and charging control decisions. The subscription
information may apply for both session based and non-session based services. The subscription specific information for
each service may contain e.g. max QoS class and max bit rate.
If the AF requests it, the PCRF shall report IP-CAN session events (including bearer event
...