Description
Generic Number (GN) is a parameter defined in 3GPP signaling protocols, most notably within the Customised Applications for Mobile network Enhanced Logic (CAMEL) framework and the IP Multimedia Subsystem (IMS). It is a versatile data structure used to carry addressing information in a generic, type-agnostic format. The GN parameter can encapsulate different types of numbers, such as Mobile Station International Subscriber Directory Number (MSISDN), service numbers, or other identifiers, along with attributes that specify the number's nature, presentation restrictions, and screening characteristics. This flexibility allows service control functions to process and route calls or sessions based on dynamic number information without being tightly coupled to a specific numbering plan.
Architecturally, the GN is transported within signaling messages, such as Initial Detection Point (IDP) in CAMEL or within SIP messages in IMS. It consists of several sub-fields: the Numbering Plan Indicator, which identifies the numbering scheme (e.g., E.164, private); the Type of Number, which indicates the number's format (e.g., international, national); the Number Digits themselves; and Presentation and Screening indicators, which control whether the number can be presented to the called party and how it should be screened. This structured format allows the receiving network node, like a Service Control Point (SCP) or an Application Server (AS), to interpret the number correctly and apply appropriate service logic.
In operation, when a trigger condition is met (e.g., a mobile-originated call), the visited Mobile Switching Center (MSC) or Call Session Control Function (CSCF) includes a GN parameter in the signaling message sent to the service platform. The service logic, residing on the SCP or AS, analyzes the GN—along with other parameters—to make routing decisions, apply charging rules, or invoke value-added services like number translation or prepaid call control. For instance, in a prepaid roaming scenario, the GN can carry the caller's MSISDN to the home network's charging system. The generic nature of GN means the same parameter structure can be reused across different services and network generations, promoting interoperability.
The role of GN is critical for enabling intelligent network (IN) services and IMS-based services in a standardized manner. By abstracting the specifics of the number into a well-defined container, 3GPP specifications (like TS 29.163 for interworking between IMS and CS networks) ensure that service logic remains portable and network evolution (e.g., from CS to IMS) does not break existing service implementations. It decouples service execution from the underlying transport and numbering details, which is essential for the seamless operation of complex services like virtual private networks, freephone numbers, and mobility management across heterogeneous networks.
Purpose & Motivation
The Generic Number (GN) parameter was created to solve the problem of transporting diverse and variable addressing information within telecommunications signaling protocols in a standardized, flexible manner. Early intelligent network (IN) architectures required a way to pass caller/callee numbers and other identifiers between network switches and service control points, but different services and regions used different number formats and attributes. GN provides a universal container that can carry any type of number, along with metadata about its presentation and screening, thus enabling reusable service logic independent of the specific numbering context.
Historically, before the standardization of parameters like GN, service implementations were often proprietary and tightly integrated with switch vendors' specific signaling extensions. This made service deployment complex, expensive, and hindered interoperability, especially in multi-vendor networks and international roaming scenarios. The introduction of GN in CAMEL (from 3GPP Rel-99 onwards, with Rel-8 refining its use in EPS) provided a common language for number transport. It allowed network operators to deploy services like prepaid, number portability, and toll-free calling consistently across their networks and in partnership with other operators.
Furthermore, GN addresses the evolution towards all-IP networks and IMS. As services migrated from circuit-switched CAMEL to IMS-based SIP signaling, there was a need to carry the same rich set of number information. GN, specified in protocols like SIP for IMS (e.g., in TS 29.163), ensures continuity of service logic. It solves the problem of interworking between legacy CS networks and IMS, allowing service platforms to receive a familiar GN parameter whether the call originates from a traditional phone or an IMS client. This backward compatibility and forward-looking design motivate its continued relevance in modern 3GPP architectures.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (5 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-8, normative work from Rel-15.
In Release 15, a correction was introduced for the interworking of the Redirecting Number within the Generic Number (GN) function. This specifically addressed the mapping procedures between SIP components, like the P-Asserted-Identity header, and ISUP/BICC parameters to ensure proper handling of E.164 and non-E.164 number formats. The update clarified network options for setting address signals and the Nature of Address indicator based on the received number format and operator policy.
- Correction of the Interworking of the Redirecting Number TS 29.163CR1042
In Release 16, the GN function was enhanced to explicitly support the interworking of local number formats, including their mapping with the `phone-context` parameter in SIP or tel URIs to the appropriate Nature of Address indicator in ISUP. Furthermore, procedures were updated for setting the P-Asserted-Identity header when a calling party number is unavailable and for mapping the SIP History-Info header to the ISUP Original Called Number parameter.
- Interworking of Local Number Format in Generic Number TS 29.163CR1070
- Interworking of Local Number Format in From Header Field TS 29.163CR1072
- Modification on the setting of P-Asserted-Identity header field when a calling party number is not available. TS 29.163CR1058
- Mapping of History-Info header field to ISUP Original called number TS 29.163CR1069
Explore further
Broader topics and technologies where GN plays a role.
Defining Specifications
3GPP specifications that define or reference GN, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 29.163 vj00 | Interworking between 3GPP IM CN and CS networks | Rel-19 |