Core Functions
A mobile or IMS core needs a handful of capabilities that sit underneath every application-facing function: a standard way to expose and discover APIs, a place to send and receive SMS, a way to play announcements and handle call media, and a record of which operator actually owns a number today. These are usually bundled inside a larger platform, forcing an operator to adopt the whole thing just to get the one piece it's missing. Slicce's Core Functions come as standalone, cloud-native building blocks instead — each deployable on its own, for exactly the capability a workload needs.
CAPIF Core Function
The Common API Framework Core Function is an element defined by 3GPP to harmonize all aspects of northbound service APIs — onboarding API invokers, registering and discovering the APIs other engines publish, and applying authorization and authentication against all of them from one point. AEFs publish their APIs here instead of each exposing its own separate gateway, so an operator or a third party reaches every one of them the same way. This is ideal to have a single point of authorization, discovery and logging across every northbound API in the catalog.
Go to the CAPIF-CF page >SMS Core Function
SMS-CF is the store-and-forward, routing and charging core behind Slicce's SMS stack — it queues every message, decides where it goes, retries it until delivery or expiry, and rates it against the OCS in real time, while SMS-AEF instances handle the actual GSM-MAP, SMPP, Diameter SGd or SIP termination in front of it. Every step of a message's life is recorded as an EDR, so support can reconstruct exactly what happened to any one of them. This is ideal to centralize SMS routing, retry and charging logic behind any number of protocol-facing SMS-AEF instances.
Go to the SMS-CF page >Media Resource Function Core Function
MRF-CF is a media server that plays announcements, collects DTMF digits and bridges basic conferencing on command from an external call-control application, driven entirely over standard SIP signalling rather than a proprietary control channel. It plays stored AMR and AMR-WB prompts natively when it can, falling back to transcoding automatically the moment a native match isn't possible. This is ideal as the shared media layer behind a call-screening, IVR or conferencing feature, without building media handling into the call-control application itself.
Go to the MRF-CF page >Mobile Number Portability Core Function
MNP-CF resolves where a number actually lives today, so the rest of the network doesn't have to guess — a SIP call to a potentially-ported number triggers a live MAP query against the network's own HLR, and the result comes back as a SIP redirect to the number's real current destination. Send Routing Information and Anytime Interrogation are also available directly over REST, independent of a live call, for manual checks or integration testing. This is ideal to resolve portability once, at the point a call enters the network, instead of every downstream element carrying its own routing logic for ported numbers.
Go to the MNP-CF page >Ask us about our core functions?
When and how to add a standalone core capability without adopting a full platform around it.
Get in touch!