BOC

Bell Operating Company

Other
Introduced in Rel-4
Bell Operating Company (BOC) refers to the local telephone companies created from the breakup of AT&T in 1984. In 3GPP context, it is a legacy term used in early specifications to describe certain service provider entities and their operational domains, particularly for circuit-switched services.

Description

Within the 3GPP specifications, the term Bell Operating Company (BOC) is a historical reference to a specific type of telecommunications service provider. It originates from the regulatory environment in the United States following the 1984 breakup of the AT&T monopoly, which resulted in the creation of multiple independent Regional Bell Operating Companies (RBOCs). In the 3GPP framework, particularly in early releases like Rel-4, the term was used to denote the administrative and operational domain of such a local exchange carrier. This domain was relevant for defining service boundaries, billing relationships, and interconnection points for traditional telephony services that were being integrated into or interfaced with early mobile networks.

The technical role of a BOC in the 3GPP architecture primarily pertained to the circuit-switched core network, specifically the Mobile Switching Center (MSC) and its interaction with the Public Switched Telephone Network (PSTN). A BOC represented the PSTN operator to which a mobile subscriber's call might be routed or from which a call might originate. The MSC would handle call control and routing, potentially interacting with BOC switches using signaling protocols like ISUP (ISDN User Part). The specifications referencing BOCs (such as 22.060) used the term to help define service requirements and network scenarios involving fixed-mobile interconnection.

Architecturally, a BOC was an external entity to the 3GPP-defined Public Land Mobile Network (PLMN). It was part of the broader telecommunications ecosystem with which the PLMN needed to interoperate. The interface between the PLMN (via the Gateway MSC or GMSC) and the BOC's network was a critical point for call delivery, number translation, and service feature interaction. While the term itself does not describe a protocol or a network node within 3GPP, it defines a contractual and operational boundary that influenced requirements on numbering, addressing, routing, and charging.

In later 3GPP releases, the explicit use of the term 'Bell Operating Company' diminished as specifications became more generic and internationally focused. The concept evolved into more standardised terms like 'PSTN/ISDN network', 'fixed network', or simply 'external network'. The functional requirements originally associated with BOC interconnection were absorbed into broader specifications for network interworking and roaming, making the specific BOC terminology largely obsolete in technical descriptions of network architecture, though it remains as a historical artifact in some document titles and scopes.

Purpose & Motivation

The inclusion of the term Bell Operating Company in early 3GPP specifications served a specific purpose: to provide a concrete real-world reference point for defining requirements related to fixed-mobile interconnection. During the development of 2G and early 3G systems, a primary use case for mobile telephony was to connect to and from the existing, vast fixed-line telephone network. In the North American context, this network was largely operated by the BOCs. Therefore, specifying requirements for scenarios involving BOCs ensured that the 3GPP system designs could seamlessly interoperate with this dominant segment of the global telecommunications infrastructure.

The term addressed the problem of defining clear service boundaries and administrative responsibilities. It helped specify which network entity (the PLMN or the BOC) was responsible for functions like call routing, charging, and subscriber service provisioning at the point of interconnection. This was crucial for billing settlements, legal intercept, and ensuring quality of service across network borders. Using a well-understood industry term like BOC provided immediate context to engineers designing interfaces and protocols for the Gateway MSC.

Historically, this reflected the transition era where mobile networks were not standalone systems but were extensions of, and needed to integrate deeply with, the incumbent fixed-line networks. The limitations of previous, more proprietary mobile systems were their often narrow or vendor-specific interworking capabilities. By formally referencing entities like BOCs, 3GPP aimed to create standardized, robust interconnection models that would work globally, even if the specific term was regionally derived. As the industry moved towards all-IP core networks and the operational landscape evolved with new types of service providers, the need for this specific legacy term faded, and its purpose was fulfilled by more generic and technology-agnostic network definitions.

Key Features

  • Defined an external PSTN operator domain for interconnection
  • Provided a model for fixed-mobile call routing and service boundaries
  • Influenced requirements for numbering and addressing (E.164 numbers) at network borders
  • Established a context for charging and billing settlements between network operators
  • Served as a reference point for regulatory and service scenarios in early specifications
  • Represented a legacy administrative boundary in telecommunications

Evolution Across Releases

Rel-4 Initial

Introduced as a defined term referencing the legacy Bell Operating Companies. Used in service and stage 1 specifications to describe scenarios and requirements for interconnection between GSM/UMTS mobile networks and the traditional fixed-line telephone network in North America. Established the BOC as an external administrative domain relevant for call delivery and service interworking.

Defining Specifications

SpecificationTitle
TS 21.905 3GPP TS 21.905
TS 22.060 3GPP TS 22.060