3GPP specification 23.

501 defined the following 5G QoS Parameters as part of QoS

Implementation.

 5G QoS Identifier (5GQI)

 Allocation and Retention Priority (ARP)
 Reflective QoS Attribute (RQA)
 Notification Control
 Flow Bit Rates
 Aggregate Bit Rates
 Default values
 Maximum Packet Loss Rate

5G QoS Identifier (5GQI)

A 5QI is a scalar that is used as a reference to 5G QoS characteristics  i.e. access node-specific
parameters that control QoS forwarding treatment for the QoS Flow (e.g. scheduling weights,
admission thresholds, queue management thresholds, link layer protocol configuration, etc.).

 Standardized 5QI values have one-to-one mapping to a standardized combination of 5G

QoS characteristics .
 The 5G QoS characteristics for pre-configured 5QI values are pre-configured in the
Access Node (gNB).
 Standardized or pre-configured 5G QoS characteristics, are indicated through the 5QI
value, and are not signalled on any interface, unless certain 5G QoS characteristics are
modified .
 The 5G QoS characteristics for QoS Flows with dynamically assigned 5QI are signalled
as part of the QoS profile.

Allocation and Retention Priority (ARP)

The QoS parameter ARP contains information about the priority level, the pre-emption capability
and the pre-emption vulnerability. The ARP priority level defines the relative importance of a
resource request to allows in deciding whether a new QoS Flow may be accepted or needs to be
rejected in the case of resource limitations (typically used for admission control of GBR traffic). It
may also be used to decide which existing QoS Flow to pre-empt during resource limitations.
ARP has following characteristics:

 The range of the ARP priority level is 1 to 15 with 1 as the highest level of priority
 The ARP priority levels 1-8 should only be assigned to resources for services that are
authorized to receive prioritized treatment within an operator domain (i.e. that are
authorized by the serving network)
 The ARP priority levels 9-15 may be assigned to resources that are authorized by the
home network and thus applicable when a UE is roaming
 The ARP pre-emption capability defines whether a service data flow may get resources
that were already assigned to another service data flow with a lower ARP priority level
 The ARP pre-emption capability and the ARP pre-emption vulnerability shall be either set
to ‘enabled’ or ‘disabled’
 The ARP pre-emption vulnerability defines whether a service data flow may lose the
resources assigned to it in order to admit a service data flow with higher ARP priority
level
 The ARP pre-emption vulnerability of the QoS Flow which the default QoS rule is
associated with should be set appropriately to minimize the risk of unnecessary release
of this QoS Flow
Reflective QoS Attribute (RQA)

The  RQA is an optional parameter which indicates that certain traffic (not necessarily all) carried
on this QoS Flow is subject to Reflective QoS. Only when the RQA is signalled for a QoS Flow,
the RAN/AN enables the transfer of the RQI for AN resource corresponding to this QoS Flow.
The RQA may be signalled to NG-RAN via the N2 reference point at UE context establishment in
NG-RAN and at QoS Flow establishment or modification.

Notification Control

The QoS Parameter Notification control indicates whether notifications are requested from the
NG-RAN when the GFBR can no longer (or can again) be guaranteed for a QoS Flow during the
lifetime of the QoS Flow. Notification control may be used for a GBR QoS Flow if the application
traffic is able to adapt to the change in the QoS (e.g. if the AF is capable to trigger rate
adaptation).

 The SMF shall only enable Notification control when the QoS Notification Control
parameter is set in the PCC rule (received from the PCF) that is bound to the QoS Flow.
 The Notification control parameter is signalled to the NG-RAN as part of the QoS profile.
 If, for a given GBR QoS Flow, Notification control is enabled and the NG-RAN
determines that the GFBR can no longer be guaranteed, NG-RAN shall send a
notification towards SMF and keep the QoS Flow (i.e. while the NG-RAN is not delivering
the requested GFBR for this QoS Flow), unless specific conditions at the NG-RAN
require the release of the NG-RAN resources for this GBR QoS Flow, e.g. due to Radio
link failure or RAN internal congestion. The NG-RAN should try to guarantee the GFBR
again.
 Upon receiving a notification from the NG-RAN that the GFBR can no longer be
guaranteed, the SMF may forward the notification to the PCF, 5GC may initiate N2
signalling to modify or remove the QoS Flow
 When the NG-RAN determines that the GFBR can be guaranteed again for a QoS Flow
(for which a notification that the GFBR can no longer be guaranteed has been sent), the
NG-RAN shall send a notification, informing the SMF that the GFBR can be guaranteed
again and the SMF may forward the notification to the PCF,  The NG-RAN shall send a
subsequent notification that the GFBR can no longer be guaranteed whenever
necessary.
 During a handover, the Source NG-RAN does not explicitly inform the Target NG-RAN
about those QoS Flows for which a notification that the GFBR can no longer be
guaranteed has been sent. The Target NG-RAN performs admission control rejecting any
QoS Flows for which resources cannot be permanently allocated. The accepted QoS
Flows are included in the N2 Path Switch Request message from the NG-RAN to the
AMF.

Flow Bit Rates

For GBR QoS Flows only, the additional QoS parameters are Guaranteed Flow Bit Rate (GFBR)
and Maximum Flow Bit Rate (MFBR) applicable for Uplink  and Downlink.

 The GFBR denotes the bit rate that is guaranteed to be provided by the network to the
