What should we validate when several offers can serve the same event?▾
Define the account, service, offer group and product priorities used to select the applicable subscription. Exercise events that could match more than one owned product, then check the selected tariff and the monetary or bundle balance affected by the result.
What exactly is supported on the HTTP Nchf path?▾
HTTP Nchf supports immediate event and reserved event charging using IEC and ECUR. Map the required 5G event flows to those operations, then define how they coexist with the Diameter, REST and offline paths already used by your network.
Can Diameter charging run beside 5G charging?▾
Yes. Diameter Ro and Gy run alongside HTTP Nchf immediate event and reserved event charging, REST and offline inputs. Operators can introduce 5G event charging while existing Diameter services remain active.
What should our capacity test reproduce?▾
Reproduce the intended traffic mix, account volume, rating rules and simultaneous balance activity. Include the relevant tenant and traffic-class allocation, then inspect average and tail processing time as well as throughput. The benchmark above provides its configuration and data volumes so your team can compare like for like.
How are incomplete or duplicate sessions handled?▾
Session controls support duplicate protection, rollback and continuation across Core nodes. Incomplete sessions can be resumed, settled from offline data or terminated when inactivity rules apply.
How does multitenancy work?▾
Providers and retailers can have scoped catalogs, charging rules, accounts, data and access roles. Traffic controls and administration for each retailer remain inside that tenant boundary.
What should determine the deployment choice?▾
Start with the operator-approved infrastructure, redundancy model and operational ownership. Match the release to its supported operating-system and platform versions, then agree who maintains the Ansible, Terraform or Helm delivery configuration. The available private- and public-cloud options are listed in the deployment section.
What should we bring to the first OCS engineering session?▾
Bring representative charging requests, offer and tariff examples, account and balance structures, traffic volumes and the connected BSS operations. Identify the owners of network interfaces, provisioning and mediation so the first pilot can be scoped against actual inputs and responsibilities.
Can prepaid, postpaid and hybrid services use one charging model?▾
Prepaid, postpaid and hybrid services use one connected product model for accounts, offers, rating plans, tariffs, balances and bundles. Configure the charging rules for each service and account model in the selected rollout.
Can a tariff change take effect during an active session?▾
Yes. Tariff values can be scheduled in advance, and the charging logic can split an active session at the effective time so usage before and after the change is rated with the appropriate value.
How do we separate customer-care operations from network charging?▾
Map the REST evaluation, session-termination and provisioning operations needed by care and BSS systems separately from the live network interfaces. Keep mediated CDR and SQL usage on the offline path. The interface map assigns an operation and owner to each connected system.
Which administrative changes can operations trace?▾
GUI audit history covers catalog changes, top ups, refunds, deductions and transfers, alongside scoped administrative access. Agree which changes the operating team needs to review and how the resulting audit history fits its charging and customer-care investigations.
How does token based unit reservation work for AI services?▾
The AI gateway reserves a token quota before the model runs. Long generations or agent loops extend the reservation mid session. When the response completes, input, output and cached tokens are rated and charged, and any unused reservation is released back to the balance. OVOO OCS is the first OCS with native support for this reservation model for AI traffic.
Can OVOO OCS charge and rate API calls?▾
Yes. API calls are rated per call, per volume, per tier or per outcome with quotas per API key, application or account. The same balances, bundles, notifications and charging records apply to API traffic, network traffic and AI tokens.