MPR Delta Training

9500 MPR Delta Training
Rel 1.2 Rel 1.3

ASAP & AUX boards management
Alcatel-Lucent
April, 2010
All Rights Reserved Alcatel-Lucent 2006, #####
Content
1. ATM networks An introduction.

2. ATM traffic management in 9500MPR.
3. ASAP board provisioning procedure.

4. AUX board Provisioning
All Rights Reserved Alcatel-Lucent 2006
ATM networks
An Introduction
1. ATM networks Introduction

1.1 Introduction
1.2 Frame structure
1.3 Switching in ATM networks
1.4 ATM protocol stack
1.5 ATM Traffic characterization
1.6 QoS parameters
1.7 ATM service categories

1.1 Introduction
1.2 Frame structure
1.6 QoS parameters
1.1. Introduction
ATM networking architecture is designed with a view to transmit Voice, Video and Data
traffic on the same network. Although these different types of traffic have different
tolerance levels for packet loss and end-to-end delay.
ATM networks are connection-oriented, and packet-switched networks:
- Connection-Oriented: As a connection must be established first between circuit ends
(call-setup phase), before the exchange of information commences.
- Packet-switched: As the exchanged information is in the form of packets (Referred to as
CELLs).
An ATM cell is of fixed length (53Bytes), containing 5 bytes of header and 48 bytes of
payload.
Switching inside an ATM network is based on the circuit identifier (CI) information,
found in the cell header.
There is neither error control nor flow control between two adjacent ATM nodes.
However, ATM cell header is protected in order to avoid forwarding the packet to the
wrong destination

1.1 Introduction
1.2 Frame structure


1.6 QoS parameters
1.2. ATM frame structure

An ATM cell is of fixed length (53 Bytes), containing 5 header bytes and 48
payload bytes.
Two slightly different formats for the cell header were adopted, for UNI and NNI
cells.
UNI cells (User Network Interface) are the cells exchanged between an ATM end
device and an ATM switch. While NNI cells (Network Network Interface) are
exchanged between ATM switches belonging to the same network or two different
networks.
Contd
The structure of an ATM NNI cell is described in the figure below:
Where:
VPI = Virtual Path Identifier.
VCI = Virtual Circuit Identifier.
PTI = Payload Type Indicator.
CLP = Cell Loss Priority
HEC = Header Error Control
Contd
VPI/VCI fields:
An ATM connection is identified by the combined Virtual Path Identifier
VPI and Virtual Circuit Identifier VCI. Such a connection is referred to as
Virtual Channel Connection VCC.
VPI field is 12 bits long in an NNI cell. Therefore, there can be a max of 4096
virtual paths in an NNI interface.
VCI field is 16 bits long, allowing a maximum of 65,535 virtual circuits inside
the same virtual path.
The combined VPI and VCI allocated for a connection is known as the Connection
Identifier (CI) i.e. CI = {VPI, VCI}
Contd
PTI Field:
Payload Type indicator Field is used to indicate different types of payload;
such as user date or OAM.
Its also used to notify that network congestion was experienced.
CLP Field:
Cell Loss Priority Field indicates whether the cell can be discarded when
congestion arises in the network.
HEC field:
Header Error Control is used for error detection and correction for the
header part of the cell only. (Correction is possible only in case of single
error).
9-bit pattern CRC is used for detection and correction.

1.1 Introduction
1.2 Frame structure

1.6 QoS parameters
1.3. Switching in ATM networks

A Virtual Channel Connection between end devices consists of a path through a number of ATM
switches.
500
500
500
500
500
For each point to point link along the path, the connection is identified by a different VPI/VCI
pair. i.e. VPI/VCI has local significance and is translated to a different VPI/VCI at each switch the
cell traverses.
This VPI/VCI translation is performed by an ATM switch, this operation is also known as Label
Swapping.
Port 1
VP3
Port 3
VP18
1.3. Switching in ATM networks
contd
The VPI/VCI translation involves a look-up in the switching table, in order for the
switch to determine what is the output port and new VPI/VCI to use before
forwarding a received cell.
Input
Output
Port #
VPI
VCI
Port #
VPI
VCI
100
85
231
33
42
54
95
ATM switching table Simplified example
According to the example switching table shown:

An incoming cell at port 1, having VPI = 100 and VCI = 85, is forwarded to port 3,
with a new VPI = 231 and a new VCI = 3.
While an incoming cell at the same port, but with VPI/VCI = 33/42, is forwarded to
port 5 with new VPI/VCI = 54/95

1.1 Introduction
1.2 Frame structure

1.6 QoS parameters
1.4. ATM protocol stack

The ATM protocol stack consists of the following layers:
Physical Layer.
ATM Layer.
ATM adaptation layer (AAL)
Higher layers permitting various applications

to run on top of ATM, transmitting different traffic types.
The Physical Layer:
Contd
This layer maps cells to the transmission medium, it performs the following
Functions:
1.
Generation and verification of HEC.
2.
Insertion of idle cells in case of no incoming traffic.
3.
Timing function; generates timing for Tx cells, and derives timing from Rx cells.
4.
Encoding and decoding of the bit stream (Block coding).
The ATM layer:
Switching in ATM networks is performed by this layer, the most important functions
are:
1.
Cell switching.
2.
QoS management.
3.
Congestion control.
Contd
The ATM Adaptation Layer:
This Layer converts the traffic generated by higher level layers to suitable ATM
payload, to be further on delivered to destination by the ATM layer.
Several AALs were defined according to the type of traffic to be sent, most important
is:
1.
AAL-1: Used for circuit emulation services (CES), constant bit rate video, and
high quality constant bit rate audio.
2.
AAL-2: suitable for delay sensitive, low bit rate applications.
3.
AAL-5: The most popular AAL, used for transfer of data traffic.

1.1 Introduction
1.2 Frame structure

1.6 QoS parameters
1.5. ATM traffic characterization
The traffic submitted by an ATM source can be described by the following parameters:
Peak Cell Rate (PCR):

Is the max amount of traffic submitted by a source to the network (in cells/sec)
Sustained Cell Rate (SCR):
Is the Max average transmission rate of traffic submitted by the source (in cells/sec)
Minimum Cell Rate (MCR):

Is the min cell rate that must be guaranteed by the network for a given source.
Maximum Burst Size (MBS):

For bursty sources, the max burst
size is the max number of cells that
can be submitted by the source @ PCR.

1.1 Introduction
1.2 Frame structure
1.6 QoS parameters

1.6. QoS Parameters
Different parameters can be defined to express the QoS level of a connection.
During the call setup phase, values are set for the desired QoS parameters. The network
will accept the connection if it can guarantee these values throughout the whole path.
The standardized QoS parameters are described as follows:
Cell Loss Rate (CLR): Max allowed rate for cell loss. CLR is the most popular QoS
parameter, as its easy to quantify.
Jitter: Is a very important QoS parameter in case of real time applications. It is used
to set an upper bound for the inter-arrival gaps between the received cells. Interarrival gaps (In case of real-time audio/video), if too large, might cause the play out
process to pause.
Cell Transfer Delay (CTD): Is the time it takes to transfer a cell end-to-end. CTD is
made up of a fixed component (Due to Txn medium propagation delay, switch
processing time, etc), and a variable component due to queuing delays inside
switches (Variable CTD is also refered to as Peak-to-peak cell delay variation).

1.1 Introduction
1.2 Frame structure
1.6 QoS parameters
1.7. ATM Service Categories
ATM service categories are classes of services carried over the ATM network.
Each service category is associated with a set of traffic parameters, and a set of QoS
parameters.
Cells belonging to different service categories are treated differently inside the switch
scheduler.
The service category of a connection is signaled at call setup phase.
Six ATM service categories were standardized by ATM forum: Constant Bit Rate (CBR), Real
time Variable Bit Rate (RT-VBR), Non Real Time Variable Bit Rate (NRT-VBR), Unspecified
Bit Rate (UBR), Available Bit Rate (ABR), and Guaranteed Frame Rate (GFR).
To define a service category during call setup phase, two mandatory pieces of information
must be supplied:
A description for the traffic parameters (e.g. whats the PCR, the SCR, etc)
A description for the required QoS parameters.
Supplying this info, leads to a settlement of an agreement (a contract) between the network and the
source. To be respected by both parties throughout the transmission period.
Any of the above service categories can be used with any ATM Adaptation Layer (There is
no restriction).
Contd
Constant Bit Rate service (CBR) :
This service is intended for real time applications transmitting at constant bit rate
like circuit emulation services (CES), and constant bit rate audio or video.
Required traffic parameters for contract: PCR and CDVT.
Required QoS parameters: CLR, peak-to-peak cell delay variation, and Max CTD.
Real time Variable Bit Rate service (RT-VBR):
This service is intended for real time applications that transmit at variable bit rate.
Like encoded video and encoded voice.
PCR, MBS, CDVT, and SCR are needed to characterize this VBR traffic.
QoS parameters needed: CLR, peak-to-peak cell delay variation, and Max CTD.
Contd
Non Real Time Variable Bit Rate service (NRT-VBR) :
This service is intended for non-real time applications that transmit at variable bit
rate.
PCR, MBS, CDVT, and SCR are needed to characterize this VBR traffic.
QoS parameters needed: only CLR (As the transmitting aplication is non-real time,
there are no constrains on delay).
Unspecified Bit Rate service (UBR):
This is a BEST EFFORT type of service intended for data transfer application like file
transfer and web browsing.
No traffic descriptors nor QoS parameters required, as (if defined) they can be
ignored by the network.
Contd
UBR + MDCR (UBR+):
This service is the same as UBR but adding a Minimum Desired Cell Rate that the
network commits to transmit.
PCR, and MDCR are required to characterize the traffic.
ATM Management
In 9500 MPR
1. ATM management in 9500MPR

