Define device-to-application traffic
Map device groups, APNs, IP addressing and data-network connections. Evaluate Packet LTE functions against the connectivity behavior your applications require.
Operators, enterprises & IoT service providers
Connect devices with the applications behind them.
Plan LTE data connectivity, subscriber provisioning and application integration for connected-device services. Fonetika combines documented core functions with engineering for the device and service flows in your project.
IoT & Service Exposure — integration viewNetwork view
LTE access & connected devices
Subscriber provisioning
FonetikaCore Suite
IoT applications
Enterprise data 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.
LTE connectivity and identity
Packet LTE provides the EPC functions, APN separation, IP addressing and QoS controls to evaluate for your design. Identity provides subscriber data and authentication.
- Fonetika Packet LTE — 4G Evolved Packet Core
- Fonetika Identity — Subscriber Data & Authentication
Configuration and application messaging
Control manages its supported elements. Add Message when SMSC-based application messaging is part of the connected-device service.
- Fonetika Control — Network Element Management
- Fonetika Message — Short Message Service Center
Integration boundaries
Plan the systems around the software.
Identify ownership, interfaces and responsibilities before implementation begins.
Device and radio compatibility
Validate the selected devices, radio network and service procedures together. A general IoT use case does not establish support for every device category or radio profile.
Service exposure
SCEF-related integration requires a defined set of APIs, access controls and service procedures. Agree the functional scope and delivery responsibilities alongside the selected core products.
Applications, policy and charging
IoT platforms, enterprise applications, BSS and external policy or charging systems remain separately identified parts of the solution.
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.
Provisioning and connectivity
Test subscriber provisioning, authentication and device connectivity using the actual device and radio combinations proposed for the project.
Application data paths
Check the agreed APNs, IP allocation and application traffic paths, plus SMS exchanges if Message is selected.
Integration behavior
For any service-exposure work, define the specific application requests, authorization requirements, responses and error scenarios to be validated.
Planning questions
Get the scope right from the start.
Bring your device and radio choices, subscriber provisioning flow, APN and addressing needs, application traffic profile and any service-exposure requirements.
Is SCEF a separate Fonetika product?
SCEF-related service exposure is an engineering integration scope. It is not a separate Core Suite product; its required functions, interfaces and delivery responsibilities are defined for the project.
Do all connected-device projects need SMS?
No. Message is relevant when your service uses SMS application integration. A data-connectivity project can have a different product mix based on its device and application requirements.
Does this imply support for every IoT device or radio technology?
No. Device behavior, radio support and required service procedures must be checked against the selected products and deployment. These are explicit inputs to the design and pilot acceptance plan.
Get started
Let’s define your solution.
Bring your device and radio choices, subscriber provisioning flow, APN and addressing needs, application traffic profile and any service-exposure requirements.