North American GSM Number Portability

Description

North American GSM Number Portability (NAGNP) is a specific implementation of number portability tailored for GSM-based networks in the North American region (primarily the United States and Canada). It operates on the fundamental principle of separating a subscriber's telephone number (the Directory Number) from their network location and service provider. When a number is ported, calls to that number must be routed to the new network instead of the original one.

The technical implementation involves a centralized Number Portability Database (NPDB), often administered by a neutral third party. When a Mobile Switching Center (MSC) or a Gateway MSC (GMSC) receives a call setup request for a mobile number, it must determine if the number has been ported. This is done via a database query. In the NAGNP model, the query is typically triggered at the originating network's switch. The switch analyzes the dialed number (specifically the Numbering Plan Area, or NPA-NXX) to decide if a query is necessary based on a local table of portable number ranges.

If a query is required, the MSC/GMSC formulates a signaling message, such as an ANSI-41 Location Request (LOCREQ) or a SIP-based query, and sends it to the NPDB via a Signal Transfer Point (STP) or directly over an IP network. The NPDB contains records mapping ported numbers to their current serving network identifiers, like the Location Routing Number (LRN). The LRN is a unique 10-digit number that uniquely identifies the switch currently serving the ported subscriber. The database returns this LRN to the querying switch.

The originating switch then uses this LRN, instead of the dialed directory number, to route the call through the Public Switched Telephone Network (PSTN) or the mobile network. The call is delivered to the correct MSC in the recipient's new network. This process is largely transparent to the end-users. The architecture also includes mechanisms for supporting SMS and other services for ported numbers, requiring similar database lookups by SMSCs or other network elements.

Purpose & Motivation

NAGNP was created to fulfill regulatory mandates in North America that required wireless local number portability (WLNP). Prior to its implementation, a subscriber's mobile number was permanently tied to their original service provider. Switching providers meant changing phone numbers, a significant inconvenience that acted as a barrier to competition by locking customers in (a phenomenon known as 'customer inertia').

The problem NAGNP solves is the technical challenge of decoupling a telephone number—a fundamental routing address in the PSTN and mobile networks—from a specific physical switch or network provider. Older routing schemes assumed a number's prefix (NPA-NXX) directly indicated the serving carrier and switch. Portability breaks this assumption, requiring an additional lookup step to find the current network location.

3GPP standardized NAGNP to ensure interoperability between different vendors' equipment and different operators' networks within the North American region, which uses ANSI-41 (later evolved to 3GPP2 standards) core network signaling alongside GSM radio access. The specification provided a common framework for queries, responses (using the Location Routing Number concept), and procedures, preventing fragmentation and ensuring a consistent user experience for portability across all GSM/UMTS operators in the market. It addressed the limitations of proprietary or non-standard solutions that would have hindered seamless operation.

Key Features

• Defines the use of a centralized Number Portability Database (NPDB) for storing porting records
• Specifies the Location Routing Number (LRN) as the key routing identifier for a ported subscriber's switch
• Supports query mechanisms at call origination (All Call Query - ACQ method) for efficient routing
• Integrates with ANSI-41 (IS-41) and evolving 3GPP2 core network signaling protocols
• Enables portability for voice calls, SMS, and other supplementary services
• Provides procedures for updating the NPDB when a subscriber ports their number

Evolution Across Releases

Defining Specifications