SBI
Service-Based Interface: the API interface exposed by each 5GC network function, using HTTP/2 with JSON payloads for service registration, discovery, and invocation.
SBI is the architectural style of the 5G core: instead of fixed point-to-point interfaces between named nodes, each network function exposes services as APIs that any authorised consumer can call. A function registers its services with the NRF (the repository), other functions discover it there, and they invoke it over HTTP/2 with JSON. So rather than "the MME talks to the HSS over S6a with these Diameter messages," you have "the AMF consumes the UDM's subscriber-data service via its API."
The payoff is modularity and cloud-native operation. Services can be deployed, scaled and updated more independently, and adding a consumer doesn't require a brand-new interface — it just calls an existing service. Naming reflects this: interfaces carry service names like Namf, Nudm, Nsmf rather than the old letter-number labels. The trade-offs are the ones any API platform faces — discovery, authorization between services (via OAuth2 tokens), and securing the calls — which is why the NRF and the SEPP matter so much in this model.
Related terms
Want to truly understand SBI? Learn it in context.
SBI is taught inside our 5G Signaling & Procedures course with diagrams and worked examples. The first module is free with an account; labs, TelcoMentor and the rest of the curriculum are on Pro.
- Free to join
- First module of every course
- No card needed
- TELCOMA since 2009
Get weekly 5G/LTE engineering deep-dives
One technical breakdown every Tuesday — plus first access to new tools and lessons. No spam, no marketing, just engineering. Unsubscribe in one click.