GN3 view on multi-d domain services and its implications on NOC - - PowerPoint PPT Presentation

GN3 view on multi-d implications on NOC implications on NOC

Ann Harding (SWITCH) TF-NOC preparation me Copenhagen, Denmark,

domain services and its Cs Cs

eeting 3.5.2010

connect • communicate • collaborate

Agenda

Starting point for multi Starting point for multi Delivering Connectivit Supporting Services Supporting Services Blurring the bounda N t k M t Network Management History Standards-based a Community-specific y p domain services domain services y Services s aries t pproaches c needs

connect • communicate • collaborate

The same, but different

NOCs participating in the p p g GN3 multi-domain environment Di it f Diversity of

• rganization, structure,

and roles

NOCs cope with similar issues, in very different ways for local scope ways for local scope Lack or partial or custom adoption of Operational Support Systems functions Support Systems functions

connect • communicate • collaborate

Starting point

GN2/GN3 results so far: Multi-domain services’ definition Multi-domain services definition Manual or semi manual service deliv Multi-domain toolsets for

– Topology modeling – Monitoring the physical/logic – Provisioning – Implementation of specific m – Developed as silos with no coher

support pp

TF-NOC is an opportunity: To exchange expertise, best-practic processes in NOCs processes in NOCs To define standards’ based NOC bu seamless adoption of multi-domain very

al infrastructure multi-domain workflows rent requirements from NOCs on operational

ces, methodologies for optimizing internal usiness processes and OSS functions for the services

connect • communicate • collaborate

Multidomain Services - S Services Services What is a service anyway What is a service anyway More than infrastructu Intra & Interdomain boun Intra & Interdomain boun My network is part of * How does this fit with t How does this fit with t One to many or many Th “ h d” f t The “overhead” of auto upporting y? y? re daries of responsibility daries of responsibility *our* service the NOC mindset? the NOC mindset? to many? ti i it th?

• mation - is it a myth?

connect • communicate • collaborate

Blurring the boundaries

Who delivers connectivity ser 90s answer - NOCs Now - it is complicated S i b i d i d Services being designed Wavelengths Bandwidth on Demand Bandwidth on Demand Monitoring Working together Security teams, AAI, deve How do we be sure we do no Research to the rescue! Research to the rescue! rvices? elopers, vendors t drop the ball?

connect • communicate • collaborate

Network management evo

90’s

Device management perspective – Network management meant device and monitoring SNMP – Simple Network Manageme p g Protocol

2000’s

Network Management means much w set of activities set of activities Emphasis on service provisioning an management, designing OSS/BSS to “Old” network management is only on g y

• f the overall activity

Multi-domain network services, user- accessible composable services are subsets of Network Management in t subsets of Network Management in t modern sense Operations, planning of services, ma

• utreach, user support processes ca

be mapped onto standardized NM be mapped onto standardized NM frameworks

• lution

control ent

management

wider

management

network management

d

• ols

ne part

software d i networking

p

• the

design networking

the rket n also

connect • communicate • collaborate

Network management sta

GN3 Joint Research Activity 2 (J standards: standards:

TeleManagementForum (eTOM, S ITU-T (M and Y standards) ETSI-TISPAN (WG 8) IETF/IRTF DMTF MEF, OIF, OGF ITIL

S l i Some conclusions:

TMF appears to be the most releva ETSI TISPAN, SID is being increm – IPSphere covers some multi-domain i ITU-T NGN architecture can be us Network Management Architecture

andards

JRA2) analyzed NM related

SID, NGOSS/TNA, TAM, IPSphere) ant: eTOM is fully adopted by ITU-T, mentally adopted by ITU-T

issues, but assumes existing OSS/BSS

ed as a model for a multi-domain e by GN3 (GN3 NMA)

connect • communicate • collaborate

Network management vie Network management is Network management is can be seen from differen

Business processes (e.g. p ( g facto’ standard for busines decomposition) F ti l ( li ti ) i Functional (application) vi components Information/Data models u Information/Data models u implementation Architectural principles (S principles)

(At least) TMF and ITU-T i views ews a very complex activity that a very complex activity that nt perspectives:

TMF’s eTOM provides the ‘de p ss process description and th t d ib b i OSS ews that describe basic OSS used in the OSS design and used in the OSS design and ervice Oriented Architecture

T are converging in their

connect • communicate • collaborate

TMF views of Network Management

TMF Framework

connect • communicate • collaborate

GN3 environment

Multi-domain Distinguished transport and servic

Based on ITU-T/TMF recommendat

OSS functions in both strata of ea OSS functions in both strata of ea ce stratum functions

tions

ach domain ach domain

connect • communicate • collaborate

Multi-domain network ma the effect on NOC operat the effect on NOC operat

NOCs typically deal with transport stratum with transport stratum functions NOC possible shift of focus: from device configurations/ monitoring to OSS monitoring to OSS

• perations

The network exists to provide services to provide services to users)

Sound policy and it h security scheme Automated multi- domain services based domain services based

• n OSS functions

anagement: ions ions

NOC

connect • communicate • collaborate

A first step: the GN3 NMA s

So far a business process view (eTOM to the GN3 multi-domain case) Service Stratum: processes for the Transport Stratum: network manag

specification

Service and Resource processes mapped support of multi-domain services ement processes

connect • communicate • collaborate

A gradual approach

Adopt a standards’ based inform

TMF SID DMTF CIM

• ther?

TMF SID, DMTF CIM… other? Supporting policies, context …

Define a common subset of NO

Starting from TMF recommendatio practices….other?

Engineer NOC OSS functions a g TNA (SOA principles) Define business processes ado

Organization mapping Organization mapping Process workflows Specification of the OSS functions processes processes

Define inter-OSS functions need business processes and (b) serv i t environment mation/data model C OSS functions

• ns (TNA), existing OSSs, best

according to the TMF NG-OSS g pted by a NOC based on eTOM

s involved in each one of business

ded by NOCs to support (a) vices, in a multi-domain

connect • communicate • collaborate

Directions

GN3 ongoing work Standardized Information/

– Feedback from GN3 to

S i Synergies Specification of a minimum Transport Stratum Transport Stratum

– So that NOCs participa

can support a minimum processes

– A proposed TF-NOC a

with GN3 JRA2 with GN3 JRA2 Specification of multi-dom Others? Others? /Data model

• TF-NOC

m set of OSS functions at the ating in the multi-domain chain m common set of business agenda item in collaboration main OSS functions?

connect • communicate • collaborate

Contact points

For GN3 work on a multi-dom architecture and OSS function Afrodite Sevasti, <sevasti@ Pavle Vuletic, pavle.vuleti For GN3 work on multidomain A H di h di @ Ann Harding ann.harding@ Brian Bach Mortensen <b main network management g ns: @grnet.gr> c@rcub.bg.ac.rs n service design: @ it h h @switch.ch rian@nordu.net>

connect • communicate • collaborate