2.1 The physical layer (What is IMA?)
2.2 Pseudo wire emulation (What is a PWE3?)
2.3 Policing and Shaping
2.4 Supported service categories

2.2 Pseudo wire emulation (What is a PWE3?)
2.1. The Physical Layer (IMA)
ATM cells can be carried over several physical interfaces (e.g SONET, DS3, 100Mbps
multimode fiber, etc)
9500MPR uses IMA protocol (Inverse Multiplexing of ATM) to interface ATM traffic.
IMA protocol is based on the multiplexing of ATM cells over several physical links to form a
higher capacity logical link.
Multiplexing of ATM cells is performed in a cyclic way (Round Robin).
Physical links used are E1 links.
ATM end device

e.g. NodeB
IMA Group
PHY Physical Link #0
IMA Group
PHY
9500 MPR
ASAP board
Physical Link #1
PHY
ATM Cell
Stream from
ATM Layer
PHY
PHY
Physical Link #2
PHY
IMA Virtual Link
Original Cell
Stream Passed
to ATM Layer
2.1. The Physical Layer (IMA) contd
In 9500 MPR, an IMA interface can support up to 8 E1 links.
ASAP board can manage up to 8 IMA groups.
An IMA E1 link carries around 4490 cells/sec.
Example:
Two ATM end devices are interfaced to 9500MPR ASAP board using 2 IMA groups.
IMA group #1 interfacing device A is composed of 3 E1 links.
IMA group #2 interfacing device B is composed of 2 E1 links.

Max 8980 cells/sec
Device B
VC
VC
VC
VC
VC
VC
VC
VP
2x E1
VP
VC
VC
VC
VC
VC
VC
VC
ASAP board
9500MPR
Device A
VC
VC
VC
VC
VC
VC
VC
VP
3x E1
VP
Max 13440 cells/sec

VC
VC
VC
VC
VC
VC
VC

2.2 Pseudo Wire Emulation (What is a PWE3?)

2.2. Pseudo Wire Emulation (PWE3)
Pseudo Wire Edge-to-Edge Emulation (PWE3) is a mechanism to carry emulated services

such as ATM or TDM over a packet switched network (PSN). Connecting two provider edges
together.
PWE3 is a Layer two VPN between end points over the PSN.
ATM
CES
ATM
CES
PWE3
PWE3
PSN
CES
PWE3
CES
ATM
ATM
2.2. Pseudo Wire Emulation (PWE3) contd
As 9500 MPR is a packet based equipment, ASAP board performs the Circuit Emulation for
incoming ATM cells via MPLS encapsulation to make it suitable for transmission over the
PSN (Via radio port or Ethernet aggregation).
Ingress and Egress VPI/VCI translation is performed by ASAP board (If needed) during the
PWE3 creation.
Each ATM PW is identified by a separate VLAN ID.
GbE on Core-E
PSN
GbE
Core-E
MD300
PWE3
GbE
ASAP
ATM


