5G Standalone

A 5G Standalone subscriber has no circuit-switched channel and may not be on IMS. Without an SMSF, that subscriber cannot send or receive a text. The SMSF carries SMS over 5G signalling and hands it to the SMSC you already run.

AMTP · SMSF
InterfacesN20 (AMF) · N21 (UDM)
ProtocolsHTTP/2 (SBI)MAP/Diameter to SMSC
Message typesMO and MT — both directions
SMSC bridgeOuroboros or third-party SMSC
SubscriptionRetrieved from UDM over N21
DeploymentVMware, KVM, Docker, Kubernetes
in production since
99.9999%
availability
MO+MT
both directions
NAS
no CS/IMS needed
00The problem

SMS is not optional. Two-factor codes, banking alerts, account notifications, and service messages all depend on it. But a 5G Standalone subscriber has no 2G/3G circuit-switched fallback for messaging, and may attach before VoLTE/VoNR IMS messaging is in place. The path that delivered SMS on earlier generations is not there.

5G SA defines a dedicated path: SMS over NAS, carried by the SMSF. Without that function, a 5G SA subscriber drops off the messaging network the moment they attach. For an operator launching 5G SA, that affects every subscriber who relies on text for authentication or alerts, which is most of them.

01How it works

SMSFcore
AMFN20 NAS
SMSCstore-fwd
UDMN21 profile
A2Penterprise
01 / 02

Subscriber sends — AMF relays to SMSF over N20

In 5G Standalone, SMS travels inside NAS signalling rather than over a voice channel. When a 5G subscriber sends a message, the AMF relays it to the SMSF over N20. The SMSF retrieves the subscriber's SMS subscription from the UDM over N21, then routes the message onward to the SMSC for store-and-forward delivery. Mobile-terminated messages take the reverse path: the SMSF receives them from the SMSC and delivers them to the subscriber through the AMF.

02 / 02

UDM lookup validates the SMS subscription

The Ouroboros SMSF bridges 5G SA subscribers into the existing messaging infrastructure. It connects to the Ouroboros Next-Gen SMSC, or to a third-party SMSC over standard interfaces, so an operator adding 5G SA does not deploy a parallel messaging stack. The same SMSC that serves 2G, 3G, and LTE serves 5G through the SMSF.

02Use cases

5G SA launch, SMSC continuity, A2P delivery, private 5G — SMS from first attach.

01

SMS continuity at 5G SA launch

An operator launching 5G SA deploys the SMSF so subscribers keep sending and receiving SMS from first attach. Two-factor codes and alerts continue to work without a circuit-switched or IMS dependency.

02

Inbound roaming SMS to a 5G SA visitor

A subscriber roaming in on a visited 5G SA network receives home-network and A2P messages through the SMSF, which delivers them over NAS via the AMF while the home SMSC handles origination.

03

A2P delivery to 5G subscribers

Enterprise application-to-person messages, transaction alerts, and authentication codes reach 5G SA handsets via the SMSF and the SMSC, with no change to the originating A2P platform.

04

Private 5G messaging

A private 5G network uses the SMSF to deliver operational and alert messages to devices that attach over 5G SA without a separate messaging deployment.

Quote placeholder client input needed.

Operator CTO

CTO · Major MNO

03Specifications

5G SA function
SMSF (SMS Function)
Delivery method
SMS over NAS
Interfaces
N20 (AMF), N21 (UDM)
SMSC integration
Ouroboros Next-Gen SMSC or third-party SMSC
Protocols
HTTP/2 (SBI), MAP/Diameter to SMSC
Message types
Mobile-originated (MO), mobile-terminated (MT)
Subscription data
Retrieved from UDM
Message throughput
Contact us for current figures
Virtualisation
VMware, KVM, Docker, Kubernetes
Standards
3GPP 5G SA compliant
Availability
99.9999%
Business model
OPEX rental · CAPEX licence
04Inside the platform

01

SMS over NAS for 5G SA

The SMSF carries SMS inside 5G NAS signalling between the subscriber and the network. 5G SA subscribers send and receive text without a circuit-switched or IMS messaging dependency.

02

Bridges to the existing SMSC

The SMSF routes 5G messages to the Ouroboros Next-Gen SMSC or a third-party SMSC. Operators add 5G messaging without deploying a parallel SMS platform.

03

UDM subscription lookup over N21

The SMSF retrieves SMS subscription data from the UDM before routing. Messaging respects each subscriber's SMS subscription and service profile.

04

Mobile-originated and mobile-terminated delivery

The SMSF handles both directions through the AMF over N20. Sending and receiving both work for 5G SA subscribers from first attach.

05

A2P reach to 5G subscribers

Application-to-person traffic from the SMSC reaches 5G handsets through the SMSF. Two-factor codes and enterprise alerts deliver to 5G SA subscribers with no change to A2P platforms.

06

Standard SBI and SMSC interfaces

Service-based interfaces to the 5G core and standard interfaces to the SMSC. The SMSF connects to a third-party SMSC or 5G core without custom integration.

05Why Ouroboros

The SMSF is the function that keeps SMS working when a network turns up 5G Standalone. Its value is in what it connects to: the Ouroboros SMSF bridges 5G subscribers into the same SMSC that already serves 2G, 3G, and LTE, rather than standing up a separate 5G messaging silo. Operators running the Ouroboros Next-Gen SMSC add 5G coverage by adding the SMSF. Operators on a third-party SMSC connect over standard interfaces.

Carrier-grade, in production since 2004, deployable on COTS, virtualised, or cloud. OPEX rental is available.

Ouroboros Telecom

Give us your 5G core vendor, current SMSC, and launch date, and we'll confirm how the SMSF bridges 5G subscribers into your existing messaging infrastructure.