1、 ETSI TS 129 250 V14.2.0 (2018-01) LTE; Nu reference point between SCEF and PFDF for sponsored data connectivity (3GPP TS 29.250 version 14.2.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 129 250 V14.2.0 (2018-01)13GPP TS 29.250 version 14.2.0 Release 14Reference RTS/TSGC-0329250ve20 Keywords L
2、TE 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from:
3、 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 present document shall not be modified without the prior written authorization of ETSI. In case of any existing or percei
4、ved 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 revisi
5、on 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 in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/Commite
6、eSupportStaff.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 aut
7、horization of 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
8、 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 ETSI TS 129 250 V14.2.0 (2018-01)23GPP TS 29.250 version 14.2.0 Release 14Intellectual Prope
9、rty Rights Essential 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
10、 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 searche
11、s, 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
12、 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
13、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
14、 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 http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the pres
15、ent 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
16、 except when used in direct citation. ETSI ETSI TS 129 250 V14.2.0 (2018-01)33GPP TS 29.250 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
17、Abbreviations . 7g34 Nu reference point 7g34.1 Overview 7g34.2 Nu reference model 7g34.3 Functional elements 8g34.3.1 PFDF . 8g34.3.2 SCEF . 8g34.4 Procedures over Nu reference point . 8g34.4.1 Management of PFD . 8g35 Nu protocol . 9g35.1 Introduction 9g35.2 Transport layer . 9g35.3 Application del
18、ivery layer 10g35.3.1 General 10g35.3.2 HTTP status codes 10g35.3.3 Methods 10g35.3.4 Resources and URI design 10g35.3.5 HTTP request/response formats 11g35.3.5.1 General 11g35.3.5.2 POST /nuapplication/provisioning 11g35.4 Specific application communication 13g35.4.1 General 13g35.4.2 Content type
19、13g35.4.3 JSON provisioning fields 13g35.4.3.1 General 13g35.4.4 Void 14g35.4.5 JSON errors and informational response fields 14g35.4.5.1 General 14g35.4.6 JSON report fields 14g35.4.6.1 General 14g35.4.6.2 pfd-reports . 15g35.4.6.3 application-ids . 15g35.5 PFDF discovery 15g36 Secure communication
20、 . 15g3Annex A (informative): JSON Schema . 16g3A.1 Provisioning schema. 16g3A.2 Error and Informational response schema 17g3Annex B (informative): Call Flows . 20g3B.1 General . 20g3B.2 Provisioning of PFDs . 20g3ETSI ETSI TS 129 250 V14.2.0 (2018-01)43GPP TS 29.250 version 14.2.0 Release 14Annex C
21、 (informative): Change history . 21g3History 22g3ETSI ETSI TS 129 250 V14.2.0 (2018-01)53GPP TS 29.250 version 14.2.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work
22、 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
23、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 change
24、s have been incorporated in the document. ETSI ETSI TS 129 250 V14.2.0 (2018-01)63GPP TS 29.250 version 14.2.0 Release 141 Scope The present document provides the stage 3 specification of the Nu reference point. The functional requirements and the stage 2 specifications of the Nu reference point are
25、 specified in 3GPP TS 23.682 2. The Nu reference point lies between the Packet Flow Description Function (PFDF) and the Service Capability Exposure Function (SCEF). 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present doc
26、ument. - 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
27、(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 TS 23.682: “Architecture enhancements to facilitate communications with packet dat
28、a networks and applications“. 3 3GPP TS 23.203: “Policy and charging control architecture“. 4 3GPP TS 29.213: “Policy and Charging Control signalling flows and QoS parameter mapping“. 5 3GPP TS 33.210: “3G security; Network Domain Security (NDS); IP network layer security“. 6 IETF RFC 2818: “HTTP Ov
29、er TLS“. 7 IETF RFC 793: “Transmission Control Protocol“. 8 Void. 9 3GPP TS 29.251: “Gw and Gwn reference points for sponsored data connectivity“. 10 IETF RFC 3986: “Uniform Resource Identifier (URI): Generic Syntax“. 11 IETF RFC 7159: “The JavaScript Object Notation (JSON) Data Interchange Format“.
30、 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 7230: “Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing“. 14 IETF RFC 7231: “Hype
31、rtext Transfer Protocol (HTTP/1.1): Semantics and Content“. 15 IETF RFC 7232: “Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests“. 16 IETF RFC 7233: “Hypertext Transfer Protocol (HTTP/1.1): Range Requests“. 17 IETF RFC 7234: “Hypertext Transfer Protocol (HTTP/1.1): Caching“. 18 IETF RFC 7
32、235: “Hypertext Transfer Protocol (HTTP/1.1): Authentication“. ETSI ETSI TS 129 250 V14.2.0 (2018-01)73GPP TS 29.250 version 14.2.0 Release 143 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 followin
33、g 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. 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 3). 3.2 A
34、bbreviations 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 JavaScript Object Notation PCEF Poli
35、cy and Charging Enforcement Function PFD Packet Flow Description PFDF Packet Flow Description Function SCEF Service Capability Exposure Function TDF Traffic Detection Function 4 Nu reference point 4.1 Overview The Nu reference point is located between the Packet Flow Description Function (PFDF) and
36、the Service Capability Exposure Function (SCEF). The Nu reference point is used for provisioning of PFDs from the SCEF to the PFDF and reporting the result of the PFD Management from the PFDF to the SCEF. The stage 2 level requirements for the Nu reference point are defined in 3GPP TS 23.682 2. 4.2
37、Nu reference model The Nu reference point is defined between the SCEF and the PFDF. 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 4. SCEFg3Nug3PFDFg3Figure 4.2.1: Nu refere
38、nce model ETSI ETSI TS 129 250 V14.2.0 (2018-01)83GPP TS 29.250 version 14.2.0 Release 144.3 Functional elements 4.3.1 PFDF The PFDF (Packet Flow Description Function) is a functional element which receives and manages the PFDs associated to application identifier (s) from the SCEF via the Nu refere
39、nce point. The PFDF provisions PFDs for the corresponding application identifier (s) to the PCEF/TDF as defined in 3GPP TS 23.203 3 and 3GPP TS 29.251 9. 4.3.2 SCEF The SCEF (Service Capability Exposure Function) is a functional element which provides means to securely expose the services and capabi
40、lities provided by the 3GPP network interfaces. The SCEF shall support the management of PFDs provided by the 3rdparty SCS/AS. The SCEF may provision the PFDs to the PFDF via the Nu reference point. 4.4 Procedures over Nu reference point 4.4.1 Management of PFD The PFDs associated with application i
41、dentifier (s) may be created, updated or removed in the PFDF by the third party SCS/AS via the SCEF as defined in 3GPP TS 23.682 2. If the SCEF receives one or more sets of PFDs for external application identifier (s) provisioned by the third party SCS/AS, which is authorized to perform the manageme
42、nt of PFDs based on operator policies, the SCEF shall: - If the external application identifier(s) is different from the application identifier(s) known at the PFDF, translate the external application identifier(s) to the application identifier(s) known at the PFDF; and - may check if the allowed de
43、lay satisfies the required SLA against the minimum allowed delay as defined in 3GPP TS 23.682 2; and - send an HTTP POST message to the PFDF including the provisioned PFD changes for the the application identifier (s) within the body of the HTTP POST as described in subclause 5.3.5.2. NOTE 1: It is
44、up to operator configuration whether to use different external application identifiers that require a mapping to application identifiers known at the PFDF. The external application identifier can be the same as the application identifier known at the PFDF. Upon receipt of the HTTP request for the pr
45、ovisioning operation from the SCEF, the PFDF shall perform the following steps: - If an allowed delay is received for an application identifier, for Pull mode as defined in 3GPP TS 29.251 9, the PFDF shall compare the allowed delay with the configured caching time which is: - a caching time value co
46、nfigured for that application identifier; or - the default caching time value if no caching time value is configured for that application identifier. - Then if the PFDF cannot ensure the PCEF/TDF will pull the PFDs in time (i.e. allowed delay is shorter than the caching time), the PFDF shall within
47、the HTTP response send a failure reason and that caching time value used in the comparison and may still store (create/update/remove) the PFDs for this application identifier. NOTE 2: In the Combination mode as defined in 3GPP TS 29.251 9, the PFDF can check the received allowed delay against the ca
48、ching time but will always store (create/update/remove) the PFDs. - In the Pull mode as defined in 3GPP TS 29.251 9, for the application identifier(s) without the need to send failure reason; or in the Push or Combination mode as defined in 3GPP TS 29.251 9, for received application identifier(s), t
49、he PFDF shall: ETSI ETSI TS 129 250 V14.2.0 (2018-01)93GPP TS 29.250 version 14.2.0 Release 14- delete all the PFD(s) for the application identifier(s) where the removal-flag is also provided and set to true; - update the existing PFD(s) if a new PFD(s) with the same PFD identifier(s) is received , add new PFD(s) if the new PFD(s) with a new PFD identifier(s) is received, and/or delete an existing PFD(s) if the same PFD identifier(s) without any content is received, where the partial-flag is also provided an
