Provisioning and Mediation
Provisioning manages customer access to services.
Mediation collects and preprocesses usage data (CDR and UDR).
Both modules integrate well with any equipment or software service delivery platform for telecom or subscription-based service
Compatibility with Various Equipment and Software Platforms
Learn more
CPE and Provider Equipment Inventory
Learn more
Profile-Based Autonomous AAA, RADIUS, and DHCP Servers
Learn more
Scalability Up to Millions of Customers
Learn more
Compatibility with Any Equipment and Software Platforms
Hydra Provisioning is compatible with any hardware or software managed via RADIUS, SNMP, API, or ssh. Here are just some of the popular types of hardware and software being provisioned by Hydra in hundreds of service providers around the globe.
Broadband Services
  • Cisco BRAS: ASR, 7200, 7600
  • Mikrotik: all router series
  • Juniper: MX, ERX
  • Ericsson/RedBack SmartEdge
  • Software BRASes: accel-pppoe, VASExperts, RDP
  • DPI equipment: Procera, Sandvine
  • LTE EPC support: Telrad, Huawei
  • Wireless: Cambium, Infinet, Mikrotik
  • Other platforms
Digital TV, IPTV, and OTT
  • CAS: Irdeto, XCrypt, CTI
  • Middleware and video streaming: Stalker, Minerva, Flussonic
  • OTT: HBO Go, custom platforms
  • Other platforms
PBX and Softswitches
  • Asterisk-based
  • Sipwise
  • 3CX
  • Kolmisoft
  • Eltex
  • Avaya Definity
  • Iskratel Si2000, Si3000
  • Huawei SoftX3000
  • Nortel Meridian
  • Other platforms
Custom Platforms
  • IoT
  • EDI (electonic data interchange)
  • PaaS and IaaS
  • Toll roads
  • Car sharing
  • Other platforms
Equipment Inventory
Keep Track of All CPE and Provider Equipment Installed on Your Network
Hydra knows everything about your equipment: model, vendor, IP, IPv6, MAC addresses, phone numbers, IMSI, owner, serial number, street address, GPS location, physical and logical components.
Inventory also stores links between units of equipment at the component level (e.g. links between CPE and specific port of the switch).
Information stored in Inventory is readily available for Provisioning module
Custom fields for storing extra data.
Bulk import of the equipment from vendor-supplied file.
Improved Utilization of Equipment
Accelerate customer onboarding by using Inventory from business processes.
Reliable resource management: never forget to collect your equipment when terminating the contract with customer.
Manage CPE replacement during and outside warranty period.
Easy integration with warehousing software.
Profile-Based Autonomous RADIUS and DHCP Servers
The Hydra Provisioning module includes the RADIUS server for AAA (Authentication, Authorization, and Accounting) of data services and telephony.
Autonomous RADIUS Server
Full independence from central Billing and Provisioning modules. It has its own database of CPE profiles, which are asynchronously replicated from Provisioning. A loss of connection between AAA server and Provisioning does not affect the quality of customer services: customers are authenticated and authorized in the regular mode, while accounting data continues to be accumulated.
Support for Geographically Distributed Networks
Autonomy from the RADIUS server allows one centralized billing system, while AAA servers are situated as close to customers as possible. It is a good solution for AAA stability, even in areas with unreliable communication far away from billing system.
Flexible Rules for Processing RADIUS Requests
Even the weirdest logic of processing AAA requests can be implemented in Hydra due to its flexibility. It supports all kinds of NASes and BRASes including Cisco, Juniper, Mikrotik, Huawei, and Ericsson. Dynamic ISG service configuration, L4 redirect for notifying customers about the non-payment suspension, CoA requests for playing with customer's bandwidth and quotas—everything is possible.
High Availability AAA Server
Replication of profiles from Provisioning can be forwarded to several RADIUS servers simultaneously so that, in case of a primary server failure, NAS automatically switches to the secondary one. It is guaranteed that the secondary server has the same profile database as the primary one. This can be further enhanced by setting up a fault-tolerant RADIUS cluster of three or more nodes with a load balancer.
Scalability Up to Millions of Customers
Being a critical part of the system, the AAA server is most reliable, able to scale linearly, and fit to serve any number of customers. On a commodity hardware, one node processes 500 requests per second. You can use any number of such servers (we recommend at least two for backup purposes).
To rate the following services: paid metered service usage, long-distance and international phone calls, connection fees, and digital services such as VoD, CDN, and EDI, billing system needs usage data. Hydra includes a Mediation module which prepares raw accounting data for further rating and charging.
Parsing and Processing CDRs and UDRs: Rules for Everything
Mediation parses CDRs and UDRs in different formats according to the rules set in the config files. A set of rules for various CDR types will also differ. This is convenient when you need to separately process transit calls or simultaneously use several softswitches.

In some cases you may need extra CDR or UDR processing before loading. Mediation allows you to modify prefixes in selected CDRs. Moreover, it is possible to filter out CDRs with certain prefixes or from certain switches.

Working with External Billing
Some major service providers send already rated CDRs/UDRs. For example, satellite networks, like INMARSAT, sell traffic wholesale to their reseller partners, which subsequently sell it to retail users.

Hydra Mediation installed at a reseller processes CDRs (adds markups and so on) and passes them into Billing without internal rating. Thus, resellers are more than happy to offer their own price plans to customers.
RADIUS, SNMP, and Netflow Accounting
Data usage accounting via Netflow, SNMP and RADIUS protocols have ready-made solutions in Hydra. Mediation collects accounting data and loads it in batches into Billing.

Hydra is able to charge separately for different traffic classes, based on ASN, subnets, time intervals, or pre-classified accounting data.

Hydra also polls SNMP counters to measure currently consumed bandwidth for percentile-based billing.
Made on