name: SPC
full_form: Signalling Point Code
context: If the SAS invokes a positioning method by sending a PCAP Position Activation Request message to the SRNC, it may subsequently receive a PCAP Position Activation Failure or PCAP Abort message from the SRNC, while positioning in the SRNC is active, according to subclause 7.3.1.2. At any time after receiving a PCAP Position Initiation Request message and whether positioning in the SRNC is active or not active, the SAS may receive a PCAP Abort message or PCAP Position Parameter Modification message from the SRNC, according to subclause 7.3.1.2. If the SAS receives a PCAP Abort message it shall immediately cease positioning attempts and return a PCAP Position Initiation Response message to the SRNC carrying any location estimate already obtained or a Position Initiation Failure message containing a cause of failure indication. If the SAS receives a PCAP Postion Activation Failure message, the SAS may either terminate positioning as for receipt of a PCAP Abort or continue the positioning
description: The Signalling Point Code (SPC) is a unique identifier used in Location Services (LCS) architecture, specifically for interworking between control-plane and user-plane positioning methods. It enables the SPC function to retrieve measurements from eNodeB, facilitating consistent positioning methods across different deployments.
explanation: The context highlights the role of SPC as an identifier within the LCS architecture, enabling communication and data exchange between different network components for positioning purposes. This classification is based on its usage in the provided paragraph.
section_title: B.2	SUPL 2.0 and LTE Architecture
biotag_Context: O,O,B-Specification,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Specification,O,O,O,B-Message,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,B-Message,O,O,O,O,O,B-Specification,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O
biotag_Description: O,B-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,B-Service,I-Service,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