CompoundLearn

5G QoS and 5QI: Service Requirements and Network Slices Interview Prep

5G QoS framework — 5QI table, GBR vs non-GBR, packet delay budget, packet error rate, QoS flows, DRB mapping via SDAP, and slicing integration.

Quick answer

5G QoS is the framework that translates application-level service requirements into per-flow scheduling and resource-allocation policy across the 5GC and RAN.

5G QoS is the network-layer integration question in cellular interviews — the candidate has to navigate the 5GC, RAN, and air-interface layers in one coherent model.

Editorial review

Written by

CompoundLearn editorial team

Wireless / RF / hardware engineering

Reviewed by

CompoundLearn editorial team

Wireless / RF / hardware engineering

Last reviewed

Built from curated topic maps, editorial validation, and subject-matter review so the page stays aligned with the interview intent and the current content pipeline.

What it is

5G QoS is the framework that translates application-level service requirements into per-flow scheduling and resource-allocation policy across the 5GC and RAN. Every QoS-aware behavior in a 5G network — voice traffic getting scheduled ahead of best-effort downloads, URLLC industrial-control packets meeting their 10⁻⁵ reliability target (see /topics/nr-urllc-mini-slot-preemption), network-slice-specific QoS treatment — rests on the 5QI / QoS-flow / DRB / SDAP stack defined in 3GPP TS 23.501. A candidate must navigate all four layers. The 5QI (5G QoS Indicator) is a scalar value that identifies a standardized combination of QoS characteristics: resource type (GBR vs non-GBR), priority level, packet delay budget (PDB), packet error rate (PER), default maximum data burst, and averaging window. 3GPP standardizes a table of 5QI values so operators and roaming partners interpret the same value identically. 5QI=1 is conversational voice (GBR, priority 20, PDB 100 ms, PER 10⁻²); 5QI=9 is default best-effort (non-GBR); 5QI=82/83/85 are mission-critical and URLLC services with tight delay budgets and stringent error-rate targets. Operators can also use non-standardized 5QIs within designated ranges for vendor-specific services. The GBR vs non-GBR split is the central scheduling distinction. GBR (Guaranteed Bit Rate) 5QIs require the gNB scheduler to reserve a guaranteed minimum bit rate — they are scheduled as priority traffic before non-GBR. Conversational voice, conversational video, real-time gaming, and mission-critical services use GBR. Non-GBR 5QIs are best-effort — scheduled opportunistically with no bit-rate guarantee, sharing remaining cell capacity. Admission control: when the cell cannot honor new GBR commitments, new GBR flows are blocked rather than degrading existing ones. The QoS flow is the 5GC-level traffic class. Each flow is identified by a QFI (QoS Flow Identifier, 6-bit value) and tied to a 5QI via the QoS profile. The 5GC sets up QoS flows at PDU-session establishment based on application requirements. The DRB (Data Radio Bearer) is the RAN-level radio bearer carrying user-plane packets; the gNB configures DRBs via RRC reconfiguration (see /topics/nr-rrc-states). SDAP (Service Data Adaptation Protocol) in both UE and gNB maps QoS flows to DRBs — multiple compatible flows can share one DRB to save signaling overhead, or each flow can have its own DRB for distinct radio-layer treatment. SDAP marks each PDU with the source QFI in the SDAP header so the gNB scheduler applies per-flow QoS handling. SDAP is the protocol layer that did not exist in LTE; it was added in NR (see /topics/5g-nr) to bridge the 5GC per-flow QoS model with the RAN per-DRB bearer model. The integration with network slicing: a network slice (identified by S-NSSAI) is a logical network instance with its own AMF/SMF/UPF deployment, isolated from other slices. Each slice can carry multiple QoS flows per UE, each with its own 5QI. Slices provide isolation and service-class differentiation at the network level; QoS flows provide per-flow QoS treatment within a slice. A UE can simultaneously connect to multiple slices (e.g., eMBB consumer slice plus URLLC industrial slice), each with its own QoS flows. The gNB scheduler implements 5QI QoS through several mechanisms: GBR flows get priority scheduling to meet bit-rate and delay commitments; the 5QI priority level sets relative priority among competing GBR flows; PDB drives scheduling urgency (flows approaching delay budget scheduled sooner); PER drives MCS table choice (URLLC 5QIs use MCS Table 3 / qLowSE for 10⁻⁵ BLER); admission control prevents new GBR flows when capacity is insufficient. The scheduler typically runs proportional-fair with 5QI-derived weights and HARQ retx priority on top.