2.3. Policing and Shaping
Policing and Shaping are QoS components controlling the amount of traffic received and
transmitted on an ATM interface; ensuring the conformity of the traffic to the connection
traffic contract
Ingress Policing:
Before forwarding the ATM cells to circuit emulation block, ASAP board may perform
policing on the incoming traffic to ensure that the transmitting ATM source is
respecting the traffic contract of the connection.
The resulting traffic (Policed) is used for pseudo wire creation, and aggregation over
a radio or Ethernet link.
2.3. Policing and Shaping
contd
Egress Shaping:
Before forwarding the ATM cells to the receiving ATM device, ASAP board may apply
traffic shaping to the egress traffic, to ensure that the output traffic from MPR is
respecting the traffic contract of the connection.
Egress Shaping is based on the leaky bucket mechanism.
The yellow cells represent shaped traffic, while red cells correspond to traffic that
couldnt be shaped due to buffer overflow.

2.4. Supported service categories
9500MPR supports the following service categories:
CBR : Constant Bit Rate service. The Commit Information Rate (CIR) for this service is
equal to the defined PCR of the connection.
UBR : Unspecified Bit Rate service (Best effort). CIR = 0.
UBR+ : UBR with a Minimum Desired Cell Rate (MDCR) (CIR = MDCR).
ASAP board provisioning
3. ASAP board provisioning

3.1 Introduction to ASAP
3.2 Provisioning phases
3.3 Creating Traffic descriptors
3.4 The E1 Layer
3.5 The IMA Layer
3.6 The ATM Layer
3.7 The PW layer
3.8 PW Cross-Connection

3.4 The E1 Layer
3.5 The IMA Layer
3.6 The ATM Layer
3.7 The PW layer
3.1. Introduction to ASAP
ASAP board performs MPLS encapsulation for the incoming

ATM cells producing pseudo wires (PWE3).
The resulting PWE3 are then forwarded to the Main and Spare
Core-E boards to connect them to the aggregation port
(Radio or Ethernet).
During MPLS encapsulation, ASAP board performs

VPI/VCI translation (If needed).
ASAP board accepts only the configured connection

(Predefined VPI and VCI) respecting the traffic contracts.
16 E1 ports are available on the ASAP board

front plate, constituting up to 8 IMA interfaces.

3.4 The E1 Layer
3.5 The IMA Layer
3.6 The ATM Layer
3.7 The PW layer
3.2. Provisioning phases
To provision the ASAP board, one should pass through the following phases:
1.
Creating Traffic Descriptors (TD):

Defining traffic contracts that will be associated to each ATM connection.
2.
Configuring the E1 Layer:

Choosing the active E1 ports to be used, as well as the timing mode of each link.
3.
Configuring the IMA Layer:

In this phase we define how many IMA groups/Interfaces are used, how many links
inside each interface, and which physical E1 ports are associated with each IMA
group.
4.
Configuring the ATM Layer:
Once IMA interfaces are defined, we need to inform the ASAP about the expected
VPs and VCs on each interface, as well as the amount of traffic and class of
service expected on each VP and VC (Using the TDs created in phase 1).
5.
Configuring the PWE3 Layer:

In this phase, the PWE3 are created for each VP/VC.
6.
PWE3 Cross-connection:
Cross-Connecting the created PWE3s to an Ethernet port or to a radio link.
Its also possible to connect PWE3 between radio directions without having local ASAP board (ATM
repeater sites)

3.4 The E1 Layer
3.5 The IMA Layer
3.6 The ATM Layer
3.7 The PW layer
3.3. Creating Traffic Descriptors

To open the traffic descriptors view, go Configuration Traffic descriptors.
contd
Contd
Example: an ATM interface is carrying the following connections:

VPI/VCI = 1/32, CBR source, PCR = 4000C/S, CDVT = 1000uS.
VPI/VCI = 1/33, UBR+ source, PCR = 7000C/S, MDCR = 2000C/S, CDVT = 1000uS.
VPI/VCI = 1/34, UBR source, PCR = 9000C/S.
VPI = 2, CBR source, PCR = 151C/S.
Note that VP 1 contains VCI 32, 33 and 34. The amount of guaranteed traffic inside this VP =
sum of guaranteed traffic inside VCs (4000 + 2000).
VP 1 can be considered as a UBR+ pipe with MDCR 6000C/S and PCR = 20000C/S.
A traffic contract is created for VP1, VC32, VC33, VC34 and VP2 as follows.

