02 - ATM Traffic - and Resource Management

3G Platform
3G ATM - ATM Traffic- and

Resource Management
Training Document
6-282561 © Nokia Networks Oy 1 (51)

Issue 1.0 en
Issue 1.0en
Contents
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This document is intended for the
use of Nokia's customers only for the purposes of the agreement under which the document is
submitted, and no part of it may be reproduced or transmitted in any form or means without
the prior written permission of Nokia. The document has been prepared to be used by
professional and properly trained personnel, and the customer assumes full responsibility
when using it. Nokia welcomes customer comments as part of the process of continuous
development and improvement of the documentation.
The information or statements given in this document concerning the suitability, capacity, or
performance of the mentioned hardware or software products cannot be considered binding
but shall be defined in the agreement made between Nokia and the customer. However,
Nokia has made all reasonable efforts to ensure that the instructions contained in the
document are adequate and free of material errors and omissions. Nokia will, if necessary,
explain issues which may not be covered by the document.
Nokia's liability for any errors in the document is limited to the documentary correction of
errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS
DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING
MONETARY LOSSES), that might arise from the use of this document or the information in it.
This document and the product it describes are considered protected by copyright according
to the applicable laws.
NOKIA logo is a registered trademark of Nokia Oyj.
Other product names mentioned in this document may be trademarks of their respective
companies, and they are mentioned for identification purposes only.
Copyright © Nokia Oyj 2005. All rights reserved.

Issue 1.0 en
ATM traffic and resource management
Contents
1 Objectives .............................................................................................. 5
2 ATM traffic management....................................................................... 6

2.1 Traffic management functions ................................................................. 6
2.1.1 Connection Admission Control (CAC) ..................................................... 6
2.1.2 Usage / Network Parameter Control (UPC/NPC) .................................... 7
2.1.3 Traffic shaping ......................................................................................... 8
2.1.4 Priority control........................................................................................ 10
2.1.5 Frame Discard ....................................................................................... 10
2.1.5.1 Partial Packet Discard (PPD) ................................................................ 10
2.1.5.2 Early Packet Discard (EPD) .................................................................. 11
2.2 Traffic contract and negotiation ............................................................. 12
2.2.1 ATM quality of service (QoS)................................................................. 12
2.2.2 Traffic descriptors .................................................................................. 13
2.2.3 Definition of a compliant connection...................................................... 16
2.2.4 QoS classes .......................................................................................... 16
2.3 ATM layer service categories ................................................................ 17
3 Resource management in ATM network ........................................... 21

3.1 Physical Layer Trail Termination Point (phyTTP) .................................. 22
3.2 ATM interface ........................................................................................ 23
3.3 Access profile of ATM interface............................................................. 24
3.4 VP/VC Link termination point................................................................. 26
4 Routing and digit analysis.................................................................. 30

4.1 Digit analysis ......................................................................................... 30
4.2 Routing .................................................................................................. 31
4.3 Routing objects in ATM network............................................................ 33
5 Review of ATM resource management and digit analysis .............. 36
4 (51) © Nokia Networks Oy 6-282561

Issue 1.0 en
1 Objectives
After completing this module, the student should be able to:
• List the key aspects of ATM traffic management.
• Distinguish ATM Quality of Service parameters, Traffic parameters and
Service Classes from each other.
• Describe the main purposes of ATM resource management.
• Identify the steps to create ATM resources.
• Understand the configuration of routing and digit analysis in an ATM
network element.

Issue 1.0 en
2 ATM traffic management

ATM provides a mechanism to ensure that the quality of service (QoS) remains
as high as possible while the operator is able to utilise the network capacity in
an efficient way. The actions taken to achieve the QoS targets in ATM networks
are called traffic management. The operator can use ATM traffic management
for providing QoS for ATM connections. Also fairness of resource allocation
between users can be guaranteed with traffic management functions. Bandwidth
of ATM connections can be allocated flexibly according to application needs.
2.1 Traffic management functions

There are different functions to manage and control the traffic in ATM
networks. The two basic control functions are Connection Admission Control
(CAC) and Usage/Network Parameter Control (UPC/NPC). On top of this two
basic control functions, the following ones may be used in appropriate
combinations to support and complement the actions of UPC/NPC and CAC:
traffic shaping, priority control, frame discard etc.
2.1.1 Connection Admission Control (CAC)
Connection Admission Control (CAC) is used for checking that there are
bandwidth and buffer resources for requested connections. CAC is defined as a
set of actions taken by the network at the connection establishment phase in
order to decide whether a virtual channel/path connection can be accepted or
rejected. Sophisticated CAC algorithms allow maximal utilisation of network
element internal resources and external links while guaranteeing agreed
bandwidth and quality of service for all existing connections. CAC verifies
whether network (or node) is able to offer requested QoS without risking the
QoS of the existing connections.
ATM Network
Usea A
User User B
Setup CAC
Figure 1. Connection Admission Control (CAC)

Issue 1.0 en
2.1.2 Usage / Network Parameter Control (UPC/NPC)
Usage/Network Parameter Control (UPC/NPC), also known as traffic policing,

is used for monitoring the compliance of ATM end systems to agreed traffic
contracts. Traffic contract defines traffic parameters (e.g. peak cell rate) for
each connection. UPC is applied in the User-Network Interface (UNI) and NPC
is performed in the Network-Node Interface (NNI).
User A User B
UPC ATM NPC ATM

Network Network
UNI NNI UNI
NPC UPC
Figure 2. Usage Parameter Control (UPC) and Network Parameter Control (NPC)
Traffic policing is defined as a set of actions taken by the network to monitor

and control the amount of incoming ATM traffic. The main purpose is to
protect resources from misbehaviour that can affect the QoS of other already
established connections. This is done by detecting violations of negotiated
parameters and taking appropriate actions. At the ATM cell level actions may
include cell passing, cell tagging (only for CLP=0 cell stream) and cell
discarding. UPC/NPC supports the QoS objectives for all compliant
connections.
Both UPC and NPC function can be enabled or disabled for all connections at
an interface.
Note
RNC/MGW supports a dual leaky bucket policing algorithm defined by ATM
Forum (For further information on dual leaky bucket policing algorithm refer to
appendix D at the end of this module). Policing is currently always enabled for
terminated CBR type VCCs. Policing does not apply to UBR type virtual
connections. For cross-connected semipermanent connection ("PVCs") on both
VP and VC level policing can be enabled and disabled by using MML
command LBC. Traffic policing parameters are configured manually via
management interface when ATM Permanent Virtual Connection (PVC) is
created.

Issue 1.0 en
Note
Policing service is available only for CBR connections in NIS and MXU units.
Policing of low bit rate ATM interfaces (E1/T1/JT1) is performed in
Multiplexing unit (MXU).
ATM
ATMcell
cell ATM
ATMcell
cell
Check on PCR(CLP=0+1) and
CVDT (PCR)
Not Conforming Cell
Check on
SCR(CLP=0+1),BT(SCR) and
CVDT (SCR)
Not Conforming Cell
Conforming Cell
Figure 3. Possible example of Dual Leaky Bucket ( Peak Cell Rate,

Sustained Cell Rate, Burst Tolerance and Cell Delay Variation
Tolerance are Traffic Parameters described in the section 2.2 )
2.1.3 Traffic shaping
Traffic shaping is a mechanism that alters the traffic characteristics of a stream

of cells on a connection to achieve better network efficiency whilst meeting the
QoS objectives, or to ensure conformance in a subsequent interface. Traffic
shaping is performed by delaying (buffering) cells until they can be transmitted
in accordance with the traffic parameters.
Traffic shaping capability is particularly important when connecting across a
public User-Network Interface (UNI) to a public network, since many such
networks are basing their tariffs to a particular aggregate bandwidth.
An ATM network does not need to guarantee QoS performance for non-
conforming cells and thus a user wanting guaranteed QoS must shape traffic to
ensure conformance to the traffic parameters in an agreed traffic contract. A
network may employ shaping when transferring a cell flow to another network
in order to meet the conditions of a network-to-network traffic contract, or in

