Description
Originating Call Screening (OCS) is a classic telephony supplementary service standardized by 3GPP for circuit-switched (CS) domains, including GSM and UMTS. It operates as a network-based filtering mechanism applied to call attempts initiated by a subscriber. When a user attempts to place a call, the service logic for OCS is invoked at the originating Mobile Switching Center (MSC) or Visited MSC. The service checks the dialed destination number (the Basic Service Code and the called party number) against a screening list associated with the subscriber's profile. This list is stored in the subscriber's Home Location Register (HLR) and downloaded to the serving MSC/VLR during registration or call setup.
The screening logic is typically based on patterns or specific numbers. For example, a list may contain entries like specific country codes (e.g., blocking all international calls), specific area codes, or exact phone numbers (e.g., blocking calls to a particular premium-rate service). If a match is found between the dialed number and a restricted entry in the screening list, the MSC interrupts the call setup procedure. The user is then typically notified by a specific announcement or tone that the call is barred. The service can be provisioned with different levels of granularity, such as screening for all calls, only for certain bearer services (e.g., data calls), or only when roaming.
Architecturally, OCS relies on the integration between the MSC, the VLR, and the HLR. The HLR holds the subscriber's service profile, including the OCS data. During call origination, the MSC retrieves this data from the VLR (which got it from the HLR) and executes the screening logic. OCS is a prime example of an originating CAMEL (Customised Applications for Mobile network Enhanced Logic) service or a native MAP (Mobile Application Part) based supplementary service. Its role is to provide administrative control, security, and cost containment. It is widely used in corporate environments to prevent unauthorized use, in prepaid systems as a default barring for certain destinations, and by individual users to avoid accidental calls to expensive numbers.
Purpose & Motivation
OCS was developed to address the need for controlled and secure telephony usage, particularly in the context of mobile networks where call charges can be significant. Before such network-based services, controlling outgoing calls was only possible on the terminal side (if at all) or through manual operator intervention, which was not scalable. The primary problems it solves are cost management, fraud prevention, and policy enforcement.
For businesses providing mobile phones to employees, OCS prevents misuse by barring calls to unauthorized or expensive destinations like international or premium-rate numbers. For network operators, it is a tool to manage risk with prepaid subscribers, by barring high-cost destinations that could lead to unpaid bills. For individual subscribers, it offers a form of parental control or a way to self-impose spending limits. Its creation was motivated by the commercial and operational requirements of the GSM era, where supplementary services became a key differentiator and source of revenue. OCS provided a standardized, network-centric way to implement these controls, ensuring consistent behavior across different networks and for roaming subscribers.
Key Features
- Network-based screening of outgoing call attempts.
- Uses a subscriber-specific screening list stored in the HLR.
- Supports pattern-based screening (e.g., country codes, area codes).
- Can be activated/deactivated by the subscriber or network operator.
- Integrates with CAMEL for prepaid and intelligent network services.
- Provides immediate call barring and user notification upon violation.
Evolution Across Releases
Defined as a core supplementary service for GSM and UMTS circuit-switched networks. Established the basic architecture involving HLR, VLR, and MSC for storing screening lists and executing barring logic during call origination. Supported barring based on basic service and destination number.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 23.003 | 3GPP TS 23.003 |
| TS 23.060 | 3GPP TS 23.060 |
| TS 23.125 | 3GPP TS 23.125 |
| TS 23.203 | 3GPP TS 23.203 |
| TS 23.234 | 3GPP TS 23.234 |
| TS 23.237 | 3GPP TS 23.237 |
| TS 23.401 | 3GPP TS 23.401 |
| TS 23.503 | 3GPP TS 23.503 |
| TS 23.979 | 3GPP TS 23.979 |
| TS 28.849 | 3GPP TS 28.849 |
| TS 29.212 | 3GPP TS 29.212 |
| TS 29.215 | 3GPP TS 29.215 |
| TS 29.219 | 3GPP TS 29.219 |
| TS 29.234 | 3GPP TS 29.234 |
| TS 29.817 | 3GPP TS 29.817 |
| TS 29.890 | 3GPP TS 29.890 |
| TS 32.240 | 3GPP TR 32.240 |
| TS 32.250 | 3GPP TR 32.250 |
| TS 32.251 | 3GPP TR 32.251 |
| TS 32.255 | 3GPP TR 32.255 |
| TS 32.260 | 3GPP TR 32.260 |
| TS 32.270 | 3GPP TR 32.270 |
| TS 32.271 | 3GPP TR 32.271 |
| TS 32.272 | 3GPP TR 32.272 |
| TS 32.273 | 3GPP TR 32.273 |
| TS 32.276 | 3GPP TR 32.276 |
| TS 32.277 | 3GPP TR 32.277 |
| TS 32.278 | 3GPP TR 32.278 |
| TS 32.280 | 3GPP TR 32.280 |
| TS 32.281 | 3GPP TR 32.281 |
| TS 32.293 | 3GPP TR 32.293 |
| TS 32.295 | 3GPP TR 32.295 |
| TS 32.296 | 3GPP TR 32.296 |
| TS 32.297 | 3GPP TR 32.297 |
| TS 32.299 | 3GPP TR 32.299 |
| TS 32.808 | 3GPP TR 32.808 |
| TS 32.825 | 3GPP TR 32.825 |
| TS 32.843 | 3GPP TR 32.843 |
| TS 32.849 | 3GPP TR 32.849 |
| TS 32.850 | 3GPP TR 32.850 |
| TS 32.869 | 3GPP TR 32.869 |