1、 ETSI TS 129 251 V14.2.0 (2018-01) LTE; Gw and Gwn reference point for sponsored data connectivity (3GPP TS 29.251 version 14.2.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 129 251 V14.2.0 (2018-01)13GPP TS 29.251 version 14.2.0 Release 14Reference RTS/TSGC-0329251ve20 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 2018. 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.2.0 (2018-01)23GPP TS 29.251 version 14.2.0 Release 14Intellectual Property Rights Ess
9、ential patents 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 members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs)
10、; 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 ca
11、rried 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 wh
12、ich 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
13、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 identiti
14、es, 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 http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “
15、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 u
16、sed in direct citation. ETSI ETSI TS 129 251 V14.2.0 (2018-01)33GPP TS 29.251 version 14.2.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations
17、. 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 Request for PFDs (“Pull mode“ and “Combination mode“) . 8g34.4.2 Provisioning of PFDs (“Push mode“” and “Combination m
18、ode“) 9g35 Gwn reference point . 10g35.1 Overview 10g35.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 . 11g36.1 Introduction 11g36.2 Transport layer . 11g36.3 Application delivery layer 12g36.3.2
19、 Resources and URI design 12g36.3.2.1 General 12g36.3.2.2 URI design for Pull mode . 13g36.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/pfds/application-identifier 14g36.3.3.3 GET /gwapplication/pfds?query-parameters 15g36.
20、3.3.4 GET /gwapplication/pfds 17g36.3.3.5 POST /gwapplication/provisioning . 18g36.3.4 HTTP status codes 20g36.3.5 Feature negotiation . 20g36.3.5.1 General 20g36.3.5.2 HTTP custom headers . 21g36.3.5.2.1 3gpp-Optional-Features . 21g36.3.5.2.2 3gpp-Required-Features 21g36.3.5.2.3 3gpp-Accepted-Featu
21、res 21g36.3.5.3 Precedence for HTTP custom headers 22g36.4 Specific application communication 22g36.4.1 General 22g36.4.2 Content type 22g36.4.3 JSON PFDs fields . 22g36.4.3.1 General 22g3ETSI ETSI TS 129 251 V14.2.0 (2018-01)43GPP TS 29.251 version 14.2.0 Release 146.4.3.2 application-identifier .
22、22g36.4.3.3 void . 23g36.4.3.4 caching-time 23g36.4.3.5 pfds 23g36.4.3.6 pfd-identifier . 23g36.4.3.7 flow-descriptions . 23g36.4.3.8 urls. 23g36.4.3.9 domain-names . 23g36.4.4 JSON provisioning fields 24g36.4.4.1 General 24g36.4.4.2 notification-flag . 24g36.4.4.3 removal-flag 24g36.4.4.4 allowed-d
23、elay 24g36.4.4.5 partial-flag . 24g36.4.5 JSON errors and informational response fields 24g36.4.5.1 General 24g36.4.5.2 error-tag. 25g36.4.6 JSON report fields 25g36.4.6.1 General 25g36.4.6.2 pfd-reports . 25g36.4.6.3 pfd-failure-code . 26g36.5 The discovery of PCEF/TDF and PFDF . 26g36.5.1 PCEF/TDF
24、 discovery 26g36.5.2 PFDF discovery 26g37 Secure communication . 26g3Annex A (normative): JSON Schema . 27g3A.1 PFDs schema 27g3A.2 Provisioning schema. 28g3A.3 Error and Informational response schema 29g3Annex B (informative): Call Flows . 32g3B.1 General . 32g3B.2 Request for PFDs (“Pull mode”) 32
25、g3B.3 Provisioning of PFDs (“Push mode”) . 32g3B.4 Provisioning of PFDs by Push with Notifications 33g3Annex C (informative): Change history . 35g3History 36g3ETSI ETSI TS 129 251 V14.2.0 (2018-01)53GPP TS 29.251 version 14.2.0 Release 14Foreword This Technical Specification has been produced by the
26、 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 the TSG with an identifying change of rele
27、ase 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.
28、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.2.0 (2018-01)63GPP TS 29.251 version 14.2.0 Release 141 Scope The present document provides the stage 3 specification of th
29、e 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 Charging Enforcement Function (PCEF). The
30、 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. - References are either specific (iden
31、tified 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 re
32、ference 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 Charging Control signalling flows and QoS
33、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“. 7 Void. 8 3GPP TS 33.210: “3G security;
34、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 Notation (JSON) Data Interchange Format“. 12 IETF draft-newton-json-content-rules-08: “A Languag
35、e 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 point between SCEF and PFDF for sponsored data connectivity“. 15 3GPP TS 29.155: “Traffic
36、 steering control; Representational state transfer (REST) over St reference point“. 16 IETF RFC 7230: “Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing“. 17 IETF RFC 7231: “Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content“. 18 IETF RFC 7232: “Hypertext Transfer Protoco
37、l (HTTP/1.1): Conditional Requests“. 19 IETF RFC 7233: “Hypertext Transfer Protocol (HTTP/1.1): Range Requests“. ETSI ETSI TS 129 251 V14.2.0 (2018-01)73GPP TS 29.251 version 14.2.0 Release 1420 IETF RFC 7234: “Hypertext Transfer Protocol (HTTP/1.1): Caching“. 21 IETF RFC 7235: “Hypertext Transfer P
38、rotocol (HTTP/1.1): Authentication“. 3 Definitions and abbreviations 3.1 Definitions 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,
39、 in TR 21.905 1. Packet Flow Description (PFD): A set of information enabling the detection 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 req
40、uest from the PCEF/TDF. Push mode: A mode used between the PCEF/TDF and the PFDF where 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 allow
41、s the PFDF to send the PFDs at reception of an HTTP request from the PCEF/TDF and provision PFD changes (creation/update/deletion) and/or notification of PFD creation/update/deletion in the HTTP request to the PCEF/TDF. 3.2 Abbreviations For the purposes of the present document, the abbreviations gi
42、ven 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 JavaScript Object Notation PCEF Policy and Charging Enforcement Function PFD Packet Flow Description PFDF Packe
43、t 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 Description Function (PFDF) and the Policy and Charging Enforcement Function (PCEF). The Gw reference point
44、 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 point are defined in 3GPP TS 23.203 2. 4.2 Gw reference model The Gw reference point is defined between the
45、 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.213 3. ETSI ETSI TS 129 251 V14.2.0 (2018-01)83GPP TS 29.251 version 14.2.0 Release 14PFDFg3Gwg3PCEFg3Figure 4
46、.2.1: Gw reference model 4.3 Functional elements 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 detection wh
47、en 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.2 of
48、 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 over Gw
49、 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“ and “Combination mode“) At the time a PCC 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 applic