Issue 1.0 en
order to ensure that the receiving user application operates in an acceptable

way.
ATM Router ATM switch
Traffic policing
Traffic shaping
yes
...
Actual data Shaped data Within an envelope?

no
Figure 4. Traffic shaping and traffic policing
User A Network A Network B User B
Shaping Policing Shaping Policing Shaping
Shaping Policing Shaping Policing Shaping
Figure 5. Generic placement of policing and shaping functions
Note
Traffic shaping capability is implemented in each RNC/MGW computer or
signal processing (DMCU/TCU) unit terminating/originating traffic. Traffic
originating unit provides shaping of generated ATM traffic according to
configured traffic parameters. In addition Multiplexing unit (MXU) and NIS
units shape outgoing traffic per port.

Issue 1.0 en
2.1.4 Priority control
Cell loss priority bit in ATM cell header can be used to generate different
priority cell flows within a virtual path or channel connection. A network
element may selectively discard cells with low priority (CLP=1) before higher
priority cell (CLP=0) in congestion situation.
2.1.5 Frame Discard
If a congested network needs to discard cells, it may be better to drop all the
cells of one Protocol Data Unit (PDU) rather than to randomly drop cells
belonging to different PDUs. If a single cell is discarded, it may cause the
retransmission of the whole PDU, which in turn may cause more traffic when
congestion is already occurring. Discarding a packet may help to avoid
congestion in the ATM network and can increase throughput.
The two most common congestion control mechanisms implemented in ATM
are:
• Partial Packet Discard
If a cell is dropped from a switch buffer, the subsequent cells in the
higher layer protocol datagram are also discarded.
• Early Packet Discard
When the switch buffer queues reach a threshold level, the entire higher
level datagrams are dropped.
2.1.5.1 Partial Packet Discard (PPD)

This congestion control mechanism drops all subsequent cells from a PDU as
soon as one cell has been dropped. Once the switch drops a cell from a PDU,
the switch continues dropping cells from the same PDU until the end of the
PDU is indicated. The last cell is not discarded, as it is required to indicate the
end of the PDU and by implication indicate the start of the next PDU.
PPD offers limited improvement, because the switch begins to drop cells only
when the buffer overflows, the first cell dropped might belong to a packet in
which the majority of cells have already been forwarded. Also, when the switch
first drops a cell, the switch does not look in the buffer for earlier cells that
belong to the same packet. Therefore, cells from the corrupt packet may be
forwarded from the switch even though PPD is in effect.

Issue 1.0 en
Buffer positions
for cells
When the buffer reaches the
capacity, PPD discards the the
remaining cells, except the last
one.
PPD discards cells
Figure 6. Partial Packet Discard (PPD)
2.1.5.2 Early Packet Discard (EPD)

Early Packet Discard (EPD) greatly reduces the number of corrupted PDUs
transmitted, offering significant improvement over PPD. Whenever the
proportion of the buffer in use exceeds a fixed threshold, the ATM switch will
begin dropping entire PDUs prior to buffer overflow. The switch drops the first
arriving cell and all subsequent cells of that particular PDU. This will continue
until the number of cells in the buffer drops below the set threshold.
EPD only discards packets, which have already been buffered.
Buffer positions
for cells
When the buffer level exceeds the EPD

EPD threshold, the cells are Threshold
selectively discarded from the entire
frames
EPD Discards
Frames
Figure 7. Early Packet Discard (EPD)

Issue 1.0 en
2.2 Traffic contract and negotiation

Traffic contract negotiated during connection establishment consists of the
connection traffic descriptor, the requested QoS class and the definition of a
compliant connection. The values of the traffic contract parameters can be
specified either explicitly or implicitly. A parameter value is explicitly specified
in the initial call establishment message. This can be accomplished via
signalling for SVCs (Switched Virtual Connections) or via the Network
Management System (NMS) for PVCs (Permanent Virtual Connections). A
parameter value is implicitly specified when its value is assigned by the network
using default rules.
2.2.1 ATM quality of service (QoS)
One of the advantages of ATM is the QoS. The ATM supports QoS guarantees
for different types of traffic. The quality of service defines the performance to
be guaranteed. There are six QoS parameters. Three of these are negotiated
between the end system and the networks.
The QoS parameters that are negotiated:

• Cell Loss Ratio (CLR)
• Cell Transfer Delay (CTD)
• Cell Delay Variation (CDV)
The QoS parameters that are not negotiated:

• Cell Error Ratio (CER)
• Severely Errored Cell Block Ratio (SECBR)
• Cell Misinsertion Rate (CMR)
Propagation delay dominates the fixed delay component of CTD, while queuing
behaviour contributes to delay variations in heavily loaded networks. The
effects of queue service strategy and buffer sizes dominate loss and delay
variation performance in congested networks. Transmission link error
characteristics largely determine the CER, SECBR and CMR parameters. (For
further information on QoS parameters refer to appendix C at the end of this
module)

Issue 1.0 en
2.2.2 Traffic descriptors
The traffic parameters describe traffic characteristics of a source. The traffic

descriptors are the generic list of traffic parameters, which describe the traffic
characteristics of an ATM connection.
The traffic descriptor consists of:
• Peak Cell Rate (PCR)
The PCR represents the maximum allowable cell rate. It is defined as the
inverse of the minimum inter-arrival time T between two consecutive
cells. T is called the peak emission interval of the connection.
1
PCR =
min(T)
ATM cells
T
Figure 2. Peak Cell Rate (PCR)
• Sustained Cell Rate (SCR)

The SCR represents a theoretical average of the cell average rate ( cell )
transmission sustained over the duration of a transmission, for a VBR
connection.
1
SCR =
TSCR
TPCR Real Flow
TSCR Nominal Flow
Figure 3. Sustained Cell Rate (SCR)

Issue 1.0 en
• Burst Tolerance (BT)

The BT represents the maximum time in advance allowed to transmit a
cell compared to Its nominal transmission time : TSCR = 1 / SCR .
BT
TPCR Real Flow
TSCR Nominal Flow
Figure 4. Burst Tolerance (BT)
• The Maximum Burst Size (MBS)

The MBS specifies the maximum number of cells that can be transmitted
at PCR while still being compliant to the negotiated SCR
MBS = 6
TPCR Real Flow
TSCR Nominal Flow
Figure 5. Maximum Burst Size (MBS)

Issue 1.0 en
• Minimum Cell Rate (MCR)

The MCR represents the minimum user's required bandwidth or the
minimum cell rate guaranteed for the user. It is the descriptor used for
ABR service.
Figure 6. Minimum Cell Rate (MCR)
• Cell Delay Variation Tolerance (CDVT)

The CDVT gives information on the maximum time in advance allowed
for a cell arrival. It can be used with PCR and SCR.
TPCR
Nominal Flow
……..
t
CDVT CDVT CDVT

Real Flow
……..
t
t t t
t > (TPCR - CDVT) ⇒ OK
t ≤ (TPCR - CDVT) ⇒ NOT OK
Figure 7. Cell Delay Variation Tolerance (CDVT)
In the previous figure the fourth cell , in the real flow, is NOT OK .

Issue 1.0 en
2.2.3 Definition of a compliant connection
Once the connection has been accepted, the QoS requested is provided as long
as the connection is compliant with the traffic contract.
A connection is catalogued as compliant as long as the proportion of non-
conforming cells does not exceed a certain positive threshold, the value of
which has to be specified in the traffic contract by the network operator. For
non-compliant connections, the network does not need to respect the contracted
QoS, that is, the network could release the connection. For compliant
connections, the requested QoS has always to be supported by the network. (For
further information on Cell Conformance and Connection Compliance refer to
appendix D at the end of this module).
2.2.4 QoS classes
ITU-T recommendation I.356 defines QoS objectives for a reference

