Frame Relay

Frame Relay (FR) is a standardized wide area network (WAN) technology that specifies the physical and data link layers of digital telecommunications channels using a packet switching methodology.

Uses your system voice; voice and rate in settings.

≈ 12 min read

Cite, export and learn8 citation formats · 8 exports · lesson and quiz

Names in other languages

No names in other languages are held for this entry yet.

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

Frame Relay (FR) is a standardized wide area network (WAN) technology that specifies the physical and data link layers of digital telecommunications channels using a packet switching methodology. Frame Relay was originally developed as a simplified version of the X.25 system designed to be carried over the emerging Integrated Services Digital Network (ISDN) networks.

X.25 had been designed to operate over normal telephone lines that were subject to noise that would result in lost data, and the protocol featured extensive error correction to address this. ISDN offered dramatically lower error rates, in effect zero, and the extensive error correction overhead was no longer needed.

The new protocol suite was essentially a cut-down X.25 with no error correction, leading to lower overhead, better channel efficiency, and often significantly overall higher performance than X.25. Like X.25, Frame Relay is normally used in a circuit switched layout, where connections between two endpoints are long-term (in computer terms at least).

This matches the normal use of the telephone network, which X.25 was designed to run on top of. This contrasts with protocols design to be short-term, like the internet Protocol, where every packet might go to a different endpoint.

In practice, Frame Relay was often used as a bridging mechanism to link together local area network (LAN) systems or devices with dedicated links to back-end systems. Users are provided with a connection that encapsulates their data (in some cases including voice in VoFR) and sends that to a Frame Relay node which then forwards that to another endpoint where it is injected into the remote network, appearing as if it were local traffic.

It is less expensive than using leased lines for this purpose and that is one reason for its popularity. The extreme simplicity of configuring user equipment in a Frame Relay network offers another reason for Frame Relay's popularity.

With the advent of Ethernet over fiber optics, MPLS, VPN and dedicated broadband services such as cable modem and DSL, Frame Relay has become less popular in recent years. The Frame Relay standards were promoted by the Frame Relay Forum (FRF). Address Field.

Each address field may occupy either octet 2 to 3, octet 2 to 4, or octet 2 to 5, depending on the range of the address in use. A two-octet address field comprises the EA=ADDRESS FIELD EXTENSION BITS and the C/R=COMMAND/RESPONSE BIT. DLCI-Data Link Connection Identifier Bits.

The DLCI serves to identify the virtual connection so that the receiving end knows which information connection a frame belongs to. Note that this DLCI has only local significance. A single physical channel can multiplex several different virtual connections.

FECN, BECN, DE bits. These bits report congestion: FECN=Forward Explicit Congestion Notification bit BECN=Backward Explicit Congestion Notification bit DE=Discard Eligibility bit Information Field. A system parameter defines the maximum number of data bytes that a host can pack into a frame.

Hosts may negotiate the actual maximum frame length at call set-up time. The standard specifies the maximum information field size (supportable by any network) as at least 262 octets.

Since end-to-end protocols typically operate on the basis of larger information units, Frame Relay recommends that the network support the maximum value of at least 1600 octets in order to avoid the need for segmentation and reassembling by end-users. Frame Check Sequence (FCS) Field.

Since one cannot completely ignore the bit error-rate of the medium, each switching node needs to implement error detection to avoid wasting bandwidth due to the transmission of erred frames. The error detection mechanism used in Frame Relay uses the cyclic redundancy check (CRC) as its basis. Committed information rate (CIR).

The average rate (in bit/s) at which the network guarantees to transfer information units over a measurement interval T. This T interval is defined as: T = Bc/CIR. Committed burst size (BC). The maximum number of information units transmittable during the interval T. Excess burst size (BE).

The maximum number of uncommitted information units (in bits) that the network will attempt to carry during the interval. Once the network has established a connection, the edge node of the Frame Relay network must monitor the connection's traffic flow to ensure that the actual usage of network resources does not exceed this specification.

Frame Relay defines some restrictions on the user's information rate. It allows the network to enforce the end user's information rate and discard information when the subscribed access rate is exceeded. Explicit congestion notification is proposed as the congestion avoidance policy.