3.4 The E1 Layer
3.5 The IMA Layer
3.6 The ATM Layer
3.7 The PW layer
3.4. The E1 Layer

To start provisioning layers, double click on the ASAP board to open the ASAP main view:
3.4. The E1 Layer
contd
On the ASAP main view, choose the E1 layer tab
3.4. The E1 Layer
Contd
Back to our Example: The max amount of traffic submitted to this interface (According to the
last example) is 20000 cells. With each E1 IMA link carrying around 4000 C/S, this interface
must have 5 E1 links.
On E1 Layer, five E1 ports are enabled, and timing mode is determined depending on the
location of the interface (e.g node timed @ NodeB side, and Loop timed @ RNC side).

3.4 The E1 Layer
3.5 The IMA Layer
3.6 The ATM Layer
3.7 The PW layer
3.5. The IMA Layer

Move on to the IMA Layer tab, and associate the 5 E1s (Enabled in E1 Layer) to group#01.

3.4 The E1 Layer
3.5 The IMA Layer
3.6 The ATM Layer
3.7 The PW layer
3.6. The ATM Layer

Move on to the ATM Layer tab, and create required VPs.
3.6. The ATM Layer

The VP Layer configuration opens.
Input the VP ID in the first field.
Choose the VP role:
Logical: If further VCs to be created.
NotLogical: If no VCs to be created.
3.6. The ATM Layer
contd
Associate a TD by clicking Browse

(Choose one of the previously created TDs
describing the traffic flowing over this VP).
In our example, VP 1 is Logical, associated to TD 1, while VP 2 is NotLogical and associated

to a different TD 2..
3.6. The ATM Layer
contd
Once a Logical VP is created, select it

and press Create VC in the VC Layer
configuration Area.
Proceed with VC creation, just like VP creation. Associating the appropriate traffic descriptors
for each VC. (Must be created in advance from the TD configuration view)
In our example, VP1 contains
VCs 32, 33, and 34.
Traffic descriptors were created
in advance to describe the traffic
flowing on these VCs.

3.4 The E1 Layer
3.5 The IMA Layer
3.6 The ATM Layer
3.7 The PW layer
3.7. The PWE3 Layer

Move on to ATMPWLayer, and create PWE3s.
3.7. The PWE3 Layer
contd
In our Example, 4 connection exist on interface#1; namely VPI/VCI 1/32, 1/33, 1/34 and VPI 2.
One PWE3 must be created for each of these connections. Here PWE3 labels are 132, 133,
134 and 20 respectively.
No VPI/VCI translation is required. (Note that Egress and Ingress VPI/VCI are the same).
The only remaining step is to cross-connect these PWE3s to the radio (Or to an Ethernet port
on Core-E).

3.4 The E1 Layer
3.5 The IMA Layer
3.6 The ATM Layer
3.7 The PW layer
3.8. PWE3 Cross-Connection

From Cross-connection view, cross-connect PWE3 from ASAP to Radio or Ethernet port
3.8. PWE3 cross connection
contd
A new window will open to complete the cross-connection operation.
3.8. PWE3 Cross-Connection
Contd
Other PWE3 cross-connection types:
The PWE3 cross connection covered ion our example is an ASAP - Radio cross connection.
Three other PW cross-connection types are supported:

1.
ASAP Ethernet:
To connect the Pseudo Wire to an Ethernet port on Core-E for service aggregation
2.
Radio Ethernet:
To connect PWE3 coming from radio to an Ethernet port on Core-E board.
3.
Radio Radio:
To connect PWE3 between different radio directions, without the need of a local ASAP board (ATM
repeater site)
AUX board Provisioning
4. AUX Board Provisioning

4.1 Introduction to AUX board
4.2 Provisioning Procedure
4.2.1 Configuring Service Channels
4.2.2 Configuring H/K Alarms

4.2.1 Configuring Service Channels.
4.2.2 Configuring H/K alarms.

