name: LCF
full_form: Location Client Function
context: core is not changed at all in carrier sharing deployment. - Stand-alone scenario requires minimal changes or no changes for the current specifications and network elements: - RNC ID in TS 25.413 range extension in RANAP etc, if very large evolved HSPA networks are deployed (refer to 7.4). - Optionally, new HLR parameter "PS only network allowed", if operator offers true PS-only HSPA access (without CS service enabling handover), then "PS only network allowed" parameter in HLR could be useful for roaming cases. TS 22.011, 24.008, 23.060, 21.101, 23.122. - Carrier sharing scenario requires changes for Iur interface, the required changes to specification are FFS.
description: The Location Client Function (LCF) is a network element responsible for understanding and processing location information in a local geographic system. It works in conjunction with the Location Client Coordinate Transformation Function (LCCTF) to convert universal latitude and longitude coordinates into local coordinates that can be used by the LCF.
explanation: The context describes the LCF as an entity that interacts with the LCCTF and processes location information, indicating its role as a functional component within the network. This classification is based on the description of the LCF's responsibilities and interactions within the specified paragraph.
section_title: Location Client Coordinate Transformation Function (LCCTF)
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,B-Network Function,B-Parameter,O,B-Specification,O,O,O,O,B-Protocol,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,B-Mode,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Network Function,I-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,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O