It tries to keep the network operating at its desired equilibrium point so that a certain quality of service (QoS) for the network can be met. To do so, special congestion control bits have been incorporated into the address field of the Frame Relay: FECN and BECN. The basic idea is to avoid data accumulation inside the network.

FECN means forward explicit congestion notification. The FECN bit can be set to 1 to indicate that congestion was experienced in the direction of the frame transmission, so it informs the destination that congestion has occurred. BECN means backwards explicit congestion notification.

The BECN bit can be set to 1 to indicate that congestion was experienced in the network in the direction opposite of the frame transmission, so it informs the sender that congestion has occurred.

Origin

Frame Relay began as a stripped-down version of the X.25 protocol, releasing itself from the error-correcting burden most commonly associated with X.25. When Frame Relay detects an error, it simply drops the offending packet.

Frame Relay uses the concept of shared access and relies on a technique referred to as "best-effort", whereby error-correction practically does not exist and practically no guarantee of reliable data delivery occurs. Frame Relay provides an industry-standard encapsulation, utilizing the strengths of high-speed, packet-switched technology able to service multiple virtual circuits and protocols between connected devices, such as two routers.

Although Frame Relay became very popular in North America, it was never very popular in Europe. X.25 remained the primary standard until the wide availability of IP made packet switching almost obsolete. It was used sometimes as backbone for other services, such as X.25 or IP traffic.

Where Frame Relay was used in the USA also as carrier for TCP/IP traffic, in Europe backbones for IP networks often used ATM or PoS, later replaced by Carrier Ethernet

Relationship to X.25

X.25 was an important early WAN protocol, and is often considered to be the grandfather of Frame Relay as many of the underlying protocols and functions of X.25 are still in use today (with upgrades) by Frame Relay. X.25 provides quality of service and error-free delivery, whereas Frame Relay was designed to relay data as quickly as possible over low error networks.

Frame Relay eliminates a number of the higher-level procedures and fields used in X.25. Frame Relay was designed for use on links with error-rates far lower than available when X.25 was designed. X.25 prepares and sends packets, while Frame Relay prepares and sends frames.

X.25 packets contain several fields used for error checking and flow control, most of which are not used by Frame Relay. The frames in Frame Relay contain an expanded link layer address field that enables Frame Relay nodes to direct frames to their destinations with minimal processing.

The elimination of functions and fields over X.25 allows Frame Relay to move data more quickly, but leaves more room for errors and larger delays should data need to be retransmitted. X.25 packet switched networks typically allocated a fixed bandwidth through the network for each X.25 access, regardless of the current load.

This resource allocation approach, while apt for applications that require guaranteed quality of service, is inefficient for applications that are highly dynamic in their load characteristics or which would benefit from a more dynamic resource allocation. Frame Relay networks can dynamically allocate bandwidth at both the physical and logical channel level.

Virtual circuits

As a WAN protocol, Frame Relay is most commonly implemented at Layer 2 (data link layer) of the Open Systems Interconnection (OSI) seven layer model. Two types of circuits exist: permanent virtual circuits (PVCs) which are used to form logical end-to-end links mapped over a physical network, and switched virtual circuits (SVCs).

The latter are analogous to the circuit-switching concepts of the public switched telephone network (PSTN), the global phone network.

Local management interface

Initial proposals for Frame Relay were presented to the Consultative Committee on International Telephone and Telegraph (CCITT) in 1984. Lack of interoperability and standardization prevented any significant Frame Relay deployment until 1990, when Cisco, Digital Equipment Corporation (DEC), Northern Telecom, and StrataCom formed a consortium to focus on its development.

They produced a protocol that provided additional capabilities for complex inter-networking environments. These Frame Relay extensions are referred to as the local management interface (LMI). Datalink connection identifiers (DLCIs) are numbers that refer to paths through the Frame Relay network.

They are only locally significant, which means that when device-A sends data to device-B it will most likely use a different DLCI than device-B would use to reply. Multiple virtual circuits can be active on the same physical end-points (performed by using subinterfaces).

