Suppress Outgoing Access (CUG SS)

Description

Suppress Outgoing Access (SOA) is a specific capability within the Closed User Group (CUG) Supplementary Service framework standardized by 3GPP. A CUG is a service that provides a group of subscribers with the ability to communicate among themselves, often with specific privileges or restrictions compared to the general public network. SOA is one of the key restrictions that can be applied to a member of a CUG. When SOA is active for a subscriber within a particular CUG, the subscriber is barred from originating calls (or sometimes other communication sessions) to destinations that are not part of that same CUG. The enforcement of this barring is performed by the core network, typically within the Mobile Switching Center (MSC) or Call Session Control Function (CSCF), depending on the network generation (circuit-switched or IMS-based).

The operation of SOA is tied to the subscriber's service profile, which is stored in the Home Location Register (HLR) or Home Subscriber Server (HSS). When a subscriber attempts to originate a call, the serving network node retrieves the CUG information, including any outgoing access restrictions like SOA, as part of the call setup procedure. The node then analyzes the called party number against the list of permitted CUG interconnections or the public network. If the called party is not within a permitted group and SOA is active, the call setup is rejected. The service logic can be complex, as a subscriber may belong to multiple CUGs with different SOA settings, and precedence rules defined in the standards determine which restriction applies.

SOA is a fundamental tool for creating private virtual networks within the public mobile infrastructure. It allows network operators and enterprises to define clear communication boundaries. For example, a company can define a CUG for its employees with SOA enabled, ensuring that company-provided mobile phones cannot be used for personal calls, thereby controlling costs and enforcing usage policies. The management of SOA, including its activation, deactivation, and interrogation, is performed through standardized supplementary service control procedures, often initiated by the subscriber via USSD codes or managed by the network operator.

Purpose & Motivation

SOA was created to meet the demand for controlled communication services within the broader CUG feature set. Enterprises and organizations required the ability to provide mobile services to employees or members with restrictions that mimic a private branch exchange (PBX) or a private network. The primary problem SOA solves is cost control and policy enforcement by preventing unauthorized outgoing calls to external, potentially expensive, destinations such as international numbers or premium-rate services.

Historically, before such standardized supplementary services, similar restrictions required proprietary solutions or physical modifications to handsets, which were not scalable. The standardization of CUG and SOA within 3GPP allowed for a uniform, network-centric approach to call barring that could be provisioned remotely and managed efficiently. It addressed the limitation of basic call barring services, which were often all-or-nothing, by providing a more granular, group-based restriction mechanism. SOA, combined with other CUG features like incoming access restrictions, enables the creation of sophisticated virtual private network offerings for mobile operators.

Key Features

• Network-enforced barring of outgoing calls to destinations outside the subscriber's Closed User Group.
• Integral part of the standardized CUG Supplementary Service (SS) framework.
• Subscriber-specific provisioning stored in HLR/HSS.
• Call control enforcement at the MSC or CSCF during call origination.
• Support for complex scenarios with multiple CUG memberships and precedence rules.
• Remote management via standardized supplementary service control procedures.

Evolution Across Releases

Defining Specifications