Abstract Information Model
 An abstract model contains all the pieces of information that
are essential towards the software abstraction of the
resources and traffic load conditions of a multiplexing unit;
 It remains independent of vendor-specific characteristics and
capabilities, thus enabling integrated traffic control over a
heterogeneous networking environment;
 It allows for transparent upgrades and for customisation to
the individual needs of Network Operators or Service
Providers;
 It provides generic interfaces to TCAs;
Network Management
1
An ATM Switch-Independent MIB
 The proposed Switch-Independent MIB defines an abstract
information layer for portable deployment of TCAs.
 Although, the emphasis is mainly placed on CAC, the SIMIB offers generic interfaces for routing and resource
allocation/configuration functions.
 The SI-MIB enhances the information fields of existing
ATM related MIBs with appropriate generic constructs for
TCAs.
Network Management
2
Design of the SI-MIB
Identification of common
generic information items
Review of existing ATM
related MIBs
SI-MIB
Review of existing
CAC schemes
Network Management
3
Review of ATM MIBs
 Existing ATM MIBs have been defined by the following
standards bodies:
ATM Forum (SNMP and CMIP);
ETSI (CMIP);
IETF (SNMP);
ANSI (SNMP);
NM Forum (CMIP);
Bellcore (CMIP);
ITU-T (CMIP);
 In addition, there are proprietary MIBs (primarily SNMP-based)
developed by vendors.
 The proposed SI-MIB has the ability of semantically representing
information elements in various major standards-based and
proprietary MIBs.
Network Management
4
Skeleton of the Switch-Independent MIB
Switch
SwitchID, Name, Vendor, Model, Address,
numPorts
port
portID, linkBw, BufferSize,
numQoSLevels
QoSLeve
l
QoSValue, allocBuffer, allocBw,
background_traffic, TrCACparams, numclasses,
acceptedCalls, rejectedCalls
class
Type, Traffic_Descriptor,
numCalls
call
Network Management
VPI, VCI,
RefNum
5
The Proposed Software Infrastructure
System hierarchy
Traffic Control
Algorithms (TCAs)
P1520 classification
TCAs
Interfaces
Resource
Configuration/
Allocation
NGSL
Routing
CAC
Switch-Independent
Interface
Switch-Independent
MIB (SI-MIB)
L Interface
software representation of ATM
switch switching hardware
resources and load conditions
Switch-Specific
Interface
VNDL
CCM Interface
ATM Switching System
PE Level
Network Management
6
The P1520 Reference Model
End-user applications
V-Interface
Algorithms for value-added communication
services created by network operators, users
and third parties
U-Interface
Algorithms for routing, connection
management, admission control, etc.
L-Interface
Virtual network devices (software
representation)
CCM-Interface
Physical elements
Network Management
Value-Added
Services Level
(VASL)
Network-Generic
Services Level
(NGSL)
Virtual Network
Device Level
(VNDL)
Physical Element
(PE) Level
7
Open platform architecture for embedding traffic
control functionality in ATM networks
NNI
TC
NNI
L - Interface
(P1520)
UNI
TC
UNI
TC
SI-MIB
L - Interface
(P1520)
L - Interface
(P1520)
SI-MIB
Core Network
SI-MIB
Access Node
Access Node
SI-MIB: Switch-Independent MIB
TC: Traffic Control functionality (CAC, routing, etc.)
Network Management
8
Virtual Signaling Protocol
Current signaling standards do not support externally defined
traffic control functionality.
Thus
An open signaling protocol, which ensures that the enhanced
control functionality supported by the presented software
architecture can be communicated between different switches, is
necessary.
The examination of VSP messages that run through the L
interface (of the P1520 model) constitutes one of the main objective
of the paper.
Network Management
9
Interactions in case of an Accepted Call
Request
NNI
Source
UNI
(1) call_req
(16) connect
SrcRM
(2) start_CAC
UNI
(11) call_req_cont
(6) call_req_cont
(13) connect
(5) CAC_ok
(12) connect
DestRM
(7) start_CAC
Intermediate CAC
entities accept the
call request
(10) CAC_ok
(17) update
SrcCAC
NGSL
(14) update
(18) create_conn
(4) CAC_info
Destination
DestCAC
(9) CAC_info
L Interface
(3) ask_info
(15) create_conn
(8) ask_info
SrcSI-MIB
DestSI-MIB
VNDL
CCM Interface
SrcSwitch
DestSwitch
Network Management
10
Call Rejection by the Network
NNI
Source
UNI
(1) call_req
(13) call_reject
(6) call_req_cont
SrcRM
DestRM
(11) call_reject
(12) There is no
alternative route
(2) start_CAC
(7) start_CAC
(10) CAC_reject
(5) CAC_ok
SrcCAC
(4) CAC_info
Intermediate CAC
entities accept the
call request
DestCAC
(9) CAC_info
L Interface
(3) ask_info
NGSL
(8) ask_info
SrcSI-MIB
DestSI-MIB
VNDL
CCM Interface
SrcSwitch
DestSwitch
Network Management
11
Call Rejection by the Destination
Destination rejects
the call request
NNI
Source
UNI
(1) call_req
(14) call_dest_reject
SrcRM
(5) CAC_ok
(2) start_CAC
SrcCAC
(4) CAC_info
(6) call_req_cont
(13) call_dest_reject
Intermediate CAC
entities accept the
call request
UNI
(11) call_req_cont
Destination
(12) call_dest_reject
DestRM
(7) start_CAC
(10) CAC_ok
NGSL
DestCAC
(9) CAC_info
L Interface
(8) ask_info
(3) ask_info
DestSI-MIB
SrcSI-MIB
VNDL
CCM Interface
DestSwitch
SrcSwitch
Network Management
12
Call Release
NNI
Source
UNI
(1) call_release
UNI
(9) call_release
(2) call_release
SrcRM
Destination
DestRM
NGSL
(3) call_release
(10) call_release
(6) CAC_release
(13) CAC_release
(7) update_release
SrcCAC
(14) update_release
DestCAC
(8) release_conn
(5) CAC_info_release
(4) call_release
L Interface
(15) release_conn
(12) CAC_info_release
(11) call_release
SrcSI-MIB
DestSI-MIB
VNDL
CCM Interface
SrcSwitch
DestSwitch
Network Management
13
A Prototype Implementation
A prototype system that follows the proposed architectural framework and
makes use of intelligent software agents was implemented.
Although not mandated by the design, and for facilitating the implementation
process:
The software enttities of the prototype infrastructure have been built on top
of an agent platform that supports communication primitives according to
the ontology specified by the FIPA organization,
 The underlying agent platform used in the implementation was based on
