name: PSER
full_form: PDU Set Error Rate
context: The PDU Set Error Rate (PSER) defines an upper bound for the rate of PDU Sets 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 PSER defines an upper bound for a rate of non-congestion related PDU Set losses. The purpose of the PSER is to allow for appropriate link layer protocol configurations (e.g. RLC and HARQ in RAN of a 3GPP access). NOTE 1: In this Release, a PDU Set is considered as successfully delivered only when all PDUs of a PDU Set are delivered successfully. NOTE 2: How RAN enforces PSER is up to RAN implementation. A QoS Flow is associated with at most one PDU Set Error Rate value per direction. PSER is an optional parameter. If the PSER is available, the PSER supersedes the PER.
description: The PDU Set Error Rate (PSER) is a parameter that defines the maximum allowable rate of PDU Sets that are not successfully delivered by the receiver to the upper layer, excluding congestion-related losses. It serves as an upper bound for non-congestion related PDU Set losses and enables appropriate link layer protocol configurations, such as RLC and HARQ in 3GPP access networks. The PSER is considered on a per QoS Flow basis, with each flow associated with at most one PSER value per direction, and it supersedes the Packet Error Rate (PER) if available.
explanation: PSER is classified as a Parameter because it is a configurable setting used in link layer protocols to manage PDU Set delivery and error rates. Its primary purpose is to guide protocol configurations for efficient data transmission, aligning with the 3GPP's specifications for network performance optimization.
section_title: 5.7.7.3 PDU Set Error Rate
biotag_Context: O,B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,B-Network,O,O,B-Organization,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,B-Network,O,O,B-Organization,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,B-Protocol,O,B-Network,O,O,B-Organization,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,B-Network,O,B-Parameter,O,O,O,B-Network,O,O,B-Measurement,O,O,O,O,O,O,O,B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,B-Parameter,O,O,O,O,O,O,B-Parameter,O,O,O,B-Parameter,O,O,O
biotag_Description: O,B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,B-Protocol,O,B-Organization,O,O,O,B-Parameter,O,O,O,O,O,B-Measurement,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Parameter,I-Parameter,I-Parameter,O,O,O