8/17/2019 C4hapter

1/48

Chapter 4

Functional, Physical

and logicalArchitecture

Author 

Prof. Dr Abdul Qadir

8/17/2019 C4hapter

2/48

5.1 What is !"#

• $t is a set of international standards for %anagingteleco% net&or's

• According to $() reco%%endation !.*1++

  !" is conceptually a separate net&or'

that interfaces a teleco%%unication net&or'

at se-eral dierent points to send/recei-e

infor%ation to/fro% it and to control its

operation0

• his %eans the idea of !" is to use anindependent

%anage%ent net&or' to %anage a

teleco%%unication net&or' by co%%unicating -ia

&ell dened and standardi2ed interfaces.

8/17/2019 C4hapter

3/48

Cont3

Why standards are reuired#

• because teleco% net&or's typicallyconsist

of net&or' ele%ents of dierent

technologies supplied by %ultiple-endors

• ee Fig.5.1. $t sho&s relationshipbet&een

a !" and the teleco%%unicationnet&or' it

%ana es

8/17/2019 C4hapter

4/48

 !" consists of 6 7peration syste%s

 data co%%unication net&or's

 %anaged net&or' ele%ents

• 7peration syste% i%ple%ents%anage%ents

functions in coordination &ith portion of

net&or' ele%ents that fall in the !"

do%ain 8i.e. switches, transmission systemsetc. )

8/17/2019 C4hapter

5/48

5.9 !anaged net&or's

 his includes any co%bination offollo&ing technologies6

• circuit s&itched or pac'et s&itched

net&or's• public s&itched telephone net&or's

•  Pri-ate enterprise net&or's

• con-entional P" or intelligentnet&or'

8/17/2019 C4hapter

6/48

!anaged euip%ents

:uip%ents in %anaged net&or'%ay include6

• trans%ission lines

• digital s&itches• analog s&itches

• soft&are to be %anaged

• ser-ices, these reuire ser-ice%anage%ent

8/17/2019 C4hapter

7/48

5.* !" Architecture layers

•A set of architectures that collecti-elypro-ide

a for%al architectural foundation for

the%anage%ent of teleco%%unications

net&or's

that up until their introduction hadlargely

been ad hoc practice

• hese include physical, functional,

8/17/2019 C4hapter

8/48

Fig. 5.1

;eneral relationship of !" to a teleco%%unication net&or's

 

7perating

syste%

7perating

syste%

7perating syste%

7peratingsyste%

Data co%%unicationnet&or'

s&itch

 rans%ission syste%

 rans%ission syste%

s&itch

8/17/2019 C4hapter

9/48

Co%ponents of eleco%%unicationyste%

  Figure 5.9

8/17/2019 C4hapter

10/48

5.* !7$

8/17/2019 C4hapter

11/48

Proprietary en-iron%ent6

All teleco% net&or's are proprietary. othese are unable to interoperate &ith eachother. >ence %anage%ent reuired

!ulti-endor en-iron%ent6• here is no ho%ogeneity a%ong -endor?snet&or'.

•"o&adays the net&or' of ser-ice pro-ider is

%ade of euip%ent fro% %ultiple -endors.•o di@cult to operate

•>ence e@cient %anage%ent reuired

8/17/2019 C4hapter

12/48

Cont..

ac' of integration6

• $n con-entional teleco% net&or's a seriousproble% &as that ser-ice &as often tightly coupled&ith special resource

• >ence %anage%ent syste% is reuired to cater

to each ser-ice resource pair.• "o&adays integrated syste%s eBist pro-idingco%prehensi-e -ie& of ser-ices and resources in

their net&or'.

• >o&e-er, it is di@cult to integrate under%ulti-endor and proprietary en-iron%ent

• >ence %anage%ent of this scenario is ta'en careof by !" syste%

8/17/2019 C4hapter

13/48

Cont..

ac' of auto%ation6• !ost net&or' and ser-ice%anage%ent