Why interviewers ask

5G QoS is the network-layer integration question in cellular interviews — the candidate has to navigate the 5GC, RAN, and air-interface layers in one coherent model. A candidate who fluently distinguishes 5QI values, GBR vs non-GBR, QoS flows vs DRBs, and the SDAP layer is showing the cross-layer understanding that staff network-architect and 5GC-engineer roles require. The 5QI table question is the foundation. Strong candidates can name several standardized 5QIs (1 for voice, 9 for default, 82/83 for URLLC) and explain what each parameter (resource type, priority, PDB, PER) drives in scheduler behavior. Weak candidates know 5QI exists but cannot quote specific values or characteristics. The GBR-vs-non-GBR distinction is the scheduling probe. Strong candidates explain that GBR reserves a guaranteed bit rate and gets priority scheduling, while non-GBR is best-effort. They connect this to admission control (block new GBR when cell is congested) and to the priority-level mechanism for differentiating among competing GBR flows. Candidates who collapse the two miss the central scheduling lever. The QoS-flow-to-DRB mapping question is the architecture probe. Strong candidates explain that QoS flows are 5GC-level (per-flow, identified by QFI), DRBs are RAN-level (radio bearer), and SDAP bridges them — multiple compatible flows can share a DRB, or each flow can get its own. Candidates who use "flow" and "DRB" interchangeably reveal a layer-confusion that interviewers will probe further. SDAP is the depth probe. Strong candidates know that SDAP is the new NR-only protocol layer that maps QoS flows to DRBs and marks PDUs with QFI. They connect it to the historical LTE difference — LTE had per-bearer QCI without a separate flow concept; NR added SDAP because the 5GC moved to per-flow QoS. Candidates who do not know SDAP exists or who confuse it with PDCP miss a key protocol-stack distinction. The slice-vs-flow question is the senior-level architecture probe. Strong candidates distinguish slices (logical network instances with own AMF/SMF/UPF, isolated by S-NSSAI) from QoS flows (per-flow QoS treatment within a slice) and explain that a UE can simultaneously be in multiple slices each with its own flows. Candidates who treat slices and flows as the same concept have not internalized the network-slicing architecture.

Common mistakes

The most common mistake is collapsing 5QI into a single concept. The 5QI value carries multiple parameters (resource type, priority, PDB, PER, default burst), and each drives different scheduler behavior. Candidates who treat 5QI as just "the QoS class number" miss the parameter-vector structure. A second gap is conflating GBR and non-GBR. They have fundamentally different scheduler treatment — GBR gets reserved capacity and priority; non-GBR is opportunistic. The admission-control implications differ too — new GBR flows can be blocked, new non-GBR flows are usually admitted opportunistically. Candidates who do not distinguish miss the central scheduling lever. A third gap is confusing QoS flow with DRB. Flow is 5GC-level (identified by QFI, tied to 5QI); DRB is RAN-level (radio bearer with its own PDCP/RLC instances). SDAP maps between them, with flexibility to share DRBs across compatible flows or assign per-flow DRBs. Candidates who use the terms interchangeably reveal a layer-confusion. A fourth gap is missing SDAP entirely. SDAP is the new NR-only protocol layer that bridges 5GC per-flow QoS to RAN per-DRB bearers. LTE had no equivalent because LTE used per-bearer QCI without a separate flow concept. Candidates who do not know SDAP exists miss a key protocol-stack distinction. A fifth gap is confusing slices with flows. Slices are logical network instances (own AMF/SMF/UPF, S-NSSAI-identified, network-level isolation); flows are per-flow QoS treatment within a slice. A UE can be in multiple slices, each with its own flows. Candidates who treat them as equivalent miss the network-slicing-vs-QoS-flow architecture. A sixth gap is treating PDB as end-to-end latency. PDB is the UPF-to-UE budget at the IP layer; additional latency from application server to UPF and from UE to application is separate. Candidates who quote "5QI=1 PDB=100 ms" as end-to-end voice latency overstate the QoS contribution. See /topics/nr-mac-scheduling for the scheduler context, /topics/nr-channel-coding for the MCS-table connection, and /topics/nr-architecture-nsa-sa-cu-du for the 5GC SBA functions.

Standardized 5QI Values — Representative Examples

