Presence Network Architecture

Description

The Presence Network Architecture (PNA) is the 3GPP-specified framework for the presence service, a core enabler for rich communication. Presence information is dynamic data that describes the communication status of a presentity (e.g., a user or a service). This includes availability (online/offline), communication means (voice, video, messaging), willingness to communicate, current activity, and location (if permitted). The PNA defines the logical entities, reference points, and procedures for collecting, processing, storing, and distributing this information to authorized consumers, known as watchers.

The architecture is fundamentally client-server based and heavily integrated with the IP Multimedia Subsystem (IMS). Key functional entities include the Presence Server (PS), which is the central repository and processing engine for presence information. It receives publication updates from Presence User Agents (PUAs) associated with the presentity's devices or services. The PS authenticates publications, applies subscription authorization policies, and generates composite presence views by aggregating data from multiple PUAs. It then notifies subscribed watchers (via their Presence User Agents) of any changes. The Resource List Server (RLS) is an optimization entity that allows a watcher to subscribe to a list of presentities (a "buddy list") with a single subscription, reducing signaling load.

How it works: A user's device (a PUA) publishes its local status (e.g., "mobile phone, registered, willing to receive voice") to the Presence Server via the IMS core. The PS aggregates this with publications from the user's other devices (laptop, tablet) to create a unified presence state. When another user (a watcher) wants to see this status, their client subscribes to the presentity's presence information. The PS checks authorization rules defined by the presentity and, if permitted, sends a notification containing the current presence document (typically in Presence Information Data Format - PIDF). This entire process uses SIP (Session Initiation Protocol) for signaling, specifically the SIP PUBLISH, SUBSCRIBE, and NOTIFY methods, making it a native IMS application.

Purpose & Motivation

The PNA was developed to standardize and scale the presence service, which was popularized by internet-based instant messaging applications but lacked interoperability and carrier-grade reliability. Proprietary presence systems created walled gardens. 3GPP recognized presence as a fundamental building block for next-generation telecommunication services, essential for enabling intelligent communication choices (e.g., seeing if someone is busy before calling) and for enriching services like voice calls with context.

Its creation addressed the limitations of ad-hoc implementations by providing a robust, secure, and scalable architecture that leverages the IMS control plane. This allowed mobile network operators to offer presence as a standardized, billable service with guaranteed quality and integrated subscriber management. It solved problems of fragmentation, security (through IMS authentication and authorization), and network efficiency (through optimizations like the RLS). The PNA enabled a wide range of services beyond simple chat status, including network address book services with presence, enriched call routing based on callee availability, and integration with multimedia telephony, forming the foundation for Rich Communication Services (RCS).

Key Features

• Centralized Presence Server for aggregation, storage, and distribution of presence data
• Support for multiple Presence User Agents (PUAs) per presentity to aggregate device status
• Resource List Server (RLS) for efficient subscription to presence lists (buddy lists)
• Utilizes SIP (PUBLISH, SUBSCRIBE, NOTIFY) as the core signaling protocol within IMS
• Defines comprehensive authorization policies allowing presentities to control who sees what information
• Standardized presence data model using formats like PIDF (Presence Information Data Format) and RPID (Rich Presence Information Data)

Evolution Across Releases

Defining Specifications