QoS Flow over the Averaging Time Window
 The MFBR limits the bit rate to the highest bit rate that is expected by the QoS Flow (e.g.
excess traffic may get discarded or delayed by a rate shaping or policing function at the
UE, RAN, UPF)

Bit rates above the GFBR value and up to the MFBR value, may be provided with relative priority
determined by the Priority Level of the QoS Flows. GFBR and MFBR are signalled to the (R)AN
in the QoS Profile and signalled to the UE as QoS Flow level QoS parameter for each individual
QoS Flow.

Aggregate Bit Rates

Each PDU Session of a UE is associated with the following aggregate rate limit QoS parameter:

 per Session Aggregate Maximum Bit Rate (Session-AMBR). The subscribed Session-
AMBR is a subscription parameter which is retrieved by the SMF from UDM. SMF may
use the subscribed Session-AMBR or modify it based on local policy or use the
authorized Session-AMBR received from PCF to get the Session-AMBR, which is
signalled to the appropriate UPF entity/ies to the UE and to the (R)AN (to enable the
calculation of the UE-AMBR). The Session-AMBR limits the aggregate bit rate that can
be expected to be provided across all Non-GBR QoS Flows for a specific PDU Session.
The Session-AMBR is measured over an AMBR averaging window which is a
standardized value. The Session-AMBR is not applicable to GBR QoS Flows.

Each UE is associated with the following aggregate rate limit QoS parameter:

 per UE Aggregate Maximum Bit Rate (UE-AMBR). The UE-AMBR limits the aggregate
bit rate that can be expected to be provided across all Non-GBR QoS Flows of a UE.
Each (R)AN shall set its UE-AMBR to the sum of the Session-AMBR of all PDU Sessions
with active user plane to this (R)AN up to the value of the subscribed UE-AMBR. The
subscribed UE-AMBR is a subscription parameter which is retrieved from UDM and
provided to the (R)AN by the AMF. The UE-AMBR is measured over an AMBR averaging
window which is a standardized value. The UE-AMBR is not applicable to GBR QoS
Flows.

Default values

For each PDU Session Setup, the SMF retrieves the subscribed default values for the 5QI and
the ARP priority level and optionally, the 5QI Priority Level, from the UDM. The subscribed
default 5QI value shall be a Non-GBR 5QI from the standardized value range.

 The SMF may change the subscribed values for the default 5QI and the ARP priority
level and if received, the 5QI Priority Level, based on local configuration or interaction
with the PCF to set QoS parameters for the QoS Flow which the default QoS rule is
associated with
 The SMF shall set the ARP pre-emption capability and the ARP pre-emption vulnerability
of the QoS Flow which the default QoS rule is associated with based on local
configuration or interaction with the PCF
 The SMF shall apply the same values for the ARP priority level, the ARP pre-emption
capability and the ARP pre-emption vulnerability for all QoS Flows of the PDU Session
unless a different ARP setting is required for a QoS Flow
 If dynamic PCC is not deployed, the SMF can have a DNN based configuration to enable
the establishment of a GBR QoS Flow as the QoS Flow that is associated with the
default QoS rule. This configuration contains a standardized GBR 5QI as well as GFBR
and MFBR for UL and DL.

Maximum Packet Loss Rate

The Maximum Packet Loss Rate (UL, DL) indicates the maximum rate for lost packets of the
QoS flow that can be tolerated in the uplink and downlink direction. . This is provided to the QoS
flow if it is compliant to the GFBR.
Reference: 3GPP TS 23.501; System architecture for the 5G System (5GS)

[Link]  General
This clause specifies the 5G QoS characteristics associated with 5QI. The characteristics describe the packet
forwarding treatment that a QoS Flow receives edge-to-edge between the UE and the UPF in terms of the
following performance characteristics:

1. Resource Type (GBR, Delay critical GBR or Non-GBR);

2. Priority Level;
3. Packet Delay Budget (including Core Network Packet Delay Budget);
4. Packet Error Rate;
5. Averaging window (for GBR and Delay-critical GBR resource type only);
6. Maximum Data Burst Volume (for Delay-critical GBR resource type only).

