#Параметры качества LTE (QoS)

Представлена информация о параметрах качества LTE (QoS сети 4G). После того как пользователь запрашивает определённый тип сервиса, сеть 4G LTE автоматически назначает для пользовательского сервиса идентификатор LTE QCI (4G QoS Identifier) с требуемым качеством сервиса (QoS, Quality of Service) и перестраивает технические параметры сети 4G с целью выполнения требований LTE QCI.

Модель использования параметров качества LTE QCI  сети 4G основана на использование EPS Bearer и  как в сети 5G NR поддерживает как GBR (guaranteed flow bit rate, гарантированную скорость) так и Non-GBR (do not guaranteed flow bit rate,  не гарантированную скорость).

На рисунке ниже представлена модель  применения LTE QCI в сетях 4G. 

4G LTE QoS architecture

Требования  к параметрам качества LTE, каждого назначенного LTE QCI строго регламентируется в рамках 3GPP TS 23.203 и представлены в таблицах ниже

QCI

Resource Type

Priority Level

Packet Delay Budget

(NOTE 13)

Packet Error Loss

Rate (NOTE 2)

Example Services

1
(NOTE 3)

 GBR

2

100 ms
(NOTE 1, NOTE 11)

10-2

Conversational Voice

2
(NOTE 3)

4

150 ms
(NOTE 1, NOTE 11)

10-3

Conversational Video (Live Streaming)

3
(NOTE 3, NOTE 14)

3

50 ms
(NOTE 1, NOTE 11)

10-3

Real Time Gaming, V2X messages

Electricity distribution — medium voltage (e.g. TS 22.261 [51] clause 7.2.2)

Process automation — monitoring (e.g. TS 22.261 [51] clause 7.2.2)

4
(NOTE 3)

5

300 ms
(NOTE 1, NOTE 11)

10-6

Non-Conversational Video (Buffered Streaming)

65
(NOTE 3, NOTE 9, NOTE 12)

0.7

75 ms
(NOTE 7,
NOTE 8)

10-2

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

66
(NOTE 3, NOTE 12)

2

100 ms
(NOTE 1,
NOTE 10)

10-2

Non-Mission-Critical user plane Push To Talk voice

67
(NOTE 3, NOTE 12)

1.5

100 ms
(NOTE 1,
NOTE 10)

10-3

Mission Critical Video user plane

75
(NOTE 14)

2.5

50 ms
(NOTE 1)

10-2

V2X messages

5
(NOTE 3)

 Non-GBR

1

100 ms
(NOTE 1, NOTE 10)

10-6

IMS Signalling

6
(NOTE 4)

6

300 ms
(NOTE 1, NOTE 10)

10-6

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

7
(NOTE 3)

7

100 ms
(NOTE 1, NOTE 10)

10-3

Voice,
Video (Live Streaming)
Interactive Gaming

8
(NOTE 5)

8

300 ms
(NOTE 1)

10-6

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

9
(NOTE 6)

9

69
(NOTE 3, NOTE 9, NOTE 12)

0.5

60 ms
(NOTE 7, NOTE 8)

10-6

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

70
(NOTE 4, NOTE 12)

5.5

200 ms
(NOTE 7, NOTE 10)

10-6

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

79
(NOTE 14)

6.5

50 ms
(NOTE 1, NOTE 10)

10-2

V2X messages

80
(NOTE 3)

6.8

10 ms
(NOTE 10, NOTE 15)

10-6

Low latency eMBB applications (TCP/UDP-based);

Augmented Reality

NOTE 1:    A delay of 20 ms for the delay between a PCEF and a radio base station should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. This delay is the average between the case where the PCEF is located «close» to the radio base station (roughly 10 ms) and the case where the PCEF is located «far» from the radio base station, e.g. in case of roaming with home routed traffic (the one-way packet delay between Europe and the US west coast is roughly 50 ms). The average takes into account that roaming is a less typical scenario. It is expected that subtracting this average delay of 20 ms from a given PDB will lead to desired end-to-end performance in most typical cases. Also, note that the PDB defines an upper bound. Actual packet delays — in particular for GBR traffic — should typically be lower than the PDB specified for a QCI as long as the UE has sufficient radio channel quality.

NOTE 2:    The rate of non congestion related packet losses that may occur between a radio base station and a PCEF should be regarded to be negligible. A PELR value specified for a standardized QCI therefore applies completely to the radio interface between a UE and radio base station.

NOTE 3:    This QCI is typically associated with an operator controlled service, i.e., a service where the SDF aggregate’s uplink / downlink packet filters are known at the point in time when the SDF aggregate is authorized. In case of E-UTRAN this is the point in time when a corresponding dedicated EPS bearer is established / modified.

