name: CLPC
full_form: Closed loop power control
context: the multicast group that is interested to join over the default PDP context using FDD unicast bearers, the IP multicast address of the group is extracted from the SDP description document for this particular MBMS service. The FDD GGSN receives the "IGMP Join" request as in [5]. The FDD GGSN initiates the appropriate Gmb interface signaling in order to request authorization from the BM-SC for the terminal with the particular IMSI to receive traffic for this particular multicast group. The authorization decision, which is based on subscription data in the BM-SC, is provided in the MBMS Authorization Response together with the APN to be used for creation of the MBMS UE context. Note: In this case, common GGSN for TDD and FDD networks is assumed. Hence the APN points to the common GGSN. The GGSN sends an MBMS Notification Request (IP multicast address, APN, Linked NSAPI) to the FDD SGSN. Linked NSAPI is set equal to the NSAPI of the PDP context over which the Join request was received.
description: Closed Loop Power Control (CLPC) is a procedure used in the downlink (DL) system to control the transmission power of the base station. It involves adjusting the power based on feedback from the user equipment, with the goal of maintaining an optimal Signal-to-Interference-plus-Noise Ratio (SINR). The CLPC delay refers to the time it takes for the base station to adjust its transmission power in response to changes in the SINR estimation.
explanation: The context describes a comparison between different methods of SINR estimation, including one that uses Closed Loop Power Control (CLPC) with a delay of 0 slots. This suggests that CLPC is a procedure used to control transmission power and adjust it based on SINR estimation, which is why it falls under the category of Procedure.
section_title: 9.3.1.1	Impact on SINR estimation mechanism
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Technology,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Service,O,O,B-Technology,B-Network Function,O,O,O,O,O,O,O,O,O,B-Technology,B-Network Function,O,O,O,B-Interface,O,O,O,O,O,O,O,O,O,B-Network Function,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,B-Service,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,B-Service,B-Device,O,O,O,O,O,O,B-Network Function,O,B-Technology,O,B-Technology,O,O,O,O,O,B-Network,O,O,O,O,O,O,B-Network Function,O,O,B-Service,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,B-Parameter,O,O,O,O,O,B-Parameter,O,O,B-Protocol,O,O,O,O,O,O,O,O
biotag_Description: O,O,B-Parameter,I-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,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,O