ETSI TS 129 521 V17.5.0 (2022-07)

TECHNICAL SPECIFICATION
5G;
5G System;
Binding Support Management Service;
Stage 3
(3GPP TS 29.521 version 17.5.0 Release 17)


3GPP TS 29.521 version 17.5.0 Release 17 1 ETSI TS 129 521 V17.5.0 (2022-07)

Reference
RTS/TSGC-0329521vh50
Keywords
5G
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 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

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
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
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 2022.
All rights reserved.
ETSI
3GPP TS 29.521 version 17.5.0 Release 17 2 ETSI TS 129 521 V17.5.0 (2022-07)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are 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 Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
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.
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.
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
3GPP TS 29.521 version 17.5.0 Release 17 3 ETSI TS 129 521 V17.5.0 (2022-07)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
2 References . 7
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Binding Support Management Service . 8
4.1 Service Description . 8
4.1.1 Overview . 8
4.1.2 Service Architecture . 9
4.1.3 Network Functions . 10
4.1.3.1 Binding Support Function (BSF) . 10
4.1.3.2 NF Service Consumers . 10
4.2 Service Operations . 11
4.2.1 Introduction. 11
4.2.2 Nbsf_Management_Register Service Operation . 12
4.2.2.1 General . 12
4.2.2.2 Register a new PCF for a PDU Session binding information. 12
4.2.2.3 Register a new PCF for a UE binding information . 15
4.2.3 Nbsf_Management_Deregister Service Operation . 16
4.2.3.1 General . 16
4.2.3.2 Deregister an individual PCF for a PDU Session binding information . 16
4.2.3.3 Deregister an individual PCF for a UE binding information . 17
4.2.4 Nbsf_Management_Discovery Service Operation . 17
4.2.4.1 General . 17
4.2.4.2 Retrieve the PCF binding information for a PDU session. 18
4.2.4.3 Retrieve the PCF binding information for a UE . 19
4.2.5 Nbsf_Management_Update Service Operation. 19
4.2.5.1 General . 19
4.2.5.2 Update an existing PCF for a PDU Session binding information . 20
4.2.5.3 Update an existing PCF for a UE binding information . 21
4.2.6 Nbsf_Management_Subscribe Service Operation . 22
4.2.6.1 General . 22
4.2.6.2 Creating a new subscription . 22
4.2.6.3 Modifying an existing subscription . 23
4.2.7 Nbsf_Management_Unsubscribe Service Operation . 24
4.2.7.1 General . 24
4.2.7.2 Unsubscription from event notifications . 24
4.2.8 Nbsf_Management_Notify Service Operation . 25
4.2.8.1 General . 25
4.2.8.2 Notification about subscribed events . 25
5 Nbsf_Management Service API . 27
5.1 Introduction . 27
5.2 Usage of HTTP . 27
5.2.1 General . 27
5.2.2 HTTP standard headers . 27
5.2.2.1 General . 27
5.2.2.2 Content type . 28
5.2.3 HTTP custom headers . 28
5.2.3.1 General . 28
ETSI
3GPP TS 29.521 version 17.5.0 Release 17 4 ETSI TS 129 521 V17.5.0 (2022-07)
5.3 Resources . 28
5.3.1 Resource Structure . 28
5.3.2 Resource: PCF for a PDU Session Bindings . 30
5.3.2.1 Description . 30
5.3.2.2 Resource definition . 30
5.3.2.3 Resource Standard Methods . 31
5.3.2.3.1 POST . 31
5.3.2.3.2 GET . 31
5.3.3 Resource: Individual PCF for a PDU Session Binding . 32
5.3.3.1 Description . 32
5.3.3.2 Resource definition . 32
5.3.3.3 Resource Standard Methods . 33
5.3.3.3.1 DELETE . 33
5.3.3.3.2 PATCH . 34
5.3.4 Resource: Binding Subscriptions . 35
5.3.4.1 Description . 35
5.3.4.2 Resource definition . 35
5.3.4.3 Resource Standard Methods . 35
5.3.4.3.1 POST . 35
5.3.4.4 Resource Custom Operations . 36
5.3.5 Resource: Individual Binding Subscription . 36
5.3.5.1 Description . 36
5.3.5.2 Resource definition . 36
5.3.5.3 Resource Standard Methods . 36
5.3.5.3.1 PUT . 36
5.3.5.3.2 DELETE . 37
5.3.6 Resource Custom Operations . 38
5.3.7 Resource: PCF for a UE Bindings . 38
5.3.7.1 Description . 38
5.3.7.2 Resource definition . 38
5.3.7.3 Resource Standard Methods . 39
5.3.7.3.1 POST . 39
5.3.7.3.2 GET . 39
5.3.8 Resource: Individual PCF for a UE Binding . 40
5.3.8.1 Description . 40
5.3.8.2 Resource definition . 40
5.3.8.3 Resource Standard Methods . 40
5.3.8.3.1 DELETE . 40
5.3.8.3.2 PATCH . 41
5.4 Custom Operations without associated resources. 42
5.5 Notifications . 42
5.5.1 General . 42
5.5.2 BSF Notification . 42
5.5.2.1 Description . 42
5.5.2.2 Target URI . 43
5.5.2.3 Standard Methods . 43
5.5.2.3.1 POST . 43
5.6 Data Model . 44
5.6.1 General . 44
5.6.2 Structured data types . 45
5.6.2.1 Introduction . 45
5.6.2.2 Type PcfBinding . 46
5.6.2.3 Type PcfBindingPatch . 48
5.6.2.4 Type ParameterCombination. 49
5.6.2.5 Type ExtProblemDetails . 49
5.6.2.6 Type BindingRe sp . 49
5.6.2.7 Type BsfSubscription . 50
5.6.2.8 Type BsfNotification . 50
5.6.2.9 Type BsfEventNotification . 51
5.6.2.10 Type PcfForUeBinding . 52
5.6.2.11 Type PcfForUeBindingPatch . 52
5.6.2.12 Type SnssaiDnnPair . 52
ETSI
3GPP TS 29.521 version 17.5.0 Release 17 5 ETSI TS 129 521 V17.5.0 (2022-07)
5.6.2.13 Type PcfForUeInfo . 53
5.6.2.14 Type PcfForPduSessionInfo . 53
5.6.3 Simple data types and enumerations . 53
5.6.3.1 Introduction . 53
5.6.3.2 Simple data types . 53
5.6.3.3 Enumeration: BindingLevel . 54
5.6.3.4 Void. 54
5.6.3.5 Enumeration: BsfEvent . 54
5.6.4 Data types describing alternative data types or combinations of data types . 54
5.6.4.1 Type: BsfSubscriptionResp . 54
5.7 Error handling . 55
5.7.1 General . 55
5.7.2 Protocol Errors . 55
5.7.3 Application Errors . 55
5.8 Feature negotiation . 55
5.9 Security . 56
Annex A (normative): OpenAPI specification . 57
A.1 General . 57
A.2 Nbsf_Management API . 57
Annex B (informative): Deployment option to support BSF and DRA coexistence due to
network migration . 71
Annex C (informative): Change history . 72
History . 76

