5G SBP Use Case - HEXAeBPF: The Future of Interoperable eBPF Defined 5G Core (eDC)
Use this template to submit Use Cases for submission to the 5G Super Blueprint Use Case & Requirements Advisory Group. All input marked Mandatory is required for the blueprint use case proposal to be deemed ready for review by the Use Case & Requirements Advisory Group.
Use Case Name: | HEXAeBPF |
---|---|
Use Case Description: | HEXAeBPF provides openness and interoperability to the open source community. HEXAeBPF is a Kubernetes (K8s) Operator designed to redefine how open-source 5G core networks are deployed and managed. By integrating and automating the deployment of Control Plane (CP) from Vendor A and eBPF-based User Plane (UP) from Vendor B, HEXAeBPF enables seamless, end-to-end 5G setup. Whether one is a telecommunications researcher, developer, or network operator, HEXAeBPF streamlines deployment procedures, enhances interoperability, and facilitates the advancement of 5G core network architectures. HEXAeBPF simplifies the integration and deployment process, offering one-click deployment capabilities. |
-Epic -Problem Statement | Epic: Leveraging HEXAeBPF for automated deployment and management of interoperable, high-performance, eBPF-driven 5G Core Solutions Problem Statement: Traditional deployment and management of 5G Core are complex, time-consuming, and often lack interoperability across multiple vendor solutions. This leads to higher deployment complexity, increased operational costs, vendor lock-in, and limited performance tuning capabilities. HEXAeBPF addresses these challenges by providing automated, interoperable, and high-performance 5G core deployments using cloud-native Kubernetes Operators and extended Berkeley Packet Filter (eBPF) technology for highly efficient user plane packet processing. |
Blueprint Owner | @SHANKAR MALIK |
Users Stories |
|
Interaction with other open source projects and components |
|
Resources -people | Resources (people) to execute on the blueprint:
|
Steps to Realization |
|
High-level architecture diagram | |
High level lab topology diagram |
|
Dependencies - list of any dependencies that rely of future releases of a specfic component. | Yes
or No |
High-level timeline |
|
Upstreaming Opportunities |
|
Blueprint Outputs (Suggested. Not all may apply) | check all that apply: Code repository Configuration files (e.g. Helm charts, etc.) Upstreaming to relevant projects Continuous Integration Test requirements and test results (if applicable) Documentation: Overview and Theory of Operation (i.e., what does it do?) Deployment and setup Videos demo lab setup/behind the scenes other |
Links to existing documentation (Build Guide, Slideware, etc), if available. | |
Links to existing demo/video, if available. |
|
Links to existing code/repos, if available. |