configuration spanning multiple ATM networks operated by different carriers.
The networks span distances of up to 27 500 km. Figure 14 shows the
provisional numerical values defined for different QoS classes. It presents
bounds on the end-to-end network performance. The ITU-T may change these
objectives to better or worse, values based upon actual operational experience.
The actual QoS offered to a given connection will depend on its distance and
complexity. It will often be better than the bounds in Figure 14.
QoS Parameter Notes QoS Class 1 QoS Class 2 QoS Class 3 U class
CTD Mean Value 400 ms Unspecified Unspecified Unspecified

CDV 2 point 10-8 quantile 3 ms Unspecified Unspecified Unspecified
CLR(0+1) Applies to CLP=0+1 3 * 10-7 10-5 Unspecified Unspecified
CLR(0) Applies to CLP=0 N/A Unspecified 10-5 Unspecified
CER Upper Bound 4* 10-6 4* 10-6 4* 10-6 Unspecified
CMR Upper Bound Once per Day Once per Day Once per Day Unspecified
SECBR Upper Bound 10-4 10-4 10-4 Unspecified
Figure 8. QoS class performance objectives

Issue 1.0 en
While establishing a new connection (VP or VC), calling users can signal their
preferred quality of service (QoS) class. The networks progress the connection
request towards the called user. If one of the networks is unable to support the
requested QoS class, the network will clear the connection request. As long as
the users comply with their traffic contract, the network providers should
support these end-to-end bounds for the duration of the connection.
2.3 ATM layer service categories

The traffic in ATM networks has different demands regarding the QoS. One
idea how to fulfil these requirements is to create so-called traffic classes, also
known as service categories. One service category has same kind of QoS
requirements.
Service classes divide connections into

Service Classes "main" classes (real time, non-real time,
bursty, etc.)
Traffic parameters define mainly the

Traffic Parameters bandwidth requirements
QoS parameters define finally the QoS of the

QoS Parameters connection: delay, cell loss, etc.
Figure 9. Relation between service classes, traffic parameters and QoS
ATM service categories include:

Constant Bit Rate (CBR) is used by applications that request a static amount
of bandwidth that is continuously available during the connection lifetime. This
amount of bandwidth is characterised by a peak cell rate value. In the CBR
capability, the source can emit cells at the peak cell rate at any time and for any
duration and the QoS commitments still pertain.

Issue 1.0 en
Bandwidth
Time
Figure 10. Constant bit rate (CBR)
Real time Variable Bit Rate (rt-VBR) service category is intended for real
time applications that transmit at a rate that varies over time. Rt-VBR
connections are characterised in terms of a peak cell rate, sustainable cell rate,
and maximum burst size. Cells that are delayed beyond the value specified by
maxCTD are assumed to be of significantly reduced value to the application.
Rt-VBR service category is not supported in the first RNC/MGW release.
Bandwidth
Time
Figure 11. Real time variable bit rate (rt-VBR)
Non-Real Time Variable Bit Rate (nrt-VBR) service category is intended for
non-real time applications which have bursty traffic characteristics. It has the
same traffic parameters as the rt-VBR. However, no delay bounds are
associated with this service category. Nrt-VBR service category is not
supported in the first RNC/MGW release.

Issue 1.0 en
Bandwidth
Time
Figure 12. None-real time variable bit rate (nrt-VBR)
Available Bit Rate (ABR) is intended for non-real time application sources
having ability to reduce or increase their information rate if the network requires
them to do so. The example of the application is LAN interconnection services.
ABR provides a guaranteed minimum capacity but allows data to be bursted at
higher capacities when the network is free. These are designated as the
Minimum Cell Rate (MCR) and the Peak Cell Rate (PCR), respectively. The
MCR may be specified as zero. A flow control mechanism is specified to
provide feedback to control the source rate. Although no specific QoS
parameter is negotiated, it is expected that an end system that adapts its traffic
in accordance with the feedback will experience a low cell loss ratio (CLR) and
obtain a fair share of the available bandwidth according to a network specific
allocation policy.
Unspecified Bit Rate (UBR) is meant for non-real time applications that do not
have strict requirements for delay and delay variance. UBR does not have
guaranteed QoS and is also known as 'best effort' traffic class.
Note
CBR is equivalent to DBR (Deterministic Bit Rate), whereas VBR is equivalent
with SBR (Statistical Bit Rate). The CBR and VBR are the terms used by ATM
Forum, while the DBR and SBR are used by ITU-T.
Figure 13 shows traffic descriptors and QoS parameters guaranteed by different

service categories and Figure 14 shows the suitable application for ATM service
categories.

Issue 1.0 en
Service Traffic Guarantees Use of

Category Description Feedback Application
Min Loss (CLR) Delay/Variance Bandwidth Control
CBR PCR, CDVT YES YES YES NO Circuit emulation,

Video conference
rt-VBR PCR, SCR, YES YES YES NO VBR video, silence

MBS, CDVT suppressed voice
nrt-VBR PCR, SCR, YES NO YES NO Critical data (e.g.

MBS, CDVT airline reservation,
banking transactions),
signalling
ABR PCR, MCR, YES NO YES YES Native ATM, Frame

CDVT Relay over ATM,
LAN
UBR PCR, CDVT NO NO NO NO LAN, email,
file transfer
Figure 13. Service category attributes and guarantees
Applications CBR rt-VBR nrt-VBR ABR UBR
Critical data Good Fair Best Fair No

LAN interconnection Fair Fair Good Best Good
WAN data transmission Fair Fair Good Best Good
Circuit emulation Best Good No No No
Telephony, videoconf. Best - - No No
Compressed audio Fair Best Good Good Fair
Video distribution Best Good Fair No No
Interactive multimedia Best Best Good Good Fair
Figure 14. Suitable applications for ATM service categories

Issue 1.0 en
3 Resource management in ATM network

The resource management is used for reserving resources of an ATM exchange
for different purposes such as signalling, routing and IP over ATM connections
as well as for permanent cross-connections through an ATM network element.
The resource management covers the following areas:
• Management of a Physical layer Trail Termination Point (phyTTP)
• Management of ATM interfaces, related to a Physical layer Trail
Termination Point (phyTTP)
• Management of the access profiles of ATM interfaces
• Management of VP Link termination points
• Management of VC Link termination points.
The following figures illustrate the resource creation order when building
connections on VC level.
VC connection creation order
phyTTP
ATM interface
Access profiles of ATM interfaces
VPL termination point (VPLtp)
VCL termination point (VCLtp)
VC connection
Figure 15. ATM resource creation order
The ATM resources are created on the external interfaces of a network element
and they form the basis for VP and VC level connections to other network
elements.

Issue 1.0 en
- VPI
- VPL service level: VP/VC
- usage e.g. MTP3SL, AAL2UD, IPOAM, AAL2SL, DNBAP, CNBAP
- service category: CBR/UBR
- traffic parameters: PCR, CDVT, SCR, Burst tolerance
- QoS class
2
Access profile of 3 4 O&M traffic (UBR, IPOAM)
ATM interface VP VP
- max bandwidth - VCI
- max VPI/VCI bits Lt VC - service category
VCLt
1 p, Lt - traffic and QoS parameters
Lt
p,
p p
RNC MGW
ATM logical interface

AT AT
M Signalling traffic (CBR, MTP3SL) M
Ph log VP VC VP logPh
Phy TTP
Phy TTP
VC
y ica Lt Lt Lt Lt
ica y
TT l p, p p p, l TT
P int int P
erf erf
User traffic (CBR, AAL2UD)
- phyTTP id ac VC VC ac
- PET/IMA/ SET/ VP Lt Lt VP
PROTGROUP Lt p p Lt
VC VC
p, Lt Lt
p,
- interface id
- UNI / NNI p p
- phyTTP id
Figure 16. Resource management in the ATM network
3.1 Physical Layer Trail Termination Point (phyTTP)

