Glossary
Definitions of the telco OSS, BSS, agentic AI, and no-code concepts used throughout our writing.
A
- Agentic AI OSS
- An OSS where self-learning AI agents detect, diagnose, and remediate operational issues autonomously. Differs from legacy AIOps by acting (not just alerting) on issues end-to-end.
- Autonomous network
- A network that operates with minimal human intervention — self-configuring, self-healing, self-optimizing. Sitting between zero-touch automation and full autonomy; Symphonica customers target L4 within 24 months.
B
- BSS (Business Support System)
- The revenue-side systems of a telco — CRM, billing, charging, order management, product catalog. BSS sits above OSS and interacts with customers; OSS handles the network-facing side.
C
- CAMARA / Open Gateway APIs
- A GSMA + Linux Foundation initiative defining standardized network APIs (Quality-on-Demand, SIM Swap, Location, etc.) that telcos can monetize. Symphonica exposes CAMARA APIs from the OSS layer.
- Cloud-Native OSS
- An OSS architected from day one for Kubernetes, horizontal scale, and zero-downtime deployments. Replaces the monolithic, upgrade-painful OSS stacks of the last generation.
- Convergent OSS
- An OSS capable of orchestrating services across multiple network domains — mobile, fixed, fiber, cable, 5G, IoT — from a single catalog and a single fulfillment engine.
M
- MagicNBI
- Symphonica's legacy-OSS adapter. Sits on top of your existing OSS and replaces northbound interfaces with a single, modern API — zero-downtime migration path for telcos stuck on aging stacks.
N
- No-Code OSS
- An Operations Support System where service fulfillment, assurance, and catalog logic is designed visually — drag-and-drop — instead of through custom integration code. Ops teams own change velocity.
O
- ODA (Open Digital Architecture)
- TM Forum's reference blueprint for modular, API-first telco IT. Symphonica ships ODA-aligned components so telcos can compose OSS/BSS stacks from best-of-breed vendors instead of locked-in suites.
- OSS (Operations Support System)
- The systems telcos use to design, provision, and maintain their services and networks. Traditionally a tangle of legacy stacks; Symphonica consolidates OSS into a single agentic, cloud-native platform.
- Order fallout
- When a service-provisioning workflow fails to complete end-to-end — a blocked order, a missing activation, a stuck configuration. Tier-1 telcos see 5–15% fallout rates on legacy OSS; Symphonica customers run under 0.3%.
S
- Service orchestration
- Coordinating the multi-step, multi-system workflow needed to fulfill a customer service request. Symphonica's visual designer lets ops teams build orchestration flows without writing integration code.