Standardized 5G QoS Identifier (5QI) values are specified for services that are assumed to be frequently used in 5G networks and thus benefit from optimized signalling by using standardized QoS characteristics. Dynamically assigned 5QI values which require a signalling of QoS characteristics as part of the QoS profile can be used for services for which standardized 5QI values are not defined. The one-to-one mapping of standardized 5QI values to 5G QoS characteristics is specified in following table
| 5QI Value | Resource Type | Default Priority Level | Packet Delay Budget | Packet Error Rate | Default Maximum Data Burst Volume (NOTE 2) | Default Averaging Window | Example Services |
|---|---|---|---|---|---|---|---|
| 1 | GBR (NOTE 1) | 20 | 100 ms (NOTE 11,NOTE 13) | 10-2 | N/A | 2000 ms | Conversational Voice |
| 2 | GBR (NOTE 1) | 40 | 150 ms (NOTE 11, NOTE 13) |
10-3 | N/A | 2000 ms | Conversational Video (Live Streaming) |
|
3 (NOTE 14) |
GBR (NOTE 1) | 30 | 50 ms (NOTE 11, NOTE 13) | 10-3 | N/A | 2000 ms | Real Time Gaming, V2X messages Electricity distribution – medium voltage, Process automation – monitoring |
| 4 | GBR (NOTE 1) | 50 | 300 ms (NOTE 11, NOTE 13) | 10-6 | N/A | 2000 ms | Non-Conversational Video (Buffered Streaming) |
|
65 (NOTE 9,NOTE 12) |
GBR (NOTE 1) | 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) |
GBR (NOTE 1) | 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) |
GBR (NOTE 1) | 15 | 100 ms (NOTE 10, NOTE 13) | 10-3 | N/A | 2000 ms | Mission Critical Video user plane |
|
75 (NOTE 14) |
GBR (NOTE 1) | ||||||
| 71 | GBR (NOTE 1) | 56 | 150 ms (NOTE 11, NOTE 13, NOTE 15) | 10-6 | N/A | 2000 ms | “Live” Uplink Streaming |
| 72 | GBR (NOTE 1) | 56 | 300 ms (NOTE 11, NOTE 13, NOTE 15) | 10-4 | N/A | 2000 ms | “Live” Uplink Streaming |
| 73 | GBR (NOTE 1) | 56 | 300 ms (NOTE 11, NOTE 13, NOTE 15) | 10-8 | N/A | 2000 ms | “Live” Uplink Streaming |
| 74 | GBR (NOTE 1) | 56 | 500 ms (NOTE 11, NOTE 15) | 10-8 | N/A | 2000 ms | “Live” Uplink Streaming |
| 76 | GBR (NOTE 1) | 56 | 500 ms (NOTE 11, NOTE 13, NOTE 15) | 10-4 | N/A | 2000 ms | “Live” Uplink Streaming |
| 5 | Non-GBR (NOTE 1) | 10 | 100 ms NOTE 10, NOTE 13) | 10-6 | N/A | N/A | IMS Signalling |
| 6 | Non-GBR (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 | Non-GBR (NOTE 1) | 70 | 100 ms(NOTE 10, NOTE 13) | 10-3 | N/A | N/A | Voice,Video (Live Streaming) Interactive Gaming |
| 8 | Non-GBR (NOTE 1) | 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 | Non-GBR (NOTE 1) | 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) |
Non-GBR (NOTE 1) | 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) |
Non-GBR (NOTE 1) | 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 | Non-GBR (NOTE 1) | 65 | 50 ms (NOTE 10, NOTE 13) |
10-2 | N/A | N/A | V2X messages |
| 80 | Non-GBR (NOTE 1) | 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 |
| 83 | Delay Critical GBR | 22 | 10 ms (NOTE 4) | 10-4 | 1354 bytes (NOTE 3) | 2000 ms | Discrete Automation |
| 84 | Delay Critical GBR | 24 | 30 ms (NOTE 6) | 10-5 | 1354 bytes (NOTE 3) | 2000 ms | Intelligent transport systems |
| 85 | Delay Critical GBR | 21 | 5 ms (NOTE 5) |
10-5 | 255 bytes | 2000 ms | Electricity Distribution- high voltage |
- 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: This MDBV value is set to 1354 bytes to avoid IP fragmentation for the IPv6 based, IPSec protected GTP tunnel to the 5G-AN node (the value is calculated as in Annex C of TS 23.060 [56] and further reduced by 4 bytes to allow for the usage of a GTP-U extension header).
- 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 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 [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.
Related Posts: