Ericsson Billing vs ONOS
Ericsson Billing
ericsson.comONOS
onosproject.orgSide by side
| Figure | Ericsson Billing | ONOS |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| macOS | — | Yes |
| Linux | — | Yes |
| API | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 0 | 1 |
| Spec score · Software-Defined Networking Software | 7.5 (#8) | 8.2 (#2) |
Plans
In their own words
Ericsson Billing
Ericsson Billing is a convergent, end-to-end billing system for communications providers offering mobile, fixed-line, broadband, TV, digital, or OTT services. It supports prepaid and postpaid services in one contract and manages customers and partners through a common database. A convergent rating engine processes voice, data, content, and other event-based usage online or in batches. Billing can run on demand or in batches, with split billing for separate corporate and private invoices. Functions include configurable taxation, multi-tenancy, multiple currencies, promotions, rounding algorithms, and plan management. The system supports traditional telecom services alongside digital services, 5G, and IoT, including TAP/RAP and IMS specifications. Ericsson describes open, componentized architecture, TM Forum and REST interfaces, an SDK, public or private cloud deployment, and horizontal auto-scaling. AI/ML use cases address invoice quality, while a GUI chatbot can explain invoice differences. Pricing is on request.
ONOS
ONOS is an open-source software-defined networking platform that provides a control plane for managing network components and running communication-service modules. Its µONOS architecture supports device configuration, monitoring and maintenance, forwarding-plane programming, topology validation, and fine-grained performance metrics. A symmetric cluster of identical instances distributes work across servers and is designed to handle instance failures; the architecture is described as highly available and dynamically scalable. Control and configuration interfaces include P4/P4Runtime, gNMI/OpenConfig, and gNOI, with gRPC connecting modular microservices. OpenFlow is the primary southbound protocol, and OVSDB, NETCONF, and SNMP are also named for device configuration. The microservices are designed for cloud and data center infrastructure using Kubernetes, with Docker images and Helm charts listed as deployment tools. A cloud-native web GUI uses Angular and gRPC Web to access backend modules. ONOS is free and published under the Apache License 2.0. It is aimed mainly at service-provider networks, with data-center and campus networks also identified as possible uses. Production downloads are recommended as a release tar.gz package or Docker image; the listed LTS release is X-Wing 2.7.0, dated July 16, 2021.