name: PDN
full_form: Packet Data Network
context: The PDN GW may provide mechanisms for avoiding and handling overload situations. These include the rejection of PDN connection requests from UEs. The PDN GW may detect APN congestion and start and stop performing overload control based on criteria such as: - Maximum number of active bearers per APN; and/or - Maximum rate of bearer activations per APN. When performing overload control the PDN GW rejects PDN connection requests. When receiving the rejection from the PDN GW, the MME rejects the UE's PDN connection request as specified in clause 4.3.7.4.2. In addition the PDN GW may indicate a "PDN GW back-off time" for a specific APN to the MME. The MME should reject PDN connection requests, for the specific APN related to that PDN GW during the "PDN GW back-off time", by the means specified in clause 4.3.7.4.2. If a PDN GW indicates APN congestion by the "PDN GW back-off time" the MME may select another PDN GW of that APN instead of rejecting PDN connection requests unless there is already an existing PDN connection to the same APN for the UE, in which case, the MME shall reject PDN connection request.
description: The Packet Data Network (PDN) Gateway (GW) is a critical network function within the Evolved Packet Core (EPC) architecture. It serves as an entry and exit point for data traffic between the E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and external packet data networks, such as the Internet or private IP networks. The PDN GW is responsible for managing packet data sessions, including bearer setup, modification, and release. Additionally, it provides mechanisms for avoiding and handling overload situations by rejecting PDN connection requests from User Equipment (UEs), detecting APN congestion, and indicating a 'PDN GW back-off time' to the Mobility Management Entity (MME).
explanation: The PDN is classified as a Network Function because it plays a vital role in managing packet data sessions and providing mechanisms for overload control within the EPC architecture. Its functions align with the 3GPP's specifications for efficient network operations, making it an essential component of the telecommunications infrastructure.
section_title: 4.3.7.5 PDN GW control of overload
biotag_Context: O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,B-Network Function,I-Network Function,O,O,B-Network,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,O,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,O,B-Network,O,O,O,O,O,O,O,O,B-Network,O,O,B-Network Function,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network,O,O,O,O,B-Network Function,O,O,B-Network,O,O,O,O,O,B-Network,O,O,O,B-Network Function,I-Network Function,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,O,B-Network,O,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,O,B-Network Function,I-Network Function,O,O,B-Network,O,O,O,B-Network,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,B-Network,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network,O,O
biotag_Description: O,B-Network,I-Network,I-Network,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network,I-Network,I-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Network Function,I-Network Function,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-Network,O,O,O,B-Device,I-Device,O,O,B-Network,O,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O