Anonymous Communications Rejection

Description

Anonymous Communications Rejection (ACR) is a standardized supplementary service defined within the 3GPP framework, primarily for Circuit-Switched (CS) and IP Multimedia Subsystem (IMS) based networks. It operates as a network-based feature, typically provisioned and managed by the service provider on behalf of the subscriber. The core function of ACR is to intercept incoming communication attempts—such as voice calls or, in IMS, potentially other session types—and analyze the calling party's identification information. The key parameter is the presentation status of the Calling Line Identity (CLI), also known as Calling Party Number. If the incoming request is flagged with a presentation indicator signifying 'anonymous', 'withheld', or 'restricted', the ACR service logic is triggered. The network then prevents the call from completing to the called user's terminal, typically returning a specific tone, announcement, or SIP response code (e.g., 403 Forbidden) to the caller, indicating the call has been rejected due to anonymity.

Architecturally, for CS networks, ACR service logic resides within the Mobile Switching Center (MSC) or the Visitor Location Register (VLR) serving the subscriber. The MSC/VLR checks the subscriber's service profile, which includes the ACR subscription status, against the presentation indicator in the incoming call setup message (e.g., an ISUP Initial Address Message). For IMS networks, the service logic is implemented within the Serving-Call Session Control Function (S-CSCF) by applying initial Filter Criteria (iFC) that route the incoming SIP INVITE request to an Application Server (AS) hosting the ACR service. The AS evaluates the SIP P-Asserted-Identity header or the 'From' header with privacy settings to determine if the identity is presented. The service decision (allow or reject) is then enforced by the S-CSCF.

The service is highly configurable. Subscribers can typically activate or deactivate ACR via network-based management, such as Unstructured Supplementary Service Data (USSD) codes or through a customer portal. Some implementations may allow for more granular control, such as creating an exception list (a 'white list') of specific anonymous numbers that are permitted to connect. The service interacts closely with other supplementary services like Calling Line Identification Presentation (CLIP) and Calling Line Identification Restriction (CLIR). ACR essentially provides the inverse logic of CLIP; while CLIP allows the called party to see the number, ACR allows them to block calls when that number is not presented. Its role is fundamental to user-centric privacy and control in telecommunications, acting as a gatekeeper that enforces the called party's preference to only engage with identifiable callers.

Purpose & Motivation

The primary purpose of ACR is to empower network subscribers with control over their communications and enhance their privacy. Before such services were standardized, users receiving calls from anonymous parties had no network-assisted means to filter them out; they had to answer the call or let it go to voicemaill to determine the caller, potentially leading to harassment, spam, or unwanted telemarketing. ACR solves this by providing an automated, network-enforced barrier. It addresses the social and privacy concerns arising from the very capability of calling line identification restriction (CLIR), which allows callers to withhold their number. While CLIR is a legitimate privacy tool for callers, ACR balances the ecosystem by giving the called party an equivalent right to reject such anonymous interactions.

Historically, the development of ACR in 3GPP Release 7 was part of a broader maturation of supplementary services for GSM and UMTS, extending them into the emerging IMS architecture. It formalized a service that had existed in various proprietary forms in fixed-line networks and early mobile networks. Standardization ensured interoperability across different network operators and equipment vendors, allowing subscribers to reliably use the service even when roaming. It addressed the limitation of purely terminal-based solutions (like phone-side blocklists), which could be bypassed or were not universally available. By being a network-centric service, ACR provides consistent behavior regardless of the user's handset type or capabilities, and the rejection happens before the call rings the terminal, conserving battery and avoiding disturbance.