1、 ETSI TS 129 551 V15.0.0 (2018-07) 5G; 5G System; Packet Flow Description Management Service; Stage 3 (3GPP TS 29.551 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 129 551 V15.0.0 (2018-07)13GPP TS 29.551 version 15.0.0 Release 15Reference DTS/TSGC-0329551vf00 Keywords 5G ETSI 650
2、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: http:/www.e
3、tsi.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 differen
4、ce 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
5、 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/CommiteeSupportStaf
6、f.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 o
7、f 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 LTETMare trademarks of ETSI registered for the benefit of
8、 its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 129 551 V15.0.0 (2018-07)23GPP TS 29.551 version 15.0.0 Release 15Intellectual Property Rights E
9、ssential patents IPRs essential or potentially essential to normative deliverables 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 (I
10、PRs); 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 bee
11、n 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 tradename
12、s 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 constitute
13、 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 3GPP iden
14、tities, 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 docume
15、nt “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 wh
16、en used in direct citation. ETSI ETSI TS 129 551 V15.0.0 (2018-07)33GPP TS 29.551 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 6g33.1 Definitions 6g33.2 A
17、bbreviations . 7g34 Packet Flow Description Management Service 7g34.1 Service Description 7g34.1.1 Overview 7g34.1.2 Service Architecture . 7g34.1.3 Network Functions 8g34.1.3.1 Packet Flow Description Function (PFDF) . 8g34.1.3.2 NF Service Consumers 8g34.2 Service Operations . 8g34.2.1 Introductio
18、n. 8g34.2.2 Nnef_PFDmanagement_Fetch Service Operation 8g34.2.2.1 General 8g34.2.2.2 Retrieval of PFDs 8g34.2.3 Nnef_PFDmanagement_Subscribe Service Operation . 9g34.2.3.1 General 9g34.2.3.2 Subscription for event notifications on PFDs change . 9g34.2.4 Nnef_PFDmanagement_Notify Service Operation .
19、10g34.2.4.1 General 10g34.2.4.2 Notification of PFD change. 10g34.2.5 Nnef_PFDmanagement_Unsubscribe Service Operation . 11g34.2.5.1 General 11g34.2.5.2 Unsubscribe from event notifications on PFDs change. 11g35 Nnef_PFDmanagement API . 11g35.1 Introduction 11g35.2 Usage of HTTP . 12g35.2.1 General
20、12g35.2.2 HTTP standard headers . 12g35.2.2.1 General 12g35.2.2.2 Content type 12g35.2.3 HTTP custom headers . 12g35.3 Resources . 12g35.3.1 Resource Structure 12g35.3.2 Resource: PFD of applications 13g35.3.2.1 Description 13g35.3.2.2 Resource definition . 13g35.3.2.3 Resource Standard Methods 13g3
21、5.3.2.3.1 GET . 13g35.3.2.4 Resource Custom Operations 14g35.3.3 Resource: Individual application PFD 14g35.3.3.1 Description 14g35.3.3.2 Resource definition . 14g35.3.3.3 Resource Standard Methods 14g35.3.3.3.1 GET . 14g35.3.3.4 Resource Custom Operations 14g35.3.4 Resource: PFD subscriptions 15g35
22、.3.4.1 Description 15g3ETSI ETSI TS 129 551 V15.0.0 (2018-07)43GPP TS 29.551 version 15.0.0 Release 155.3.4.2 Resource definition . 15g35.3.4.3 Resource Standard Methods 15g35.3.4.3.1 POST . 15g35.3.4.4 Resource Custom Operations 15g35.3.5 Resource: Individual PFD subscription 16g35.3.5.1 Descriptio
23、n 16g35.3.5.2 Resource definition . 16g35.3.5.3 Resource Standard Methods 16g35.3.5.3.1 DELETE 16g35.3.5.4 Resource Custom Operations 16g35.4 Custom Operations without associated resources. 16g35.5 Notifications . 16g35.5.1 General 16g35.5.2 PFD Change Notification 17g35.5.2.1 Description 17g35.5.2.
24、2 Target URI 17g35.5.2.3 Standard Methods . 17g35.5.2.3.1 POST . 17g35.6 Data Model . 18g35.6.1 General 18g35.6.2 Structured data types . 18g35.6.2.1 Introduction . 18g35.6.2.2 Type: PfdDataForApp . 18g35.6.2.3 Type: PfdSubscription . 19g35.6.2.4 Type: PfdChangeNotification . 19g35.6.2.5 Type: PfdCo
25、ntent 19g35.6.2.6 Type: PfdChangeReport 20g35.6.3 Simple data types and enumerations . 20g35.6.3.1 Introduction . 20g35.6.3.2 Simple data types 20g35.6.3.3 Enumeration: 20g35.6.3.4 Enumeration: 20g35.7 Error handling 20g35.7.1 General 20g35.7.2 Protocol Errors 21g35.7.3 Application Errors 21g35.8 Fe
26、ature negotiation . 21g3Annex A (normative): OpenAPI specification . 22g3A.1 General . 22g3A.2 Nnef_PFDmanagement API . 22g3Annex B (informative): Change history . 26g3History 27g3ETSI ETSI TS 129 551 V15.0.0 (2018-07)53GPP TS 29.551 version 15.0.0 Release 15Foreword This Technical Specification has
27、 been produced by the 3rd Generation 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 iden
28、tifying 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 incremented for all chang
29、es 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 551 V15.0.0 (2018-07)63GPP TS 29.551 version 15.0.0 Release 151 Scope The present document provides the stage
30、 3 specification of the PFD Management Service of 5G system. The stage 2 definition and related procedures of the PFD Management Service are contained in 3GPP TS 23.502 3 and 3GPP TS 23.503 4. The 5G System Architecture is defined in 3GPP TS 23.501 2. The Technical Realization of the Service Based A
31、rchitecture and the Principles and Guidelines for Services Definition of the 5G System are specified in 3GPP TS 29.500 5 and 3GPP TS 29.501 6. The Packet Flow Description Function (PFDF) provides the PFD Management Service to the NF consumers (i.e. Session Management Function). The PFDF is functiona
32、lity within the NEF. 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 non-specific. - For a speci
33、fic 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 same Release as the present
34、 document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 23.501: “System Architecture for the 5G System; Stage 2“. 3 3GPP TS 23.502: “Procedures for the 5G System; Stage 2“. 4 3GPP TS 23.503: “Policy and Charging Control Framework for the 5G System; Stage 2“. 5 3GPP TS 29.500: “5
35、G System; Technical Realization of Service Based Architecture; Stage 3“. 6 3GPP TS 29.501: “5G System; Principles and Guidelines for Services Definition; Stage 3“. 7 IETF RFC 7540: “Hypertext Transfer Protocol Version 2 (HTTP/2)“. 8 IETF RFC 8259: “The JavaScript Object Notation (JSON) Data Intercha
36、nge Format“. 9 OpenAPI: “OpenAPI 3.0.0 Specification“, https:/ 10 3GPP TS 29.571: “5G System; Common Data Types for Service Based Interfaces Stage 3“. 11 3GPP TS 29.122: “T8 reference point for Northbound APIs“. 12 3GPP TS 29.251: “Gw and Gwn reference points for sponsored data connectivity“. 3 Defi
37、nitions, symbols 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 TR 21.905 1. ETSI ET
38、SI TS 129 551 V15.0.0 (2018-07)73GPP TS 29.551 version 15.0.0 Release 153.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 takes precedence over the definition of the same ab
39、breviation, if any, in 3GPP TR 21.905 1. API Application Programming Interface HTTP Hypertext Transfer Protocol NF Network Function PFDF Packet Flow Description Function 4 Packet Flow Description Management Service 4.1 Service Description 4.1.1 Overview The PFD Management Service, as defined as defi
40、ned in 3GPP TS 23.501 2, 3GPP TS 23.502 3 and 3GPP TS 23.503 4, is provided by the Packet Flow Description Function (PFDF). The only known NF Service Consumer is the SMF. This service: - allows an SMF to subscribe to and unsubscribe from PFD changes; - notifies an SMF about the changed PFDs; and - a
41、llows an SMF to retrieve PFDs. 4.1.2 Service Architecture The 5G System Architecture is defined in 3GPP TS 23.501 2. The Policy and Charging related 5G architecture is also described in 3GPP TS 23.503 4. The PFD Management Service is provided by the PFDF to the SMF and shown in the SBI representatio
42、n model in Figure 4.1.2-1. PFDF is functionality within NEF. Figure 4.1.2-1: Reference Architecture for the Nnef_PFDmanagement Service; SBI representation Figure 4.1.2-2: Reference Architecture for the Nnef_PFDmanagement Service; reference point representation NEF PFDF NnSMF Nnef_PFDmanagement NEF P
43、FDF SMF N29 ETSI ETSI TS 129 551 V15.0.0 (2018-07)83GPP TS 29.551 version 15.0.0 Release 154.1.3 Network Functions 4.1.3.1 Packet Flow Description Function (PFDF) The Packet Flow Description Function (PFDF): - provides PFDs associated with one or more Application Identifiers; and - allows NF consume
44、rs to subscribe to and unsubscribe from the notification of changes of PFDs for Application Identifier. 4.1.3.2 NF Service Consumers The SMF shall support: - requesting and receiving the PFD(s) for one or more Application Identifiers. 4.2 Service Operations 4.2.1 Introduction Service operations defi
45、ned for the Nnef_PFDmanagement Service are shown in table 4.2.1-1. Table 4.2.1-1: Nnef_PFDmanagement Service Operations Service Operation Name Description Initiated by Nnef_PFDmanagement_Fetch Provides the PFDs for application identifier(s) to the NF service consumer. SMF Nnef_PFDmanagement_Subscrib
46、e Allows NF service consumers to subscribe the notification of events when the PFDs for application identifier change. SMF Nnef_PFDmanagement_Notify Notifies NF service consumer to update and/or delete the PFDs for application identifier(s). PFDF Nnef_PFDmanagement_Unsubscribe Allows NF service cons
47、umers to unsubscribe the notification of events. SMF 4.2.2 Nnef_PFDmanagement_Fetch Service Operation 4.2.2.1 General The Nnef_PFDmanagement_Fetch service operation provides a means for the NF service consumer to retrieve the PFDs for one or more application identifier(s). The following procedures u
48、sing the Nnef_PFDmanagement_Fetch service operation are supported: - Retrieval of PFDs. 4.2.2.2 Retrieval of PFDs This procedure as shown in Figure 4.2.2.2-1 is used to retrieve PFDs for an application identifier from the PFDFg23409g23395ETSI ETSI TS 129 551 V15.0.0 (2018-07)93GPP TS 29.551 version
49、15.0.0 Release 15Figure 4.2.2.2-1: Retrieval of PFDs 1. The NF service consumer (i.e. SMF) shall send a GET request to the resource representing the PFD for application identifier(s) to be required: - for PFD of individual application identifier, the request URI shall include “apiRoot/nnef-pfdmanagement/v1/applications/appId“; - for PFD of all application identifiers, the request URI shall include “apiRoot/nnef-pfdmanagement/v1/applications“; and - fo
