ATM Model

7 out of 8 rated this helpful Rate this topic The ATM model's primary layers are the physical layer, the ATM layer, and the ATM Adaptation layer. Each layer and sub layer is described in more detail in the following sections.

Physical Layer
The physical layer provides for the transmission and reception of ATM cells across a physical medium between two ATM devices; this can be a transmission between an ATM endpoint and an ATM switch, or it can be between two ATM switches. The physical layer is subdivided into a Physical Medium Dependent sub layer and Transmission Convergence sub layer. Top Of Page

PMD Sub layer

The Physical Medium Dependent (PMD) sublayer is responsible for the transmission and reception of individual bits on a physical medium. These responsibilities encompass bit timing, signal encoding, interacting with the physical medium, and the cable or wire itself. ATM does not rely on any specific bit rate, encoding scheme or medium and various specifications for ATM exist for coaxial cable, shielded and unshielded twisted pair wire, and optical fiber at speeds ranging from 64 kilobits per second to 9.6 gigabits per second. In addition, the ATM physical medium can extend up to 60 kilometers or more using single-mode fiber and long-reach lasers, so it can readily support campus-wide connectivity and even private metropolitan area networks (MANs). The independence of ATM from a particular set of hardware constraints has allowed it to be implemented over radio and satellite links. Top Of Page

Transmission Convergence Sublayer

The Transmission Convergence (TC) sublayer functions as a converter between the bit stream of ATM cells and the Physical Medium Dependent sublayer. When transmitting, the TC sublayer

maps ATM cells onto the format of the Physical Medium Dependent sublayer (such as DS-3 or SONET frames). Because a continuous stream of bytes is required, unused portions of the ATM cell stream are "filled" by idle cells. These idle cells are identified in the ATM header and are silently discarded by the receiver. They are never passed to the ATM layer for processing. The TC sublayer also generates and verifies the Header Error Control (HEC) field for each cell. On the transmitting side, it calculates the HEC and places it in the header. On the receiving side, the TC sublayer checks the HEC for verification. If a single bit error can be corrected, the bit is corrected and the results are passed to the ATM layer. If the error cannot be corrected (as in the case of a multi-bit error) the cell is silently discarded. Finally, the TC sublayer delineates the ATM cells, marking where ATM cells begin and where they end. The boundaries of the ATM cells can be determined from the Physical Medium Dependent layer formatting or from the incoming byte stream using the HEC field. The PMD performs the HEC validation per byte on the preceding 4 bytes. If it finds a match, the next ATM cell boundary is 48 bytes away (corresponding to the ATM payload). The PMD performs this verification several times to ensure that the cell boundaries have been determined correctly. Top Of Page

The ATM Layer

The ATM layer provides cell multiplexing, demultiplexing, and VPI/VCI routing functions. The ATM layer also supervises the cell flow to ensure that all connections remain within their negotiated cell throughput limits. If connections operate outside their negotiated parameters, the ATM layer can take corrective action so the misbehaving connections do not affect connections that are obeying their negotiated connection contract. The ATM layer also maintains the cell sequence from any source. The ATM layer multiplexes and demultiplexes and routes ATM cells, and ensures their sequence from end to end. However, if a cell is dropped by a switch due to congestion or corruption, it is not the ATM layer's responsibility to correct the dropped cell through retransmission or to notify other layers of the dropped cell. Layers

above the ATM layer must sense the lost cell and decide whether to correct it or disregard it. In the case of interactive voice or video, a lost cell is typically disregarded because it would take too long to resend the cell and place it in the proper sequence to reconstruct the audio or video signal. A significant number of dropped cells in time-dependent services, such as voice or video, results in a choppy audio or video playback, but the ATM layer cannot correct the problem unless a higher Quality of Service is specified for the connection. In the case of data (such as a file transfer), the upper layer application must sense the absence of the cell and retransmit it. A file with missing 48-bytes chunks here and there is a corrupted file that is unacceptable to the receiver. Because operations such as file transfers are not time dependent, the contents of the cell can be recovered by incurring a delay in the transmission of the file corresponding to the recovery of the lost cell. Top Of Page

ATM Layer Multiplexing and Demultiplexing

ATM layer multiplexing blends all the different input types so that the connection parameters of each input are preserved. This process is known as traffic shaping. ATM layer demultiplexing takes each cell from the ATM cell stream and, based on the VPI/VCI, either routes it (for an ATM switch) or passes the cell to the ATM Adaptation Layer (AAL) process that corresponds to the cell (for an ATM endpoint). Top Of Page

ATM Adaptation Layers

The ATM Adaptation Layers (AAL) are responsible for the creation and reception of 48-byte payloads through the lower layers of ATM on behalf of different types of applications. Though there are five different types of AALs, Windows 2000 supports only AAL5. ATM Adaptation is necessary to link the cell-based technology at the ATM Layer to the bit-stream technology of digital devices (such as telephones and video cameras) and the packet-stream technology of modern data networks (such as Frame Relay, X.25 or LAN protocols such as TCP/IP or Ethernet).

The five different AALs each provide a distinct class of service: AAL0 AAL0 is user-defined, or No AAL, meaning that no AAL layer is used. In all other AAL types, some delineation of the data segment is included at the AAL level before the segment is made into cells. This affects how the data is passed up to the ATM layer. With AAL5, the data is not passed up until a complete AAL segment is received. With AAL0, for example, there is no delineation or synchronization, so individual cells are passed up as they are received, or the adapter might optimize and accrue a certain amount before indicating that a cell can be passed along. AAL1 AAL1 provides circuit emulation over an ATM network. This requires constant bit rate, time-dependent service. To provide this, AAL1 adds timestamps, error checking and sequencing to the data payload. Additional functionality is provided in AAL1 to load the 48-byte cell payload with multiple smaller-than-48-byte samples, as is usually required with voice streams. Due to its high overhead, AAL1 is used only when these features are required. This format is most commonly used with voice or video applications. AAL2 AAL2 is a mechanism that allows the transfer of highspeed, variable bit rate information in an isochronous, connectionoriented manner. Unlike AAL1, AAL2 is designed to use bandwidth only when data is sent. AAL2 has never been fully defined by the standards committee and did not gained wide acceptance. It has largely been supplanted by AAL5. AAL3/4 AAL3/4 combines two once-separate AAL specifications. AAL3 was intended for the framing of connection-oriented protocols, while AAL4 was intended for the framing of connectionless protocols. While pursuing these two standards, the ATM standards bodies learned that there was no difference in the framing between the two types of protocols; therefore, they combined the two separate framing methods to create AAL3/4. This AAL adds information to the payload regarding segment size, sequencing, and ordering control. However, AAL 3/4 is rarely used because of the high overhead required; AAL5 provides the same services with minimal overhead. AAL5 AAL5 provides a way for non-isochronous, variable bit rate, connectionless applications to send and receive data. AAL5

was developed as a way to provide a more efficient transfer of network traffic than AAL3/4. AAL5 merely adds a trailer to the payload to indicate size and provide error detection. AAL5 is the AAL of choice when sending connection-oriented or connectionless LAN protocol traffic over an ATM network. Windows 2000 supports AAL5. Top Of Page

AAL5 in Detail
AAL5 provides a straightforward framing at the Common Part Convergence Sublayer (CPCS) that behaves more like existing LAN technologies, such as Ethernet. Figure 14.5 shows a detailed breakdown of an AAL5 Cell Header and Payload. Figure 14.5 Breakdown of an AAL5 Cell Header and Payload With AAL5, there is no longer a dual encapsulation. The service class frames cells at the CPCS, but not at the Segmentation and Reassembly (SAR) sublayer to minimize overhead. It also uses a bit in the Payload Type (PT) field of the ATM header rather than a separate SAR framing. AAL5 is the AAL of choice when sending connection-oriented (X.25 or Frame Relay) or connectionless (IP or IPX) LAN protocol traffic over an ATM network. Top Of Page