The 5G QoS characteristics should be understood as guidelines for setting node specific parameters for each
QoS Flow e.g. for 3GPP radio access link layer protocol configurations.
Standardized or pre-configured 5G QoS characteristics, are indicated through the 5QI value, and are not
signalled on any interface, unless certain 5G QoS characteristics are modified as specified in clauses [Link],
[Link], [Link], and [Link].
NOTE: As there are no default values specified, pre-configured 5G QoS characteristics have to include all of
the characteristics listed above.
Signalled 5G QoS characteristics are provided as part of the QoS profile and shall include all of the
characteristics listed above.
[Link]  Resource Type
The Resource Type determines if dedicated network resources related to a QoS Flow-level Guaranteed Flow
Bit Rate (GFBR) value are permanently allocated (e.g. by an admission control function in a radio base
station).
GBR QoS Flows are therefore typically authorized "on demand" which requires dynamic policy and charging
control. A GBR QoS Flow uses either the GBR resource type or the Delay-critical GBR resource type. The
definition of PDB and PER are different for GBR and Delay-critical GBR resource types, and the MDBV
parameter applies only to the Delay-critical GBR resource type.
A Non-GBR QoS Flow may be pre-authorized through static policy and charging control. A Non-GBR QoS Flow
uses only the Non-GBR resource type.
[Link]  Priority Level
The Priority Level associated with 5G QoS characteristics indicates a priority in scheduling resources among
QoS Flows. The lowest Priority Level value corresponds to the highest priority.
The Priority Level shall be used to differentiate between QoS Flows of the same UE, and it shall also be used
to differentiate between QoS Flows from different UEs.
In the case of congestion, when all QoS requirements cannot be fulfilled for one or more QoS Flows, the
Priority Level shall be used to select for which QoS Flows the QoS requirements are prioritised such that a
QoS Flow with Priority Level value N is priorized over QoS Flows with higher Priority Level values (i.e. N+1,
N+2, etc).In the case of no congestion, the Priority Level should be used to define the resource distribution
between QoS Flows. In addition, the scheduler may prioritize QoS Flows based on other parameters (e.g.
resource type, radio condition) in order to optimize application performance and network capacity.
Every standardized 5QI is associated with a default value for the Priority Level -specified in QoS
characteristics Table [Link]). Priority Level may also be signalled together with a standardized 5QI to the
-R)AN, and if it is received, it shall be used instead of the default value.
Priority Level may also be signalled together with a pre-configured 5QI to the (R)AN, and if it is received, it
shall be used instead of the pre-configured value.
[Link]  Packet Delay Budget  Word-p. 136
The Packet Delay Budget (PDB) defines an upper bound for the time that a packet may be delayed between
the UE and the UPF that terminates the N6 interface. For a certain 5QI the value of the PDB is the same in UL
and DL. In the case of 3GPP access, the PDB is used to support the configuration of scheduling and link layer
functions (e.g. the setting of scheduling priority weights and HARQ target operating points). For GBR QoS
Flows using the Delay-critical resource type, a packet delayed more than PDB is counted as lost if the data
burst is not exceeding the MDBV within the period of PDB and the QoS Flow is not exceeding the GFBR. For
GBR QoS Flows with GBR resource type not exceeding GFBR, 98 percent of the packets shall not experience a
delay exceeding the 5QI's PDB.
The delay budget that applies to the radio interface is determined by subtracting a static value for the Core
Network Packet Delay Budget (CN PDB), which represents the delay between any UPF terminating N6 (that
may possibly be selected for the PDU Session) and the 5G-AN from a given PDB.
NOTE 1: For a standardized 5QI, the static value for the CN PDB is specified in the QoS characteristics Table
5.7.4-1.
NOTE 2: For a non-standardized 5QI, the static value for the CN PDB is homogeneously configured in the
network.
For GBR QoS Flows using the Delay-critical resource type, in order to obtain a more accurate delay budget
PDB available for the NG-RAN, a dynamic value for the CN PDB, which represents the delay between the UPF
terminating N6 for the QoS Flow and the 5G-AN, can be used. If used for a QoS Flow, the NG-RAN shall apply
the dynamic value for the CN PDB instead of the static value for the CN PDB (which is only related to the
5QI).
The dynamic value for the CN PDB of a Delay-critical GBR 5QI may be configured in the network in two ways:

 Configured in each NG-RAN node, based on a variety of inputs such as different IP address(es) or
TEID range of UPF terminating the N3 tunnel and based on different combinations of PSA UPF to NG-
RAN under consideration of any potential I-UPF, etc;
 Configured in the SMF, based on different combinations of PSA UPF to NG-RAN under consideration
of any potential I-UPF. The dynamic value for the CN PDB for a particular QoS Flow shall be signalled
to NG-RAN (during PDU Session Establishment, PDU Session Modification, Xn/N2 handover and the
Service Request procedures) when the QoS Flow is established or the dynamic value for the CN PDB
of a QoS Flow changes, e.g. when an I-UPF is inserted by the SMF.

