One of the main requirements for trusting a new technology is to provide insurance against external or fortuitous exception cases resulting from attacks, failures, misconfigurations or defects. These become even more important when the same infrastructure is shared between multiple tenants having different administrators. Every flexibility feature, such as self-scaling, brings a new set of requirements in terms of robustness of the overall system.

For a graceful system, robustness and security have to be included immediately during the design of the architecture. For this, we are currently concentrating on:

  • Critical infrastructures robustness (on independent and shared 5G environments) – this is mainly achieved in the Open5GCore through the implementation of a distributed data storage layer and session-level stateless components
  • Automatic fault management systems for the dynamic 5G environments – this is currently achieved by the monitoring of the different components
  • Load balancing and high availability features – albeit not yet completed, in the next releases Open5GCore will include some features for load balancing and high availability of the control plane as well as the control of the distributed data path.
  • State information sharing for distributed network functions – a new communication protocol was developed to be able to share state information between the edge and the central locations to assure the high availability of state share information against edge node failures.
  • AAA support for self-backhauled network islands, docking on demand to different core network locations – Open5GCore features a basic implementation for the Integrated-Access-Backhaul node as well as a set of security components which enable the connection of network islands to the central core networks.