name: PRC
full_form: Pseudorange Correction
context: TTI, the set of valid TFCs shall be established. All TFCs in the set of valid TFCs shall: 1. belong to the TFCS. 2. not be in the Blocked state. 3. be compatible with the RLC configuration. 4. not require RLC to produce padding PDUs 5. not carry more bits than can be transmitted in a TTI (e.g. when compressed mode by higher layer scheduling is used and the presence of compressed frames reduces the number of bits that can be transmitted in a TTI using the Minimum SF configured). The UE may remove from the set of valid TFCs, TFCs in Excess-power state in order to maintain the quality of service for sensitive applications (e.g. speech). Additionally, if compressed frames are present within the longest configured TTI to which the next transmission belongs, the UE may remove TFCs from the set of valid TFCs in order to account for the higher power requirements. The chosen TFC shall be selected from within the set of valid TFCs and shall satisfy the following criteria in the order in which
description: Pseudorange Correction (PRC) refers to a parameter used in the context of DGPS Corrections, which involves reporting corrections when the PRC has drifted from its previously reported value beyond a certain threshold or when there is a change in the IODE. This parameter plays a crucial role in ensuring accurate location information within telecommunications networks.
explanation: The classification of PRC as a Parameter stems from its description within the context, where it is mentioned alongside other parameters such as 'DGPS Corrections' and 'IODE'. The text highlights conditions under which the RNC2 initiates the Information Reporting procedure based on changes or thresholds related to these parameters. This indicates that PRC serves as a specific value or setting used in the operation of DGPS corrections.
section_title: 8.5.6.2	Successful Operation
biotag_Context: 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-Protocol,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,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,B-Parameter,O,O,O,B-Parameter,O,O,B-Device,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-Parameter,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,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
biotag_Description: B-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,B-Technology,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,O,O,O,O