The Red Hat Ecosystem Catalog is the official source for discovering and learning more about the Red Hat Ecosystem of both Red Hat and certified third-party products and services.
We’re the world’s leading provider of enterprise open source solutions—including Linux, cloud, container, and Kubernetes. We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Jio Platforms - Cloud Native Binding Support Function (BSF) of 5G SA Core
For 5G use cases, it is crucial to create and implement business rules on demand for each UE subscriber. The ecosystem necessitates connectivity to application functions hosted in the operator’s on-premise data centers or external data networks. To ensure a robust signaling solution in 5G, continuous communication between various network functions must be maintained in all scenarios. To achieve this, the 5GC 3GPP architecture has introduced a new entity called the Binding Support Function (BSF). BSF serves a similar purpose of the Diameter Routing Agent (DRA) to discover the PCRF in 4G. With multiple Policy Control Function (PCF) in the network, it is essential in 5G to bind the subscriber PDU sessions with PCF identity in the network.
This service allows the Policy Control Function to register the PDU 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. The BSF stores this information and keeps mapping the UEs with the PCF instances.
This service operation allows NEF of AF to retrieve the address information of the selected PCF. It takes binding details as an input. The discovery can be based on the UE address, SUPI, DNN, or S-NSSAI and IPv4 address domain.
This service operation allows the PCF to update an existing session binding information for a UE in the BSF by providing information to be updated (such as the UE address/es) for a PDU session, and based on that the BSF updates the session binding information.
In proxy mode, when the BSF receives a request from an AF, it checks whether it has already selected a PCF for the Rx session, then it proxies the request to the corresponding PCF.
In redirect mode, BSF acts like a Diameter Redirect Agent and sends the route information to the requesting node. The AF contacts the BSF on Rx session establishment to retrieve the PCF address. The BSF (redirect) does not maintain Diameter sessions, therefore, an AF should not send an Rx session modification or termination request to the BSF.
This matrix displays product versions and their claimed compatibility with Red Hat platforms, as provided by the partner through Partner Validations and the Red Hat Certifications.
| Partner product version | Red Hat platform | Certification type |
|---|---|---|
- | Red Hat OpenShift Container Platform 4.20 | |
- | Red Hat OpenShift Container Platform 4.14 |
Red Hat certified products are tested to meet Red Hat’s criteria and supported as defined in the Red Hat Collaborative Support Process.
Partner validated products are tested by Red Hat Partners and supported as defined in the Red Hat Third Party Component Policy.
| Product | Certification type | Level | |
|---|---|---|---|
Red Hat OpenShift Container Platform 4.20 Architecture: x86_64 View Kbase | RHOCP 4 CNF | ||
Red Hat OpenShift Container Platform 4.14 Architecture: x86_64 | RHOCP 4 CNF | ||