1、 ETSI TS 1Universal Mobile TelRepresentatireference point beand Pro(3GPP TS 29.2TECHNICAL SPECIFICATION129 201 V13.6.0 (2017elecommunications System (LTE; ational State Transfer (REST) between Application FunctionProtocol Converter (PC) .201 version 13.6.0 Release 1317-01) (UMTS); T) on (AF) 13) ETS
2、I ETSI TS 129 201 V13.6.0 (2017-01)13GPP TS 29.201 version 13.6.0 Release 13Reference RTS/TSGC-0329201vd60 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 lu
3、cratif enregistre la Sous-Prfecture 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
4、 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 netwo
5、rk 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 https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors
6、 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
7、 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. European Telecommunications Standards Institute 2017. All rights reserved. DE
8、CTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM
9、 Association. ETSI ETSI TS 129 201 V13.6.0 (2017-01)23GPP TS 29.201 version 13.6.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available
10、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 (ht
11、tps:/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, ess
12、ential to the present document. 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 interp
13、reted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 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
14、“, “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 ETSI TS 129 201 V13.6.0 (2017-01
15、)33GPP TS 29.201 version 13.6.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Representational State Transfer (REST) reference point
16、 based on Protocol Converter (PC) architecture . 8g34.1 Overview 8g34.2 Reference model . 8g34.3 Functional elements 9g34.3.1 Application function . 9g34.3.2 Protocol converter . 9g34.4 Location of the PC within the PLMN . 9g34.4.1 General 9g34.4.2 Protocol converter located in the PLMN but outside
17、of the PCRF realm . 9g34.4.3 Protocol converter located in the PCRF realm 10g34.5 PCC Procedures over the RESTful reference point 10g34.5.1 General 10g34.5.2 Initial Provisioning of Session Information 11g34.5.3 Modification of Session Information 12g34.5.4 AF Session Termination . 13g34.5.5 Gate Re
18、lated Procedures . 13g34.5.6 Subscription to Notification of Signalling Path Status . 13g34.5.7 Traffic Plane Events 13g35 Protocol 14g35.1 Introduction 14g35.2 Transport layer . 14g35.3 Application delivery layer 14g35.3.1 Methods 15g35.3.2 Void 16g35.3.3 Resources and URI design 16g35.3.4 HTTP req
19、uest/response dialogues . 16g35.3.5 AF Session ID . 18g35.4 Specific application communication 18g35.4.0 General 18g35.4.1 Content type XML 18g35.4.1.1 XML schema . 18g35.4.1.2 Data types and mapping between XML elements . 18g35.4.1.3 Mapping between Diameter AVPs and XML elements and groups 19g35.5
20、 PC discovery 21g36 Routing . 21g36.1 PC located in the PLMN but outside of the PCRF realm . 21g36.2 PC located in the PCRF realm 21g37 Secure communication . 22g3Annex A (informative): Call Flows . 23g3ETSI ETSI TS 129 201 V13.6.0 (2017-01)43GPP TS 29.201 version 13.6.0 Release 13A.1 General . 23g3
21、A.2 AF session establishment . 23g3A.3 AF Session Modification Initiated by AF 23g3A.4 AF Session Termination . 24g3A.5 Gate Related Procedures 24g3A.6 Subscription to Notification of Signalling Path Status . 25g3A.7 Notification of Traffic Plane Events 25g3A.7.1 Traffic plane event reporting 26g3A.
22、7.2 Service data flow deactivation when all service data flows are affected 26g3A.7.3 IP-CAN Session Termination . 27g3Annex B (normative): XML Schema 29g3B.1 XML elements and groups . 29g3B.2 Diameter message representation . 32g3Annex C (informative): Change history . 36g3History 37g3ETSI ETSI TS
23、129 201 V13.6.0 (2017-01)53GPP TS 29.201 version 13.6.0 Release 13Foreword 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.
24、 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 gr
25、eater 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 ETSI TS 129 20
26、1 V13.6.0 (2017-01)63GPP TS 29.201 version 13.6.0 Release 131 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 s
27、hall 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, et
28、c.) 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
29、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: “Po
30、licy 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 Sy
31、ntax“. 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)“
32、. 16 IETF RFC 3588: “Diameter Base Protocol“. ETSI ETSI TS 129 201 V13.6.0 (2017-01)73GPP TS 29.201 version 13.6.0 Release 133 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 d
33、efined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 1. 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 D
34、iameter 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 componen
35、ts, 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
36、 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
37、BBERF Bearer Binding and Event Reporting Function DHCP Dynamic Host Configuration Protocol DNS Domain Name System DRA Diameter Routing AgentDRMP Diameter Routing Message Priority DSCP Differentiated Services Code Point HTTP HyperText Transfer Protocol HTTPS Hypertext Transfer Protocol Secure IP-CAN
38、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 Subscript
39、ion Profile Repository UDR User Data Repository URI Uniform Resource Identifier URL Uniform Resource Locator UE User Equipment XML Extensible Markup Language ETSI ETSI TS 129 201 V13.6.0 (2017-01)83GPP TS 29.201 version 13.6.0 Release 134 Representational State Transfer (REST) reference point based
40、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 vi
41、a the Diameter based Rx reference point (3GPP TS 29.214 4). 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 inter
42、face 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
43、 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 spe
44、cified in Annex A. The overall PCC architecture is depicted in subclause 3a of 3GPP TS 29.2133. The relationships between the different functional entities involved are depicted in figure 4.2.1. PCg3REST-Rxg3AFg3PCRFg3Rxg3Figure 4.2.1: The REST-Rx reference model NOTE: The PCRF and PC are both toget
45、her 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 ETSI ETSI TS 129 201 V13.6.0 (2017-01)93GPP TS 29.201 version
46、13.6.0 Release 134.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 t
47、o 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. The Protocol converter (PC
48、) 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;
49、(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. ETSI ETSI TS 129 201 V13.6.0 (2017-01)103GPP TS 29.201 version 13.6.0 Release 13PLMNDiameter (PCRF) realmAFPCRFPCRFPCRFDRADiameter (PCRF) realmPCRFPCRFPCRFDRA Rx NOTE: A DRA is needed if more than one PCRF is present in a Diameter (PCRF) realm. Figure
