Ericsson Billing vs OpenDaylight

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.

OpenDaylight is a free, open-source SDN controller for centralized, programmable network control and monitoring. Its modular design uses YANG models and MD-SAL to connect applications with network hardware through northbound REST APIs and southbound plugins. Listed protocol support includes OpenFlow, NETCONF, BGP-LS, PCEP, OVSDB, LISP, and SNMP, among others. Clustering, sharded data stores, and leader-based consensus support scaling across nodes. The project describes uses in optical transport, service-provider WAN automation, data center SDN, network telemetry, enterprise network control, and ONAP. Its AAA project provides authentication, authorization, accounting, and role-based access control for northbound interfaces. OpenDaylight is self-hosted and runs on Linux, macOS, and Windows; setup requires Java 21 or later. The downloads page identifies Chromium-SR0 as the current release and lists Vanadium-SR1 and Titanium-SR3 under supported releases. Documentation, Zulip chat, mailing lists, a wiki, and weekly Technical Steering Committee meetings are listed as community resources.