5QIResource TypePriorityPDBPERTypical Service
1GBR20100 ms10⁻²Conversational voice
2GBR40150 ms10⁻³Conversational video
3GBR3050 ms10⁻³Real-time gaming
4GBR50300 ms10⁻⁶Non-conversational video (buffered)
9Non-GBR90300 ms10⁻⁶Default best-effort (TCP-based)
82GBR1960 ms10⁻²Mission-critical voice
83GBR2230 ms10⁻⁵URLLC discrete automation
85GBR215 ms10⁻⁵URLLC electricity distribution

Sample interview questions

  1. A 5G UE has a QoS flow with 5QI=1 (conversational voice). What does 5QI=1 specify, and what kind of resource-allocation behavior does it require from the gNB scheduler?
    • A. 5QI=1 specifies best-effort delivery with no latency guarantee.
    • B. 5QI=1 is a standardized Guaranteed Bit Rate (GBR) 5QI value for conversational voice: priority level 20, packet delay budget 100 ms, packet error rate 10⁻². GBR means the gNB must reserve a guaranteed minimum bit rate (typically tens of kbps for voice). The scheduler treats GBR flows as priority traffic — they get scheduled before non-GBR best-effort traffic to meet their delay-budget commitment. ✓
    • C. 5QI=1 is for emergency services only.
    • D. 5QI=1 means the flow uses 1 Mbps bandwidth.

    Option B is correct. 3GPP TS 23.501 defines a standardized table of 5QI (5G QoS Indicator) values, each mapping to a specific combination of resource-type, priority level, packet delay budget (PDB), packet error rate (PER), and other parameters. 5QI=1 specifically is: - **Resource Type**: GBR (Guaranteed Bit Rate) - **Priority level**: 20 (lower number = higher priority) - **Packet Delay Budget (PDB)**: 100 ms - **Packet Error Rate (PER)**: 10⁻² - **Typical service**: conversational voice GBR means the gNB scheduler must reserve a guaranteed minimum bit rate for the flow — typically tens of kbps for voice. The scheduler treats GBR flows as priority traffic, scheduling them ahead of non-GBR best-effort traffic to meet the delay-budget commitment. If the cell becomes congested to the point that GBR commitments cannot be honored, the operator-configured admission control should block new GBR flows rather than degrade existing ones. Non-GBR 5QIs (e.g., 5QI=9 for default best-effort) get scheduled opportunistically without a guaranteed bit rate. Other 5QI examples: - 5QI=2: Conversational video (GBR, priority 40, PDB 150 ms, PER 10⁻³) - 5QI=82: Discrete automation (delay-critical GBR, priority 19, PDB 10 ms, PER 10⁻⁴, MDBV 255 B) - 5QI=83: Discrete automation / V2X (delay-critical GBR, priority 22, PDB 10 ms, PER 10⁻⁴, MDBV 1354 B) - 5QI=9: Default non-GBR (best-effort) Each 5QI is standardized so that operators and roaming partners interpret the same value identically. Operators can also define non-standardized (vendor-specific) 5QIs within designated ranges, but the standardized values are the interoperability baseline. Option A misses GBR vs non-GBR. Option C is wrong — 5QI=1 is for normal conversational voice, not emergency-only. Option D misreads 5QI=1 as a bit-rate value rather than a QoS-table index.

  2. How does a UE's QoS flow map to a DRB (Data Radio Bearer) in 5G NR, and what role does SDAP play?
    • A. QoS flow and DRB are identical; the names are synonyms.
    • B. A QoS flow is the 5GC-level traffic class identified by a QFI (QoS Flow Identifier) and tied to a 5QI value. A DRB is the RAN-level radio bearer that carries the actual user-plane packets between UE and gNB. The SDAP (Service Data Adaptation Protocol) layer in the RAN maps QoS flows to DRBs — multiple flows can share one DRB if they have compatible QoS characteristics, or each flow can have its own DRB. SDAP marks each PDU with its source QFI so the gNB scheduler can apply the appropriate QoS handling. ✓
    • C. SDAP only operates on the UE side; the gNB does not implement SDAP.
    • D. DRBs are configured by the AMF; QoS flows are configured by the gNB.

    Option B is correct. The 5G QoS architecture has two layers of bearer abstraction: **QoS Flow** (5GC layer): - Identified by a QFI (QoS Flow Identifier), 6-bit value - Tied to a 5QI value via the QoS profile - The granularity at which the 5GC manages QoS — each flow is treated as one QoS class **DRB / Data Radio Bearer** (RAN layer): - The actual radio bearer the UE and gNB use for user-plane traffic - Configured by the gNB via RRC reconfiguration - Has its own PDCP and RLC instances **SDAP** (Service Data Adaptation Protocol) bridges the two: - Implemented in both UE and gNB - Maps each QoS flow to a DRB based on operator policy - Can map multiple compatible flows to one DRB (sharing RLC/PDCP instances) or give each flow its own DRB - Marks each user-plane PDU with the source QFI in the SDAP header so the gNB scheduler can apply the per-flow QoS treatment Why the two-layer split exists: - 5GC manages QoS at the flow level (granular policy, billing, etc.) - RAN manages bearers at the DRB level (radio-layer scheduling, HARQ, etc.) - The mapping flexibility lets the RAN consolidate compatible flows to save signaling overhead, or separate flows that need different radio-layer treatment (different HARQ profile, different RLC mode) Common configurations: - One flow per DRB: simplest, used for high-priority flows like voice or URLLC - Multiple flows per DRB: used for compatible non-GBR traffic to save RLC/PDCP instances - The mapping is per-UE per-session, configured at session establishment Option A collapses two distinct concepts. Option C is wrong — SDAP is symmetric, runs in both UE and gNB. Option D inverts the configuration responsibility — DRBs are gNB-configured, QoS flows are 5GC-configured. Production reality: SDAP-aware flow management is one of the operational details that distinguishes proper 5G deployments from "5G non-standalone delivering only LTE-equivalent QoS."

