ETSI TS 129 214 V15.7.0 (2019-10)

TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
LTE;
Policy and charging control over Rx reference point
(3GPP TS 29.214 version 15.7.0 Release 15)

3GPP TS 29.214 version 15.7.0 Release 15 1 ETSI TS 129 214 V15.7.0 (2019-10)

Reference
RTS/TSGC-0329214vf70
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.214 version 15.7.0 Release 15 2 ETSI TS 129 214 V15.7.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.214 version 15.7.0 Release 15 3 ETSI TS 129 214 V15.7.0 (2019-10)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 7
1 Scope . 8
2 References . 8
3 Definitions and abbreviations . 10
3.1 Definitions . 10
3.2 Abbreviations . 11
4 Rx reference point . 12
4.1 Overview . 12
4.2 Rx reference model . 12
4.3 Functional ele me nts . 13
4.3.1 AF . 13
4.3.2 PCRF . 13
4.4 PCC procedures over Rx reference point . 14
4.4.1 Initial Provisioning of Session Information . 14
4.4.2 Modification of Session Information . 18
4.4.3 Gate Related Procedures . 21
4.4.4 AF Session Termination . 21
4.4.5 Subscription to Notification of Signalling Path Status . 22
4.4.5a Provisioning of AF Signalling Flow Information . 23
4.4.6 Traffic Plane Events. 23
4.4.6.1 IP-CAN Session Termination. 23
4.4.6.2 Service Data Flow Deactivation . 24
4.4.6.3 Notification of Signalling Path Status . 24
4.4.6.4 IP-CAN type change Notification . 25
4.4.6.5 Access Network Charging Information Notification. 25
4.4.6.6 Reporting Usage for Sponsored Data Connectivity . 25
4.4.6.7 Reporting Access Network Information. 26
4.4.6.8 Temporary Network Failure handling . 26
4.4.6.9 PLMN information change Notification . 27
4.4.7 P-CSCF Restoration Enhancement Support . 27
4.4.8 Priority Sharing Request . 27
4.4.9 Support for media component versioning . 28
4.4.10 Extended bandwidth support for EPC supporting Dual Connectivity (E-UTRAN and 5G NR) . 29
5 Rx protocol . 29
5.1 Protocol support . 29
5.2 Initialization, maintenance and termination of connection and session. 29
5.3 Rx specific AVPs . 30
5.3.0 General . 30
5.3.1 Abort-Cause AVP . 33
5.3.2 Access-Network-Charging-Address AVP . 33
5.3.3 Access-Network-Charging-Identifier AVP . 34
5.3.4 Access-Network-Charging-Identifier-Value AVP . 34
5.3.5 AF-Application-Identifier AVP . 34
5.3.6 AF-Charging-Identifier AVP . 34
5.3.7 Codec-Data AVP . 34
5.3.8 Flow-Description AVP . 35
5.3.9 Flow-Number AVP . 35
5.3.10 Flows AVP. 36
5.3.11 Flow-Status AVP . 36
5.3.12 Flow-Usage AVP . 36
ETSI
3GPP TS 29.214 version 15.7.0 Release 15 4 ETSI TS 129 214 V15.7.0 (2019-10)
5.3.13 Specific-Action AVP . 37
5.3.14 Max-Requested-Bandwidth-DL AVP . 40
5.3.15 Max-Requested-Bandwidth-UL AVP . 40
5.3.16 Media-Component-Description AVP . 40
5.3.17 Media-Component-Number AVP . 42
5.3.18 Media-Sub-Component AVP . 42
5.3.19 Media-Type AVP . 43
5.3.20 RR-Bandwidth AVP . 43
5.3.21 RS-Bandwidth AVP . 43
5.3.22 SIP-Forking-Indication AVP . 43
5.3.23 Service-URN AVP . 43
5.3.24 Acceptable-Service-Info AVP . 44
5.3.25 Service-Info-Status-AVP . 44
5.3.26 AF-Signalling-Protocol-AVP . 44
5.3.27 Sponsored-Connectivity-Data AVP . 44
5.3.28 Sponsor-Identity AVP. 45
5.3.29 Application-Service-Provider-Identity AVP . 45
5.3.30 MPS-Identifier AVP . 45
5.3.31 Rx-Request-Type AVP . 45
5.3.32 Min-Requested-Bandwidth-DL AVP . 46
5.3.33 Min-Requested-Bandwidth-UL AVP . 46
5.3.34 Required-Access-Info AVP . 46
5.3.35 IP-Domain-Id AVP . 46
5.3.36 GCS-Identifier AVP . 46
5.3.37 Sharing-Key-DL AVP . 46
5.3.38 Sharing-Key-UL AVP . 47
5.3.39 Retry-Interval AVP . 47
5.3.40 Sponsoring-Action AVP . 47
5.3.41 Max-Supported-Bandwidth-DL AVP . 47
5.3.42 Max-Supported-Bandwidth-UL AVP . 47
5.3.43 Min-Desired-Bandwidth-DL AVP . 48
5.3.44 Min-Desired-Bandwidth-UL AVP . 48
5.3.45 MCPTT-Identifier AVP . 48
5.3.45a MCVideo-Identifier AVP . 48
5.3.46 Service-Authorization-Info AVP . 48
5.3.47 Priority-Sharing-Indicator AVP . 48
5.3.48 Media-Component-Status AVP . 49
5.3.49 Content-Version AVP . 49
5.3.50 AF-Requested-Data AVP . 49
5.3.51 Pre-emption-Control-Info AVP . 49
5.3.52 Extended-Max-Requested-BW-DL AVP . 50
5.3.53 Extended-Max-Requested-BW-UL AVP . 50
5.3.54 Extended-Max-Supported-BW-DL AVP . 50
5.3.55 Extended-Max-Supported-BW-UL AVP . 50
5.3.56 Extended-Min-Desired-BW-DL AVP . 50
5.3.57 Extended-Min-Desired-BW-UL AVP . 50
5.3.58 Extended-Min-Requested-BW-DL AVP . 51
5.3.59 Extended-Min-Requested-BW-UL AVP . 51
5.3.60 IMS-Content-Identifier AVP . 51
5.3.61 IMS-Content-Type AVP . 51
5.4 Rx re-used AVPs . 51
5.4.0 General . 51
5.4.1 Use of the Supported-Features AVP on the Rx reference point . 56
5.5 Rx specific Experimental-Result-Code AVP values . 60
5.5.1 Permanent Failures . 60
5.5.2 Transient Failures . 61
5.6 Rx messages . 61
5.6.0 General . 61
5.6.1 AA-Request (AAR) command . 61
5.6.2 AA-Answer (AAA) command . 62
5.6.3 Re-Auth-Request (RAR) command . 63
5.6.4 Re-Auth-Answer (RAA) command . 63
ETSI
3GPP TS 29.214 version 15.7.0 Release 15 5 ETSI TS 129 214 V15.7.0 (2019-10)
5.6.5 Session-Termination-Request (STR) command . 64
5.6.6 Session-Termination-Answer (STA) command . 64
5.6.7 Abort-Session-Request (ASR) command . 65
5.6.8 Abort-Session-Answer (ASA) command . 65
Annex A (normative): IMS Related P-CSCF Procedures over Rx . 66
A.1 Provision of Service Information at P-CSCF . 66
A.2 Enabling of IP Flows . 68
A.2.0 General . 68
A.2.1 Gate control procedures considering the P-Early-Media header field . 68
A.2.2 Gate control procedures based on the configuration in the P-CSCF . 70
A.3 Support for SIP forking . 70
A.3.1 PCC rule provisioning for early media for forked responses . 70
A.3.2 Updating the provisioned PCC rules at the final answer . 71
A.4 Notification of AF Signalling Transmission Path Status . 71
A.5 Indication of Emergency Registration and Session Establishment . 72
A.6 Notification IP-CAN Type Change . 72
A.7 Support for Early Session disposition SDP . 73
A.7.1 General . 73
A.7.2 Service Information Provisioning for Early Media . 73
A.7.3 Updating the Provisioned Service Information when Dialogue is established . 74
A.8 Provision of Signalling Flow Information at P-CSCF . 74
A.9 Handling of MPS Session. 75
A.10 Retrieval of network provided location information . 75
A.10.1 General . 75
A.10.2 Retrieval of network provided location information at originating P-CSCF for inclusion in SIP Request . 75
A.10.3 Retrieval of network provided location information at originating P-CSCF for inclusion in SIP response
confirmation . 76
A.10.4 Retrieval of network provided location information at terminating P-CSCF . 76
A.11 Handling of RAN/NAS release cause values . 77
A.12 Resource Sharing . 77
A.13 Handling of MCPTT priority call . 78
A.13.1 General . 78
A.13.2 Determination of MCPTT priority parameter values . 78
A.14 Notification of PLMN Change . 78
A.15 Handling of MCVideo priority call . 79
A.15.1 General . 79
A.15.2 Determination of MCVideo priority parameter values . 79
A.16 Support for volume based charging of IMS services . 79
Annex B (normative): Flow identifiers: Format definition and examples . 81
B.1 Format of a flow identifier . 81
B.1.1 General . 81
B.1.2 Derivation of Flow Identifiers from SDP . 82
B.1.2.1 Standard Procedure . 82
B.1.2.2 SDP with "early session" disposition type . 82
B.2 Example 1 . 82
B.3 Example 2 . 83
B.4 Example 3 without media components. 84
ETSI
3GPP TS 29.214 version 15.7.0 Release 15 6 ETSI TS 129 214 V15.7.0 (2019-10)
B.5 Example 4 . 85
Annex C (informative): Void . 87
Annex D (normative): Monitoring Related SCEF Procedures over Rx . 88
D.1 Monitoring events support, using SCEF procedures over Rx . 88
Annex E (normative): Interworking with 5GS via Rx interface . 89
E.1 General . 89
E.2 Mapping table for IP-CAN types and Access types . 89
Annex F (informative): Change history . 91
History . 94

