How is MPLS different from SONET and ATM networks?

Synchronous Optical Network (SONET) is the fiber optic standard that is focused on the physical layers of the OSI model. SONET, and its international equivalent Synchronous Digital

    Requires Free Membership to View

Hierarchy (SDH), originally define how voice traffic will be carried across the carrier-built fiber optic networks deployed throughout the world. As a Layer-1, physical level protocol, SONET makes link connections along and between these fiber networks. SONET was evolved over time to include data services -- such as frame relay, T1, and OC-3 -- to connect over the fiber links. Because SONET was originally designed for voice and not variable-sized data packets, however, moving data across it was inefficient and required padding data packets with irrelevant data to make up any differences. Asynchronous transfer mode (ATM) was introduced as a solution for this inefficiency. Through the use of hardware network interface adapters, ATM networks break data into smaller cells for transport. ATM over SONET also makes home and business ISDN (Integrated Services Digital Network) data services possible.

In contrast, ATM and Multiprotocol Label Switching (MPLS) are data transport protocols, meaning that both reside above the physical data layers in the OSI model and aid in moving data from one point to another. The primary difference between ATM and MPLS is that while ATM was designed to exist in a circuit-switched environment, MPLS has its place within modern packet-switched networks such as Ethernet or IP. This difference is most apparent in how the two types of network topologies are deployed. ATM is primarily designed as a point-to-point connection, requiring an ATM adapter on each end of a physical or virtual circuit. MPLS, on the other hand, operates similar to an Ethernet switch in an any-to-any topology, allowing each of the network endpoints to be connected to the MPLS network and mesh with a particular customer’s virtual mesh. For ATM to replicate this level of meshing, multiple ATM connections would have to be installed at each of an organization’s locations. The multi-protocol nature of MPLS also enables the technology to label and pass other protocols, including ATM, across an MPLS network. Two ATM endpoints, for example, could be connected across an MPLS network, with the network itself quickly guiding traffic to each other transparently.

This was first published in November 2010

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.