background work, conducted in the scope of the IMPACT research project.
Network Management
14
Structure of the Implemented Software
Infrastructure
Two different types of agents may be identified:
CRA
Routing
CAC
L Interface
SWA
ATM Switching
System
The Switch Wrapper Agent that furnishes an
abstract software environment for performing
management and control operations on an ATM
switch.
The CAC & Routing Agent, which is the
software entity expressing in abstract and
portable terms the actual traffic control
algorithms.
Network Management
15
An Intelligent Agents-based Prototype
Implementation
Source Agent
RMI
CAC&Routing Agent
CAC
GUI
RT1
Generator
Interface
RT2
RMI
RMI
SI-MIB
SI-MIB
Traffic
Generator
D
CAC points
Path #1
Path #2
SI-MIB: Switch-Independent MIB
RT: Routing Table
Network Management
16
CAC & Routing Agent
CRA
CRAWorkerThread
incoming calls
queue
CallProcessThreads list
Instances a thread for
each call in the queue
RMI call from an
agent peer
CallProcessThread
Asks
PortInfo
for CAC
Put request in queue
CallRequest_dispatcher()
Returns call request result. For accepted calls, it creates
crossconnections on the switches and updates their SI-MIBs.
Network Management
17
PortInfo Class
PortInfo
PortThread
CAC
Returns true
or false
Calls queue
Call on a PortInfo
instance
addRequest()
Put request in queue
Network Management
18
The Proposed Software Multi-Agent System
UNI
CMA
NNI
TA
L - Interface
UNI
CMA
CELL A
SWA
L - Interface
TA
CMA
SWA
Core Network
Move
L - Interface
TA
SWA
Fixed
terminal
CELL B
Mobile
terminal
Switch radio port
First connection
Second connection
TA: Terminal Agent
SWA: Switch Wrapper Agent
UNI: User Network Inetrface
NNI: Network Network Interface
CMA: Connection Management Agent
Network Management
19
CMA Subagents
 Connection Admission Control Agent (CACA)
decides to either accept or reject a connection
request following the rules of a CAC scheme.
CMA
Database
CACA
Mobile hosts
registrations
RA
CA
 Routing Agent (RA) accomplishes for each
connection request a routing algorithm in
order to compute a path that connects the
connection’s source and destination.
 Connection Agent (CA) is responsible for
establishing, maintaining and releasing the
ATM switches’ VCCs, which are involved in
the requested connection.
Network Management
20
Second Intermediate Report

HP OPENVIEW NETWORK NODE
MANAGER



I. Stergiou
A. Sgora
Deadline: 27/05/03
Network Management
21
End of Fourth Lecture
Network Management
22