|
TECHNICAL SPECIFICATION
5G;
5G System;
Binding Support Management Service;
Stage 3
(3GPP TS 29.521 version 15.2.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 29.521 version 15.2.0 Release 15 1 ETSI TS 129 521 V15.2.0 (2019-04)
Reference
RTS/TSGC-0329521vf20
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 - 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:
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
If you find errors in the present document, please send your comment to one of the following services:
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.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
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.521 version 15.2.0 Release 15 2 ETSI TS 129 521 V15.2.0 (2019-04)
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.
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 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
.
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.521 version 15.2.0 Release 15 3 ETSI TS 129 521 V15.2.0 (2019-04)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Binding Support 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 Binding Support Function (BSF) . 8
4.1.3.2 NF Service Consumers . 8
4.2 Service Operations . 8
4.2.1 Introduction. 8
4.2.2 Nbsf_Management_Register Service Operation . 9
4.2.2.1 General . 9
4.2.2.2 Register a new PCF Session binding information . 9
4.2.3 Nbsf_Management_Deregister Service Operation . 9
4.2.3.1 General . 9
4.2.3.2 Deregister an individual PCF Session binding information . 10
4.2.4 Nbsf_Management_Discovery Service Operation . 10
4.2.4.1 General . 10
4.2.4.2 Retrieve the PCF Session binding information for a given tuple . 10
5 Nbsf_Management Service API . 11
5.1 Introduction . 11
5.2 Usage of HTTP . 11
5.2.1 General . 11
5.2.2 HTTP standard headers . 11
5.2.2.1 General . 11
5.2.2.2 Content type . 11
5.2.3 HTTP custom headers . 12
5.2.3.1 General . 12
5.3 Resources . 12
5.3.1 Resource Structure . 12
5.3.2 Resource: PCF Session Bindings . 12
5.3.2.1 Description . 12
5.3.2.2 Resource definition . 12
5.3.2.3 Resource Standard Methods . 13
5.3.2.3.1 POST . 13
5.3.2.3.2 GET . 13
5.3.3 Resource: Individual PCF Session Binding . 14
5.4 Custom Operations without associated resources. 15
5.5 Notifications . 15
5.6 Data Model . 15
5.6.1 General . 15
5.6.2 Structured data types . 15
5.6.2.1 Introduction . 15
5.6.2.2 Type PcfBinding . 16
5.6.3 Simple data types and enumerations . 16
5.6.3.1 Introduction . 16
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 29.521 version 15.2.0 Release 15 4 ETSI TS 129 521 V15.2.0 (2019-04)
5.6.3.2 Simple data types . 16
5.7 Error handling . 16
5.8 Feature negotiation . 17
5.9 Security . 17
Annex A (normative): OpenAPI specification . 18
A.1 General . 18
A.2 Nbsf_Management API . 18
Annex B (informative): Deployment option to support BSF and DRA coexistence due to
network migration . 22
Annex C (informative): Change history . 23
History . 24
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 29.521 version 15.2.0 Release 15 5 ETSI TS 129 521 V15.2.0 (2019-04)
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
---------------------- Page: 6 ----------------------
3GPP TS 29.521 version 15.2.0 Release 15 6 ETSI TS 129 521 V15.2.0 (2019-04)
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 3.0.0 Specification", https://github.com/OAI/OpenAPI-
Specification/blob/master/versions/3.0.0.md.
[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".
[n2] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
[n3] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 29.521 version 15.2.0 Release 15 7 ETSI TS 129 521 V15.2.0 (2019-04)
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].
API Application Programming Interface
BSF Binding Support Function
DRA Diameter Routing Agent
HTTP Hypertext Transfer Protocol
NF Network Function
NRF Network Repository Function
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 service is used for the BSF to provide a PDU session binding functionality, which ensures that an AF request
for a certain PDU Session reaches the relevant PCF holding the PDU Session information.
This service:
- Allows NF consumers to register, update and remove the binding information; and
- allows NF consumers to retrieve the binding information.
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).
Known consumers of the Nbsf_management service are:
- Policy Control Function (PCF)
- Network Exposure Function (NEF)
- Application Function (AF)
As described in 3GPP TS 23.503 [4], the BSF is a function that can be deployed standalone or can be the functionality
provided by other network functions, such as PCF, UDR, NRF, SMF.
NOTE: The PCF accesses the Nbsf_management service at the BSF via an internal interface when it is collocated
with BSF.
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 29.521 version 15.2.0 Release 15 8 ETSI TS 129 521 V15.2.0 (2019-04)
BSF
Nbsf
Nbsf_management service
PCF NEF AF
Figure 4.1.2-1: Reference Architecture for the Nbsf_management service; SBI representation
4.1.3 Network Functions
4.1.3.1 Binding Support Function (BSF)
The BSF provides:
- stores the binding information for a certain PDU Session; and
- discovers the selected PCF according to the binding information.
The BSF allows PCFs to register, update and remove the binding information from it, and allows NF consumers to
discover the selected PCF.
The BSF can be deployed standalone or can be collocated with other network functions, such as PCF, UDR, NRF
andSMF.
4.1.3.2 NF Service Consumers
The Policy Control Function (PCF):
- registers and deregisters the binding information in BSF for a UE when an IP address is allocated , updated or
released for a PDU Session.
The Network Exposure Function (NEF):
- provides a 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 by using the Nbsf management
service discovery service operation.
The Application Function (AF):
- discover the selected PCF by using the Nbsf management service discovery service operation when it is allowed
to interact directly with the policy framework for policy 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 consumer (PCF)
information for a UE when an IP address is allocated for
a PDU Session.
Nbsf_Management_Deregister This service operation is used to deregister the binding NF consumer (PCF)
information for a UE when the PDU Session is released.
Nbsf_Management_Discovery This service operation is used by an NEF or AF to NF consumer (NEF,
discover a selected PCF . AF)
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 29.521 version 15.2.0 Release 15 9 ETSI TS 129 521 V15.2.0 (2019-04)
4.2.2 Nbsf_Management_Register Service Operation
4.2.2.1 General
This service operation allows the service consumer to register the session binding information for a UE in the BSF by
providing the user identity, the DNN, the UE IP address(es) and the selected PCF address for a certain PDU Session to
the BSF, and BSF stores the information.
4.2.2.2 Register a new PCF 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 Session binding information
The NF service consumer shall invoke the Nbsf_Management_Register service operation to register the session binding
information for a UE in the BSF. The NF service consumer shall send an HTTP POST request with "{apiRoot}/nbsf-
management/v1/pcfBindings" as Resource URI representing the "PCF Session Bindings", as shown in figure 4.2.2.2-1,
step 1, to create a binding information for an "Individual PCF Session Binding" according to the information (e.g. UE
address(es), SUPI; GPSI, DNN, S-NSSAI,.NSI) in message body. The PcfBinding data structure provided in the request
body shall include:
- UE address(es);
- PCF Id;
and may include:
- DNN;
- SUPI;
- GPSI;
- S-NSSAI, and
- IPv4 address domain.
Upon the reception of an HTTP POST request with: "{apiRoot}/nbsf-management/v1/pcfBindings" as Resource URI
and PcfBinding data structure as request body, the BSF shall:
- create new binding information;
- assign a bindingId; and
- store the binding information.
If the BSF created an "Individual PCF Session Binding" resource, the BSF shall respond with "201 Created" with the
message body containing a representation of the created binding information, as shown in figure 4.2.2.2.2-1, step 2. The
BSF shall include a Location HTTP header field. The Location header field shall contain the URI of the created binding
information i.e. "{apiRoot}/nbsf-management/v1/pcfBindings/{bindingId}".
4.2.3 Nbsf_Management_Deregister Service Operation
4.2.3.1 General
This service operation allows the service consumer to remove the session binding information for a UE in the BSF by
providing an IP-address for a certain PDU Session to the BSF. It is executed by deleting a given resource identified by
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 29.521 version 15.2.0 Release 15 10 ETSI TS 129 521 V15.2.0 (2019-04)
an "IP-address". The operation is invoked by issuing a DELETE request on the URI representing the specific session
binding information.
4.2.3.2 Deregister an individual PCF Session binding information
NF service
BSF
consumer
1. DELETE …/pcfBindings/{bindingId}
2. 204 No Content
Figure 4.2.3.2-1: Session Binding Information Deregistration
The NF service consumer shall invoke the Nbsf_Management_DeRegister service operation to deregister the session
binding information for a UE in the BSF. The NF service consumer shall send an HTTP DELETE request with
"{apiRoot}/nbsf-management/v1/pcfBindings/{bindingId}" as Resource URI , where "{bindingId}" is the event
subscriptionId of the existing subscription that is to be deleted.
Upon the the reception of an HTTP DELETE request with: "{apiRoot}/nbsf-management/v1/pcfBindings/{bindingId}"
as Resource URI, the BSF shall:
- remove the corresponding binding information.
If the HTTP request message from the NF service consumer is accepted, the BSF shall respond with "204 No Content".
If the Individual PCF Session Binding resource does not exist, the BSF shall respond with "404 Not Found".
4.2.4 Nbsf_Management_Discovery Service Operation
4.2.4.1 General
This service operation allows the service consumer to use the HTTP GET method to obtain the selected PCF ID.
4.2.4.2 Retrieve the PCF Session binding information for a given tuple
NF service
BSF
consumer
1. GET …/pcfBindings?query_parameters
2. 200 OK (pcfBinding)
Figure 4.2.4.2-1: NF service consumer retrieve the PCF Session binding information for a given tuple
The NF service consumer shall invoke the Nbsf_Management_Descovery service operation to obtain the selected PCF
ID for a PDU session in the BSF. The NF service consumer shall send an HTTP GET request with "{apiRoot}/nbsf-
management/v1/pcfBindings?query_parameters" as Resource URI, where query_parameters shall include:
- UE address(es); or
- the tuple UE address, DNN, S-NNSAI; or
- the tuple SUPI, DNN, S-NNSAI; or
- the tuple GPSI, DNN, S-NNSAI; or
ETSI
---------------------- Page: 11 ----------------------
3GPP TS 29.521 version 15.2.0 Release 15 11 ETSI TS 129 521 V15.2.0 (2019-04)
- the tuple UE address, DNN, SUPI/GPSI, S-NNSAI.
Upon the the reception of an HTTP GET request with: "{apiRoot}/nbsf-
management/v1/pcfBindings?query_parameters" as Resource URI, the BSF shall:
- search the corresponding binding information.
If the HTTP request message from the NF service consumer is accepted, the BSF shall respond the PCF id within the
pcfBinding data structure with "200 OK". If the PCF Session Binding resource does not exist, the BSF shall respond
with "404 Not Found".
5 Nbsf_Management Service API
5.1 Introduction
The Nbsf_management Service shall use the Nbsf_management API.
The request URI used in each HTTP request from the NF service consumer towards the BSF shall have the structure
defined in subclause 4.4.1 of 3GPP TS 29.501 [7], i.e.:
{apiRoot}/{apiName}/{apiVersion}/{apiSpecificResourceUriPart}
with the following components:
- The {apiRoot} shall be set as described in 3GPP TS 29.501 [7].
- The {apiName} shall be "nbsf-management".
- The {apiVersion} shall be "v1".
- The {apiSpecificResourceUriPart} shall be set as described in subclause 5.3.
5.2 Usage of HTTP
5.2.1 General
HTTP/2, IETF RFC 7540 [8], shall be used as specified in clause 5 of 3GPP TS 29.500 [6].
HTTP/2 shall be transported as specified in subclause 5.3 of 3GPP TS 29.500 [6].
The OpenAPI [11] specification of HTTP messages and content bodies for the Nbsf_management is contained in
Annex A.
5.2.2 HTTP standard headers
5.2.2.1 General
See subclause 5.2.2 of 3GPP TS 29.500 [6] for the usage of HTTP standard headers.
5.2.2.2 Content type
JSON, IETF RFC 8259 [9], shall be used as content type of the HTTP bodies specified in the present specification as
specified in subclause 5.4 of 3GPP TS 29.500 [6]. The use of the JSON format shall be sig
...