Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.501  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   3…   4.2.3   4.2.4   4.2.5…   4.2.8…   4.2.8.2.2   4.2.8.2.3…   4.2.8.4…   4.2.9…   4.3…   4.3.3   4.3.4   4.3.5   4.4…   4.4.6…   4.4.8   5…   5.3…   5.3.3…   5.4…   5.5…   5.6…   5.6.7…   5.7…   5.7.2…   5.7.3…   5.7.4   5.7.5…   5.8…   5.8.2.11…   5.9…   5.10…   5.11…   5.15…   5.16…   5.17…   5.18…   5.19…   5.21…   5.22…   5.27…   5.28…   5.29…   5.30…   5.31…   5.32…   5.33…   5.34…   5.35…   6…   6.3…   7…   7.2…   8…   8.2.4   8.2.5…   8.3…   A…   D…   E…   F   G…   G.3   G.4…   J…

 

5.7.4  Standardized 5QI to QoS characteristics mappingp. 166

Standardized 5QI values are specified for services that are assumed to be frequently used 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 Table 5.7.4-1.
5QI Value Resource Type Default Priority Level Packet Delay Budget (3) Packet Error Rate Default Maximum Data Burst Volume (2) Default Averaging Window Example Services
1 GBR
(1)
20 100 ms (11, 13) 10-2 N/A 2000 ms Conversational Voice
2 40 150 ms (11, 13) 10-3 N/A 2000 ms Conversational Video (Live Streaming)
3 30 50 ms (11, 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 (11, 13) 10-6 N/A 2000 ms Non-Conversational Video (Buffered Streaming)
65
(9, 12)
7 75 ms (7, 8) 10-2 N/A 2000 ms Mission Critical user plane Push To Talk voice (e.g. MCPTT)
66 (12) 20 100 ms (10, 13) 10-2 N/A 2000 ms Non-Mission-Critical user plane Push To Talk voice
67 (12) 15 100 ms (10, 13) 10-3 N/A 2000 ms Mission Critical Video user plane
75 (12)
71 56 150 ms (11, 13, 15) 10-6 N/A 2000 ms "Live" Uplink Streaming (e.g. TS 26.238)
72 56 300 ms (11, 13, 15) 10-4 N/A 2000 ms "Live" Uplink Streaming (e.g. TS 26.238)
73 56 300 ms (11, 13, 15) 10-8 N/A 2000 ms "Live" Uplink Streaming (e.g. TS 26.238)
74 56 500 ms (11, 15) 10-8 N/A 2000 ms "Live" Uplink Streaming (e.g. TS 26.238)
76 56 500 ms (11, 13, 15) 10-4 N/A 2000 ms "Live" Uplink Streaming (e.g. TS 26.238)
5 Non-GBR
(1)
10 100 ms (10, 13) 10-6 N/A N/A IMS Signalling
6 60 300 ms (10, 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 (10, 13) 10-6 N/A N/A Voice, Video (Live Streaming) Interactive Gaming
8 80 300 ms (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
10 90 1100 ms (13, 17) 10-6 N/A N/A Video (Buffered Streaming) TCP-based (e.g. www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.) and any service that can be used over satellite access type with these characteristics
69
(9, 12)
5 60 ms (7, 8) 10-6 N/A N/A Mission Critical delay sensitive signalling (e.g. MC-PTT signalling)
70 (12) 55 200 ms (7, 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 (10, 13) 10-2 N/A N/A V2X messages (see TS 23.287)
80 68 10 ms (5, 10) 10-6 N/A N/A Low Latency eMBB applications Augmented Reality
82 Delay-critical GBR 19 10 ms (4) 10-4 255 bytes 2000 ms Discrete Automation (see TS 22.261)
83 22 10 ms (4) 10-4 1354 bytes (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.186, TS 23.287)
84 24 30 ms (6) 10-5 1354 bytes (3) 2000 ms Intelligent transport systems (see TS 22.261)
85 21 5 ms (5) 10-5 255 bytes 2000 ms Electricity Distribution- high voltage (see TS 22.261). V2X messages (Remote Driving. See TS 22.186, (16), see TS 23.287)
86 18 5 ms (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 (4) 10-3 500 bytes 2000 ms Interactive Service - Motion tracking data, (see TS 22.261)
88 25 10 ms (4) 10-3 1125 bytes 2000 ms Interactive Service - Motion tracking data, (see TS 22.261)
89 25 15 ms (4) 10-4 17000 bytes 2000 ms Visual content for cloud/edge/split rendering (see TS 22.261)
90 25 20 ms (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 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 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.
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). 5QI-10 can accommodate the worst case PDB for GEO satellite type.
Up

Up   Top   ToC