23.501中英对照（45）：5G Qos特征

前言

本文是对5G最基础也是最重要的规范

TS23.501的中英对照翻译。 

但不是全文翻译，有以下重要说明：

• 不是全文翻译，一些国内不可能用到的特性不翻。

• 原文有些章节没有内容，或者意义不大，直接跳过。

• 所以是从第4章开始翻译。

• 一句英文原文，一句中文。方便对照。

• 采用最新的2024年12月发布的R18.8版本。

• 任何问题，欢迎微信交流。

• 作者微信：gprshome201101，微信名：爱卫生

---

5.7.3 5G QoS characteristics

5.7.3 5G QoS特性

5.7.3.1 General

5.7.3.1 概述

This clause specifies the 5G QoS characteristics associated with 5QI. The characteristics describe the packet forwarding treatment that a QoS Flow receives edge-to-edge between the UE and the UPF in terms of the following performance characteristics:

本节规定了与5QI相关的5G QoS特性。这些特性描述了QoS流在用户设备（UE）和用户面功能（UPF）之间端到端的数据包转发处理，涵盖以下性能特性：

1 Resource type (Non-GBR, GBR, Delay-critical GBR);
2 Priority Level;
3 Packet Delay Budget (including Core Network 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).

1 资源类型（非保证比特率Non-GBR、保证比特率GBR、延迟关键型GBR）；
2 优先级；
3 分组时延预算（包括核心网分组时延预算）；
4 分组误码率；
5 平均窗口（仅适用于GBR和延迟关键型GBR资源类型）；
6 最大数据突发量（仅适用于延迟关键型GBR资源类型）。

The 5G QoS characteristics should be understood as guidelines for setting node specific parameters for each QoS Flow e.g. for 3GPP radio access link layer protocol configurations.

5G QoS特性应被理解为为每个QoS流设置节点特定参数的指导原则，例如用于3GPP无线接入链路层协议配置。

Standardized or pre-configured 5G QoS characteristics, are indicated through the 5QI value and are not signalled on any interface, unless certain 5G QoS characteristics are modified as specified in clauses 5.7.3.3, 5.7.3.4, 5.7.3.6 and 5.7.3.7.

标准化或预配置的5G QoS特性通过5QI值指示，不在任何接口上传递信令，除非按照5.7.3.3、5.7.3.4、5.7.3.6和5.7.3.7章节的规定修改某些5G QoS特性。

NOTE: As there are no default values specified, pre-configured 5G QoS characteristics have to include all of the characteristics listed above.

注意：由于未指定默认值，预配置的5G QoS特性必须包含上述所有特性。

Signalled 5G QoS characteristics are provided as part of the QoS profile and shall include all of the characteristics listed above.

信令传递的5G QoS特性作为QoS配置文件的一部分提供，必须包含上述所有特性。

5.7.3.2 Resource Type

5.7.3.2 资源类型

The resource type determines if dedicated network resources related to a QoS Flow-level Guaranteed Flow Bit Rate (GFBR) value are permanently allocated (e.g. by an admission control function in a radio base station).

资源类型决定了与QoS流级别的保证流比特率（GFBR）相关的专用网络资源是否被永久分配（例如，由无线基站中的准入控制功能分配）。

GBR QoS Flows are therefore typically authorized "on demand" which requires dynamic policy and charging control. A GBR QoS Flow uses either the GBR resource type or the Delay-critical GBR resource type. The definition of PDB and PER are different for GBR and Delay-critical GBR resource types and the MDBV parameter applies only to the Delay-critical GBR resource type.

因此，GBR QoS流通常被按需授权，这需要动态的策略和计费控制。GBR QoS流使用GBR资源类型或延迟关键型GBR资源类型。对于GBR和延迟关键型GBR资源类型，PDB和PER的定义不同，MDBV参数仅适用于延迟关键型GBR资源类型。

A Non-GBR QoS Flow may be pre-authorized through static policy and charging control. A Non-GBR QoS Flow uses only the Non-GBR resource type.

非GBR QoS流可通过静态策略和计费控制进行预授权。非GBR QoS流仅使用非GBR资源类型。

5.7.3.3 Priority Level

5.7.3.3 优先级

The Priority Level associated with 5G QoS characteristics indicates a priority in scheduling resources among QoS Flows. The lowest Priority Level value corresponds to the highest priority.

与5G QoS特性相关的优先级表示在QoS流之间调度资源的优先顺序。最低的优先级值对应于最高的优先级。

The Priority Level shall be used to differentiate between QoS Flows of the same UE and it shall also be used to differentiate between QoS Flows from different UEs.