Frequently asked questions

What is 5QI?
5QI (5G QoS Indicator) is a scalar value (integer) that identifies a standardized combination of QoS characteristics — resource type (GBR vs non-GBR), priority level, packet delay budget, packet error rate, default maximum data burst, and averaging window. The 3GPP TS 23.501 specification defines the standardized 5QI table so operators and roaming partners interpret 5QI values identically. Each 5QI maps to a specific service type — 5QI=1 for conversational voice, 5QI=2 for conversational video, 5QI=9 for default best-effort, 5QI=82/83 for mission-critical and URLLC services. Operators can also use non-standardized 5QIs within designated ranges for vendor-specific services.
What is the difference between GBR and non-GBR 5QIs?
GBR (Guaranteed Bit Rate) 5QIs require the gNB to reserve a guaranteed minimum bit rate for the flow — the scheduler treats them as priority traffic, scheduled ahead of non-GBR best-effort traffic to meet their delay-budget commitment. Conversational voice (5QI=1), conversational video (5QI=2), real-time gaming (5QI=3), and mission-critical services use GBR. Non-GBR 5QIs are best-effort — they get scheduled opportunistically without a bit-rate guarantee, sharing remaining cell capacity after GBR commitments are met. Default best-effort traffic (5QI=9) and most non-real-time application traffic use non-GBR. Admission control: if the cell cannot meet new GBR commitments, the operator-configured admission control should block new GBR flows rather than degrade existing ones.
What is Packet Delay Budget (PDB)?
PDB is the maximum allowed latency for a packet between the UPF (User Plane Function in the 5GC) and the UE, measured at the IP layer. PDB is one of the parameters specified per 5QI and bounds how the gNB scheduler must prioritize the flow. Examples: 5QI=1 (conversational voice) has PDB=100 ms; 5QI=82 (discrete automation) has PDB=10 ms; 5QI=84 (discrete automation) has PDB=30 ms. The scheduler must allocate resources so the per-packet delay stays under the PDB — which is an upper bound, not an average. Note that PDB is a UPF-to-UE budget — additional latency from the application server to UPF and from UE to application is separate.
What is Packet Error Rate (PER)?
PER is the maximum allowed rate of packet loss for a flow, specified per 5QI. Examples: 5QI=1 has PER=10⁻² (voice tolerates moderate loss with concealment); 5QI=83 (URLLC) has PER=10⁻⁵ (one error per 100,000 packets — the URLLC reliability target). PER drives the choice of MCS table — URLLC 5QIs use MCS Table 3 (qLowSE) targeting 10⁻⁵ BLER rather than the 10⁻¹ BLER target of normal eMBB MCS tables. See /topics/nr-channel-coding for the MCS-table context.
What is a QoS flow and how does it map to DRBs?
A QoS flow is the 5GC-level traffic class identified by a QFI (QoS Flow Identifier, 6-bit value) and tied to a 5QI value via the QoS profile. The 5GC sets up QoS flows at PDU-session establishment based on application requirements. The RAN-side DRB (Data Radio Bearer) is the actual radio bearer carrying user-plane packets between UE and gNB. SDAP (Service Data Adaptation Protocol) in both UE and gNB maps QoS flows to DRBs — multiple compatible flows can share one DRB to save signaling overhead, or each flow can have its own DRB for distinct radio-layer treatment. SDAP marks each PDU with the source QFI so the gNB scheduler applies the correct per-flow QoS handling.
What is SDAP?
SDAP (Service Data Adaptation Protocol) is the 5G NR protocol layer that adapts 5GC QoS flows to RAN DRBs. SDAP sits above PDCP in the user-plane protocol stack and is implemented in both UE and gNB. Its functions: map QoS flows to DRBs per UE configuration, mark each user-plane PDU with the source QFI so the receiver knows which QoS flow the packet belongs to, and support reflective QoS where the UE can echo the gNB's QFI marking back on uplink. SDAP is the bridge between the 5GC QoS model (per-flow) and the RAN bearer model (per-DRB) — a layer that did not exist in LTE because LTE had a different QoS architecture (per-bearer QCI rather than per-flow QFI).
How does 5G QoS relate to network slicing?
Network slices and QoS flows are different but related abstractions. A network slice (identified by S-NSSAI) is a logical network instance with its own AMF/SMF/UPF deployment, isolated from other slices (see /topics/network-slicing-explained). Each slice can have multiple QoS flows per UE, each flow with its own 5QI. Slices provide isolation and service-class differentiation at the network level (e.g., one slice for eMBB consumer broadband, another for URLLC industrial automation, another for IoT); QoS flows provide per-flow QoS treatment within a slice. A UE can simultaneously connect to multiple slices, each with its own set of QoS flows. The NSSF (Network Slice Selection Function) in the 5GC selects the appropriate slice per UE-service pairing.
How does the gNB scheduler implement 5QI QoS?
The gNB scheduler (see /topics/nr-mac-scheduling) implements per-flow QoS in several ways: (1) scheduling order follows the 5QI priority level, not GBR-vs-non-GBR — a high-priority non-GBR flow (e.g. 5QI 5 IMS signalling, priority 10) outranks a lower-priority GBR flow (5QI 1 voice, priority 20); GBR instead guarantees a reserved minimum bit rate and admission control; (2) the priority-level field of the 5QI sets relative priority among multiple GBR flows competing for resources; (3) PDB drives the scheduler's urgency — flows approaching their delay budget get scheduled sooner; (4) PER drives MCS table choice — URLLC 5QIs use MCS Table 3 (qLowSE) for 10⁻⁵ BLER; (5) admission control prevents new GBR flows when capacity is insufficient to honor existing GBR commitments. The scheduler typically runs a proportional-fair base algorithm with 5QI-derived weights applied per flow, with HARQ retx priority on top.

Related topics

Pillar

Siblings

Practice

Essential AI-Native Skills for 5G QoS and 5QI: Service Requirements and Network Slices

Modern engineering work increasingly uses AI tools for design and code review, debugging, documentation, test and testbench generation, and workflow automation. The goal is not to let AI replace engineering judgment — it is to move faster while keeping verification discipline.

  • Use AI to explain unfamiliar code, logs, waveforms, datasheets, or test failures.
  • Break large problems into small, reviewable steps you can verify independently.
  • Ask AI for hypotheses, then validate them against tests, measurements, simulations, or lab data.
  • Version-control your analysis scripts, testbenches, and configs — keep changes small and reviewable.
  • Document your assumptions, design tradeoffs, and debugging decisions.
  • Verify AI output before trusting it: run the checks that fit the domain — unit tests, linters, simulations, or bench/lab measurements.
  • Review AI output for correctness, edge cases, and real-world consequences.

5G QoS and 5QI: Service Requirements and Network Slices — coming to the question bank

The adaptive practice engine is already live for core wireless, RF, and ML systems. 5G QoS and 5QI: Service Requirements and Network Slices isn't covered in the question bank yet — get notified when it's added.

One email when this topic launches. Nothing else. Unsubscribe in one click.