What Is Frame Relay?

Frame relay is a wide area network (WAN) protocol that provides a packet-switched data link layer service for transmitting variable-length frames across a shared network infrastructure. Unlike circuit-switched technologies that reserve a fixed bandwidth channel for the duration of a connection, frame relay establishes virtual circuits through a carrier network and transmits frames only when data is available, making it well suited for bursty traffic patterns typical of enterprise data applications. Defined by ITU-T standards in the late 1980s and standardized by the Frame Relay Forum in the early 1990s, the technology displaced older X.25 packet-switching networks because it operated at the data link layer (Layer 2 of the OSI model) rather than the network layer, eliminating the error-correction overhead of X.25 and delivering significantly higher throughput.

Frame relay networks were widely deployed in enterprise WAN environments throughout the 1990s and into the 2000s, connecting geographically dispersed offices across leased lines to carrier point-of-presence nodes. While Frame Relay has been largely superseded by MPLS, broadband IP services, and SD-WAN, it remains in operation on some legacy installations and serves as a conceptual foundation for understanding virtual circuit-based WAN architectures.

Packet Switching and Virtual Circuits

In a frame relay network, each data frame is routed through the carrier network using a Data Link Connection Identifier (DLCI), a locally significant address that identifies the virtual circuit between the customer premises equipment (CPE) and the frame relay switch. Permanent virtual circuits (PVCs) are provisioned in advance by the carrier and remain active continuously; switched virtual circuits (SVCs) are established on demand for the duration of a session. The agreed throughput parameters for each PVC include a Committed Information Rate (CIR), the rate the carrier guarantees to deliver under normal conditions, and a Burst Committed Rate (Bc) that permits temporary exceedances above the CIR when network capacity allows. Frames marked as discard eligible (DE) are the first to be dropped when the network is congested. The Cisco Frame Relay configuration guide documents how DLCI assignment, LMI (Local Management Interface) signaling, and subinterface configuration are implemented on router-based CPE, and covers troubleshooting procedures for common PVC failures including LMI type mismatches and DLCI status errors.

Relationship to ISDN and B-ISDN

Frame relay originated as a bearer service specification within the ISDN (Integrated Services Digital Network) standards framework developed by the ITU-T in the 1980s. ISDN defined a family of digital access services over the public switched telephone network, and frame relay was designed as a high-speed packet-mode interface for both narrowband ISDN (N-ISDN) and broadband ISDN (B-ISDN). B-ISDN, which was intended to deliver broadband services over fiber and was defined in the ITU-T I.121 and I.150 recommendations, used Asynchronous Transfer Mode (ATM) as its transport technology. While frame relay and ATM coexisted in WAN deployments during the 1990s, with frame relay dominant for general enterprise data and ATM for applications requiring strict quality-of-service guarantees, ATM's complexity and cost eventually limited its adoption beyond carrier backbones and specialized applications. The ScienceDirect overview of frame relay technology places frame relay within the broader evolution from analog leased lines and X.25 through ISDN to the IP-based services that followed. The RingCentral overview of frame relay architecture summarizes how frame relay's virtual circuit model influenced the design of subsequent WAN technologies including MPLS label-switched paths.

Applications

Frame relay has applications in a range of wide area networking scenarios, including:

• Enterprise WAN connectivity linking branch offices to headquarters across leased lines
• Voice over Frame Relay (VoFR) for private voice networks before VoIP adoption
• SNA (IBM Systems Network Architecture) traffic encapsulation over shared WAN infrastructure
• Interconnection of ATM and IP networks through interworking functions
• Legacy industrial control and SCADA systems requiring dedicated WAN connectivity