5G Voice Service Implementation Options in 5G NR

Introduction

"Voice options" is the name for the handful of ways a 5G subscriber's phone call can actually be delivered, given that the 5G Core carries no circuit-switched voice. Every option ultimately runs the same telephony service — IMS/MMTEL voice over an IP bearer with tight QoS — and they differ only in which radio and core carry it: 5G NR (VoNR), LTE after a move down from 5G (EPS Fallback to VoLTE), or LTE from the start (NSA VoLTE).

This matters throughout the network lifecycle. At registration, the network tells the UE whether IMS voice is even possible here (the IMS VoPS indicator). At call setup, the core requests a dedicated voice QoS flow, and the gNB decides in that instant whether to serve the call on NR or fall back to LTE. Getting the options straight is what turns "why did my 5G call drop to LTE?" from a mystery into a predictable consequence of coverage, UE capability, and operator configuration.

The page is grounded in TS 23.501 (system architecture and the 5G QoS model), TS 23.502 (session-management and mobility procedures, including fallback), and TS 24.501 (5G NAS, where the voice-domain indications live).

Why 5G needs "voice options" at all

The concrete reason options exist is a mismatch of maturity. Voice is unforgiving: a conversational call needs a guaranteed-bit-rate flow with bounded delay and loss for its entire duration, including at the cell edge and while moving. Early 5G NR often cannot promise that — it sits on high bands with patchy coverage, and many gNBs have not enabled voice admission yet. Data, by contrast, tolerates best-effort treatment. So operators launch 5G for data immediately but keep leaning on the mature, reliable LTE VoLTE stack for the call until VoNR coverage and support catch up. The "options" are simply the graceful ways to bridge that gap without dropping calls.

Why 5G Has No Native Circuit Voice

In 2G and 3G, voice rode a dedicated circuit-switched (CS) domain with its own MSC and CS bearers. LTE already dropped native CS voice and moved telephony onto IMS as VoLTE (Voice over LTE), carried on dedicated EPS bearers with strict QoS. 5G Standalone (SA) goes one step further: the 5G Core (5GC) is a packet-only, service-based architecture. There is no MSC, no CS bearer, and nothing CS-shaped to fall back to inside the 5GC. So the only way to deliver voice to a 5G UE is as media packets in an IMS session, described by the MMTEL telephony service.

Because voice is now "just data with strict QoS," it is delivered on QoS flows inside a PDU session, exactly like any other traffic — the difference is purely the QoS treatment. IMS signalling (the SIP messages that set up, modify and tear down the call) rides a non-GBR flow, and the conversational voice media rides a guaranteed-bit-rate (GBR) flow so the codec packets arrive on time with bounded delay and loss.

These 5QI values are standardised in TS 23.501, meaning every compliant network maps them to the same characteristics without per-operator negotiation. Each 5QI row fixes a resource type (GBR or non-GBR), a Priority Level, a Packet Delay Budget (PDB) and a Packet Error Rate (PER): 5QI=1 (GBR, conversational voice) carries a low PER and a ~100 ms PDB, while 5QI=5 (non-GBR, IMS signalling) is highest-priority so SIP setup is never starved. The individual flows are identified on the air by their QFI (QoS Flow Identifier) and governed by an ARP (Allocation and Retention Priority) that decides who wins when radio resources are scarce — which is exactly why a voice GBR flow can pre-empt best-effort data.

VoNR — Voice Stays on 5G

VoNR (Voice over NR) is the target end-state: the entire call — both signalling and media — is carried over 5G NR while the UE stays in 5G SA. It is the direct analogue of VoLTE, just anchored on the NR radio and the 5GC instead of the LTE radio and the EPC.

Concretely, when a call is set up the PCF authorises a dedicated 5QI=1 GBR flow, the SMF signals it to the gNB in a PDU Session Resource Modify request carrying the QoS profile, and the gNB reconfigures the radio bearer to carry the media. The codec packets (typically AMR-WB or EVS) then flow over NR and the conversation proceeds entirely on 5G.

