The cellular IoT connectivity challenges of today
Mobile operators have designed their mobile core for a handful of different subscription types, resulting in a few pre-defined policies.
However, IoT customers often need their own unique subscriptions. Subscriptions with complex, dynamic connectivity and security policies. Furthermore, IoT business customers want to sit in the driver’s seat and manage their own policies.
The ability to offer these kinds of instant, customized IoT connectivity services is therefor very challenging. Sometimes it is nearly impossible to achieve these kinds of services in the current mobile core. That was what one of our longstanding mobile operator customers told us.
That was the start of the Aptilo IoT Connectivity Control Service™, one of Aptilo’s IoT solutions.
Dedicated IoT mobile core or not?
To keep up with IoT customer’s demands, we have seen mobile operators building a dedicated mobile core just for IoT. But is this really necessary? Is it even enough?
Our first IoT CCS customer, a tier 1 mobile operator, stated that they couldn’t get the IoT connectivity management they needed even in a dedicated IoT mobile core. Especially in delivering flexible and cost-effective global IoT connectivity services to their customers. And, just think about the additional cost of duplicating mobile core nodes and to scale for capacity in two places.
Mobile operators can also deliver a simple “bit-pipe” like service from their existing mobile core. But where is the money in this? Where is the customer stickiness?