AAL5 CPCS Sublayer

Figure 14.5 shows the framing that occurs at the AAL5 CPCS sublayer. (Note that only a trailer is added.) Top Of Page

CPCS PDU Payload

The block of data that an application sends. The size can vary from 1 byte to 65,535 bytes. The PAD consists of padding bytes of variable length (0-47 bytes), which create a whole number of cells by making the CPCS PDU payload length a multiple of 48 bytes. Top Of Page

User-to-User Indication
Transfers information between AAL users. Top Of Page

Common Part Indicator

Currently used only for alignment processes so that the AAL5 trailer falls on a 64-bit boundary. Top Of Page

Length of CPCS PDU Payload Field

Indicates the length of the CPCS PDU payload in bytes. The length does not include the PAD. Top Of Page

Cyclic Redundancy Check (CRC)

A Cyclic Redundancy Check, or CRC, is a 32-bit portion of the trailer that performs error checking on the bits in the CPCS PDU. The AAL5 CRC uses the same CRC-32 algorithm used in 802. x -based networks such as Ethernet and Token Ring. Top Of Page

AAL5 SAR Sublayer

Byte-by-byte, Figure 14.5 shows the framing that occurs at the AAL5 SAR sublayer. There is no SAR header or trailer added. On the transmitting side, the AAL5 SAR sublayer merely segments the CPCS PDU into 48-byte units and passes them to the ATM layer for the final ATM header. On the receiving side, the sublayer reassembles a series of 48-byte units and passes the result to the CPCS. The AAL5 SAR uses the third bit in the Payload Type (PT) field to indicate when the last 48byte unit in a CPCS PDU is being sent. When the ATM cell is received with the third bit of the PT field set, the ATM layer indicates this fact to the AAL; the AAL then begins a CRC and length-checking analysis of the full CPCS PDU.
----------------------------------------------------

What is a ATM ? Asynchronous Transfer Mode

Home Search Get this document in PDF form

Presented by: Copyright 2000

Asynchronous Transfer Mode (ATM) Switching Background Asynchronous Transfer Mode (ATM) is an International Telecommunication Union- Telecommunication Standardization Sector (ITU-T) standard for cell relay wherein information for multiple service types, such as voice, video, or data, is conveyed in small, fixed-size cells. ATM networks are connection oriented. This chapter provides summaries of ATM protocols, services, and operation. Figure 20-1 illustrates a private ATM network and a public ATM network carrying voice, video, and data traffic. Figure 20-1: A private ATM network and a public ATM network both can carry voice, video, and data traffic.

About Pulse Products Services

Contact Us Email Us

Ordering

Manufacturers

Learn Datacomm

Mailing List

Standards ATM is based on the efforts of the ITU-T Broadband Integrated Services Digital Network (BISDN) standard. It was originally conceived as a high-speed transfer technology for voice, video, and data over public networks. The ATM Forum extended the ITU-T's vision of ATM for use over public and private networks. The ATM Forum has released work on the following specifications:

User-to-Network Interface (UNI) 2.0 UNI 3.0 UNI 3.1 Public-Network Node Interface (P-NNI) LAN Emulation (LANE)

ATM Devices and the Network Environment ATM is a cell-switching and multiplexing technology that combines the benefits of circuit switching (guaranteed capacity and constant transmission delay) with those of packet switching (flexibility and efficiency for intermittent traffic). It provides scalable bandwidth from a few megabits per second (Mbps) to many gigabits per second (Gbps). Because of its asynchronous nature, ATM is more efficient than synchronous technologies, such as time-division multiplexing (TDM). With TDM, each user is assigned to a time slot, and no other station can send in that time slot. If a station has a lot of data to send, it can send only when its time slot comes up, even if all other time slots are empty. If, however, a station has nothing to transmit when its time slot comes up, the time slot is sent empty and is wasted. Because ATM is asynchronous, time slots are available on demand with information identifying the source of the transmission contained in the header of each ATM cell. ATM Cell Basic Format ATM transfers information in fixed-size units called cells. Each cell consists of 53 octets, or bytes. The first 5 bytes contain cell-header information, and the remaining 48 contain the "payload" (user information). Small fixed-length cells are well suited to transferring voice and video traffic because such traffic is intolerant of delays that result from having to wait for a large data packet to download, among other things. Figure 20-2 illustrates the basic format of an ATM cell. Figure 20-2: An ATM network comprises ATM switches and endpoints.

ATM Devices An ATM network is made up of an ATM switch and ATM endpoints. An ATM switch is responsible for cell transit through an ATM network. The job of an ATM switch is well defined: it accepts the incoming cell from an ATM endpoint or another ATM switch. It then reads and updates the cell-header information and quickly switches the cell to an output interface toward its destination. An ATM endpoint (or end system) contains an ATM network interface adapter. Examples of ATM endpoints are workstations, routers, digital service units

(DSUs), LAN switches, and video coder-decoders (CODECs). Figure 20-3 illustrates an ATM network made up of ATM switches and ATM endpoints. Figure 20-3: An ATM network comprises ATM switches and endpoints.

ATM Network Interfaces An ATM network consists of a set of ATM switches interconnected by point-topoint ATM links or interfaces. ATM switches support two primary types of interfaces: UNI and NNI. The UNI connects ATM end systems (such as hosts and routers) to an ATM switch. The NNI connects two ATM switches. Depending on whether the switch is owned and located at the customer's premises or publicly owned and operated by the telephone company, UNI and NNI can be further subdivided into public and private UNIs and NNIs. A private UNI connects an ATM endpoint and a private ATM switch. Its public counterpart connects an ATM endpoint or private switch to a public switch. A private NNI connects two ATM switches within the same private organization. A public one connects two ATM switches within the same public organization. An additional specification, the Broadband Interexchange Carrier Interconnect (B-ICI), connects two public switches from different service providers. Figure 20-4 illustrates the ATM interface specifications for private and public networks. Figure 20-4: ATM interface specifications differ for private and public networks.

ATM Cell-Header Format An ATM cell header can be one of two formats: UNI or the NNI. The UNI header is used for communication between ATM endpoints and ATM switches in private ATM networks. The NNI header is used for communication between ATM switches. Figure 20-4 depicts the basic ATM cell format, the ATM UNI cell-header format, and the ATM NNI cell-header format. Figure 20-5: An ATM cell, UNI cell, and ATM NNI cell header each contain 48 bytes of payload.

Unlike the UNI, the NNI header does not include the Generic Flow Control (GFC) field. Additionally, the NNI header has a Virtual Path Identifier (VPI) field that occupies the first 12 bits, allowing for larger trunks between public ATM switches. ATM Cell-Header Fields In addition to GFC and VPI header fields, several others are used in ATM cellheader fields. The following descriptions summarize the ATM cell-header fields illustrated in Figure 20-5:

Generic Flow Control (GFC)---Provides local functions, such as identifying multiple stations that share a single ATM interface. This field is typically not used and is set to its default value. Virtual Path Identifier (VPI)---In conjunction with the VCI, identifies the next destination of a cell as it passes through a series of ATM switches on the way to its destination. Virtual Channel Identifier (VCI)---In conjunction with the VPI, identifies the next destination of a cell as it passes through a series of ATM switches on the way to its destination. Payload Type (PT)---Indicates in the first bit whether the cell contains user data or control data. If the cell contains user data, the second bit indicates congestion, and the third bit indicates whether the cell is the

last in a series of cells that represent a single AAL5 frame.

Congestion Loss Priority (CLP)---Indicates whether the cell should be discarded if it encounters extreme congestion as it moves through the network. If the CLP bit equals 1, the cell should be discarded in preference to cells with the CLP bit equal to zero. Header Error Control (HEC)---Calculates checksum only on the header itself.

