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.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-4, normative work from Rel-15.
In Release 15, the enhancement for the Incoming Calls Barred (ICB) function specifically involved the handling of unwanted calls within a Closed User Group (CUG). This was addressed by introducing a new profile status in the proxy role to manage such scenarios. The change was aligned with the broader initiative to define a SIP response code for rejecting unwanted calls.
- Added the profile status in proxy role regarding “A SIP Response Code for Unwanted Calls” TS 29.165CR0919
Explore further
Broader topics and technologies where ICB plays a role.
Defining Specifications
3GPP specifications that define or reference ICB, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 22.173 vk00 | IMS Multimedia Telephony Service Definition | Rel-20 |
| TS 22.273 v1700 | IMS Multimedia Telephony with PSTN/ISDN Simulation | Rel-7 |
| TS 23.085 vj00 | Closed User Group (CUG) Supplementary Service Stage 2 | Rel-19 |
| TS 24.196 vj00 | Enhanced Calling Name (eCNAM) Stage 3 Protocol | Rel-19 |
| TS 24.407 v830 | OIP and OIR Simulation Services Protocol | Rel-8 |
| TS 24.411 v1830 | ACR and CB Service Protocol Specification | Rel-8 |
| TS 24.454 v840 | Closed User Group (CUG) Protocol Specification | Rel-8 |
| TS 24.607 vj10 | OIP and OIR Supplementary Services Stage 3 | Rel-19 |
| TS 24.611 vj00 | Anonymous Communication Rejection & Barring | Rel-19 |
| TS 24.654 vj00 | Closed User Group (CUG) supplementary service | Rel-19 |
| TS 29.165 vj10 | Inter-IMS Network to Network Interface (NNI) | Rel-19 |
| TS 29.292 vj00 | IMS Centralized Services (ICS) Interworking | Rel-19 |
| TS 29.364 vj10 | IMS AS Service Data Descriptions | Rel-19 |
| TS 29.864 v801 | Application Server Service Data Definition for IMS Telephony | Rel-8 |
| TS 32.275 vj00 | MMTel Charging Specification | Rel-19 |