If the NG-RAN node is configured locally with a dynamic value for the CN PDB for a Delay-critical GBR 5QI,
and receives a different value via N2 signalling for a QoS Flow with the same 5QI, local configuration in RAN
node determines which value takes precedence.
Services using a GBR QoS Flow and sending at a rate smaller than or equal to the GFBR can in general assume
that congestion related packet drops will not occur.
NOTE: Exceptions (e.g. transient link outages) can always occur in a radio access system which may then lead
to congestion related packet drops. Packets surviving congestion related packet dropping may still be subject
to non-congestion related packet losses (see PER below).
Services using Non-GBR QoS Flows should be prepared to experience congestion-related packet drops and
delays. In uncongested scenarios, 98 percent of the packets should not experience a delay exceeding the 5QI's
PDB.
The PDB for Non-GBR and GBR resource types denotes a "soft upper bound" in the sense that an "expired"
packet, e.g. a link layer SDU that has exceeded the PDB, does not need to be discarded and is not added to
the PER. However, for a Delay critical GBR resource type, packets delayed more than the PDB are added to
the PER and can be discarded or delivered depending on local decision.
[Link]  Packet Error Rate  Word-p. 137
The Packet Error Rate (PER) defines an upper bound for the rate of PDUs (e.g. IP packets) that have been
processed by the sender of a link layer protocol (e.g. RLC in RAN of a 3GPP access) but that are not
successfully delivered by the corresponding receiver to the upper layer (e.g. PDCP in RAN of a 3GPP access).
Thus, the PER defines an upper bound for a rate of non-congestion related packet losses. The purpose of the
PER is to allow for appropriate link layer protocol configurations (e.g. RLC and HARQ in RAN of a 3GPP
access). For every 5QI the value of the PER is the same in UL and DL. For GBR QoS Flows with Delay critical
GBR resource type, a packet which is delayed more than PDB is counted as lost, and included in the PER
unless the data burst is exceeding the MDBV within the period of PDB or the QoS Flow is exceeding the GFBR.
[Link]  Averaging Window
Each GBR QoS Flow shall be associated with an Averaging window. The Averaging window represents the
duration over which the GFBR and MFBR shall be calculated (e.g. in the (R)AN, UPF, UE).
Every standardized 5QI (of GBR and Delay-critical GBR resource type) is associated with a default value for
the Averaging window (specified in QoS characteristics Table [Link]). The averaging window may also be
signalled together with a standardized 5QI to the (R)AN and UPF, and if it is received, it shall be used instead
of the default value.
The Averaging window may also be signalled together with a pre-configured 5QI to the (R)AN, and if it is
received, it shall be used instead of the pre-configured value.
[Link]  Maximum Data Burst Volume
Each GBR QoS Flow with Delay-critical resource type shall be associated with a Maximum Data Burst Volume
(MDBV).
MDBV denotes the largest amount of data that the 5G-AN is required to serve within a period of 5G-AN PDB
(i.e. 5G-AN part of the PDB).
Every standardized 5QI (of Delay-critical GBR resource type) is associated with a default value for the MDBV
(specified in QoS characteristics Table [Link]). The MDBV may also be signalled together with a standardized
5QI to the (R)AN, and if it is received, it shall be used instead of the default value.
The MDBV may also be signalled together with a pre-configured 5QI to the (R)AN, and if it is received, it shall
be used instead of the pre-configured value.
5.7.4  Standardized 5QI to QoS characteristics mapping
Packet Delay Budget (Note 3)
Default Maximum Data Burst Volume (Note 2)

GBR Resource Type (Note 1)

5QI Value  1

Default Priority Level 20

Packet Delay Budget 100 ms (Note 11, Note 13)

Packet Error Rate 10-2

Default Maximum Data Burst Volume N/A

Default Averaging Window 2000 ms

Example Services Conversational Voice

5QI Value  2
Default Priority Level 40
Packet Delay Budget 150 ms (Note 11, Note 13)
Packet Error Rate 10-3
Default Maximum Data Burst Volume N/A
Default Averaging Window 2000 ms
Example Services Conversational Video (Live Streaming)

5QI Value  3 (Note 14)

Default Priority Level 30
Packet Delay Budget 50 ms (Note 11, Note 13)
Packet Error Rate 10-3
Default Maximum Data Burst Volume N/A
Default Averaging Window 2000 ms
Example Services Real Time Gaming, V2X messages Electricity distribution - medium voltage, Process
automation - monitoring

5QI Value  4
Default Priority Level 50
Packet Delay Budget 300 ms (Note 11, Note 13)
Packet Error Rate 10-6
Default Maximum Data Burst Volume N/A
Default Averaging Window 2000 ms
Example Services Non-Conversational Video (Buffered Streaming)

5QI Value  65 (Note 9, Note 12)

Default Priority Level 7
Packet Delay Budget 75 ms (Note 7, Note 8)
Packet Error Rate 10-2
Default Maximum Data Burst Volume N/A
Default Averaging Window 2000 ms
Example Services Mission Critical user plane Push To Talk voice (e.g., MCPTT)

5QI Value  66 (Note 12)

Default Priority Level 20
Packet Delay Budget 100 ms (Note 10, Note 13)
Packet Error Rate 10-2
Default Maximum Data Burst Volume N/A
Default Averaging Window 2000 ms
Example Services Non-Mission-Critical user plane Push To Talk voice

5QI Value  67 (Note 12)

Default Priority Level 15
Packet Delay Budget 100 ms (Note 11, Note 13)
Packet Error Rate 10-3
Default Maximum Data Burst Volume N/A
Default Averaging Window 2000 ms
Example Services Mission Critical Video user plane

5QI Value  71
Default Priority Level 56
Packet Delay Budget 150 ms (Note 11, Note 13, Note 15)
Packet Error Rate 10-6
Default Maximum Data Burst Volume N/A
Default Averaging Window 2000 ms
Example Services "Live" Uplink Streaming (e.g. TS 26.238)

5QI Value  72
Default Priority Level 56
Packet Delay Budget 300 ms (Note 11, Note 13, Note 15)
Packet Error Rate 10-4
Default Maximum Data Burst Volume N/A
Default Averaging Window 2000 ms
Example Services "Live" Uplink Streaming (e.g. TS 26.238)

5QI Value  73
Default Priority Level 56
Packet Delay Budget 300 ms (Note 11, Note 13, Note 15)
Packet Error Rate 10-8
Default Maximum Data Burst Volume N/A
Default Averaging Window 2000 ms
Example Services "Live" Uplink Streaming (e.g. TS 26.238)

