1 Introduction

The Binding Support Function (BSF) allows Policy Control Function (PCF) to register, update, and remove the binding information from it, and allows Network Function (NF) consumers to discover the selected Policy Control Function.

The BSF stores the binding information for a certain PDU sessions and discovers the selected Policy Control Function according to the binding information. It also acts as diameter proxy agent or diameter redirect agent to Rx requests targeting an IP address of a UE to the selected Policy Control Function.

For any AF using Rx, such as P-CSCF, the Binding Support Function determines the selected Policy Control Function address according to the information carried by the incoming Rx requests.

The BSF provides a PDU session binding functionality, which ensures that an Application Function (AF) request for a certain PDU Session reaches the relevant PCF holding the PDU Session information. This service:
  • Allows Policy Control Function users to register, update, and remove the binding information
  • Allows NF consumers to retrieve the binding information

For more information, see Oracle Communications Cloud Native Binding Support Function User's Guide.

References

Refer to the following documents for more information about Cloud Native Binding Support Function.

  • Cloud Native Environment Installation Document
  • Binding Support Function Cloud Native User's Guide

Acronyms and Terminology

The following table provides information about the acronyms and the terminology used in the document.

Table 1-1 Acronyms and Terminology

Acronym Definition
5GC 5G Core Network
5GS 5G System
5G-AN 5G Access Network
5G-EIR 5G-Equipment Identity Register
5G-GUTI 5G Globally Unique Temporary Identifier
5G-S-TMSI 5G S-Temporary Mobile Subscription Identifier
5QI 5G QoS Identifier
AF Application Function
AMF Access and Mobility Management Function
AS Access Stratum
AUSF Authentication Server Function
BSF Binding Support Function
CAPIF Common API Framework for 3GPP northbound APIs
CUSTOMER_REPO The docker registry address in customer side, plus Port No. if registry has port attached
IMAGE_TAG

The image tag from release tar file is 1.4.0, You can decide to use any tag No.

Then push related docker image with that specific tag to their registry

METALLB_ADDRESS_POOL The address pool which configured on metallb to provide external IPs
MPS Multimedia Priority Service
N3IWF Non-3GPP InterWorking Function
NAI Network Access Identifier
NEF Network Exposure Function
NF Network Function
NGAP Next Generation Application Protocol
NR New Radio
NRF Network Repository Function
NSI ID Network Slice Instance Identifier
NSSAI Network Slice Selection Assistance Information
NSSF Network Slice Selection Function
NSSP Network Slice Selection Policy
NWDAF Network Data Analytics Function
PCF Policy Control Function
PDR Packet Detection Rule
PEI Permanent Equipment Identifier
PER Packet Error Rate
PFD Packet Flow Description
PPD Paging Policy Differentiation
PPF Paging Proceed Flag
PPI Paging Policy Indicator
PSA PDU Session Anchor
QFI QoS Flow Identifier
QoE Quality of Experience
(R)AN (Radio) Access Network
RQA Reflective QoS Attribute
RQI Reflective QoS Indication
SA NR Standalone New Radio
SBA Service Based Architecture
SBI Service Based Interface
SD Slice Differentiator
SEAF Security Anchor Functionality
SEPP Security Edge Protection Proxy
SMF Session Management Function
SMSF Short Message Service Function
S-NSSAI Single Network Slice Selection Assistance Information
SSC Session and Service Continuity
SSCMSP Session and Service Continuity Mode Selection Policy
UDM Unified Data Management
UDR Unified Data Repository
UDSF Unstructured Data Storage Function