Open6GCore follows a three-layer architecture. The data layer provides a shared data backbone that combines Redis with a relational database: session data is stored in Redis, while subscriber data is stored in the relational database. The processing layer implements network functionality as software-based services rather than fixed, monolithic network functions.
Its service decomposition is configurable, allowing the core to operate either with the standard 5G network-function split or with a custom composition of service functions tailored to project requirements. The interface layer separates external protocols and interfaces from internal core communication. It exposes 3GPP-defined 5G protocols and interfaces, including NGAP, PFCP and the Service-Based Interface, to connected systems and components.
The three-layer architecture is complemented by logging, tracing and metrics-collection tools that provide end-to-end observability. A message queue distributes requests across service instances for load balancing.
It connects to the SBI proxy, enabling communication between Open6GCore’s 6G services and conventional 5G network functions.
