TIF-CSI

Translation Information Flag for Camel Subscription Information

Core Network
Introduced in Rel-4
TIF-CSI is a CAMEL service indicator flag used in GSM/UMTS networks to signal whether translation information for a called party number is required for Intelligent Network (IN) service triggering. It ensures accurate service logic execution by indicating if number portability or other translation data is needed before invoking CAMEL services.

Description

The Translation Information Flag for Camel Subscription Information (TIF-CSI) is a specific parameter within the CAMEL Subscription Information (CSI) data set stored in the Home Location Register (HLR). CAMEL (Customised Applications for Mobile network Enhanced Logic) is the 3GPP standard for Intelligent Network (IN) services in GSM and UMTS, enabling operator-specific services like prepaid, call screening, and VPNs. TIF-CSI functions as a boolean flag associated with a subscriber's CAMEL service profile. When set, it instructs the Visited Mobile Switching Center (VMSC) or Gateway MSC (GMSC) that translation information—such as that obtained from a Number Portability Database (NPDB) or other numbering analysis—must be retrieved for the called party number before any CAMEL service logic, like Initial DP (Detection Point) triggering, is invoked. This ensures the service logic receives the correct, potentially ported or translated, destination number for accurate processing.

The architectural role of TIF-CSI is critical in the call setup and service invocation chain. When a mobile-originated or mobile-terminated call occurs, the MSC interrogates the HLR for the subscriber's CSI. If TIF-CSI is present and set, the MSC is mandated to perform a translation query, often via an SS7 signaling interface to an SCP or dedicated database, to resolve the called number. This translation step typically handles scenarios like Mobile Number Portability (MNP), where the dialed number may no longer be associated with its original network or routing prefix. Only after obtaining this translated routing number (the Mobile Station Roaming Number, MSRN, for mobile-terminated calls, or the final routed number) does the MSC proceed to trigger the CAMEL service by sending an Initial DP message to the CAMEL Service Environment (CSE) or Service Control Point (SCP), including the translated number as a parameter.

Key components interacting with TIF-CSI include the HLR (which stores it), the MSC or GMSC (which interprets it and acts upon it), and external translation databases or SCPs. Its operation is defined within the CAMEL Application Part (CAP) signaling procedures. The flag's presence prevents incorrect service execution; for instance, a prepaid service might incorrectly calculate tariffs based on an untranslated, potentially non-routable number. By ensuring translation occurs first, TIF-CSI maintains the integrity of IN service logic, supports regulatory requirements like number portability, and enables complex call routing scenarios. It is a foundational element for ensuring that CAMEL-based services work correctly in modern, interoperable networks where number translation is common.

Purpose & Motivation

TIF-CSI was introduced to address a critical gap in early CAMEL implementations: the need to integrate Intelligent Network service triggering with network-based number translation, primarily driven by the advent of Mobile Number Portability (MNP). Before its introduction, CAMEL service logic would trigger based on the dialed digits as received from the calling party. However, with MNP, the dialed number might no longer correspond to its original network routing information. Triggering a service like prepaid charging or call forwarding based on an untranslated number could lead to incorrect service behavior, failed call routing, or billing errors. TIF-CSI provides a standardized mechanism to force number translation to occur as a mandatory step prior to CAMEL invocation, ensuring service logic uses accurate, routable destination information.

The creation of TIF-CSI was motivated by regulatory and competitive pressures mandating number portability, which required networks to modify call handling procedures. Without a flag like TIF-CSI, operators would have needed proprietary, non-interoperable solutions or would risk CAMEL services malfunctioning in ported-number scenarios. By standardizing this flag in 3GPP Release 4, it ensured consistent behavior across different vendors' MSCs and HLRs, facilitating seamless roaming and service interoperability. It solved the problem of sequencing—ensuring translation (a network routing function) logically precedes service logic execution (an application-layer function). This separation of concerns is fundamental to robust IN architecture.

Furthermore, TIF-CSI supports more than just MNP; it can be used for any service requiring number translation, such as freephone number translation, carrier selection, or national numbering plan changes. Its purpose extends to future-proofing CAMEL services against evolving numbering schemes. By decoupling the translation requirement from the specific service logic, it allows network operators to introduce new translation databases or rules without modifying every CAMEL service application on the SCP. Thus, TIF-CSI is a key enabler for flexible, reliable, and regulation-compliant Intelligent Network services in 2G and 3G ecosystems.

Key Features

  • Boolean indicator within CAMEL Subscription Information (CSI) stored in the HLR
  • Mandates number translation (e.g., via MNP query) before CAMEL Initial DP triggering
  • Ensures CAMEL service logic receives correct, routable destination number
  • Critical support for regulatory Mobile Number Portability (MNP) requirements
  • Prevents billing errors and service malfunctions for ported numbers
  • Enables separation of translation functions from service logic execution

Evolution Across Releases

Rel-4 Initial

TIF-CSI was introduced as a new parameter within the CAMEL Subscription Information data structures. The initial architecture defined its storage in the HLR and its interpretation by the MSC/GMSC, mandating a translation query for the called party number before any CAMEL service triggering could proceed, specifically to support Mobile Number Portability scenarios.

Defining Specifications

SpecificationTitle
TS 23.078 3GPP TS 23.078