Presence Watcher

Description

In 3GPP's presence service architecture, a Watcher is a fundamental entity that actively seeks presence information about a Presentity (the entity whose presence is being tracked) or watcher information about another Watcher. The presence service, defined in specifications such as TS 22.127 and TS 22.141, enables users to publish, subscribe to, and receive updates about the availability, willingness, and other presence attributes of other users. A Watcher is uniquely identifiable within the system and is always associated with exactly one Principal, which is typically the human user or application on whose behalf the Watcher acts. This principal association ensures accountability and proper authorization for presence subscriptions. Specialized types of Watchers exist to cater to different interaction models: a Fetcher requests presence information on-demand without a persistent subscription; a Poller periodically queries the presence service for updates; and a Subscribed-Watcher establishes a subscription to receive notifications when presence information changes. The Watcher interacts with the presence service through standardized interfaces, typically based on SIP/SIMPLE or other protocols, to send subscription requests and receive notifications. The presence service validates the Watcher's identity and permissions, applying privacy rules to determine what information can be disclosed. The Watcher model is integral to many applications, including instant messaging, VoIP, social networking, and enterprise collaboration, where real-time availability information enhances communication efficiency. The 3GPP presence architecture includes functional entities such as the Presence Server, Watcher Information Template, and Resource List Server, which manage Watcher subscriptions and notification delivery. Security and privacy are paramount, with mechanisms to block Watchers, anonymize presence data, and enforce access control policies based on the Principal's preferences.

Purpose & Motivation

The Watcher concept was created to define a clear, standardized role within presence services, addressing the need for a structured approach to requesting and receiving presence information. Before the introduction of formal presence services in 3GPP, presence-like features were proprietary and lacked interoperability, making it difficult for users to track availability across different networks and applications. The Watcher abstraction enables consistent behavior across implementations, ensuring that any entity requesting presence information adheres to common protocols and privacy rules. It solves the problem of unauthorized or malicious presence tracking by requiring each Watcher to be associated with a Principal and subject to authorization checks. The distinction between different Watcher types (fetcher, poller, subscribed-watcher) allows optimization of network resources and battery life on devices, as on-demand fetches consume less resources than persistent subscriptions. The Watcher also facilitates scalable presence services by allowing watcher information to be queried, enabling users to see who is watching them. This transparency builds trust and enables reciprocal privacy controls. As communication services evolved towards rich, context-aware applications, the Watcher role became essential for delivering timely presence updates that drive features like availability indicators, location sharing, and social presence. The 3GPP standardization ensures global interoperability, enabling operators to offer presence services that work seamlessly across different vendors' equipment and different access technologies.