LAPB

LAPB
Name	LAPB
Full name	Link Access Procedure, Balanced
Type	Data link layer protocol
Developed by	International Organization for Standardization (ISO), CCITT
Initial release	1970s
Related standards	X.25, OSI model, HDLC, SDLC
Status	Historical / legacy

LAPB

LAPB is a byte-oriented link layer protocol specified as part of the X.25 suite and standardized by the International Organization for Standardization and the CCITT. It provides balanced, connection‑oriented frame transfer, error detection, and retransmission services between peer devices over packet switches such as those defined in X.25 or over leased links used by institutions like Bell Labs and national telecommunications carriers. LAPB influenced and interoperated with protocols from IBM and Digital Equipment Corporation that implemented similarly framed link control, and it formed a foundational component in early wide area network deployments with implementations in equipment from vendors such as Siemens, Nokia, and Alcatel.

Overview

LAPB operates at the data link layer of the OSI model and is derived from the bit-oriented HDLC family defined by the ISO. It defines frame formats, sequence numbering, acknowledgement, and retransmission behaviors used by packet switching networks including X.25 public data networks and private leased circuits for organizations like AT&T and British Telecom. LAPB supports balanced operation between two peer stations, allowing both to initiate and respond to frame exchange without a primary/secondary relationship as in SDLC. Equipment manufacturers such as Motorola and Cisco Systems incorporated LAPB modes into hardware and firmware to interface with early WAN services offered by carriers including DATAPAC and TRANSPAC.

History and Development

LAPB evolved in the early 1970s during standardization efforts by CCITT Study Groups and the International Organization for Standardization to provide reliable link layer service for X.25 packet switching projects like RCP and national networks such as Telenet. Designers drew on earlier link protocols implemented at Bell Labs and on framing ideas from IBM Synchronous Data Link Control work; contributions came from telecommunications firms and research institutes including Xerox PARC collaborators and vendors such as Hewlett-Packard. Subsequent revisions were incorporated into ISO/IEC recommendations and national equivalents used by carriers like France Télécom and Deutsche Bundespost to support public data networks through the 1980s and into the 1990s.

Technical Specifications

LAPB uses fixed‑length and variable‑length fields within frames starting and ending with flag sequences adopted from HDLC. Core frame types include Information (I), Supervisory (S), and Unnumbered (U) frames; sequence numbers (N(S), N(R)) provide modulo counting and acknowledgement similar to mechanisms in TCP but implemented at the link layer as in SDLC. Error detection employs Frame Check Sequence (FCS) variants compatible with IEEE polynomial definitions used by CRC standards. Timers such as T1 (retransmit), T3 (keepalive), and N2 (retransmission limit) are specified, mirroring timer constructs codified by ITU‑T. The protocol supports both normal and extended sequence numbering (modulo 8 and modulo 128) to accommodate higher throughput links used by carriers like Sprint and MCI.

Operation and Procedures

A LAPB association begins with link establishment using Unnumbered frames to negotiate modes and parameters, followed by balanced exchange of I frames for user data encapsulation. Supervisory S frames (RR, RNR, REJ) manage flow control and selective acknowledgement behavior; these procedures were implemented in equipment sold to enterprises such as General Electric and Siemens AG for connectivity to public X.25 services. Retransmission logic follows ARQ principles similar to selective-repeat and go‑back‑n strategies documented in ITU recommendations and manuals provided by vendors like Nokia Networks. Link termination uses disconnect U frames and orderly release sequences standardized in ISO documents and adopted by national packet switching operators.

Implementations and Use Cases

LAPB saw wide deployment in public data networks operated by carriers including Telenet, DATAPAC, and TRANSPAC, and in enterprise WAN routers from Cisco Systems, 3Com, and Bay Networks. It was embedded in network switches, terminal adapters, and packet assemblers/disassemblers used by financial institutions such as Visa and Mastercard for transaction switching over X.25 backbones. Telecommunications equipment manufacturers like Ericsson and Alcatel-Lucent provided interoperable LAPB implementations in routers and multiplexers that connected government networks (e.g., NASA testbeds) and industrial control systems in utilities run by entities like ABB.

Security and Reliability

LAPB provides link‑level reliability through CRC‑based error detection and ARQ retransmission but does not include encryption, authentication, or integrity protections beyond frame checks; secure deployments layered additional protocols such as proprietary encryption modules from Nokia or link encryption devices specified by national authorities like NSA for sensitive traffic. Reliability controls—sequence numbering, acknowledgement, timers, and rejection frames—help prevent data loss and duplication, and implementations often incorporated watchdog mechanisms inspired by Bell Labs practices. Interoperability testing between vendors such as Siemens and Motorola was common at forums organized by ITU‑T to validate behavior under error conditions and during congestion on public packet networks.

Legacy and Successors

LAPB’s design influenced later link and transport technologies, informing framing and ARQ elements in protocols developed by IETF working groups and shaping modem and router firmware in products from Cisco Systems and Juniper Networks. The decline of public X.25 networks and the rise of Internet Protocol‑based WANs moved many services to PPP, Frame Relay, and IP/MPLS architectures standardized by IETF and adopted by carriers like Verizon and Orange. Nonetheless, LAPB remains referenced in legacy documentation used in industrial installations overseen by organizations such as Siemens and ABB, and its principles persist in virtual circuit and reliable link designs within modern networking stacks.

Category:Network protocols