5G（NR）網(wǎng)絡(luò)中的服務(wù)質(zhì)量標(biāo)識(shí)(5QI值用于用戶在5G網(wǎng)絡(luò)中的服務(wù)；從而通過(guò)使用標(biāo)準(zhǔn)的服務(wù)質(zhì)量特征從優(yōu)化的信令中受益。動(dòng)態(tài)分配的5QI值需要QoS特征的信令消息，作為QoS配置文件一部分，可以用于未定義標(biāo)準(zhǔn)化5QI值的服務(wù)。下表指定了標(biāo)準(zhǔn)化的5QI值與5G QoS特性的映射。

       上表中的注釋詳細(xì)說(shuō)明如下：

•         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 “l(fā)ive” 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.

原文來(lái)自：http://www.techplayon.com/