Description
A Closed User Group (CUG) is a service feature defined within 3GPP standards that enables the creation of a private communication community within a public mobile network. It operates by defining a specific group of subscribers who are permitted to communicate with each other, while interactions with users outside the group are either prohibited or subject to specific restrictions and controls. The CUG functionality is implemented through network-based mechanisms that involve subscription data stored in the Home Location Register (HLR) or Home Subscriber Server (HSS), which contains CUG membership information and associated privileges for each subscriber.
From a technical perspective, the CUG service relies on several key components within the network architecture. The core network elements, particularly the HLR/HSS, maintain CUG subscription data including group identifiers, member lists, and access rights. When a subscriber attempts to initiate a call or session, the Mobile Switching Center (MSC) or Call Session Control Function (CSCF) queries the HLR/HSS to verify whether the destination subscriber belongs to the same CUG as the originating subscriber. This verification process determines whether the call should be allowed, rejected, or subjected to specific handling procedures such as routing through dedicated gateways or applying special charging rates.
The implementation of CUG involves multiple protocol interactions across different network interfaces. During call setup, the MSC or CSCF exchanges signaling messages with the HLR/HSS to retrieve CUG information through protocols like MAP (Mobile Application Part) or Diameter. The network applies CUG restrictions based on predefined rules that may include complete prohibition of outgoing calls to non-members, restrictions on incoming calls from outsiders, or special handling for inter-CUG communications when a subscriber belongs to multiple groups. Charging systems are also integrated with CUG functionality to apply differentiated billing for intra-group and extra-group communications, supporting various business models for group services.
CUG plays a significant role in enabling specialized communication services within public networks. It allows mobile operators to offer tailored solutions for corporate customers, government agencies, emergency services, and other organizations requiring controlled communication environments. By leveraging the existing public network infrastructure, CUG provides a cost-effective alternative to dedicated private networks while maintaining security and access control through standardized 3GPP mechanisms. The service supports various configurations including hierarchical CUG structures, overlapping membership across multiple groups, and differentiated privileges within a single group, making it adaptable to diverse organizational communication needs.
Purpose & Motivation
The Closed User Group (CUG) feature was developed to address the need for controlled communication environments within public mobile networks. Before its implementation, organizations requiring private communication capabilities had to establish separate dedicated networks, which involved significant infrastructure costs, maintenance overhead, and limited flexibility. CUG enables these organizations to leverage existing public network infrastructure while maintaining security, access control, and communication privacy through standardized mechanisms defined in 3GPP specifications.
CUG solves several practical problems in telecommunications service delivery. It allows mobile operators to offer value-added services to corporate and government customers without requiring separate network infrastructure. By defining clear boundaries between group members and non-members, CUG ensures that sensitive communications remain within authorized circles while still allowing necessary interactions with external parties under controlled conditions. This balance between isolation and connectivity makes CUG particularly valuable for organizations that need both internal privacy and selective external access, such as emergency services coordinating with public agencies or corporate departments communicating with suppliers while maintaining internal confidentiality.
The creation of CUG was motivated by the growing demand for specialized communication services in the late 1990s and early 2000s, as mobile networks expanded beyond individual consumers to serve organizational needs. 3GPP standardized CUG to ensure interoperability across different operators' networks and equipment vendors, allowing organizations to maintain consistent communication policies across multiple regions and service providers. This standardization also enabled the development of advanced features like inter-CUG communication rules, hierarchical group structures, and integrated charging mechanisms, making CUG a comprehensive solution for managed communication communities within public mobile networks.
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.
In Release 15, the Closed User Group (CUG) function was newly extended to operate using the IP Multimedia (IM) Core Network (CN) subsystem. This introduction allows for the establishment of closed groups with a pre-defined set of members within the IMS framework. The enhancement leverages the existing core network to provide this restricted group communication service.
- Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem TS 24.654CR0029
Explore further
Broader topics and technologies where CUG plays a role.
Defining Specifications
3GPP specifications that define or reference CUG, 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 |
| TR 22.976 v1200 | Release 2000 Services Overview | Rel-2 |
| TS 23.018 vj00 | Basic call handling in 3GPP CS domain | Rel-19 |
| TS 23.085 vj00 | Closed User Group (CUG) Supplementary Service Stage 2 | Rel-19 |
| TS 23.259 vj00 | Personal Network Management (PNM) Procedures | Rel-19 |
| TS 24.186 vj60 | IMS Data Channel applications | Rel-19 |
| TS 24.196 vj00 | Enhanced Calling Name (eCNAM) Stage 3 Protocol | Rel-19 |
| TS 24.259 vj00 | Personal Network Management (PNM) Protocol Details | Rel-19 |
| TS 24.447 v800 | Advice Of Charge (AOC) Service Protocol | Rel-8 |
| TS 24.454 v840 | Closed User Group (CUG) Protocol Specification | Rel-8 |
| TS 24.654 vj00 | Closed User Group (CUG) supplementary service | 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.808 v1800 | Common User Profile Storage Framework | Rel-8 |
| TS 32.850 ve00 | IMS Charging Correlation Methods Study | Rel-14 |