1、 ETSI TS 129 250 V14.0.0 (2017-07) LTE; Nu reference point between SCEF and PFDF for sponsored data connectivity (3GPP TS 29.250 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 129 250 V14.0.0 (2017-07)13GPP TS 29.250 version 14.0.0 Release 14Reference DTS/TSGC-0329250ve00 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 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
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.0.0 (2017-07)23GPP TS 29.250 version 14.0.0 Release 14Intellectual Prope
9、rty 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 members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Es
10、sential, 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 carrie
11、d 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. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Genera
12、tion 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 being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP a
13、nd 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“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting
14、 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 250 V14.0.0 (2017-07)33GPP TS 29.250 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs te
15、rminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Nu reference point 6g34.1 Overview 6g34.2 Nu reference model 6g34.3 Functional elements 6g34.3.1 PFDF . 6g34.3.2 SCEF . 6g34.4 Procedures over Nu reference point . 7
16、g34.4.1 Management of PFD . 7g35 Nu protocol . 7g35.1 Introduction 7g35.2 Transport layer . 8g35.3 Application delivery layer 8g35.3.1 General 8g35.3.2 HTTP status codes 8g35.3.3 Methods 8g35.3.4 Resources and URI design 9g35.3.5 HTTP request/response formats 9g35.3.5.1 General 9g35.3.5.2 POST /nuap
17、plication/provisioning 10g35.4 Specific application communication 12g35.4.1 General 12g35.4.2 Content type 12g35.4.3 JSON provisioning fields 12g35.4.3.1 General 12g35.4.4 Void 12g35.4.5 JSON errors and informational response fields 12g35.4.5.1 General 12g35.4.6 JSON report fields 13g35.4.6.1 Genera
18、l 13g35.5 PFDF discovery 13g36 Secure communication . 13g3Annex A (informative): JSON Schema . 14g3A.1 Provisioning schema. 14g3A.2 Error and Informational response schema 15g3Annex B (informative): Call Flows . 18g3B.1 General . 18g3B.2 Provisioning of PFDs . 18g3Annex C (informative): Change histo
19、ry . 19g3History 20 ETSI ETSI TS 129 250 V14.0.0 (2017-07)43GPP TS 29.250 version 14.0.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 within the TSG and may chang
20、e 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 TSG for information; 2 presen
21、ted 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 changes have been incorporated in t
22、he document. ETSI ETSI TS 129 250 V14.0.0 (2017-07)53GPP TS 29.250 version 14.0.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 specified in 3GPP TS23.682 2
23、. 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 document. - References are either
24、 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 (including a GSM document), a
25、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 data networks and applications“.
26、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 Over TLS“. 7 IETF RFC 793: “Tran
27、smission Control Protocol“. 8 IETF RFC 2616: “Hypertext Transfer Protocol HTTP/1.1“. 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 I
28、nterchange 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. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, th
29、e 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 TR 21.905 1. Packet Flow Description (PFD): A set of information enabling the detection of application traffic prov
30、ided by a 3rdparty service provider (from 3GPP TS 23.203 3). ETSI ETSI TS 129 250 V14.0.0 (2017-07)63GPP TS 29.250 version 14.0.0 Release 143.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 prese
31、nt 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 Packet Flow Description Function SCEF Service Capability Exposure Function TDF Traffi
32、c Detection Function 4 Nu reference point 4.1 Overview The Nu reference point is located between the Packet Flow Description Function (PFDF) and 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
33、 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 Nu reference model The Nu reference point is defined between the SCEF and the PFDF. The relationships between the different functional entities involved ar
34、e 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 reference model 4.3 Functional elements 4.3.1 PFDF The PFDF (Packet Flow Description Function) is a functional element which receives and manages the PFDs associ
35、ated to application identifier (s) from the SCEF via the Nu reference 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 eleme
36、nt which provides means to securely expose the services and capabilities 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. ETSI ETSI TS 129 250 V14.0.0 (2017-
37、07)73GPP TS 29.250 version 14.0.0 Release 144.4 Procedures over Nu reference point 4.4.1 Management of PFD The PFDs associated with application identifier (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 on
38、e or more sets of PFDs for external application identifier (s) provisioned by the third party SCS/AS, which is authorized to perform the management of PFDs based on operator policies, the SCEF shall: - If the external application identifier(s) is different from the application identifier(s) known at
39、 the PFDF, translate the external application identifier(s) to the application identifier(s) known at the PFDF; and - may check if the allowed delay 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
40、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: It is up to operator configuration whether to use different external application identifiers that require a mapping to application identifiers known at the PFDF. T
41、he external application identifier can be the same as the application identifier known at the PFDF. Upon receipt of the HTTP request for the provisioning operation from the SCEF, the PFDF shall perform the following steps: - If an allowed delay is received for an application identifier, for Pull mod
42、e 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 configured for that application identifier; or - the default caching time value if no caching time value is configured for that application identifier. - Then
43、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 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 appli
44、cation identifier. - for the application identifier(s) without the need to send failure reason, the PFDF shall: - delete all the PFDs for the application identifier(s) where the removal-flag is included and set to true; - update the existing PFDs or add new PFDs for the corresponding PFD identifier(
45、s), or delete all of the PFDs for the received PFD identifier(s) without any content, where the partial-flag is included and set to true; - install the new PFDs and remove existing PFDs for the corresponding PFD identifier(s) where the PFDs are provided without any flag; - acknowledge the HTTP POST
46、message by sending a corresponding HTTP response with the appropriate status code as defined in subclause 5.3.2. If the POST operation was successful for at least one application identifier, the PFDF shall respond with an HTTP 200 OK status code. 5 Nu protocol 5.1 Introduction The following layers o
47、f the protocol stack for the Nu reference point between the SCEF and the PFDF are described in subclauses: IETF RFC 793 7 provides the communication service at the transport layer. ETSI ETSI TS 129 250 V14.0.0 (2017-07)83GPP TS 29.250 version 14.0.0 Release 14An optional communication security layer
48、 can be added between the transport and the application delivery layer (see subclause 6). The application delivery layer provides the transport of the specific application communication data using IETF RFC 2616 8. The specific application communication layer constitutes the transport of the JSON con
49、tent type. Figure 5.1.1 illustrates the protocol stack of the RESTful Nu reference point. L1L2Physical layerTCPHTTPJSONSCEFL1L2IPTCPHTTPJSONPFDFIPData link layerNetwork layerTransport layerApplication deliverySpecific application communicationREST-NuFigure 5.1.1: Protocol stack of the RESTful Nu reference point 5.2 Transport layer HTTP is layered over TCP, which provides a reliable transport. For provisioning of PFDs from the SCEF to the PFDF, the SCEF acts as an HTTP client and the PFDF acts as an HTTP server. As a res