优先级应用于区分同一UE的QoS流，也应用于区分不同UE的QoS流。

In the case of congestion, when all QoS requirements cannot be fulfilled for one or more QoS Flows, the Priority Level shall be used to select for which QoS Flows the QoS requirements are prioritised such that a QoS Flow with Priority Level value N is prioritized over QoS Flows with higher Priority Level values (i.e. N+1, N+2, etc). In the case of no congestion, the Priority Level should be used to define the resource distribution between QoS Flows. In addition, the scheduler may prioritize QoS Flows based on other parameters (e.g. resource type, radio condition) in order to optimize application performance and network capacity.

在发生拥塞时，当一个或多个QoS流的所有QoS需求无法满足时，优先级将用于选择哪些QoS流的QoS需求被优先满足，使得优先级值为N的QoS流优先于具有更高优先级值（即N+1、N+2等）的QoS流。在没有拥塞的情况下，优先级应用于定义QoS流之间的资源分配。此外，调度器还可根据其他参数（例如资源类型、无线条件）来优先处理QoS流，以优化应用性能和网络容量。

Every standardized 5QI is associated with a default value for the Priority Level (specified in QoS characteristics Table 5.7.4-1). Priority Level may also be signalled together with a standardized 5QI to the (R)AN and if it is received, it shall be used instead of the default value.

每个标准化的5QI都与一个默认的优先级值相关（在QoS特性表5.7.4-1中指定）。优先级也可以与标准化的5QI一起传送给（R）AN，如果接收到，则应使用该值代替默认值。

Priority Level may also be signalled together with a pre-configured 5QI to the (R)AN and if it is received, it shall be used instead of the pre-configured value.

优先级也可以与预配置的5QI一起传送给（R）AN，如果接收到，则应使用该值代替预配置值。

5.7.3.4 Packet Delay Budget

5.7.3.4 分组时延预算

The Packet Delay Budget (PDB) defines an upper bound for the time that a packet may be delayed between the UE and the N6 termination point at the UPF. The PDB applies to the DL packet received by the UPF over the N6 interface and to the UL packet sent by the UE. For a certain 5QI the value of the PDB is the same in UL and DL. In the case of 3GPP access, the PDB is used to support the configuration of scheduling and link layer functions (e.g. the setting of scheduling priority weights and HARQ target operating points). For GBR QoS Flows using the Delay-critical resource type, a packet delayed more than PDB is counted as lost if the data burst is not exceeding the MDBV within the period of PDB and the QoS Flow is not exceeding the GFBR. For GBR QoS Flows with GBR resource type not exceeding GFBR, 98 percent of the packets shall not experience a delay exceeding the 5QI's PDB.

分组时延预算（PDB）定义了数据包在UE和UPF的N6终止点之间可能延迟的上限。PDB适用于UPF通过N6接口接收的下行数据包和UE发送的上行数据包。对于某个5QI，PDB的值在上行和下行方向是相同的。在3GPP接入情况下，PDB用于支持调度和链路层功能的配置（例如调度优先级权重的设置和HARQ目标工作点）。对于使用延迟关键型资源类型的GBR QoS流，如果在PDB周期内数据突发未超过MDBV且QoS流未超过GFBR，延迟超过PDB的分组被视为丢失。对于使用GBR资源类型且未超过GFBR的GBR QoS流，98％的分组不应经历超过5QI的PDB的延迟。

The 5G Access Network Packet Delay Budget (5G-AN PDB) is determined by subtracting a static value for the Core Network Packet Delay Budget (CN PDB), which represents the delay between any N6 termination point at the UPF (for any UPF that may possibly be selected for the PDU Session) and the 5G-AN from a given PDB.

5G接入网络分组时延预算（5G-AN PDB）通过从给定的PDB中减去核心网分组时延预算（CN PDB）的静态值来确定，该值表示UPF上任何N6终止点（对于可能为PDU会话选择的任何UPF）与5G-AN之间的延迟。

NOTE 1: For a standardized 5QI, the static value for the CN PDB is specified in the QoS characteristics Table 5.7.4-1.

注意1：对于标准化的5QI，CN PDB的静态值在QoS特性表5.7.4-1中指定。

NOTE 2: For a non-standardized 5QI, the static value for the CN PDB is homogeneously configured in the network.

注意2：对于非标准化的5QI，CN PDB的静态值在网络中统一配置。

