|
TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
LTE;
Policy and charging control over Rx reference point
(3GPP TS 29.214 version 10.15.0 Release 10)
---------------------- Page: 1 ----------------------
3GPP TS 29.214 version 10.15.0 Release 10 1 ETSI TS 129 214 V10.15.0 (2019-01)
Reference
RTS/TSGC-0329214vaf0
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 10.15.0 Release 10 2 ETSI TS 129 214 V10.15.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 10.15.0 Release 10 3 ETSI TS 129 214 V10.15.0 (2019-01)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
2 References . 7
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 9
4 Rx reference point . 9
4.1 Overview . 9
4.2 Rx reference model . 9
4.3 Functional ele me nts . 11
4.3.1 AF . 11
4.3.2 PCRF . 11
4.4 PCC procedures over Rx reference point . 12
4.4.1 Initial Provisioning of Session Information . 12
4.4.2 Modification of Session Information . 14
4.4.3 Gate Related Procedures . 15
4.4.4 AF Session Termination . 16
4.4.5 Subscription to Notification of Signalling Path Status . 16
4.4.5a Provisioning of AF Signalling Flow Information . 17
4.4.6 Traffic Plane Events. 17
4.4.6.1 IP-CAN Session Termination. 17
4.4.6.2 Service Data Flow Deactivation . 17
4.4.6.3 Notification of Signalling Path Status . 18
4.4.6.4 IP-CAN type change Notification . 18
4.4.6.5 Access Network Charging Information Notification. 18
4.4.6.6 Reporting Usage for Sponsored Data Connectivity . 18
5 Rx protocol . 19
5.1 Protocol support . 19
5.2 Initialization, maintenance and termination of connection and session. 19
5.3 Rx specific AVPs . 20
5.3.1 Abort-Cause AVP . 21
5.3.2 Access-Network-Charging-Address AVP . 21
5.3.3 Access-Network-Charging-Identifier AVP . 21
5.3.4 Access-Network-Charging-Identifier-Value AVP . 21
5.3.5 AF-Application-Identifier AVP . 21
5.3.6 AF-Charging-Identifier AVP . 22
5.3.7 Codec-Data AVP . 22
5.3.8 Flow-Description AVP . 22
5.3.9 Flow-Number AVP . 23
5.3.10 Flows AVP. 23
5.3.11 Flow-Status AVP . 23
5.3.12 Flow-Usage AVP . 24
5.3.13 Specific-Action AVP . 24
5.3.14 Max-Requested-Bandwidth-DL AVP . 26
5.3.15 Max-Requested-Bandwidth-UL AVP . 26
5.3.16 Media-Component-Description AVP . 26
5.3.17 Media-Component-Number AVP . 27
5.3.18 Media-Sub-Component AVP . 27
5.3.19 Media-Type AVP . 28
5.3.20 RR-Bandwidth AVP . 28
5.3.21 RS-Bandwidth AVP . 28
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 29.214 version 10.15.0 Release 10 4 ETSI TS 129 214 V10.15.0 (2019-01)
5.3.22 SIP-Forking-Indication AVP . 28
5.3.23 Service-URN AVP . 28
5.3.24 Acceptable-Service-Info AVP . 29
5.3.25 Service-Info-Status-AVP . 29
5.3.26 AF-Signalling-Protocol-AVP . 29
5.3.27 Sponsored-Connectivity-Data AVP . 29
5.3.28 Sponsor-Identity AVP. 30
5.3.29 Application-Service-Provider-Identity AVP . 30
5.3.30 MPS-Identifier AVP . 30
5.3.31 Min-Requested-Bandwidth-DL AVP . 30
5.3.32 Min-Requested-Bandwidth-UL AVP . 30
5.4 Rx re-used AVPs . 30
5.4.1 Use of the Supported-Features AVP on the Rx reference point . 31
5.5 Rx specific Experimental-Result-Code AVP values . 33
5.6 Rx messages . 34
5.6.1 AA-Request (AAR) command . 34
5.6.2 AA-Answer (AAA) command . 34
5.6.3 Re-Auth-Request (RAR) command . 35
5.6.4 Re-Auth-Answer (RAA) command . 35
5.6.5 Session-Termination-Request (STR) command . 36
5.6.6 Session-Termination-Answer (STA) command . 36
5.6.7 Abort-Session-Request (ASR) command . 36
5.6.8 Abort-Session-Answer (ASA) command . 36
Annex A (normative): IMS Related P-CSCF Procedures over Rx . 38
A.1 Provision of Service Information at P-CSCF . 38
A.2 Enabling of IP Flows . 39
A.3 Support for SIP forking . 39
A.3.1 PCC rule provisioning for early media for forked responses . 39
A.3.2 Updating the provisioned PCC rules at the final answer . 40
A.4 Notification of AF Signalling Transmission Path Status . 40
A.5 Indication of Emergency Session . 41
A.6 Notification IP-CAN Type Change . 41
A.7 Support for Early Session disposition SDP . 41
A.7.1 General . 41
A.7.2 Service Information Provisioning for Early Media . 41
A.7.3 Updating the Provisioned Service Information when Dialogue is established . 42
A.8 Provision of Signalling Flow Information at P-CSCF . 42
A.9 Handling of MPS Session. 43
Annex B (normative): Flow identifiers: Format definition and examples . 44
B.1 Format of a flow identifier . 44
B.1.1 General . 44
B.1.2 Derivation of Flow Identifiers from SDP . 45
B.1.2.1 Standard Procedure . 45
B.1.2.2 SDP with "early session" disposition type . 45
B.2 Example 1 . 45
B.3 Example 2 . 46
B.4 Example 3 without media components. 47
B.5 Example 4 . 48
Annex C (informative): Void . 50
Annex D (informative): Change history . 51
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 29.214 version 10.15.0 Release 10 5 ETSI TS 129 214 V10.15.0 (2019-01)
History . 53
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 29.214 version 10.15.0 Release 10 6 ETSI TS 129 214 V10.15.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: 7 ----------------------
3GPP TS 29.214 version 10.15.0 Release 10 7 ETSI TS 129 214 V10.15.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: 8 ----------------------
3GPP TS 29.214 version 10.15.0 Release 10 8 ETSI TS 129 214 V10.15.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".
[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] 3GPP TS 23.335: "User Data Convergence (UDC); Technical realization and information flows;
Stage 2".
[30] 3GPP TS 29.335: "User Data Convergence (UDC); User Data Repository Access Protocol over the
Ud interface; Stage 3".
[31] 3GPP TS 22.153: "Multimedia Priority Service".
[32] 3GPP TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS) Progressive
Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH) ".
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
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 29.214 version 10.15.0 Release 10 9 ETSI TS 129 214 V10.15.0 (2019-01)
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
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:
AF Application Function
ASP Application Service Provider
AVP Attribute Value Pair
CRF Charging Rules Function
IP-CAN IP Connectivity Access Network
MPS Multimedia Priority Service
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 Quali
...