processes are %anual. his is becauseof lac' of

standardi2ation of the process

the%sel-es• i%ilarly &hen proprietary processbeco%es

outdated &ith euip%ent update•

8/17/2019 C4hapter

14/48

Cont..

"e& reality of teleco% industry6

• As ne& technology is introduced, pre-ious

practices are outdated

• "e& reuire%ents are created &ith

technological ad-ance, e.g. ;! euip%ent

&ill not &or' for *;. "e& set up ha-e been laid

do&n

• Another eBa%ple is that of intelligent net&or'.

$n it ser-ice processing fro% call processing and

net&or' resource functions. raditional syste%s

&or'ed such that call processing and ser-ice &ere

coupled

8/17/2019 C4hapter

15/48

Cont3

• As the teleco% net&or's arebeco%ing large and co%plicated,%anage%ent syste%s ha-e to be

able to scale up accordingly• "et&or' ser-ice e-ol-es &ith %orerapid pace, so %ust the

%anage%ent of ne& and %odiedser-ices be a-ailable at a %ore rapidpace

8/17/2019 C4hapter

16/48

5.4 "et&or' and er-ice %anage%ent reuire%ents

•  here are %any but the follo&ingneed special addressing

upport Auto%ation

• $ncreased co%pleBity andderegulated &orld&ide teleco%%ar'et, %anual operation is too

eBpensi-e• >ence auto%ation is needed &hich%ust be -ia standard)based syste%s

8/17/2019 C4hapter

17/48

 !" =eco%%endations

8/17/2019 C4hapter

18/48

$nteroperability support6

• his is reuire%ent by %ar'et, regulation andtechnological ad-ances

• $nteroperability bet&een dierent ser-ices is

%andated by regulation such as eleco%%unication

