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

Glossary term · Services

Access Rules

Presence Service Access Rules

Services →

Access Rules is a set of constraints that govern how a presence service exposes a presentity's presence information to watchers, managed by the controlling principal to enforce privacy and authorization in presence-enabled services.

Introduced
Rel-5
Where
Services
Specifications
2 specs
Access Rules Description Purpose What changed Neighbours Specifications

Description

Access Rules are a concept defined within the 3GPP presence service architecture, specified in TS 22.127 (Open Service Access) and TS 22.141 (Presence Service). The presence service allows a user, called a presentity, to publish information about their availability, willingness to communicate, location, and other attributes. Other users, called watchers, subscribe to this information. Access Rules define the constraints under which the presence service makes a presentity's presence information available to a given watcher. They are the authorization mechanism that sits between the raw presence data held by the presence server and the watchers who request it.

The architecture of the presence service involves several functional entities. The presentity (or its principal, the entity that owns and controls the presence information) publishes presence information to a presence server. Watchers request presence information either by subscribing to it or by fetching it on demand. Before any presence information is delivered, the presence server evaluates the applicable Access Rules for that presentity against the identity and context of the requesting watcher. If the rules permit, the information is delivered, possibly filtered or partially masked; if not, the request is rejected or the information is withheld.

Access Rules are managed by the principal that controls the presentity's presence information. This means the user (or an authorized administrator acting on the user's behalf) decides who can see what. The rules can be granular: they may distinguish between different watchers, different categories of watchers (for example, friends, colleagues, or unknown parties), different pieces of presence information (for example, availability versus location), and different times or contexts. This granularity is essential because presence information is inherently sensitive and its uncontrolled disclosure can lead to privacy violations, stalking, or unwanted communication.

The concept is closely tied to the broader presence and instant messaging work that 3GPP standardized in the early 2000s, which drew heavily on IETF frameworks such as SIMPLE and XCAP. Access Rules in 3GPP specifications are expressed at the requirements level: they define what the presence service must enforce, while the concrete encoding and protocol for managing the rules is left to the underlying presence enablers. Over successive releases the definition has remained remarkably stable, reflecting the maturity of the concept and its role as a foundational privacy control rather than a feature that evolves with each release.

In practice, Access Rules are one of the primary means by which a presence service balances usefulness against privacy. Without them, a presence service would either have to expose all information to all watchers, which is unacceptable, or expose nothing, which defeats the purpose. Access Rules provide the middle ground: a policy-driven, principal-controlled mechanism that lets presence information flow to exactly the audience the presentity intends, and no further.

Purpose & Motivation

Presence information is among the most privacy-sensitive categories of user data in a telecommunications system. It can reveal whether a person is online, where they are, what device they are using, and whether they are willing to be contacted. Early presence and instant messaging systems often exposed this information with little or no control, leading to spam, unwanted contact, and privacy concerns. Access Rules were created to give the principal controlling a presentity's presence information explicit, enforceable control over who can see what.

The motivation is both technical and regulatory. Technically, a presence server needs a deterministic policy to decide, for each request, whether to release information. Access Rules provide that policy in a form that can be evaluated per watcher and per information element. From a regulatory and user-trust perspective, giving the presentity control over disclosure is a prerequisite for the service to be acceptable to users and compliant with data protection expectations.

Access Rules also solve the problem of scalability of consent. Rather than requiring the presentity to approve each watcher individually in real time, the rules encode the presentity's policy once, and the presence server applies it automatically to every request. This makes presence services practical for large populations of watchers while preserving the presentity's control.

What changed in its specifications

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

TS 22.127Rel-7 → Rel-8

Topology hiding, policy management, service subscription, API accounting, identity management, and content management are the main additions in OSA Rel-8.

Full comparison in TS 22.127 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-5 Initial

Initial definition introduced with the 3GPP presence service: Access Rules are constraints on how the presence service makes presence information available to watchers, managed by the principal controlling the presentity.

Definition carried over unchanged from Rel-5, confirming the stability of the presence access control concept.

The definition text was replaced by a cross-reference ('For the definition see [7].'); the substantive change cannot be assessed from the available wording.

The change cannot be assessed from the available wording; the definition was re-expressed in the specification.

Definition carried over unchanged, restating the constraints on presence information disclosure managed by the controlling principal.

Definition carried over unchanged from the previous release.

Definition carried over unchanged from the previous release.

Definition carried over unchanged from the previous release.

Definition carried over unchanged from the previous release.

Definition carried over unchanged from the previous release.

Definition carried over unchanged from the previous release.

Definition carried over unchanged from the previous release.

Definition carried over unchanged from the previous release.

Definition carried over unchanged from the previous release.

Definition carried over unchanged from the previous release.

Defining Specifications

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

SpecificationTitleRelease
TS 22.127 v900 Open Service Access (OSA) Stage 1 Requirements Rel-9 read
TS 22.141 vj00 Presence Service Requirements Rel-19 read