ATM Services Three types of ATM services exist: permanent virtual circuits (PVC), switched virtual circuits (SVC), and connectionless service (which is similar to SMDS). A PVC allows direct connectivity between sites. In this way, a PVC is similar to a leased line. Among its advantages, a PVC guarantees availability of a connection and does not require call setup procedures between switches. Disadvantages of PVCs include static connectivity and manual setup. An SVC is created and released dynamically and remains in use only as long as data is being transferred. In this sense, it is similar to a telephone call. Dynamic call control requires a signaling protocol between the ATM endpoint and the ATM switch. The advantages of SVCs include connection flexibility and call setup that can be handled automatically by a networking device. Disadvantages include the extra time and overhead required to set up the connection. ATM Virtual Connections ATM networks are fundamentally connection oriented, which means that a virtual channel (VC) must be set up across the ATM network prior to any data transfer. (A virtual channel is roughly equivalent to a virtual circuit.) Two types of ATM connections exist: virtual paths, which are identified by virtual path identifiers, and virtual channels, which are identified by the combination of a VPI and a virtual channel identifier (VCI). A virtual path is a bundle of virtual channels, all of which are switched transparently across the ATM network on the basis of the common VPI. All VCIs and VPIs, however, have only local significance across a particular link and are remapped, as appropriate, at each switch. A transmission path is a bundle of VPs. Figure 20-6 illustrates how VCs concatenate to create VPs, which, in turn, concatenate to create a transmission path. Figure 20-6: VC concatenate to create VPs.

ATM Switching Operations The basic operation of an ATM switch is straightforward: The cell is received across a link on a known VCI or VPI value. The switch looks up the connection value in a local translation table to determine the outgoing port (or ports) of the connection and the new VPI/VCI value of the connection on that link. The switch then retransmits the cell on that outgoing link with the appropriate connection identifiers. Because all VCIs and VPIs have only local significance across a particular link, these values are remapped, as necessary, at each switch. ATM Reference Model The ATM architecture uses a logical model to describe the functionality it supports. ATM functionality corresponds to the physical layer and part of the data link layer of the OSI reference model. The ATM reference model is composed of the following planes, which span all layers:

Control---This plane is responsible for generating and managing signaling requests. User--- This plane is responsible for managing the transfer of data. Management--- This plane contains two components Layer management manages layer-specific functions, such as the detection of failures and protocol problems. Plane management manages and coordinates functions related to the complete system.

The ATM reference model is composed of the following ATM layers:

Physical layer---Analogous to the physical layer of the OSI reference model, the ATM physical layer manages the medium-dependent transmission. ATM layer---Combined with the ATM adaptation layer, the ATM layer is roughly analogous to the data link layer of the OSI reference model. The ATM layer is responsible for establishing connections and passing cells through the ATM network. To do this, it uses information in the header of each ATM cell. ATM adaptation layer (AAL)---Combined with the ATM layer, the AAL is roughly analogous to the data data-link layer of the OSI model. The AAL is responsible for isolating higher-layer protocols from the details of the ATM processes.

Finally, the higher layers residing above the AAL accept user data, arrange it into packets, and hand it to the AAL. Figure 20-7 illustrates the ATM reference model. Figure 20-7: The ATM reference model relates to the lowest two layers of the OSI reference model.

The ATM Physical Layer The ATM physical layer has four functions: bits are converted into cells, the transmission and receipt of bits on the physical medium are controlled, ATM cell boundaries are tracked, and cells are packaged into the appropriate types of frames for the physical medium. The ATM physical layer is divided into two parts: the physical mediumdependent (PMD) sublayer and the transmission-convergence (TC) sublayer. The PMD sublayer provides two key functions. First, it synchronizes transmission and reception by sending and receiving a continuous flow of bits with associated timing information. Second, it specifies the physical media for the physical medium used, including connector types and cable. Examples of physical medium standards for ATM include Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH), DS-3/E3, 155 Mbps over multimode fiber (MMF) using the 8B/10B encoding scheme, and 155 Mbps 8B/10B over shielded twisted-pair (STP) cabling. The TC sublayer has four functions: cell dilineation, header error-control (HEC) sequence generation and verification, cell-rate decoupling, and transmission-frame adaptation. The cell delineation function maintains ATM cell boundaries, allowing devices to locate cells within a stream of bits. HEC sequence generation and verification generates and checks the header errorcontrol code to ensure valid data. Cell-rate decoupling maintains synchronization and inserts or suppresses idle (unassigned) ATM cells to adapt the rate of valid ATM cells to the payload capacity of the transmission system. Transmission frame adaptation packages ATM cells into frames

acceptable to the particular physical-layer implementation. ATM Adaptation Layers: AAL1 AAL1, a connection-oriented service, is suitable for handling circuit-emulation applications, such as voice and video conferencing. Circuit-emulation service also accommodates the attachment of equipment currently using leased lines to an ATM backbone network. AAL1 requires timing synchronization between the source and destination. For this reason, AAL1 depends on a medium, such as SONET, that supports clocking. The AAL1 process prepares a cell for transmission in three steps. First, synchronous samples (for example, 1 byte of data at a sampling rate of 125 microseconds) are inserted into the Payload field. Second, Sequence Number (SN) and Sequence Number Protection (SNP) fields are added to provide information that the receiving AAL1 uses to verify that it has received cells in the correct order. Third, the remainder of the Payload field is filled with enough single bytes to equal 48 bytes. Figure 20-8 illustrates how AAL1 prepares a cell for transmission. Figure 20-8: AAL1 prepares a cell for transmission so that the cells retain their order.

ATM Adaptation Layers: AAL3/4 AAL3/4 supports both connection-oriented and connectionless data. It was designed for network service providers and is closely aligned with Switched Multimegabit Data Service (SMDS). AAL3/4 is used to transmit SMDS packets over an ATM network. AAL3/4 prepares a cell for transmission in four steps. First, the convergence sublayer (CS) creates a protocol data unit (PDU) by prepending a beginning/end tag header to the frame and appending a length field as a trailer. Second, the segmentation and reassembly (SAR) sublayer fragments the PDU and prepends a header to it. Then, the SAR sublayer appends a CRC-10 trailer to each PDU fragment for error control. Finally, the completed SAR PDU becomes the Payload field of an ATM cell to which the ATM layer prepends the standard ATM header. An AAL 3/4 SAR PDU header consists of Type, Sequence Number, and Multiplexing Identifier fields. Type fields identify whether a cell is the beginning, continuation, or end of a message. Sequence number fields

identify the order in which cells should be reassembled. The Multiplexing Identifier field determines which cells from different traffic sources are interleaved on the same virtual circuit connection (VCC) so that the correct cells are reassembled at the destination. ATM Adaptation Layers: AAL5 AAL5 is the primary AAL for data and supports both connection-oriented and connectionless data. It is used to transfer most non-SMDS data, such as classical IP over ATM and LAN Emulation (LANE). AAL5 also is known as the simple and efficient adaptation layer (SEAL) because the SAR sublayer simply accepts the CS-PDU and segments it into 48-octet SAR-PDUs without adding any additional fields. AAL5 prepares a cell for transmission in three steps. First, the CS sublayer appends a variable-length pad and an 8-byte trailer to a frame. The pad ensures that the resulting PDU falls on the 48-byte boundary of an ATM cell. The trailer includes the length of the frame and a 32-bit cyclic redundancy check (CRC) computed across the entire PDU. This allows the AAL5 receiving process to detect bit errors, lost cells, or cells that are out of sequence. Second, the SAR sublayer segments the CS-PDU into 48-byte blocks. A header and trailer are not added (as is in AAL3/4), so messages cannot be interleaved. Finally, the ATM layer places each block into the Payload field of an ATM cell. For all cells except the last, a bit in the Payload Type (PT) field is set to zero to indicate that the cell is not the last cell in a series that represents a single frame. For the last cell, the bit in the PT field is set to one. ATM Addressing The ITU-T standard is based on the use of E.164 addresses (similar to telephone numbers) for public ATM (BISDN) networks. The ATM Forum extended ATM addressing to include private networks. It decided on the subnetwork or overlay model of addressing, in which the ATM layer is responsible for mapping network-layer addresses to ATM addresses. This subnetwork model is an alternative to using network-layer protocol addresses (such as IP and IPX) and existing routing protocols (such as IGRP and RIP). The ATM Forum defined an address format based on the structure of the OSI network service access point (NSAP) addresses. Subnetwork Model of Addressing The subnetwork model of addressing decouples the ATM layer from any existing higher-layer protocols, such as IP or IPX. Therefore, it requires an entirely new addressing scheme and routing protocol. Each ATM system must be assigned an ATM address, in addition to any higher-layer protocol addresses. This requires an ATM address resolution protocol (ATM ARP) to map higher-layer addresses to their corresponding ATM addresses. NSAP Format ATM Addresses The 20-byte NSAP-format ATM addresses are designed for use within private ATM networks, whereas public networks typically use E.164 addresses, which are formatted as defined by ITU-T. The ATM Forum has specified an NSAP encoding for E.164 addresses, which is used for encoding E.164 addresses within private networks, but this address can also be used by some private networks. Such private networks can base their own (NSAP format) addressing on the