Act 1EE in (A• Con-ergence of %ultiple technologies 8e.g. -oice,

data, ynchronous 7ptical "et&or' 87": andA!,

&ireless and &ireline and %erging of %ar'ets 8e.g.$nternet, P", cable telephony business %a'e

interoperability bet&een the di-erse %anage%ent

syste%s %ore i%portant than e-er

8/17/2019 C4hapter

19/48

upport rapid technological

e-olution6

=apid technological ad-ances, rapid%ar'et e-olution and global %ar'et

%a'e it i%perati-e for a net&or' andser-ice %anage%ent paradig% to beable to adapt this rapid pace of

change

8/17/2019 C4hapter

20/48

5.4 !" Functional Architecture

$ntroduction6•$t consists of a set of functional bloc's, a set of

reference points and a set of functional co%ponents

• Functional bloc' is a logical entity that perfor%s

a prescribed %anage%ent function.• =eference point separates a pair of functional bloc's,

and t&o functional bloc's %ust co%%unicate -ia a

reference point. ee Fig.5.*

• $t is not necessary that all should be present ineach !" conguration

• Fig. 5.9 describes -arious types of net&or'

congurations

8/17/2019 C4hapter

21/48

Fig.5.98a6 !anage%ent yste% and its $nterface

(ser

Accessco%puter

A%anage%ent

syste%

A dierentagent

Co%plaintagent

"et&or'ele%ent A

Proprietaryagent

"et&or'ele%ent G

8/17/2019 C4hapter

22/48

Fig.5.98bGasic co%ponents of a eleco% net&or'

8/17/2019 C4hapter

23/48

Fig.5.98cWide Area "et&or'

8/17/2019 C4hapter

24/48

Fig.5.98d Wide Area "et&or'

WA"

7ntari

o

"or&ay

Gelgiu%

Pensyl-ania

California

GritishColu%b

ia

 HapanDo%inica

n=epublic

8/17/2019 C4hapter

25/48

Fig.5.98e ocal Area "et&or'

8/17/2019 C4hapter

26/48

Fig.5.98f 7ther :)business net&or's

8/17/2019 C4hapter

27/48

8/17/2019 C4hapter

28/48

Fig.5.98g Client er-er net&or'ing

8/17/2019 C4hapter

29/48

 eleco% Processors and oft&areIs

Processors

•   Modems

• Multiplexers

•   InternetworkProcessors – Switches

 – Routers

 – Hubs – Gateways

•  Fire walls

Sotware!s

• "etwork #peratin$

System•   %elecommunications

Monitor 

•   Middleware

• "etwork Mana$ementSotware

8/17/2019 C4hapter

30/48

•!anage%ent syste%s %anages t&o net&or'

ele%ents• "et&or' ele%ent A has an agent &ith a

standards co%plaint interface, and the other

ele%ent is fro% a dierent -endor &ith an

agent that has a proprietary %anage%ent

protocol

• (ser can access the net&or' %anage%ent -ia

a re%ote access co%puter• he %anage%ent syste% is connected to

another %anage%ent syste% of yet another

%anage%ent protocol.

8/17/2019 C4hapter

31/48

5.5  !" Functional Gloc's

1. !" is to %anage a teleco% net&or' consisting

of di-erse net&or' ele%ents fro% dierent-endors. o acco%plish this %anage%ent goal, thefollo&ing co%ponents are in-ol-ed6

 A set of %anage%ent functions to %onitor,control and coordinate the net&or'

 a set of %anaged net&or' ele%ents

 the capability for the !" user to access the%anage%ent operations and to get apresentation of the operation results

9. $n addition there shall be the capability tocon-ert %anage%ent infor%ation in aproprietary for%at into a standard !" for%atto achie-e the interoperability.

8/17/2019 C4hapter

32/48

 here are -e functional bloc' to

acco%plish the abo-e described%anage%ent6

1. 7peration yste% Function 87F

9. "et&or' :le%ent Function 8":F*. Wor'station Function 8WF

4. !ediation Function 8!F

5. Q)adaptor Function 8QF

Fig 5 * Functional Gloc's and =eference

8/17/2019 C4hapter

33/48

Fig. 5.* Functional Gloc's and =eferencePoints

  f 

 

f f 

*

  *

  B

* f 

 

%

WF

!F7F

QAF ":F

8/17/2019 C4hapter

34/48

Functional bloc's as copied fro% !" =eco%%endations

8/17/2019 C4hapter

35/48

7F8operating syste% function

• $t is %anager

•$t pro-ides bul' of %anage%ent facility

• $t process %anage%ent infor%ation for the purpose of %onitoring, coordinatingand controlling teleco% net&or's

Core ser-ices pro-ided by 7F6

Application support in the areas of conguration, fault, perfor%ance,

accounting, and security %anage%ent

Database functions to support net&or' resources, conguration, topology,

control states and status

(ser ter%inal support to pro-ide hu%an %achine interface capabilitiesAnalysis progra%s pro-iding the analytical capability in fault and perfor%ance

analysis

Data for%atting and reporting to support the co%%unication bet&een t&o

 !" functional entities or bet&een a !" function bloc' and an outside entity

8e.g. a hu%an user or another !"

Analysis and decision support to pro-ide the decision)%a'ing capabilities to the%anage%ent applications

$ts %aJor co%%unication is &ith net&or' ele%ent function ":F 8through referencepoint *.

8/17/2019 C4hapter

36/48

7F

":F

=eference point*

Fig.5.46 7F)":FCo%%unication

8/17/2019 C4hapter

37/48

":F 8"et&or' :le%ent Function

$t presents a -ie& of the %anaged

net&or' ele%ents to the 7F and itpro-ides the net&or' being %anaged &ithteleco% and support functions.

Pri%ary responsibility is to handle tra@c,8see Fig.5.5

 

Fig.5.5

7F ":F

=eference point *

8/17/2019 C4hapter

38/48

When obser-ed closely, it can be

seen that6• QF and 7F are dra&n &ithin boBlabeled

  !"• his %eans these functional bloc'sare co%pletely specied by !"

