Match the host-network agreement
Map the functions retained by the host operator and those you need to own. Use that split to define subscriber management, packet data, signaling and service responsibilities.
Virtual operators & enablement platforms
Choose which network functions your business will operate. Fonetika brings together subscriber data, signaling, voice, messaging and packet core software for integration with host networks and business systems.
Relevant building blocks
These products provide a starting point for design. The final mix follows your operating model and the functions already available in your network.
Identity supplies subscriber data and authentication. Add Packet LTE or scope Packet 5G when the operating model includes your own packet core; host-managed functions need not be duplicated.
Signal handles SS7 routing, Relay supports Diameter routing and edge roles, and Transit supplies gateway MSC voice functions when required.
Select Message for SMSC, Dialog for USSD applications and Air for SIM OTA updates. Control manages the supported core elements in the chosen deployment.
Integration boundaries
Identify ownership, interfaces and responsibilities before implementation begins.
The host agreement defines radio access, roaming and the network functions available to your service. Connectivity and interconnection agreements are separate commercial dependencies.
Existing BSS, online charging, external policy systems and application backends connect through the interfaces of the selected products.
Agree SIM data, subscriber provisioning ownership and the configuration and support processes across your team, Fonetika and the host operator.
Pilot & acceptance
Choose representative scenarios and measurable acceptance criteria for your environment. Targets and test scope are agreed for the project.
Test the agreed provisioning changes and authentication flows between business systems, subscriber data and the host network.
Exercise the selected voice, SMS, USSD or data scenarios, including the applicable records and charging exchanges.
Validate routing, error handling and the operational procedures required for each agreed host or partner connection.
Planning questions
Bring the host-network responsibility split, service plan, BSS and charging interfaces, subscriber scale and launch priorities.
No. The product mix depends on the functions you operate and the functions supplied by your host network. Individual products can be selected for a specific subsystem or a broader deployment.
Identity provides JSON/REST subscriber provisioning integration, and other products offer their documented application or charging interfaces. The field mapping, workflows and acceptance tests are defined with your BSS team.
No. Air prepares SIM OTA commands for delivery through an SMSC. eSIM remote provisioning, including SM-DP+ or SM-SR requirements, needs a separate solution assessment.
Get started
Bring the host-network responsibility split, service plan, BSS and charging interfaces, subscriber scale and launch priorities.