1

GBR

(NOTE 1)

20

100 ms

(NOTE 11,

NOTE 12)

10^-2

N/A

2000 ms

Conversational Voice

2

40

150 ms

(NOTE 11,

NOTE 13)

10^-3

N/A

2000 ms

Conversational Video (Live Streaming)

3

30

50 ms

(NOTE 11,

NOTE 13)

10^-3

N/A

2000 ms

Real Time Gaming, V2X messages (see TS 23.287). Electricity distribution medium voltage, Process automation monitoring

4

50

300 ms

(NOTE 11,

NOTE 13)

10^-6

N/A

2000 ms

Non-Conversational Video (Buffered Streaming)

65

(NOTE 9,

NOTE 12)

7

75 ms

(NOTE 7,

NOTE 8)

10^-2

N/A

2000 ms

Mission Critical user plane Push To Talk voice (e.g., MCPTT)

66

(NOTE 12)

20

100 ms

(NOTE 10,

NOTE 13)

10^-2

N/A

2000 ms

Non-Mission-Critical user plane Push To Talk voice

67

(NOTE 12)

15

100 ms

(NOTE 10,

NOTE 13)

10^-3

N/A

2000 ms

Mission Critical Video user plane

75

(NOTE 14)

N/A

N/A

N/A

N/A

N/A

N/A

71

56

150 ms

(NOTE 11,

NOTE 13,

NOTE 15)

10^-6

N/A

2000 ms

"Live" Uplink Streaming (e.g. TS 26.238)

72

56

300 ms

(NOTE 11,

NOTE 13,

NOTE 15)

10^-4

N/A

2000 ms

"Live" Uplink Streaming (e.g. TS 26.238)

73

56

300 ms

(NOTE 11,

NOTE 13,

NOTE 15)

10^-8

N/A

2000 ms

"Live" Uplink Streaming (e.g. TS 26.238)

74

56

500 ms

(NOTE 11,

NOTE 15)

10^-8

N/A

2000 ms

"Live" Uplink Streaming (e.g. TS 26.238)

76

56

500 ms

(NOTE 11,

NOTE 13,

NOTE 15)

10^-4

N/A

2000 ms

"Live" Uplink Streaming (e.g. TS 26.238)

5

non-GBR

(NOTE 1)

10

100 ms

(NOTE 10,

NOTE 13)

10^-6

N/A

N/A

IMS Signalling

6

(NOTE 1)

60

300 ms

(NOTE 10,

NOTE 13)

10^-6

N/A

N/A

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

7

70

100 ms

(NOTE 10,

NOTE 13)

10^-3

N/A

N/A

Voice, Video (Live Streaming) Interactive Gaming

8

80

300 ms

(NOTE 13)

10^-6

N/A

N/A

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

9

90

300 ms

(NOTE 13)

10^-6

N/A

N/A

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

69

(NOTE 9,

NOTE 12)

5

60 ms

(NOTE 7,

NOTE 8)

10^-6

N/A

N/A

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

70

(NOTE 12)

55

200 ms

(NOTE 7,

NOTE 10)

10^-6

N/A

N/A

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

79

65

50 ms (NOTE 10, NOTE 13)

10^-2

N/A

N/A

V2X messages (see TS 23.287)

80

68

10 ms

(NOTE 5,

NOTE 10)

10^-6

N/A

N/A

Low Latency eMBB applications Augmented Reality

82

Delay critical

GBR

19

10 ms

(NOTE 4)

10^-4

255 bytes

2000 ms

Discrete Automation (see TS 22.261)

83

22

10 ms

(NOTE 4)

10^-4

1354 bytes

(NOTE 3)

2000 ms

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

84

24

30 ms

(NOTE 6)

10^-5

1354 bytes

(NOTE 3)

2000 ms

Intelligent transport systems (see TS 22.261)

85

21

5 ms

(NOTE 5)

10^-5

255 bytes

2000 ms

Electricity Distribution-high voltage (see TS 22.261); V2X messages (Remote Driving. See TS 22.186, NOTE 18, see TS 22.261)

86

18

5 ms

(NOTE 5)

10^-4

1354 bytes

2000 ms

V2X messages (Advanced Driving: Collision Avoidance, Platooning with high LoA. See TS 22.186, TS 23.287)

87

25

5 ms

(NOTE 4)

10^-3

500 bytes

2000 ms

Interactive Service - Motion tracking data, (see TS 22.261)

88

25

10 ms

(NOTE 4)

10^-3

1125 bytes

2000 ms

Interactive Service - Motion tracking data, (see TS 22.261)

89

25

15 ms

(NOTE 4)

10^-4

17000 bytes

2000 ms

Visual content for cloud/edge/split rendering (see TS 22.261)

90

25

20 ms

(NOTE 4)

10^-4

63000 bytes

2000 ms

Visual content for cloud/edge/split rendering (see TS 22.261)

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 [56] 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 5.7.3.4.

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 5.7.3.4.

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 5.7.3.4.

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 PDB of 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 [72] but the value is reserved for future use.

NOTE 15: For "live" uplink streaming (see TS 26.238 [76]), guidelines for PDB values of the different 5QIs correspond to

the latency configurations defined in TR 26.939 [77]. 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 [112] may contain some guidance.

NOTE 17: The worst case one way propagation delay for GEO satellite is expected to be ~270ms, ,~ 21 ms for LEO at

1200km, and 13 ms for LEO at 600km. The UL scheduling delay that needs to be added is also typically two

way propagation delay e.g. ~540ms for GEO, ~42ms for LEO at 1200km, and ~26 ms for LEO at 600km.

Based on that, the 5G-AN Packet delay budget is not applicable for 5QIs that require 5G-AN PDB lower than

the sum of these values when the specific types of satellite access are used (see TS 38.300 [27]). 5QI-10 can

accommodate the worst case PDB for GEO satellite type.