Spending Status Notification Request

Description

The Spending Status Notification Request, abbreviated as SN-Request, is a specific operation within the CAMEL (Customised Applications for Mobile network Enhanced Logic) protocol suite, which is a 3GPP standard for intelligent network (IN) services in GSM, UMTS, and later networks. CAMEL allows network operators to deploy custom services like prepaid charging, number translation, and call screening. The SN-Request is a message sent from the network's Service Control Point (SCP) – which hosts the prepaid service logic – to the Service Switching Point (SSP), typically the Mobile Switching Center (MSC) or Gateway MSC. Its purpose is to instruct the SSP to monitor a subscriber's call or session and send a notification back to the SCP when the subscriber's account balance reaches certain predefined thresholds during the communication.

How it works is integral to real-time prepaid charging. When a prepaid subscriber initiates a call, the MSC/SSP detects the CAMEL-triggered call and suspends call processing. It sends an InitialDP message to the SCP. The SCP, after checking the subscriber's balance and rating the call, authorizes the call for an initial duration. Crucially, the SCP can include an SN-Request in its response (e.g., in a RequestReportBCSMEvent or ApplyCharging operation). This request contains parameters like the spending limit thresholds (e.g., notify when 50% of the allocated credit is used, and again at 80%). As the call progresses, the MSC/SSP monitors the call duration or data volume. When a specified threshold is crossed, the SSP sends a notification (an EventReportBCSM or ApplyChargingReport) back to the SCP.

Upon receiving the notification, the SCP can then take further action. This typically involves re-checking the subscriber's balance, calculating a new credit allocation for the next segment of the call, and sending a new authorization to the SSP to continue the call. This process of periodic notification and re-authorization continues until the call ends or the credit is exhausted. The SN-Request mechanism is key to implementing features like low-balance warnings, where the network can play an announcement to the subscriber, or graceful call termination when funds run out. It ensures that prepaid charging is accurate, real-time, and allows for interactive subscriber notifications.

Purpose & Motivation

The SN-Request was developed to address the fundamental challenge of real-time control and notification in prepaid telephony services. Before CAMEL and mechanisms like SN-Request, prepaid services were often implemented through less efficient means, such as call gapping or simple duration limits without granular control. These methods could lead to subscriber dissatisfaction due to abrupt call termination without warning or inaccurate charging. The SN-Request provides a standardized, in-call signaling mechanism for the charging system (SCP) to stay informed of resource consumption.

It solves the problem of proactive account management during an active session. Without it, the SCP would only know the total cost at the end of the call, risking overspending. With SN-Request, the SCP can monitor spending incrementally, allowing for: 1) **Precise credit control**: Allocating credit in chunks prevents subscribers from exceeding their balance. 2) **Enhanced user experience**: Enabling low-balance announcements gives subscribers a chance to top up or end the call gracefully. 3) **Flexible service logic**: Operators can define multiple thresholds for different notification types or actions. Its creation was motivated by the massive growth of prepaid mobile subscriptions, which demanded robust, scalable, and feature-rich charging systems that could operate across different network elements and vendors, which CAMEL and its detailed operations like SN-Request provided.

Key Features

• A CAMEL operation used for real-time prepaid charging control
• Instructs the MSC/SSP to report when a subscriber's resource usage hits predefined thresholds
• Enables periodic re-authorization of calls or sessions based on remaining credit
• Supports subscriber notifications like low-balance warnings via in-call announcements
• Works in conjunction with CAMEL phases and other operations like ApplyCharging
• Applicable to voice calls, SMS, and data sessions in GSM, UMTS, and evolved packet core contexts

Evolution Across Releases

Defining Specifications