5QI Value  74
Default Priority Level 56
Packet Delay Budget 500 ms (Note 11, Note 15)
Packet Error Rate 10-8
Default Maximum Data Burst Volume N/A
Default Averaging Window 2000 ms
Example Services "Live" Uplink Streaming (e.g. TS 26.238)

5QI Value  76
Default Priority Level 56
Packet Delay Budget 500 ms (Note 11, Note 13, Note 15)
Packet Error Rate 10-4
Default Maximum Data Burst Volume N/A
Default Averaging Window 2000 ms
Example Services "Live" Uplink Streaming (e.g. TS 26.238)

Non-GBR Resource Type (Note 1)

5QI Value  5

Default Priority Level 10

Packet Delay Budget 100 ms (Note 10, Note 13)

Packet Error Rate 10-6

Default Maximum Data Burst Volume N/A

Default Averaging Window N/A

Example Services IMS Signalling

5QI Value  6

Default Priority Level 60

Packet Delay Budget 300 ms (Note 10, Note 13)

Packet Error Rate 10-6

Default Maximum Data Burst Volume N/A

Default Averaging Window N/A

Example Services Video (Buffered Streaming) TCP-based (e.g., www, e-mail, chat, ftp, p2p file sharing,
progressive video, etc.)

5QI Value  7

Default Priority Level 70

Packet Delay Budget 100 ms (Note 10, Note 13)

Packet Error Rate 10-3

Default Maximum Data Burst Volume N/A

Default Averaging Window N/A

Example Services Voice, Video (Live Streaming) Interactive Gaming

5QI Value  8

Default Priority Level 80

Packet Delay Budget 300 ms (Note 13)

Packet Error Rate 10-6

Default Maximum Data Burst Volume N/A

Default Averaging Window N/A

Example Services Video (Buffered Streaming) TCP-based (e.g., www, e-mail, chat, ftp, p2p file sharing,
progressive video, etc.)

5QI Value  9

Default Priority Level 90

Packet Delay Budget 300 ms (Note 13)

Packet Error Rate 10-6

Default Maximum Data Burst Volume N/A

Default Averaging Window N/A

Example Services Video (Buffered Streaming) TCP-based (e.g., www, e-mail, chat, ftp, p2p file sharing,
progressive video, etc.)

5QI Value  69 (Note 9, Note 12)

Default Priority Level 5

Packet Delay Budget 60 ms (Note 7, Note 8)

Packet Error Rate 10-6

Default Maximum Data Burst Volume N/A

Default Averaging Window N/A

Example Services Mission Critical delay sensitive signalling (e.g., MC-PTT signalling)

5QI Value  70 (Note 12)

Default Priority Level 55

Packet Delay Budget 200 ms (Note 7, Note 10)

Packet Error Rate 10-6

Default Maximum Data Burst Volume N/A

Default Averaging Window N/A

Example Services Mission Critical Data (e.g. example services are the same as 5QI 6/8/9)

5QI Value  79

Default Priority Level 65

Packet Delay Budget 50 ms (Note 10, Note 13)

Packet Error Rate 10-2

Default Maximum Data Burst Volume N/A

Default Averaging Window N/A

Example Services V2X messages

5QI Value  80

Default Priority Level 68

Packet Delay Budget 10 ms (Note 5, Note 10)

Packet Error Rate 10-2

Default Maximum Data Burst Volume N/A

Default Averaging Window N/A

Example Services Low Latency eMBB applications Augmented Reality

Delay Critical GBR Resource Type

5QI Value  82

Default Priority Level 19

Packet Delay Budget 10 ms (Note 4)

Packet Error Rate 10-4

Default Maximum Data Burst Volume 255 bytes

Default Averaging Window 2000 ms

Example Services Discrete Automation (see TS 22.261)

5QI Value  83

Default Priority Level 22

Packet Delay Budget 10 ms (Note 4)

Packet Error Rate 10-4

Default Maximum Data Burst Volume 1354 bytes

Default Averaging Window 2000 ms

Example Services Discrete Automation (see TS 22.261); V2X messages (UE - RSU Platooning, Advanced
Driving: Cooperative Lane Change with low LoA. See TS 22.186)

5QI Value  84

Default Priority Level 24

Packet Delay Budget 30 ms (Note 6)

Packet Error Rate 10-5

Default Maximum Data Burst Volume 1354 bytes

Default Averaging Window 2000 ms

Example Services Intelligent transport systems (see TS 22.261)

5QI Value  85

Default Priority Level 21

Packet Delay Budget 5 ms (Note 5)

Packet Error Rate 10-5

Default Maximum Data Burst Volume 255 bytes

Default Averaging Window 2000 ms

Example Services Electricity Distribution- high voltage (see TS 22.261). V2X messages (Remote Driving.
See TS 22.186, NOTE 16)

5QI Value  86

Default Priority Level 18

Packet Delay Budget 5 ms (Note 5)

Packet Error Rate 10-4

Default Maximum Data Burst Volume 1354 bytes

Default Averaging Window 2000 ms

Example Services V2X messages (Advanced Driving: Collision Avoidance, Platooning with high LoA.
See TS 22.186)
Note 1: A packet which is delayed more than PDB is not counted as lost, thus not included in the PER.

