Documentation
Welcome to the TOSSI documentation. TOSSI is the Telecom Open Source System Integrator - a neutral foundation that integrates the open telecom stack into a coherent, validated whole. These docs are organized around the reference architecture and the eight technology pillars beneath it.
Start here
Section titled “Start here” Reference Architecture The end-to-end blueprint: how the pillars compose, the interfaces between them, and where security and orchestration cut across.
5G Core - Getting Started Stand up a cloud-native 5G core and understand the service-based architecture.
RIC - Getting Started Bring up a Near-RT RIC and connect an E2 node to run your first control loop.
Post-Quantum Security The crypto-agile migration to ML-KEM / ML-DSA across every telecom interface.
The eight pillars
Section titled “The eight pillars”Each pillar is a layer of the open telecom system. TOSSI selects, versions, integrates, and validates them so they interoperate end to end.
5G Core Cloud-native, service-based 5GC - control plane and user plane, aligned to the 3GPP service-based architecture across open 5G core implementations.
RAN & O-RAN Disaggregated, multi-vendor radio over open fronthaul and the O-CU/O-DU/O-RU split, drawing on open RAN stacks.
RAN Intelligent Controllers Near-RT and Non-RT RIC control loops over the E2 and A1 interfaces.
Service Management & Orchestration The management plane terminating O1, O2, and A1 across the deployment.
xApps & rApps The RAN-control application ecosystem - SDKs, descriptors, onboarding, and lifecycle.
Post-Quantum Security ML-KEM, ML-DSA, and SLH-DSA with crypto-agility across TLS, IPsec, and PKI.
Cloud-Native & Kubernetes Operators The Kubernetes substrate, operators, and GitOps that package and lifecycle telecom CNFs.
eBPF & Dataplane Kernel-programmable networking and a high-throughput UPF dataplane via eBPF/XDP.
How these docs are organized
Section titled “How these docs are organized”We follow the Diátaxis model. Within each pillar you’ll typically find:
- an overview that orients you and lists the key implementations and standards,
- an architecture / concepts page that explains how the layer works,
- a getting-started / how-to page with concrete procedures, and
- a reference page for interfaces, APIs, and standards.