Description
Outgoing Calls Barred (OCB) is a supplementary service defined within the 3GPP framework, operating as a specific restriction within the broader Closed User Group (CUG) service. A CUG is a subscription option that defines a group of subscribers who are permitted to communicate only amongst themselves, creating a logical private network over the public mobile infrastructure. The OCB feature is a specific barring condition applied to a CUG member, which prohibits that member from initiating (i.e., making) calls to destinations outside the boundaries of their assigned CUG. The enforcement of this barring is managed by the core network, specifically within the Home Location Register (HLR) or Home Subscriber Server (HSS) and the Mobile Switching Center (MSC) or Call Session Control Function (CSCF). When a subscriber with an active OCB restriction attempts to place a call, the originating MSC or CSCF queries the subscriber's profile from the HLR/HSS. Upon identifying the OCB flag and verifying that the dialed number is not a member of the subscriber's permitted CUG(s), the network rejects the call setup request, typically returning a tone or announcement to the caller. The service is highly configurable per subscriber, allowing network operators to define multiple CUGs with different barring characteristics, including combinations with Incoming Calls Barred (ICB) and other CUG interlock codes. This architecture ensures that service logic and subscriber data are centralized in the home network, allowing for consistent application of barring rules even when the subscriber is roaming. OCB is a fundamental tool for implementing controlled communication environments, directly impacting call control, billing (by preventing chargeable calls to external numbers), and service differentiation.
Purpose & Motivation
The primary purpose of OCB is to provide a mechanism for creating controlled, private communication groups within a public mobile network. It solves the problem of uncontrolled communication costs and unauthorized external calls for specific subscriber groups, such as employees within a company, members of a government agency, or devices in a machine-to-machine (M2M) fleet. Before such features were standardized, organizations had to rely on physical private networks or basic barring services that lacked the granularity of group-based logic. The creation of CUG services with OCB and ICB options was motivated by commercial demands from enterprise customers who required the cost control and privacy of a Private Branch Exchange (PBX) but with the mobility and coverage of a public cellular network. It allows operators to offer value-added services that cater to business segments, generating additional revenue streams beyond individual consumer plans. Historically, this concept originated in fixed-line telephony and was adapted into GSM and subsequent 3GPP systems, becoming a cornerstone of intelligent network (IN) based supplementary services. It addresses the limitation of simple barring (like barring all outgoing calls) by providing a more sophisticated, group-aware restriction that still permits essential internal communication.
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 OCB (Outgoing Calls Barred within the CUG) function was enhanced by adding the profile status in proxy role. This addition was made in relation to defining a SIP response code for unwanted calls, providing a more specific handling mechanism within the communication session.
- 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 OCB plays a role.
Defining Specifications
3GPP specifications that define or reference OCB, 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.173 vj00 | Multimedia Telephony Service and Supplementary Services in IMS | Rel-19 |
| TS 24.404 v1700 | Communication Diversion Services (CDIV) | Rel-7 |
| TS 24.411 v1830 | ACR and CB Service Protocol Specification | Rel-8 |
| TS 24.429 v1700 | Explicit Communication Transfer (ECT) Service Specification | Rel-7 |
| TS 24.454 v840 | Closed User Group (CUG) Protocol Specification | Rel-8 |
| TS 24.504 v8m0 | Communication Diversion Services Stage 3 | Rel-8 |
| TS 24.529 v820 | Explicit Communication Transfer (ECT) Simulation Service | Rel-8 |
| TS 24.604 vj00 | Communications Diversion (CDIV) Protocol Spec | Rel-19 |
| TS 24.611 vj00 | Anonymous Communication Rejection & Barring | Rel-19 |
| TS 24.629 vj00 | Explicit Communication Transfer (ECT) Protocol | 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 |
| TS 32.850 ve00 | IMS Charging Correlation Methods Study | Rel-14 |
| TR 38.805 ve00 | Study on New Radio Access Technology; 60 GHz unlicensed spectrum | Rel-14 |
| TS 38.807 vg10 | NR beyond 52.6 GHz Study | Rel-16 |
| TR 38.808 vh00 | Study on NR above 52.6 GHz to 71 GHz | Rel-17 |
| TR 38.889 vg00 | NR-based access to unlicensed spectrum study | Rel-16 |