AUX board provide access for two service channels, Housekeeping Alarms and
EOW.
Four connectors can be found on the front plate of AUX board as described in the
below figure:
Status LED:
Off = Card not powered or not
configured.
Green Blinking = SW download/booting
or Flash card alignment in progress.
Green = In service.
Red = Card fail.
Red blinking = Card mismatch.
Each Engineering Service Channel connector (ESC-1 and ESC-2) interface one
Synchronous 64Kbps RS422/V11 DCE co-directional channels for radio transport.
Three radio service channels (Out band) are available for cross-connection of local
service channels on AUX board.
Housekeeping alarms connector supports 6 Input and 7 Output alarms.
EOW voice channel is not supported in this release.
contd
Like all other 9500MPR boards, the main function of an AUX card is to transform the incoming
Service channels and H/K alarm into a format suitable for transmission to the CORE-E board
via the GbE interface on the back plan.
Data coming from the AUX board is then processed and cross-connected by the CORE-E to
the appropriate radio port.
AUX board is allowed to be inserted only in slot-8 in an MSS-8 or Slot-4 in an MSS-4 chassis.


4.2.2 Configuring H/K Alarms.
To access AUX board configuration view, double click on the AUX board in Equipment
view.
Service Channels provisioning is performed in two steps:

1.
Define the operational ESC ports (Enable / Disable).
2.
Cross-connect the configured ports to the appropriate radio channel.
Contd
In resulting AUX board configuration view, Settings tab, configure ESC ports as described
below:
Contd
Cross-connect the configured ports to the appropriate radio port as follows:
** Possible TP combinations are:

1.
Radio port Radio port

Where a pass-through connection is
performed between different radio directions
2.
Radio port ESC port

Where a radio service channel is connected
to an ESC port on AUX board

4.2.2 Configuring H/K Alarms.
4.2.2 Configuring H/K alarms
On AUX board provisioning view, select the External points tab.
Configure input alarms as follows:
4.2.2 Configuring H/K alarms
Configure Output alarms as follows:
End Of Training
Thanks for your attention
WWW.ALCATEL-LUCENT.COM

MPR Delta Training

Cargado por

Información del documento

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

MPR Delta Training

Cargado por

Copyright:

Formatos disponibles

9500 MPR Delta Training

Rel 1.2 Rel 1.3

All Rights Reserved Alcatel-Lucent 2006, #####

1. ATM networks An introduction.

3. ASAP board provisioning procedure.

All Rights Reserved Alcatel-Lucent 2006

All Rights Reserved Alcatel-Lucent 2006

1. ATM networks Introduction

All Rights Reserved Alcatel-Lucent 2006

1. ATM networks Introduction

All Rights Reserved Alcatel-Lucent 2006

All Rights Reserved Alcatel-Lucent 2006

1. ATM networks Introduction

1.2 Frame structure

1.4 ATM protocol stack

All Rights Reserved Alcatel-Lucent 2006

1.2. ATM frame structure

All Rights Reserved Alcatel-Lucent 2006

1.2. ATM frame structure

The structure of an ATM NNI cell is described in the figure below:

All Rights Reserved Alcatel-Lucent 2006

1.2. ATM frame structure

All Rights Reserved Alcatel-Lucent 2006

1.2. ATM frame structure

All Rights Reserved Alcatel-Lucent 2006

1. ATM networks Introduction

1.3 Switching in ATM networks

All Rights Reserved Alcatel-Lucent 2006

1.3. Switching in ATM networks

All Rights Reserved Alcatel-Lucent 2006

1.3. Switching in ATM networks

ATM switching table Simplified example

According to the example switching table shown:

All Rights Reserved Alcatel-Lucent 2006

1. ATM networks Introduction

1.4 ATM protocol stack

All Rights Reserved Alcatel-Lucent 2006

1.4. ATM protocol stack

Higher layers permitting various applications

All Rights Reserved Alcatel-Lucent 2006

1.4. ATM protocol stack

The Physical Layer:

Generation and verification of HEC.

Insertion of idle cells in case of no incoming traffic.

Encoding and decoding of the bit stream (Block coding).

The ATM layer:

All Rights Reserved Alcatel-Lucent 2006

1.4. ATM protocol stack

The ATM Adaptation Layer:

AAL-2: suitable for delay sensitive, low bit rate applications.

All Rights Reserved Alcatel-Lucent 2006

1. ATM networks Introduction

1.5 ATM Traffic characterization

All Rights Reserved Alcatel-Lucent 2006

1.5. ATM traffic characterization

Peak Cell Rate (PCR):

Sustained Cell Rate (SCR):

Minimum Cell Rate (MCR):

Maximum Burst Size (MBS):

All Rights Reserved Alcatel-Lucent 2006

1. ATM networks Introduction

1.6 QoS parameters

All Rights Reserved Alcatel-Lucent 2006