ETSI TS 129 551 V15.5.0 (2019-10)

5G; 5G System; Packet Flow Description Management Service; Stage 3 (3GPP TS 29.551 version 15.5.0 Release 15)

RTS/TSGC-0329551vf50

General Information

• Status: Published
• Publication Date: 13-Oct-2019
• Technical Committee: 3GPP CT 3 - Interworking with external networks (formely CN3)
• Current Stage: 12 - Completion
• Completion Date: 14-Oct-2019

Standards Content (Sample)

ETSI TS 129 551 V15.5.0 (2019-10)






TECHNICAL SPECIFICATION
5G;
5G System;
Packet Flow Description Management Service;
Stage 3
(3GPP TS 29.551 version 15.5.0 Release 15)



---------------------- Page: 1 ----------------------
3GPP TS 29.551 version 15.5.0 Release 15 1 ETSI TS 129 551 V15.5.0 (2019-10)



Reference
RTS/TSGC-0329551vf50
Keywords
5G
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
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 perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision 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/CommiteeSupportStaff.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 ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2019.
All rights reserved.

DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3GPP TS 29.551 version 15.5.0 Release 15 2 ETSI TS 129 551 V15.5.0 (2019-10)
Intellectual Property Rights
Essential 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 (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 searches, 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 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 constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
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 identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and 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 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

---------------------- Page: 3 ----------------------
3GPP TS 29.551 version 15.5.0 Release 15 3 ETSI TS 129 551 V15.5.0 (2019-10)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions, symbols and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Packet Flow Description Management Service . 7
4.1 Service Description . 7
4.1.1 Overview . 7
4.1.2 Service Architecture . 7
4.1.3 Network Functions . 8
4.1.3.1 Packet Flow Description Function (PFDF) . 8
4.1.3.2 NF Service Consumers . 8
4.2 Service Operations . 8
4.2.1 Introduction. 8
4.2.2 Nnef_PFDmanagement_Fetch Service Operation . 9
4.2.2.1 General . 9
4.2.2.2 Retrieval of PFDs . 9
4.2.3 Nnef_PFDmanagement_Subscribe Service Operation . 10
4.2.3.1 General . 10
4.2.3.2 Subscription for event notifications on PFDs change . 10
4.2.4 Nnef_PFDmanagement_Notify Service Operation . 10
4.2.4.1 General . 10
4.2.4.2 Notification of PFD change. 11
4.2.5 Nnef_PFDmanagement_Unsubscribe Service Operation . 11
4.2.5.1 General . 11
4.2.5.2 Unsubscribe from event notifications on PFDs change. 11
5 Nnef_PFDmanagement API . 12
5.1 Introduction . 12
5.2 Usage of HTTP . 12
5.2.1 General . 12
5.2.2 HTTP standard headers . 12
5.2.2.1 General . 12
5.2.2.2 Content type . 12
5.2.3 HTTP custom headers . 12
5.3 Resources . 13
5.3.1 Resource Structure . 13
5.3.2 Resource: PFD of applications. 13
5.3.2.1 Description . 13
5.3.2.2 Resource definition . 14
5.3.2.3 Resource Standard Methods . 14
5.3.2.3.1 GET . 14
5.3.2.4 Resource Custom Operations . 14
5.3.3 Resource: Individual application PFD . 14
5.3.3.1 Description . 14
5.3.3.2 Resource definition . 14
5.3.3.3 Resource Standard Methods . 15
5.3.3.3.1 GET . 15
5.3.3.4 Resource Custom Operations . 15
5.3.4 Resource: PFD subscriptions . 15
ETSI

---------------------- Page: 4 ----------------------
3GPP TS 29.551 version 15.5.0 Release 15 4 ETSI TS 129 551 V15.5.0 (2019-10)
5.3.4.1 Description . 15
5.3.4.2 Resource definition . 15
5.3.4.3 Resource Standard Methods . 16
5.3.4.3.1 POST . 16
5.3.4.4 Resource Custom Operations . 16
5.3.5 Resource: Individual PFD subscription . 16
5.3.5.1 Description . 16
5.3.5.2 Resource definition . 16
5.3.5.3 Resource Standard Methods . 16
5.3.5.3.1 DELETE . 16
5.3.5.4 Resource Custom Operations . 17
5.4 Custom Operations without associated resources. 17
5.5 Notifications . 17
5.5.1 General . 17
5.5.2 PFD Change Notification . 17
5.5.2.1 Description . 17
5.5.2.2 Target URI . 17
5.5.2.3 Standard Methods . 18
5.5.2.3.1 POST . 18
5.6 Data Model . 18
5.6.1 General . 18
5.6.2 Structured data types . 19
5.6.2.1 Introduction . 19
5.6.2.2 Type: PfdDataForApp . 19
5.6.2.3 Type: PfdSubscription . 20
5.6.2.4 Type: PfdChangeNotification . 20
5.6.2.5 Type: PfdContent . 20
5.6.2.6 Type: PfdChangeReport . 21
5.6.3 Simple data types and enumerations . 21
5.6.3.1 Introduction . 21
5.6.3.2 Simple data types . 21
5.7 Error handling . 21
5.7.1 General . 21
5.7.2 Protocol Errors . 21
5.7.3 Application Errors . 21
5.8 Feature negotiation . 22
5.9 Security . 22
Annex A (normative): OpenAPI specification . 23
A.1 General . 23
A.2 Nnef_PFDmanagement API . 23
Annex B (informative): Change history . 29
History . 30

ETSI

---------------------- Page: 5 ----------------------
3GPP TS 29.551 version 15.5.0 Release 15 5 ETSI TS 129 551 V15.5.0 (2019-10)
Foreword
This Technical Specification has 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
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 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 the document.

ETSI

---------------------- Page: 6 ----------------------
3GPP TS 29.551 version 15.5.0 Release 15 6 ETSI TS 129 551 V15.5.0 (2019-10)
1 Scope
The present document provides the stage 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 Architecture 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 functionality 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 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 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.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: "5G 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 Interchange Format".
[9] OpenAPI: "OpenAPI 3.0.0 Specification", https://github.com/OAI/OpenAPI-
Specification/blob/master/versions/3.0.0.md.
[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".
[13] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3".
[14] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
[15] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
[16] IETF RFC 7807: "Problem Details for HTTP APIs".
[17] 3GPP TR 21.900: "Technical Specification Group working methods".
ETSI

---------------------- Page: 7 ----------------------
3GPP TS 29.551 version 15.5.0 Release 15 7 ETSI TS 129 551 V15.5.0 (2019-10)
3 Definitions, 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].
3.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 abbreviation, if any, in
3GPP TR 21.905 [1].
JSON JavaScript Object Notation
NEF Network Exposure Function
NRF Network Repository Function
PFD Packet Flow Description
PFDF Packet Flow Description Function
SBI Service Based Interface
SMF Session Management Function
4 Packet Flow Description Management Service
4.1 Service Description
4.1.1 Overview
The PFD Management Service, as defined as defined 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
- allows 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 representation model in
Figure 4.1.2-1. PFDF is functionality within NEF.
ETSI

---------------------- Page: 8 ----------------------
3GPP TS 29.551 version 15.5.0 Release 15 8 ETSI TS 129 551 V15.5.0 (2019-10)
NEF
PFDF
Nn
Nnef_PFDmanagement
SMF

Figure 4.1.2-1: Reference Architecture for the Nnef_PFDmanagement Service; SBI representation
NEF
SMF
PFDF
N29

Figure 4.1.2-2: Reference Architecture for the Nnef_PFDmanagement Service; reference point
representation
4.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 consumers 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 defined for the Nnef_PFDmanagement Service are shown in table 4.2.1-1.
ETSI

---------------------- Page: 9 ----------------------
3GPP TS 29.551 version 15.5.0 Release 15 9 ETSI TS 129 551 V15.5.0 (2019-10)
Table 4.2.1-1: Nnef_PFDmanagement Service Operations
Service Operation Name Description Initiated by
Nnef_PFDmanagement_Fetch Provides the PFDs for application SMF
identifier(s) to the NF service consumer.
Nnef_PFDmanagement_Subscribe Allows NF service consumers to subscribe SMF
the notification of events when the PFDs for
application identifier change.
Nnef_PFDmanagement_Notify Notifies NF service consumer to update PFDF
and/or delete the PFDs for application
identifier(s).
Nnef_PFDmanagement_Unsubscribe Allows NF service consumers to SMF
unsubscribe the notification of events.

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 using 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 PFDF.
NF Service
PFDF
Consumer
1. GET …/applications
2. 200 OK ()

Figure 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}"; and
- for PFD of a collection of application identifiers, the request URI shall include
"{apiRoot}/nnef-pfdmanagement/v1/applications/" with query parameters indicating the requested
application identifier(s).
2. On success, "200 OK" shall be returned; the payload body of GET response shall contain a representation of
"Individual application PFD" resource or "PFD of applications" resource for the requested application
identifier(s). If the resource of one or more requested application identifier(s) is not provided in the response, the
SMF shall remove the PFD(s) of the requested application identifier(s) which is not included in the response.

On failure, one of the HTTP status code listed in table 5.3.2.3.1-3 or table 5.3.3.3.1-3 shall be returned. For "404
Not Found", the NF service consumer shall remove:
ETSI

---------------------- Page: 10 ----------------------
3GPP TS 29.551 version 15.5.0 Release 15 10 ETSI TS 129 551 V15.5.0 (2019-10)
- all the PFD(s) existing in the NF service consumer if the request is for PFD of all application identifiers;
- the PFD(s) of the requested application identifier(s) in the NF service consumer if the request is for PFD of
individual application identifier or a collection of application identifiers.
4.2.3 Nnef_PFDmanagement_Subscribe Service Operation
4.2.3.1 General
The Nnef_PFDmanagement_Subscribe service operation enables NF service consumer to subscribe the notification of
events when the PFDs for application identifier change.
4.2.3.2 Subscription for event notifications on PFDs change
This procedure as shown in Figure 4.2.3.2-1 is used to subscribe the notification of events when the PFDs for
application ide
...