1、 ETSI TS 1Universal Mobile TelRepresentatireference point beand Pr(3GPP TS 29.2TECHNICAL SPECIFICATION129 201 V12.4.0 (2016elecommunications System (LTE; ational State Transfer (REST) between Application FunctionProtocol Converter (PC) .201 version 12.4.0 Release 1216-05) (UMTS); T) on (AF) 12) ETSI
2、 ETSI TS 129 201 V12.4.0 (2016-05)13GPP TS 29.201 version 12.4.0 Release 12Reference RTS/TSGC-0329201vc40 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 luc
3、ratif 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 networ
5、k 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 http:/portal.etsi.org/tb/status/status.asp If you find errors in the pre
6、sent 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 authori
7、zed 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 2016. All rights reserved. DECTTM, PLUGT
8、ESTSTM, 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 Associatio
9、n. ETSI ETSI TS 129 201 V12.4.0 (2016-05)23GPP TS 29.201 version 12.4.0 Release 12Intellectual 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 for ETSI me
10、mbers 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.et
11、si.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 t
12、he 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 interpreted as be
13、ing 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“, “will“,
14、“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 V12.4.0 (2016-05)33GPP TS 2
15、9.201 version 12.4.0 Release 12Contents 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 based on P
16、rotocol Converter (PC) architecture . 8g34.1 Overview 8g34.2 Reference model . 8g34.3 Functional elements 13g34.3.1 Application function . 13g34.3.2 Protocol converter . 13g34.4 Location of the PC within the PLMN . 13g34.4.1 General 13g34.4.2 Protocol converter located in the PLMN but outside of the
17、 PCRF realm . 14g34.4.3 Protocol converter located in the PCRF realm 14g34.5 PCC Procedures over the RESTful reference point 15g34.5.1 General 15g34.5.2 Initial Provisioning of Session Information 15g34.5.3 Modification of Session Information 16g34.5.4 AF Session Termination . 17g34.5.5 Gate Related
18、 Procedures . 17g34.5.6 Subscription to Notification of Signalling Path Status . 17g34.5.7 Traffic Plane Events 17g35 Protocol 18g35.1 Introduction 18g35.2 Transport layer . 18g35.3 Application delivery layer 18g35.3.1 Methods 19g35.3.2 Void 20g35.3.3 Resources and URI design 20g35.3.4 HTTP request/
19、response dialogues . 20g35.3.5 AF Session ID . 22g35.4 Specific application communication 22g35.4.0 General 22g35.4.1 Content type XML 22g35.4.1.1 XML schema . 22g35.4.1.2 Data types and mapping between XML elements . 22g35.4.1.3 Mapping between Diameter AVPs and XML elements and groups 23g35.5 PC d
20、iscovery 25g36 Routing . 25g36.1 PC located in the PLMN but outside of the PCRF realm . 25g36.2 PC located in the PCRF realm 25g37 Secure communication . 26g3Annex A (informative): Call Flows . 27g3ETSI ETSI TS 129 201 V12.4.0 (2016-05)43GPP TS 29.201 version 12.4.0 Release 12A.1 General . 27g3A.2 A
21、F session establishment . 27g3A.3 AF Session Modification Initiated by AF 27g3A.4 AF Session Termination . 28g3A.5 Gate Related Procedures 28g3A.6 Subscription to Notification of Signalling Path Status . 29g3A.7 Notification of Traffic Plane Events 29g3A.7.1 Traffic plane event reporting 30g3A.7.2 S
22、ervice data flow deactivation when all service data flows are affected 30g3A.7.3 IP-CAN Session Termination . 31g3Annex B (normative): XML Schema 33g3B.1 XML elements and groups . 33g3B.2 Diameter message representation . 36g3Annex C (informative): Change history . 40g3History 41g3ETSI ETSI TS 129 2
23、01 V12.4.0 (2016-05)53GPP TS 29.201 version 12.4.0 Release 12Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Shoul
24、d 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
25、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 201 V12.
26、4.0 (2016-05)63GPP TS 29.201 version 12.4.0 Release 121 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 b
27、e 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
28、 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
29、 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 a
30、nd Charging Control over Rx reference point“. 5 3GPP TS 23.203: “Policy and Charging Control architecture“. 6 3GPP TS 23.335: “User Data Convergence (UDC); Technical realization and information flows; Stage 2“. 7 3GPP TS 29.335: “User Data Convergence (UDC); User Data Repository Access Protocol over
31、 the Ud interface; Stage 3“. 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
32、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 IETF RFC 3588: “Diameter Base Protocol“. ETSI ETSI TS 129 201 V12.4.0 (2016-05)73GPP TS 29.201 v
33、ersion 12.4.0 Release 123 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
34、 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 Diameter based Rx reference point. Representation: is a view of a resource state, it is encoded in one
35、 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
36、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 t
37、akes 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
38、 Name System DRA Diameter Routing AgentHTTP 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 Packe
39、t 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 ETSI ETSI TS 129 201 V
40、12.4.0 (2016-05)83GPP TS 29.201 version 12.4.0 Release 124 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 conve
41、rts 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). 4.2 Reference model The Rx reference point, which is based on Diameter, is defined between the PCRF and the AF (3GPP TS
42、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,
43、 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
44、 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 relationships between the different functional entities involved for non-roaming scenario are depicted in figure 4.2.1 and 4.2.2. ETSI ETSI TS 129 201 V12.4.0
45、 (2016-05)93GPP TS 29.201 version 12.4.0 Release 12SdProtocol Converter (PC)SyGyGzSubscription ProfileRepository(SPR)RxSpOffline Charging System (OFCS)GxxGxTDFPolicy and Charging Rules Function (PCRF)-BBERFGatewayPCEFOnline ChargingSystem (OCS)Application Function(AF)REST-RxGznGynFigure 4.2.1: The P
46、CC architecture with the PC for non-roaming scenario with SPR With the UDC-based architecture, as defined in 3GPP TS 23.335 6 and applied in 3GPP TS 23.203 5, the UDR replaces the SPR and the Ud reference point provides access to the subscription data in the UDR. The Ud interface as defined in 3GPP
47、TS 29.335 7 is the interface between the PCRF and the UDR. When the UDC architecture is used, SPR and Sp, whenever mentioned in this document, are replaced by UDR and Ud. ETSI ETSI TS 129 201 V12.4.0 (2016-05)103GPP TS 29.201 version 12.4.0 Release 12SdProtocol Converter (PC)SyGyGzUser DataRepositor
48、y(UDR)RxUdOffline Charging System (OFCS)GxxGxTDFPolicy and Charging Rules Function (PCRF)-BBERFGatewayPCEFOnline ChargingSystem (OCS)Application Function(AF)REST-RxGznGynFigure 4.2.2: The PCC architecture with the PC for non-roaming scenario with UDR The relationships between the different functiona
49、l entities involved for home routed scenario are depicted in figure 4.2.3 and 4.2.4. ETSI ETSI TS 129 201 V12.4.0 (2016-05)113GPP TS 29.201 version 12.4.0 Release 12Figure 4.2.3: The PCC architecture with the PC for home routed scenario with SPR Figure 4.2.4: The PCC architecture with the PC for home routed scenario with UDR The relationships between the different functional entities involved for local breakout scenario are depicted in figure 4.2.5 and 4.2.6. ETSI ETSI TS 129 201 V12.4.0 (2016-05)123GPP TS 29.201 version
