34-QoS管理

与核心网之间不再采用承载

的概念，

由

NSA

组网中的

EP S Bearer

变成了

QoS Flow

。

QoS Flow

是

QoS

控制

的最细粒度，类似于

NSA

组网中的

EPS Bearer

。每一个

QoS Flow

用一个

QoS

Flow ID (QFI)

来标识。在一个

PDU

会话内，每个

QoS Flow

的

Q FI

都是唯一

的。核心网会通知

gNo deB

每个

QoS Flow

对应的

5QI(5G QoS Identifier )

，用

于确定其

QoS

属性。

gNodeB

需要将

QoS Flow

映射到承载上，

QoS Flow

与空口

Radio Bearer

可以是

多对一的映射关系，也可以是一对一的映射关系。

SA

组网下的

QoS

架构

当

UE

发起业务请求时，

gNod eB

读取

N2

接口

INITIAL CONTEXT SETUP REQUEST

消息或

PDU SESSION RESOURCE SETUP REQUEST

消息中各

QoS Flow

的

QoS

属性

值，根据参数配置， 将不同的

QoS Flow

（不同的

5 QI

）映射到对应的承载上，

为业务配置合适的无线承载参数、 传输资源配置参数。

QoS

涉及到如下一些参数：

1

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

2

Priority Level;

3

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

NSA

组网下，各

QCI

对应的资源类型如下：

QCI

Resource

Priority

Packet

Packet

Example Services

1

(NOTE 3)

2

(NOTE 3)

3

(NOTE 3,

NOTE 14)

4

(NOTE 3)

65

(NOTE 3,

NOTE 9,

NOTE 12)

66

(NOTE 3,

NOTE 12)

67

(NOTE 3,

NOTE 12)

75

(NOTE 14)

71

72

73

Type

Level

Delay

Error

Budget

Loss

(NOTE 13)

Rate

(NOTE 2)

2

100 ms

10

-2

Conversational Voice

(NOTE 1,

NOTE 11)

4

150 ms

10

-3

Conversational Video (Live

GBR

(NOTE 1,

Streaming)

NOTE 11)

3

50 ms

10

-3

Real Time Gaming, V2X

(NOTE 1,

messages

NOTE 11)

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)

5

300 ms

10

-6

Non-Conversational Video

(NOTE 1,

(Buffered Streaming)

NOTE 11)

0.7

75 ms

Mission Critical user plane Push

(NOTE 7,

10

-2

To Talk voice (e.g., MCPTT)

NOTE 8)

100 ms

Non- Mission-Critical user plane

2

(NOTE 1,

10

-2

Push To Talk voice

NOTE 10)

100 ms

Mission Critical Video user plane

1.5

(NOTE 1,

10

-3

NOTE 10)

2.5

50 ms

10

-2

V2X messages

(NOTE 1)

5.6

150ms

10

-6

(NOTE 1,

TS 26.238 [53])

NOTE 16)

5.6

300ms

10

-4

(NOTE 1,

TS 26.238 [53])

NOTE 16)

5.6

300ms

10

-8

(NOTE 1,

TS 26.238 [53])

NOTE 16)

74

5.6

500ms

(NOTE 1,

NOTE 16)

10

-8

TS 26.238 [53])

76

5.6

500ms

(NOTE 1,

NOTE 16)

10

-4

TS 26.238 [53])

5

(NOTE 3)

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)

Non-GBR

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

10

-6

Video (Buffered Streaming)

TCP-based (e.g., www, e-mail,

chat, ftp, p2p file

9

(NOTE 6)

69

(NOTE 3,

NOTE 9,

NOTE 12)

70

(NOTE 4,

NOTE 12)

79

(NOTE 14)

9

sharing, progressive video, etc.)

0.5

60 ms

(NOTE 7,

NOTE 8)

Mission Critical delay sensitive

signalling (e.g., MC-PTT

signalling, MC Video signalling)

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)

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

to the radio base station (roughly 10 ms) and the case where the PCEF is located

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

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

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

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

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.

NOTE 16: For

QCIs correspond to the latency configurations defined in TR 26.939 [54]. In order to

support higher latency reliable streaming services (above 500ms PDB), if different PDB

and PELR combinations are needed these configurations will have to use non-

standardised QCIs.

SA

组网下，各标准

5QI

对应的

QoS

属性根据 资源类型的不同，分为

GBR

、

Non -

GBR

及

Delay Critical GBR

。

Standardized 5QI to QoS characteristics mapping