|
TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
LTE;
Representational State Transfer (REST)
reference point between Application Function (AF)
and Protocol Converter (PC)
(3GPP TS 29.201 version 15.0.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 29.201 version 15.0.0 Release 15 1 ETSI TS 129 201 V15.0.0 (2018-07)
Reference
RTS/TSGC-0329201vf00
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 2018.
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 protected for the benefit of its Members.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 29.201 version 15.0.0 Release 15 2 ETSI TS 129 201 V15.0.0 (2018-07)
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.201 version 15.0.0 Release 15 3 ETSI TS 129 201 V15.0.0 (2018-07)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 7
4 Representational State Transfer (REST) reference point based on Protocol Converter (PC)
architecture . 7
4.1 Overview . 7
4.2 Reference model . 8
4.3 Functional ele me nts . 8
4.3.1 Application function . 8
4.3.2 Protocol converter . 8
4.4 Location of the PC within the PLMN . 9
4.4.1 General . 9
4.4.2 Protocol converter located in the PLMN but outside of the PCRF realm . 9
4.4.3 Protocol converter located in the PCRF realm . 9
4.5 PCC Procedures over the RESTful reference point . 10
4.5.1 General . 10
4.5.2 Initial Provisioning of Session Information . 10
4.5.3 Modification of Session Information . 11
4.5.4 AF Session Termination . 12
4.5.5 Gate Related Procedures . 12
4.5.6 Subscription to Notification of Signalling Path Status . 12
4.5.7 Traffic Plane Events. 13
5 Protocol . 13
5.1 Introduction . 13
5.2 Transport layer . 14
5.3 Application delivery layer . 14
5.3.1 Methods . 15
5.3.2 Void . 15
5.3.3 Resources and URI design . 15
5.3.4 HTTP request/response dialogues . 16
5.3.5 AF Session ID . 17
5.4 Specific application communication . 18
5.4.0 General . 18
5.4.1 Content type XML . 18
5.4.1.1 XML schema . 18
5.4.1.2 Data types and mapping between XML elements . 18
5.4.1.3 Mapping between Diameter AVPs and XML elements and groups . 18
5.5 PC discovery . 21
6 Routing . 21
6.1 PC located in the PLMN but outside of the PCRF realm . 21
6.2 PC located in the PCRF realm . 21
7 Secure communication . 22
Annex A (informative): Call Flows . 23
A.1 General . 23
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 29.201 version 15.0.0 Release 15 4 ETSI TS 129 201 V15.0.0 (2018-07)
A.2 AF session establishment . 23
A.3 AF Session Modification Initiated by AF . 23
A.4 AF Session Termination . 24
A.5 Gate Related Procedures . 24
A.6 Subscription to Notification of Signalling Path Status . 25
A.7 Notification of Traffic Plane Events . 25
A.7.1 Traffic plane event reporting . 25
A.7.2 Service data flow deactivation when all service data flows are affected . 26
A.7.3 IP-CAN Session Termination . 27
Annex B (normative): XML Schema . 29
B.1 XML elements and groups . 29
B.2 Diameter message representation . 32
Annex C (informative): Change history . 36
History . 37
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 29.201 version 15.0.0 Release 15 5 ETSI TS 129 201 V15.0.0 (2018-07)
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
---------------------- Page: 6 ----------------------
3GPP TS 29.201 version 15.0.0 Release 15 6 ETSI TS 129 201 V15.0.0 (2018-07)
1 Scope
The present document describes the Representational State Transfer (REST) reference point, which is used to exchange
application level session information between the Protocol Converter (PC) and the Application Function (AF). REST
shall be used as an architectural style as appropriate.
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 TR 29.817: "Study on XML based access of AF to the PCRF".
[3] 3GPP TS 29.213: "Policy and Charging Control signalling flows and Quality of Service (QoS)
parameter mapping".
[4] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point".
[5] 3GPP TS 23.203: "Policy and Charging Control architecture".
[6] Void.
[7] Void.
[8] IETF RFC 793: "Transmission Control Protocol".
[9] IETF RFC 2616: "Hypertext Transfer Protocol – HTTP/1.1".
[10] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".
[11] IETF RFC 1035: "Domain Names – Implementation and Specification".
[12] IETF RFC 2131: "Dynamic Host Configuration Protocol".
[13] 3GPP TS 33.310: "Network Domain Security (NDS); Authentication Framework (AF)".
[14] IETF RFC 2818: "HTTP Over TLS".
[15] IETF RFC 1786: "Uniform Resource Locators (URL)".
[16] Void.
[17] IETF RFC 6733: "Diameter Base Protocol".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 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].
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 29.201 version 15.0.0 Release 15 7 ETSI TS 129 201 V15.0.0 (2018-07)
Application Function (AF): element offering application(s) that use IP bearer resources.
Protocol Converter (PC): element that converts the RESTful/XML based Rx reference point to the Diameter based Rx
reference point.
Representation: is a view of a resource state, it is encoded in one or more transferable formats, such as XML, JSON,
plain text or other formats.
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.
REST-Rx: term that is used to indicate the Rx interface based on RESTful HTTP between the AF and the PC.
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].
AAA Authentication, Authorization, Accounting
AF Application Function
API Application Programming Interface
BBERF Bearer Binding and Event Reporting Function
DHCP Dynamic Host Configuration Protocol
DNS Domain Name System
DRA Diameter Routing Agent
DRMP Diameter Routing Message Priority
DSCP Differentiated Services Code Point
HTTP HyperText Transfer Protocol
HTTPS Hypertext Transfer Protocol Secure
IP-CAN IP Connectivity Access Network
PC Protocol Converter
PCC Policy and Charging Control
PCEF Policy and Charging Enforcement Function
PCRF Policy and Charging Rules Function
PDN Packet Data Network
PLMN Public Land Mobile Network
QoS Quality of Service
REST Representational State Transfer
SPR Subscription Profile Repository
UDR User Data Repository
URI Uniform Resource Identifier
URL Uniform Resource Locator
UE User Equipment
XML Extensible Markup Language
4 Representational State Transfer (REST) reference
point based on Protocol Converter (PC) architecture
4.1 Overview
The Representational State Transfer (REST) reference point resides between the AF and the Protocol Converter (PC).
The PC converts application level information received from the AF to Diameter session information and communicates
with the PCRF via the Diameter based Rx reference point (3GPP TS 29.214 [4]).
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 29.201 version 15.0.0 Release 15 8 ETSI TS 129 201 V15.0.0 (2018-07)
4.2 Reference model
The Rx reference point, which is based on Diameter, is defined between the PCRF and the AF in 3GPP TS 29.214 [4].
If the AF supports RESTful HTTP and XML a Protocol Converter (PC) is needed. In this specification the interface
between the AF and the PC is named REST-Rx. The REST-Rx interface shall be used in non-IMS scenarios only.
The PC converts the information, received over the REST-Rx interface, into information that can be used on the
Diameter based Rx interface in order to get an access to the PCC architecture and vice versa. The PC manages RESTful
resources, which are an integral part of the REST-Rx interface. As defined in the stage 2 specifications
(3GPP TS 23.203 [5]), information from the AF is part of the input used by the PCRF for Policy and Charging Control
(PCC) decisions. Signalling flows are specified in Annex A.
The overall PCC architecture is depicted in subclause 3a of 3GPP TS 29.213[3].
The relationships between the different functional entities involved are depicted in figure 4.2.1.
REST-Rx Rx
PCRF
AF
PC
Figure 4.2.1: The REST-Rx reference model
NOTE: The PCRF and PC are both together either located in the VPLMN or HPLMN. The AF is either in the
same PLMN as the PC, or it is in a third part network attached to that PLMN.
Figure 4.2.2: Void
Figure 4.2.3: Void
Figure 4.2.4: Void
Figure 4.2.5: Void
Figure 4.2.6: Void
4.3 Functional elements
4.3.1 Application function
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). 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 Protocol converter
If the AF only supports RESTful HTTP and XML a protocol converter is needed between the AF and the PCRF.
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 29.201 version 15.0.0 Release 15 9 ETSI TS 129 201 V15.0.0 (2018-07)
The Protocol converter (PC) is an element converting information carried over RESTful HTTP and XML to information
carried over Diameter in order to get an access to the PCC architecture.
4.4 Location of the PC within the PLMN
4.4.1 General
The protocol converter can be located:
(1) In the PLMN but outside of the PCRF realm;
(2) In the PCRF realm.
There is only one logical protocol converter in both above cases.
4.4.2 Protocol converter located in the PLMN but outside of the PCRF
realm
In this scenario the protocol converter is in the PLMN but outside of the PCRF realm, as shown in figure 4.4.2.1.
PLMN
Diameter (PCRF) realm
PCRF
PCRF
DRA
PCRF
AF Rx
Diameter (PCRF) realm
PCRF
DRA
PCRF
PCRF
NOTE: A DRA is needed if more than one PCRF is present in a Diameter (PCRF) realm.
Figure 4.4.2.1: Protocol converter placed within PLMN but outside of the Diameter (PCRF) realm
4.4.3 Protocol converter located in the PCRF realm
In this scenario the protocol converter is in the PCRF realm, as shown in figure 4.4.3.1.
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 29.201 version 15.0.0 Release 15 10 ETSI TS 129 201 V15.0.0 (2018-07)
PLMN
Diameter (PCRF) realm
PCRF
PCRF
DRA
PCRF
Rx
AF
Rx
Diameter (PCRF) realm
PCRF
DRA
PCRF
PCRF
Figure 4.4.3.1: Protocol converter placed within the Diameter (PCRF) realm
NOTE: A DRA is needed if more than one PCRF is present in a Diameter (PCRF) realm.
4.5 PCC Procedures over the RESTful reference point
4.5.1 General
PCC procedures which can be operated at the REST-Rx interface are described in the following subclauses.
4.5.2 Initial Provisioning of Session Information
When a new AF session is being established and media information for this AF session is available at the AF and the
related media require PCC supervision, the AF shall open an RESTful Rx session with the PC for the AF session using
an HTTP POST message that addresses the resource responsible for resource creation, unless an Rx session has already
been established for the AF session. If the RESTful Rx session already exists for the AF session, the AF uses the
existing RESTful Rx session and shall use the HTTP PUT message including the AF Session ID in the path element to
address the existing resource. The AF shall provide the full IP address of the UE using either UEIP element or UEIPv6
element, and the corresponding Service Information within MCD group(s). The AF shall not include circuit-switched
bearer related media in the service information sent to the PC. The AF shall indicate to the PC as part of the MCD
element whether the media IP flow(s) should be enabled or disabled with the FlowStatus element.
The AF may include the AFAppId element into the AF session establishment representation in order to indicate the
particular service that the AF session belongs to. This element can be provided at both AF session level, and media
component description level. When provided at both levels, the AFAppId element provided within the MCD group will
have precedence.
The AF may include the AFChargingId element into the AF session establishment representation for charging
correlation purposes. The AF may also include the SpecificAction element to request notification for certain user plane
events, e.g. bearer termination.
The AF may include the SvcURN element in order to indicate that the new AF session relates to emergency traffic.
The AF may include the MPSId element in order to indicate that the new AF session relates to an MPS session.
If the AF provides service information that has been fully negotiated, the AF may include the SvcInfoStatus element set
to FINAL_SERVICE_INFORMATION as specified in 3GPP TS 29.214 [4].
The AF may additionally provide preliminary service information not fully negotiated yet at an earlier stage. To do so,
the AF shall include the SvcInfoStatus element with the value set to PRELIMINARY SERVICE INFORMATION as
specified in 3GPP TS 29.214 [4].
ETSI
---------------------- Page: 11 ----------------------
3GPP TS 29.201 version 15.0.0 Release 15 11 ETSI TS 129 201 V15.0.0 (2018-07)
For sponsored data connectivity and if SponsoredConnectivity is supported, the AF shall provide the application service
provider identity and the sponsor identity to the PCRF via the PC by including the ASPId element and the SponsId
element in the SpConnData group in the AF session establishment representation. Additionally if SponsorChange is
supported the AF shall provide an indication whether to enable or not enable sponsored data connectivity to the PCRF
by including the SponsAct element set to the applicable value.
NOTE 1: The relationship between AF and sponsor is out of scope of this specification. A single AF can serve
multiple sponsors.
To support the usage monitoring of sponsored data connectivity, the AF may also include the GSU group in the
SpConnData group and the SpecificAction element set to the value USAGE_REPORT as specified in
3GPP TS 29.214 [4] to request notification when the usage threshold has been reached.
NOTE 2: If the AF is in the user plane, the AF can handle the usage monitoring and therefore it is not required to
provide a usage threshold to the PCRF as part of the sponsored data connectivity information.
If the PCRF includes the Retry-Interval AVP within the AA-Answer command to the PC, the PC shall provide the same
value of retry interval in the RetryInterval element in the AF session establishment representation. The AF shall not
send the same service information to the PCRF (via the PC) again (for the same IP-CAN session) until the retry interval
has elapsed.
To allow the PCRF and PCEF to perform PCC rule authorization and bearer binding for the described service IP flows,
the AF may supply both source and destination IP addresses and port numbers within the FlowDesc element, if such
information is available.
The AF may specify the TTC element for the described service data flows together with the FlowDesc element.
NOTE 3: The TTC element can be useful when another packet filter attribute is needed to differentiate between
flows. For example, (when EPS bearers are used for group communication services) flows encapsulated
and encrypted by a tunneling protocol and thus having their IP five-tuple attributes obscured can be
differentiated by the Type of Service (or Traffic Class) value of the outer header.
NOTE 4: The use of TTC element by the AF assumes that no DSCP re-marking is applied from the application to
the PGW.
The AF may specify the ResPrio element at request level in the AF session establishment representation in order to
assign a priority
...