1 Introduction

This document provides information on how to configure the Oracle Communications Cloud Native Core Binding Support Function (BSF).

1.1 Overview

Binding Support Function (BSF) provides a Protocol Data Unit (PDU) session binding functionality and ensures an Application Function request for a certain PDU session that reaches the relevant Binding Support Function (BSF) holding the PDU Session information.

Note:

The performance and capacity of the BSF system may vary based on the call model, Feature/Interface configuration, and underlying CNE and hardware environment.

BSF supports the following functions:

  • Allows BSF users to register, discover, and remove the binding information
  • Allows network function consumers to retrieve the binding information

CNC BSF Availability

Oracle Communications Cloud Native Core (CNC) BSF availability is dependent on many factors. BSF applications are designed to achieve 99.999% availability, according to the applicable Telecommunications Industry Association TL9000 standards, with the following deployment requirements:
  • Deploy on a Cloud Native Environment with at least 99.999% Availability.
  • Deploy with n + k application redundancy, where k is greater than or equal to one.
  • Maintain production software within n-3 software releases, where n is the current general availability release.
  • Apply bug fixes, critical patches, and configuration recommendations provided by Oracle promptly.
  • Maintain disaster recovery procedures external to the applications for the reconstruction of lost or altered files, data, programs, or Cloud Native environment.
  • Install, configure, operate, and maintain CNC BSF as per Oracle’s applicable installation, operation, administration, and maintenance specifications.
  • Maintain an active support contract and provide access to the deployed CNC BSF and your personnel to assist Oracle in addressing any outage.
CNC BSF availability is measured for each calendar year and is calculated as follows:

Table 1-1 Measuring CNC BSF Availability

Availability Description
Planned Product Availability (Product available time in each month) less (Excluded Time (defined below) in each month).
Actual Product Availability (Planned Product Availability) less (any Unscheduled Outage)
Product Availability Level (Actual Product Availability across all Production instances divided by Planned Product Availability across all Production instances) x 100

Note:

Excluded Time means:
  • Scheduled maintenance time.
  • Lack of power or backhaul connectivity, except to the extent that such lack of backhaul connectivity was caused directly by the CNC NF.
  • Hardware failure.
  • Issues arising out of configuration errors or omissions.
  • Failures caused by third-party equipment or software not provided by Oracle.
  • Occurrence of any event under Force Majeure.
  • Any time associated with failure to maintain the recommended architecture and redundancy model requirements above.

1.2 References

Following are the reference documents:

  • Oracle Communications Cloud Native Binding Support Function Installation and Upgrade Guide
  • Oracle Communications Cloud Native Core, Binding Support Function REST Specification Guide
  • Oracle Communications Cloud Native Core, Binding Support Function Network Impact Report Guide
  • Oracle Communications Cloud Native Core, Binding Support Function Network Impact Report Guide
  • Oracle Communications Cloud Native Core, Binding Support Function Troubleshooting Guide