ETSI
3GPP TS 29.521 version 17.5.0 Release 17 6 ETSI TS 129 521 V17.5.0 (2022-07)
Foreword
rd
This Technical Specification has been produced by the 3 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
3GPP TS 29.521 version 17.5.0 Release 17 7 ETSI TS 129 521 V17.5.0 (2022-07)
1 Scope
The present specification provides the stage 3 definition of the Binding Support Management Service of the 5G System.
The 5G System Architecture is defined in 3GPP TS 23.501 [2]. The stage 2 definition and related procedures for
Binding Support Management Service is specified in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [4].
The 5G System stage 3 call flows are provided in 3GPP TS 29.513 [5].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition
are specified in 3GPP TS 29.500 [6] and 3GPP TS 29.501 [7].
The Binding Support Management Service is provided by the Binding Support Function (BSF).
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.513: "5G System; Policy and Charging Control signalling flows and QoS parameter
mapping; Stage 3".
[6] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[7] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[8] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)".
[9] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
[10] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces Stage 3".
[11] OpenAPI: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0.
[12] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3".
[13] IETF RFC 7807: "Problem Details for HTTP APIs".
[14] 3GPP TS 29.213: " Policy and Charging Control signalling flows and Quality of Service (QoS)
parameter mapping".
[15] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
[16] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
[17] 3GPP TS 23.527: "5G System; Restoration Procedures".
ETSI
3GPP TS 29.521 version 17.5.0 Release 17 8 ETSI TS 129 521 V17.5.0 (2022-07)
[18] 3GPP TR 21.900: "Technical Specification Group working methods".
[19] 3GPP TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)".
[20] IETF RFC 7396: "JSON Merge Patch".
[21] 3GPP TS 29.512: "5G System; Session Management Policy Control Service; Stage 3".
3 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 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].
5G-RG 5G Residential Gateway
AF Application Function
AM Access and Mobility Management
BSF Binding Support Function
DNN Data Network Name
DRA Diameter Routing Agent
HTTP Hypertext Transfer Protocol
FN-RG Fixed Network Residential Gateway
FQDN Fully Qualified Domain Name
GPSI Generic Public Subscription Identifier
JSON JavaScript Object Notation HTTP Hypertext Transfer Protocol
MAC Media Access Control
NEF Network Exposure Function
NRF Network Repository Function
NWDAF Network Data Analytics Function
PCF Policy Control Function
SMF Session Management Function
S-NSSAI Single Network Slice Selection Assistance Information
SUPI Subscription Permanent Identifier
TSCTSF Time Sensitive Communication and Time Synchronization Function
UDR Unified Data Repository
4 Binding Support Management Service
4.1 Service Description
4.1.1 Overview
The Binding Support Management Service as defined in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [4], is provided by
the Binding Support Function (BSF).
The Nbsf_Management service is used to provide:
ETSI
3GPP TS 29.521 version 17.5.0 Release 17 9 ETSI TS 129 521 V17.5.0 (2022-07)
- a PDU session binding functionality, which ensures that an AF request for a certain PDU Session reaches the
relevant PCF holding that PDU Session information, or ensures that the same PCF is selected for multiple PDU
sessions.
- a PCF for a UE binding functionality, which ensures that an AF request for Access and Mobility related Policy
Authorization for a UE reaches the relevant PCF for a UE holding the AM Policy Association.
- Subscription to notification events about a newly registered or deregistered PCF for a UE or PCF for a PDU
session.
This service:
- allows NF service consumers to register, update and remove binding information;
- allows NF service consumers to retrieve binding information;
- allows NF service consumers to subscribe to notifications of registration/deregistration events of newly
registered or deregistered PCF for a UE or PCF for a PDU session.
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] and 3GPP TS 29.513 [5].
The Binding Support Management Service (Nbsf_Management) is exhibited by the Binding Support Function (BSF).
The known consumers of the Nbsf_Management service are:
- Policy Control Function (PCF)
- Network Exposure Function (NEF)
- Application Function (AF);
- Network Data Analytics Function (NWDAF); and
- Time Sensitivy Communication and Time Synchronization Function (TSCTSF).
As described in 3GPP TS 23.503 [4], the BSF is a function that can be deployed standalone or as a functionality
provided by other network functions, such as PCF, UDR, NRF, SMF.
NOTE 1: The PCF accesses the Nbsf_Management service at the BSF via an internal interface when it is collocated
with BSF.
NOTE 2: The DRA decides to select a BSF based on user IP address range when the DRA has no binding
information for the subscriber to get the relevant PCF for a PDU session address. DRA and BSF
coexistence is described in 3GPP TS 29.513 [5], Annex A.
ETSI
3GPP TS 29.521 version 17.5.0 Release 17 10 ETSI TS 129 521 V17.5.0 (2022-07)
BSF
Nbsf
Nbsf_Management service
PCF NEF AF NWDAF TSCTSF
Figure 4.1.2-1: Reference Architecture for the Nbsf_Management service; SBI representation
NOTE 3: The PCF in the figure represents both, the PCF for a UE and the PCF for a PDU session. The PCF for a
UE and the PCF for a PDU session separately and independently register themselves at the BSF,
regardless they are deployed in the same NF instance or separately in different NF instances.
4.1.3 Network Functions
4.1.3.1 Binding Support Function (BSF)
The BSF:
- stores the binding information for a certain PDU Session;
- stores the binding information for a certain UE;
- enables the subscription to notifications of PCF for a PDU session registration/deregistration events;
- enables the subscription to notifications of PCF for a UE registration/deregistration events;and
- enables the discovery of binding information (e.g. the address information of the selected PCF for a PDU
session).
The BSF allows NF service consumers (e.g. PCF) to register, update and remove a binding information, and allows NF
service consumers (e.g. AF, NEF, NWDAF) to discover a binding information (e.g. the address information of the
selected PCF). The BSF also allows NF service consumers (e.g. PCF for a UE, AF, NEF) to subscribe to notifications
of PCF registration/deregistration events.
The BSF can be deployed standalone or collocated with other network functions, such as PCF, UDR, NRF and SMF.
4.1.3.2 NF Service Consumers
The Policy Control Function (PCF):
- The PCF for a PDU session:
a. registers binding information in the BSF for a UE when an IPv4 address and/or IPv6 prefix is allocated, or a
MAC address is used for the PDU session;
b. updates binding information in the BSF when a UE address information is changed for the PDU Session; and
c. removes binding information in the BSF when an IPv4 address and/or IPv6 prefix is released, or a MAC
address is not used for the PDU Session.
- The PCF for a UE:
ETSI
3GPP TS 29.521 version 17.5.0 Release 17 11 ETSI TS 129 521 V17.5.0 (2022-07)
a. registers binding information in the BSF for a UE when an AM Policy Association is established;
b. removes binding information in the BSF when the AM Policy Association is terminated; and
c. subscribes with the BSF to notification of registration/deregistration events of the PCF for a PDU session.
The Network Exposure Function (NEF):
- provides means for the Application Functions to securely interact with the Policy framework for policy control
to 3GPP network. During the procedure, it needs to discover the selected PCF for a PDU session or the selected
PCF for a UE by using the Nbsf_Management_Discovery service operation and the selected PCF for a UE by
using the Nbsf_Management_Subscribe/Notify service operations.
The Application Function (AF):
- discovers the selected PCF for a PDU session or the selected PCF for a UE by using the
Nbsf_Management_Discovery service operation and the selected PCF for a UE by using the
Nbsf_Management_Subscribe/Notify service operations when it is allowed to interact directly with the policy
framework for policy control.
The Network Data Analytics Function (NWDAF):
- discovers the selected PCF for a PDU session by using the Nbsf_Management_Discovery service operation.
The Time Sensitive Communication and Time Synchronization Function (TSCTSF)
- discovers the selected PCF for a PDU session by using the Nbsf_Management_Discovery service operation and
the selected PCF for a UE by using Nbsf_Management_Subscribe/Notify service operations when it is allowed
to interact with the policy framework for time sensitive communication and time synchronization control.
4.2 Service Operations
4.2.1 Introduction
Table 4.2.1-1: Operations of the Nbsf_Management Service
Service operation name Description Initiated by
Nbsf_Management_Register This service operation is used to register the binding NF service consumer
information for a PDU session or a UE. (e.g., PCF)
Nbsf_Management_Deregister This service operation is used to deregister the binding NF service consumer
information for a PDU session or a UE. (PCF)
Nbsf_Management_Discovery This service operation is used by an NF service NF service consumer
consumer or NWDAF to discover a selected PCF for a (e.g., NEF, AF,
PDU session or a selected PCF for a UE. NWDAF)
Nbsf_Management_Update This service operation is used to update an existing NF service consumer
binding information for a PDUsession or a UE. (e.g., PCF)
Nbsf_Management_Subscribe This service operation is used by an NF service NF service consumer
consumer to subscribe or to modify a subscription for (e.g., NEF, AF, PCF)
event notifications of PCF for the UE or PCF for the PDU
session binding related events.
Nbsf_Management_Unsubscrib This service operation is used by an NF service NF service consumer
e consumer to terminate a previous subscription. (e.g., NEF, AF, PCF)
Nbsf_Management_Notify This service operation is used by the BSF to notify BSF
binding related event(s) to the NF service consumer
which has subscribed to such event(s).

ETSI
3GPP TS 29.521 version 17.5.0 Release 17 12 ETSI TS 129 521 V17.5.0 (2022-07)
4.2.2 Nbsf_Management_Register Service Operation
4.2.2.1 General
This service operation allows a NF service consumer (e.g. PCF for a PDU session) to register the session binding
information for a UE in the BSF by providing the user identity, the DNN, the UE address(es) and the selected PCF
address for a certain PDU Session to the BSF, and BSF stores the information.
If the BindingUpdate feature is not supported and the NF service consumer (e.g. PCF for a PDU session) receives a new
UE address (e.g. IPv6 prefix) and has already registered session binding information for this PDU session, the NF
service consumer (e.g. PCF for a PDU session) shall register a new session binding information in the BSF.
If the SamePcf feature or the ExtendedSamePcf feature is supported, this service operation allows the NF service
consumer (e.g. PCF for a PDU session) to check whether PCF addressing information for Npcf_SMPolicyControl
service is already registered in the BSF by another PCF for a combination of the UE ID, DNN and S-NSSAI parameters
of the PDU session.
This service operation also allows a NF service consumer (e.g. PCF for a UE) to register PCF for a UE binding
information for a UE in the BSF, by providing to the BSF the user identity and the selected PCF address for a certain
UE, and the BSF stores the information.
The following procedures using the Nbsf_Management_Registration service operation are supported:
- Register a new PCF for a PDU Session binding information.
- Register a new PCF for a UE binding information.
4.2.2.2 Register a new PCF for a PDU Session binding information
NF Service
BSF
Consumer
1. POST ./pcfBindings
2. 201 Created
Figure 4.2.2.2-1: NF service consumer register a new PCF for a PDU Session binding information
The NF service consumer shall invoke the Nbsf_Management_Register service operation to register the PDU session
binding information for a UE in the BSF. The NF service consumer shall send for this an HTTP POST request with
"{apiRoot}/nbsf-management//pcfBindings" as Resource URI representing the "PCF for a PDU Session
Bindings", as shown in figure 4.2.2.2-1, step 1, to create a binding information for an "Individual PCF for a PDU
Session Binding" according to the information (e.g. UE address(es), SUPI, GPSI, DNN, S-NSSAI) in the message
body. When the "ExtendedSamePcf" feature is not supported, the "PcfBinding" data structure provided in the request
body shall include:
- if the "MultiUeAddr" feature is not supported or not yet known, address information of the served UE consisting
of:
(i) either IP address information consisting of:
+ the IPv4 address encoded as "ipv4Addr" attribute; and/or
+ the /128 IPv6 address, the IPv6 address prefix or an IPv6 prefix shorter than /64 encoded as "ipv6Prefix"
attribute; or
(ii) the MAC address encoded as "macAddr48" attribute;
Otherwise, address information of the served UE consisting of:
ETSI
------------------
...