reco%%endations• WF, ":F and QAF are dra&n at theedge of the boB

• his only parts of these functional

8/17/2019 C4hapter

39/48

!F 8!ediation Function

•$t acts on infor%ation passing

bet&een an 7F

and ":F.

•$t pro-ides storage, adaptation,

ltering,

thresholding and condensingoperations on

the data recei-ed fro% the ":F

• $t also routes and acts oninfor%ation Ko&ing

bet&een a %ana er and an a ent.

8/17/2019 C4hapter

40/48

QAF 8Q)Adaptor function

• Pro-ides translation capability toconnect a

proprietary ":F or 7F to a !"

• $t also pro-ides capability toconnect a non)

  !" ele%ent to !"

• $t is a capability of !" to gi-enthat its

%ission is to integrate eBistinglegacy

8/17/2019 C4hapter

41/48

WF8Wor'station Function

• Pro-ides functionality for interaction

bet&een a hu%an user and the 7Fs.• $t can be -ie&ed as a %ediation bet&een a

hu%an user and the 7F

• $t con-ert infor%ation co%ing out of a 7F

into a for%at that can be presented to a user

and -ice -ersa.

• $t is not considered the full part of !" and

hence is sho&n at the edge of !" boundary• $t co%%unicates -ia g)reference point8discussed

later

8/17/2019 C4hapter

42/48

5.=eference points

Reference point6

• he intention of reference points is to dene ser-iceboundaries bet&een t&o %anage%ent function bloc's

• also to identify the %anage%ent infor%ation passingbet&een function bloc's

• Another &ay to dene is that it is Conceptual point of

infor%ation eBchange bet&een non)o-erlapping%anage%ent

function bloc's.

• reference point is a logical entity, its

implementation is an interface

 

8/17/2019 C4hapter

43/48

Classes of =eference points

1. class6 reference point bet&een ":F and

7F, QAF or !F. Within this class &e ha-e

qx  6 &hich is bet&een ":D and QAF, or !F andbet&een t&o !F

q36 bet&een ":F and 7F, !F and 7F and 7F and

7F9. f class6 it is for attach%ent to WF

*. x  class6 $t is bet&een to 7Fs belonging to dierent !"s

4. g point6 bet&een WF and the operating personnel5. m point6 bet&een QAF and non)!" %anaged

entities 8e.g. proprietary interfaces

 

8/17/2019 C4hapter

44/48

Can also be su%%ari2ed as6

TMN reference points:

.q reference points- qx: Between NEF and MF, QAF and MF, MF and MF

-q3: Between NEF and OSF, QAF and OSF, MF and OSF, OSF and OSF

.f reference points- Between WSF and OSF, WSF and MF

.x reference points- Between the OSF function blocks in different TMNs

Non -TMN reference points:

g reference points - Between human users and the WSF

m reference points

 - Between QAF and non-TMN managed entities

=eference Points

8/17/2019 C4hapter

45/48

Get&een !anage%ent Function Gloc'sFig.5.

8/17/2019 C4hapter

46/48

$%ple%entation of a reference point is

an interface.

ee Fig.5.L

8/17/2019 C4hapter

47/48

Fig.5.L !" Functional Architecture $llustration

  g

 

f 

  x 

 

q

  q q

 m

(ser

Accessco%puter

!anage%ent syste%

A dierent%anage%ent

syste%

co%pliant agent

Proprietary agent

":F Proprietary ":F

user

WF

7F

!F

":F Proprietary ":

QAF

7F

8/17/2019 C4hapter

48/48

•Fig.5.L illustrates %apping of !"

functional

architecture onto the net&or' eBa%ple

sho&n in Fig.5.98a

• he %anage%ent syste% %aps to 7F, andt&o net&or' ele%ents &ith an agent

%ap to t&o ":F?s

• access co%puter is WF

• $n addition t&o %ore function bloc's are

added6 he %ediation function and the

Q)adaptor