Private Automatic Branch eXchange

Description

Within the 3GPP architecture, a Private Automatic Branch eXchange (PABX) is not a 3GPP-defined network function per se, but rather a referenced external customer premises equipment (CPE) entity. It represents a legacy or contemporary on-premises telephony switch that serves a private organization, such as a business, government office, or campus. The 3GPP specifications define how the public mobile network, specifically the Core Network (CN), interfaces with and provides services to such PABX systems. This is primarily governed through the concept of a PABX subscription, where the PABX is treated as a single subscriber with multiple associated telephone numbers (e.g., a block of MSISDNs).

Architecturally, the PABX connects to the mobile core network via standardized interfaces. Historically, this could be via a circuit-switched interconnection (e.g., using ISDN Primary Rate Interface - PRI - over E1/T1 lines) to the Mobile Switching Center (MSC). In modern IP-based deployments, the connection may utilize SIP trunks towards the IP Multimedia Subsystem (IMS). The PABX contains its own internal switching matrix, call control logic, and typically supports features like hold, transfer, conference calling, and a private numbering plan (extension dialing). From the mobile network's perspective, the PABX appears as a single subscriber entity, but with the capability to route incoming calls to specific internal extensions based on the dialed MSISDN.

Its role in the 3GPP ecosystem is to facilitate enterprise communication services. Key specifications like TS 29.007 (General requirements on interworking between the Public Land Mobile Network and other networks) detail the signaling interworking requirements for connecting a PLMN to a PABX, covering aspects like call setup, number translation, and supplementary service handling. TS 21.905 includes it in the vocabulary of terms. The network provides the PABX with a trunk group or a range of public numbers, and manages mobility for any associated mobile extensions (e.g., via PBX mobility solutions). This integration allows employees to have a unified identity (e.g., a single business number that rings on both desk phone and mobile).

Purpose & Motivation

The PABX concept exists to extend the reach and features of the public telephone network into private organizational domains. It solves the problem of efficient internal communication and external call management for businesses without requiring a separate, publicly-switched line for every employee. By acting as a private switch, it allows for short-number dialing between extensions, centralized call routing, and cost control.

In the context of 3GPP standardization, the explicit referencing of PABX addresses the critical need for interworking between public mobile networks and established private telephony infrastructure. This was especially important during the 2G/3G era when corporate communications heavily relied on legacy PABX systems. 3GPP standards had to define how mobile-originated calls could terminate at a PABX extension, and how calls from the public network (PSTN) destined for a specific person within a company could be routed via the mobile network to that person's mobile handset, treating the PABX as an intermediary or logical group. This interworking solved the limitation of mobile networks being purely 'public' and enabled sophisticated corporate telephony features, laying the groundwork for later Fixed Mobile Convergence (FMC) and Unified Communications (UC) solutions.