name: GTP-U
full_form: GPRS Tunnelling Protocol User plane
context: The NG-RAN node (non-split) bases the selection of its PCI either on a centralized or distributed PCI assignment algorithm. In the split gNB architecture, there are several options for the PCI selection. A non-exhaustive list of possible option is reported below. Details about which option will be selected for normative specification will be provided during work item phase. Case 1: centralized PCI selection, OAM assigns a single PCI to each NR cell In this case, the OAM configures a single PCI value for NR cells in the DU. The DU sends the PCI of each serving cell to the CU during the F1 setup procedure. - Option 1a: CU detects PCI conflict and indicates to OAM via DU. OAM assigns a new PCI. In option 1, when the CU detects PCI conflict between NR cells within a DU or between neighbouring gNBs, it sends the PCI conflict indication to the DU. The DU reports the PCI conflict to the OAM. After that, the OAM will allocate a new PCI value for the DU. - Option 1b: CU detects PCI conflict and
description: GPRS Tunnelling Protocol User plane (GTP-U) is a protocol used in mobile networks to tunnel user data between different network elements. It is part of the GTP protocol suite, which also includes GTP-C for control plane messages. The context highlights considerations for simplifying the GTP-U header to reduce overhead for real-time applications, indicating its role in optimizing user plane data transmission.
explanation: GTP-U is classified as a Protocol based on the provided context, which discusses its use in user plane data transmission, header structure, and potential optimizations. The text mentions specific details about GTP-U messages, the TEID field, and its relationship with other protocols like GTP-C, solidifying its classification as a protocol.
section_title: 6.13.1.4	User plane header simplification considerations for the Iu-PS
biotag_Context: O,B-Network Function,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Parameter,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-Parameter,O,B-Miscellaneous,O,O,O,B-Parameter,O,O,B-Network,O,O,O,O,O,B-Miscellaneous,O,O,O,B-Parameter,O,O,B-Network,O,O,O,O,O,B-Network Function,O,O,B-Parameter,O,O,O,O,O,O,B-Network Function,O,O,B-Interface,O,O,O,O,O,B-Network Function,O,B-Parameter,O,O,O,O,B-Miscellaneous,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Parameter,O,O,B-Network,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,B-Network Function,O,O,B-Parameter,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Network Function,O,B-Parameter,O,O
biotag_Description: B-Protocol,I-Protocol,I-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O