E.164 address of the public UNI to which they are connected and can take the address prefix from the E.164 number, identifying local nodes by the lowerorder bits. All NSAP-format ATM addresses consist of three components: the authority and format identifier (AFI), the initial domain identifier (IDI), and the domain specific part (DSP). The AFI identifies the type and format of the IDI, which, in turn, identifies the address allocation and administrative authority. The DSP contains actual routing information. Three formats of private ATM addressing differ by the nature of the AFI and IDI. In the NSAP-encoded E.164 format, the IDI is an E.164 number. In the DCC format, the IDI is a data country code (DCC), which identifies particular countries, as specified in ISO 3166. Such addresses are administered by the ISO National Member Body in each country. In the ICD format, the IDI is an international code designator (ICD), which is allocated by the ISO 6523 registration authority (the British Standards Institute). ICD codes identify particular international organizations. The ATM Forum recommends that organizations or private-network service providers use either the DCC or ICD formats to form their own numbering plan. Figure 20-9 illustrates the three formats of ATM addresses used for private networks. Figure 20-9: Three formats of ATM addresses are used for private networks.

ATM Address Fields The following descriptions summarize the fields illustrated in Figure 20-9:

AFI---Identifies the type and format of the address (DCC, ICD, or

E.164).

DCC---Identifies particular countries. High-Order Domain Specific Part (HO-DSP)---Combines the routing domain (RD) and area indentifier (AREA) of the NSAP addresses. The ATM Forum combined these fields to support a flexible, multilevel addressing hierarchy for prefix-based routing protocols End System Identifier (ESI)---Specifies the 48-bit MAC address, as administered by the Institute of Electrical and Electronic Engineers (IEEE). Selector (SEL)---Used for local multiplexing within end stations and has no network significance. ICD---Identifies particular international organizations. E.164---Indicates the BISDN E.164 address.

ATM Connections ATM supports two types of connections: point-to-point and point-to-multipoint. Point-to-point connects two ATM end systems and can be unidirectional (oneway communication) or bidirectional (two-way communication). Point-tomultipoint connects a single-source end system (known as the root node) to multiple destination end systems (known as leaves). Such connections are unidirectional only. Root nodes can transmit to leaves, but leaves cannot transmit to the root or each other on the same connection. Cell replication is done within the ATM network by the ATM switches where the connection splits into two or more branches. It would be desirable in ATM networks to have bidirectional multipoint-tomultipoint connections. Such connections are analogous to the broadcasting or multicasting capabilities of shared-media LANs, such as Ethernet and Token Ring. A broadcasting capability is easy to implement in shared-media LANs, where all nodes on a single LAN segment must process all packets sent on that segment. Unfortunately, a multipoint-to-multipoint capability cannot be implemented by using AAL5, which is the most common AAL to transmit data across an ATM network. Unlike AAL3/4, with its Message Identifier (MID) field, AAL5 does not provide a way within its cell format to interleave cells from different AAL5 packets on a single connection. This means that all AAL5 packets sent to a particular destination across a particular connection must be received in sequence; otherwise, the destination reassembly process will be unable to reconstruct the packets. This is why AAL5 point-to-multipoint connections can be only unidirectional. If a leaf node were to transmit an AAL5 packet onto the connection, for example, it would be received by both the root node and all other leaf nodes. At these nodes, the packet sent by the leaf could be interleaved with packets sent by the root and possibly other leaf nodes, precluding the reassembly of any of the interleaved packets. ATM and Multicasting

ATM requires some form of multicast capability. AAL5 (which is the most common AAL for data) currently does not support interleaving packets, so it does not support multicasting. If a leaf node transmitted a packet onto an AAL5 connection, the packet can get intermixed with other packets and be improperly reassembled. Three methods have been proposed for solving this problem: VP multicasting, multicast server, and overlaid point-to-multipoint connection. Under the first solution, a multipoint-to-multipoint VP links all nodes in the multicast group, and each node is given a unique VCI value within the VP. Interleaved packets hence can be identified by the unique VCI value of the source. Unfortunately, this mechanism would require a protocol to uniquely allocate VCI values to nodes, and such a protocol mechanism currently does not exist. It is also unclear whether current SAR devices could easily support such a mode of operation. A multicast server is another potential solution to the problem of multicasting over an ATM network. In this scenario, all nodes wanting to transmit onto a multicast group set up a point-to-point connection with an external device known as a multicast server (perhaps better described as a resequencer or serializer). The multicast server, in turn, is connected to all nodes wanting to receive the multicast packets through a point-to-multipoint connection. The multicast server receives packets across the point-to-point connections and then retransmits them across the point-to-multipoint connection---but only after ensuring that the packets are serialized (that is, one packet is fully transmitted prior to the next being sent). In this way, cell interleaving is precluded. An overlaid point-to-multipoint connection is the third potential solution to the problem of multicasting over an ATM network. In this scenario, all nodes in the multicast group establish a point-to-multipoint connection with each other node in the group and, in turn, become leaves in the equivalent connections of all other nodes. Hence, all nodes can both transmit to and receive from all other nodes. This solution requires each node to maintain a connection for each transmitting member of the group, whereas the multicast-server mechanism requires only two connections. This type of connection would also require a registration process for informing the nodes that join a group of the other nodes in the group so that the new nodes can form the point-tomultipoint connection. The other nodes must know about the new node so that they can add the new node to their own point-to-multipoint connections. The multicast-server mechanism is more scalable in terms of connection resources but has the problem of requiring a centralized resequencer, which is both a potential bottleneck and a single point of failure. ATM Quality of Service (QoS) ATM supports QoS guarantees composed of traffic contract, traffic shaping, and traffic policing. A traffic contract specifies an envelope that describes the intended data flow. This envelope specifies values for peak bandwidth, average sustained bandwidth, and burst size, among others. When an ATM end system connects to an ATM network, it enters a contract with the network, based on QoS parameters. Traffic shaping is the use of queues to constrain data bursts, limit peak data rate, and smooth jitters so that traffic will fit within the promised envelope. ATM devices are responsible for adhering to the contract by means of traffic