Note 2: It is required that default MDBV is supported by a PLMN supporting the related 5QIs.

Note 3: The Maximum Transfer Unit (MTU) size considerations in clause 9.3 and Annex C of TS 23.060 are also
applicable. IP fragmentation may have impacts to CN PDB, and details are provided in clause 5.6.10.

Note 4: A static value for the CN PDB of 1 ms for the delay between a UPF terminating N6 and a 5G-AN should
be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. When a
dynamic CN PDB is used, see clause [Link].

Note 5: A static value for the CN PDB of 2 ms for the delay between a UPF terminating N6 and a 5G-AN should
be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. When a
dynamic CN PDB is used, see clause clause [Link].

Note 6: A static value for the CN PDB of 5 ms for the delay between a UPF terminating N6 and a 5G-AN should
be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. When a
dynamic CN PDB is used, see clause clause [Link].

Note 7: For Mission Critical services, it may be assumed that the UPF terminating N6 is located "close" to the
5G_AN (roughly 10 ms) and is not normally used in a long distance, home routed roaming situation. Hence a
static value for the CN PDBof 10 ms for the delay between a UPF terminating N6 and a 5G_AN should be
subtracted from this PDB to derive the packet delay budget that applies to the radio interface.

Note 8: In both RRC Idle and RRC Connected mode, the PDB requirement for these 5QIs can be relaxed (but
not to a value greater than 320 ms) for the first packet(s) in a downlink data or signalling burst in order to
permit reasonable battery saving (DRX) techniques.

Note 9: It is expected that 5QI-65 and 5QI-69 are used together to provide Mission Critical Push to Talk
service (e.g., 5QI-5 is not used for signalling). It is expected that the amount of traffic per UE will be similar
or less compared to the IMS signalling.

Note 10: In both RRC Idle and RRC Connected mode, the PDB requirement for these 5QIs can be relaxed for
the first packet(s) in a downlink data or signalling burst in order to permit battery saving (DRX) techniques.

Note 11: In RRC Idle mode, the PDB requirement for these 5QIs can be relaxed for the first packet(s) in a
downlink data or signalling burst in order to permit battery saving (DRX) techniques.

Note 12: This 5QI value can only be assigned upon request from the network side. The UE and any application
running on the UE is not allowed to request this 5QI value.

Note 13: A static value for the CN PDB of 20 ms for the delay between a UPF terminating N6 and a 5G-AN
should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface.
Note 14: This 5QI is not supported in this Release of the specification as it is only used for transmission of
V2X messages over MBMS bearers as defined in TS 23.285 but the value is reserved for future use.

Note 15: For "live" uplink streaming (see TS 26.238), guidelines for PDB values of the different 5QIs
correspond to the latency configurations defined in TR 26.939. In order to support higher latency reliable
streaming services (above 500ms PDB), if different PDB and PER combinations are needed these configurations
will have to use non-standardised 5QIs.

Note 16: These services are expected to need much larger MDBV values to be signalled to the RAN. Support
for such larger MDBV values with low latency and high reliability is likely to require a suitable RAN
configuration, for which, the simulation scenarios in TR 38.824 may contain some guidance.

Evolution of the QoS Classes in 5G by Charlie

Martin

Published on: 11/25/2019

Author: Charlie Martin, Senior Consultant, Award Solutions

As 3GPP continues the standardization process for 5G, it is now well

understood that 5G Quality of Service (QoS) will be applied purely on a
per-Quality of Service Flow (QoS Flow) basis versus the previous per-
Evolved Packet Service (EPS) bearer basis in 4G LTE. It is important to
remember that the QoS Class Identifier (QCI), Allocation and Retention
Priority (ARP), Guaranteed Bit Rate (GBR), Maximum Bit Rate (MBR),
and Aggregate Maximum Bit Rate (AMBR) parameters were the five
primary QoS parameters that could be determined for the EPS bearer. The
operator specifies those parameters using the guidelines in the 3GPP and
GSMA documents and specifications, as well as their own field
experience. History shows us that this QoS implementation strategy
devised by 3GPP has been very successful in the LTE networks built over
the last seven to eight years, with a multitude of different types of services
rolled out requiring GBR, or non-GBR QoS, with a wide range of latency
requirements, i.e., VoLTE. Here, we will examine what is happening with
the evolution of the QCI parameter as the industry moves forward towards
5G.

First, let’s go back and review the 3GPP definition of QCI and its
characteristics. From the 3GPP Technical Specification TS23.203, Policy
and Charging Control Architecture (Release 15), the following list of
performance characteristics were defined for all QCIs.

 Resource Type (GBR or non-GBR)

 Priority Level (PL)
 Packet Delay Budget (PDB)
 Packet Error Loss Rate (PELR)

In addition, two more performance characteristics have been defined for

some QCIs.

 Maxium Burst Size

 Data Rate Averaging Window

The QCI was defined to be a scalar value that is used as a reference by the
eNodeB for the scheduling of the packets for that EPS Bearer, and each of
the characteristics supplies information to the eNodeB to help it properly
do that scheduling.

For ease of viewing, two separate tables are shown below by resource
type, with Table 1 depicting GBR example services and Table 2 depicting
non-GBR example services, both of these tables being derived from Table
6.1.7-A of TS23.203. Note that these tables are simplified for the sake of
clarity and brevity and do not contain the complete set of associated notes
from the specification.

These tables show the QCIs and associated example services, along with
the first four QoS performance characteristics.

Listed below is a quick review of the four characteristics.

The resource type is self-explanatory and essentially divides the QCI types
into two categories - QCIs for services requiring Guaranteed Bit Rate
treatment or QCIs for services requiring Non-Guaranteed Bit Rate
treatment.

The Priority Level column refers to the priority for the packets to be
scheduled, with the lower priority numbers corresponding to the higher
priority level.

The Packet Delay Budget column provides an upper bound for the
tolerable packet delay in milliseconds between the User Equipment (UE)
and the Policy and Charging Enforcement Function (PCEF), which is
typically co-located with the Packet Data Network (PDN) Gateway or P-
GW.

The Packet Error Loss Rate (PELR) column defines an upper bound for
the tolerable loss of Service Data Units (SDUs), or in simplified speech,
the payload portion of packets over the airlink between the eNodeB and
the UE. According to TS 23.203 Policy and Charging Control
Architecture, these are “SDUs that have been processed by the sender of a
link layer protocol (e.g., RLC in E-UTRAN), but that are not successfully
delivered by the corresponding receiver to the upper layer (e.g., PDCP in
E-UTRAN).” In simplified terms, these are non-congestion-related packet
losses intended to capture the failure of the airlink and its lower layer
retransmission protocols, Radio Link Control (RLC) and Hybrid
Automatic Repeat Request (HARQ), to successfully deliver transmitted
packets from the transmitting end of the airlink to the receiver. 
Table 1 (GBR-based Services)
 

Table 2 (Non-GBR-based Services)

In addition, Table 3 below depicts additional GBR example services, along
with the extra fifth and sixth performance characteristics. This table is
derived from Table 6.1.7-B of TS23.203, and the newer characteristics are
listed below.

The maximum burst size is the amount of data that the radio access
network is expected to deliver within the packet delay budget.

The data rate averaging window refers to a sliding time window (or
duration) that is used for calculating GBR and MBR values in the RAN,
PDN-GW, and UE

Table 3 (Additional GBR-based Services)

At this point, there are several important takeaways that need to be

summarized before proceeding to look at the corresponding 5G
information. First, there has been a huge growth in the number of QCIs
and example services supported for 4G LTE, since the initial release of
this specification (Release 8). 3GPP has not been waiting for 5G to handle
the next generation of advanced services, and the present state of the QCI
parameter shows support for:

 Smart Grid (both medium and high voltage)

  Process Automation Monitoring
 Autonomous Vehicles (V2X messaging)
 Mission-critical Public Safety applications
 Low-latency enhanced Mobile Broadband (eMBB)
 Augmented Reality
 Discrete Automation
 Intelligent Transport Systems

It is interesting to look over the variance in the values of the performance

characteristics for the next generation advanced services. Of particular
interest are the QCI values from 80 – 85, all of which have packet delay
budgets of 30 milliseconds or less (remember that this delay budget is
from UE to PCEF/P-GW). Also, the next generation services supported by
QCIs 82 – 85 require the additional information provided by the maximum
burst size and data rate averaging window for aiding the eNodeB scheduler
to provide satisfactory service.

To understand the 5G equivalent of the QCI parameter, 3GPP Technical

Specification TS23.501, System Architecture for the 5G System, provides
the relevant information. From section [Link], the 5G QoS Identifier (5QI)
parameter is defined, and again, it is defined to be a scalar value that is
used as a reference by the eNodeB for the QoS forwarding treatment. The
5QI is equivalent to the QCI in 4G LTE. Tables 4 and 5 below show the
5QI table 5.7.4-1 in the 3GPP specification, as broken out by GBR and
non-GBR example services again. In addition, Table 5.7.4-1 of the
specification now breaks out a new category of 5QI, called Delay-Critical
GBR, and the associated 5QIs are shown in Table 6 below.
Table 4 (GBR-based Services)
 

Table 5 (Non-GBR-based Services)

 
Table 6 (Delay-critical GBR-based Services)

After looking at Tables 4, 5 and 6, it can be seen that there is a lot of

commonality between the 4G QCI and the 5G 5QI tables, and the 5QI
tables are clearly a direct evolution of the QCI tables. From TS23.501,
Section 5.7.3, 5G QoS characteristics, a high-level summary of the 5G
performance characteristics is provided below, along with contrasting
information versus the associated 4G characteristic.

The resource type is again mostly self-explanatory and shows some

refinement versus the 4G definition. The QCI types are now divided into
three categories - QCIs for services requiring GBR treatment, QCIs for
services requiring Delay-Critical GBR treatment, or QCIs for services
requiring Non-GBR treatment. This new Delay-Critical GBR resource
type can be seen as an evolution of the additional GBR services that were
called out in Table 3 above for 4G.

