/oai-cn5g-fed

OPENAIR-CN-5G: An implementation of the 5G Core network by the OpenAirInterface community.

Primary LanguagePythonOtherNOASSERTION

OAI

License License GitLab Release (custom instance) Supported OS Supported OS Supported OS

Docker Pulls Docker Pulls Docker Pulls Docker Pulls Docker Pulls Docker Pulls Docker Pulls Docker Pulls Docker Pulls Docker Pulls Docker Pulls

OPENAIR-CN-5G: An implementation of the 5G Core network by the OpenAirInterface community.

OPENAIR-CN-5G is an implementation of the 3GPP specifications for the 5G Core Network. At the moment, it contains the following network elements:

  • Access and Mobility Management Function (AMF)
  • Authentication Server Management Function (AUSF)
  • Location Management Function (LMF)
  • Network Exposure Function (NEF)
  • Network Repository Function (NRF)
  • Network Slicing Selection Function (NSSF)
  • Network Data Analytics Function (NWDAF)
  • Policy Control Function (PCF)
  • Session Management Function (SMF)
  • Unified Data Management (UDM)
  • Unified Data Repository (UDR)
  • User Plane Function (UPF) with 2 variants:
    • Simple Implementation (with a eBPF option) (UPF)
    • VPP-Based Implementation (UPF-VPP)
  • Unstructured Data Storage Function (UDSF)

Each has its own repository. Some of these repositories are still private, soon to be released.

This repository is a Federation of the OpenAir CN 5G repositories.

Its main purpose is for Continuous Integration scripting.

It also hosts some tutorials.

Licence info

It is distributed under OAI Public License V1.1. See OAI Website for more details.

The text for OAI Public License V1.1 is also available under LICENSE file at the root of this repository.

Note that the UPF-VPP implementation is distributed under Apache V2.0 License.

See Apache Website for more details.

Collaborative work

This source code is managed through a GITLAB server, a collaborative development platform.

Process is explained in CONTRIBUTING file.

If you wish to discuss development topics, we have a weekly one-hour meeting every Tuesday at 11AM CET.

The meeting details are available through this ics file.

Contribution requests

In a general way, anybody who is willing can contribute on any part of the code in any network component.

Contributions can be simple bugfixes, advices and remarks on the design, architecture, coding/implementation.

Release Notes

They are available on the CHANGELOG file.