shaping. ATM switches can use traffic policing to enforce the contract The switch can measure the actual traffic flow and compare it against the agreedupon traffic envelope. If the switch finds that traffic is outside of the agreedupon parameters, it can set the cell-loss priority (CLP) bit of the offending cells. Setting the CLP bit makes the cell discard eligible, which means that any switch handling the cell is allowed to drop the cell during periods of congestion. ATM Signaling and Connection Establishment When an ATM device wants to establish a connection with another ATM device, it sends a signaling-request packet to its directly connected ATM switch. This request contains the ATM address of the desired ATM endpoint, as well as any QoS parameters required for the connection. ATM signaling protocols vary by the type of ATM link, which can be either UNI signals or NNI signals. UNI is used between an ATM end system and ATM switch across ATM UNI, and NNI is used across NNI links. The ATM Forum UNI 3.1 specification is the current standard for ATM UNI signaling. The UNI 3.1 specification is based on the Q.2931 public network signaling protocol developed by the ITU-T. UNI signaling requests are carried in a well-known default connection: VPI = 0, VPI = 5. Standards currently exist only for ATM UNI signaling, but standardization work is continuing on NNI signaling. The ATM Connection-Establishment Process ATM signaling uses the one-pass method of connection setup that is used in all modern telecommunication networks, such as the telephone network. An ATM connection setup proceeeds in the following manner. First, the source end system sends a connection-signaling request. The connection request is propagated through the network. As a result, connections are set up through the network. The connection request reaches the final destination, which either accepts or rejects the connection request. Connection-Request Routing and Negotiation Routing of the connection request is governed by an ATM routing protocol (which routes connections based on destination and source addresses), traffic, and the QoS parameters requested by the source end system. Negotiating a connection request that is rejected by the destination is limited because call routing is based on parameters of initial connection; changing parameters might, in turn, affect the connection routing. Figure 20-10 highlights the one-pass method of ATM connection establishment. Figure 20-10: ATM devices establish connections through the one-pass method.

ATM Connection-Management Messages A number of connection- management message types, including setup, call proceeding, connect, and release, are used to establish and tear down an ATM connection. The source end end-system sends a setup message (including the destination end-system address and any traffic QoS parameters) when it wants to set up a connection. The ingress switch sends a call proceeding message back to the source in response to the setup message. The destination end system next sends a connect message if the connection is accepted. The destination end system sends a release message back to the source end system if the connection is rejected, thereby clearing the connection. Connection-management messages are used to establish an ATM connection in the following manner. First, a source end system sends a setup message, which is forwarded to the first ATM switch (ingress switch) in the network. This switch sends a call proceeding message and invokes an ATM routing protocol. The signaling request is propagated across the network. The exit switch (called the egress switch) that is attached to the destination end system receives the setup message. The egress switch forwards the setup message to the end system across its UNI, and the ATM end system sends a connect message if the connection is accepted. The connect message traverses back through the network along the same path to the source end system, which sends a connect acknowledge message back to the destination to acknowledge the connection. Data transfer can then begin. LAN Emulation (LANE) LANE is a standard defined by the ATM Forum that gives to stations attached via ATM the same capabilities they normally obtain from legacy LANs, such as Ethernet and Token Ring. As the name suggests, the function of the LANE protocol is to emulate a LAN on top of an ATM network. Specifically, the LANE protocol defines mechanisms for emulating either an IEEE 802.3 Ethernet or an 802.5 Token Ring LAN. The current LANE protocol does not define a separate encapsulation for FDDI. (FDDI packets must be mapped into either Ethernet or Token Ring emulated LANs [ELANs] by using existing translational bridging techniques.) Fast Ethernet (100BaseT) and IEEE 802.12 (100VG-AnyLAN) both can be mapped unchanged because they use the same packet formats. Figure 20-11 compares a physical LAN and an ELAN. Figure 20-11: ATM networks can emulate a physical LAN.

The LANE protocol defines a service interface for higher-layer (that is, network layer) protocols that is identical to that of existing LANs. Data sent across the ATM network is encapsulated in the appropriate LAN MAC packet format. Simply put, the LANE protocols make an ATM network look and behave like an Ethernet or Token Ring LAN---albeit one operating much faster than an actual Ethernet or Token Ring LAN network. It is important to note that LANE does not attempt to emulate the actual MAC protocol of the specific LAN concerned (that is, CSMA/CD for Ethernet or token passing for IEEE 802.5). LANE requires no modifications to higher-layer protocols to enable their operation over an ATM network. Because the LANE service presents the same service interface of existing MAC protocols to network-layer drivers (such as an NDIS- or ODI-like driver interface), no changes are required in those drivers. The LANE Protocol Architecture The basic function of the LANE protocol is to resolve MAC addresses to ATM addresses. The goal is to resolve such address mappings so that LANE end systems can set up direct connections between themselves and then forward data. The LANE protocol is deployed in two types of ATM-attached equipment: ATM network interface cards (NICs) and internetworking and LAN switching equipment. ATM NICs implement the LANE protocol and interface to the ATM network but present the current LAN service interface to the higher-level protocol drivers within the attached end system. The network-layer protocols on the end system continue to communicate as if they were on a known LAN by using known procedures. However, they are able to use the vastly greater bandwidth of ATM networks. The second class of network gear to implement LANE consists of ATMattached LAN switches and routers. These devices, together with directly attached ATM hosts equipped with ATM NICs, are used to provide a virtual LAN (VLAN) service in which ports on the LAN switches are assigned to particular VLANs independently of physical location. Figure 20-12 shows the LANE protocol architecture implemented in ATM network devices.: Figure 20-12: LANE protocol architecture can be implemented in ATM network devices.

Note The LANE protocol does not directly affect ATM switches. LANE, as with most of the other ATM internetworking protocols, builds on the overlay model. As such, the LANE protocols operate transparently over and through ATM switches, using only standard ATM signaling procedures. LANE Components The LANE protocol defines the operation of a single ELAN or VLAN. Although multiple ELANs can simultaneously exist on a single ATM network, an ELAN emulates either an Ethernet or a Token Ring and consists of the following components:

LAN emulation client (LEC)---The LEC is an entity in an end system that performs data forwarding, address resolution, and registration of MAC addresses with the LAN emulation server (LES). The LEC also provides a standard LAN interface to higher-level protocols on legacy LANs. An ATM end system that connects to multiple ELANs has one LEC per ELAN.

LES---The LES provides a central control point for LECs to forward registration and control information. (Only one LES exists per ELAN.) Broadcast and unknown server (BUS)---The BUS is a multicast server that is used to flood unknown destination address traffic and to forward multicast and broadcast traffic to clients within a particular ELAN. Each LEC is associated with only one BUS per ELAN. LAN emulation configuration server (LECS)---The LECS maintains a database of LECs and the ELANs to which they belong. This server accepts queries from LECs and responds with the appropriate ELAN identifier, namely the ATM address of the LES that serves the appropriate ELAN. One LECS per administrative domain serves all ELANs within that domain.

Figure 20-13 illustrates the components of an ELAN.: Figure 20-13: An ELAN consists of clients, servers, and various intermediate nodes.

LAN Emulation Connection Types The Phase 1 LANE entities communicate with each other by using a series of ATM VCCs. LECs maintain separate connections for data transmission and control traffic. The LANE data connections are data-direct VCC, multicast send VCC, and multicast forward VCC. Data-direct VCC is a bidirectional point-to-point VCC set up between two LECs that want to exchange data. Two LECs typically use the same datadirect VCC to carry all packets between them rather than opening a new VCC for each MAC address pair. This technique conserves connection resources and connection setup latency. Multicast send VCC is a bidirectional point-to-point VCC set up by the LEC to the BUS. Multicast forward VCC is a unidirectional VCC set up to the LEC from the BUS. It typically is a point-to-multipoint connection, with each LEC as a leaf. Figure 20-14 shows the LANE data connections. Figure 20-14: LANE data connections use a series of VCLs to link a LAN switch and ATM hosts.

Control connections include configuration-direct VCC, control-direct VCC, and control-distribute VCC. Configuration-direct VCC is a bidirectional point-topoint VCC set up by the LEC to the LECS. Control-direct VCC is a bidirectional VCC set up by the LEC to the LES. Control-distribute VCC is a unidirectional VCC set up from the LES back to the LEC (this is typically a point-to-multipoint connection). Figure 20-15 illustrates LANE control connections. Figure 20-15: LANE control connections link the LES, LECS, LAN switch, and ATM host.

