Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

PCAP

Positioning Calculation Application Part

Services →

PCAP is the protocol in UTRAN that enables positioning services by facilitating communication between the Serving Mobile Location Center and the Radio Network Controller.

Introduced
Rel-5
Where
Radio Access Network › UTRAN (3G)
Specifications
5 specs
PCAP Description Purpose What changed Family Neighbours Detected Changes Specifications

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).

What changed in its specifications

The latest release-to-release comparison of specifications that define PCAP. Each summary describes the whole specification, not only this term.

TS 25.305Rel-11 → Rel-12

Rel-12 added support for BeiDou Navigation Satellite System (BDS) for UTRA and LTE, including a network-assisted positioning method, a normative reference to BDS ICD, and a definition for BDS.

Full comparison in TS 25.305 →
TS 25.450Rel-6 → Rel-7

SAS Centric position services management, GANSS related data management, new definitions, specification notation tags for 7.68 Mcps TDD, updates to TDD applicability declarations.

Full comparison in TS 25.450 →

Technology family

Location services architecture · Services

  1. R98 BSSAP-LE, BSSLAP, GMLC, LMU, RRLP, SMLC
  2. Rel-5 PCAP, SAS
  3. Rel-6 PPR, R-GMLC
  4. Rel-7 LRF, SUPL
  5. Rel-9 E-SMLC, LCS-AP, LPP, LPPa
  6. Rel-15 LMF, NRPPa
  7. Rel-18 LCS-UPP, RSPP, SLPP

Also in this family (introduction release not pinned to a single defining specification): H-GMLC, LMC, MLP, V-GMLC

  • PCAP used together with SAS
    “the SAS shall not send a new PCAP Position Activation Request message until the SRNC has responded to a previous request or the SAS has timed out on a response.” TS 25.305

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 6 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-5 introduced

PCAP is specified for the first time in Rel-5 as the Iupc protocol between the RNC and the Stand-alone A-GPS SMLC (SAS), with its procedures, services and signalling transport.

  • “The present document specifies the Positioning Calculation Application Part (PCAP) between the Radio Network Controller (RNC) and the Stand-alone A-GPS SMLC (SAS).” TS 25.453 v5.12.0
  • “The signalling between RNC and SAS is done by using PCAP procedures specified in [27].” TS 25.305 v5.9.0
  • “The PCAP Position Calculation message flow illustrates how an SRNC invokes an SAS to calculate a position estimate of a UE.” TS 25.305 v5.9.0
Rel-7 specification text

PCAP procedures were extended in Rel-7: new Position Activation Request/Response and Position Initiation Request messages enable SAS-centric positioning method selection, and Position Calculation Request now supports U-TDOA and periodic location information.

  • “The SAS may initiate a specific positioning method by sending a PCAP Position Activation Request message to the SRNC” TS 25.305 v7.4.0
  • “The PCAP Position Calculation Request message may contain periodic location information (reporting interval and number of outstanding requests for the overall periodic location procedure)” TS 25.305 v7.4.0
  • “the SRNC shall terminate all activity for the previous request, including sending any response to the SAS, and shall process the new request.” TS 25.305 v7.4.0
Rel-8 specification text

PCAP in Rel-8 gained support for additional navigation satellite systems, replacing the earlier GANSS introduction wording in the positioning protocol.

  • “Support for additional navigation satellite systems in PCAP” TS 25.453 v8.3.0
Rel-9 specification text

PCAP in TS 25.453 gained a technical addition: a DGNSS Validity Period was added to PCAP, alongside reference-format updates in the related specifications.

Rel-10 specification text

SAS-centric PCAP Position Activation Request/Response now also covers Enhanced Cell ID based positioning, returning Enhanced Cell ID measurements instead of only Cell ID and RTT.

  • “the request for a Cell ID or Enhanced Cell ID based position may be originated by an associated SAS via a PCAP Postion Activation Request” TS 25.305 v10.0.0
  • “the SAS may continue to invoke Cell ID or Enhanced Cell ID based position via PCAP Position Activation Request messages” TS 25.305 v10.0.0
Rel-13 specification text

PCAP-based SAS/SRNC positioning procedures over Iupc were extended so PCAP Position Activation Request and related messages now support Barometric Pressure, WLAN, Bluetooth and TBS positioning methods.

  • “the SRNC shall allow A-GNSS, OTDOA, Cell ID, U-TDOA, WLAN, Bluetooth, Barometric Pressure and TBS positioning events to be originated by the SAS via PCAP messages” TS 25.305 v13.0.0
  • “the SAS initiates a WLAN positioning procedure by sending a PCAP: Position Activation Request message that allows for the use of WLAN positioning” TS 25.305 v13.0.0
  • “RAT-Independent positioning enhancements for PCAP” TS 25.453 v13.1.0

Defining Specifications

3GPP specifications that define or reference PCAP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 25.305 vj00 UTRAN UE Positioning Stage 2 Rel-19 read
TS 25.450 vj00 Iupc Interface Introduction for UTRAN Positioning Rel-19 read
TS 25.452 vj00 Iupc Interface Signalling Transport for PCAP Rel-19 read
TS 25.453 vj00 PCAP Protocol Specification Rel-19 read
TS 37.857 vd10 Indoor Positioning Enhancements for UTRA and LTE Rel-13 read