Your 5G core speaks a different language. Does your authentication and policy layer?

 Most operators launched 5G the fast way. Non-Standalone put 5G radio under the existing 4G core, kept the HSS, kept the PCRF, and got a 5G badge on the phone in months. The trade was deferred rather than avoided. Under Standalone, the 5G core takes over the control plane entirely, and everything the EPC was quietly doing for authentication, policy, and subscriber data now has to be done by new functions over new interfaces. The systems that were fine under NSA are the ones nobody re-evaluated.

Our new article is not another explainer of what 5G SA is. It is a working gap analysis built around four dimensions: authentication protocol support, policy control granularity, network slicing readiness, and subscriber data architecture. For each one you get the NSA-era state, the SA requirement, and the indicator that tells you whether you have a gap, all in a single table you can score in an afternoon.

It also covers the traps that surface during SA integration testing rather than before it. The assumption that the AAA server retires once AUSF and UDM own primary authentication (it doesn't; 3GPP wrote it into NSSAA, secondary authentication, and non-3GPP access). The PCRF that has never heard of Npcf_SMPolicyControl. The separate PCF standing beside the PCRF, with two rule sets that drift apart within a year. And the enterprise private slice that cannot be sold because nothing in the estate can act as its EAP server.

A worked example walks through a typical mid-sized operator's scorecard, and the closing section gives you the remediation order, because the four dimensions are not independent.

If 5G SA is on next year's plan, this is the assessment to run before the program plan is signed. Read More:5G Standalone Readiness: An Authentication and Policy Gap Analysis