LANE Operation The operation of a LANE system and components is best understood by examining these stages of LEC operation: intialization and configuration, ; joining and registering with the LES, ; finding and joining the BUS, ; and data transfer. Initialization and Configuration Upon initialization, an LEC finds the LECs to obtain required configuration information. It begins this process when the LEC obtains its own ATM address, which typically occurs through address registration. The LEC must then determine the location of the LECS. To do this, the LEC first must locate the LECS by one of the following methods: by using a defined ILMI procedure to determine the LECS address, by using a well-known LECS address, or by using a well-known permanent connection to the LECS (VPI = 0, VCI = 17). When the LECS is found, the LEC sets up a configuration-direct VCC to the LECS and sends a LE_CONFIGURE_REQUEST. If a matching entry is found, the LECS returns a LE_CONFIGURE_RESPONSE to the LEC with the configuration information it requires to connect to its target ELAN, including the following: ATM address of the LES, type of LAN being emulated, maximum packet size on the ELAN, and ELAN name (a text string for display

purposes). Joining and Registering with the LES When an LEC joins the LES and registers its own ATM and MAC addresses, it does so by following three steps:. 1. After the LEC obtains the LES address, the LEC optionally clears the connection to the LECS, sets up the control-direct VCC to the LES, and sends an LE_JOIN_REQUEST on that VCC. This allows the LEC to register its own MAC and ATM addresses with the LES and (optionally) any other MAC addresses for which it is proxying. This information is maintained so that no two LECs will register the same MAC or ATM address. 2. After receipt of the LE_JOIN_REQUEST, the LES checks with the LECS via its open connection, verifies the request, and confirms the client's membership. 3. Upon successful verification, the LES adds the LEC as a leaf of its point-to-multipoint control-distribute VCC and issues the LEC a successful LE_JOIN_RESPONSE that contains a unique LAN Emulation Client ID (LECID). The LECID is used by the LEC to filter its own broadcasts from the BUS. Finding and Joining the BUS After the LEC has successfully joined the LECS, its first task is to find the BUS/s ATM address to join the broadcast group and become a member of the emulated LAN. First, the LEC creates an LE_ARP_REQUEST packet with the MAC address 0xFFFFFFFF. Then the LEC sends this special LE_ARP packet on the control-direct VCC to the LES. The LES recognizes that the LEC is looking for the BUS and responds with the BUS's ATM address on the control- distribute VCC. When the LEC has the BUS's ATM address, it joins the BUS by first creating a signaling packet with the BUS's ATM address and setting up a multicast-send VCC with the BUS. Upon receipt of the signaling request, the BUS adds the LEC as a leaf on its point-to-multipoint multicast forward VCC. The LEC is now a member of the ELAN and is ready for data transfer. Data Transfer The final state, data transfer, involves resolving the ATM address of the destination LEC and actual data transfer, which might include the flush procedure. When a LEC has a data packet to send to an unknown-destination MAC address, it must discover the ATM address of the destination LEC through which the particular address can be reached. To accomplish this, the LEC first sends the data frame to the BUS (via the multicast send VCC) for distribution to all LECs on the ELAN via the multicast forward VCC. This is done because resolving the ATM address might take some time, and many network protocols are intolerant of delays. The LEC then sends a LAN Emulation Address Resolution Protocol Request