The phyTTP is used to hide the properties of the physical resources from the
upper protocol layers. It is configured between the physical layer and the ATM
Layer. The only interesting property from the upper layer point of view is the
capacity of the phyTTP that can be used to transport the protocol data units of
the upper layer, for example ATM cells. A Physical layer Trail Termination
Point (phyTTP) can consist of one of the following: a single PET, an IMA
group, a single SDH VC path or an SDH protection group.

Issue 1.0 en
Figure 17. Physical layer Trail Termination Point (phyTTP)
3.2 ATM interface

The ATM interface is an external logical interface, under which the connections
are built. The ATM interface can work as:
• UNI (User Network Interface) or
• NNI (Network Node Interface).
UNI refers to the interface between terminal equipment and a network
termination where access protocols apply. In an ATM network, the interface
between a RNC and a WCDMA BTS is seen as an UNI interface.
The NNI interface is the interface between two network nodes like a RNC and
an MGW.
When an ATM interface is created, it is tied up to a Physical layer Trail
Termination Point (phyTTP).
The capacity of an ATM interface must be smaller than the capacity of the
object it is tied up to.
For further information on ATM Interface creation, refer to refer to Nokia on-
line document.

Issue 1.0 en
3.3 Access profile of ATM interface

The access profile created for an ATM interface defines the connection
structure built under that ATM interface. The following parameters have
to be specified :
• interface id
• the maximum ingress and egress transmission bandwidth
• the maximum ingress and egress bandwidth unit
• the maximum number of VPI bits
• the maximum number of VCI bits
Interface id
This parameter identifies the ATM interface whose access profile
you want to create. The parameter value is a decimal number
ranging from 1 to 320.The parameter is obligatory.
The maximum bandwidth values

This parameter identifies the numerical value of the maximum ingress
transmission bandwidth at the ATM interface. The parameter value is a decimal
number ranging from 10 to 9999.
The maximum allowed ingress and egress transmission bandwidth value given
for the access profile of a STM-1 interface is 149760 kbit/s, that is 353 207 c/s
(= the payload). The remaining resource (5760 kbit/s) is available only for the
physical layer overhead.
In case of an ATM interface connected to an E1 transmission link, the
maximum allowed bandwidth is 4528 c/s. In case of an ATM interface
connected to a T1 transmission link, the maximum value is 3622 c/s.
When an ATM interface is connected to an IMA group, IMA frames use a part
of the payload, as the IMA frame length is not currently modifiable. Therefore,
you can calculate the maximum allowed bandwidth for an ATM interface with
an IMA group with the following formula:
0.99 x <number of E1/T1 links> x <maximum allowed bandwidth for E1/T1>.
For example, if the ATM interface is tied up to an IMA group with 3*2 Mbit/s
lines, the maximum bandwidth is 0.99*3*4528 c/s = 13448 c/s.
For further information on calculating bandwidth, refer to Inverse Multiplexing
for ATM (IMA) Specification Version 1.1, ATM Forum.

Issue 1.0 en
The maximum ingress and egress bandwidth unit

This parameter identifies the unit of the maximum ingress/egress transmission
bandwidth at the ATM interface. The parameter can have the following values:
CPS Cells per second
KCPS Kilo-cells per second
MCPS Mega-cells per second
Note
The egress bandwidth (for outgoing traffic) cannot be defined larger than the
capacity of the neighbouring ATM exchange; otherwise ATM cells are lost.
VPI bits and VCI bits
The maximum number of VPI bits defines the space (number of bits) available
for specifying the VPLtp's under the interface. This defines the maximum
number of Virtual Paths (VPs). For example, if the space reserved for VPI is 4
bits, it means that the maximum number of VPLtp's that can be created under
the ATM interface is 16 (= 24). This parameter identifies the maximum number
of allocated bits of the VPI sub field for the defined ATM interface. The
parameter is used by the system to select the appropriate VPI values when
establishing ATM connections. The parameter value can range from 1 to 8 for a
UNI interface and from 1 to 12 for an NNI interface.
The maximum number of VCI bits defines the space (number of bits) available
for specifying VCLtp's under the interface. This defines the maximum number
of Virtual Channels (VCs) that can be created inside each virtual path. For
example, if the space reserved for VCI is 8 bits, the maximum number of
VCLtp's that can be created under a VPLtp is (= 28) - 1 = 255 (VCI with value 0
is not allowed). This parameter identifies the maximum number of allocated bits
of the VCI sub field per VPLtp of the defined ATM interface. This parameter is
used by the system to select the appropriate VCI values when establishing ATM
connections.
The parameter value can range from 1 to 14 for both UNI and NNI
interface. You should select the lowest possible value.
The VCI values 1 - 31 are reserved for specific purposes. For example, VCI 3
and VCI 4 are reserved for O&M (operation and maintenance). For this reason,
you must use VCI number 32 or bigger for an external VC connection. When
creating an access profile, you should reserve at least 6 VCI bits (= 26 different
VCI values).

Issue 1.0 en
It depends on the network level planning how the ATM interface and its access
profile, and thus the connections, should be created. For example, there can be
many Virtual Paths with a few Virtual Channels inside each path, or only a few
large VPs with numerous VCs inside each path.
3.4 VP/VC Link termination point

