N32 Interface
The reference point between SEPPs of different PLMNs for secure inter-operator signaling exchange, using TLS and application-layer security (PRINS or TLS).
N32 is the one place where two different operators' 5G cores meet directly, and it's deliberately the most scrutinised interface in roaming. It connects the SEPP of one PLMN to the SEPP of another, carrying the service-based signalling that has to cross between networks. Because that traffic leaves your security domain, N32 protects it: peer authentication between the SEPPs, plus integrity and confidentiality for the messages.
It comes in two flavours, and which one you use depends on whether intermediaries in the path need to touch the messages. If the SEPPs connect directly, plain TLS over N32 (sometimes called N32-c for the control/negotiation and N32-f for the forwarded messages) is enough. But roaming hubs in the IPX often need to read or modify specific header fields, and you can't do that through end-to-end TLS. For that case there's PRINS (PRotocol for N32 INterconnect Security), an application-layer scheme that protects message content while allowing authorised intermediaries to alter only agreed, specific parts — and proving exactly what was changed.
Related terms
Want to truly understand N32 Interface? Learn it in context.
A free account opens all 13 courses — 404 video lessons, labs and full practice exams — for 7 days, no card. Prime Membership keeps them and adds the certification exam and a verifiable certificate.
- 7 days of every course
- Then the first module, free
- No card needed
- TELCOMA since 2009
Get one 5G/LTE engineering deep-dive a fortnight
One thing explained properly every other Tuesday — a real failure, and the lab or trace where you work it yourself. No spam, no marketing, just engineering. Unsubscribe in one click.