NOTE 4:    If the network supports Multimedia Priority Services (MPS) then this QCI could be used for the prioritization of non real-time data (i.e. most typically TCP-based services/applications) of MPS subscribers.

NOTE 5:    This QCI could be used for a dedicated «premium bearer» (e.g. associated with premium content) for any subscriber / subscriber group. Also in this case, the SDF aggregate’s uplink / downlink packet filters are known at the point in time when the SDF aggregate is authorized. Alternatively, this QCI could be used for the default bearer of a UE/PDN for «premium subscribers».

NOTE 6:    This QCI is typically used for the default bearer of a UE/PDN for non privileged subscribers. Note that AMBR can be used as a «tool» to provide subscriber differentiation between subscriber groups connected to the same PDN with the same QCI on the default bearer.

NOTE 7:    For Mission Critical services, it may be assumed that the PCEF is located «close» to the radio base station (roughly 10 ms) and is not normally used in a long distance, home routed roaming situation. Hence delay of 10 ms for the delay between a PCEF and a radio base station 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 QCIs 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 QCI-65 and QCI-69 are used together to provide Mission Critical Push to Talk service (e.g., QCI-5 is not used for signalling for the bearer that utilizes QCI-65 as user plane bearer). 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 QCIs 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 QCIs 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 QCI 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 QCI value.

NOTE 13: Packet delay budget is not applicable on NB-IoT or when Enhanced Coverage is used for WB-E-UTRAN (see TS 36.300 [19]).

NOTE 14: This QCI could be used for transmission of V2X messages as defined in TS 23.285 [48].

NOTE 15: A delay of 2 ms for the delay between a PCEF and a radio base station should be subtracted from the given PDB to derive the packet delay budget that applies to the radio interface.

QCI

Resource Type

Priority Level

Packet Delay Budget (NOTE B1)

Packet Error Loss

Rate (NOTE B2)

Maximum Data Burst Volume

(NOTE B1)

Data Rate Averaging Window

Example Services

82

(NOTE B6)

GBR

1.9

10 ms

(NOTE B4)

10-4

(NOTE B3)

255 bytes

2000 ms

Discrete Automation (TS 22.278 [38], clause 8 bullet g, and TS 22.261 [51], table 7.2.2-1, «small packets»)

83

(NOTE B6)

2.2

10 ms

(NOTE B4)

10-4

(NOTE B3)

1354 bytes

(NOTE B5)

2000 ms

Discrete Automation (TS 22.278 [38], clause 8 bullet g, and TS 22.261 [51], table 7.2.2-1, «big packets»)

84

(NOTE B6)

2.4

30 ms

(NOTE B7)

10-5

(NOTE B3)

1354 bytes

(NOTE B5)

2000 ms

Intelligent Transport Systems (TS 22.278 [38], clause 8, bullet h, and TS 22.261 [51], table 7.2.2).

85

(NOTE B6)

2.1

5 ms

(NOTE B8)

10-5

(NOTE B3)

255 bytes

2000 ms

Electricity Distribution- high voltage (TS 22.278 [38], clause 8, bullet i, and TS 22.261 [51], table 7.2.2 and Annex D, clause D.4.2).

NOTE B1:       The PDB applies to bursts that are not greater than Maximum Data Burst Volume.

NOTE B2:       This Packet Error Loss Rate includes packets that are not successfully delivered over the access network plus those packets that comply with the Maximum Data Burst Volume and GBR requirements but which are not delivered within the Packet Delay Budget.

NOTE B3:       Data rates above the GBR, or, bursts larger than the Maximum Data Burst Volume, are treated as best effort, and, in order to serve other packets and meet the PELR, this can lead to them being discarded.

NOTE B4:       A delay of 1 ms for the delay between a PCEF and a radio base station should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface.

NOTE B5:       This Maximum Data Burst Volume value is set to 1354 bytes to avoid IP fragmentation on an IPv6 based, IPSec protected GTP tunnel to the eNB (the value is calculated as in Annex C of TS 23.060 [12] and further reduced by 4 bytes to allow for the usage of a GTP-U extension header).

NOTE B6:       This QCI is typically associated with a dedicated EPS bearer.

NOTE B7:       A delay of 5 ms for the delay between a PCEF and a radio base station should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface.

NOTE B8:       A delay of 2 ms for the delay between a PCEF and a radio base station should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface.

Дополнительная информация о параметры качества LTE QoS приводится в: 3GPP TS 36.300, 3GPP TS23.401

Нашли ошибку? Напишите нам!

Статья была полезна?

Поделись с коллегами или воспользуйся:

#Калькулятор NR ARFCN 5G#Калькулятор скорости 4G#Калькулятор LTE EARFCN 4G, #Калькулятор скорости 5G

Share:
Share

Добавить комментарий

Ваш e-mail не будет опубликован.