The Default Priority Level column evolves directly from the Priority Level
column shown in Tables 1 – 3 for 4G. When examining the definitions
from TS 23.501 for the 5G Default Priority Level versus TS 23.203 for the
4G Priority Level, the emphasis is on the default priority level being used
as a differentiator for QoS treatment for individual QoS flows, whereas for
4G, the emphasis is on the priority level being used as a differentiator for
QoS treatment for aggregations of Service Data Flows (SDFs). Again,
lower priority numbers correspond to the higher priority level.

The Packet Delay Budget column evolves directly from the column of the
exact same name shown in Tables 1 – 3 for 4G. This performance
characteristic provides an upper bound for the tolerable packet delay in
milliseconds between the User Equipment (UE) and the new 5G Virtual
Network Function called the User Plane Function (UPF). Therefore, this
characteristic provides almost exactly the same functionality as its 4G
equivalent. The UPF is equivalent to the user plane – packet routing –
functions of the 4G S-GW and P-GW. 

The Packet Error Rate (PER) evolves directly from the column called
Packet Error Loss Rate (PELR) in Tables 1 – 3 for 4G. The intent and
usage of PER is very similar to PELR. However, the wording has slightly
changed. Instead of referring to SDUs, TS 25.301 refers to Protocol Data
Units (PDUs). A PDU consists of an SDU with an attached header. It can
be interpreted that the newer spec refers to an entire packet, instead of the
payload (SDU) of the packet that is referred to in the 4G definition of
PELR. Again, in simplified terms, these are non-congestion-related packet
losses, intended to capture the failure of the air link and its lower layer
retransmission protocols, to successfully deliver transmitted packets from
the transmitting end of the air link to the receiver.

The Default Data Maximum Data Burst Volume (MDBV) evolves directly
from the column in Table 3 called Maximum Burst Size. In 5G, each
delay-sensitive GBR QoS flow will be associated with an MDBV. Table 3
shows a portion of the overall 4G QCI table in TS 23.203, where 3GPP
was clearly beginning to group and emphasize the most delay-sensitive
GBR applications being considered by cellular network operators, and the
4G maximum burst size was a newer performance characteristic. The
definitions are essentially the same for both the 4G maximum burst size
and 5G data maximum data burst volume, with the 4G eNB or the 5G
Access Node (5G-AN) being required to deliver up to this maximum
amount of data within the packet delay budget. Note that for the GBR and
non-GBR 5QIs, the default MDBV is not applicable and has no value.

The default averaging window evolves directly from the Data Rate
Averaging Window column in Table 3. The definition is exactly the same
for both 4G and 5G performance characteristics. In other words, it defines
the sliding time window (or duration) that is used for calculating GBR and
MBR values in the RAN, UPF, and UE.

As seen from the QoS performance characteristics definitions alone, a

direct evolution from 4G QCI to 5G 5QI is very clear. Other major
takeaways include the fact that Table 4 is essentially a direct translation of
Table 1, with identical values being used for 5QI, default priority level,
packet delay budget, packet error rate, and example services entries versus
the 4G equivalents. The same is true when comparing Table 5 to Table 2.
Default Maximum Data Burst Volume and Default Averaging Window
have now been added as standard columns for Tables 4 and 5. However,
MDBV is N/A in both tables, and Default Averaging Window is N/A for
Non-GBR services and is set to a single value of 2000 ms for all GBR
services. The 5QI values are created simply by multiplying each QCI
value in Tables 1 and 2 by a factor of 10, creating exactly the new double-
digit 5QI values, which is simple, elegant, and greatly expands the range
of possible values for the future.

The last major takeaway involves the comparison of Table 6 versus Table
3. Table 3 for 4G had already started the double-digit values for QCI, and
the values of 82 – 85 translate directly over to the 5G Table 6. A new
remote-control service, 5QI of 81, has been created in Table 6, with no
equivalent in Table 3, and the high-voltage electricity distribution service,
4G QCI of 85, has been replaced (thus far) with the Discrete Automation
5G 5QI of 85. Beyond this, there has been some juggling of the services
and associated values for some of the additional Table 6 values.

3GPP looks to be doing a very complete job of transitioning the network

end-to-end QoS scheme from 4G to 5G, as reflected in the evolution of the
4G QCI to the 5G 5QI QoS parameter.

References:
3GPP Technical Specification TS23.203, Policy and Charging Control
Architecture
3GPP Technical Specification TS23.501, System Architecture for the 5G
System

About the Author:

Charlie joined Award Solutions in 2011 and has over 36 years of

experience in wireless. He is a true RF nut, and in his early career enjoyed
chasing down electromagnetic interference problems, doing system level
testing and analysis, and designing/building microwave transmitters.
Having led enterprise-level organizations at both network operators and
vendors, Charlie brings a unique perspective to wireless and has been a
featured speaker at leading mobility conferences. Charlie now pursues his
passion for all things wireless at Award Solutions as the Radio Access
Networks (RAN) Product Lead, researching new technologies and
teaching others about next generation networks like 5G.

About Award Solutions:

Award Solutions is the trusted training partner to the world's best

networks. We help companies tackle new technologies by equipping their
teams with knowledge and skills. Award Solutions invests heavily in
technology, research, engineering, and labs to ensure our customers make
the most of their resource and network investments.

Award has expertise and training across all technologies that touch
wireless: 5G, Artificial Intelligence, Data Manipulation, Automation,
Machine Learning, Network Virtualization, Data Visualization, 4G LTE,
and more.