Incoming Calls Barred (within the CUG)

Description

Incoming Calls Barred (ICB) is a supplementary service defined within the 3GPP framework, specifically operating in conjunction with the Closed User Group (CUG) service. It functions as a call control mechanism that prevents a subscriber who is a member of a CUG from receiving incoming calls originating from numbers outside that predefined group. The service is provisioned and managed by the network operator, typically within the Home Location Register (HLR) or Home Subscriber Server (HSS) as part of the subscriber's service profile. When a call is attempted to a subscriber with ICB active, the originating MSC or call session control function queries the subscriber's data. If the calling party is not a member of the same CUG, the call is barred, and the caller may receive an announcement or tone indicating the restriction.

The architectural implementation involves the core network nodes responsible for call control and subscriber data management. For circuit-switched domains, the Mobile Switching Center (MSC) interacts with the HLR to verify CUG membership and ICB status during call setup. In the IP Multimedia Subsystem (IMS), the Serving-Call Session Control Function (S-CSCF) applies initial filter criteria that may trigger service logic, often via an Application Server (AS), to enforce the barring based on the subscriber's profile fetched from the HSS. The service logic compares the calling party's identity (e.g., MSISDN) against the list of authorized CUG members associated with the called party.

Key components include the subscriber's CUG subscription data, which contains the CUG index and associated interlock code, and the ICB indicator within that data. The network uses this information to perform a membership check. The service is integral to providing tailored communication services for enterprises, government agencies, or any organization requiring controlled access. It ensures that communication remains within a trusted circle, enhancing security and operational focus by eliminating unsolicited or external interruptions, thereby supporting specialized service offerings beyond standard public telephony.

Purpose & Motivation

ICB was created to address the need for controlled and private communication within specific user groups, a requirement prominent in business and organizational contexts. Prior to such services, mobile networks primarily offered public, unrestricted calling, which was insufficient for entities needing to enforce internal-only communication for security, cost control, or operational efficiency. The Closed User Group concept itself was developed to emulate private branch exchange (PBX) functionality on public mobile networks, and ICB serves as a critical component to enforce the 'closed' nature by restricting inbound access.

The service solves the problem of unwanted external calls disrupting group activities or compromising confidentiality. For example, a company could deploy mobile phones for field staff that should only receive calls from colleagues or headquarters, not from personal contacts or external clients via that number. This limitation of previous approaches—where all incoming calls were permitted unless individually blocked—required a group-based, manageable solution. ICB, as part of the CUG suite, provided a standardized, network-centric mechanism to implement such policies efficiently across large subscriber bases, facilitating the adoption of mobile services for corporate customers and driving network operator revenue through value-added services.

Key Features

• Restricts incoming calls to only those originating from within the same Closed User Group
• Network-enforced barring applied during call setup based on subscriber profile
• Integrates with HLR/HSS for subscriber data management and service authorization
• Supports both circuit-switched and IMS-based call control architectures
• Provides a standardized mechanism for group privacy and controlled communication
• Operates as a supplementary service that can be combined with other CUG features like outgoing access

Evolution Across Releases

Defining Specifications