The LMI global addressing extension gives Frame Relay data-link connection identifier (DLCI) values global rather than local significance. DLCI values become DTE addresses that are unique in the Frame Relay WAN. The global addressing extension adds functionality and manageability to Frame Relay internetworks.

Individual network interfaces and the end nodes attached to them, for example, can be identified by using standard address-resolution and discovery techniques. In addition, the entire Frame Relay network appears to be a typical LAN to routers on its periphery. LMI virtual circuit status messages provide communication and synchronization between Frame Relay DTE and DCE devices.

These messages are used to periodically report on the status of PVCs, which prevents data from being sent into black holes (that is, over PVCs that no longer exist). The LMI multicasting extension allows multicast groups to be assigned. Multicasting saves bandwidth by allowing routing updates and address-resolution messages to be sent only to specific groups of routers.

The extension also transmits reports on the status of multicast groups in update messages.

Committed information rate

Frame Relay connections are often given a committed information rate (CIR) and an allowance of burstable bandwidth known as the extended information rate (EIR). The provider guarantees that the connection will always support the C rate, and sometimes the PRa rate should there be adequate bandwidth.

Frames that are sent in excess of the CIR are marked as discard eligible (DE) which means they can be dropped should congestion occur within the Frame Relay network. Frames sent in excess of the EIR are dropped immediately.

Market reputation

promoted the standards Frame Relay aimed to make more efficient use of existing physical resources, permitting the over-provisioning of data services by telecommunications companies to their customers, as clients were unlikely to be using a data service 45 percent of the time. In more recent years, Frame Relay has acquired a bad reputation in some markets because of excessive bandwidth overbooking.

Telecommunications companies often sell Frame Relay to businesses looking for a cheaper alternative to dedicated lines; its use in different geographic areas depended greatly on governmental and telecommunication companies' policies. Some of the early companies to make Frame Relay products included StrataCom (later acquired by Cisco Systems) and Cascade Communications (later acquired by Ascend Communications and then by Lucent Technologies).

As of June 2007, AT&T was the largest Frame Relay service provider in the US, with local networks in 22 states, plus national and international networks.

FRF.12

When multiplexing packet data from different virtual circuits or flows, quality of service concerns often arise. This is because a frame from one virtual circuit may occupy the line for a long enough period of time to disrupt a service guarantee given to another virtual circuit. IP fragmentation is a method for addressing this.

An incoming long packet is broken up into a sequence of shorter packets and enough information is added to reassemble that long frame at the far end. FRF.12 is a specification from the Frame Relay Forum which specifies how to perform fragmentation on frame relay traffic primarily for voice traffic.

The FRF.12 specification describes the method of fragmenting Frame Relay frames into smaller frames.

See also

Multiprotocol Label Switching List of interface bit rates

– Multiprotocol Interconnect over Frame Relay – PPP in Frame Relay – Multiprotocol Interconnect over Frame Relay Technical Library | Broadband Forum - includes Frame Relay Forum documents Cisco Frame Relay Tutorial CCITT I.233 ISDN Frame Mode Bearer Services

Text derived from https://en.wikipedia.org/w/index.php?oldid=1375356913 under CC BY-SA 4.0; modifications have been made.

Words in each sectionLocal management interf…Local management interfaceLocal management interface: 304 words304Relationship to X.25Relationship to X.25Relationship to X.25: 266 words266OriginOriginOrigin: 178 words178Market reputationMarket reputationMarket reputation: 150 words150FRF.12FRF.12FRF.12: 120 words120Committed information r…Committed information rateCommitted information rate: 85 words85Virtual circuitsVirtual circuitsVirtual circuits: 71 words71See alsoSee alsoSee also: 8 words8
Words in each section. Measured from the stored article body; sections below the minimum are not plotted.

Provenance

snapshot enwiki-001375356913 · captured 2026-09-17 · ledger · version history

Cite this page as: encyclopegia.org, “Frame Relay”, snapshot enwiki-001375356913. https://encyclopegia.org/a/frame-relay

Sources cited in this revision

8 named source(s) extracted from the cited revision. A source with no author is shown by its publication; nothing is invented.