Underneath, the gNB maps the incoming 5QI=1 QoS flow to a data radio bearer (DRB) and, over the air, applies the delay-sensitive tooling that makes conversational voice work on a packet radio: a short PDCP discard timer so late codec frames are dropped rather than delivered stale, robust-header-compression (ROHC) to shrink the IP/UDP/RTP headers of small voice packets, and typically RLC UM (unacknowledged mode) because retransmitting a 20 ms voice frame is pointless once its PDB has passed. The GBR guarantee is admission-controlled: the gNB will only accept the flow if it can reserve the Guaranteed Flow Bit Rate (GFBR) for the codec, which is why VoNR needs genuine coverage margin, not just a bar of signal.

The catch is that VoNR needs the full stack ready and good enough NR coverage to sustain a GBR voice flow for the whole call, including at the cell edge and during mobility. In early networks that condition often is not met — NR sits on high bands with patchy coverage, or the gNB has simply not enabled VoNR admission. That gap is exactly why EPS Fallback exists as the interim answer.

EPS Fallback — Borrow LTE for the Call

EPS Fallback (EPSFB) is the common early-deployment option. The UE camps on 5G SA and does its data on 5G, but the moment a voice call needs a media flow, the network moves the UE down to LTE/EPS and the call runs there as VoLTE. You keep the benefits of 5G data while re-using the mature VoLTE voice that already works reliably on LTE.

The trigger sequence is the thing to memorise. Notice the fallback is triggered by the 5QI=1 flow request, not by the SIP INVITE directly — the gNB never parses SIP; it reacts to the QoS flow the core asks it to set up:

1. The UE is in RRC_CONNECTED on 5G SA doing data. An incoming or outgoing call produces a SIP INVITE at the IMS layer over the 5QI=5 signalling flow (the detailed IMS call flow has its own page).
2. IMS session negotiation causes the PCF/SMF to request the dedicated voice QoS flow — the 5QI=1 GBR flow — to be set up towards the UE via the gNB (a PDU Session Resource Modify).
3. The gNB sees the 5QI=1 flow request and, per operator policy or because it lacks VoNR support/coverage, decides it will serve this call on LTE instead of NR. It may first order a B1 measurement of E-UTRA to pick a target.
4. The gNB moves the UE to E-UTRA/EPS: either an inter-RAT handover (measurement-based, seamless) or an RRCRelease with redirectedCarrierInfo pointing at an LTE carrier (faster to issue, but the UE must re-acquire LTE). It rejects/holds the 5QI=1 flow on the NR side.
5. On LTE the core re-establishes the session on the EPC (via N26 interface handover, or via a fresh TAU/attach after redirect) and the voice runs as ordinary VoLTE on a dedicated EPS bearer (QCI=1).

RAT Fallback vs EPS Fallback — the nuance

"Fallback" is used loosely, so pin down the flavours. The general term is RAT fallback: the network moves the voice UE to E-UTRA (the LTE radio) to serve the call. Where that E-UTRA cell connects — to the EPC or to the 5GC — determines the exact name and what the core looks like afterward.

Keep it simple. EPS Fallback means the UE genuinely leaves 5GS and lands on EPC-anchored LTE where VoLTE already lives; the PDU session is transferred to an EPS bearer context. RAT fallback within 5GS keeps the 5G Core but uses an LTE cell (an ng-eNB) attached to the 5GC, so the QoS model stays 5QI-based and the session never touches the EPC. Most early deployments do EPS Fallback because the EPC + LTE VoLTE stack is mature. Either way the voice is IMS-based — only the radio and core anchor change.

NSA VoLTE — Voice Anchored on LTE

Everything above assumes 5G Standalone (SA) with a 5GC. Many first-generation 5G networks are Non-Standalone (NSA), specifically EN-DC (E-UTRA New Radio Dual Connectivity): the UE is anchored on an LTE eNB for the control plane and uses NR only as a secondary node for extra data throughput. In NSA there is no 5GC and no NAS to NR at all — the master node is LTE and the core is the EPC.

Because the control plane and the core are LTE/EPC, voice in NSA is simply VoLTE, exactly as on a 4G network. There is no VoNR and no EPS Fallback to speak of, because the UE never left LTE for its signalling in the first place — NR was only ever a data booster. The voice call sets up on the LTE leg over a QCI=1 dedicated bearer while NR continues to carry (or is released for) user-plane data.

