5G QoS does not stop inside the Core

5G QoS does not stop inside the Core.

It must be translated into radio behavior.

That is where QoS Flow and DRB mapping becomes important.

In 5G, the Core defines how traffic should be treated.

But the RAN must actually deliver that treatment over the air.

A simple way to understand it:

  • QoS Flow = service quality requirement
  • DRB = radio bearer that carries the user data

A PDU Session can contain multiple QoS Flows.

Each QoS Flow is identified by a QFI.

QFI tells the network which QoS Flow the packet belongs to.

5QI defines the QoS characteristics such as:

  • Priority
  • Packet delay budget
  • Packet error rate

Then SDAP maps the QoS Flow to the correct DRB.

So the full chain looks like this:

App / Service
→ PDU Session
→ QoS Flow
→ QFI
→ SDAP Mapping
→ DRB
→ gNB Radio Transmission
→ UPF / Data Network

This matters because different services need different treatment.

  • VoNR needs low delay and high priority.
  • Video needs throughput.
  • Best-effort internet can use normal/default treatment.
  • Gaming and XR need low latency and consistency.
  • IoT may need efficient periodic reporting.

Common troubleshooting clues:

  • Wrong QFI mapping
  • 5QI mismatch
  • DRB not established
  • SDAP mapping issue
  • Congested radio bearer
  • PCF / SMF policy issue

If QoS is configured correctly in the Core but the radio bearer mapping is wrong, the user experience can still fail.

That is why 5G engineers need to understand both sides:

Core-level QoS
RAN-level bearer delivery

Quick memory:

QoS Flow tells the network how traffic should be treated.
DRB carries that traffic over the radio interface.

PDU Session + QoS Flow + QFI + SDAP + DRB = 5G Service Quality Delivery

What should I explain next: 5QI, QFI or SDAP?

Linkedin: :backhand_index_pointing_down: