LRN

Location Routing Number

Identifier
Introduced in Rel-8
A unique number used in North American telecommunications to route calls to a specific geographic location or ported number. It enables number portability by separating the dialed number from the actual routing address, ensuring calls reach the correct service provider's network.

Description

The Location Routing Number (LRN) is a critical identifier within the North American Numbering Plan (NANP) ecosystem, standardized by 3GPP to support Local Number Portability (LNP). It is a 10-digit number, structurally identical to a standard telephone number, that uniquely identifies a specific switch or network point of interconnection (POI) within a carrier's network. When a subscriber ports their telephone number from one service provider to another, the dialed Directory Number (DN) remains the same for the caller, but the underlying routing must change to direct the call to the new carrier's network. The LRN serves as this new routing address.

Architecturally, LRN functionality is integrated into the core network, primarily within signaling systems like Signaling System 7 (SS7) and its IP-based successors (e.g., SIGTRAN). When a call is placed to a ported number, the originating carrier's switch performs a query to a centralized Number Portability Database (NPDB), often via the Number Portability Query (NPQ) service. This query uses the dialed DN as the key. The NPDB returns the corresponding LRN for that DN, which identifies the recipient carrier's switch that now hosts the subscriber. The originating switch then uses this LRN, instead of the dialed DN, as the routing address within the Initial Address Message (IAM) to set up the call through the Public Switched Telephone Network (PSTN) or IP-based interconnects.

Its role extends beyond simple call routing. The LRN is essential for billing and settlement between carriers, as it accurately identifies the network terminating the call. In 3GPP specifications, particularly the 32-series on charging and management, the LRN is a key parameter for accounting records (e.g., Call Detail Records or Charging Data Records). It ensures that revenue is correctly assigned when calls traverse multiple networks. Furthermore, the LRN mechanism supports various portability types, including wireline-to-wireless, wireless-to-wireline, and intra-carrier porting, providing a flexible and scalable solution for a competitive telecommunications market.

Purpose & Motivation

The LRN was created to solve the fundamental challenge introduced by Local Number Portability (LNP): allowing subscribers to retain their telephone numbers when changing service providers without disrupting the call routing infrastructure of the PSTN. Before LNP, telephone numbers were intrinsically tied to a specific carrier's switch and a geographic rate center. The number itself contained the NPA-NXX prefix that identified the serving switch, making routing straightforward. However, this rigid system became a barrier to competition, as customers were reluctant to switch providers and lose their established phone number.

LNP mandated by regulatory bodies broke this direct link, creating a problem: how to route a call to a number that no longer resides on its originally assigned switch? The LRN provides the solution by introducing an indirect routing layer. It decouples the dialable subscriber identifier (the Directory Number) from the network routing address. This allows the dialed number to remain constant for end-users while the network uses a separate, carrier-assigned identifier (the LRN) to physically route the call to the correct destination switch. This innovation preserved the simplicity of the user dialing experience and the efficiency of the existing SS7 routing hierarchy while enabling full number mobility.

The adoption of LRN was motivated by the need for a standardized, interoperable, and efficient method to implement LNP across all North American carriers. It addressed the limitations of alternative, more complex routing schemes that could have required massive changes to switch translations or introduced significant latency. By leveraging existing database query mechanisms, the LRN solution allowed for a relatively graceful integration of portability into legacy networks, forming the backbone for a competitive telecommunications landscape.

Key Features

  • A 10-digit numeric identifier conforming to the NANP format
  • Uniquely identifies a specific switching entity or point of interconnection
  • Enables call routing for ported telephone numbers independent of the dialed DN
  • Retrieved via queries to a centralized Number Portability Database (NPDB)
  • Used as the routing address in SS7/SIGTRAN Initial Address Messages (IAM)
  • Critical parameter for inter-carrier billing and settlement records

Evolution Across Releases

Rel-8 Initial

Introduced the Location Routing Number (LRN) concept into 3GPP standards to support North American Local Number Portability (LNP) requirements. Specified its role as a key routing identifier for ported numbers, defining its structure and its use within charging and management systems (specs 32.250, 32.272). Established the framework for LRN-based call routing and accounting in inter-operator scenarios.

Enhanced charging specifications to further clarify the handling of LRN in Charging Data Records (CDRs) for inter-operator settlements. Ensured consistency in LRN reporting across different network interfaces and service scenarios.

Maintained and refined LRN definitions as part of ongoing charging architecture evolution. No major functional changes specific to LRN were introduced in this release.

Continued support for LRN within updated management and charging frameworks. Specifications were updated for alignment with broader architectural developments.

LRN support persisted without significant modification, ensuring backward compatibility for North American LNP requirements in evolving networks.

No specific evolution for LRN documented. The concept remained stable as a mature solution for number portability routing.

LRN definitions and usage were maintained within the relevant charging and management specifications. No new capabilities were added.

As part of the 5G system standardization, existing support for legacy interworking, including LRN-based routing for interconnects with traditional PSTN/IMS networks, was ensured.

Continued inclusion of LRN parameters in specifications to support legacy interconnect and charging scenarios, particularly for 5G networks interfacing with North American fixed and mobile networks.

Maintained LRN support. Focus was on other areas of network evolution; LRN remained a stable, region-specific identifier.

LRN specifications were upheld without change, ensuring operational continuity for number portability in applicable regions.

The Location Routing Number remains a supported identifier within 3GPP standards for charging and management related to North American number portability, with no functional updates in this release.

Defining Specifications

SpecificationTitle
TS 32.250 3GPP TR 32.250
TS 32.272 3GPP TR 32.272
TS 32.293 3GPP TR 32.293