Fast Return — Getting Back to 5G

After an EPS Fallback call, you do not want the UE stranded on LTE, because then its data drops off 5G too and the "5G experience" evaporates for as long as the UE idles on LTE. Fast Return brings the UE back to NR quickly once the voice call on LTE ends.

When the VoLTE call finishes and the dedicated voice bearer is released, the LTE network releases the RRC connection with redirection information — an RRCConnectionRelease carrying redirectedCarrierInfo pointing at an NR carrier (or a measurement-based inter-RAT handover) — so the UE re-selects 5G promptly instead of idling on LTE until ordinary reselection would drift it back. Voice borrowed LTE for a few minutes, but the UE is back on 5G for data almost immediately.

Prerequisites — What Must Be True for Voice

Whether a UE even attempts an IMS voice call, and which option it lands on, is decided before any INVITE by three things lining up: what the network advertises, what the UE can do, and what the deployment actually supports. Get one wrong and the phone either falls back unnecessarily or shows "no voice service."

The pivotal signal is the IMS Voice over PS Session (IMS VoPS) indicator. During registration the AMF returns it to the UE in the Registration Accept (in the 5GS network feature support IE, per access — 3GPP and non-3GPP), telling the UE whether "IMS voice over PS session" is supported in the current registration area. If IMS VoPS says voice-over-PS is not supported, a voice-centric UE may treat the cell as unsuitable for voice and follow its configured voice-domain preference (for example, fall back toward E-UTRA/EPS). If it says supported, the UE knows it can attempt IMS voice on 5G — and the network's later behaviour (serve on NR = VoNR, or trigger EPS Fallback) fills in the rest.

The UE side matters just as much. A UE advertises whether it supports VoNR; one that does not will provoke EPS Fallback even where the gNB could serve VoNR. The UE's usage setting (voice-centric vs data-centric) governs what it does when voice-over-PS is unavailable: a voice-centric UE leaves an access that cannot carry voice to seek one that can, while a data-centric UE stays on 5G for data and forgoes voice there. The exact NAS/RRC signalling for all of this is covered on the Voice Signalling page (see the bridge below).

Choosing an Option — VoNR vs EPSFB vs VoLTE

Which option a UE uses depends on network support, coverage, and whether the deployment is SA or NSA. The comparison below is the one to keep in your head; the "when used" table maps each option to the deployment that selects it.

Reading the two tables together: a UE on NSA always does VoLTE — VoNR never arises. A UE on SA does VoNR only if the whole chain (UE capability, gNB admission, coverage, IMS) is ready; otherwise the gNB triggers EPS Fallback when the 5QI=1 flow is requested, and the call becomes VoLTE on LTE with a Fast Return afterward. There is deliberately no "circuit voice" row — that domain does not exist in 5GC.

Summary

The 5G Core has no circuit-switched voice, so every "voice option" is really the same thing — IMS/MMTEL voice on an IP flow with tight QoS (5QI=1 GBR media, 5QI=5 non-GBR signalling) — differing only in which radio and core carry it. VoNR keeps the whole call on 5G NR and is the target end-state; EPS Fallback moves an SA UE down to LTE/EPC so the call runs as VoLTE; NSA VoLTE is native LTE from the start because the UE was never on a 5GC.

The decision is made mechanically at call setup: the core requests the 5QI=1 GBR flow, and the gNB either admits it on NR (VoNR) or, lacking VoNR support or coverage, triggers fallback by handover or RRCRelease+redirectedCarrierInfo. Fast Return then brings the UE back to NR after the call so data stays on 5G. Whether voice is attempted on 5G at all is gated earlier by the IMS VoPS indicator plus the UE's capability and voice-centric/data-centric usage setting.

Three traps to avoid: EPS Fallback is not CSFB (no CS domain exists to fall back to); NSA VoLTE is not EPS Fallback (different starting point, same VoLTE result); and the SIP INVITE does not trigger fallback (the 5QI=1 flow request does). Keep those straight and the whole voice landscape reduces to "IMS voice, delivered over whichever RAT and core are ready."

Quick LTE 4G / 5G NR Interview Questions