For GBR QoS Flows using the Delay-critical resource type, in order to obtain a more accurate delay budget PDB available for the NG-RAN, a dynamic value for the CN PDB, which represents the delay between the UPF terminating N6 for the QoS Flow and the 5G-AN, can be used. If used for a QoS Flow, the NG-RAN shall apply the dynamic value for the CN PDB instead of the static value for the CN PDB (which is only related to the 5QI). Different dynamic value for CN PDB may be configured per uplink and downlink direction.

对于使用延迟关键型资源类型的GBR QoS流，为了获得可用于NG-RAN的更准确的时延预算PDB，可使用CN PDB的动态值，该值表示为QoS流终止N6的UPF与5G-AN之间的延迟。如果用于QoS流，NG-RAN应使用CN PDB的动态值代替CN PDB的静态值（仅与5QI相关）。可在上行和下行方向上配置不同的CN PDB动态值。

NOTE 3: The configuration of transport network on CN tunnel can be different per UL and DL, which can be different value for CN PDB per UL and DL.

注意3：CN隧道上的传输网络配置可以在上行和下行方向上不同，这可能导致每个方向的CN PDB值不同。

NOTE 4: It is expected that the UPF deployment ensures that the dynamic value for the CN PDB is not larger than the static value for the CN PDB. This avoids that the functionality that is based on the 5G-AN PDB (e.g. MDBV, NG-RAN scheduler) has to handle an unexpected value.

注意4：预期UPF的部署确保CN PDB的动态值不大于CN PDB的静态值。这避免了基于5G-AN PDB的功能（例如MDBV、NG-RAN调度器）必须处理意外的值。

The dynamic value for the CN PDB of a Delay-critical GBR 5QI may be configured in the network in two ways:

延迟关键型GBR 5QI的CN PDB动态值可通过两种方式在网络中配置：

• Configured in each NG-RAN node, based on a variety of inputs such as different IP address(es) or TEID range of UPF terminating the N3 tunnel and based on different combinations of PSA UPF to NG-RAN under consideration of any potential I-UPF, etc;

• 在每个NG-RAN节点中配置，基于各种输入，如终止N3隧道的UPF的不同IP地址或TEID范围，以及考虑任何潜在的I-UPF情况下的PSA UPF到NG-RAN的不同组合等；

• Configured in the SMF, based on different combinations of PSA UPF to NG-RAN under consideration of any potential I-UPF. The dynamic value for the CN PDB for a particular QoS Flow shall be signalled to NG-RAN (during PDU Session Establishment, PDU Session Modification, Xn/N2 handover and the Service Request procedures) when the QoS Flow is established or the dynamic value for the CN PDB of a QoS Flow changes, e.g. when an I-UPF is inserted by the SMF.

• 在SMF中配置，基于考虑任何潜在的I-UPF情况下PSA UPF到NG-RAN的不同组合。当QoS流建立或QoS流的CN PDB动态值更改时（例如，当SMF插入I-UPF时），该QoS流的CN PDB动态值应传递给NG-RAN（在PDU会话建立、PDU会话修改、Xn/N2切换和服务请求过程期间）。

If the NG-RAN node is configured locally with a dynamic value for the CN PDB for a Delay-critical GBR 5QI and receives a different value via N2 signalling for a QoS Flow with the same 5QI, local configuration in RAN node determines which value takes precedence.

如果NG-RAN节点本地配置了延迟关键型GBR 5QI的CN PDB动态值，并且通过N2信令接收到具有相同5QI的QoS流的不同值，则RAN节点中的本地配置决定哪个值具有优先权。

Services using a GBR QoS Flow and sending at a rate smaller than or equal to the GFBR can in general assume that congestion related packet drops will not occur.

使用GBR QoS流并以小于或等于GFBR的速率发送的服务通常可以假设不会发生与拥塞相关的分组丢失。

NOTE 5: Exceptions (e.g. transient link outages) can always occur in a radio access system which may then lead to congestion related packet drops. Packets surviving congestion related packet dropping may still be subject to non-congestion related packet losses (see PER below).

注意5：在无线接入系统中总是可能发生异常情况（例如瞬时链路中断），这可能导致与拥塞相关的分组丢失。幸存于拥塞相关分组丢失的分组可能仍会遭受非拥塞相关的分组丢失（参见下文的PER）。

Services using Non-GBR QoS Flows should be prepared to experience congestion-related packet drops and delays. In uncongested scenarios, 98 percent of the packets should not experience a delay exceeding the 5QI's PDB.

使用非GBR QoS流的服务应准备好应对与拥塞相关的分组丢失和延迟。在非拥塞场景中，98%的分组不应经历超过5QI的PDB的延迟。

