GSMA TS.43 Entitlement Server

A standards-compliant GSMA TS.43 Entitlement Configuration Server. It is the component a device asks, before it will switch on RCS, VoWiFi, VoLTE, a companion watch or an eSIM transfer, whether this subscriber is allowed to use that service on this network. Without it, the handset simply does not offer the feature.

TS.43 entitlement configuration for RCS, VoWiFi, VoLTE, SMSoIP and data plans
eSIM transfer, ODSA subscription activation and companion-device (watch) pairing
EAP-AKA and OpenID Connect authentication against your HLR/HSS/UDM and IdP
Per-tenant policy — built for MVNEs as well as single-brand operators
Small, self-contained project: weeks to integrate, not quarters

Scope an entitlement project

Messaging & Entitlement

GSMA TS.43

RCS entitlement

VoWiFi · VoLTE

eSIM transfer

ODSA

Watch pairing

EAP-AKA

OpenID Connect

XML & JSON profiles

Multi-tenant

Kubernetes

Why this became urgent

For years TS.43 was the quiet component behind VoWiFi activation. Then cross-platform RCS arrived on iOS, and entitlement moved onto the critical path for a service that operators are now actively marketing.

The mechanics are unforgiving. The device queries the entitlement server before it will expose the feature. If the server is missing, or answers with a malformed configuration, or authenticates against the wrong identity, the user simply does not get RCS — and there is no error message anyone in your care organisation can act on.

The same server governs VoWiFi and VoLTE activation, eSIM transfer between devices, on-device subscription activation and watch pairing. It is one small component sitting in front of a growing list of revenue-relevant journeys.

There are very few independent vendors for it, and most are large. That is the gap we built for.

Services it governs

RCS entitlement

TS.43 application ID ap2009 configuration for the RCS client
Per-subscriber and per-tenant enablement policy
Provisioning handover to your RCS stack and Jibe or an on-net server
The precondition for cross-platform RCS on iOS and Android

VoWiFi and VoLTE

Activation, terms-of-service acceptance and emergency address capture
Web-view flows fully brandable per tenant
Address validation hooks into your existing emergency-services database
Per-country and per-roaming-partner policy

eSIM, ODSA and devices

eSIM transfer between devices, including primary-device change
ODSA on-device subscription activation for tablets and laptops
Companion-device and watch pairing with shared-number policy
SM-DP+ integration for profile download and activation codes

Identity and authorisation

EAP-AKA against HLR, HSS or UDM through the interfaces you already expose
OpenID Connect against your existing identity provider
Token lifetime, refresh and revocation policy per service
Full audit trail of every entitlement decision, retained per policy

Architecture

Entitlement endpoint. The TS.43 HTTPS interface the device talks to, with configuration documents rendered per application, per device class and per OS version.

Authentication broker. EAP-AKA against your subscriber database, or OIDC against your identity provider, with the vector exchange and token lifecycle handled for you.

Policy engine. Which services this subscriber, on this device, in this country, under this tariff, in this tenant is entitled to — sourced live from your BSS over REST, or from a cached projection.

Web-view service. The branded activation, terms and address capture screens the device opens, theme-able per tenant.

Assurance. Every entitlement transaction is measured by ProBee: success ratio, latency and failure mode, per device model and per OS release. Entitlement failures are otherwise invisible.

How assurance is wired in

Who needs one

Operators launching RCS

If you intend to offer RCS to iOS users, entitlement is not optional and it is on the critical path.

Operators with VoWiFi or eSIM

You may already have entitlement embedded in a legacy vendor stack. Extracting it is usually cheaper than extending it.

MVNEs and MVNOs

Host operators rarely expose entitlement to their MVNOs. A per-tenant server closes a gap your BSS cannot.

Integrators

A small, well-specified component that completes an RCS or IMS programme without adding a Tier-1 vendor to the plan.

A deliberately small project

This is the fastest thing in our portfolio to put into production, which is why it is usually the first thing customers buy from us.

Week	Activity	Dependency on you
1	Interface workshop: subscriber database, identity provider, BSS policy source, branding.	Two hours of an architect’s time.
2–3	Deployment into your cluster or ours. EAP-AKA or OIDC integration. Policy mapping.	Test credentials and a test SIM range.
4–5	Device testing across handset models and OS versions via BeeTest. Web-view branding.	Access to a device pool, or use ours.
6	Friendly-user launch with per-transaction assurance live.	A sign-off meeting.

Indicative. A single-tenant deployment against clean interfaces has run faster; a multi-tenant one with a legacy HLR has run longer.

What our customers say

References are anonymised at the customer’s request. Named references and written reference letters are available under NDA.

Core network operations, Tier-1 MNO (DT group)

„We were finding signalling degradations from the complaint queue. ProBee moved that left by roughly forty minutes — we now see the retransmission pattern build before the first customer calls. It is the same Grafana our NOC already lives in, so nobody had to learn a new console.”

Head of Platforms, MVNE serving 300k+ subscribers

„Our BSS was complete and our network layer was not. Mobees dropped in the messaging core and the TS.43 entitlement server behind our existing provisioning, per tenant. We stopped referring those deals out.”

Delivery director, systems integrator, CEE

„They are the people we call when a transformation programme hits SS7 or CAMEL and the schedule is already tight. Small team, no layers, an answer the same week.”

Is your RCS launch blocked on entitlement?

It is a common place to be stuck. A thirty-minute call is usually enough to tell you whether this is a six-week project or a six-month one.

Contact us

Messaging & Entitlement