| ||||
|
|
menu |
ATM (Asynchronous Transfer Mode) Basics - Part TwoThis is Part Two of the article "ATM (Asynchronous Transfer Mode) Basics - Part One". For better understanding read Part One of the article first. ATM networks are fundamentally connection oriented. This means that a virtual connection needs
to be established across the ATMnetwork prior to any data transfer. ATM virtual connections are of two types:
Virtual path connections, identified by virtual path identifiers (VPIs).
Virtual channel connections, identified by the combination of a VPI and a virtual channel
identifier (VCI). A virtual channel is roughly equivalent to a virtual circuit.
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. A virtual path connection is a bundle of virtual channels (see Figure 1-6).
Every cell header contains a VPI field and a VCI field, which explicitly associate a cell with a given
virtual channel on a physical link. It is important to remember the following attributes of VPIs and
VCIs:
VPIs and VCIs are not addresses, such as MAC addresses used in LAN switching.
VPIs and VCIs are explicitly assigned at each segment of a connection and, as such, have only
local significance across a particular link. They are remapped, as appropriate, at each switching
point.
Using the VCI/VPI identifier, the ATM layer can multiplex (interleave), demultiplex, and switch
cells from multiple connections.
Point-to-Point and Point-to-Multipoint Connections
Point-to-point connections connect two ATM systems and can be unidirectional or bidirectional. By contrast, point-to-multipoint connections (see Figure 1-7) join a single source end system (known as the root node) to multiple destination end-systems (known as leaves). Such connections can be unidirectional only, in which only the root transmits to the leaves, or bidirectional, in which both root and leaves can transmit.
Note that there is no mechanism here analogous to the multicasting or broadcasting capability
common in many shared medium LAN technologies, such as Ethernet or Token Ring. In such
technologies, multicasting allows multiple end systems to both receive data from other multiple
systems, and to transmit data to these multiple systems. Such capabilities are easy to implement in
shared media technologies such as LANs, where all nodes on a single LAN segment must
necessarily process all packets sent on that segment. The obvious analog in ATMto a multicast LAN group would be a bidirectional multipoint-to-multipoint connection. Unfortunately, this obvious solution cannot be implemented when using AAL5, the most common ATM Adaptation Layer (AAL) used to transmit data across ATM networks.
AAL 5 does not have any provision within its cell format for the interleaving of 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, with no interleaving
between the cells of different packets on the same connection, or the destination reassembly process would not be able to reconstruct the packets.
This is why ATM AAL 5 point-to-multipoint connections can only be unidirectional; if a leaf node
were to transmit an AAL 5 packet onto the connection, it would be received by both the root node
and all other leaf nodes. However, at these nodes, the packet sent by the leaf could well be interleaved with packets sent by the root, and possibly other leaf nodes; this would preclude the reassembly of any of the interleaved packets.
Solutions
For ATM to interoperate with LAN technology, it needs some form of multicast capability. Among
the methods that have been proposed or tried, two approaches are considered feasible (see
Figure 1-8).
Multicast server. In this mechanism, all nodes wishing to transmit onto a multicast group set up
a point-to-point connection with an external device known as a multicast server. The multicast
server, in turn, is connected to all nodes wishing to receive the multicast packets through a
point-to-multipoint connection. The multicast server receives packets across the point-to-point
connections, serializes them (that is, ensures that one packet is fully transmitted prior to the next
being sent), and retransmits them across the point-to-multipoint connection. In this way, cell
interleaving is precluded.
Overlaid point-to-multipoint connections. In this mechanism, all nodes in the multicast group
establish a point-to-multipoint connection with each other node in the group and, in turn, become
a leaf 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, while the multicast server mechanism requires only two
connections. The overlaid connection model also requires a registration process for telling nodes
that join a group what the other nodes in the group are, so that it can form its own
point-to-multipoint connection. The other nodes also need to know about the new node so they
can add the new node to their own point-to-multipoint connections.
Of these two solutions, 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.
Applications
Two applications that require some mechanism for point-to-multipoint connections are:
LAN emulationin this application, the broadcast and unknown server (BUS) provides the
functionality to emulate LAN broadcasts. See the chapter Layer 3 Protocols overATMand LAN
Emulation for a details.
Video broadcastin this application, typically over a CBR connection, a video server needs to
simultaneously broadcast to any number of end stations. See the chapter Circuit Emulation
Services and Voice over ATM.
Operation of an ATM Switch
An ATM switch has a straightforward job:
1 Determine whether an incoming cell is eligible to be admitted to the switch (a function of Usage
Parameter Control [UPC]), and whether it can be queued.
2 Possibly perform a replication step for point-to-multipoint connections.
3 Schedule the cell for transmission on a destination interface. By the time it is transmitted, a
number of modifications might be made to the cell, including the following:
VPI/VCI translation
setting the Early Forward Congestion Indicator (EFCI) bit
setting the CLP bit
The functions of UPC, EFCI, and CLP are discussed in the chapter ATM Technology
Fundamentals.
ATM switches fall into two categories, those that do virtual path switching only and those that do
switching based on virtual path and virtual channel values. The basic operation of an ATMswitch is the same for both types of switches.
Based on the incoming cells VPI, VCI, or both, the switch must identify which output port to
forward a cell received on a given input port, and it must determine the new VPI/VCI values on the
outgoing link, substituting these new values in the cell before forwarding it. The ATMswitch derives these values from its internal tables, which are set up either manually for permanent virtual
connections, or through signaling for switched virtual connections.
Note Your Cisco ATM switch routers performs both virtual path and virtual channel switching.
Figure 1-9 shows an example of virtual path switching, in which cells are switched based only on
the value of the VPI; the VCI values do not change between the ingress and the egress of the
connection. This is analogous to central office trunk switching.
Figure 1-10 shows an example of switching based on both VPI and VCI values. Because all VCIs
and VPIs have only local significance across a particular link, these values get remapped, as
necessary, at each switch.
The ATM Reference Model
The ATM architecture is based on a logical model, called the ATM reference model, that describes
the functionality it supports. In the ATMreference model (see Figure 1-11), the ATMphysical layer
corresponds approximately to the physical layer of the OSI reference model, and the ATMlayer and ATM adaptation layer (AAL) are roughly analogous to the data link layer of the OSI reference model.
The layers of the ATM reference model have the following functions:
Physical layermanages the medium-dependent transmission. The physical layer is divided into
two sublayers:
Physical medium-dependent sublayersynchronizes transmission and reception by sending
and receiving a continuous flow of bits with associated timing information, and specifies
format used by the physical medium.
Transmission convergence (TC) sublayermaintains ATM cell boundaries (cell
delineation), generates and checks the header error-control code (HEC), maintains
synchronization and inserts or suppresses idle ATM cells to provide a continuous flow of
cells (cell-rate decoupling), and packages ATMcells into frames acceptable to the particular
physical layer-implementation (transmission-frame adaptation).
ATM layerestablishes connections and passes cells through the ATM network. The specific
tasks of the ATM layer include the following:
Multiplexes and demultiplexes cells of different connections
Translates VPI/VCI values at the switches and cross connections
Extracts and inserts the header before or after the cell is delivered to the AAL
Maintains flow control using the GFC bits of the header
ATM adaptation layer (AAL)isolates higher-layer protocols from the details of the ATM
processes by converting higher-layer information into ATM cells and vice versa. The AAL is
divided into two sublayers:
Convergence sublayer (CS)takes the common part convergence sublayer (CPCS) frame,
divides it into 53-byte cells, and sends these cells to the destination for reassembly.
Segmentation and reassembly sublayersegments data frames into ATM cells at the
transmitter and reassembles them into their original format at the receiver.
Higher layersaccept user data, arrange it into packets, and hand it to the AAL.
ATM Addressing
If cells are switched through an ATMnetwork based on the VPI/VCI in the cell header, and not based
directly on an address, why are addresses needed at all? For permanent, statically configured virtual
connections there is in fact no need for addresses. But switched virtual connections, which are set
up through signaling, do require address information.
Switched virtual connections work much like a telephone call. When you place a telephone call you
must have the address (telephone number) of the called party. The calling party signals the called
partys address and requests a connection. This is what happens with ATM switched virtual
connections; they are set up using signaling and therefore require address information.
The types and formats of ATM addresses, along with their uses, are described in the chapter ATM Signaling and Addressing.
Polls |
Telecom Interview Q&ATelecom Articles |
|||||||||||||||||||||