View source for Asynchronous Transfer Mode

{{short description|Digital telecommunications protocol for voice, video, and data}}
{{multiple issues|
{{More footnotes needed|date=April 2009}}
{{Tone|article|date=October 2012}}
}}
{{Use dmy dates|date=July 2020}}
{{Use American English|date=July 2023}}

[[File:IBM Turboways ATM 155.jpg|thumb|[[IBM]] Turboways ATM 155 [[Peripheral Component Interconnect|PCI]] network interface card]]

'''Asynchronous Transfer Mode''' ('''ATM''') is a [[telecommunications]] standard defined by the [[American National Standards Institute]] and [[International Telecommunication Union Telecommunication Standardization Sector]] (ITU-T, formerly CCITT) for digital transmission of multiple types of traffic. ATM was developed to meet the needs of the [[Broadband Integrated Services Digital Network]] as defined in the late 1980s,<ref name="bisdn" /> and designed to integrate telecommunication networks. It can handle both traditional high-throughput data traffic and [[Real-time computing|real-time]], [[low-latency]] content such as [[telephony]] (voice) and video.<ref>Telcordia Technologies, ''Telcordia Notes on the Network'', Publication SR-2275 (October 2000)</ref><ref name="ATMF-INTRO">ATM Forum, The User Network Interface (UNI), v. 3.1, {{ISBN|0-13-393828-X}}, Prentice Hall PTR, 1995, page 2.</ref> ATM provides functionality that uses features of [[circuit switching]] and [[packet switching]] networks by using [[asynchronous communication|asynchronous]] [[time-division multiplexing]].<ref>{{cite web|url= http://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-I.150-199902-I!!PDF-E&type=items|title=Recommendation I.150, B-ISDN Asynchronous Transfer Mode functional characteristics |publisher=ITU}}</ref><ref name="McDysan 1999 287">McDysan (1999), p. 287.</ref> ATM was seen in the 1990s as a competitor to [[Ethernet]] and networks carrying IP traffic as, unlike Ethernet, it was faster and designed with quality-of-service in mind, but it fell out of favor once Ethernet reached speeds of 1 gigabits per second.<ref>{{cite book | url=https://books.google.com/books?id=ghy9BOw6svMC&dq=atm+network&pg=PP1 | isbn=978-0-471-49827-8 | title=An Introduction to ATM Networks | date=28 November 2001 | publisher=John Wiley & Sons }}</ref>

In the [[OSI model|Open Systems Interconnection (OSI) reference model]] [[data link layer]] (layer 2), the basic transfer units are called ''[[Frame (networking)|frames]]''. In ATM these frames are of a fixed length (53 [[Octet (computing)|octets]]) called ''cells''. This differs from approaches such as [[Internet Protocol]] (IP) (OSI layer 3) or [[Ethernet]] (also layer 2) that use variable-sized packets or frames. ATM uses a [[connection-oriented model]] in which a [[virtual circuit]] must be established between two endpoints before the data exchange begins.<ref name="McDysan 1999 287"/> These virtual circuits may be either permanent (dedicated connections that are usually preconfigured by the service provider), or switched (set up on a per-call basis using [[Signaling (telecommunications)|signaling]] and disconnected when the call is terminated).

The ATM network reference model approximately maps to the three lowest layers of the OSI model: [[physical layer]], data link layer, and [[network layer]].<ref name="McDysan-Spohn">McDysan, David E. and Spohn, Darrel L., ''[[iarchive:atmtheoryapplica00mcdy/page/n9/mode/2up|ATM : Theory and Application]]'', {{ISBN|0-07-060362-6}}, McGraw-Hill series on computer communications, 1995, page 563.</ref> ATM is a core protocol used in the [[SONET/SDH|synchronous optical networking and synchronous digital hierarchy]] (SONET/SDH) backbone of the [[public switched telephone network]] and in the [[Integrated Services Digital Network]] (ISDN) but has largely been superseded in favor of [[next-generation network]]s based on IP technology. Wireless and mobile ATM never established a significant foothold.

==Protocol architecture==
To minimize [[queuing delay]] and [[packet delay variation]] (PDV), all ATM cells are the same small size. Reduction of PDV is particularly important when carrying voice traffic, because the conversion of digitized voice into an analog audio signal is an inherently [[real time computing|real-time]] process. The [[codec|decoder]] needs an evenly spaced stream of data items.

At the time of the design of ATM, 155&nbsp;Mbit/s [[synchronous digital hierarchy]] with 135&nbsp;Mbit/s payload was considered a fast optical network link, and many [[plesiochronous digital hierarchy]] links in the digital network were considerably slower, ranging from 1.544 to 45&nbsp;Mbit/s in the US, and 2 to 34&nbsp;Mbit/s in Europe.

At 155&nbsp;Mbit/s, a typical full-length 1,500 byte [[Ethernet frame]] would take 77.42&nbsp;[[μs]] to transmit. On a lower-speed 1.544&nbsp;Mbit/s [[T1 line]], the same packet would take up to 7.8 milliseconds. A queuing delay induced by several such data packets might exceed the figure of 7.8&nbsp;ms several times over. This was considered unacceptable for speech traffic.

The design of ATM aimed for a low-jitter network interface. Cells were introduced to provide short queuing delays while continuing to support [[datagram]] traffic. ATM broke up all packets, data, and voice streams into 48-byte chunks, adding a 5-byte routing header to each one so that they could be reassembled later. The choice of 48 bytes was political rather than technical.<ref>D. Stevenson, "Electropolitical Correctness and High-Speed Networking, or, Why ATM is like a Nose", [https://www.amazon.co.uk/dp/0306444860 Proceedings of TriCom '93], April 1993.</ref> When the [[CCITT]] (now ITU-T) was standardizing ATM, parties from the United States wanted a 64-byte payload because this was felt to be a good compromise between larger payloads optimized for data transmission and shorter payloads optimized for real-time applications like voice.

Parties from Europe wanted 32-byte payloads because the small size (and therefore short transmission times) improve performance for voice applications. Most of the European parties eventually came around to the arguments made by the Americans, but France and a few others held out for a shorter cell length. With 32 bytes, France would have been able to implement an ATM-based voice network with calls from one end of France to the other requiring no echo cancellation. 48 bytes (plus 5 header bytes = 53) was chosen as a compromise between the two sides. 5-byte headers were chosen because it was thought that 10% of the payload was the maximum price to pay for routing information.<ref name="bisdn">{{cite web |last=Ayanoglu |first=Ender |title=B-ISDN (Broadband Integrated Services Digital Network) |url=http://repositories.cdlib.org/cpcc/2/ |publisher=Center for Pervasive Communications and Computing, UC Irvine|access-date=3 June 2011|author2=Akar, Nail|date=25 May 2002 }}</ref> ATM multiplexed these 53-byte cells instead of packets which reduced worst-case cell contention jitter by a factor of almost 30, reducing the need for echo cancellers.

===Cell structure===
An ATM cell consists of a 5-byte header and a 48-byte payload. ATM defines two different cell formats: [[user–network interface]] (UNI) and [[network-to-network interface|network–network interface]] (NNI). Most ATM links use UNI cell format.

{| width="100%"
|-----
|
'''Diagram of a UNI ATM cell'''

{| style="width: 20em; text-align: left;" border="1" cellpadding="2" cellspacing="0"
|-----
| style="vertical-align: top; text-align: center; white-space: nowrap; width: 2.5em;" | 7
| style="vertical-align: top; text-align: center; white-space: nowrap; width: 2.5em;" | 
| style="vertical-align: top; text-align: center; white-space: nowrap; width: 2.5em;" | 
| style="vertical-align: top; text-align: center; white-space: nowrap; width: 2.5em;" | 4
| style="vertical-align: top; text-align: center; white-space: nowrap; width: 2.5em;" | 3
| style="vertical-align: top; text-align: center; white-space: nowrap; width: 2.5em;" | 
| style="vertical-align: top; text-align: center; white-space: nowrap; width: 2.5em;" | 
| style="vertical-align: top; text-align: center; white-space: nowrap; width: 2.5em;" | 0
|-----
| colspan="4" rowspan="1" style="background-color: rgb(102, 255, 255); vertical-align: top; text-align: center; white-space: nowrap; width: 10em;" | GFC
| colspan="4" rowspan="1" style="vertical-align: top; text-align: center; white-space: nowrap; width: 10em; background-color: rgb(255, 204, 255);" | VPI<br />
|-----
| colspan="4" rowspan="1" style="vertical-align: top; text-align: center; white-space: nowrap; width: 10em; background-color: rgb(255, 204, 255);" | VPI<br />
| colspan="4" rowspan="1" style="vertical-align: top; text-align: center; white-space: nowrap; width: 10em; background-color: rgb(255, 255, 153);" | VCI<br />
|-----
| colspan="8" rowspan="1" style="vertical-align: top; text-align: center; white-space: nowrap; width: 20em; background-color: rgb(255, 255, 153);" | VCI<br />
|-----
| colspan="4" rowspan="1" style="vertical-align: top; text-align: center; white-space: nowrap; width: 10em; background-color: rgb(255, 255, 153);" | VCI
| colspan="3" rowspan="1" style="vertical-align: top; text-align: center; white-space: nowrap; width: 7.5em; background-color: rgb(255, 255, 204);" | PT
| style="vertical-align: top; text-align: center; white-space: nowrap; width: 2.5em; background-color: rgb(255, 204, 204);" | CLP
|-----
| colspan="8" rowspan="1" style="vertical-align: top; text-align: center; white-space: nowrap; width: 20em; background-color: rgb(153, 255, 153);" | HEC
|-----
| colspan="8" rowspan="1" style="background-color: rgb(204, 204, 204); vertical-align: top; text-align: center; white-space: nowrap; width: 20em;" | <br />
<br />
Payload and padding if necessary (48 bytes)<br />
<br />
|}
|
'''Diagram of an NNI ATM cell'''

{| style="width: 20em; text-align: left;" border="1" cellpadding="2" cellspacing="0"
|-----
| style="vertical-align: top; text-align: center; white-space: nowrap; width: 2.5em;" | 7
| style="vertical-align: top; text-align: center; white-space: nowrap; width: 2.5em;" | 
| style="vertical-align: top; text-align: center; white-space: nowrap; width: 2.5em;" | 
| style="vertical-align: top; text-align: center; white-space: nowrap; width: 2.5em;" | 4
| style="vertical-align: top; text-align: center; white-space: nowrap; width: 2.5em;" | 3
| style="vertical-align: top; text-align: center; white-space: nowrap; width: 2.5em;" | 
| style="vertical-align: top; text-align: center; white-space: nowrap; width: 2.5em;" | 
| style="vertical-align: top; text-align: center; white-space: nowrap; width: 2.5em;" | 0
|-----
| colspan="8" rowspan="1" style="vertical-align: top; text-align: center; white-space: nowrap; width: 20em; background-color: rgb(255, 204, 255);" | VPI<br />
|-----
| colspan="4" rowspan="1" style="vertical-align: top; text-align: center; white-space: nowrap; width: 10em; background-color: rgb(255, 204, 255);" | VPI<br />
| colspan="4" rowspan="1" style="vertical-align: top; text-align: center; white-space: nowrap; width: 10em; background-color: rgb(255, 255, 153);" | VCI<br />
|-----
| colspan="8" rowspan="1" style="vertical-align: top; text-align: center; white-space: nowrap; width: 20em; background-color: rgb(255, 255, 153);" | VCI<br />
|-----
| colspan="4" rowspan="1" style="vertical-align: top; text-align: center; white-space: nowrap; width: 10em; background-color: rgb(255, 255, 153);" | VCI
| colspan="3" rowspan="1" style="vertical-align: top; text-align: center; white-space: nowrap; width: 7.5em; background-color: rgb(255, 255, 204);" | PT
| style="vertical-align: top; text-align: center; white-space: nowrap; width: 2.5em; background-color: rgb(255, 204, 204);" | CLP
|-----
| colspan="8" rowspan="1" style="vertical-align: top; text-align: center; white-space: nowrap; width: 20em; background-color: rgb(153, 255, 153);" | HEC
|-----
| colspan="8" rowspan="1" style="background-color: rgb(204, 204, 204); vertical-align: top; text-align: center; white-space: nowrap; width: 20em;" | <br />
<br />
Payload and padding if necessary (48 bytes)<br />
<br />
|}
|}

;GFC
:The generic flow control (GFC) field is a 4-bit field that was originally added to support the connection of ATM networks to shared access networks such as a distributed queue dual bus (DQDB) ring. The GFC field was designed to give the User-Network Interface (UNI) 4 bits in which to negotiate multiplexing and flow control among the cells of various ATM connections. However, the use and exact values of the GFC field have not been standardized, and the field is always set to 0000.<ref>{{cite web|title=ATM Cell Structure|date=11 September 2008 |url=https://technet.microsoft.com/en-us/library/cc976978.aspx|access-date=13 June 2017}}</ref>
;VPI
:[[Virtual path identifier]] (8 bits UNI, or 12 bits NNI)
;VCI
:[[Virtual channel identifier]] (16 bits)
;PT
:Payload type (3 bits)
::Bit 3 (msbit): Network management cell. If 0, user data cell and the following apply:
::Bit 2: Explicit forward congestion indication (EFCI); 1 = [[network congestion]] experienced
::Bit 1 (lsbit): ATM user-to-user (AAU) bit. Used by AAL5 to indicate packet boundaries.
;CLP
:Cell loss priority (1-bit)
;HEC
:[[CRC-based framing|Header error control]] (8-bit CRC, polynomial = X<sup>8</sup> + X<sup>2</sup> + X + 1)

ATM uses the PT field to designate various special kinds of cells for [[operations, administration and management]] (OAM) purposes, and to delineate packet boundaries in some [[ATM adaptation layer]]s (AAL). If the [[most significant bit]] (MSB) of the PT field is 0, this is a user data cell, and the other two bits are used to indicate network congestion and as a general-purpose header bit available for ATM adaptation layers. If the MSB is 1, this is a management cell, and the other two bits indicate the type: network management segment, network management end-to-end, resource management, and reserved for future use.

Several ATM link protocols use the HEC field to drive a [[CRC-based framing]] algorithm, which allows locating the ATM cells with no overhead beyond what is otherwise needed for header protection. The 8-bit CRC is used to correct single-bit header errors and detect multi-bit header errors. When multi-bit header errors are detected, the current and subsequent cells are dropped until a cell with no header errors is found.

A UNI cell reserves the GFC field for a local [[flow control (data)|flow control]] and sub-multiplexing system between users. This was intended to allow several terminals to share a single network connection in the same way that two ISDN phones can share a single basic rate ISDN connection. All four GFC bits must be zero by default.

The NNI cell format replicates the UNI format almost exactly, except that the 4-bit GFC field is re-allocated to the VPI field, extending the VPI to 12 bits. Thus, a single NNI ATM interconnection is capable of addressing almost 2<sup>12</sup> VPs of up to almost 2<sup>16</sup> VCs each.{{efn|In practice some of the VP and VC numbers are reserved.}}

===Service types===
ATM supports different types of services via AALs. Standardized AALs include AAL1, AAL2, and AAL5, and the rarely used<ref>{{Cite web|title=A Brief Overview of ATM: Protocol Layers, LAN Emulation, and Traffic Management|url=https://www.cse.wustl.edu/~jain/papers/ftp/atm_tut/index.html|access-date=2021-07-21|website=www.cse.wustl.edu}}</ref> AAL3 and AAL4. AAL1 is used for constant bit rate (CBR) services and circuit emulation. Synchronization is also maintained at AAL1. AAL2 through AAL4 are used for [[variable bitrate]] (VBR) services, and AAL5 for data. Which AAL is in use for a given cell is not encoded in the cell. Instead, it is negotiated by or configured at the endpoints on a per-virtual-connection basis.

Following the initial design of ATM, networks have become much faster. A 1500 byte (12000-bit) full-size [[Ethernet frame]] takes only 1.2&nbsp;μs to transmit on a 10&nbsp;Gbit/s network, reducing the motivation for small cells to reduce jitter due to contention. The increased link speeds by themselves do not eliminate jitter due to queuing.

ATM provides a useful ability to carry multiple logical circuits on a single physical or virtual medium, although other techniques exist, such as [[Point-to-Point Protocol#Multiclass PPP|Multi-link PPP]], Ethernet [[VLAN]]s, [[VxLAN]], [[MPLS]], and multi-protocol support over [[SONET]].

== Virtual circuits == <!--[[Virtual channel identifier]] and [[Virtual path identifier]] redirect here-->
An ATM network must establish a connection before two parties can send cells to each other. This is called a [[virtual circuit]] (VC). It can be a permanent virtual circuit (PVC), which is created administratively on the end points, or a switched virtual circuit (SVC), which is created as needed by the communicating parties. SVC creation is managed by [[signaling (telecommunications)|signaling]], in which the requesting party indicates the address of the receiving party, the type of service requested, and whatever traffic parameters may be applicable to the selected service. ''[[Admission control|Call admission]]'' is then performed by the network to confirm that the requested resources are available and that a route exists for the connection.

=== Motivation ===
ATM operates as a channel-based transport layer, using VCs. This is encompassed in the concept of the virtual paths (VP) and virtual channels. Every ATM cell has an 8- or 12-bit virtual path identifier (VPI) and 16-bit virtual channel identifier (VCI) pair defined in its header.<ref name="cisco-atm">Cisco Systems [https://indigothemes.com/wikipedia-contribution/techgd.pdf ''Guide to ATM Technology''] (2000). Section "Operation of an ATM Switch". Retrieved 2 June 2011.</ref> The VCI, together with the VPI, is used to identify the next destination of a cell as it passes through a series of ATM switches on its way to its destination. The length of the VPI varies according to whether the cell is sent on a user-network interface (at the edge of the network), or if it is sent on a network-network interface (inside the network).

As these cells traverse an ATM network, switching takes place by changing the VPI/VCI values (label swapping). Although the VPI/VCI values are not necessarily consistent from one end of the connection to the other, the concept of a circuit ''is'' consistent (unlike IP, where any given packet could get to its destination by a different route than the others).<ref name="cisco-atm-cell">Cisco Systems [https://indigothemes.com/wikipedia-contribution/techgd.pdf ''Guide to ATM Technology''] (2000). Section "ATM Cell Header Formats". Retrieved 2 June 2011.</ref> ATM switches use the VPI/VCI fields to identify the virtual channel link (VCL) of the next network that a cell needs to transit on its way to its final destination. The function of the VCI is similar to that of the [[data link connection identifier]] (DLCI) in [[Frame Relay]] and the logical channel number and logical channel group number in [[X.25]].

Another advantage of the use of virtual circuits comes with the ability to use them as a multiplexing layer, allowing different services (such as voice, Frame Relay, IP). The VPI is useful for reducing the switching table of some virtual circuits which have common paths.<ref>{{cite web |title=What is VPI and VCI settings of broadband connections? |url=http://www.techlineinfo.com/what-is-vpi-and-vci-settings-of-broadband-connections/ |website=Tech Line Info |publisher=Sujith |access-date=1 July 2010}}</ref>

=== Types ===
ATM can build virtual circuits and virtual paths either statically or dynamically. Static circuits (permanent virtual circuits or PVCs) or paths (permanent virtual paths or PVPs) require that the circuit is composed of a series of segments, one for each pair of interfaces through which it passes.

PVPs and PVCs, though conceptually simple, require significant effort in large networks. They also do not support the re-routing of service in the event of a failure. Dynamically built PVPs (soft PVPs or SPVPs) and PVCs (soft PVCs or SPVCs), in contrast, are built by specifying the characteristics of the circuit (the service ''contract'') and the two endpoints.

ATM networks create and remove switched virtual circuits (SVCs) on demand when requested by an [[end station]]. One application for SVCs is to carry individual telephone calls when a network of telephone switches are interconnected using ATM. SVCs were also used in attempts to replace [[local area network]]s with ATM.

=== Routing ===
Most ATM networks supporting SPVPs, SPVCs, and SVCs use the [[Private Network-to-Network Interface]] (PNNI) protocol to share topology information between switches and select a route through a network. PNNI is a [[link-state routing protocol]] like [[OSPF]] and [[IS-IS]]. PNNI also includes a very powerful [[route summarization]] mechanism to allow construction of very large networks, as well as a [[call admission control]] (CAC) algorithm which determines the availability of sufficient bandwidth on a proposed route through a network in order to satisfy the service requirements of a VC or VP.

== Traffic engineering ==
Another key ATM concept involves the [[traffic contract]]. When an ATM circuit is set up each switch on the circuit is informed of the traffic class of the connection. ATM traffic contracts form part of the mechanism by which [[quality of service]] (QoS) is ensured. There are four basic types (and several variants) which each have a set of parameters describing the connection.
# CBR {{En dash}} Constant bit rate: a Peak Cell Rate (PCR) is specified, which is constant.
# VBR {{En dash}} Variable bit rate: an average or Sustainable Cell Rate (SCR) is specified, which can peak at a certain level, a PCR, for a maximum interval before being problematic.
# ABR {{En dash}} Available bit rate: a minimum guaranteed rate is specified.
# UBR {{En dash}} Unspecified bit rate: traffic is allocated to all remaining transmission capacity.

VBR has real-time and non-real-time variants, and serves for [[Burstiness|bursty]] traffic. Non-real-time is sometimes abbreviated to vbr-nrt. Most traffic classes also introduce the concept of cell-delay variation tolerance (CDVT), which defines the ''clumping'' of cells in time.

=== Traffic policing ===
To maintain network performance, networks may apply [[Traffic policing (communications)|traffic policing]] to virtual circuits to limit them to their traffic contracts at the entry points to the network, i.e. the [[user–network interface]]s (UNIs) and [[network-to-network interface]]s (NNIs) using [[UPC and NPC|usage/network parameter control]] (UPC and NPC).<ref name="UPC_NPC" >ITU-T, ''Traffic control and congestion control in B ISDN'', Recommendation I.371, International Telecommunication Union, 2004, page 17</ref> The reference model given by the ITU-T and ATM Forum for UPC and NPC is the [[generic cell rate algorithm]] (GCRA),<ref name="ITU-T-GCRA" >ITU-T, ''Traffic control and congestion control in B ISDN'', Recommendation I.371, International Telecommunication Union, 2004, Annex A, page 87.</ref><ref name="ATMF-GCRA" >ATM Forum, The User Network Interface (UNI), v. 3.1, {{ISBN|0-13-393828-X}}, Prentice Hall PTR, 1995.</ref> which is a version of the [[Leaky bucket#As a Meter|leaky bucket algorithm]]. CBR traffic will normally be policed to a PCR and CDVT alone, whereas VBR traffic will normally be policed using a dual leaky bucket controller to a PCR and CDVT and an SCR and maximum burst size (MBS). The MBS will normally be the [[Network packet|packet]] ([[Segmentation and Reassembly|SAR]]-[[Service data unit|SDU]]) size for the VBR VC in cells.

If the traffic on a virtual circuit exceeds its traffic contract, as determined by the GCRA, the network can either drop the cells or set the [[Cell Loss Priority]] (CLP) bit, allowing the cells to be dropped at a congestion point. Basic policing works on a cell-by-cell basis, but this is sub-optimal for encapsulated packet traffic as discarding a single cell will invalidate a packet's worth of cells. As a result, schemes such as partial packet discard (PPD) and early packet discard (EPD) have been developed to discard a whole packet's cells. This reduces the number of useless cells in the network, saving bandwidth for full packets. EPD and PPD work with AAL5 connections as they use the end of packet marker: the ATM user-to-ATM user (AUU) indication bit in the payload-type field of the header, which is set in the last cell of a SAR-SDU.

=== Traffic shaping ===
[[Traffic shaping]] usually takes place in the [[network interface controller]] (NIC) in user equipment, and attempts to ensure that the cell flow on a VC will meet its traffic contract, i.e. cells will not be dropped or reduced in priority at the UNI. Since the reference model given for traffic policing in the network is the GCRA, this algorithm is normally used for shaping as well, and single and dual [[leaky bucket]] implementations may be used as appropriate.

==Reference model==
The ATM network reference model approximately maps to the three lowest layers of the [[OSI reference model]]. It specifies the following layers:<ref>{{cite web|publisher=Cisco Systems |title=Guide to ATM Technology for the Catalyst 8540 MSR, Catalyst 8510 MSR, and LightStream 1010 ATM Switch Routers |year=2000 |work=Customer Order Number: DOC-786275 |url=https://www.cisco.com/application/pdf/en/us/guest/products/ps1891/c2001/ccmigration_09186a00800f4b5d.pdf |archive-url=https://ghostarchive.org/archive/20221009/https://www.cisco.com/application/pdf/en/us/guest/products/ps1891/c2001/ccmigration_09186a00800f4b5d.pdf |archive-date=2022-10-09 |url-status=live |access-date=19 July 2011 }}</ref>
*At the physical network level, ATM specifies a layer that is equivalent to the OSI [[physical layer]].
*The ATM layer 2 roughly corresponds to the OSI [[data link layer]].
*The OSI [[network layer]] is implemented as the [[ATM adaptation layer]] (AAL).

== Deployment ==
[[File:ForeRunnerLE 25 ATM switch (1).jpg|thumb|ATM switch by FORE systems]]
ATM became popular with telephone companies and many computer makers in the 1990s. However, even by the end of the decade, the better [[price–performance ratio]] of [[Internet Protocol]]-based products was competing with ATM technology for integrating real-time and bursty network traffic.<ref name="bellheads">{{Cite news |title= Netheads vs Bellheads |author= Steve Steinberg |magazine= Wired |date= October 1996 |volume= 4 |number= 10 |url= https://www.wired.com/wired/archive/4.10/atm.html |access-date=24 September 2011 }}</ref> Companies such as [[FORE Systems]] focused on ATM products, while other large vendors such as [[Cisco Systems]] provided ATM as an option.<ref>{{Cite news |title= What's in store for FORE? |page= 12 |work= Network World |date= 16 September 1996 |url= https://books.google.com/books?id=IxgEAAAAMBAJ&pg=PA12 |access-date=24 September 2011 }}</ref> After the burst of the [[dot-com bubble]], some still predicted that "ATM is going to dominate".<ref>{{Cite news |title= Optical Ethernet firms brave stormy industry seas |page= 14 |work= Network World |date= 7 May 2001 |url= https://books.google.com/books?id=GBwEAAAAMBAJ&pg=PA14 |access-date=24 September 2011 }}</ref> However, in 2005 the [[ATM Forum]], which had been the trade organization promoting the technology, merged with groups promoting other technologies, and eventually became the [[Broadband Forum]].<ref>{{Cite web |title= About the Broadband Forum: Forum History |url= http://www.broadband-forum.org/about/forumhistory.php |access-date= 24 September 2011  |archive-url= https://web.archive.org/web/20111009003434/http://www.broadband-forum.org/about/forumhistory.php |archive-date= 9 October 2011}}</ref>

== Wireless or mobile ATM==
Wireless ATM,<ref name="watm1">{{Cite web|url=https://archive.today/20130615202256/http://connectedplanetonline.com/wireless/mag/wireless_wireless_atm_debate/|title=The Wireless ATM Debate|date=15 June 2013|website=archive.ph}}</ref> or mobile ATM, consists of an ATM core network with a wireless access network. ATM cells are transmitted from base stations to mobile terminals. Mobility functions are performed at an ATM switch in the core network, known as a ''crossover switch'',<ref name="watm5">[http://www.barnesandnoble.com/w/wireless-atm-and-ad-hoc-networks-c-k-toh/1112737100?ean=9780792398226 Book on Wireless ATM Networks] - [[Chai Keong Toh]], Kluwer Academic Press 1997</ref> which is similar to the [[mobile switching center]] of GSM networks.

The advantage of wireless ATM is its high bandwidth and high-speed handoffs done at layer 2. In the early 1990s, [[Bell Labs]] and [[NEC]] research labs worked actively in this field.<ref name="watm10">[https://www.researchgate.net/publication/3233809_WATMnet_a_prototype_wireless_ATM_system_for_multimedia_personalcommunication WATMnet: a prototype wireless ATM system for multimedia personal communication], D. Raychaudhuri, et al.</ref> [[Andy Hopper]] from the [[University of Cambridge]] Computer Laboratory also worked in this area.<ref name="watm2">{{Cite web |url=http://www.cl.cam.ac.uk/research/dtg/attarchive/radio/ |title=Cambridge Mobile ATM work |access-date=10 June 2013 |archive-url=https://web.archive.org/web/20150625230533/http://www.cl.cam.ac.uk/research/dtg/attarchive/radio/ |archive-date=25 June 2015  }}</ref> There was a wireless ATM forum formed to standardize the technology behind wireless ATM networks. The forum was supported by several telecommunication companies, including NEC, [[Fujitsu]] and [[AT&T]]. Mobile ATM aimed to provide high-speed multimedia communications technology, capable of delivering broadband mobile communications beyond that of GSM and WLANs.

== See also ==
* [[VoATM]]
* [[ATM25]]

== Notes ==
{{notelist}}

== References ==
{{reflist}}

==Further reading==
* {{cite book
|last=Black
|first=Uyless D.
|title=ATM—Volume III: Internetworking with ATM
|year=1998
|publisher=Prentice Hall
|location=Toronto
|isbn=0-13-784182-5
|url-access=registration
|url=https://archive.org/details/atm00blac
}}
* {{cite book
|first=Martin
|last=De Prycker
|title=Asynchronous Transfer Mode. Solutions for Broadband ISDN
|publisher=Prentice Hall
|year=1993}}
* {{cite book
|last=Joel
|first=Amos E. Jr.
|title=Asynchronous Transfer Mode
|publisher=IEEE Press
|year=1993}}
* {{cite book
|last=Golway
|first=Tom
|title=Planning and Managing ATM Network
|url=https://archive.org/details/planningmanaging0000mino
|url-access=registration
|location=New York
|publisher=Manning
|year=1997
|isbn=978-0-13-262189-2}}
* {{cite book
|last=McDysan
|first=David E.
|author2=Darren L. Spohn
|title=ATM Theory and Applications
|year=1999
|publisher=McGraw-Hill
|location=Montreal
|isbn=0-07-045346-2}}
* {{cite book
|last=Neelakanta
|first=P. S.
|title=A Textbook on ATM Telecommunications, Principles and implementation
|year=2000
|publisher=CRC Press
|isbn=0-8493-1805-X}}

== External links ==
* {{cite web |url=http://www.atmforum.com/ |title=ATM forum |archive-url=https://web.archive.org/web/20050701081559/http://www.atmforum.com/ |archive-date=1 July 2005}}
* {{cite web |url=http://www.telecomspace.com/vop-atm.html |title=ATM Info and resources |archive-url=https://web.archive.org/web/20130102183255/http://www.telecomspace.com/vop-atm.html |archive-date=2 January 2013 }}
* [http://www.chipweb.de/atm/ ATM ChipWeb - Chip and NIC database]
* {{cite web |url=http://www.juniper.net/techpubs/software/erx/junose61/swconfig-link/html/atm-config2.html |title=A tutorial from Juniper web site |archive-url=https://web.archive.org/web/20081013151843/http://www.juniper.net/techpubs/software/erx/junose61/swconfig-link/html/atm-config2.html |archive-date=2008-10-13}}
* {{cite web |url=http://www2.rad.com/networks/2004/atm/main.htm |title=ATM Tutorial |archive-url=https://web.archive.org/web/20070114172002/http://www2.rad.com/networks/2004/atm/main.htm |archive-date=2007-01-14}} 
* {{cite web |url=http://docwiki.cisco.com/wiki/Asynchronous_Transfer_Mode_Switching |archive-url=https://web.archive.org/web/20180131030149/http://docwiki.cisco.com/wiki/Asynchronous_Transfer_Mode_Switching |archive-date=2018-01-31 |title=Asynchronous Transfer Mode Switching |publisher=[[Cisco Systems]] |work=DocuWiki}}
* {{cite web |url=http://www.cisco.com/univercd/cc/td/doc/product/atm/c8540/12_0/13_19/trouble/cells.htm |title=ATM Cell formats |publisher=Cisco Systems |archive-url=https://archive.today/20121206000842/http://www.cisco.com/univercd/cc/td/doc/product/atm/c8540/12_0/13_19/trouble/cells.htm |archive-date=2012-12-06}}
* {{cite web |url=http://www.cisco.com/web/psa/technologies/index.html?c=268435599 |archive-url=https://web.archive.org/web/20071029234552/https://www.cisco.com/web/psa/technologies/index.html?c=268435599 |archive-date=2007-10-29 |title=Asynchronous Transfer Mode (ATM) |publisher=Cisco Systems}}

[[Category:Asynchronous Transfer Mode| ]]
[[Category:ITU-T recommendations]]
[[Category:Link protocols]]
[[Category:Networking standards]]