Professional Documents
Culture Documents
AAL Assigment Final
AAL Assigment Final
By kedir Hassen
Student ID :GSE/9896/11
AUGUST 5, 2019
end-to-end protocol to adapt the cell transfer service provided by ATM network to the requirements
of specific application classes
Includes conversion to cells and back, and additional adaptation functions, e.g. timing recovery,
reliable transfer
The only way for a higher layer protocol to communicate across an ATM network is over the ATM Adaptation
Layer (AAL).
is perhaps the most important functional part of ATM, since it provides for the conversion of
information into a format suitable for carriage across an ATM transport network
is designed to support different types of applications and different types of traffic, such as voice,
video, imagery, and data
Its basic function is the enhanced adaptation of services provided by the ATM layer to the
requirements of the higher layer
It maps the user, control, or management protocol data units (PDU) into the information field of the
ATM cell and vice versa.
present only in end systems (only at edge of ATM network), not in switches.
converts the large Service Data Unit (SDU) data packet of the upper layer to 48 bytes for the ATM cell pay load
AAL has two sublayers:
Convergence Sublayer (CS): service dependent and provides the AAL services at the
AAL-SAP
Common Part: packet framing and error detection functions required by all AAL
users
Specific Part: functions that depend on specific requirements of AAL user classes
Segmentation and Reassembly (SAR) Sublayer: segmentation of higher layer PDUs into a
suitable size for the information field of the ATM cell (48 octets) at the transmitting end and
reassembly of the information fields into higher layer PDUs at the receiving end
> Connectionless
Four AAL protocols have been defined to support four AAL service classes
Convergence Sublayer (CS): divides the bit stream into 47-byte segments and
passes them to the SAR sublayer below. Note that the CS sublayer does not add a header
Two CS PDU formats
> Non-P format: No CS header (CS PCI), 47 octet user information for
transfer of unstructured data such as circuit emulation of full DS1 or DS3
> P format: 1 octet header (Structure Pointer SP), and 46 octet user
information for transfer of octet-aligned data such as N x 64 kbps (e.g.,
fractional DS1) services
segmentation and reassembly (SAR) sublayer: Add 1-byte header called the
protocol control information (PCI) to 47-byte payload
The header has two four-bit fields, four-bit Sequence Number (SN) and four-
bit Sequence Number Protection (SNP)fields. Each of these four-bit fields
is further subdivided into two subfields as described below
I. Sequence Number (SN)- four-bit field: contain 1-bit CSI and 3-bit Sequence count
Convergence Sublayer Indication (CSI): A 1-bit of first bit of SN; indicate the use/presence of of
convergence sublayer protocol control information; the default value is 0. Has two uses
> To encode Source clock frequency recovery
CSI bits from four successive cells (1, 3, 5, 7) form Synchronous Residual Time
Stamp (SRTS) for source clock recovery at the destination
The 4-bit RTS is transferred by the CSI bit in successive SAR-PDU
headers when the sequence count is odd (i.e. Value 1, 3, 5 or 7) and when
the CSI (convergence sub layer indication bit) is set to '1'.
> To indicate the presence of structured Data in CS layer
• by use of a pointer carried in the first octet of the SAR-PDU payload when
CSI= 1 and the sequence count is an even value (i.e. 0, 2, 4 or 6) to indicates
that the first byte of payload is the structure pointer to start of structured
block
• CSI = 0: no pointer for partially filled cells
In general,
𝟎 , if SRTS is not used (no 𝑝𝑜𝑖𝑛𝑡𝑒𝑟)
𝐂𝐒𝐈 = {𝐑𝐓𝐒 𝐯𝐚𝐥𝐮𝐞, if SRTS is used
𝟏 , for structured data
A 3-bit sequence count: indicate the sequence number of SAR-PDU making up the CS information
stream and to detect deletion or misinsertion of cells, the sequence count is used by the receiving SAR to check
that all cells have been received and that cells are in the correct order.
II. Sequence Number Protection (SNP): provides error detection and correction capabilities for the
SAR-POU header. This ensures correct interpretation of the SN field information even if it is corrupted by
transmission line errors.it provides two stage error protection for the SAR-PDU header
The SNP field comprises a 3-bit CRC with even parity for detecting and correcting SN error
• set to '1’' or '0' to make sure that an even number of ‘1 's appear in the 8 bits of the SN
and SNP fields.
Summary of AAL 1 functions
- Segmentation and reassembly of user information
- Handling lost and Misinserted cells
- Recovery of sending clock frequency at receiver
- Emulation of DS1 and DS3 Circuits
- Distribution with forward error correction
- Handle cell delay for constant bit rate
short packet.): Uniquely identifies the individual user logical link channels (LLC) within the
AAL2, and allows up to 248 (8 - 255) individual users within each AAL2 structure. is used in the
packet header to identify the LLC to which a packet belongs
Length indicator (LI). The 6-bit LI field indicates how much of the final packet is data.
Identifies the length of the LLC packet associated with each individual user, and assures
conveyance of variable payload. is used to identify the boundaries of variable-length
LLC packets
Packet payload type (PPT). The PPT field defines the type of packet.
User-to-user indicator (UUI). The UUI field can be used by end-to-end users; Provides
a link between CPS and an appropriate SSCS that satisfies the higher layer application.
Different SSCS protocols may be defined to support specific AAL2 user services, or
groups of services. The SSCS may also be null.
Header error control (HEC). The last 5 bits is used to correct errors in the header.
The only overhead at the SAR layer is the start field (SF) that defines
the offset from the beginning of the packet.
The Offset Field (OSF) identifies the location of the start of the remaining length
of the packet that possibly started in the preceding cell and is continuing in the
current cell from end of the field to start of first CPCS PDU or to start of PAD.
Maximum of CPCS PDU may span 2 SDUs
Sequence Number (SN): to protect Data integrity is protected by the
Parity bit (P): to protect The Start Field from error
PADPING: When it is necessary to transmit a partially filled cell to limit packet
emission delay, the remainder of the cell is padded with all zero octets
PAD: 0 to 24 bits; padding (PAD) of up to 3 octets of 0's may be added to the end of the user
information to aligns
trailer length to 32-bit boundary; To ensure that packet payload is
integer multiple of 4 bytes (Actual payload may be 0 to 3 bytes long. It is Inserted
between the end of the CPCS-PDU payload field and start of the CPCS tailor
The SAR has 2-octet header 44-octet payload, and 2-octet trailer consist of five fields:
Segment type (ST). The 2-bit ST identifier specifies the position of the segment
in the message:
• Indicates which part of the packet (CS-PDU) is carried in the cell:
Beginning OF message BOM (00), Middle/continuation of Message COM
(01), or End of Message EOM (10)
• A single-segment message SSM has an STof (11).
Sequence number (SN). used to ensure the correct order of receipt of cells
Multiplexing identifier (MID). The 10-bit MID field identifies cells coming from
different data flows and allows SAR sublayer multiplexing Up to 210 AAL users shares on the same
ATM virtual connection.VC
Length indicator (LI). This field defines how much of the packet is data used to indicate
how many of the octets within the SAR-PDU payload (total 44 bytes) are actually being
used to carry user information.it indicate the size of payload. Where the payload is full
(as will always be the case for BOM and COM SAR-PDUs) the LI is set to the maximum
value of 44 in the case of EOM and SSM payloads the user information will only partly
fill the SAR-PDU payload. The minimum permissible value of the LI is 4 (for EOM
payloads) and 8 (for SSM payloads). Except for last cell, all cells have LI=44 Last cell
has LI = 4 to 44
cyclic redundancy check (CRC). A 10-bit error detection code, for the entire data unit
that is to detect received errors in the SAR-PDU header, payload and length indication
fields
CRC. The last 4 bytes is for error control on the entire data unit; a 32-bit CRC error detection
code for detecting errors in the remainder of the CPCS-PDU.
A padding (PAD) of between 0 and 47 octets follows it to make sure that the CPCS-
PDU has a size equal to an integral number of AALS SAR-PDUs (i.e. cells).