ETSI
3GPP TS 29.214 version 15.7.0 Release 15 7 ETSI TS 129 214 V15.7.0 (2019-10)
Foreword
This Technical Specification has been produced by the 3rd 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.214 version 15.7.0 Release 15 8 ETSI TS 129 214 V15.7.0 (2019-10)
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 [2].
The Rx reference point lies between the Application Function (AF) and the Policy and Charging Rule Function (PCRF).
In the 5GS the Rx reference point resides between the AF and the Policy Control Function (PCF) as specified in
3GPP TS 23.501 [55] and 3GPP TS 23.503 [56].
NOTE: Interactions between the PCF and the AF using the 5GS Npcf_PolicyAuthorization service (the N5
reference point) are defined in 3GPP TS 29.514 [57].
The Rx interface which is based on RESTful HTTP and XML is specified in 3GPP TS 29.201 [37].
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 (PCC); Reference points".
[9] 3GPP TS 29.213: "Policy and Charging Control signalling flows and Quality of Service (QoS)
parameter mapping".
[10] Void.
[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".
ETSI
3GPP TS 29.214 version 15.7.0 Release 15 9 ETSI TS 129 214 V15.7.0 (2019-10)
[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)".
[19] Void.
[20] IETF RFC 3162: "Radius and IPv6".
[21] IETF RFC 5031: "A Uniform Resource Name (URN) for Emergency and Other Well-Known
Services".
[22] Void.
[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".
[27] IETF RFC 3959 (December 2004): "The Early Session Disposition Type for the Session Initiation
Protocol (SIP)".
[28] 3GPP TS 23.380: "IMS Restoration Procedures".
[29] Void.
[30] Void.
[31] 3GPP TS 22.153: "Multimedia Priority Service".
[32] Void.
[33] 3GPP TS 29.274: "3GPP Evolved Packet System. Evolved GPRS Tunnelling Protocol for EPS
(GTPv2)".
[34] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting
packet based services and Packet Data Networks (PDN)".
[35] IETF RFC 7683: "Diameter Overload Indication Conveyance".
[36] 3GPP TS 23.468: "Group Services and System Aspects; Group Communication System Enablers
for LTE (GCSE LTE)".
[37] 3GPP TS 29.201: "Representational State Transfer (REST) reference point between Application
Function (AF) and Protocol Converter (PC)".
[38] 3GPP TS 23.003: "Numbering, addressing and identification".
[39] 3GPP TS 29.273: "3GPP EPS AAA interfaces".
[40] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data
networks and applications".
[41] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and
interaction".
ETSI
3GPP TS 29.214 version 15.7.0 Release 15 10 ETSI TS 129 214 V15.7.0 (2019-10)
[42] IETF RFC 5761: "Multiplexing RTP Data and Control Packets on a Single Port".
[43] IETF RFC 7944: "Diameter Routing Message Priority".
[44] Void.
[45] IETF RFC 8101: "IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority
Namespace for Mission Critical Push To Talk service".
[46] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2".
[47] 3GPP TS 29.154: "Service capability exposure functionality over Nt reference point".
[48] IETF RFC 5009: "Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for
Authorization of Early Media".
[49] IETF RFC 3948: "UDP Encapsulation of IPsec ESP Packets".
[50] 3GPP TS 24.302: "Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access
networks; stage 3".
[51] IETF RFC 8583: "Diameter Load Information Conveyance".
[52] IETF RFC 6733: "Diameter Base Protocol".
[53] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions".
[54] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push
To Talk (MCPTT); Stage 2".
[55] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[56] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2".
[57] 3GPP TS 29.514: "5G System; Policy Authorization Service; Stage 3".
[58] 3GPP TS 29.512: "5G System; Session Management Policy Control Service; Stage 3".
[59] 3GPP TS 29.513: "5G System; Policy and Charging Control signalling flows and QoS parameter
mapping; Stage 3".
[60] 3GPP TS 23.280: "Common functional architecture to support mission critical services; Stage 2".
[61] 3GPP TS 23.281: "Functional architecture and information flows to support Mission Critical
Video (MCVideo); Stage 2".
[62] 3GPP TS 24.182: "IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol
specification".
[63] 3GPP TS 24.147: "Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem;
Stage 3".
[64] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; 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.
ETSI
3GPP TS 29.214 version 15.7.0 Release 15 11 ETSI TS 129 214 V15.7.0 (2019-10)
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 ETF RFC 6733 [52], 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.
Bit rate: The number of bits (denoted in units of bits, kbits, etc.) that are conveyed or processed per unit of time. The
bit rate in bit/s can be abbreviated with bps. This specification uses SI (International System of Units) prefixes as unit
prefixes, which strictly refer to the power of 10, and shall not be used for the power of 2. For example, 1 kbit/s
represents 1000 bit/s or 1 Mbit/s represents 1000 kbit/s and so on.
IP-CAN bearer: IP transmission path of defined capacity, delay and bit error rate, etc.
See 3GPP TR 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.
MPS session: A session for which priority treatment is applied for allocating and maintaining radio and network
resources to support the Multimedia Priority Service (MPS). MPS is defined in 3GPP TS 22.153 [31].
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.
RESTful HTTP: is an architectural style consisting of a coordinated set of architectural constraints applied to
components, connectors, and data elements, within a distributed hypermedia system applied to the development of web
services.
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.
3.2 Abbreviations
For the purpose of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply:
5GS 5G System
ADC Application Detection and Control
AF Application Function
AS Application Server
ASP Application Service Provider
AVP Attribute Value Pair
CRF Charging Rules Function
DRMP Diameter Routing Message Priority
DSCP Differentiated Services Code Point
GCS Group Communication Service
GCS AS Group Communication Service Application Server
IP-CAN IP Connectivity Access Network
MPS Multimedia Priority Service
PCC Policy and Charging Control
ETSI
3GPP TS 29.214 version 15.7.0 Release 15 12 ETSI TS 129 214 V15.7.0 (2019-10)
PCEF Policy and Charging Enforcement Function
PCF Policy Control Function
PCRF Policy and Charging Rule Function
PDF Policy Decision Function
P-CSCF Proxy-Call Session Control Function
PSAP Public Safety Answering Point
RCAF RAN Congestion Awareness Function
QoS Quality of Service
SCEF Service Capability Exposure Function
SCS Service Capability Server
SDF Service Data Flow
SMF Session Management Function
SPR Subscriber Profile Repository
TDF Traffic Detection Function
UDC User Data Convergence
UE User Equipment
UDR User Data Repository
XML Extensible Markup Language
4 Rx reference point
4.1 Overview
The Rx reference point is used to exchange application level session information:
- and the Application Function (AF); and
- in the 5GS, between the Policy Control Function (PCF) 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
...