Trigger Detection Point

Description

The Trigger Detection Point (TDP) is a core architectural element of the Intelligent Network (IN) and Customised Applications for Mobile network Enhanced Logic (CAMEL) standards. It represents a precise, standardized location within the finite state machine that models a call or session (e.g., the Basic Call State Model, BCSM). At a TDP, the network's Service Switching Function (SSF) can be configured to suspend normal call/session processing and interact with an external Service Control Function (SCF) that hosts the service logic. This interaction allows the SCF to influence how the call or session proceeds.

Technically, a TDP is defined by its type and the point in processing where it occurs. Types include TDP-R (Request), where detection occurs and a request is sent to the SCF before further processing, and TDP-N (Notification), where the SSF notifies the SCF of an event but does not necessarily wait for instructions. Key TDPs in a call model include Collected_Info (after digits are collected), Analyzed_Information (after number analysis), and Route_Select_Failure (if routing fails). When a call reaches an armed TDP, the SSF packages relevant call data into a standardized message (like an InitialDP in CAP) and sends it to the designated SCF. The SCF then executes its service logic and returns instructions (e.g., Continue, Connect, Release) to the SSF to resume processing.

In the network architecture, TDPs are the glue between the switching layer and the service intelligence layer. The SSF, often integrated within an MSC or GMSC, contains the call state model and monitors for armed TDPs. Arming can be static (pre-provisioned in the subscriber's profile, like in a CAMEL Subscription Information, CSI) or dynamic (instructed by the SCF during a prior interaction). This mechanism allows for a clear separation of service control from basic switching, enabling the creation and deployment of services independently of the switch vendor and without modifying every switch in the network.

Purpose & Motivation

The TDP was created to solve the fundamental problem of inflexibility in traditional telephony networks. In pre-IN networks, new services required lengthy, expensive, and proprietary software upgrades to every telephone switch. This stifled innovation and made deploying features like freephone (800) numbers or complex call routing a massive undertaking. The Intelligent Network architecture, with TDPs as a cornerstone, introduced a revolutionary separation of service logic from switching functionality.

Its purpose is to provide a standardized 'hook' or interception point within call processing. This allows an external, centralized service control point to influence calls in real-time. The historical context is the evolution from switch-based features to network-based services in the 1990s. TDPs enabled the rise of a vast market for value-added services, most notably prepaid cellular service, which was economically unviable without real-time credit control mediated through TDPs like Collected_Info. They addressed the limitations of monolithic switch software by defining a stable, abstract interface (the TDP) where service interactions could occur, future-proofing the network against new service demands.

Key Features

• Standardized point in a call/session state model for service interaction
• Defines types such as TDP-R (Request) and TDP-N (Notification)
• Enables arming statically (from subscriber data) or dynamically (from SCF)
• Triggers the suspension of call processing and invocation of service logic
• Facilitates the exchange of call data and control instructions between SSF and SCF
• Core enabler for CAMEL, IMS Service Control, and other IN-based services

Evolution Across Releases

Defining Specifications