External termination points are created both on VP level and VC level. They are
the terminating ends of the VP/VC connections. Virtual Path Link termination
points (VPLtp's) must be created before any Virtual Channel Link termination
points (VCLtp's) and VC level connections can be created under the VPLtp.
Each VPLtp is related to one ATM interface. The interface configuration
defines the limits to the total VPLtp capacity reservations.
The number of VCLtps created under each VPLtp depends on the total VPLtp
capacity. Therefore, when reserving capacity for a VPLtp, you should plan how
many VC level connections are needed under that VPLtp.
Termination points are reserved for:
• Signalling links on VC level
• VCC endpoints and thus for allowing the creation of AAL type 2
connections for user traffic
• IP over ATM connections on VC level
• Permanent Virtual Connections (PVCs) on VP and VC level inside an
ATM network element.
When creating a VPLtp with VC service level, you define the purpose, for
which the VPLtp and the underlying VCLtps will be used.
For further information on VP/VC link termination point, refer to Nokia on-line
document.
Service category and conformance definition

In the current ATM network, the service category CBR (Constant Bit Rate) is
applied for user plane and signalling traffic, and the service category UBR1
(Unspecified Bit Rate) is applied for IP over ATM connections. The
conformance definition must comply with the service category used. The
VCLtp's created under a certain VPLtp of UBR1 type must have the same
service category and conformance definition as that VPLtp. However, you can
create VCLtp's of UBR1 type under a VPLtp of CBR type.
For further information on service category and conformance definition, refer to
the Appendix D or Traffic Management Specification Version 4.1, ATM Forum.

Issue 1.0 en
Figure 18 to Figure 21 show the ATM resource management at Iub, Iur, Iu-CS
and Iu-PS.
- VPI
- traffic and QoS parameters
2 3 4 O&M traffic (UBR, IPOAM)

Access profile of VP V V
VP
- VCI
ATM interface Lt CL - service category CL Lt
- max bandwidth p, tp tp p,
- max VPI/VCI bits
- max VPC/VCC Signalling and user traffic (CBR, AA2SL, DNBAP, CNBAP, AAL2UD)
1 VC VC
Lt Common NBAP signalling Lt
BS
RNC p p

VC VC
Lt Dedicated NBAP signalling Lt
p p
VC VC
Lt Dedicated NBAP signalling Lt WAM
Phy TTP
Phy TTP
p p
VC VC VP
Lt SAAL UNI (AAL2) signalling Lt WAM
VP p p Lt
VP
VC VC
Lt Lt SAAL UNI (AAL2) signalling Lt p,
Lt
p p
p, VC VC
p,
Lt User traffic Lt
p p
phyTTP id VC VC
Lt User traffic Lt
PET/IMA/ SET/ p p
PROTGROUP VC VC
Lt User traffic Lt
- interface p p
VC VC
- UNI / NNI Lt User traffic Lt
- IMAGR /PET p p
Figure 18. ATM resource management at Iub interface
- VPI
2
3 4 O&M traffic (UBR, IPOAM)
Access profile of
ATM interface VP VP
- VCI
- max bandwidth Lt V - service category
V
Lt
- max VPI/VCI bits 1 p, CL - traffic and QoS parameters
CL
- max VPC/VCC tp tp p,
RNC RNC
Signalling and user traffic (CBR, MTP3SL, AAL2UD)
Phy TTP
Phy TTP
V V
CL For RNSAP, AAL2 (MTP3SL) signalling CL
VP tp tp VP
Lt Lt
phyTTP id p, p,
PET/IMA/ SET/ V V
PROTGROUP CL User traffic CL
tp tp
- interface id
- UNI / NNI
- IMAGR/ PET /SET

Issue 1.0 en
Figure 19. ATM resource management at Iur interface
- VPI
2
Access profile of
ATM interface VP - VCI
VP
- max bandwidth Lt V - service category
V
Lt
- max VPI/VCI bits CL - traffic and QoS parameters CL
- max VPC/VCC 1 p, tp tp p,
MGW

RNC Signalling traffic (CBR, MTP3SL)
VPV VP
Phy TTP
Phy TTP
V
Lt CL For RANAP, AAL2 (MTP3SL) signalling
CLLt
p, tp tp p,
User traffic (CBR, AAL2UD)

phyTTP id
VC VC
PET/IMA/ SET/ VP Ltp User traffic Ltp VP
PROTGROUP
Lt Lt
VC VC
- interface id p, Ltp User traffic Ltp p,
- UNI / NNI
- IMAGR/PET/ SET
Figure 20. ATM resource management at Iu-CS interface

Issue 1.0 en
- VPI
2
Access profile of
ATM interface VP VP
- VCI
- max bandwidth Lt VC - service category
VCLt
- max VPI/VCI bits 1 p, Ltp - traffic and QoS parameters
Ltp
p,
- max VPC/VCC

RNC SGSN
Signalling traffic (CBR, MTP3SL)
Phy TTP
Phy TTP
VP VP
VC VC
Lt Ltp For RANAP and AAL2 (MTP3SL)signalling LtpLt
p, p,
User traffic (UBR, IPOAM)

phyTTP id
PET/IMA/ SET/ VP VC
VP
PROTGROUP
VC For user traffic
Lt Ltp Ltp Lt
(one per GTPU unit)
- interface id p, p,
- UNI / NNI
- IMAGR/PET/ SET
Figure 21. ATM resource management at Iu-PS interface

Issue 1.0 en
4 Routing and digit analysis

Analysis and routing are needed in the network element for directing user plane
traffic, voice, or data connections to the desired destination and for finding free
resources for the connection. Analysis and routing also offer functions to
configure and manage the routing and analysis -related objects.
Digit analysis and routing are closely connected to each other. They function in
a call setup phase.
4.1 Digit analysis

The purpose of the digit analysis is to find a destination for the call and to select
a route to the destination.
Digit analysis analyses the digit sequences that it receives. Typically the
received sequence is an address of the receiving end, but digit analysis may be
used to analyse any number sequence that can be analysed hierarchically digit
by digit. The received digits are analysed in an analysis tree to locate the
destination for the connection. An analysis tree is a chain of records in an
analysis file beginning from the first digit of the analysed number sequence.
Each unique set of digits is associated with a destination.
Destination is comprised of one or more routing alternatives. Subdestination
determines which ATM route is selected. Subdestination is always mapped to
one route.
When the result of digit analysis is the route, it is the starting point of routing.
Digits Analysis Tree
Digit
Digit Analysis
Analysis
Destination Subdestination
Destination
Destination
Main
Main functions:
functions:
Subdestination
Subdestination 55 •• Analyze
Analyze the
the E.164
E.164 number
number
Subdestination
Subdestination 44 and
and to
to find
find destination
destination of
of
Route
Route
Subdestination
Subdestination 33
Route the
the call
call
Subdestination
Subdestination 22 Route •• Select
Select aa route
route for
for the
the
Subdestination
Subdestination 11 Route
“primary” Route destination
destination
“primary”
Route
Figure 22. Digit analysis

Issue 1.0 en
Note
Currently there is only one subdestination alternative in the RNC. In the future
more than one subdestination might be implanted to support, for example,
different QoS requirements in AAL2 transport.
Note
In IPA2800 A3 there will be digit analysis in MGW to transfer Iur traffic
through MGW.
Digit analysis is used in the RNC for finding a route to another RNC (in Iur
interface) or to BS (in Iub interface). The digit is analysed when a new
connection at Iur or Iub is needed; for example, a new call establishment or soft
handover branch to the existing call is going to be added.
Digit analysis gets the address of other network element and finds the route for
the destination by analysing the address. The address to be analysed in RNC is
AAL2 Service Endpoint Address (A2EA) which uses AESA format. The
address points to a certain AAL2 or ATM termination point in the neighbouring
node.
4.2 Routing
Routing is used for finding free resources under a given route for connections
going to another network element.
Route can be seen as a common concept in ATM/TDM environment.
In ATM, concept of circuit groups/circuits, used in TDM, are replaced by new
concepts:
− Virtual Channel Connection Endpoint Group (VCCEG)
− Virtual Channel Connection Endpoint (VCCE)
Routing manages these objects and provides selection of VPCs/VCCs

according to needed quality of service (QoS) and traffic parameters.

Issue 1.0 en
AAL2 connections
VCs VP
Transmission Path
VCs VP
Figure 23. AAL type 2 connection inside a virtual channel
Route
(common concept)
Circuit Group VCCE group
Circuit VCCE
Figure 24. Routing
The VCCE identifies the VC Link termination point (VCLtp), under which the
AAL2 connection (CID) is created.
In RNC and MGW, where AAL2 level signalled connections are used, only
AAL2 level routing is used for user traffic. Routing is used for finding a
suitable Virtual Channel Connection (VCC) candidate under a given route
having free resources and providing desired properties for the connection.
Under this selected VCC an AAL type 2 connection may be created. AAL type
2 is finally the level where all user traffic is carried between the ATM network
elements.

Issue 1.0 en
4.3 Routing objects in ATM network

In ATM network element, where AAL type 2 level routing is used as in RNC
and MGW, the routing objects are destination, subdestination, ATM route, VCC
endpoint groups and VCC endpoints.
Figure 22 shows the digit analysis and routing hierarchy in IPA2800, which is
the platform for RNC and MGW.
Digits Analysis tree
Digit analysis
Destination
Subdestination
ATM route
max 16 endpoint groups/1 route
VCC endpoint group VCC endpoint group

max 50 endpoints/ endpoint group
VCCep VCCep VCCep VCCep
AAL type 2 connection
Figure 25. Digit analysis and routing hierarchy in IPA2800
Destination is the result of digit analysis and it is obtained on the basis of the
call origin and received address. Destination symbolises the end node where the
connection is routed.
Subdestination is a routing alternative and it always belongs to some
destination. Subdestination provides necessary routing data that is needed in the
connection establishment phase.
Routes in this context mean external ATM routes that consist of one or more
hunted Virtual Paths (VPs) or Virtual Channels (VCs), which connect two ATM
network elements and are using the same signalling protocol.
In RNC and MGW, only AAL type 2 level routing is used for all user traffic.
The AAL type 2 connections are built inside an AAL type 2 path (VCC). VCC
extends between two Virtual Channel Connection endpoints and it is identified
with an AAL type path identifier. Therefore, ATM routes consist always of
VCC endpoints.

Issue 1.0 en
VCC endpoint group is a group of individual VCC endpoints having similar

properties. Under one ATM route there may be one or several endpoint groups.
When routing starts selecting a VCC for the connection, it first finds a suitable
VCC endpoint group and then selects one VCC endpoint from that group
according to the routing algorithm.
After a suitable VCC has been selected by routing, AAL type 2 connection
control selects a free AAL type 2 channel for the AAL2 type 2 connection under
this VCC.
Operations related to the AAL type 2 connections are managed by AAL type 2
connection control, which also automatically allocates a Channel Connection
Identifier (CID) value for each AAL type 2 connection.
In ATM, routing has a close relationship to Connection Admission Control
(CAC). It is different from the TDM world. In TDM, when a free circuit is
hunted, the resource is found for the connection. In ATM, CAC is needed after
selection of VPC/VCC. CAC decides finally if the new connection can be
accepted without violating the guaranteed quality of service for existing
connections.
NE1 (RNC)
Sub
Destination destination
Route 13
Digit
Endpoint group
VPI 41, VCI 120 (for AAL2UD)
Tree 23 NE2 NE2 VPI 41, VCI 121 (for AAL2UD)
NE2
VPI 41, VCI 122 (for AAL2UD)
(RNC or BS)
Figure 26. Routing objects
Note
In RNC there is only one subdestination alternative.

Issue 1.0 en
The following steps show the function of the digit analysis and routing:
1. Digits are directed into digit analysis.

2. Digit analysis goes through the received digit sequence and the
information about the origin of the call in digit analysis tree in order to
find a destination for the call.
3. The destination provides the subdestination. In the Iub and Iur interfaces
each destination currently provides only one subdestination.
4. The subdestination determines which external ATM route is used for the
connection.
5. The external ATM route is used for directing the call to another
exchange. Under the ATM route the routing selects an appropriate VCC
endpoint group.
6. Under the VCC endpoint group the routing selects an appropriate VCC
endpoint and thus an appropriate virtual channel.
7. Finally, AAL2 connection control selects a free AAL type 2 channel for
making the connection.
The number of ATM routes to be created depends on the number of

neighbouring network elements and the capacity of the exchange.
Under each ATM route there can be up to 16 endpoint groups, which have the
ingress and egress service categories as characteristics. These must fit with the
values of the Virtual Channel Link termination points (VCLtp's) that will
become endpoints. Each endpoint group can include max. 50 endpoints.

Issue 1.0 en
5 Review of ATM resource management

and digit analysis
Please take some time and use the material in this module to answer the
following questions.
Name five ATM traffic management functions.
An ATM traffic contract includes the following information.

a.
d. Right
Mark the abbreviations indicating ATM services classes.
PCR CDV CBR x CMR
CDVT VBR x CLR SCR MBS
CER SECBR ABR x
UBR x MCR maxCTD BT
Mark the abbreviations indicating QoS parameters.
PCR CDV x CBR CMR x
CDVT VBR CLR x SCR MBS
CER x SECBR x ABR

UBR MCR maxCTD x BT Issue 1.0 en
Mark the abbreviations indicating ATM traffic descriptors.
PCR x CDV CBR CMR
CDVT x VBR CLR SCR x MBS x
CER SECBR ABR
UBR MCR x maxCTD BT x
What is the purpose of ATM resource management?

a.
d. Right
8. When creating ATM resources, in which order should the following steps
be performed?
9. What have to be done before creating routing and digit analysis?

(Select two choices.)
Right
Right

Issue 1.0 en
Appendix A: ATM quality of service (QoS)
1. Terminology
• Cell Exit Event
A “Cell Exit Event” occurs when the first bit of an ATM cell has completed
transmission out of an end-system.
• Cell Entry Event
A “Cell Entry Event” occurs when the last bit of an ATM cell has
completed transmission into an end-system.
Successful Cell Transfer Outcome:
The cell is received, corresponding to the transmitted cell, within a specified
time Tmax. The binary content of the received cell conforms exactly to the
corresponding transmitted cell payload and the cell is received with a valid
header field after header error control procedures are completed.
Errored Cell Outcome:
The cell is received corresponding to the transmitted cell within a specified
time Tmax. The binary content of the received cell payload differs from that
of the corresponding transmitted cell payload or the cell is received with an
invalid header field after header error control procedures are completed.
Lost Cell Outcome:
No cell is received corresponding to the transmitted cell within a specified
time Tmax. (Examples include “never received” or “late”.)
Misinserted Cell Outcome:
A cell is received, for it there is no corresponding transmitted cell
Severely-Errored Cell Block Outcome:
When M or more
Lost Cell outcomes,
Misinserted Cell Outcomes,
Errored Cell outcomes
are observed in a received cell block of N cells transmitted consecutively on
a given connection.
2. The QoS parameters that are negotiated:

• Cell Loss Ratio (CLR)
The Cell Loss Ratio is defined as follows for a connection :
Lost Cell
CLR =
Total Transmitted Cells
The CLR objective applies either to the CLP=0 cell flow or to the
aggregate CLP=0+1 cell flow, as determined by the applicable
conformance definition.

Issue 1.0 en
• Cell Transfer Delay (CTD) and Cell Delay Variation (CDV)

The measured Cell Transfer Delay (CTD) is defined as the elapsed time
between a cell exit event at measurement point 1 (MP1) (e.g., at the
source ) and the corresponding cell entry event at measurement point 2
(MP2) (e.g., the destination ) for a particular connection. The Cell
Transfer Delay between two measurement points is the sum of the total
inter-ATM node transmission delay and the total ATM node processing
delay between MP1 and MP2.
Two end-to-end delay parameter objectives are negotiated:
- peak-to-peak CDV
- max CTD
The figure below illustrates the probability density function of the CTD
(in CBR and real-time VBR services), and relates it to the peak-to-peak
CDV and max CTD parameters.
Probability
density
1-α
α Cell Transfer Delay
Fixed Delay Peak to peak CDV Cells delivered late

or lost
Max CTD
Figure 27. Cell transfer delay probability density model (for real-time service categories)
The max CTD parameter represents the maximum Cell Transfer Delay
allowed in the connection.

Issue 1.0 en
The peak-to-peak CDV is the difference the best and worst case of CTD,
where the best case is equal to the fixed delay, and the worst case is equal
to a value likely to be exceeded with probability no greater than α.
The components of the fixed delay include propagation through the
physical media, delays induced by transmission system, and fixed
components of switch processing delay. CDV is induced by buffering,
cell scheduling and the variable components of switch processing delay.
Two measurement methods are defined for CDV. These are:
− One-point cell delay variation (one-point CDV)
The one-point CDV describes the variability in the pattern of cell arrival
events observed at a single measurement point with reference to the
negotiated peak rate 1/T
The one-point CDV for cell k (Yk) at a measurement point is defined as
the difference between the cell’s reference arrival time (Ck) and actual
arrival time (Ak) at the measurement point: Yk = Ck - Ak.
The reference arrival time (Ck) is defined as follows:
C0 = A0
Ck+1 = Ak+T if Ck ≤ Ak
Ck+1 = Ck+T Otherwise
Positive values of the one-point CDV correspond to cell clumping;

negative values of the one-point CDV correspond to gaps in the cell
stream. The reference arrival time defined above eliminates the effect of
gaps and provides a measurement of cell clumping.
− Two-point cell delay variation (two-point CDV)

The two-point CDV describes the variability in the pattern of cell arrival
events observed at the output of a connection portion (MP2) with
reference to the pattern of the corresponding events observed at the input
to the connection portion (MP1).
The two-point CDV for cell k (Vk) between two measurement points
(MP1 and MP2) is the difference between the absolute cell transfer delay
of cell k (Xk) between the two MPs and a defined reference celltransfer
delay (d1,2) between MP1 and MP2: Vk = Xk - d1,2.
The absolute cell transfer delay (Xk ) of cell k between MP1 and MP2 is
the Cell Transfer Delay . The reference cell transfer delay (d1,2) between
MP1 and MP2 is the absolute cell transfer delay experienced by a
reference cell between the two MPs.

Issue 1.0 en
The negotiated objective for CDV performance is expressed in terms of

peak-to-peak CDV.
Note: The QoS parameter CDV should not be confused with the
connection traffic parameter CDVT (see section 2.2.2 Traffic
Descriptors)
3. The QoS parameters that are not negotiated:

• Cell Error Ratio (CER)
The Cell Error Ratio is defined as follows for a connection :
Errored Cells
CER =
Successfully Transferred Cells + Errored Cells
• Severely Errored Cell Block Ratio (SECBR)

The Severely Errored Cell Block Ratio is defined as follows for a
connection :
Severely Errored Cell Blocks

SECBR =
Total Transmitted Cell Blocks
A cell block is a sequence of N cells transmitted consecutively on a given

connection. A severely errored cell block outcome occurs when more than M
errored cells, lost cells, or misinserted cell outcomes are observed in a received
cell block.
• Cell Misinsertion Rate (CMR)

The Cell Misinsertion Rate is defined as follows for a connection :
Misinserted Cells
CMR =
Time Interval
Cell misinsertion on a particular connection is most often caused by an

undetected error in the header of a cell being transmitted on a different
connection. This performance parameter is defined as a rate (rather than the
ratio) since the occurrence of misinserted cells is independent of the number of
transmitted cells received on the corresponding connection.

Issue 1.0 en
Appendix B: GCRA & Conformance Definitions
1. Generic Cell Rate Algorithm ( GCRA )

The GCRA is used to define conformance with respect to the traffic contract.
For each cell arrival, the GCRA determines whether the cell conforms to the
traffic contract of the connection. The UPC/NPC function may implement the
GCRA, to enforce conformance.
The GCRA is a virtual scheduling algorithm or a continuous-state Leaky Bucket
Algorithm as defined by the flowchart in Figure.XX (The RNC/MGW supports
a dual leaky bucket policing algorithm ).
Figure 28. Equivalent version of the GCRA

Issue 1.0 en
The GCRA is used to define, in an operational manner, the relationship between

PCR and the CDVT, and the relationship between SCR and the Burst Tolerance
(BT). The BT can be derived from PCR, SCR, and MBS as follows :
BT BT =( MBS -1)*(TSCR − TPCR )

MBS = inf( 1 + )
TSCR - TPCR
Tburst = TPCR * (MBS -1)
The GCRA is defined with two parameters: the Increment (I) and the Limit (L).
The notation “GCRA(I,L)” means the Generic Cell Rate Algorithm with the
value of the increment parameter set equal to I and the value of the limit
parameter set equal to L.
Note: I and L are not restricted to integer values.
The GCRA is formally defined in Figure xx. Figure xx is a generic version of
Figure 1 in Annex 1 of I.371. The two algorithms in Figure xx are equivalent in
the sense that for any sequence of cell arrival times, {ta(k), k >= 1}, the two
algorithms determine the same cells to be conforming and thus the same cells to
be non-conforming.
Multiple instances of the GCRA with possibly different I and L parameters may
be applied to multiple flows (CLP=0 and CLP=0+1) of the same connection, or
to the same flow. A cell is then conforming only if it conforms to all instances
of the GCRA against which cells with its CLP state are tested. For example, if
one instance of the GCRA tests the CLP=0 flow and one instance tests the
CLP=0+1 flow, then a CLP=0 cell is conforming only if it conforms to both
instances of the GCRA. In this same configuration, a CLP=1 cell is conforming
only if it conforms to the instance of the GCRA that tests the CLP=0+1 flow. If
tagging is used, a tagged cell is conforming only if it conforms as a CLP=1
cell..

Issue 1.0 en
2. Conformance Definitions
Conformance applies to cells as they pass at an interface and are, in principle,
tested according to some algorithm. The first cell of the connection initializes
the algorithm and from then on each cell is either conforming or non-
conforming. Even under ideal conditions some cells may be non-conforming.
Therefore it is inappropriate for the network to only commit to the QoS
objectives for those connections for which all cells are conforming. In effect,
connection compliance does not imply that all cells associated with the
connection are conforming.
For CBR, rt-VBR, nrt-VBR, and UBR, the conformance definition defines
conformity at an interface according to one or more instances of the GCRA
algorithm.
2.1 Conformance Definitions for CBR service
2.1.1 CBR.1: Conformance Definition for PCR (CLP=0+1)

The following is a conformance definition for a source traffic
descriptor that specifies PCR for the CLP=0+1 cell stream:
1. One GCRA(T0+1 , CDVT) defining the CDVT in relation to the

PCR of the CLP=0+1 cell stream. T0+1 is the inverse of the PCR
specified for the CLP=0+1 cell flow.
2. A cell that is conforming to the GCRA in (1) is said to be

conforming to the connection traffic descriptor.
The tagging option is not applicable to this conformance
definition since no separate rate is specified for CLP=0. The CLR
objective applies to the aggregate CLP=0+1 cell stream.
ATM cell ATM cell

ATM cell ATM cell Check on PCR(CLP=0+1)
and CVDT(PCR)
Leaky rate = PCR

Not Conforming Cell
Conforming Cell

Issue 1.0 en
2.2 Conformance Definitions for rt-VBR and nrt-VBR

2.2.1 VBR.1: Conformance Definition for PCR (CLP=0+1) and
SCR (CLP=0+1)
descriptor that specifies PCR for the CLP=0+1 cell stream and
SCR for the CLP=0+1 cell stream:
1. One GCRA(T0+1, CDVT) defining the CDVT in relation to the
PCR of the CLP=0+1 cell stream. T0+1 is the inverse of PCR
(CLP=0+1).
2. One GCRA(TS0+1 , BT0+1+CDVT) defining the sum of the
CDVT and the BT in relation to the SCR of the CLP=0+1 cell
stream. TS0+1 is the inverse of SCR (CLP=0+1).
3. A cell that is conforming to both GCRAs (1) and (2) above is
said to be conforming to the connection traffic descriptor.
The tagging option is not applicable to this conformance
definition. The CLR objective applies to the aggregate CLP=0+1
cell stream.
ATM cell ATM

ATM cell ATMcell
cell Check on PCR(CLP=0+1) and
CVDT (PCR)
Leaky rate = PCR

Not Conforming Cell
Check on SCR(CLP=0+1),BT(SCR)
and CVDT (SCR)
Not Conforming Cell Leaky rate = PCR
Conforming Cell

Issue 1.0 en
2.2.2 VBR.2: Conformance Definition for PCR (CLP=0+1) and SCR

(CLP=0)
SCR for the CLP=0 cell stream :
1. One GCRA(T0+1 , CDVT) defining the CDVT in relation to the
(CLP=0+1).
2. One GCRA(TS0 , BT0+CDVT) defining the sum of the CDVT
and the BT in relation to the SCR of the CLP=0 cell stream. TS0 is
the inverse of SCR (CLP=0).
3. A CLP=0 cell that is conforming to both GCRAs (1) and (2)
above is said to be conforming to the connection traffic
descriptor. A CLP=1 cell that is conforming to GCRA (1) above
is said to be conforming to the connection traffic descriptor.
ATM
ATMcell
cell ATM
ATMcell
cell Check on PCR(CLP=0+1)
and CVDT(PCR)
Leaky rate = PCR

Not Conforming Cell
CLP=1 CLP=0
CLP
Conforming Cell Check on SCR(CLP=0),
BT(SCR) and CVDT(SCR)
Leaky rate = PCR

Not Conforming Cell
CLP=0 Conforming Cell
CLP=0

Issue 1.0 en
2.2.3 VBR.3: Conformance Definition for PCR (CLP=0+1) and SCR

(CLP=0)
SCR for the CLP=0 cell stream :
(CLP=0+1).
2. One GCRA(TS0, BT0+CDVT) defining the sum of the CDVT
and the BT in relation to the SCR of the CLP=0 cell stream. Ts0
is the inverse of SCR (CLP=0).
3. A CLP=0 cell that is conforming to both GCRAs (1) and (2)
above is said to be conforming to the connection traffic
descriptor. A CLP=1 cell that is conforming to GCRA (1) above
is said to be conforming to the connection traffic descriptor.
4. If the end-system requests tagging, and if tagging is supported
by the network, a CLP=0 cell that is not conforming to GCRA (2)
above, but is conforming to GCRA (1) above, will have its CLP
bit changed to 1 and is said to be conforming to the connection
traffic descriptor.
ATM cell ATM cell

and CVDT(PCR)
Leaky rate = PCR

Not Conforming Cell
CLP=1 CLP=0
CLP
Conforming Cell Check on SCR(CLP=0),
BT(SCR) and CVDT(SCR)
Leaky rate = PCR

Not Conforming Cell
CLP=0 Conforming Cell
If the end-system requests
Tagging CLP=0
CLP=1

Issue 1.0 en
2.3 Conformance Definitions for UBR

2.3.1 UBR.1 : Conformance Definitions for PCR (CLP=0+1)
Tagging not applicable

1. One GCRA(T0+1, CDVT) defining the CDVT in relation to

the PCR of the CLP=0+1 cell stream. T0+1 is the inverse of the
PCR specified for the CLP=0+1 cell flow.

The tagging option does not applies. The Network shall not
overwrite the CLP bit.
The CLR objective does not applies to the cell stream.
ATM cell ATM cell

and CVDT(PCR)
Leaky rate = PCR

Not Conforming Cell
The tagging option does not

applies. Conforming Cell
The Network shall not
overwrite the CLP bit

Issue 1.0 en
2.3.2 UBR.2 : Conformance Definitions for PCR (CLP=0+1)

Tagging applicable

PCR of the CLP=0+1 cell stream. T0+1 is the inverse of the PCR
specified for the CLP=0+1 cell flow.

The tagging option applies. The Network may overwrite the
CLP bit to 1 for any cell of the connection. However, such
action does not necessarily imply a condition of non-
conformance, as would be the case for other service categories.
The CLR objective does not applies to the cell stream.
ATM cell ATM cell

and CVDT(PCR)
Leaky rate = PCR

Not Conforming Cell
The tagging option applies.

The Network may overwrite Conforming Cell
the CLP bit to 1

Issue 1.0 en
Abbreviations
AAL2 ATM Adaptation Layer 2
AESA ATM End System Address
ANI Adjacent AAL2 Node Identifier
ATM Asynchronous Transfer Mode
B-ISDN Broadband Integrated Services Digital Network
BS Base Station
CAC Connection Admission Control
CBR Constant Bit Rate
CDVT Cell Delay Variation Tolerance
CID Channel Identifier
GUI Graphical User Interface
IMA Inverse Multiplexing for ATM
ISO International Standards Organisation
MGW Media Gateway
MSC Mobile Switching Centre
MTP3b Broadband Message Transfer Part level 3
NIP1 Network Interface Unit for PDH-based ATM interfaces
NIS1 Network Interface Unit for two physical (optical) STM-1 interfaces
NNI Network Node Interface
NSAP Network Service Access Point
PDH Plesiochronous Digital Hierarchy
PVC Permanent Virtual Connection
QoS Quality of Service
RNC Radio Network Controller
SAAL Signalling ATM Adaptation Layer
SDH Synchronous Digital Hierarchy
STM-1 Synchronous Transport Module One (optical) 155 520 kbit/s
TDM Time Division Multiplexing
TPI Termination Point Identifier
UBR Unspecified Bit Rate
UMTS Universal Mobile Telecommunication System
UNI User Network Interface

Issue 1.0 en
VC Virtual Channel
VCCE Virtual Channel Connection Endpoint
VCCep Virtual Channel Connection Endpoint
VCI Virtual Channel Identifier
VCLtp Virtual Channel Link Termination Point
VP Virtual Path
VPC Virtual Path Connection
VPCE Virtual Path Connection Endpoint
VPCep Virtual Path Connection Endpoint
VPCEG Virtual Path Connection Endpoint Group
VPI Virtual Path Identifier
VPLtp Virtual Path Link Termination Point
WCDMA Wideband Code Division Multiple Access

Issue 1.0 en

02 - ATM Traffic - and Resource Management

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

02 - ATM Traffic - and Resource Management

Uploaded by

Copyright:

Available Formats

3G Platform

3G ATM - ATM Traffic- and

6-282561 © Nokia Networks Oy 1 (51)

6-282561 © Nokia Networks Oy 3 (51)

2 ATM traffic management....................................................................... 6

3 Resource management in ATM network ........................................... 21

4 Routing and digit analysis.................................................................. 30

5 Review of ATM resource management and digit analysis .............. 36

4 (51) © Nokia Networks Oy 6-282561

6-282561 © Nokia Networks Oy 5 (51)

2 ATM traffic management

2.1 Traffic management functions

2.1.1 Connection Admission Control (CAC)

Figure 1. Connection Admission Control (CAC)

6 (51) © Nokia Networks Oy 6-282561

2.1.2 Usage / Network Parameter Control (UPC/NPC)

Usage/Network Parameter Control (UPC/NPC), also known as traffic policing,

UPC ATM NPC ATM

Traffic policing is defined as a set of actions taken by the network to monitor

6-282561 © Nokia Networks Oy 7 (51)

Not Conforming Cell

Not Conforming Cell

Figure 3. Possible example of Dual Leaky Bucket ( Peak Cell Rate,

2.1.3 Traffic shaping

Traffic shaping is a mechanism that alters the traffic characteristics of a stream

8 (51) © Nokia Networks Oy 6-282561

order to ensure that the receiving user application operates in an acceptable

ATM Router ATM switch

Actual data Shaped data Within an envelope?

Figure 4. Traffic shaping and traffic policing

User A Network A Network B User B

Shaping Policing Shaping Policing Shaping

Shaping Policing Shaping Policing Shaping

Figure 5. Generic placement of policing and shaping functions

6-282561 © Nokia Networks Oy 9 (51)

2.1.4 Priority control

2.1.5 Frame Discard

2.1.5.1 Partial Packet Discard (PPD)

10 (51) © Nokia Networks Oy 6-282561

PPD discards cells

Figure 6. Partial Packet Discard (PPD)

2.1.5.2 Early Packet Discard (EPD)

When the buffer level exceeds the EPD

Figure 7. Early Packet Discard (EPD)

6-282561 © Nokia Networks Oy 11 (51)

2.2 Traffic contract and negotiation

2.2.1 ATM quality of service (QoS)

The QoS parameters that are negotiated:

The QoS parameters that are not negotiated:

12 (51) © Nokia Networks Oy 6-282561

2.2.2 Traffic descriptors

The traffic parameters describe traffic characteristics of a source. The traffic

Figure 2. Peak Cell Rate (PCR)

• Sustained Cell Rate (SCR)

TSCR Nominal Flow

Figure 3. Sustained Cell Rate (SCR)

6-282561 © Nokia Networks Oy 13 (51)

• Burst Tolerance (BT)

TSCR Nominal Flow

Figure 4. Burst Tolerance (BT)

• The Maximum Burst Size (MBS)

TPCR Real Flow

TSCR Nominal Flow