Content for  TS 23.501  Word version:  19.3.0

A packet which is delayed more than PDB is not counted as lost, thus not included in the PER.

It is required that default MDBV is supported by a PLMN supporting the related 5QIs.

The Maximum Transfer Unit (MTU) size considerations in clause 9.3 of TS 23.060 and Annex J are also applicable. IP fragmentation may have impacts to CN PDB and details are provided in clause 5.6.10.

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.

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.

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.

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.

In RRC_IDLE, RRC_INACTIVE 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.

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.

In RRC_IDLE, RRC_INACTIVE 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.

In RRC_IDLE and RRC_INACTIVE 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.

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.

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.

This 5QI is only used for transmission of V2X messages as defined in TS 23.287 and transmission of A2X messages as defined in TS 23.256.

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.

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.

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.

When UE is accessing the network via satellite access supporting regenerative payload, a static value for the CN PDB of ~290ms for GEO satellite, ~41 ms for LEO at 1200km and 33 ms for LEO at 600km 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.