Presence User Agent

Description

The Presence User Agent (PUA) is a fundamental component within the 3GPP Presence service framework, standardized across multiple technical specifications including TS 23.141, 24.141, 24.841, and 25.470. It acts as the source of presence information for a Presentity (the entity whose presence is being reported). The PUA is responsible for collecting, generating, and ultimately publishing the presence state of a user or service to the network. This state can include a wide range of dynamic information such as registration status (e.g., online/offline), communication willingness (e.g., available for voice, busy), current activity, location (if permitted), and terminal capabilities.

Architecturally, the PUA is a logical function that can be implemented in various physical locations. It most commonly resides within the User Equipment (UE), such as a smartphone client application. However, it can also be located in a network-based entity, like an application server, that acts on behalf of a user or service. The PUA does not communicate directly with watchers (entities requesting presence information). Instead, it interfaces with a Presence Network Agent (PNA) or, in more advanced IMS-based architectures, with a Presence Server (PS) via the Ut reference point using protocols like SIP PUBLISH.

The PUA's operation involves a continuous cycle of information gathering, processing, and publication. It monitors relevant data sources (e.g., device power state, calendar integration, manual user input), applies local policy and privacy rules, formats the data into a presence document (often using PIDF/RPID formats), and sends updates to the network whenever a significant change in state occurs. This enables rich, real-time communication services by allowing other users and services to make informed decisions about initiating contact based on the current context of the Presentity.

Purpose & Motivation

The PUA was created to enable rich presence services in mobile networks, moving beyond simple binary online/offline indicators. Its development was motivated by the convergence of cellular networks with internet-based communication and the rise of instant messaging. The PUA solves the problem of how to dynamically capture and disseminate a user's complex, multi-faceted context (availability, mood, location, device status) to authorized parties in a standardized way.

Prior to such standardized presence architectures, services relied on proprietary, siloed presence mechanisms or had no dynamic availability information at all. The PUA, as part of the 3GPP Presence service, provided a unified model for collecting this data from various sources on a device or in the network. It addressed the limitations of earlier, static methods by enabling automated, policy-controlled publication of real-time context, which is essential for enhancing user experience in services like enriched address books, intelligent call routing, and context-aware messaging.

Key Features

• Sources and generates presence information for a Presentity
• Can reside in User Equipment or in a network-based application server
• Publishes presence data to the network using SIP PUBLISH or other defined methods
• Applies local privacy and policy rules before publication
• Supports a rich set of presence attributes (activity, mood, service availability, location)
• Integrates with device sensors and applications to automate status updates

Evolution Across Releases

Defining Specifications