name: GP
full_form: Guard Period
context: The transmitting TM-RLC entity receives RLC SDUs from upper layers through the TM-SAP. All received RLC SDUs must be of a length that is a multiple of one of the valid TMD PDU lengths. If segmentation has been configured by upper layers and a RLC SDU is larger than the TMD PDU size used by the lower layer for that TTI, the transmitting TM RLC entity segments RLC SDUs to fit the TMD PDUs size without adding RLC headers. All the TMD PDUs carrying one RLC SDU are sent in the same TTI, and no segment from another RLC SDU are sent in this TTI. If segmentation has not been configured by upper layers, then more than one RLC SDU can be sent in one TTI by placing one RLC SDU in one TMD PDU. All TMD PDUs in one TTI must be of equal length. When the processing of a RLC SDU is complete, the resulting one or more TMD PDU(s) are/is submitted to the lower layer through either a BCCH, DCCH, PCCH, CCCH, SHCCH or a DTCH logical channel.
description: The Guard Period (GP) is a parameter in the frame structure of the physical layer, specifically designed to prevent interference between uplink and downlink transmissions. It ensures that an UE transmitting the UpPTS does not disturb the reception of the DwPTS for other UEs nearby. The GP has a length of 96 chips and supports cell radii of up to approximately 11 km for uplink synchronization operations.
explanation: The context describes the Guard Period (GP) as a specific parameter within the frame structure, highlighting its role in preventing interference between uplink and downlink transmissions. This description aligns with the definition of a Parameter entity type, which refers to configuration settings used in various processes.
section_title: 7.2.1	Frame structure
biotag_Context: O,O,O,O,O,B-Protocol,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,B-Message,B-Connection,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,B-Parameter,O,O,O,O,B-Message,B-Connection,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Protocol,O,O,B-Protocol,O,O,O,O,B-Message,O,O,O,O,B-Protocol,O,O,O,B-Message,O,O,O,B-Protocol,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,B-Parameter,O,O,O,O,O,B-Parameter,O,O,O,B-Protocol,B-Parameter,O,O,B-Message,O,O,B-Message,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Protocol,B-Parameter,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,B-Connection,O,O
biotag_Description: O,B-Interface,I-Interface,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-Device,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,B-Device,O,O,B-Interface,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O