(LE_ARP_Request) control frame to the LES via a control-direct VCC. If the LES knows the answer, it responds with the ATM address of the LEC that owns the MAC address in question. If the LES does not know the answer, it floods the LE_ARP_REQUEST to some or all LECs (under rules that parallel the BUS's flooding of the actual data frame, but over control-direct and control-distribute VCCs instead of the multicast send or multicast forward VCCs used by the BUS). If bridge/switching devices with LEC software participating in the ELAN exist, they translate and forward the ARP on their LAN interfaces. In the case of actual data transfer, if an LE_ARP is received, the LEC sets up a data-direct VCC to the destination node and uses this for data transfer rather than the BUS path. Before it can do this, however, the LEC might need to use the LANE flush procedure, which ensures that all packets previously sent to the BUS were delivered to the destination prior to the use of the datadirect VCC. In the flush procedure, a control cell is sent down the first transmission path following the last packet. The LEC then waits until the destination acknowledges receipt of the flush packet before using the second path to send packets.

Get this document in PDF form

Home | Search | About | Offices | Manufacturers | Products | Services | Ordering Data101 | Mailing | Employment | Email

Tel: (toll free): 888-785-7393 Int'l: 1-951-694-1173 Fax: 1-951-6941176 Copyright 2011 [Pulse, Inc.]. All rights reserved.

ATM
Alon beizer & Alon shulchami December 1996

Welcome to Asynchrono us Transfer Mode

Index
What is ATM ? Adventages of ATM Disadventages of ATM How does an ATM packet look like ? ATM layers ATM Services ATM Routing Example A look at ATM network Quality Of Service Where is ATM ? Dictionary (taken from the ATM-forum homepage)

What is ATM ?
ATM stands for "Asynchronous Transfer Mode". It is primarily driven by telecommunications companies and is a proposed telecommunications standard for Broadband ISDN. ATM has been accepted universally as the transfer mode of choice for Broadband Integrated Services Digital Networks(BISDN). ATM can handle any kind of information i.e. voice, data, image, text and video in an integrated manner. ATM provides a good bandwidth flexibility and can be used efficiently from desktop computers to local area and wide area networks. In order to understand what ATM is all about, a brief introduction to STM is in order. ATM is the complement of STM which stands for "Synchronous Transfer Mode". The telecommunications companies are investigating fiber optic cross country and cross oceanic links with Gigabit/sec speeds, and would like to carry in an integrated way, both real time traffic such as voice and hi-res video which can tolerate some loss but not delay, as well as non real time traffic such as computer data and file transfer which may tolerate some delay but not loss. The problem with carrying these different characteristics of traffic on the same medium in an integrated fashion is that the peak bandwidth requirement of these traffic sources may be quite high as in high-res full motion video, but the duration for which the data is actually transmitted may be quite small. In other words, the data comes in

bursts and must be transmitted at the peak rate of the burst, but the average arrival time between bursts may be quite large and randomly distributed. For such bursty connections, it would be a considerable waste of bandwidth to reserve them a bucket at their peak bandwidth rate for all times, when on the average only 1 in 10 bucket may actually carry the data. It would be nice if that bucket could be reused for another pending connection. And thus using STM mode of transfer becomes inefficient as the peak bandwidth of the link, peak transfer rate of the traffic, and overall burstiness of the traffic expressed as a ratio of peak/average, all go up. In the judgement of the industry pundits, this is definitely the indicated trend for multimedia integrated telecommunications and data communications demands of global economies in the late 90's and early 21st century. Hence ATM is conceived. It was independently proposed by Bellcore, the research arm of AT&T in the US, and several giant telecommunications companies in Europe, which is why there may be two possible standards in the future. The main idea here was to say, instead of always identifying a connection by the bucket number, just carry the connection identifier along with the data in any bucket, and keep the size of the bucket small so that if any one bucket got dropped enroute due to congestion, not too much data would get lost, and in some cases could easily be recovered. And this sounded very much like packet switching, so they called it "Fast packet switching with short fixed length packets." And the fixed size of the packets arose out of hidden motivation from the telecommunications companies to sustain the same transmitted voice quality as in STM networks, but in the presence of some lost packets on ATM networks. Thus two end points in an ATM network are associated with each other via an identifier called the "Virtual Circuit Identifier" (VCI label) instead of by a time-slot or bucket number as in a STM network. The VCI is carried in the header portion of the fast packet. The fast packet itself is carried in the same type of bucket as before, but there is no label or designation for the bucket anymore. The terms fast packet, cell, and bucket are used interchangeably in ATM literature and refer to the same thing.

Adventages of ATM

Fast packet switching is attempting to solve the unused bucket problem of STM by statistically multiplexing several connections on the same link based on their traffic characteristics. In other words, if a large number of connections are very bursty (i.e. their peak/average ratio is 10:1 or higher), then all of them may be assigned to the same link in the hope that statistically they will not all burst at the same time. And if some of them do burst simultaneously, that that there is sufficient elasticity that the burst can be buffered up and put in subsequently available free buckets. This is called statistical multiplexing, and it allows the sum of the peak bandwidth requirement of all connections on a link to even exceed the aggregate available bandwidth of the link under certain conditions of discipline. This was impossible on an STM network, and it is the main distinction of an ATM network.

ATM has several key benefits:

One Network-ATM will provide a single network for all traffic types-voice, data, video. ATM allows for the integration of networks improving efficiency and manageability. Enables new applications-Due to its high speed and the integration of traffic types, ATM will enable the creation and expansion of new applications such as multimedia to the desktop. Compatibility-Because ATM is not based on a specific type of physical transport, it is compatible with currently deployed physical networks. ATM can be transported over twisted pair, coax and fiber optics. Incremental Migration-Efforts within the standards organizations and the ATM Forum continue to assure that embedded networks will be able to gain the benefits of ATM incrementally-upgrading portions of the network based on new application requirements and business needs. Simplified Network Management-ATM is evolving into a standard technology for local, campus/backbone and public and private wide area services. This uniformity is intended to simplify network management by using the same

technology for all levels of the network. Long Architectural Lifetime-The information systems and telecommunications industries are focusing and standardizing on ATM. ATM has been designed from the onset to be scalable and flexible in: Geographic distance Number of users Access and trunk bandwidths (As of today, the speeds range from Megabits to Gigabits) This flexibility and scalability assures that ATM will be around for a long time.

DisAdventages of ATM

Overhead of cell header (5 bytes per cell). Complex mechanisms for achieveing QoS (Quallity of Service). Congestion may cause cell losses.

How does an ATM packet look like ?

An ATM cell or packet as specified by T1S1 sub-committee is 53 bytes.5 bytes comprise the header, and 48 bytes are payload. The header and payload are specified as follows:

Figure 1:ATM Cell Structure

The structure of ATM cells at NNI

CLP HEC PTI VCI VPI

Cell Loss Priority 1 bit Header Error Control 8 bits Payload Type Identifier 3 bits Virtual Channel Identifier 16 bits Virtual Path Identifier 12 bits

Figure 2: The Structure of ATM cells at NNI The 48 bytes of payload may optionally contain a 4 byte ATM adaptation layer and 44 bytes of actual data, or all 48 bytes may be data, based on a bit in the control field of the header. This enables fragmentation and reassembly of cells into larger packets at the source and destination respectively. (Since the header definition may still be in flux, it is possible that presense or absence of an adaptation layer information may not be explicitly indicated with a bit in the header, but rather implicitly derived from the VCI label). The control field may also contain a bit to specify whether this is a flow control cell or an ordinary cell, an advisory bit to indicate whether this cell is dropable in the face of congestion in the network or not, etc. The ETSI definition of an ATM cell is similar, 53 bytes cell size, 5 byte header, 48 bytes data. However the difference is in number of bits for the VCI field, number of bits in the header checksum, and semantics and number of some of the control bits.

ATM layers
As is probably evident by now, ATM is designed for switching short fixed length packets in hardware over Gigabit/sec links across very large distances. Thus its place in the protocol stack concept is somewhere around the data link layer. However it does not cleanly fit in to the abstract layered model, because within the ATM network

itself, end-to-end connection, flow control, and routing are all done at the ATM cell level. So there are a few aspects of traditional higher layer functions present in it. In the OSI reference model, it would be considered layer 2 (where layer 1 is the physical layer and layer 2 is the datalink layer in the internet protocol stack). But it is not very important to assign a clean layer name to ATM, so long as it is recognized that it is a hardware implemented packet switched protocol using 53 byte fixed length packets. What is perhaps more relevant is how will all this interact with current TCP/IP and IP networks in general, and with applications which want to talk ATM directly in particular. A convenient model for an ATM interface is to consider it another communications port in the system. Thus from a system software point of view, it can be treated like any other data link layer port. Thus for instance, in IP networks connected via gateways to ATM backbones, the model would be no different then it presently is for a virtual circuit connection carried over an STM link except that an IP packet over an ATM network would get fragmented into cells at the transmitting UNI, and reassembled into the IP packet at the destination UNI. Thus a typical protocol stack might look like this:
-------------------Data -------------------TCP -------------------IP -------------------ATM Adaptation Layer -------------------ATM Datalink layer -------------------Physical Layer (SONET STS-3c STS-12 STS-48) --------------------

Thus, just like an ethernet port on a host is assigned an IP address, the ATM port may also be assigned an IP address. Thus the IP software in a router decides which port to send a packet to based on the IP address, and hands the packet to the port. The port then does the right thing with it. For an ethernet port, the ethernet header is tacked on and the Frame transmitted in ethernet style. Similarly, for an ATM port, the IP datagram is fragmented into cells for which an ATM adaptation layer is specified in the standards. The

fragmentation and reassembly is done in hardware on the sending and receiving sides. A VCI label acquired via an initial one time connection establishment phase, is placed in the header of each cell, and the cells are drained down the fat ATM datalink layer pipe. On the receiving side, the cells are reassembled in hardware using the ATM adaptation layer, and the original IP packet is reformulated and handed to the receiving host on the UNI. The adaptation layer is not a separate header, but is actually carried in the payload section of the ATM cell as discussed earlier.

Figure 3: Comparison of ATM Protocol Architecture to Sevem Layer OSI Model

For direct interface to an ATM cell stream from an application, new interfaces have to be designed in the software that can provide the application with nice and fast mechanisms for connection establishment, data transfer, keep alive, tear down, and even application level flow control. In this case the software processing steps may look like this:
--------------------------Application Streaming Data --------------------------OS interface to application --------------------------ATM virtual circuit management/signalling --------------------------Driver interface to ATM --------------------------ATM ---------------------------

where the ATM virtual circuit management represents software which understands the ATM header specifics, sets up and tears down connections, does demultiplexing of the payload to appropriate connections, and responds to whatever standard signalling protocol is employed by the ATM interface at the UNI for connection management.

ATM SERVICES
ATM Layer Switching Functions at the UNI
The ATM layer is responsible for a number of functions as defined in the ATM Forum UNI specification 3.0. These functions include:

Multiplexing connections Cell rate decoupling Cell discrimination Payload type discrimination Loss priority Traffic shaping

Multiplexing is done among different ATM connections on a given link in order to provide a specific QoS for each user as defined during call setup. Cell rate decoupling is done to provide a constant bit stream to the physical layer. Since ATM is asynchronous, there are not always packets that need to be transferred. However, a physical transport such as SONET is synchronous and requires a constant bit stream. Therefore, the ATM layer outputs cells with VCI-0 and CLP-1 into the data stream to assure a continuous bit stream. Cells with these values for VCI and CLP are defined to be unassigned cells. Cell discrimination is necessary to detect unassigned cells as well as cells used for management. This discrimination is done according to the header information in the cell. The first 4 bytes of the header, namely the GFC, VPI, VPI, PT, and CLP fields, are used to distinguish different types of management information. The Metasignaling cells are used to establish and release virtual connections. The General Broadcast cells broadcast signaling information regardless for the service profile. The point to point signaling cells are used just for that. Finally, the OAM F4 flow cells are used by ATM layer management for management on the virtual path (VP) level. Payload type discrimination is similar to the cell discrimination but only deals with the PT field. The main purpose of this discrimination is to distinguish between user data cells and management cells. The OAM F5 flow cells are similar to the F4 and are used by the ATM layer management for management on the virtual channel (VC) level. The cell loss priority uses the CLP field in the ATM header to determine if a cell is discardable under heavy traffic flow conditions. A logical 0 for the CLP is high priority, while a logical 1 is low priority. Traffic shaping is used to get a specific characteristics for the stream of cells entering into a virtual channel or virtual path connection, (VCC or VPC). ATM Layer Management Functions at the UNI

The ATM layer management functions as defined by the ATM Forum UNI specification are basically used for two functions: fault management, and local management interfacing information. Fault management includes:

Alarm surveillance Connectivity verification Invalid VPI/VCI detection

These functions are accomplished using Operation and Maintenance (OAM) cells to exchange related operation information. Alarm surveillance consists of the detection, generation and propagation of VPC/VCC failures. The alarms generated to inform other switches are sent through the OAM F4 or F5 cells. The connectivity verification is an OAM function that allows the switch to perform a loop-back test on a link using a specific loopback cell. This cell is again of the OAM F4 or F5 type and can be specified to loop-back at any node throughout a connection. the invalid VPI/VCI detection merely detects incorrect VPI/VCI in a cell header and if not correctable using the HEC, discards the cells.

ATM Routing example

Preview : ATM is connection oriented. Before information is transfered from the terminal to the network, a logical/virtual connection is set. The header values are assigned to each section of a connection for the complete duration of connection, and translated when switched from one section to another. Signalling and user information are carried on separate virtual channel. Two sorts of connections are possible: * Virtual Channel Connections VCC *, Virtual Path Connections VPC. When switching or multiplexing on cells is to be performed, it must first be done on VPC ,then on the VCC. Virtual Channels This function is performed by a header sub field VCI. Since the ATM network is connection orriented each connection is characterized by a VCI which is assigned at call set up.

A VCI has only a local significance on the link between ATM node and will be translated in the ATM nodes. When the connection is released , the VCI values on the involved links will be released and can be reused by other connections. An advantage of this VCI principle is the use of multiple VCI values for multicomponent services. For instance video telephony can be composed of 3 components: voice , video and data each of which will be transported over a seperate VCI. This allows the network to add or remove components during the connection. For instance, the video telephony service can start with voice only and the video can be added later. Virtual Path The network has to support semi-permanent connections, which have to transport a large number of simultaneous connections. This concept is known as virtual path. All ATM switches can be schematically described as follows. A number of n coming links ( I1,I2,..In) transport ATM information to the switch, where depending on the value of the header this information is switched to outgoing ling (O1,O2,..On). The incoming header and the incoming link number are used to access a translation table. The result of the acces to the table is an outgoing link and a new header value. The basic operation of an ATM switch is very simple: to receive a cell across a link on a known VCI or VPI value; to look up the connection value in a local translation table to determine the outgoing port (or ports) of the connection and the new VPI/VCI value of the connection on that link; and to then retransmit the cell on that outgoing link with the appropriate connection identifiers.

Figure 4: ATM Switch Operations

The switch operation is so simple because external mechanisms set up the local translation tables prior to the transmittal of any data. Example: Assume an ATM network with nodes in TelAviv, NewYork, and Eilat. Say that Udi while vacationing in NY decides to play DukeNukem with his buddies in the above cities. Also assume that we have ATM cell interfaces at UNI's in NY Eilat and TA. This is what can happens: Udi's portable $4K laptop makes a connection request to the UNI in NY. After an exchange of connection parameters between his laptop and the UNI (such as destination, traffic type, peak and average bandwidth requirement, delay and cell loss requirement, how much money he has got left to spend, etc}, the UNI forwards the request to the network. The software running on the network computes a route based on the cost function specified by Udi, and figures out which links on each leg of the route can best support the requested quality of service and bandwidth. Then it sends a connection setup request to all the nodes in the path enroute to the destination node in TA. The route selected is NY--TA--E. Each of the two nodes might pick an unused VCI label on their respective nodes and reserve it for the connection in the connection lookup tables inside their respective switches. Say, NY picks VC1. It will send it to TA. TA in turn picks VC2, associates it with VC1 in its connection table, and forwards VC2 to E. E picks VC3 and associates it with VC2 in its connection tables, and pings the addressed UNI to see if it would accept this connection request. Fortunately, the UNI finds Udi's buddies and returns affirmative. So E hands the UNI and Udi's friends VC3 as a connection identifier for this connection. E then acks back to TA. TA puts VC3 in its connection tables to identify the path going in the reverse direction, and acks to NY sending it VC2. NY associates VC2 in its connection tables with VC1, and acks the originating UNI with VC1. The UNI hands Udi's laptop VC1 and connection is established. Udi identifies the connection with VCI label VC1, and his buddies identify the connection with VCI label VC3. The labels get translated at each node to the next outgoing label like so: NY TA E

Udi- VC1- VC2- VC3- Buddi > > > > es Udi< VC1 VC2 VC3 Buddi <<<es

Figure 5: Connection Setup through ATM Signaling (SVC) When Udi has had enough playing Aviator and wants to get back to some serious scuba diving off the Atlantic coast, the connection is torn down, and the VCI labels are resued for other connections.

A look at ATM Network

An ATM network consists of a set of ATM switches interconnected by point-to-point ATM links or interfaces. ATM switches support two kinds of interfaces: user-network interfaces (UNI) and network-node interfaces (NNI). UNI connect ATM end-systems (hosts, routers, and so on) to an ATM switch, while an NNI may be imprecisely defined as an interface connecting two ATM switches together; More precisely, however, an NNI is any physical or logical link across which two ATM switches exchange the NNI protocol. slightly different cell formats are defined across UNI and NNI

Figure 6: ATM Network Interfaces

Quality Of Service
ATM will provide a Quality Of Service ( QOS ) to connections. During connection set-up there is a need to find agreement between the user and the network on what QOS is required by that connection. The user will initiate a connection request to the network for a connection. The signalling would involve the user passing traffic parameters to the network, which is carried in the ATM user cell rate information element. Here the forward and backward parameters are specified, with parameters like the peak cell rate, the sustainable cell rate and the maximum burst size being typical. The network may adjust the parameters of the connection, if due to other connections QOS's, it would not be possible to connect the new connection. It will then be a matter for the user to decide if those parameters are sufficient for the connection or not. There are a number of QOS that have been defined and they are coupled with the type of AAL that is used. It is of course also possible to have an unspecified QOS with no network guarantees. There are a number of types of services that can be supported by using these QOS types and the AAL's. The Constant Bit Rate ( CBR ) service is one that uses AAL 1 and requires a level of QOS from the network by specifying the mean bit rate and the cell loss acceptable as well as the allowable jitter in the cell delay. Another type of service is the Variable Bit Rate ( VBR ) service, which will use the AAL 2 and will also require a QOS from the network. In this service there will be specified parameters similar to the CBR but also the burst length and burst tolerance and the peak cell rate. Another type of service is the Unspecified Bit Rate ( UBR ) service,

where there is no bit rate declared and therefore only an unspecified QOS is given to the service. To allow for some guarantees to be given a new type of service called the Available Bit Rate ( ABR ) service is being defined. This service will try to fill up the available bandwidth and still give guarantees to the services.

Where is ATM?

ATM has moved from concept to reality with products and services available today. The ATM Forum has sponsored interoperability demonstrations to prove the technology and continues to meet to discuss the evolution of ATM. ATM coexists with current LAN/WAN Technology. ATM specifications are being written to ensure that ATM smoothly integrates numerous existing network technologies, at several levels (ie, Frame Relay, Ethernet, TCP/IP) Equipment, Services and Applications are available today and are being used in live networks. The telecommunications industry is converging on ATM!