Ericsson Billing vs Kube-OVN

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.

Kube-OVN combines OVN and Open vSwitch with Kubernetes for cloud-native network orchestration. Its documented features include subnet management, static IP allocation, gateways, hybrid underlay and overlay networks, VPC features, QoS, ACLs, and traffic mirroring. VPC networks provide tenants with separate address spaces and networking resources. The project recommends it for Kubernetes environments needing KubeVirt support or multi-tenant networking; KubeVirt virtual machines can live-migrate without network interruption. Documented integrations include Cilium, MetalLB, OpenStack, Submariner, and OVN interconnect. With Cilium chaining, Kube-OVN network abstractions can be used with Cilium eBPF monitoring and security capabilities. The project runs on x86_64 and arm64, and its documentation provides one-click installation scripts. It is free under Apache-2.0, deployed on-premises, and uses a centralized control plane. The project advises against it for OpenShift, public-cloud managed Kubernetes, and cases requiring an all-in-one CNI, ingress, service mesh, and observability stack.