Carrier-grade telecom charging and execution Built and operated at scale.
Charging, service execution, access and media for operator networks
Telecom
Charging determines what a subscription can use; service logic determines what happens next in the network. Our telecom portfolio connects these functions with access, voice and messaging platforms for MNOs, MVNOs and MVNEs.
Online Charging System (OCS)
3GPP Rel-15/16 compliant charging platform for MNO, MVNO and MVNE operators. Real-time rating, policy control and quota management. Cloud-native, BSS/OSS-ready, with AI-assisted fraud detection and full 5G SA support at scale.
Java Service Logic Execution Environment (JSLEE)
A maintained JAIN SLEE runtime for services that already run in your network. Keep the SBB, resource adaptor, activity, timer and profile model while moving to a current runtime through staged compatibility work.
Our platforms
Choose the network function you need to change, from subscriber access to call treatment and media. Energy products form a separate portfolio for metering, settlement and charging infrastructure.
Telecom
Online Charging System (OCS)
Charge for calls, data and SMS as subscribers use them. Rate API calls and reserve units in real time.
Explore Online Charging System (OCS)OVOO JSLEE
Move the JAIN SLEE, SIP Servlet and EJB services you already run to cloud-native network functions in stages.
Explore OVOO JSLEEOVOO Trinity
Let callers speak to an AI assistant while your network stays in control of signalling, session state and fallback.
Explore OVOO TrinityAAA Platform
Subscriber authentication, access authorisation and accounting for mobile, fixed and operator Wi-Fi services.
Explore AAA PlatformTAS
Subscriber calling services and supplementary-service treatment in IMS, VoLTE and VoWiFi networks.
Explore TASService Broker
Service sequencing and protocol mediation across existing IN services, IMS application servers and APIs.
Explore Service BrokerCloud IVR
Voice self-service built around prompts, caller input and backend actions, with a visual flow builder.
Explore Cloud IVRCompliance Recording
Encrypted recording with retention and legal-hold policies, authorised search, redaction and auditable exports.
Explore Compliance RecordingMessaging Gateway
SMS/MMS interconnect through SMPP, MMSC and HTTP, with routing policies and a traceable delivery-report chain.
Explore Messaging GatewayCell Broadcast Centre (CBC)
Broadcast CAP 1.2 warnings as EU-Alert in the affected area over 4G and 5G, then review network confirmations.
Explore Cell Broadcast Centre (CBC)USSD Gateway
Let subscribers check balances or activate services via USSD. Send prompts from your HTTP backend over MAP/SS7.
Explore USSD GatewayVerified Caller ID
Wallet-based caller identity verification for IMS networks, with SSI and EUDI integration paths and branded calling on supported devices.
Explore Verified Caller IDOVOO SM-DP+
eSIM profile preparation and delivery using GSMA SGP.22, with BSS provisioning and a separate HSS integration.
Explore OVOO SM-DP+Skylark Media Server
Run IVR and conferences on VoLTE, keep call recordings encrypted and connect your speech engines when you need voice AI.
Explore Skylark Media ServerEnergy
Energy Platform
Billing, settlement & IoT metering for energy communities. KSeF-compliant invoicing and CSIRE integration.
Explore Energy PlatformAI Energy Analytics
Predictive analytics, demand forecasting and anomaly detection for energy community operators.
Explore AI Energy AnalyticsEV Charging Platform
EV charging session management, smart scheduling and billing for municipalities and fleet operators.
Explore EV Charging PlatformPartners & Clients
Our delivery experience spans telecom networks and energy services, alongside the technology partners shown below.
Tier-1 and Tier-2 operators · energy communities · technology partners worldwide
FAQ
Short answers to common questions. For anything else, contact us.
How do we scope availability and recovery for the selected platform?
Start with the service path, stateful components, deployment sites and failure scenarios that matter to your network. Define the required recovery behaviour and validate it in the target configuration. Availability architecture and recovery objectives are agreed for the selected product and operating model.
Do you support on-premise deployment, or is it cloud-only?
OVOO products support on-premise and cloud deployment models. The selected platform determines whether virtual machines, Kubernetes containers or a hybrid arrangement fits the deployment. We work through network connectivity, data location and operational ownership with your infrastructure team.
How does migration from a legacy OCS or billing system work?
We first map the subscriber, account, balance and integration dependencies in the current system. Migration planning then covers data transfer, parallel validation, cutover criteria and a rollback route. The service and data scope determines the sequence, with acceptance agreed before live traffic moves.
What should the service agreement define?
Specify the covered service paths, availability objectives, incident severities, response times and monitoring responsibilities. Reporting, recovery commitments and remediation terms are agreed for the selected platform, configuration and support scope.
Which standards and product evidence should our review cover?
Review the interfaces required by the service, such as Diameter Gy/Ro or HTTP Nchf for charging. The technical review should include supported versions, interoperability test scope and the security or compliance documentation relevant to that product and deployment.
What determines readiness to carry live traffic?
The joint integration plan defines the required network connections, subscriber or service data, acceptance flows and operational handover. Readiness includes monitoring ownership, failure testing and agreed cutover criteria, with the responsible teams involved before service start.










