Point In Association

Description

Point In Association (PIA) is a concept within the 3GPP core network architecture, primarily associated with Customized Applications for Mobile network Enhanced Logic (CAMEL) and service control protocols. It represents a logical point or stage in the association between network entities, such as between a Service Control Point (SCP) and a Mobile Switching Center (MSC), where specific service logic can be invoked. The PIA defines the exact moment or condition during a call or session setup, modification, or release when CAMEL triggers or other service-related actions occur, allowing for precise control over service execution. This mechanism is crucial for implementing advanced telephony services like prepaid billing, call forwarding, and number translation in a standardized manner across different network operators and regions.

Architecturally, PIA is implemented within the CAMEL Application Part (CAP) protocol, which operates over Signaling System No. 7 (SS7) or IP-based signaling. It involves key components such as the gsmSCF (Service Control Function), which contains the service logic, and the gsmSSF (Service Switching Function) in the MSC or GMSC, which detects points in call and triggers actions based on PIA definitions. The PIA is specified in 3GPP TS 23.078 and related documents, detailing various points like DP (Detection Point) types—e.g., DP Collected_Info or DP Route_Select_Failure—that correspond to specific stages in call processing. When a call reaches a defined PIA, the gsmSSF sends a notification to the gsmSCF, which can then influence the call flow by sending instructions back, such as connecting to a specific number or applying charging.

How PIA works involves a sequence of detection points and triggers configured in the network. For example, during a mobile-originated call, the MSC may encounter a PIA like DP Collected_Info after collecting dialed digits, prompting a CAMEL query to a prepaid server for credit check. The server responds with continue or apply charging commands, dictating whether the call proceeds. This enables real-time service interaction without modifying basic call switching functions. PIA's role extends beyond voice to data services in later releases, supporting GPRS and IMS environments, where it helps manage data sessions, QoS, and value-added services through standardized interfaces, ensuring interoperability and flexible service deployment in evolving core networks.

Purpose & Motivation

Point In Association was created to address the need for flexible, operator-specific service logic in mobile networks without requiring changes to standard call control protocols. Before CAMEL and PIA, implementing custom services like prepaid or virtual private networks often involved proprietary extensions to switches, leading to interoperability issues and high costs. Introduced in 3GPP R99, PIA provided a standardized way to define interaction points where external service control could be injected, solving the problem of rigid network architectures and enabling rapid service innovation across multi-vendor environments.

Historically, as GSM networks expanded globally, operators sought to differentiate through value-added services while maintaining compatibility. PIA, as part of CAMEL, allowed service logic to reside in separate nodes (SCPs), decoupling service creation from core switching functions. This addressed limitations of earlier IN (Intelligent Network) approaches by specifying precise points in call associations, ensuring reliable triggering and reducing service deployment complexity. It facilitated the growth of prepaid mobile services in the late 1990s and 2000s, which relied on real-time charging and control points defined by PIA.

In later releases, PIA evolved to support packet-switched domains and IMS, extending its purpose to data and multimedia services. It solved challenges in integrating legacy IN with IP-based networks, enabling seamless service continuity. Without PIA, networks would lack a standardized mechanism for third-party service integration, hindering the development of advanced mobile applications and personalized user experiences in the era of digital services.

Key Features

• Defines logical points for service logic invocation in call/session flow
• Integrates with CAMEL Application Part (CAP) protocol
• Supports various Detection Point (DP) types for precise triggering
• Enables real-time service control like prepaid charging and call routing
• Facilitates interoperability between network elements from different vendors
• Extensible to packet-switched and IMS domains in later releases

Evolution Across Releases

Defining Specifications