1、 ETSI TS 129 251 V14.0.0 (2017-07) LTE; Gw and Gwn reference point for sponsored data connectivity (3GPP TS 29.251 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 129 251 V14.0.0 (2017-07)13GPP TS 29.251 version 14.0.0 Release 14Reference DTS/TSGC-0329251ve00 Keywords LTE ETSI 650 Ro
2、ute 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.ets
3、i.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
4、 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 o
5、f 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.
6、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
7、ETSI. The copyright and the foregoing restriction extend to reproduction in all media. ETSI 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are trademarks of ETSI registered for the benefit of it
8、s 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 ETSI TS 129 251 V14.0.0 (2017-07)23GPP TS 29.251 version 14.0.0 Release 14Intellectual Property Rights IPR
9、s 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 members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or po
10、tentially 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.
11、 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. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnersh
12、ip 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 identi
13、ties 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
14、 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 251 V14.0.0 (2017-07)33GPP TS 29.251 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3F
15、oreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Gw reference point . 7g34.1 Overview 7g34.2 Gw reference model . 7g34.3 Functional elements 8g34.3.1 PFDF . 8g34.3.2 PCEF . 8g34.4 Procedures over Gw reference point 8g34.4.1 Requ
16、est for PFDs (“Pull mode”). 8g34.4.2 Provisioning of PFDs (“Push mode” and “Combination mode“) 9g35 Gwn reference point . 9g35.1 Overview 9g35.2 Gwn reference model . 10g35.3 Functional elements 10g35.3.1 PFDF . 10g35.3.2 TDF . 10g35.4 Procedures over Gwn reference point 10g36 Gw/Gwn protocol . 10g3
17、6.1 Introduction 10g36.2 Transport layer . 11g36.3 Application delivery layer 11g36.3.2 Resources and URI design 12g36.3.2.1 General 12g36.3.2.2 URI design for Pull mode . 12g36.3.2.3 URI design for Push mode 13g36.3.3 HTTP request/response formats 13g36.3.3.1 General 13g36.3.3.2 GET /gwapplication/
18、pfds/application-identifier 14g36.3.3.3 GET /gwapplication/pfds?query-parameters 15g36.3.3.4 GET /gwapplication/pfds 16g36.3.3.5 POST /gwapplication/provisioning . 17g36.3.4 HTTP status codes 19g36.3.5 Feature negotiation . 19g36.3.5.1 General 19g36.3.5.2 HTTP custom headers . 20g36.3.5.2.1 3gpp-Opt
19、ional-Features . 20g36.3.5.2.2 3gpp-Required-Features 20g36.3.5.2.3 3gpp-Accepted-Features 20g36.4 Specific application communication 21g36.4.1 General 21g36.4.2 Content type 21g36.4.3 JSON PFDs fields . 21g36.4.3.1 General 21g36.4.3.2 application-identifier . 21g3ETSI ETSI TS 129 251 V14.0.0 (2017-
20、07)43GPP TS 29.251 version 14.0.0 Release 146.4.3.3 void . 21g36.4.3.4 caching-time 21g36.4.3.5 pfds 22g36.4.3.6 pfd-identifier . 22g36.4.3.7 flow-descriptions . 22g36.4.3.8 urls. 22g36.4.3.9 domain-names . 22g36.4.4 JSON provisioning fields 22g36.4.4.1 General 22g36.4.4.2 notification-flag . 23g36.
21、4.4.3 removal-flag 23g36.4.4.4 allowed-delay 23g36.4.4.5 partial-flag . 23g36.4.5 JSON errors and informational response fields 23g36.4.5.1 General 23g36.4.5.2 error-tag. 24g36.4.6 JSON report fields 24g36.4.6.1 General 24g36.4.6.2 pfd-reports . 24g36.4.6.3 pfd-failure-code . 25g36.5 The discovery o
22、f PCEF/TDF and PFDF . 25g36.5.1 PCEF/TDF discovery 25g36.5.2 PFDF discovery 25g37 Secure communication . 25g3Annex A (normative): JSON Schema . 26g3A.1 PFDs schema 26g3A.2 Provisioning schema. 27g3A.3 Error and Informational response schema 28g3Annex B (informative): Call Flows . 31g3B.1 General . 3
23、1g3B.2 Request for PFDs (“Pull mode”) 31g3B.3 Provisioning of PFDs (“Push mode”) . 31g3B.4 Provisioning of PFDs by Push with Notifications 32g3Annex C (informative): Change history . 34g3History 35g3ETSI ETSI TS 129 251 V14.0.0 (2017-07)53GPP TS 29.251 version 14.0.0 Release 14Foreword This Technica
24、l 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. Should the TSG modify the contents of the present document, it will be re-released by th
25、e 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 increme
26、nted 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 251 V14.0.0 (2017-07)63GPP TS 29.251 version 14.0.0 Release 141 Scope The present document
27、provides the stage 3 specification of the Gw and Gwn reference points. The functional requirements and the stage 2 specifications of the Gw and Gwn reference points are specified in 3GPP TS 23.203 2. The Gw reference point lies between the Packet Flow Description Function (PFDF) and the Policy and C
28、harging Enforcement Function (PCEF). The Gwn reference point lies between the Packet Flow Description Function (PFDF) and the Traffic Detection Function (TDF). 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document
29、. - 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 (incl
30、uding 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 3GPP TS 29.213: “Policy and Ch
31、arging Control signalling flows and QoS parameter mapping“ 4 3GPP TS 23.682: “Architecture enhancements to facilitate communications with packet data networks and applications“. 5 3GPP TS 29.212: “Policy and Charging Control (PCC); Reference points“. 6 IETF RFC 793: “Transmission Control Protocol“.
32、7 IETF RFC 2616: “Hypertext Transfer Protocol HTTP/1.1“. 8 3GPP TS 33.210: “3G security; Network Domain Security (NDS); IP network layer security“. 9 IETF RFC 2818: “HTTP Over TLS“. 10 IETF RFC 3986: “Uniform Resource Identifier (URI): Generic Syntax“ 11 IETF RFC 7159: “The JavaScript Object Notatio
33、n (JSON) Data Interchange Format“. 12 IETF draft-newton-json-content-rules-08: “A Language for Rules Describing JSON Content“. Editors note: The above document cannot be formally referenced until it is published as an RFC. 13 IETF RFC 6733: “Diameter Base Protocol“. 14 3GPP TS 29.250: “Nu reference
34、point between SCEF and PFDF for sponsored data connectivity“. 15 3GPP TS 29.155: “Traffic steering control; Representational state transfer (REST) over St reference point“. ETSI ETSI TS 129 251 V14.0.0 (2017-07)73GPP TS 29.251 version 14.0.0 Release 143 Definitions and abbreviations 3.1 Definitions
35、For the purposes of the present document, the terms and definitions given in 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 TR 21.905 1. Packet Flow Description (PFD): A set of information enabling the det
36、ection of application traffic provided by a 3rdparty service provider (from 3GPP TS 23.203 2). Pull mode: A mode used between the PCEF/TDF and the PFDF where the PFDs are sent by the PFDF at reception of an HTTP request from the PCEF/TDF. Push mode: A mode used between the PCEF/TDF and the PFDF wher
37、e the PFDs and/or notification of PFD deletion are sent by the PFDF in an HTTP request to the PCEF/TDF. Combination mode: A mode used between the PCEF/TDF and the PFDF where both pull and push exist. This mode allows the PFDF to send PFDs and/or notification of PFD creation/update/deletion in the HT
38、TP request to the PCEF/TDF. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 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. JSON Jav
39、aScript Object Notation PCEF Policy and Charging Enforcement Function PFD Packet Flow Description PFDF Packet Flow Description Function SCEF Service Capability Exposure Function TDF Traffic Detection Function 4 Gw reference point 4.1 Overview The Gw reference point is located between the Packet Flow
40、 Description Function (PFDF) and the Policy and Charging Enforcement Function (PCEF). The Gw reference point is used for provisioning and removal of PFDs from the PFDF to the PCEF and reporting the handling result of PFDs from the PCEF to the PFDF. The stage 2 level requirements for the Gw reference
41、 point are defined in 3GPP TS 23.203 2. 4.2 Gw reference model The Gw reference point is defined between the PFDF and the PCEF. The relationships between the different functional entities involved are depicted in figure 4.2.1. The overall PCC architecture is depicted in subclause 3a of 3GPP TS 29.21
42、3 3. PFDFg3Gwg3PCEFg3Figure 4.2.1: Gw reference model ETSI ETSI TS 129 251 V14.0.0 (2017-07)83GPP TS 29.251 version 14.0.0 Release 144.3 Functional elements Editors note: This clause shall include a description of the functional elements, on which the Gw reference point has an influence. The issues
43、related to the Gw reference point shall be described. 4.3.1 PFDF The PFDF (Packet Flow Description Function) is a functional element which stores PFDs associated with application identifier (s) and transfers them to the PCEF via Gw interface to enable the PCEF to perform accurate application detecti
44、on when the PFDs are managed by a 3rdparty service provider. The PFDF receives PFDs for the corresponding application identifier (s) from the SCEF as defined in 3GPP TS 23.682 4and 3GPP TS 29.250 14. 4.3.2 PCEF The PCEF (Policy and Charging Enforcement Function) funtionality defined in subclause 4.4
45、.2 of 3GPP TS 29.212 5 shall be applied. In addition, the PCEF shall support the management of PFDs provisioned by the PFDF. The application detection filter may be extended with the PFDs provided by the PFDF. The new PFDs provided by the PFDF replace the existing ones in the PCEF. 4.4 Procedures ov
46、er Gw reference point When the PFDF is deployed and the management of PFDs is supported by the PCEF, the mode of PFDs management shall be consistently configured in one PLMN, it may be: - Pull mode only, or - Push mode only, or - Combination mode. 4.4.1 Request for PFDs (“Pull mode”) At the time a P
47、CC Rule with an application identifier for which PFDs are not available is activated or provisioned, or when the caching timer for an application identifier elapses and a PCC Rule for the application identifier is still active, the PCEF shall request all PFDs for the application identifier from the
48、PFDF. The PCEF shall send an HTTP GET message to the PFDF to retrieve the PFDs for one or more application identifier(s) as defined in subclauses 6.3.3.2, 6.3.3.3 and 6.3.3.4. Upon receipt of the HTTP request for the pull operation, the PFDF shall respond to the PCEF indicating whether the pull oper
49、ation was successful or not by using one of the HTTP status codes; if the pull operation is successful, the PFDF : - shall provide the PFDs of the specified application identifier(s) from the request within the body of the HTTP response; and - if there are caching time value(s) configured for any of the specified application identifier(s), shall set the caching-time to the caching time value(s) for those application identifier(s) in the body of the HTTP response. The PCEF shall enforce the received PFDs for the appl
