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.
JPL Cloud Native 5G User Plane Function of 5G SA Core
JPL’s UPF is a 3GPP compliant solution with zero-copy single hop packet processing. It significantly reduces the total cost of ownership of the user plane, simplifies the overall architecture, and makes deployment easy and fast. The UPF supports a scalable, robust, and resilient cluster solution. It consists of coupled microservices.
The framework is designed so that once a packet arrives at a system, it is copied only once. Various services are given direct memory access to the single packet copy in an ordered and orchestrated manner. In this way, the framework avoids overheads caused by communication of data across processes/systems, copying of packets, and unnecessary system calls. This design helps achieve very low latency and high performance.
Based on the control information from SMF, JPL’s UPF supports allocation of either one or both IPv4 and IPv6 addresses to UE. The UPF indicates support of the “UE IP Address/Prefix Allocation” feature in the PFCP Association Setup Request Message to SMF. The IP address assignment is done based on the data network name received from SMF during PFCP session establishment or modification request. Pools of IPv4 and IPv6 need to be configured for each data network. In case of IPv6 address allocation, /64 IPv6 prefix is allocated by the UPF. In case a PFCP session terminates, the UPF waits for a configurable duration before re-allocating that IP address to another UE.
Inter-PLMN User Plane Security functionality at the border of the network protects networks from invalid inter-PLMN N9 traffic.
Tunnel IDs for receiving uplink traffic can be allocated by JPL’s UPF based on control information received from SMF. The UPF indicates to SMF the support of tunnel endpoint allocation by setting the “FTUP” feature flag in Association Setup Request. It can allocate a fresh tunnel or reuse one of the pre-created tunnels in that PFCP session based on the information received from SMF. In case a PFCP session terminates, UPF waits for a configurable duration before allocating that tunnel ID to another PFCP session.
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 | ||