School of Specs 38.300v19.3.0

3GPP 38.300 v19.3.0 — the document's own text

16.15.4.2.2 Discard

When the PSIHI indicates that all PDUs of the PDU Set are needed for a QoS flow, as soon as one PDU of a PDU set is known to be lost, the remaining PDUs of that PDU Set can be considered as no longer needed by the application and may be subject to discard operation at the transmitter to free up radio resources.

NOTE 1: It cannot always be assumed that the remaining PDUs are not useful and can safely be discarded. In case of Forward Error Correction (FEC), active discarding of PDUs when assuming that a large enough number of packets have already been transmitted for FEC to recover without the remaining PDUs is not recommended as it might trigger an increase of FEC packets.

In uplink, the UE may be configured with PDU Set based discard operation for a specific DRB. When configured, the UE discards all packets in a PDU set when one PDU belonging to this PDU set is discarded due to discard timer expiry.

The gNB may perform downlink PDU Set discarding based on implementation by taking at least PSDB, PSI, PSIHI parameters into account.

In case of congestion, for downlink, the gNB may perform PDCP SDU discarding based on PSI. For uplink, dedicated downlink signalling is used to request the UE to apply a shorter discard timer to PDCP SDUs belonging to low importance PDU Sets in PDCP.

NOTE 2: How PDU Sets are identified as low importance is left up to UE implementation. When a PSI is available, it can be used according to the guidelines specified in TS 26.522 [58].

The transmitting PDCP entity can inform the receiving one of gaps in the sequence of transmitted PDCP SN, resulting from PDCP SDU discard, via a PDCP control PDU.