Service Key

Description

The Service Key (SK) is a fundamental parameter within the 3GPP CAMEL (Customised Applications for Mobile network Enhanced Logic) Intelligent Network (IN) architecture. It is an integer value that acts as a unique identifier for a specific service logic program residing on a Service Control Point (SCP). When a call or session controlled by CAMEL is initiated, the subscriber's Home Location Register (HLR) provides a set of CAMEL Subscription Information (CSI) to the serving network node (like an MSC or SGSN). This CSI includes the address of the appropriate SCP and the Service Key.

The operational flow begins when a trigger detection point is encountered in the network switch (the Service Switching Function, or SSF). The SSF formulates an initial CAMEL Application Part (CAP) message, such as InitialDP, to the SCP. This CAP message carries the Service Key as a mandatory parameter. Upon receiving the message, the SCP uses the Service Key to determine exactly which service logic program or application to execute for that particular call or session. For example, a Service Key value of '10' might map to a prepaid charging service, while '20' might map to a virtual private network (VPN) service.

This mechanism allows a single SCP to host multiple, distinct services for potentially millions of subscribers. The network switch (SSF) does not need to understand the service logic; it only needs to know when to trigger the SCP and pass the relevant data, including the SK. The SCP, using the SK, selects the correct program to perform real-time rating, routing decisions, or other advanced service control. The Service Key is therefore the essential link between a generic trigger event in the network and the execution of a specific, subscriber-tailored intelligent network service.

Purpose & Motivation

The Service Key was created to enable the flexible and efficient deployment of Intelligent Network (IN) services in GSM and, later, 3G/4G networks via the CAMEL standard. Before CAMEL, advanced services were typically hard-coded into network switches (MSCs), making them difficult to create, modify, or personalize. This vendor- and switch-specific approach was slow, costly, and hindered service portability and innovation.

The Service Key solves the problem of service identification and selection in a distributed IN architecture. It allows a centralized Service Control Point (SCP) – which is separate from the switching hardware – to host numerous different service applications. When a trigger occurs, the switch simply informs the SCP *that* a service is needed, and provides the SK to indicate *which* service. This decouples service logic from switching functionality, enabling operators to rapidly introduce new value-added services (like prepaid, freephone, or call screening) without upgrading every MSC in the network. It provided the essential mechanism for personalized, real-time control of calls and sessions, forming the backbone of the revenue-generating service layer for mobile operators for many years.