Architecture¶
OpenOP is an open-source implementation of an Operator Platform (OP) that enables App Providers, developers and researchers to consume telecom network and Edge Cloud capabilities — such as deploying Application Instances on Edge Cloud Availability Zones or configuring Quality on Demand sessions — through standardised CAMARA APIs, without requiring knowledge of the underlying operator infrastructure. It further supports inter-operator federation, allowing App Providers to access capabilities and resources across multiple Operator Platform instances via the East/Westbound Interface (EWBI).
Architectural Diagram¶
The diagram reads from top to bottom, in four layers:
- Consumers: developers and operators use the Portal in a browser, App Providers call the APIs from their own software, and partner operators connect for federation.
- Exposure: OEG offers the CAMARA APIs, and the Portal and AI² call it for their users. FM is the entry point for partner operators.
- Core: SRM decides where each request runs and keeps track of it, working with FM when a partner operator is involved. Keycloak signs in users and applications, PostgreSQL stores each component's data, and the DataBus carries messages between OEG, SRM and FM.
- Infrastructure: through TF-SDK adapters, SRM runs applications on Kubernetes and drives network functions in 5G cores.
The Data Lab is a separate catalogue and is not drawn.
Components¶
| Component | Description |
|---|---|
| AI Module (AI²) | An AI-native interface to the Operator Platform, enabling natural language interaction and AI-driven automation. |
| Portal | A web-based management interface for the Operator Platform. |
| Open Exposure Gateway (OEG) | The Northbound Interface entry point, exposing CAMARA APIs to App Providers. |
| Service Resource Manager (SRM) | The brains of the platform, managing application lifecycle and translating technology-agnostic requests into technology-specific actions. |
| Transformation Function SDK | Technology-specific adapters implementing the Southbound Interface, enabling support for heterogeneous Edge Cloud and network infrastructure. |
| Federation Manager | Manages inter-operator federation agreements and shared Availability Zones, enabling cross-operator resource sharing. |
| Data Lab | The dataspace metadata catalogue, describing datasets, their distributions and data quality using the 6G-DALI Metadata Application Profile. |
| Platform services | Keycloak, NATS and PostgreSQL: identity, the DataBus and storage shared by the components. |
Read in the specs¶
The specs are in the architecture repository. Start from the question that matches what you need:
| Question | Where to read |
|---|---|
| How does a request travel through the platform? | Platform Architecture › Mental Model |
| How do the components talk to each other? | Platform Architecture › Data Flow: How Components Communicate |
| Which standards does it follow? | Platform Architecture › Standards Alignment |
| What does a term mean? | OOP Glossary |
| Why was something decided? | Decisions |
Each component page links to the parts of its own spec.