Positioning Calculation Application Part

Description

The Positioning Calculation Application Part (PCAP) is a critical protocol defined within the 3GPP UTRAN architecture, specifically designed to support positioning services. It operates as an application part, facilitating communication between the Serving Mobile Location Center (SMLC) and the Radio Network Controller (RNC). The primary function of PCAP is to transport positioning-related information, measurement data, and calculation requests to enable accurate location determination of User Equipment (UE). This protocol is essential for implementing standardized positioning methods like Enhanced Observed Time Difference (E-OTD) and Observed Time Difference Of Arrival (OTDOA), which rely on timing measurements from multiple base stations.

Architecturally, PCAP messages are carried over the Iupc interface, which connects the SMLC and the RNC. The SMLC acts as the positioning server, responsible for calculating the UE's location based on measurements provided by the UE and/or the network. The RNC, on the other hand, manages the radio resources and can coordinate positioning measurements from Node Bs. PCAP defines procedures for initiating positioning, transferring measurement data (such as timing advance, signal strength, or observed time differences), and delivering the calculated location result. It supports both UE-assisted and UE-based positioning methods, offering flexibility depending on UE capabilities and network deployment.

Key components of the PCAP protocol include various message types for positioning control and data transfer. These include messages for positioning initiation, measurement request and reporting, abort procedures, and error handling. The protocol ensures reliable delivery of positioning data, which is crucial for services requiring high accuracy, such as emergency calls (E911), location-based services, and lawful interception. PCAP's role is integral to the Location Services (LCS) architecture in 3GPP, providing a standardized mechanism for network-based positioning that is independent of the underlying radio access technology, although initially defined for UMTS.

In operation, when a location request is triggered (e.g., by an emergency call or a commercial LBS application), the SMLC uses PCAP to request the RNC to initiate positioning procedures. The RNC may then instruct the UE and/or Node Bs to perform specific measurements. The collected measurement data is sent back to the SMLC via PCAP messages. The SMLC processes this data using positioning algorithms to compute the geographical coordinates of the UE. PCAP also supports capabilities exchange, allowing the SMLC and RNC to negotiate supported positioning methods and accuracy levels. This ensures interoperability between different vendor equipment and enables scalable deployment of location services across the network.

Purpose & Motivation

PCAP was created to standardize the signaling interface for positioning services in 3GPP networks, specifically within the UMTS UTRAN. Prior to its introduction, proprietary solutions or non-standardized interfaces could have been used for location determination, leading to interoperability issues between network elements from different vendors. The need for a standardized protocol became critical with regulatory requirements for emergency caller location (e.g., E112 in Europe) and the growing market for commercial location-based services (LBS). PCAP provided a unified way for the SMLC and RNC to communicate, enabling consistent and reliable positioning capabilities across multi-vendor networks.

The protocol addresses the problem of efficiently and accurately determining a mobile subscriber's location using network-based methods. It solves the challenge of coordinating timing measurements between the UE, multiple Node Bs, and the positioning calculation entity. By defining clear procedures and message formats, PCAP reduces complexity in implementing positioning features and ensures that location data can be delivered with the required latency and accuracy for various applications. Its creation was motivated by the 3GPP's goal to enable a robust LCS architecture as part of the core network services from Release 5 onwards, supporting both circuit-switched and packet-switched domains.

Furthermore, PCAP facilitated the evolution of positioning technologies within 3GPP. While initial releases focused on methods like E-OTD and OTDOA, the standardized interface allowed for the incorporation of more advanced techniques in later releases, such as Assisted-GNSS (A-GNSS), without requiring fundamental changes to the signaling protocol. This extensibility ensured that PCAP remained relevant as positioning accuracy requirements increased and new use cases emerged, including navigation, fleet management, and location-aware content delivery. It laid the groundwork for integrated positioning support in subsequent 4G and 5G systems, although the specific protocols evolved (e.g., to LPPa in LTE).

Key Features

• Standardized signaling between SMLC and RNC over the Iupc interface
• Support for multiple positioning methods including E-OTD and OTDOA
• Procedures for both UE-assisted and UE-based positioning modes
• Reliable transfer of positioning measurement data and calculation results
• Capabilities negotiation to ensure interoperability between network elements
• Error handling and abort procedures for robust operation

Evolution Across Releases

Defining Specifications