North American Numbering Plan

Description

The North American Numbering Plan (NANP) is a comprehensive, integrated telephone numbering system administered by the North American Numbering Plan Administrator (NANPA). In the context of 3GPP, it is not a network element but a critical external numbering plan that the mobile network must recognize, interpret, and process correctly. The NANP defines a standard 10-digit format for telephone numbers, structured as a 3-digit Numbering Plan Area (NPA) code (often called an area code), a 3-digit Central Office (NXX) code, and a 4-digit station number (XXXX). This format is embedded within the international E.164 number by prefixing it with the country code '1' (e.g., +1-212-555-1234).

3GPP networks integrate support for the NANP at multiple layers. In the core network, specifically in the Home Location Register (HLR), Home Subscriber Server (HSS), and call session control functions, numbering analysis is performed. When a Mobile Originated (MO) call or SMS is processed, the network analyzes the dialed digits. If the number matches NANP patterns (starting with '+1'), it is treated according to specific routing rules defined for the NANP region. This includes understanding special NPA codes like toll-free (800, 888, etc.), premium rate, or emergency (911) codes. For Mobile Terminated (MT) calls, the network must correctly route incoming international calls destined for NANP numbers through the appropriate gateways and inter-operator interfaces.

The handling involves several protocol elements. In signaling protocols like ISUP (ISDN User Part) and SIP (Session Initiation Protocol), the NANP number is carried in specific fields. The network must also manage number portability within the NANP region, where a subscriber can keep their number when changing service providers or locations. This requires queries to Number Portability databases (like the LNPA in the US). Furthermore, for services like SMS and MMS, the NANP format must be correctly presented and stored in the device's phonebook and on the SMSC/MMSC. 3GPP specifications ensure that devices and network elements across the globe can uniformly process these numbers, enabling seamless global interoperability for subscribers in and communicating with the NANP region.

Purpose & Motivation

The NANP was created long before cellular networks to bring order and efficiency to the expanding telephone network in North America. Its primary purpose was to automate long-distance dialing and manage the exhaustion of telephone numbers in a structured way. For 3GPP, the purpose of specifying and supporting NANP is to ensure that global mobile networks can interoperate correctly with the fixed and mobile networks in the NANP region, which represents a major economic and communications zone.

Without explicit support, a European or Asian mobile network might misinterpret a NANP number (like +1-202-555-0123) due to its unique structure and the shared country code '1' for multiple nations. This could lead to misrouted calls, failed SMS delivery, or incorrect billing. 3GPP standards integrate the NANP rules to solve these interoperability problems. They define how to parse the 10-digit NANP format from the E.164 number, how to apply national-specific routing for calls within the '+1' country code, and how to handle region-specific services like 911 emergency calling or 800 toll-free numbers. This support is crucial for enabling roaming, both for NANP-region subscribers traveling abroad and for international visitors roaming within North America, ensuring their devices and the visited networks understand local number formats.

Key Features

• Defines 10-digit number format (NPA-NXX-XXXX) for North America
• Uses a unified country code '+1' for multiple countries/territories
• Includes special service codes (e.g., 911 for emergency, 800 for toll-free)
• Requires network support for Number Portability within the plan
• Integrated into 3GPP call control, SMS, and subscriber data management
• Essential for correct routing and billing of inter-regional calls and messages

Evolution Across Releases

Defining Specifications