Start with a defined network change
Identify the function to replace or introduce and the operational reason for the change. Set boundaries around subscriber data, packet core, signaling or a specific service.
Mobile network operators
Evolve your network on your terms.
Replace a subsystem, introduce a service or plan a core deployment. Fonetika combines modular network software with the engineering to connect it to the infrastructure your team operates.
Mobile Operators — integration viewNetwork view
Radio & access networks
Existing core systems
FonetikaCore Suite
Subscriber services
External networks
Relevant building blocks
Select the functions you need.
These products provide a starting point for design. The final mix follows your operating model and the functions already available in your network.
Packet core and subscriber services
Select Packet LTE, discuss Packet 5G scope and connect Identity for subscriber data and authentication. Add Atlas where a 5G NRF is required.
- Fonetika Packet LTE — 4G Evolved Packet Core
- Fonetika Packet 5G — 5G Core Network
- Fonetika Identity — Subscriber Data & Authentication
- Fonetika Atlas — 5G Network Repository Function
Signaling and voice
Use Signal, Relay or Transit for the required SS7, Diameter or gateway voice role. Products can be introduced as individual subsystems.
- Fonetika Signal — SS7 Signaling Transfer Point
- Fonetika Relay — Diameter Routing & Edge Agent
- Fonetika Transit — Gateway Mobile Switching Center
Messaging, SIM and management
Select SMSC, USSD or SIM OTA functions for the services you intend to run, with Control for its supported network elements.
- Fonetika Message — Short Message Service Center
- Fonetika Dialog — USSD Gateway
- Fonetika Air — SIM Over-the-Air Management
- Fonetika Control — Network Element Management
Integration boundaries
Plan the systems around the software.
Identify ownership, interfaces and responsibilities before implementation begins.
Existing data and configuration
Review subscriber records, routing rules and configuration ownership. Migration tooling and procedures are project work, not an assumed automatic transfer.
Policy, charging and peers
External PCRF, charging platforms, BSS and partner systems must be included in the interface and interoperability plan where applicable.
Operational environment
Agree infrastructure, acceptance, handover and support. Availability design and maintenance responsibilities follow the selected products and service agreement.
Pilot & acceptance
Agree what the evaluation should demonstrate.
Choose representative scenarios and measurable acceptance criteria for your environment. Targets and test scope are agreed for the project.
Interface compatibility
Test the agreed messages and procedures against the actual systems surrounding the new component.
Representative service flows
Use an agreed traffic profile and service scenarios to evaluate capacity and behavior against project-defined targets.
Transition readiness
Review configuration, migration, cutover and recovery steps with the operations team before production introduction.
Planning questions
Get the scope right from the start.
Bring the subsystem or service you want to change, current interfaces, traffic profile, operational constraints and transition requirements.
Can we replace just one network function?
Yes. Core Suite is a modular portfolio. A project can focus on one subsystem, with its interfaces and surrounding dependencies defined during solution design.
Is every network element managed by Control?
Control manages GMSC, EPC, subscriber data, SMSC, STP and DRA elements. Management requirements for other products are assessed separately during solution design.
Can you guarantee capacity before reviewing our requirements?
Capacity and availability requirements need a deployment design, representative traffic profile and agreed validation plan. We use those inputs to scope the system and acceptance work.
Get started
Let’s define your solution.
Bring the subsystem or service you want to change, current interfaces, traffic profile, operational constraints and transition requirements.