The PDB for Non-GBR and GBR resource types denotes a "soft upper bound" in the sense that an "expired" packet, e.g. a link layer SDU that has exceeded the PDB, does not need to be discarded and is not added to the PER. However, for a Delay-critical GBR resource type, packets delayed more than the PDB are added to the PER and can be discarded or delivered depending on local decision.

非GBR和GBR资源类型的PDB表示一个“软上限”，即“过期”的分组（例如超过PDB的链路层SDU）不需要被丢弃，也不计入PER。然而，对于延迟关键型GBR资源类型，延迟超过PDB的分组会被计入PER，并可根据本地决定进行丢弃或传送。

5.7.3.5 Packet Error Rate

5.7.3.5 分组误码率

The Packet Error Rate (PER) defines an upper bound for the rate of PDUs (e.g. IP packets) that have been processed by the sender of a link layer protocol (e.g. RLC in RAN of a 3GPP access) but that are not successfully delivered by the corresponding receiver to the upper layer (e.g. PDCP in RAN of a 3GPP access). Thus, the PER defines an upper bound for a rate of non-congestion related packet losses. The purpose of the PER is to allow for appropriate link layer protocol configurations (e.g. RLC and HARQ in RAN of a 3GPP access). For every 5QI the value of the PER is the same in UL and DL. For GBR QoS Flows with Delay-critical GBR resource type, a packet which is delayed more than PDB is counted as lost and included in the PER unless the data burst is exceeding the MDBV within the period of PDB or the QoS Flow is exceeding the GFBR.

分组误码率（PER）定义了链路层协议发送方（例如3GPP接入的RAN中的RLC）已处理但未被相应接收方成功传递到上层（例如3GPP接入的RAN中的PDCP）的PDU（例如IP包）的比率的上限。因此，PER定义了非拥塞相关分组丢失率的上限。PER的目的是允许适当的链路层协议配置（例如3GPP接入的RAN中的RLC和HARQ）。对于每个5QI，PER的值在上行和下行方向是相同的。对于使用延迟关键型GBR资源类型的GBR QoS流，除非在PDB周期内数据突发超过MDBV或QoS流超过GFBR，否则延迟超过PDB的分组被视为丢失并计入PER。

5.7.3.6 Averaging Window

5.7.3.6 平均窗口

Each GBR QoS Flow shall be associated with an Averaging window. The Averaging window represents the duration over which the GFBR and MFBR shall be calculated (e.g. in the (R)AN, UPF, UE).

每个GBR QoS流应与一个平均窗口相关联。平均窗口表示计算GFBR和MFBR的时间段（例如在（R）AN、UPF、UE中）。

Every standardized 5QI (of GBR and Delay-critical GBR resource type) is associated with a default value for the Averaging window (specified in QoS characteristics Table 5.7.4-1). The averaging window may also be signalled together with a standardized 5QI to the (R)AN and UPF and if it is received, it shall be used instead of the default value.

每个标准化的5QI（GBR和延迟关键型GBR资源类型）都与一个默认的平均窗口值相关（在QoS特性表5.7.4-1中指定）。平均窗口也可以与标准化的5QI一起传送给（R）AN和UPF，如果接收到，则应使用该值代替默认值。

The Averaging window may also be signalled together with a pre-configured 5QI to the (R)AN and if it is received, it shall be used instead of the pre-configured value.

平均窗口也可以与预配置的5QI一起传送给（R）AN，如果接收到，则应使用该值代替预配置值。

5.7.3.7 Maximum Data Burst Volume

5.7.3.7 最大数据突发量

Each GBR QoS Flow with Delay-critical resource type shall be associated with a Maximum Data Burst Volume (MDBV).

每个具有延迟关键型资源类型的GBR QoS流应与一个最大数据突发量（MDBV）相关联。

MDBV denotes the largest amount of data that the 5G-AN is required to serve within a period of 5G-AN PDB.

MDBV表示5G-AN在5G-AN PDB周期内需要服务的最大数据量。

Every standardized 5QI (of Delay-critical GBR resource type) is associated with a default value for the MDBV (specified in QoS characteristics Table 5.7.4-1). The MDBV may also be signalled together with a standardized 5QI to the (R)AN and if it is received, it shall be used instead of the default value.

每个标准化的5QI（延迟关键型GBR资源类型）都与一个默认的MDBV值相关（在QoS特性表5.7.4-1中指定）。MDBV也可以与标准化的5QI一起传送给（R）AN，如果接收到，则应使用该值代替默认值。

The MDBV may also be signalled together with a pre-configured 5QI to the (R)AN and if it is received, it shall be used instead of the pre-configured value.

MDBV也可以与预配置的5QI一起传送给（R）AN，如果接收到，则应使用该值代替预配置值。